LucentW
commented
2 months ago I tried to help a friend troubleshooting the same exact issue, but with a RGBNES-modded AV Famicom rather than a FPGA hardware emulator and seemingly some RAM adapters are super fussy about hotplugging.
While I don't own an FDSKey yet (I'm waiting for a replacement to come since the first I got was DOA), I was able to replicate the same behavior on a fully stock AV Famicom by unplugging and replugging the FDS while a game is running. With another RAM adapter I own and the same FDS drive the issue doesn't happen, but it restarts my cheapo multiout to HDMI dongle, pointing at a some sort of load spike.
Maybe @ClusterM can chime in with some further tests?
Hey there,
I switched over to using the latest interim version for performing this, and my FDSKey is at v1.3. (I opted to use the interim version because I kept getting a no power error message, but this was when my FDSKey was at 1.0. I haven't tested the non-interim version with my FDSKey at v1.3)
When I boot into DupliFDS, it'll prompt me to eject and then insert a source disk, I'll perform such through FDSKey (In this case, I'll select DupliFDS again as my source). It'll read the source successfully and prompt me to eject the disk. I'll hit the eject button, and then it prompts me for inserting the target disk. At this point, I'll unplug the FDSKey and plug it into my Famicom Disk System that's connected to an Analogue NT Mini Noir V2. At this particular step, this is when DupliFDS crashes every time. After making the connection to the actual FDS system during this (Which I've modded to allow rewrite), the system crashes.
Edit: DupliFDS also crashes at the Source disk step when I swap from the FDSKey to the FDS. So it seems crashes only occur when I swap to the actual FDS.
I realize this could be a longshot since I'm using an FPGA system that's no longer sold, but any ideas what could be happening to cause the crash? Any workaround that could be done?
Thanks!