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

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.

  • Set drive A to be a 1581 on #8, and enable virtual drive B on #9 (don't care what type).
  • Get the Power C disk images. Here's a good resource: https://github.com/GroundhogGrafix/PowerC-C64-C128/tree/main/PowerC
  • Either copy Unmodified-PowerC.d81 to your flash/SD, or grab the two D64 images. If you grabbed the D81, skip to step 5.
  • 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.
  • Mount that D81 image on drive 8, and a blank image on drive 9.
  • 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.
  • Reboot the system (for good measure).
  • LOAD"SHELL",8 (not ,8,1; that didn't work for me) and RUN it. You will now see a $ prompt.
  • Type work 9 0; this means drive 9 is your work disk.
  • l lists the files on the WORK disk (9, with your sources) and ls lists the files on the SYSTEM disk (drive 8)
  • 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.
  • Compile with cc -p foo.c and it will read it from drive 9. The .h files must be on the same drive.
  • 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).
  • 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.

    PowerC-C64-C128/PowerC at main · GroundhogGrafix/PowerC-C64-C128

    Power C Utilities and Routines. Contribute to GroundhogGrafix/PowerC-C64-C128 development by creating an account on GitHub.

    GitHub
    Seems that Power C doesn't work right with #JiffyDOS, at least on my #C64U. It reads bogus characters while reading source files (just the compiler; the editor works fine).