Interesting YT video about "Sidecartridge TOS emulator"

[Petari]

Dima 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.  "
 

[Petari]

And 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 :-(

[Ronald J. Hall]

I 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. 

[Petari]

 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.