FS UAE and Launcher Config Issues

Dear all

I'm new to this forum. Even though I have been using FS UAE and Win UAE for quite some time, I have recently run into some weird issues whil trying to run FS UAE.exe or out of rom collection browser in XBMC/Kodi. What I did is the following:

- I started the launcher and set it up to launch the game "Nitro"
- I saved the the configuration with the name "Default". This created a config file named "Default.fs-uae" in the config folder. I opened the config file and the content looks good.
- I start the game through the launcher and everything works as intended.
- I copied the Default.fs-uae into the main folder next to fs-uae.exe and named it "Config.fs-uae" to be sure.

But:
- when I launch FS UAE by clicking on the exe I can see that the default config is loaded, because the emulator starts in full screen, but it remains sitting at the screen waiting for a disk to be inserted, even though the floppy drive (floppy_drive_0 = Nitro.zip) is loaded with the game (I tried both .zip and .adf)

- when I launch it through rom collection browser, it just opens a small window with kickstart 1.3 waiting for a disk to be inserted.

Why can the launcher launch the emulator with the game running using my config, but the FS UAE exe cannot? I'm obviously missing something, but I cannot find out what.

[FrodeSolheim]

Originally Posted by Girgl

but it remains sitting at the screen waiting for a disk to be inserted, even though the floppy drive (floppy_drive_0 = Nitro.zip) is loaded with the game (I tried both .zip and .adf)

When you specify floppy_drive_0 = Nitro.zip, it will look for Nitro.zip in the "current directory" or in the floppies directory. But note that "current directory" is not the same as the directory containing the exe file (what it is depends on how the application was started).

Instead, do something like this, if Nitro.zip is placed in the same directory as Config.fs-uae:

floppy_drive_0 = $CONFIG/Nitro.zip

(this tells FS-UAE to look for Nitro.zip in the directory containing the config file it has just loaded).