mr-atari

Message send. Hoop you can do something with it. Reading someone else his 6502/assembler is tricky. Grtz, Sijmen.

Try this, it's based on the latest build, but has no RESET-key protection. It actually has, but the code is not present in RAM. I manually hand-patched the 16k cartridge-code. So use SHIFT-CONTROL -ESC -TAB to do warm or cold start. Beside that, it seems to run fine on my end. Boot with BASIC disabled. MyBIOS-RAM.atr

I just tested. 1.3 Disk version seems to run just fine at 2400 baud. Loading with LiteDOS also works, saving not tested, most likely the "not using $9B/EOL"-bug is still present. For no reason, Plato erases page 6, effectively wiping out my ESP-driver. So I needed to revert to an older driver, not using page 6.... I have no time to hand-patch every plato-version released. Beside, Thom has the FAST-IO code to do STATUS/GET/PUT bypassing CIO to go much faster. Cheers, Sijmen.

Did I miss something? Sure the project is still alive. But when nobody reports bugs or issues, nothing to-do. Latest versions are online. Been playing with SIO2WiFi / LiteDOS the last 2 years, perhaps that's why? For direct questions and such, better email me on my homepage. I am not 24/7 online.... Cheers!

2.08 now online. Request for wildcard copy, instead of only doing the first file found that matches. I'll work on that and see where it goes, since there is no free memory to code.... Fixed: Commands bypassing CIOV, like BASIC's PUT # and PRINT #. File-ID, used for DOS2-compatibility. Added: Sectors 1-15 are now reserved as "bootsectors" on SD-disks. Exception is MD-disks, where sectors 1 + 1026-1039 are reserved. Sectors 1-10 are reserved on DD-disks.

Thanks for the bug-report. I get to it as soon as possible. Info: LiteDOS does not use this file-ID anyway, so that is OK. But if you want to read the file with a DOS2-compatible, it will error out with a mismatch. I have an update anyway, since the functions PUT # or PRINT # are broken. So I add the File-ID to the todo-list. Sijmen.

Because it calls the Atari-OS routine that does Power-up ?

LiteDOS does not write to disks that are in a different format. So you can rule that out. I just send an ATR to Avery in "DOS 2.5" format, that not will detect correctly either. Let's wait and see. Grtz!

Autorun: yes, just change the last byte of sector 1 to $FF That will execute the first file found. Must be an executable of course LiteDOS-XS only reads 128 byte/sector up to 1023 sectors/disk. So 720k, being DD and 2440 sectors is a No. He could use multiple disks though. All above, also goes for LiteDOS-RO Still working on that, need to move some routines to make memlo around $800 (or $0800 in your case). For users who wants to autorun only one file and do not need LiteDOS afterwards. Grtz, Sijmen.

If needed, you can try my LiteDOS-XS, that has some more limitations, but has a memlo of $C00 All info can be found and downloaded from my homepage. Perhaps I will release a LiteDOS-RO version (ReadOnly) shortly, that even has a lower footprint. That can be used as a "gamedos" with the ability to load files afterwards. Grtz, Sijmen.

No sweat, these games are fun. Mine isn't original either, it comes from a game in my childhood. Stone sling on videopac. I pimped it a bit, with left/right and angle. Collision in the air is present (also fun) and I coded it into Atari specifications. 4k fun, simple and colorful. Later! Sijmen.

Some spinoff of defend your castle? www.mr-atari.com/defyocas/ ??

LiteDOS 2.07 and -XS are now available on my homepage. XS are two templates of empty disks in SD and MD format. DUP uses only numbers (DIR) or RETURN (load). If needed use LiteDOS to copy executable-files on them. But LOAD/ENTER/SAVE/LIST works just fine. Enjoy and don't forget to report any bugs or issues.

"Spin-off" LiteDOS-XS, great for 600XL users, uses 1k less. ? More limitations, but does the trick. Reads DOS 2 and compatibles, SD/MD floppy only, 1 buffer. DUP only for loading and DIR. Available on request.

Thanks! yes, the "One character" commands did not work in 2.06, due to the second character being <EOL> Rather an embarrassing error.... But not as nasty as the ENTER"D:FILE.LST"-bug while still in DUP with 2.05 Change-log, Added: Second character in a DUP-command must be valid, <space>/<number>/<EOL> Need to check your runbas.xex, the one included was created with the DOS 2.5 setup. Currently coding a spin-off "LiteDOS-XS" for floppy SD/MD only. ? Later !

Version 2.06 is now available for download. I added the check that the second character after the command must be <space> or <valid drive-id>. Fixing potentially mayhem when, still in DUP, any user-input starting with a valid command-letter giving undesired results.... Also I added a small executable that can turn LiteDOS disks in automatically load/run BASIC-programs. SMALL: uses only 2k RAM, 4k more free memory, even (XL/XE-64k) 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/

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!

LiteDOS does not write to disks, if it is not " LiteDOS format".

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!

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

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

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

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.

Thanks !

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.