mr-atari Posted July 8, 2019 Share Posted July 8, 2019 Just a small note here on AtariAge. Version 2.05 is now available for download. Some bugs fixed in DUP (Rename and Dir) and LiteINIT (unusable sectors 4-15 on MD). Thanks for the feedback. =Happy birthday to LiteDOS= SMALL: uses only 2k RAM, 4k more free memory, even 8k more when using Turbo Basic ! EFFICIENT: 1016 FreeSectors on a MD disk or 700 FreeSectors on a SD disk ! FAST: boots in 2-3 seconds. SIMPLE: load/copy files wasn't this easy. COMPATIBLE: reads Atari DOS 2.0 2.5 MyDOS and other compatible disks. The file-format of a LiteDOS-disk is readable by DOS 2.0/2.5/MyDOS and clones. http://www.mr-atari.com/Mr.Atari/LiteDOS/ 11 3 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 8, 2019 Share Posted July 8, 2019 some files not in zip... no read me or manual no tinyterm no esp_oftb Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 8, 2019 Author Share Posted July 8, 2019 Thanks, Fixed. Manual is on the LiteDOS-page itself. 1 Quote Link to comment Share on other sites More sharing options...
+Philsan Posted July 8, 2019 Share Posted July 8, 2019 It would be nice if Altirra Disk Explorer would work with LiteDOS disk images. Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 9, 2019 Author Share Posted July 9, 2019 Yes, I asked but got a denial, for now. For example, Atarimax APE let me see the files, very handy. It's basically a standard DOS file system, where the DOS-ID has a negative value to mark it as "LiteDOS" formatted. Reading files from it is also standard DOS practice. The big difference is saving, I use clusters and the bitmap reflects clusters and not single sectors. And ridiculous small in it's RAM usage ? Grtz, Sijmen. 1 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 9, 2019 Share Posted July 9, 2019 That sort of hybrid thinking is what makes Atari programmers some of the best out there! Quote Link to comment Share on other sites More sharing options...
+Philsan Posted July 9, 2019 Share Posted July 9, 2019 Sijmen, you could make an application like MakeATR. In fact I need to be able to quickly add, remove and rename files and format disk images with Windows. Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 10, 2019 Author Share Posted July 10, 2019 Perhaps the current owner of "MakeATR" can do/add this to his software. Don't recall anymore if I asked him already, sorry. I stick to 6502 programming.... Perhaps Phareon will reconsider adding LiteDOS this to the disk explorer of Altirra. Grtz, Sijmen. 1 Quote Link to comment Share on other sites More sharing options...
AtariGeezer Posted July 11, 2019 Share Posted July 11, 2019 Last night I started adding support for LiteDOS to ATR Tools 5 Quote Link to comment Share on other sites More sharing options...
+Philsan Posted July 11, 2019 Share Posted July 11, 2019 4 hours ago, AtariGeezer said: Last night I started adding support for LiteDOS to ATR Tools Didn't think about your very nice ATR Tools Jay, thanks! Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 11, 2019 Author Share Posted July 11, 2019 6 hours ago, AtariGeezer said: Last night I started adding support for LiteDOS to ATR Tools Thanks ! Quote Link to comment Share on other sites More sharing options...
AtariGeezer Posted July 12, 2019 Share Posted July 12, 2019 @ Sijmen, could you provide some ATR's of the various sizes that LiteInit creates? I think I found a bug when choosing the [O]ther option, when I specify the Sector Count as 16384, the Total Sectors and Free Sectors saved in the VTOC reflect a Total Sector Count of 65535... Thanks, Jay Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 12, 2019 Author Share Posted July 12, 2019 I just tried the LiteINIT 2.05 And created all the formats from SD up to 720k (real disks) and Others (partitions) from 2048 to 65536 sectors. Looked at the VTOC-bytes generated at page 4 and all look OK. This is the table I use (code): SIZES .BYTE "SMDX7" ;LETTER .BYTE $2,$3,$2,$5,$B ;SEC-HI .BYTE $D0,$FF,$D0,$A0,$40 ;SEC-LO .BYTE 3,3,7,7,7 ;DEFAULT CLUSTER .BYTE 7,0,15,23,31 ;PERCOM-BLOCK, 0=NONE DSIZE .BYTE "631842" ;PARTITION-SIZES .BYTE 127,63,63,31,15,7 ;DEFAULT CLUSTER 510,504,504,240,120,56 The percom-number is an offset what Percom-block I need to send to the device. Number of sectors for Other sizes, start at $07FF for "2k" and rotated LEFT upto $FFFF for "64k" I attached the "2k" generated VTOC-data. Seems OK to me. Perhaps something I overlook? Can you re-download the V205 from my homepage, perhaps something screwed-up there. Grtz, Sijmen. Quote Link to comment Share on other sites More sharing options...
AtariGeezer Posted July 12, 2019 Share Posted July 12, 2019 (edited) imagerdd.atr Downloaded again and the problem still exists. I'm using Altirra to create a blank 720 sector DD image and formatting with LiteINIT 2.05 with the Other option. When I try formatting a DD, XF or 720k image, I'm still getting the "Bad or No LiteDOS Disk/IO-Error" message. Could you please post ATR's of MD, DD, XF, 720k, 1440 Sector and 16384 Sector images so I can duplicate those correctly Thanks, Jay Edited July 12, 2019 by AtariGeezer Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 12, 2019 Share Posted July 12, 2019 ah, he was using altira emulation... not even sure if you set all the disk stuff to accurate timing etc. if that will work, someone could try though. Quote Link to comment Share on other sites More sharing options...
AtariGeezer Posted July 13, 2019 Share Posted July 13, 2019 (edited) 1 hour ago, _The Doctor__ said: ah, he was using altira emulation... not even sure if you set all the disk stuff to accurate timing etc. if that will work, someone could try though. I do use accurate sector timing... Edited July 13, 2019 by AtariGeezer Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 13, 2019 Share Posted July 13, 2019 (edited) so it's alright on timing but not so much on the mechanics of the physical, logical drive capabilities possibly... did Mr. Atari provide an ATR of each density and mode yet? And do you still have physical hardware to work? Edited July 13, 2019 by _The Doctor__ Quote Link to comment Share on other sites More sharing options...
AtariGeezer Posted July 13, 2019 Share Posted July 13, 2019 At the moment, I don't have a way to transfer an ATR to real hardware since my XP PC died (It has a SD Card reader built-in)... Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted July 13, 2019 Share Posted July 13, 2019 no sio 2 pc? oh my! it is best to get verified clean images from mr atari thought Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 14, 2019 Author Share Posted July 14, 2019 On 7/12/2019 at 10:18 PM, AtariGeezer said: imagerdd.atr 179.64 kB · 1 download Downloaded again and the problem still exists. I'm using Altirra to create a blank 720 sector DD image and formatting with LiteINIT 2.05 with the Other option. When I try formatting a DD, XF or 720k image, I'm still getting the "Bad or No LiteDOS Disk/IO-Error" message. Could you please post ATR's of MD, DD, XF, 720k, 1440 Sector and 16384 Sector images so I can duplicate those correctly Thanks, Jay It still works for me, in Altirra, strange. Your selected drive is enhanced? Thus it accepts percom commands? "Other" only works on partitions, readable sectors must be present. Same check goes for "Update" and let me think, if the disk is unformatted, you won't get the question "new" or "update". You need to select DD, that is the correct way to format a new disk in DD with a percom-compatible drive. But anyway, I will create the images after this message, zip and upload them. Later. ? Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 14, 2019 Author Share Posted July 14, 2019 (edited) Ok, here you are, all possible ATR's created with LiteINIT (14/7 update). You made me find a little typo in sending the incorrect percom-block for 720k disks. All other formats were 100% So I updated my homepage with the new zip-file. Thanks ? Altirra is picky in setting the absolute correct drive settings, if it send back any error due to incorrectly set configuration, you get the message "Bad or No LiteDOS Disk/IO-Error". Here is the zip file. Please note that on larger disks, the VTOC and directory wrap inside the cluster. VTOC always starts at sector 360 though. Example: In the 65535.ATR VTOC starts at 360, then the directory entries start at 361 goes up to 383, wraps to 256 and goes up to 359. V205 ALL POSSIBLE ATR.zip Edited July 14, 2019 by mr-atari 2 Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 14, 2019 Author Share Posted July 14, 2019 (edited) Yeah, I bumped into the same Altirra pickiness.... Here are the SD MD DD images (I removed them from the ZIP above). SMD ATR.zip Edited July 14, 2019 by mr-atari Quote Link to comment Share on other sites More sharing options...
phaeron Posted July 14, 2019 Share Posted July 14, 2019 29 minutes ago, mr-atari said: Altirra is picky in setting the absolute correct drive settings, if it send back any error due to incorrectly set configuration, you get the message "Bad or No LiteDOS Disk/IO-Error". TIL that not allowing a floppy disk with 0 tracks, 0 sectors, more than two sides, larger than 32MB, or a sector size other than 128/256/512/8192 bytes is being "picky." By the way, LiteINIT is also unilaterally setting the PERCOM block without reading it from the drive first, so it is enforcing a seek rate of 1 for drives that use that field, regardless of the drive's normal seek rate. 3 Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 14, 2019 Author Share Posted July 14, 2019 Sure, don't get me wrong... Percom is send, I expect an OK, nothing fancy. The user must pay attention to the drive setting for the desired format. Later! Quote Link to comment Share on other sites More sharing options...
mr-atari Posted July 15, 2019 Author Share Posted July 15, 2019 Ok, time for a update, version 2.06 is now online. I saw a youtube video of a happy LiteDOS user and watched him type ENTER"D:PROG.LST" while still in DUP. Effectively erasing his file, since the "command" starts with "E" and the filename is decoded after ":" ? We surely do not want this to happen. Potentially any user-input starting with a valid command-letter could give undesired results or mayhem... I had some bytes left, so I added the check that the second character after the command must be <space> or <valid drive-id>. Fixing this issue. Later! 4 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.