MiSTer FPGA Forum

Probably WinUAE can use more different HD file formats than MiSTer. You could prepare the HD with MiSTer (empty file, partitioned by HDToolBox) and then use WinUAE to copy files to it.

The UART solution is pretty slow (~ 10kB/s) compared to real cards for Amigas (~ 100kB/s), so there is some justification to work on this. I see no extra value in implementing real hardware for network access, since a driver is needed in any way. Therefore going the A314 route seems to be the most efficient.

I also thought about this. Probably the way to go would be to adapt the A314 ethernet solution.

https://github.com/niklasekstrom/a314

That project was also was the inspiration for the shared file system.

Well, it might work in another way. The usb iomega should show up under linux as /dev/sdX. You can create a symbolic link from your Amiga directory, like

ln -s /dev/sdX /media/fat/Amiga/iomega.hdf

Then you should be able to select that file as harddrive in the OSD menu. The iomega software will most probably not work though.

The action replay crt does indeed work. The C128 core started in C64 mode automatically whilst I had the display on 80 column mode... hence I thought it crashed when indeed it was working as intended. Sorry, stupid beginners mistake.

I tried an action replay crt file, which works on the C64 but the C128 core won't start when it is loaded. This is an important freezer, which should run on a C64 core. Therefore it is definitely too early to replace the C64 core.

Sorgelig fixed it. Should work with stock SetClock in next release.

I found the problem: the MiSTer binary only updates the rtc time once a minute... and the 1.3 SetClock checks for a change in the seconds register after waiting for 1.5 seconds... a solution would be to incement the rtc counter on the hps side inbetween. I'll have a look into it.

I patched the detection routine. The attached version works on Kickstart 1.3, but will assume that there is a real time clock. Which is always correct for Minimig on MiSTer, but might crash systems without RTC (since then it will access the custom chips).

The RTC is not really implemented. The HPS side supplies the necessary data, but writing to the RTC chip is not supported. So, if the setclock program does some probing, it will conclude that there is no RTC clock.

You can also patch your kickstart ROM to always execute a full cold boot. That way no virus can survive a reset.

Actually, you have to put $60 into $f80154 in the official KickV1.3_34.005 (replacing $66).

Malor wrote: ↑Thu Jul 28, 2022 8:43 pm Hmm, seems like any new software would probably be written for the fastest clocking, so the Mister's version would probably be considered drastically inferior.