- Welcome to 8BitChip Forum.
Recent posts
#1
News / Re: Another shallow YT video a...
Last post by Ronald J. Hall - Today at 04:21:54Sorry about that Peter. I'm unsure why people don't do more
research and testing before posting things.
Too many people seem to be bent on getting "clicks" and "views"
these days...
research and testing before posting things.
Too many people seem to be bent on getting "clicks" and "views"
these days...
#2
News / Another shallow YT video about...
Last post by Petari - 07-08-2025, 10:33:21YT video by 'expert'
He talks that my driver is good only for TOS 1.04 and above. I'm really full of shallow 'testers', who making claims without any serious testing, looking details, and maybe reading what writes on site of programmer ...
And my comments just go deleted - sure, that's the simplest way to solve problem. Because for some that's the biggest problem - getting critic, corrections . No wonder where this 'humankind' sunk latest years.
Just something really elementary: they should read instructions supplied with partitioner/driver SW before using, and especially before doing YT video and commenting SW .
He talks that my driver is good only for TOS 1.04 and above. I'm really full of shallow 'testers', who making claims without any serious testing, looking details, and maybe reading what writes on site of programmer ...
And my comments just go deleted - sure, that's the simplest way to solve problem. Because for some that's the biggest problem - getting critic, corrections . No wonder where this 'humankind' sunk latest years.
Just something really elementary: they should read instructions supplied with partitioner/driver SW before using, and especially before doing YT video and commenting SW .
#3
News / Re: Interesting YT video about...
Last post by Petari - 04-08-2025, 08:26:07 I added new comment regarding 'opinions' about my iTOS in video.
Will quote it here - as it may be deleted, together with my right to post there :-)
"As here in this video is talk about my improved TOS, at about 10m 30s I need to say some things. It is not TOS 2.16 patch. You can not patch something what exists not. I used 2.16 because it is combination of 1.62 (GEMDOS part) and 2.06 (AES, Desktop part) . And 1.62 part is modified a lot. What needed proper disassembly of it - takes weeks of work, then correcting FAT16 filesystem code - all in ASM, as no C sources available. And not to mention adding lot of new things - is adding something new 'patch' - I don't think so. Then error was mentioned - 'but internal driver does not like other drivers' . I must say that this is just illogical - driver does not like other drivers -- huh. It is not driver what deals with other driver. It is in TOS FAT16 filesystem. As is stated goal was to keep maximal possible compatibility with regular TOS versions (because it is good for old SW) . So, if you simply install some other driver integrated will not be active (driver install will delete flags which activate integrated driver). Plus, it is not activated by default, user needs to click on 'Activ. int. driver', and there is small program to deactivate it any time. And because this is with pure DOS type partitions other drivers will not work - here mean usual drivers for TOS/AHDI kind partitions. Because iTOS works best with pure DOS type partitions - so no need for extra disk buffers, so there is 64 KB more free RAM, even with 1024 MB partitions. More details on my site. For those who care. And I need to say that I did not understand well in many case what was said, what must be purely my error. "
And, all this silliness with this video and writes on GitHub made me think about my older idea (what I exposed to Diego in e-mail some months ago) I will do some special testing version what will work without ACSI-SD adapter firmware modification. So, it will be 1-2 partitions of 32 MB size on SD card, where user can copy Atari SW runnable from hard disk. Why 32 MB ? It is enough for practically all Atari ST SW . And with that size no need for extra buffers, so 64 KB more free space, and is TOS/DOS compatible (as interested people can see on my site) . That will work even with Satandisk (but need non HxC SD card) .
It needs some PC or Mac to copy files on those partitions. When Atari session is over can attach it to PC/Mac and save somewhere changes, game state saves, so can use them even after deleting from 32 MB partitions. Yes, it needs little extra work, but I doubt that there is more than few % of users who have no modern computer with USB ports.
When I finish it and is tested I will propose to add it to firmware of SD4ST - surely fastest ACSI-SD adapter, and I expect better communication with it's designer. Then can use larger capacity SD card with FAT32, NTSC or some other new partition types. User needs to create/copy there some 32-64 MB long empty file, what will be actually image of Atari 'hard disk' where can copy files/DIRs for next session. And that can do with Atari, with firmware help (concept based on 'Hard disk' in Steem (at 2005) ) - need to select DIR from which to copy files to TOS parition(s) or just select 'Use existing' if want to continue with what is on TOS partitions since last session . When Atari session is over user will be able to save changes with special Windows program for that, and may be some other ways for it. So, this will have advantage of so called GemDrive and better SW compatibility of classic/regular TOS hard disk driver based system (low level access works too). And this will work faster too because dealing with small partitions.
Will quote it here - as it may be deleted, together with my right to post there :-)
"As here in this video is talk about my improved TOS, at about 10m 30s I need to say some things. It is not TOS 2.16 patch. You can not patch something what exists not. I used 2.16 because it is combination of 1.62 (GEMDOS part) and 2.06 (AES, Desktop part) . And 1.62 part is modified a lot. What needed proper disassembly of it - takes weeks of work, then correcting FAT16 filesystem code - all in ASM, as no C sources available. And not to mention adding lot of new things - is adding something new 'patch' - I don't think so. Then error was mentioned - 'but internal driver does not like other drivers' . I must say that this is just illogical - driver does not like other drivers -- huh. It is not driver what deals with other driver. It is in TOS FAT16 filesystem. As is stated goal was to keep maximal possible compatibility with regular TOS versions (because it is good for old SW) . So, if you simply install some other driver integrated will not be active (driver install will delete flags which activate integrated driver). Plus, it is not activated by default, user needs to click on 'Activ. int. driver', and there is small program to deactivate it any time. And because this is with pure DOS type partitions other drivers will not work - here mean usual drivers for TOS/AHDI kind partitions. Because iTOS works best with pure DOS type partitions - so no need for extra disk buffers, so there is 64 KB more free RAM, even with 1024 MB partitions. More details on my site. For those who care. And I need to say that I did not understand well in many case what was said, what must be purely my error. "
And, all this silliness with this video and writes on GitHub made me think about my older idea (what I exposed to Diego in e-mail some months ago) I will do some special testing version what will work without ACSI-SD adapter firmware modification. So, it will be 1-2 partitions of 32 MB size on SD card, where user can copy Atari SW runnable from hard disk. Why 32 MB ? It is enough for practically all Atari ST SW . And with that size no need for extra buffers, so 64 KB more free space, and is TOS/DOS compatible (as interested people can see on my site) . That will work even with Satandisk (but need non HxC SD card) .
It needs some PC or Mac to copy files on those partitions. When Atari session is over can attach it to PC/Mac and save somewhere changes, game state saves, so can use them even after deleting from 32 MB partitions. Yes, it needs little extra work, but I doubt that there is more than few % of users who have no modern computer with USB ports.
When I finish it and is tested I will propose to add it to firmware of SD4ST - surely fastest ACSI-SD adapter, and I expect better communication with it's designer. Then can use larger capacity SD card with FAT32, NTSC or some other new partition types. User needs to create/copy there some 32-64 MB long empty file, what will be actually image of Atari 'hard disk' where can copy files/DIRs for next session. And that can do with Atari, with firmware help (concept based on 'Hard disk' in Steem (at 2005) ) - need to select DIR from which to copy files to TOS parition(s) or just select 'Use existing' if want to continue with what is on TOS partitions since last session . When Atari session is over user will be able to save changes with special Windows program for that, and may be some other ways for it. So, this will have advantage of so called GemDrive and better SW compatibility of classic/regular TOS hard disk driver based system (low level access works too). And this will work faster too because dealing with small partitions.
#4
Software / Re: Future Game Adaptions Sugg...
Last post by Petari - 04-08-2025, 06:36:13Quote from: diamondspringwater on 03-08-2025, 17:54:38Can I suggest Suspicious cargo it looks interesting.
https://www.atarimania.com/game-atari-st-suspicious-cargo_11479.html
It is already done. I sent you e-mail with some details, explanations, and how to get latest image for SD card .
#5
FAQ / Re: Using proper terminology o...
Last post by Ronald J. Hall - 03-08-2025, 18:11:17I agree that there are a lot of confusing terms out there.
Confuses me anyway (and yeah, I know - that don't take
much)...
Confuses me anyway (and yeah, I know - that don't take
much)...
#6
News / Re: Interesting YT video about...
Last post by Ronald J. Hall - 03-08-2025, 18:09:22I don't understand the "delete" thing either.
I mean, if you disagree with something, fine - disagree,
in a civil manner and have a constructive discussion from
it.
Hard to have any kind of discussion when everything is just
outright deleted.
I mean, if you disagree with something, fine - disagree,
in a civil manner and have a constructive discussion from
it.
Hard to have any kind of discussion when everything is just
outright deleted.
#7
Software / Re: Future Game Adaptions Sugg...
Last post by diamondspringwater - 03-08-2025, 17:54:38Can I suggest Suspicious cargo it looks interesting.
https://www.atarimania.com/game-atari-st-suspicious-cargo_11479.html
https://www.atarimania.com/game-atari-st-suspicious-cargo_11479.html
#8
News / Re: Interesting YT video about...
Last post by Petari - 03-08-2025, 14:57:38And as was to expect - deleted. Some just can not stand that they are not in right. And not able to give real answers, so let's delete it. This will make this World better for sure :-(
#9
FAQ / Using proper terminology or ju...
Last post by Petari - 03-08-2025, 14:14:56 Some people claims that in this retro computing hobby we can name SW, HW projects, solutions as we like it, not caring about used words, terms meaning, that name may be misleading ...
Then, lot of retro computer people has problems with terms, terminology . Would it be better if those who work development, on some informative WEB pages would take more care about terminology.
And more: would it be better if those making mistakes and being corrected, would say 'tnanx' and learn something instead getting insulted, reacting harshly, in style 'how you dare to say I'm wrong' . Well, that's even bigger mistake acting like can not make some error/mistake .
I have pretty much experience with such: in 1983 in my small city where I leaved then home computer club was formed - mostly C64, Sinclair Spectrum users/owners. And beginners in it. On first meeting someone mixed terms byte and bit, and when I corrected it he came with 'how you dare' - and I was not surprised as I knew him. Similar cases, just with not so basic terms happened at Atari forums in 21-st Century . And reactions were really miserable in many cases. Moderators/admins did not react properly in many cases.
I guess quantity of posts is more important than quality for them.
Let's see some 'product', SW, HW names:
'HD Driver' (Seimet) - it is just shortage of general term 'hard disk driver' . That self is proper as name, but it should be something unique, not abbrev.
'GemDrive' - should mean something like hard disk driver under GEM . What is GEM ? graphical environment manager. Here some little confusion is done by Atari, I think - better would be to call disk related part of TOS TOSDOS instead GEMDOS - for instance as there is lot of SW not using GEM at all. So, TOSdrive sounds for me better.
'Sidecartridge' - yeah, cartridge goes at side of Atari ST :-) What about naming by what it does ?
Oh yeah - TOS emulator - huh . It is not it at all. See other thread here for more ...
'ULS' - universal loading system - name would be OK, if it would be really universal. Truth is that it is good only for SW what does floppy access with own code, and not TOS functions, and not only disk access - SW what does not using TOS at all after it is started . And percentage of TOS using games is some 65% min.
But what to expect from people who claim that they are best in it. They did not mention that whole concept is takes from Amiga WHDLoad system. Sure, why do it ? I did not see mentioning in Hatari DOCs that their GemDrive concept is same is 'Hard disk' in Steem (2005) .
Then, when we are at games: it was usual that games sold in past as pirate copies were called 'cracks' - as it was needed to 'crack' copy protection. Later came era of hard disks/Flash cards, so some called it 'patches' . What term 'patch' means - fixing some part, doing some correction so it can work in different environment (HW) . Well, that's pretty much OK for ULS . But what about games calling TOS functions ?
It needed much more - among others some TOS v. in RAM, where are some changes for better works, easier making games working in new conditions. And there may be many of it. So, I call my releases adaptations or adapts - and that just includes all needed changes, add-ons ... Then, some call it 'conversions' - very bad and not respectful - it is not conversion, and of course no SW what can do it. And will be not. All it is lot of 'manual' work and biggest help for it is some better Atari ST emulator with trace and debugger functions - yeah Steem Debugger . It makes all searching in machine code way easier, as one of main tasks is to find parts of code responsible for disk access, for input read (keyboard, mouse, joystick), copy protection too - and even if using some crack (what I do only if no other source) may need to remove all remains of floppy access in it - as we want now that it work on machines without floppy drive (or Gotek and like) . And of course there are many special cases, strange programmer's solutions, code ...
Calling it just patch, crack, conversion just does not cover all needed and involved .
But some don't care - 'I will do it as I want, it's my right' - Yeah, it is it. And my right is to openly say that it is just bad, disrespectful, sign of not reading available pages about it, not taking any time to think little about , or maybe just contact author about it ...
Then, lot of retro computer people has problems with terms, terminology . Would it be better if those who work development, on some informative WEB pages would take more care about terminology.
And more: would it be better if those making mistakes and being corrected, would say 'tnanx' and learn something instead getting insulted, reacting harshly, in style 'how you dare to say I'm wrong' . Well, that's even bigger mistake acting like can not make some error/mistake .
I have pretty much experience with such: in 1983 in my small city where I leaved then home computer club was formed - mostly C64, Sinclair Spectrum users/owners. And beginners in it. On first meeting someone mixed terms byte and bit, and when I corrected it he came with 'how you dare' - and I was not surprised as I knew him. Similar cases, just with not so basic terms happened at Atari forums in 21-st Century . And reactions were really miserable in many cases. Moderators/admins did not react properly in many cases.
I guess quantity of posts is more important than quality for them.
Let's see some 'product', SW, HW names:
'HD Driver' (Seimet) - it is just shortage of general term 'hard disk driver' . That self is proper as name, but it should be something unique, not abbrev.
'GemDrive' - should mean something like hard disk driver under GEM . What is GEM ? graphical environment manager. Here some little confusion is done by Atari, I think - better would be to call disk related part of TOS TOSDOS instead GEMDOS - for instance as there is lot of SW not using GEM at all. So, TOSdrive sounds for me better.
'Sidecartridge' - yeah, cartridge goes at side of Atari ST :-) What about naming by what it does ?
Oh yeah - TOS emulator - huh . It is not it at all. See other thread here for more ...
'ULS' - universal loading system - name would be OK, if it would be really universal. Truth is that it is good only for SW what does floppy access with own code, and not TOS functions, and not only disk access - SW what does not using TOS at all after it is started . And percentage of TOS using games is some 65% min.
But what to expect from people who claim that they are best in it. They did not mention that whole concept is takes from Amiga WHDLoad system. Sure, why do it ? I did not see mentioning in Hatari DOCs that their GemDrive concept is same is 'Hard disk' in Steem (2005) .
Then, when we are at games: it was usual that games sold in past as pirate copies were called 'cracks' - as it was needed to 'crack' copy protection. Later came era of hard disks/Flash cards, so some called it 'patches' . What term 'patch' means - fixing some part, doing some correction so it can work in different environment (HW) . Well, that's pretty much OK for ULS . But what about games calling TOS functions ?
It needed much more - among others some TOS v. in RAM, where are some changes for better works, easier making games working in new conditions. And there may be many of it. So, I call my releases adaptations or adapts - and that just includes all needed changes, add-ons ... Then, some call it 'conversions' - very bad and not respectful - it is not conversion, and of course no SW what can do it. And will be not. All it is lot of 'manual' work and biggest help for it is some better Atari ST emulator with trace and debugger functions - yeah Steem Debugger . It makes all searching in machine code way easier, as one of main tasks is to find parts of code responsible for disk access, for input read (keyboard, mouse, joystick), copy protection too - and even if using some crack (what I do only if no other source) may need to remove all remains of floppy access in it - as we want now that it work on machines without floppy drive (or Gotek and like) . And of course there are many special cases, strange programmer's solutions, code ...
Calling it just patch, crack, conversion just does not cover all needed and involved .
But some don't care - 'I will do it as I want, it's my right' - Yeah, it is it. And my right is to openly say that it is just bad, disrespectful, sign of not reading available pages about it, not taking any time to think little about , or maybe just contact author about it ...
#10
News / Interesting YT video about "Si...
Last post by Petari - 02-08-2025, 10:23:52Dima Sobolev recommended it to me. I added there comment, but it will be deleted soon most likely.YT video
So, here is my comment:
"Lot of wrong terminology. It is not TOS emulator. There is TOS ROM switch (what I made long time ago - 1992 in my ST and also in my Sinclair Spectrum (of course it is OS ROM switch there) . GemDrive is something done for first time in Steem Atari ST(E) emulator - 2005, called there just 'Hard disk' - it is actually kind of hook/replacement of TOS-es FAT16 filesystem functions - so will access, deal with files on host computers DIR (selected by user) - what will appear as Atari ST logical drive (partition) . But it is not full disk access like it is with usual harddisk drivers and regular TOS usage, No low level disk access, and some SW using that.
And most funny: my integrated driver in iTOS 'does not like other drivers' - haha - it does not need other drivers, as it does basically same thing, so why would start other driver when integrated one is activated ? Plus, if you attach some hard disk/SD card with 'other' driver integrated one will not activate - shame on you 'other drivers' - you don't like my integrated driver ! ??
Well, sarcasm aside: my iTOS (all versions) allow user selection of integrated driver - will work only with DOS FAT16 partitioned media or autoboot driver on media, and usual AHDI type partitioning too, for compatibility. Autoboot can be with DOS type FAT16 - what format integrated partitioner produces. It has some advantage over TOS (AHDI) type FAT16 - for instance much less RAM needed for disk buffers (no large logical sectors).
Visit my site, e-mail me for more details about my SW, about TOS generally. "
So, here is my comment:
"Lot of wrong terminology. It is not TOS emulator. There is TOS ROM switch (what I made long time ago - 1992 in my ST and also in my Sinclair Spectrum (of course it is OS ROM switch there) . GemDrive is something done for first time in Steem Atari ST(E) emulator - 2005, called there just 'Hard disk' - it is actually kind of hook/replacement of TOS-es FAT16 filesystem functions - so will access, deal with files on host computers DIR (selected by user) - what will appear as Atari ST logical drive (partition) . But it is not full disk access like it is with usual harddisk drivers and regular TOS usage, No low level disk access, and some SW using that.
And most funny: my integrated driver in iTOS 'does not like other drivers' - haha - it does not need other drivers, as it does basically same thing, so why would start other driver when integrated one is activated ? Plus, if you attach some hard disk/SD card with 'other' driver integrated one will not activate - shame on you 'other drivers' - you don't like my integrated driver ! ??
Well, sarcasm aside: my iTOS (all versions) allow user selection of integrated driver - will work only with DOS FAT16 partitioned media or autoboot driver on media, and usual AHDI type partitioning too, for compatibility. Autoboot can be with DOS type FAT16 - what format integrated partitioner produces. It has some advantage over TOS (AHDI) type FAT16 - for instance much less RAM needed for disk buffers (no large logical sectors).
Visit my site, e-mail me for more details about my SW, about TOS generally. "