- Welcome to 8BitChip Forum.
Recent posts
#41
FAQ / Re: Mass storage (hard disk, n...
Last post by Petari - 22-07-2025, 13:56:20Quote from AF :
" TheNameOfTheGame wrote: Thu Jul 17, 2025 8:22 pm
For people copying over to real hardware sdcard or such they will be copied over as LFN with some software which could cause issues with TOS.
FYI, EmuTOS doesn't suffer from that issue (Atari TOS does). It silently ignores all LFN artificats. This might explain why this wasn't noticed." .
Oh, sure, "buggy" Atari TOS 'suffer' - they were not aware that some 10 years later LFN will be introduced. Lamers ! So, let's all we upgrade to EmuTOS ! Or maybe to Win 11 ?
Really pathetic. Btw. I saw lot of Atari SW packages (ZIP usually) with LFN online in latest decades.
Dealing with very old SW (and TOS is it too) means knowing what it needs to work well. Surely not things which did not exist when it was created, developed. And Atari ST SW needs compatible TOS - with self , not with some later C standards, recommendations .
" TheNameOfTheGame wrote: Thu Jul 17, 2025 8:22 pm
For people copying over to real hardware sdcard or such they will be copied over as LFN with some software which could cause issues with TOS.
FYI, EmuTOS doesn't suffer from that issue (Atari TOS does). It silently ignores all LFN artificats. This might explain why this wasn't noticed." .
Oh, sure, "buggy" Atari TOS 'suffer' - they were not aware that some 10 years later LFN will be introduced. Lamers ! So, let's all we upgrade to EmuTOS ! Or maybe to Win 11 ?
Really pathetic. Btw. I saw lot of Atari SW packages (ZIP usually) with LFN online in latest decades.
Dealing with very old SW (and TOS is it too) means knowing what it needs to work well. Surely not things which did not exist when it was created, developed. And Atari ST SW needs compatible TOS - with self , not with some later C standards, recommendations .
#42
FAQ / Re: Mass storage (hard disk, n...
Last post by TheNameOfTheGame - 17-07-2025, 12:16:39I still have and use iTOS on my quad-TOS STE and I find it very well done with cool and useful features built-in.
#43
FAQ / Re: Mass storage (hard disk, n...
Last post by Ronald J. Hall - 16-07-2025, 17:08:48Thanks for the explanation Peter. 
#44
FAQ / Re: Mass storage (hard disk, n...
Last post by Petari - 16-07-2025, 12:04:45 I need to add here some things. Used some harsh words - idiotic, stoopid and like. Well, how should react on writings which say that TOS, old Atari SW is buggy.
" rely on weird patterns or buggy TOS error codes to work properly"
Really, this is something stupidest I did read in some computer related text, article.
TOS was released in 1985 and Atari ST had good sales, lot of SW from diverse firms, hobby programmers and like was released. And of course TOS DOCs by Atari, lot of it in magazines, books. I bought in 1987 April Atari 520 ST, and in same time Atari ST ProfiBuch - some 700 pages, and there were detailed descriptions how to use TOS function calls (Trap #1, #13, #14 ...) . All it was pretty consistent, and nothing weird. And of course it stays for error codes - and was not so much of them.
In same year, 1987 first updated TOS v. arrived - v 1.02 . It was not bug fixing, but doing diverse things better. And updating OS was normal thing by other firms too. I barely used 1.02 - went on 1.04 and 2.06 few years later. And they have significantly better hard disk support, filesystem.
I'm not saying that TOS was perfect - there are some flaws, and I wrote about some on my Atari WEB pages.
Some fixes appeared too - like Folder 100 - what is not bugfix. It just expands something - of course at price of some RAM used. I never needed it. Well, I programmed in ASM since 1987, made some floppy util SW, RAMdisk ... In 1992 went on IDE hard disk with Atari . And that was when did making floppy based games to work from hard disk. It was especially useful with 4 floppy based Microprose F1 GP .
And more about it: some call it 'patching', some 'conversion', some 'cracking' . Surely deactivating copy protection is needed, but that's only part of needed things. Conversion is not really good - there is need first to understand game's code - like custom floppy code, and I saw really a lot of diverse solutions, some with really weird and hard to follow, trace, understand code.
I say that 'adapting' is best term. Can not convert custom floppy code, you need to adapt it to hard disk usage. And that can be done in different ways.
Important factor is percentage of diverse program/SW solutions by games.
There are details on my pages: https://atari.8bitchip.info/doinadapts.html
So, most is with TOS function calls. That needed making TOS 1.04 running in RAM - what solves multiple things: TOS version incompatibility problems, special hard disk access from game, support for game state saves and exit to Desktop ...
Needed disassembling properly TOS 1.04 - and that was long process. First versions were with only GEMDOS part - without AES, Desktop, as most of games is with AUTO run.
Later I solved AES/Desktop part disasm. too . It is needed for games using TOS AES functions , so windows, menus and functions in second part of TOS .
To make if work faster I combined my older disk access system with HAGA, HAGE systems:
https://atari.8bitchip.info/imprhage.html
All this was lot of work, but resulted in being able to do individual game adaptations much faster.
Plus, did improved TOS versions, which are compatible with old Atari SW, games. Unlike EmuTOS .
Must be because my iTOS is buggy (as everything I do) like old Atari SW is buggy 
" rely on weird patterns or buggy TOS error codes to work properly"
Really, this is something stupidest I did read in some computer related text, article.
TOS was released in 1985 and Atari ST had good sales, lot of SW from diverse firms, hobby programmers and like was released. And of course TOS DOCs by Atari, lot of it in magazines, books. I bought in 1987 April Atari 520 ST, and in same time Atari ST ProfiBuch - some 700 pages, and there were detailed descriptions how to use TOS function calls (Trap #1, #13, #14 ...) . All it was pretty consistent, and nothing weird. And of course it stays for error codes - and was not so much of them.
In same year, 1987 first updated TOS v. arrived - v 1.02 . It was not bug fixing, but doing diverse things better. And updating OS was normal thing by other firms too. I barely used 1.02 - went on 1.04 and 2.06 few years later. And they have significantly better hard disk support, filesystem.
I'm not saying that TOS was perfect - there are some flaws, and I wrote about some on my Atari WEB pages.
Some fixes appeared too - like Folder 100 - what is not bugfix. It just expands something - of course at price of some RAM used. I never needed it. Well, I programmed in ASM since 1987, made some floppy util SW, RAMdisk ... In 1992 went on IDE hard disk with Atari . And that was when did making floppy based games to work from hard disk. It was especially useful with 4 floppy based Microprose F1 GP .
And more about it: some call it 'patching', some 'conversion', some 'cracking' . Surely deactivating copy protection is needed, but that's only part of needed things. Conversion is not really good - there is need first to understand game's code - like custom floppy code, and I saw really a lot of diverse solutions, some with really weird and hard to follow, trace, understand code.
I say that 'adapting' is best term. Can not convert custom floppy code, you need to adapt it to hard disk usage. And that can be done in different ways.
Important factor is percentage of diverse program/SW solutions by games.
There are details on my pages: https://atari.8bitchip.info/doinadapts.html
So, most is with TOS function calls. That needed making TOS 1.04 running in RAM - what solves multiple things: TOS version incompatibility problems, special hard disk access from game, support for game state saves and exit to Desktop ...
Needed disassembling properly TOS 1.04 - and that was long process. First versions were with only GEMDOS part - without AES, Desktop, as most of games is with AUTO run.
Later I solved AES/Desktop part disasm. too . It is needed for games using TOS AES functions , so windows, menus and functions in second part of TOS .
To make if work faster I combined my older disk access system with HAGA, HAGE systems:
https://atari.8bitchip.info/imprhage.html
All this was lot of work, but resulted in being able to do individual game adaptations much faster.
Plus, did improved TOS versions, which are compatible with old Atari SW, games. Unlike EmuTOS .
Must be because my iTOS is buggy (as everything I do) like old Atari SW is buggy
#45
FAQ / Re: Mass storage (hard disk, n...
Last post by Petari - 10-07-2025, 19:39:40And what can see on ACSI2STM doc
Well, they even don't know that Falcon has no ACSI port.
Works with all SD cards except SDUC (was not tested yet). Well, my experience is that very high speed newer SD cards may have problems, especially by writing on them.
"In GemDrive mode, the SD card must be formatted either in FAT16, FAT32 or ExFAT format, with a single partition (the standard format for SD cards). The partition size is limited to 2TB."
So, only 1 partition. How it will look with some 10000 DIRs ? And surely will work slower than smaller size partitions. Yes, it is basically same is in Steem and Hatari - where 1 DIR on host is assigned as Atari drive.
TOS supports up to 14 partitions C-P . And more partitions means not lower speed, actually contrary - less data on 1 partition means faster work.
They say that few games with no copy protection will work. Yeah, considering originals. What about hard disk adaptations, patches ? As usual they have no clue what all is made.
"Software relying on bugs
These programs use the normal GEMDOS interface to access disk drives but rely on weird patterns or buggy TOS error codes to work properly."
And same idiocy as on page about how hard disks work on Atari (first post in this thread).
Buggy TOS error codes - huh ! They are not buggy. May be different than some later widely used ones - it is really so stoooopid to expect from SW done 40 years ago to be by some later standards .
"Software doing BIOS access
These programs access low level disks using BIOS or XBIOS interfaces.
Programs usually working like this:
Most disk utilities
Maybe some very weirdly programmed games
"
It is not weird to use (X)BIOS call to determine is it running from floppy or hard disk. I saw it many times, and is usually by games with hard disk install option, or declared that work from hard disk.
And they mentioning my early, freeware ACSI driver from 2008. I did lot of it from then.
What about extra functions like Virtual Floppy, automatic Desktop drive icons creation ? By them, it is also bug of TOS that only icon for C is created ... Is it bug that TOS is in limited size ROM ?
Lot of it is done with compromises because HW prices were pretty much higher then.
And really, why such huge disrespect toward Atari ST designers, OS programmers ? Sure, there were some smaller errors, maybe few bugs which show in rare cases. Just one example: it crashes when in drive Window in Desktop some file is of size 10 MB or more (TOS 1.xx) . Well, I did not know about it when I used my Atari at 1992 with 40-160 MB hard disks, simply because were no so large files. I saw it first time somewhere at 2008, when used Steem with it's hard disk system . And. btw I fixed problem in my iTOS .
Well, they even don't know that Falcon has no ACSI port.
Works with all SD cards except SDUC (was not tested yet). Well, my experience is that very high speed newer SD cards may have problems, especially by writing on them.
"In GemDrive mode, the SD card must be formatted either in FAT16, FAT32 or ExFAT format, with a single partition (the standard format for SD cards). The partition size is limited to 2TB."
So, only 1 partition. How it will look with some 10000 DIRs ? And surely will work slower than smaller size partitions. Yes, it is basically same is in Steem and Hatari - where 1 DIR on host is assigned as Atari drive.
TOS supports up to 14 partitions C-P . And more partitions means not lower speed, actually contrary - less data on 1 partition means faster work.
They say that few games with no copy protection will work. Yeah, considering originals. What about hard disk adaptations, patches ? As usual they have no clue what all is made.
"Software relying on bugs
These programs use the normal GEMDOS interface to access disk drives but rely on weird patterns or buggy TOS error codes to work properly."
And same idiocy as on page about how hard disks work on Atari (first post in this thread).
Buggy TOS error codes - huh ! They are not buggy. May be different than some later widely used ones - it is really so stoooopid to expect from SW done 40 years ago to be by some later standards .
"Software doing BIOS access
These programs access low level disks using BIOS or XBIOS interfaces.
Programs usually working like this:
Most disk utilities
Maybe some very weirdly programmed games
"
It is not weird to use (X)BIOS call to determine is it running from floppy or hard disk. I saw it many times, and is usually by games with hard disk install option, or declared that work from hard disk.
And they mentioning my early, freeware ACSI driver from 2008. I did lot of it from then.
What about extra functions like Virtual Floppy, automatic Desktop drive icons creation ? By them, it is also bug of TOS that only icon for C is created ... Is it bug that TOS is in limited size ROM ?
Lot of it is done with compromises because HW prices were pretty much higher then.
And really, why such huge disrespect toward Atari ST designers, OS programmers ? Sure, there were some smaller errors, maybe few bugs which show in rare cases. Just one example: it crashes when in drive Window in Desktop some file is of size 10 MB or more (TOS 1.xx) . Well, I did not know about it when I used my Atari at 1992 with 40-160 MB hard disks, simply because were no so large files. I saw it first time somewhere at 2008, when used Steem with it's hard disk system . And. btw I fixed problem in my iTOS .
#46
FAQ / Mass storage (hard disk, now r...
Last post by Petari - 09-07-2025, 10:04:13 I saw really lot of pages, threads about it, and can say only that most of it is far from good and useful. Errors, shallowness and often in some commercial purpose.
Now we have diverse SD card adapters, and probably most sold is ACSI2STM - in diverse variants. It changed since first releases, and now pushes so called GEMdrive mode .
Let see what is on Github about : How hard disks work on the Atari ST
Quote: "Remember that using ACSI drivers is discouraged, you should probably use GemDrive unless you have very specific needs or want an authentic user experience (read: having a hard time struggling against old buggy software)."
This is so idiotic, likely just in interest to force using GemDrive (so buy ACSI2STM and not some other adapter) . Old SW is not buggy at all. Sure, there are some bugs in some, but generally most of it is pretty decent and well tested. Unless thinking that it is bug that old SW does not support some new hard disk filesystems and like :-) Sure, it should support LFN, FAT32, 2 GB partitions (in era when usual hard disk sizes were about 100 MB) ...
Then there writes that it (ACSI port) has no real name - hahaha .
"Mega STE internal hard drive
Some models have internal hard drives, however it seems that only the Mega STE has an internal ACSI drive, sharing the DMA port. By default it is set on the device id 0, but this can be changed by internal DIP switches."
Stacy has it too. And it is not ACSI drive, it is SCSI drive + ACSI-SCSI adapter. Why people with so low Atari ST experience writes about this things at all ? Complete bad approach - but hey, they are sooo smart, so know it better than those who used such machines
AHDI driver is not full of bugs. And limitations are actually in TOS self. You can read about it on my site: Atari ST family and mass storage
TOS limitations can be overridden in different ways. Surely most useful and easy to implement is TOS/DOS compatible partitioning and hard disk driver. It does not need any HW changes, just SW - partitioner and hard disk driver - easy to install. And can do it even without floppy or Gotek.
The real question here is : with what SW most of nowadays Atari ST family users use them ? I'm pretty sure that it is gaming - playing good old games in first place. As lot of people plays even older, 8-bit games.
Now even can buy new version of Atari 2600 (with cartridge port for games on ROM cartridges) .
Sure, there is lot of quality productivity SW, but using them now, when we have several thousands time faster computers and much more advanced SW ? Now simple Internet browsing needs min 2-4 GB RAM .
So, my activity is about making good old games working from modern storage - what is now really cheap considering capacity. But making SW written for floppy run, with copy protections in looot of ways to work from mass storage (now SD cards, CF cards) is pretty hard. Even if game has hard disk install option (program what does it) it may not work good - some have install only to subdir in root of C: - not good for thousands of games on mass storage. So, it needs corrections too. Plus, and I saw many such cases - there is low level hard disk access in code - what means not access to some files, DIRs, by it's name, but to physical sectors . And that's what will fails with GemDrive . I wrote about it to man behind GemDrive, and just got reply in insulting style - he is smart, I'm nobody. Sure, after doing over 2500 games I know nothing ! This is real problem in 'Atari community' - some just push own ideas, limited knowledge, and do not listen to other's experience, knowledge (not so limited).
All in all, please do not believe everything what can see online. I did not say anything new, of course.
For running good old SW, games we don't need new TOS (like EmuTOS), new hard disk systems. Best way is compatible TOS version - so regular TOS 1.00 - 4.04 or my improved TOS versions, which are made to be compatible as much is possible with original TOS versions. And of course hard disk driver what is good with old SW and TOS/DOS compatible partitions. Latest mean easy data transfers with modern computers - Windows, Linux, MacOS . And lot of things can be done on them way faster than with old Ataris .
Now we have diverse SD card adapters, and probably most sold is ACSI2STM - in diverse variants. It changed since first releases, and now pushes so called GEMdrive mode .
Let see what is on Github about : How hard disks work on the Atari ST
Quote: "Remember that using ACSI drivers is discouraged, you should probably use GemDrive unless you have very specific needs or want an authentic user experience (read: having a hard time struggling against old buggy software)."
This is so idiotic, likely just in interest to force using GemDrive (so buy ACSI2STM and not some other adapter) . Old SW is not buggy at all. Sure, there are some bugs in some, but generally most of it is pretty decent and well tested. Unless thinking that it is bug that old SW does not support some new hard disk filesystems and like :-) Sure, it should support LFN, FAT32, 2 GB partitions (in era when usual hard disk sizes were about 100 MB) ...
Then there writes that it (ACSI port) has no real name - hahaha .
"Mega STE internal hard drive
Some models have internal hard drives, however it seems that only the Mega STE has an internal ACSI drive, sharing the DMA port. By default it is set on the device id 0, but this can be changed by internal DIP switches."
Stacy has it too. And it is not ACSI drive, it is SCSI drive + ACSI-SCSI adapter. Why people with so low Atari ST experience writes about this things at all ? Complete bad approach - but hey, they are sooo smart, so know it better than those who used such machines
AHDI driver is not full of bugs. And limitations are actually in TOS self. You can read about it on my site: Atari ST family and mass storage
TOS limitations can be overridden in different ways. Surely most useful and easy to implement is TOS/DOS compatible partitioning and hard disk driver. It does not need any HW changes, just SW - partitioner and hard disk driver - easy to install. And can do it even without floppy or Gotek.
The real question here is : with what SW most of nowadays Atari ST family users use them ? I'm pretty sure that it is gaming - playing good old games in first place. As lot of people plays even older, 8-bit games.
Now even can buy new version of Atari 2600 (with cartridge port for games on ROM cartridges) .
Sure, there is lot of quality productivity SW, but using them now, when we have several thousands time faster computers and much more advanced SW ? Now simple Internet browsing needs min 2-4 GB RAM .
So, my activity is about making good old games working from modern storage - what is now really cheap considering capacity. But making SW written for floppy run, with copy protections in looot of ways to work from mass storage (now SD cards, CF cards) is pretty hard. Even if game has hard disk install option (program what does it) it may not work good - some have install only to subdir in root of C: - not good for thousands of games on mass storage. So, it needs corrections too. Plus, and I saw many such cases - there is low level hard disk access in code - what means not access to some files, DIRs, by it's name, but to physical sectors . And that's what will fails with GemDrive . I wrote about it to man behind GemDrive, and just got reply in insulting style - he is smart, I'm nobody. Sure, after doing over 2500 games I know nothing ! This is real problem in 'Atari community' - some just push own ideas, limited knowledge, and do not listen to other's experience, knowledge (not so limited).
All in all, please do not believe everything what can see online. I did not say anything new, of course.
For running good old SW, games we don't need new TOS (like EmuTOS), new hard disk systems. Best way is compatible TOS version - so regular TOS 1.00 - 4.04 or my improved TOS versions, which are made to be compatible as much is possible with original TOS versions. And of course hard disk driver what is good with old SW and TOS/DOS compatible partitions. Latest mean easy data transfers with modern computers - Windows, Linux, MacOS . And lot of things can be done on them way faster than with old Ataris .
#47
General chat / DOOM on the ST!
Last post by Ronald J. Hall - 02-07-2025, 17:41:26"Power Of Vintage" has posted an interesting
video on running DOOM on Atari computers.
STDoom running on 8 different Atari systems
https://tinyurl.com/mcmm384z
video on running DOOM on Atari computers.
STDoom running on 8 different Atari systems
https://tinyurl.com/mcmm384z
#48
Software / Re: New game adaptations
Last post by Ronald J. Hall - 16-06-2025, 16:56:37Thanks Peter. I've always been intrigued by "Advanced Destroyer Simulator".
Another one of those titles I've not managed to get around to playing yet
but it's on my list.
Another one of those titles I've not managed to get around to playing yet
but it's on my list.
#49
Software / Re: New game adaptations
Last post by Petari - 16-06-2025, 12:25:29Found more interesting/quality games. So far done these:
2 in 1 Bar 2 games: The Pools Predictor and Turf-Form
5 Intelligent Strategy Games
ABZoo
Advanced Destroyer Simulator
Superstars Ice Hockey aka American Ice Hockey
Arena
Art de la Guerre
Atari ST Tour - includes Ranarama
Brian Cloughs Football Fortunes
Count and Add
Deep Space Operation
Demenage Man
Ferme les Cris des Animaux
Football Director 2
Francais CE1
Gambler
Geometrie Debutant
Grey Seas Grey Skies
Hlava Kasandry
J'Apprends I Heure
Killer Chess
Las Vegas
Magazin, Das
Objectif Europe
Petits Coloriages Malins
Power Cut
Premier Manager
Soccer King
2 in 1 Bar 2 games: The Pools Predictor and Turf-Form
5 Intelligent Strategy Games
ABZoo
Advanced Destroyer Simulator
Superstars Ice Hockey aka American Ice Hockey
Arena
Art de la Guerre
Atari ST Tour - includes Ranarama
Brian Cloughs Football Fortunes
Count and Add
Deep Space Operation
Demenage Man
Ferme les Cris des Animaux
Football Director 2
Francais CE1
Gambler
Geometrie Debutant
Grey Seas Grey Skies
Hlava Kasandry
J'Apprends I Heure
Killer Chess
Las Vegas
Magazin, Das
Objectif Europe
Petits Coloriages Malins
Power Cut
Premier Manager
Soccer King
#50
FAQ / Which e-mail service/provider ...
Last post by Petari - 15-06-2025, 09:22:16 Lately more and more problems with gmail - when sending attachment with image files - like floppy image, TOS image , shorter hard disk/SD card image files.
Please use some other e-mail provider/service than gmail. Especially if
ordering some SW/driver, image files. Because it rejects whole e-mails just because file extensions
(and there is some 40 listed by them). And does it without any check of file content.
Decent e-mail providers check content of attachments, mostly for viruses and other harmful content.
What of course needs little more code and CPU load. But all it is
not big deal with today computer power. I recommend Proton Mail
https://go.getproton.me/aff_c?offer_id=7&aff_id=11851
It is free and safe.
Additionally gmail wrote in e-mail rejection reply that my site has bad reputation . Huh !
Surely has it by morons mostly active at atariage - who wrote diverse nonsenses about my SW causing damages like hard disk content lose, even damaging some HW - like UltraSatan and similar.
What times are this ? Big Internet companies just accept such claims without any proof ? Welcome back Stalin era !
Rule number one: before declare someone as guilty listen to both sides. Think about what you heard. Use your knowledge about computers in cases like this - or if have no it - just don't judge.
Surely, most of those false accusations - it they can be called so at all, as they were really not serious. Instead it big words, mentioning big damages - most popular is losing hard disk content, without 'any chance to recover' . That happens when some can not admit that some can do it better than them.
And what to expect from cracking crews who write all time in style: "we are the best ..." .
C.J. even wrote at great atariage about I stole his ULS code 'byte by byte' - well, so his code is that was caused damages ! Arrest him !
Seriously: ULS has no any support for games using TOS functions, is only for games not using TOS, so not floppy file functions of TOS . And majority of Atari ST games using TOS calls (like 65%).
If I would not developed support for them - like TOS 1.04 in RAM, special launchers - and all it needed lot of time. I would be not able to do over 2600 game's hard disk (now rather SD card) adaptations. Yeah, adapts (in short) - this are not cracks, patches. Sure, there may be copy protection 'crack' by need, some changes in code, and they may be simple one - like correction only few bytes, or may be replacement of whole code parts. Then there are fixes to make it work under all TOS versions.
Lot of time is needed, especially now when dealing with less known games to find proper floppy images of them. I needed to make some fixes because of errors in images. Or combine from multiple sources.
Back to e-mail providers: if you can recommend some good one, free, and without bad filters, good for attachment sending and receiving, please write here.
Please use some other e-mail provider/service than gmail. Especially if
ordering some SW/driver, image files. Because it rejects whole e-mails just because file extensions
(and there is some 40 listed by them). And does it without any check of file content.
Decent e-mail providers check content of attachments, mostly for viruses and other harmful content.
What of course needs little more code and CPU load. But all it is
not big deal with today computer power. I recommend Proton Mail
https://go.getproton.me/aff_c?offer_id=7&aff_id=11851
It is free and safe.
Additionally gmail wrote in e-mail rejection reply that my site has bad reputation . Huh !
Surely has it by morons mostly active at atariage - who wrote diverse nonsenses about my SW causing damages like hard disk content lose, even damaging some HW - like UltraSatan and similar.
What times are this ? Big Internet companies just accept such claims without any proof ? Welcome back Stalin era !
Rule number one: before declare someone as guilty listen to both sides. Think about what you heard. Use your knowledge about computers in cases like this - or if have no it - just don't judge.
Surely, most of those false accusations - it they can be called so at all, as they were really not serious. Instead it big words, mentioning big damages - most popular is losing hard disk content, without 'any chance to recover' . That happens when some can not admit that some can do it better than them.
And what to expect from cracking crews who write all time in style: "we are the best ..." .
C.J. even wrote at great atariage about I stole his ULS code 'byte by byte' - well, so his code is that was caused damages ! Arrest him !
Seriously: ULS has no any support for games using TOS functions, is only for games not using TOS, so not floppy file functions of TOS . And majority of Atari ST games using TOS calls (like 65%).
If I would not developed support for them - like TOS 1.04 in RAM, special launchers - and all it needed lot of time. I would be not able to do over 2600 game's hard disk (now rather SD card) adaptations. Yeah, adapts (in short) - this are not cracks, patches. Sure, there may be copy protection 'crack' by need, some changes in code, and they may be simple one - like correction only few bytes, or may be replacement of whole code parts. Then there are fixes to make it work under all TOS versions.
Lot of time is needed, especially now when dealing with less known games to find proper floppy images of them. I needed to make some fixes because of errors in images. Or combine from multiple sources.
Back to e-mail providers: if you can recommend some good one, free, and without bad filters, good for attachment sending and receiving, please write here.