New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LiteDOS in dir2atr #2
Comments
Quite tricky, as LiteDOS isn't really DOS2.x compatible. It doesn't use a standard DOS.SYS file but stores the DOS data directly in sectors 4-16 (4-10 on DD disks). Also it seems to use lowercase letters for it's "LiteDUP.SYS" filename. The most important issue though is that the sector allocation scheme is completely different to DOS2.x/MyDOS so compatibility to DOS2.x is limited to read-only. I had a quick go at hacking support for "extended boot data sectors" into dir2atr and pushed an experimental test branch here: https://github.com/HiassofT/AtariSIO/tree/extended-bootsectors - with the 1920 boot data bytes extracted from the LiteDOS 3.06 atr I could create a bootable ATR but it's usability is quite limited (as writing won't work). So I'm not sure if I'll include that change in the master branch, but feel free to do some tests with it. |
Thanks for the hack, Hias. I agree that this is somewhat useless w/o wrote support, apart for demo disks for example - but I could use your MyPicoDos autorun mode instead then ;) |
About bootsectors: To be precise, LiteDOS has 1 bootsector. |
What about implementing LiteDOS into dir2atr?
I've managed to extract it's bootsector(s) and to implant them by using dir2atr's -b parameter. The created image boots showing LiteDOS's message but machine crashes afterwards.
The text was updated successfully, but these errors were encountered: