Jump to content

mr-atari

Members
  • Posts

    1,202
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by mr-atari

  1. 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
  2. 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
  3. 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
  4. 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!

  5. 13 hours ago, phaeron said:

    You can't just change the protection on an address space range, something has to provide RAM at that address. One way is to write a custom device that has a memory layer to map 256 bytes of RAM there.

     

    How do I write a custom device?

    Is there a template I can download/use?

    I know my way around in 6502, that's about it....

     

    OK, I cut/paste your example of 8k cartridge and changed to this:

    It does something, any good like this ???

     

    Thanks!

     

    ---------------------------------------------

     

     option "name": "256b D500-RAM";

      Segment ram: {
          size: 256,
          source: "d5ram.bin"
      };

      MemoryLayer wina: {
          name: "D500-RAM",
          address: $D500,
          size: $100,
          segment: {
            source: ram,
            offset: 0,
            mode: "rw"
          },
          cart_mode: "left"
      };

  6. On 5/15/2020 at 3:41 AM, phaeron said:

    This is intentional, both to prevent the emulated computer from opening huge files. This is particularly an issue with H6-H9: since the file is kept in memory to support seeking with EOL translation. You should have gotten disk full errors trying to write to the file past that point, however.

     

    I could see lifting this limit for H1-H4: since in that case the data can be spooled to/from disk.

     

    Any progress in fixing the 16mb limit?

     

    One request, that is pestering me always, is it possible to include a tic-box in the device-list?

    This to disable or enable devices.

    That would awesome, when testing software on many different systems...

     

    Thanks!

    image.thumb.png.2dc609cecb512f8c8ac7c3eb2a1259c1.png

    • Like 2
  7. You could order a reset-button from steve.

    Not sure if it's on sale, or if he has it on stock.

     

    But you need to open the cartridge, drill a hole and solder a little PCB onto it.

    It goes into the JTAG-header, it's a simple soldering job.

     

    I tried a few prototypes and they work nicely.

    DSC07839.JPG

    DSC07835.JPG

    • Like 3
  8. 5 hours ago, phaeron said:

    This is intentional, both to prevent the emulated computer from opening huge files. This is particularly an issue with H6-H9: since the file is kept in memory to support seeking with EOL translation. You should have gotten disk full errors trying to write to the file past that point, however.

     

    I could see lifting this limit for H1-H4: since in that case the data can be spooled to/from disk.

     

    If that would be possible (or at least one specific Hx:), yes please.

     

    I did not check for errors (on write), assuming when files are opened correctly, this should not happen.
    So that went passed me.

     

    It had me puzzled for some time, since I was working on video-compression and I could shrink 500+ Mb into 16, lol...

     

    Many thanks in advance ?

  9. I have an issue with device H:

    Most likely nobody noticed because of the file-size in "normal" use.

    But when I output (or throughput) a file, it's output-size is limited to 16Mb.

    All bytes beyond 16Mb are lost in space...

    Can you have a look?

    Thanks!

×
×
  • Create New...