Jump to content

mr-atari

Members
  • Content Count

    1,016
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by mr-atari


  1. 17 hours ago, drac030 said:

    Man, I do not care what it is or what it is not. It is you who wants support in ATARIDOS.SYS, so it is your problem, not mine, to make the format reliably detectable among everything else.

    No it was NOT my request, it's from a SDX user and I asked you not to shoot the messenger... and you did just now.

    😢

     


  2. It's just a small DOS version, mate. No high-tech multi-purpose OS.

    Sector 360 is as described above, perhaps you can use byte 5-9 ?

    [edit] or word on byte 1,2 is larger then word on byte 3,4

    [edit] ID-values are $40-$7F

    I used the Atari Tech Manual as template and DOS 2/2.5 is the most used.

     

    For the other question I had:

    I do have an LiteDOS-XS upcoming in -SE format.

    🙂

    It was almost ready back in May, but left it to do other things.

    I will review the code and make it ready for upload.

     

    Atari BASIC:

    image.png.b05927e3896dfae29ee82711e4c88cf8.png


  3. You can still read LiteDOS disks as discussed.

    Since write-support is not supported in ATARIDOS.SYS, nothing changed in that respect.

    I guess.

     

    Some tech-info:

    The ID-byte -SE (sector 360, byte 0), bit 7=0 and bit 6=1.

    The rest of this byte is the cluster-size (1-64 sectors/cluster).

    Directory-size equals 2 times the cluster-size to match things up with previous versions.

    Also starting on sector 361 until the end of the cluster, then wraps to the beginning.

    Further more:

    Sector 360 is more DOS 2 like, bitmap starts on byte 10, byte 1-4 reflect size and free space, byte 5-9 are zero.

     

    I had plans to support writing to DOS 2 and compatible formats, but canceled this on release.

    I do not want to f*ck up other format disks...

     

    But LITEINIT can/does convert any LiteDOS to LiteDOS-SE

     

    Grtz,

    Sijmen.


  4. I think I found a bug in ATBasic 1.57

    While coding/debugging LiteDOS


    It goes like this:

    SAVE to disk and we get an error like 162, disk full.

    IOCB #7 is not closed, data still in the disk-buffer.

    I swap disk.

    DIR to see if there is room.

    IOCB is closed, DOS writes its buffer to (the new) disk,  and re-opens for DIR.

    Oops?

     

    Compared to Atari BASIC, it closes the IOCB immediately following a SAVE-error.

     

    Grtz,

    Sijmen.

     

    • Like 5
    • Thanks 1

  5. On 3/3/2021 at 4:16 AM, Big_D said:

    Well, good news and bad news, first I was able to revive the cartridge. I downloaded the 3.5 flasher I would further down the forum and that flashed and booted. Now I ran the MyBIOS 4.8.05: -RE -RI -DE -DI (5-feb) -FI -FE (7-feb) ATR file with my 8mbit cart and it flashed a bunch of games on it. So, I'm not sure if the file has been replaced, or I could still be doing something wrong.

    No idea yet, what went wrong, but this is the correct file:

    Last firmware update I did for MyIDE-I is here (4.8.0A, unreleased beta with bugfixes to the -05 version).
    https://www.atarimax.com/flashcart/forum/viewtopic.php?p=9942#p9942

    • Thanks 1

  6. I have my WARP-code still at hands.

    It can do 420 kbit/sec easily (without block transfer).

    Yes, ANTIC/NMI off.

     

    Currently FujiNET is the only device (beside my SIO-2-arduino) with external clock.

    But the firmware of Fuji does not lock this.

    On IO-error it hops to 19k2, then to pokey-divisor_X and back.

     

    Grtz!

     

    [edit] (*) All caps removed on the pokey-lines !

    • Like 1

  7. These are generic eeproms

    I opened mine, to have a look.

    ST (maker) M29F010B (1 megabit)


    This is the transparent one, early versions were black, you can easily open them.

    They are not glued, just pressed together.

    I use a Transcend 128mb, no problems, with the latest firmware I created, the one you downloaded.

     

    Black screen, means, eeprom erased, nothing programmed.

    • Like 1

  8. 6 hours ago, _The Doctor__ said:

    litedos xs?

    litedos ro?

    dunno, about apeloader as a standalone but why not? and lots of 3 sector loaders out there... wasn't this already covered

    during some talk of loading disk stuff with a 400 etc...

    food for search and thought in any case

    @mr-atari

    what's the memlo of xs and ro?

    But they are still handler based, so it installs D to the device-table.

    -XS $BD0

    -RO $9FF
    Doing a destructive load, you can start at loading $8F4

    In theory, a loader, can be much smaller....

     

    • Like 1

  9. 12 hours ago, tschak909 said:

    * People that don't use SDX

    * People that use SDX

    The problem is more who use Fuji as stand-alone or not.

     

    I have the same 'issues' when booting over SIO, I have a executable that loads and mounts the last stored Fuji-config.

     

    I would suggest that FujiNet should restore the last configuration by it self when something else takes boot-control.

    That works for any DOS or any one who uses Fuji as device (not stand-a-lone)

     

    Is that workable Thomas?

    So during powerup:

    -if Something else boots, restore configuration.

    -if Fuji boots, do the config stuff and end with OPTION to boot.

     

    I really hope this can be done.

    Later!

    • Like 1

  10. 14 hours ago, ivop said:

    I have the feeling that you are not on the same page, so to speak. @xxl an unmodified 800XL can reach divisor 0 if either the device has proper Schottky diodes in place (I have seen that working on a prototype of @mr-atari, even higher bitrates when Pokey is externally clocked), or if you run your device through @lotharek's SIO hub, which has similar signal clean-up in place.

     

    Edit: yes, SIO2SD should be able to reach divisor 0 with above mentioned solutions.

    Maximum external clock speed is 4 cl/bit for POKEY to accept serial-data in the shift-registers.

    That is what I found by trail and error.

    That is a whopping 443 kbit/sec (or 44 kByte/sec) !

    Called "project Warp-factor 4" back in the days.

     

    My experimental device is a SIO2SD-arduino, with attached clock-lines.

     

    FujiNet currently has the external clock enabled with programmable Khz.

    But you need to remove the caps to make this work.

    https://github.com/FujiNetWIFI/fujinet-platformio/wiki/SIO-Command-%24DF-Set-External-SIO-Clock

     

    The code is a bit tricky, since switching from asynchronous to synchronous is not that straight forward.

     

    Grtz,

    Sijmen.

    • Like 1

  11. One of my early production IDE interfaces.

    Interface only, no boot-rom.

    Should come with 2x 5.25"discs with software/drivers and a 3.5" disc for SIO2PC.

     

     

    I don't see them often pop up.

    Nice though, was fun times, using pole position cartridges and converting them.

     

    Currently Atarimax has the rights to produce MyIDE-interface based hardware.

     

    Later!

×
×
  • Create New...