FS-UAE shows "DF0: Empty" for some ADF images

In my case it is Turrican 1. The official image at http://www.factor5.de/downloads_backups.shtml is apparently faulty, and the recommended best practice is to use e.g. Turrican (1990)(Rainbow Arts)[cr TRSi][t +4 ACU].

However when I load that image in FS-UAE 2.3.8dev on Linux emulating an A500+ (Kickstart 2.04), I get an Amiga DOS window, and the menu shows "DF0: Empty".

This is also the case for other cracks, as "PP Hammer".

How do I make FS-UAE recognize these images?

(As I am relatively new to FS-UAE, I'll gladly post any logs or tracebacks if you tell me how. )

[jbl007]

Just a quick test...

cd /tmp
wget http://www.factor5.de/downloads/turrican.zip
unzip turrican.zip
fs-uae --amiga-model=A500+ --floppy_drive_0=Turrican.adf

Does not work? Show $BASEDIR/Cache/Logs/fs-uae.log.txt

Hi,

Originally Posted by jbl007

Just a quick test...
...
Does not work?

That works, but as I said, that ADF image is faulty and hangs at some point in the game (see this thread).

What I am trying to get to work is Turrican (1990)(Rainbow Arts)[cr TRSi][t +4 ACU], as apparently this image does work for the whole game.

[FrodeSolheim]

Please attach FS-UAE.log.txt (to a reply here) after FS-UAE have failed to recognize the disk (quit the emulator before uploading the log).

Wait. After running it from the command line

fs-uae --amiga-model=A500+ --floppy_drive_0=<file>.adf

it works. After that also from the config file, with no changes.

I'll keep an eye on it. Thanks for the attention, anyway.

And happy new year, everyone!

Cheers,

fberger

[FrodeSolheim]

A bit strange then, running FS-UAE from the command line should in no way affect if options work in config files later. But just save the log if the problem reappears!

And a happy new year to you to

Originally Posted by FrodeSolheim

A bit strange then, running FS-UAE from the command line should in no way affect if options work in config files later.

True. Turned out it was a current working directory issue, and that my path specifications in the config file were ambiguous. So all my fault, nothing FS-UAE's fault.

Cheers,

fberger