ADFFS 2.83

[JonAbbott]

Question about F.R.E.D. - to toggle mirrors you have to press up / down, but this doesn't work if any other keys are also being pressed. Is this related to a copy protection routine?

Unlikely. It's probably down to the way it was coded.

[wmd]

F1016301 Flying High: Euroblaster (1997) (GEK)
F1016302 Flying High: Joust (1997) (GEK)

In obey.zip these two are mixed up - the F1016301 file is for Joust, while the F1016302 file is for Euroblaster.

[JonAbbott]

F1016301 Flying High: Euroblaster (1997) (GEK)
F1016302 Flying High: Joust (1997) (GEK)

In obey.zip these two are mixed up - the F1016301 file is for Joust, while the F1016302 file is for Euroblaster.

Thanks for reporting.

obey.zip is actually correct, it's the ID in the OP that was the wrong way round.

[wmd]

I came across another issue:

- Open a JFD via ADFFS
- Eject JFD
- Click :0 drive (with a physical floppy in drive) - error: "Filecore does not understand this disc"
- Click :0 drive again, physical disc reads normally

[wmd]

Also, in the obey file for Axis (F1003401), there seems to be a typo:

2. Save the disc 1 image as !Axis.F1003401
3. Save the disc 2 image as !Axis.F1003401

Presumably, that should be:

2. Save the disc 1 image as !Axis.F1003401
3. Save the disc 2 image as !Axis.F1003402

[JonAbbott]

- Open a JFD via ADFFS
- Eject JFD
- Click :0 drive (with a physical floppy in drive) - error: "Filecore does not understand this disc"
- Click :0 drive again, physical disc reads normally

Could you try the following and let me know if it still reports an error:

1. Open a JFD via ADFFS
2. Dismount from the ADFS::0 Filer icon
3. Eject from ADFFS

Also, in the obey file for Axis (F1003401), there seems to be a typo:

Good spot, I'll correct for the next update.

[wmd]

Could you try the following and let me know if it still reports an error:

1. Open a JFD via ADFFS
2. Dismount from the ADFS::0 Filer icon
3. Eject from ADFFS

I tried that, and it seemed to work, but when I repeated the process on a different JFD I got a slight variation of the error - clicking on the :0 drive icon (with a floppy in the drive) opened the drive contents window, but no files were displayed (the correct disc name was showing in the window title though). When I closed the disc contents window and clicked on the :0 drive icon again I get the same error as before - "Filecore does not understand this disc". Subsequent clicks on the :0 drive icon keeps giving that error. Physically ejecting the floppy disc then reinserting fixes the problem.

[JonAbbott]

Physically ejecting the floppy disc then reinserting fixes the problem.

Probably best to avoid inserting a physical floppy until a mounted floppy image has been ejected as ADFFS can't ask ADFS to rescan the drive 0 when it hands back control. ADFS works off the hardware and whilst ADFFS has taken over drive 0, any physical floppy change notifications get lost.

The second issue is off the back of the first and probably caused by ADFSBuffers, where you're seeing cached sectors coming from the floppy image that haven't been removed.

[wmd]

About the Uffenkamp re-releases of the Eterna games - using ADFFS, can they be installed to HD, unlike the original releases?

[JonAbbott]

About the Uffenkamp re-releases of the Eterna games - using ADFFS, can they be installed to HD, unlike the original releases?

The ADFFS boot scripts for them certainly look like that's possible as they're all checking if they're run via Boot floppy or manually and do not have hardcoded paths.