home.social

#jiffydos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jiffydos, aggregated by home.social.

  1. The family is almost complete; I do have C128DCR+1571D #JiffyDOS EPROMs in my drawer, but no dumps of them...

  2. So, now I backed up the #JiffyDOS images from the chip I bought for my C16, and can now use it in VICE as well.

    It took 25 seconds to save the default ROM to my #SD2IEC, only 8 for the JD ROM.

  3. #commodore #c64 #c64u #c64ultimate #ultimate #retro #gaming #games #jiffydos #turboloader

    Everyone who is into the C64 breadbin should consider buying a JiffyDOS turbo loader to avoid very long loading times, either from the original floppy drive hardware or from a USB stick or memory card.

    You can get JiffyDOS here:

    https://jiffydos.de/startseite/49-jiffydos-64-ultimate-rom-overlay-image-standard-pack.html

    The package shown is the full package for the Ultimate 64 ...

  4. #Commodore has released firmware 1.1.0 for the #C64ultimate and it seems to contain the fixes from Gideon's #Ultimate64 3.14d firmware (including more robust #JiffyDOS support) while retaining the more refined system menus from the Commodore branded computers.

    #C64 #C64U #U64

  5. Responding to myself responding to myself:

    I borrowed the KERNAL, Basic, and Char ROMs from a VICE installation, after which the updated #Ultimate64 booted up as expected. I can’t say for sure whether all issues are gone, but Mayhem in Monsterland, which would never load successfully with #JiffyDOS earlier on this machine started up like nothing; and Gunship, which would inevitably crash at an arbitrary point in loading, has come right up into flight mode. Awesome!

  6. Experimenting with #JiffyDOS on my #Ultimate64 - it seems to be pretty hit-or-miss. The webpage had a note recommending what seems to be CIA timing settings:

    > Can I utilize JiffyDOS on the Ultimate II?
    >
    > Yes. Customers have noted that settings PH1=140 and PH2=80 work well.

    I don’t see any way of finding nor tuning these settings, though. Have I misunderstood something?
    #c64 #c64ultimate #c64u

  7. Bought some #JiffyDOS chips for various hardware. These come with toggle switches to switch them out. Instead of drilling a hole in my case(s) for that, I'm thinking of cutting a rectangular window and putting a DIP switch block there and just wiring to the first one, for future switch use (bigger eproms, etc). Is this a good idea, or are the little DIP packages not suitable for that purpose for some reason I haven't divined?

  8. @mos_8502 I guess #JiffyDOS stops the realtime clock during disk operations, because I had enough time to take a shower and empty the dishwasher while that was running, and that was on a #SuperCPU #Commmodore64, writing to an SD2IEC...

  9. @mos_8502 I guess #JiffyDOS stops the realtime clock during disk operations, because I had enough time to take a shower and empty the dishwasher while that was running, and that was on a #SuperCPU #Commmodore64, writing to an SD2IEC...

  10. @mos_8502 I guess #JiffyDOS stops the realtime clock during disk operations, because I had enough time to take a shower and empty the dishwasher while that was running, and that was on a #SuperCPU #Commmodore64, writing to an SD2IEC...

  11. This problem seems to have gone away. Works fine with #JiffyDOS today. I figured it should, since it does on original hardware.

    Here's a way to get a decent setup rolling with Power C on the #C64U. This is simpler than it looks.

    1. Set drive A to be a 1581 on #8, and enable virtual drive B on #9 (don't care what type).
    2. Get the Power C disk images. Here's a good resource: https://github.com/GroundhogGrafix/PowerC-C64-C128/tree/main/PowerC
    3. Either copy Unmodified-PowerC.d81 to your flash/SD, or grab the two D64 images. If you grabbed the D81, skip to step 5.
    4. If you used the two D64 images, copy all of the files from disk 1 and disk 2 onto a single D81 image. You need both sets of files on the same disk to work without swapping disks.
    5. Mount that D81 image on drive 8, and a blank image on drive 9.
    6. Copy all of the .h files from drive 8 to drive 9. Note that you can copy files in and out of images directly on the C64U menu; you can just arrow into image files and copy and paste from there just like normal directories.
    7. Reboot the system (for good measure).
    8. LOAD"SHELL",8 (not ,8,1; that didn't work for me) and RUN it. You will now see a $ prompt.
    9. Type work 9 0; this means drive 9 is your work disk.
    10. l lists the files on the WORK disk (9, with your sources) and ls lists the files on the SYSTEM disk (drive 8)
    11. Use ed or ced to edit your file. If you are confused press RUN/STOP and type help at the command prompt. To quit: R/S quit.
    12. Compile with cc -p foo.c and it will read it from drive 9. The .h files must be on the same drive.
    13. Link with link to produce a .sh executable that runs under the shell, or link -s to make a standalone executable with a BASIC loader. Type the name of your foo.o file and then type ^ (up arrow) to load the dependencies. Then hit enter and type your executable name (including the .sh if you didn't use -s).
    14. Run your program from the shell with foo (without the .sh). Or go back to BASIC and load/run it with LOAD and RUN, if you linked with -s. Go back to BASIC from shell with bye.

    Voila. You can now edit, compile, and run C programs from a shell, directly on your C64. And with JiffyDOS it's reasonably fast, too. But it's only 40 columns.

    Naturally, you can do the same thing on a real C64, but with only 1541s you will be sad because the whole compiler system doesn't fit on one 5.25" SS/SD floppy. It would probably fit on a 1571 5.25" DS/HD floppy, and definitely fits on a 3.5" 1581 floppy. It's just harder to set up, mostly because of copying the files.

    BTW there is a Power C manual on archive.org.