WinUAE won't detect roms in main folder

[Maren]

Here's the problem in a nutshell: WinUAE won't detect any roms stored in the exact same folder where winuae.exe is as long as I let WinUAE set my custom paths via "WinUAE default (old)"

Example:

C:\Documents and Settings\All Users\Documents\Amiga Files\WinUAE = OK
C:\Documents and Settings\All Users\Documents\Amiga Files\WinUAE\Kickstarts = OK
C:\Documents and Settings\All Users\Documents\Amiga Files\Kickstarts = OK
C:\Program Files\WinUAE\Kickstarts = OK
C:\Program Files\WinUAE\STABLE\Kickstarts = OK
C:\Program Files\WinUAE\STABLE = BROKEN

Needless to say, using winuae.ini makes no difference, but at least I can still set the problem path manually and it will work.

[Toni Wilen]

Having roms or configurations or whatever in same directory has never been officially supported.

ROM scanner does not want to scan possible random files in winuae directory because it might take long long time..

EDIT: Is that really needed? Why would anyone put roms or configurations in winuae directory?

[Maren]

Not needed at all, I was just curious since it used to work If you look closely into my previous logs, you'll see I always use a separate folder outside WinUAE's for storing the roms.

[Toni Wilen]

Sometime ago rom scanner scanned everything but it was really slow in some situations. (user had lots of stuff and archives inside winuae folder and subfolders)

Now it only automatically detects "rom" and "roms" subdirectories.

[Maren]

For what it's worth, I basically stumbled upon this when I created a separate folder for a 100% clean, anal-retentive, obsessive-compulsive, paranoid WinUAE defaults test (I had to make sure all previous settings were indeed gone, just in case ) so I put the rom in it without bothering with custom paths and expected it to work, but I agree, it can be a mess.

[trackah123]

I had something strange too with kickstart scanning, i did not have this in previous versions.

C:\Program Files\WinUAE\ (unavailable all roms)
C:\Progra~1\WinUAE\ (works fine, basically exact same folder but short names)
C:\Users\Public\Documents\Amiga Files\WinUAE\ (works fine too)

if i put winuae.exe somewhere else, start it from there and then select "C:\Program Files\WinUAE\" it works fine again..

[Toni Wilen]

Originally Posted by trackah123

I had something strange too with kickstart scanning, i did not have this in previous versions.

C:\Program Files\WinUAE\ (unavailable all roms)
C:\Progra~1\WinUAE\ (works fine, basically exact same folder but short names)
C:\Users\Public\Documents\Amiga Files\WinUAE\ (works fine too)

if i put winuae.exe somewhere else, start it from there and then select "C:\Program Files\WinUAE\" it works fine again..

Change Path panel path type to "WinUAE default (old)". New default is new.

EDIT: above should not matter. Where exactly is your rom path? (roms in root are not supported)

[trackah123]

it was already on "WinUAE default (old)"
roms are located in C:\Program Files\WinUAE

but it would make sense if you say roms are not supported in root that would explain the "unavailable" message if its designed/coded on purpose like that.

well its still kinda supported i think but not supposed to be supported like this.
"progra~1" works but "program files" doesn't if roms are in rootfolder.

[cosmicfrog]

Ive always had KS roms and config files in WinUAE dir just had HHD`s & FDD`s somewhere else

[andreas]

Originally Posted by Toni Wilen

EDIT: Is that really needed? Why would anyone put roms or configurations in winae directory?

For doing things in a quick 'n dirty fashion
Namely:
- open or create folder 'tmp'
- put winuae.exe in
- put kick.rom in

= have a working emulator for ONE kickstart version (usually 1.3)

Well, I would not consider it unnecessary: especially for speedy 5-minute tests, I would not want to be forced to remember where I have to explicitly put the kick rom, nor to be doomed to set it using the GUI...
So the possibility to have it in same directory as winuae.exe (which *WAS* working in *VERY* ancient command-line-only winuae builds, e. g. 0.6.9, though it had to be called 'kick.rom' for successful autodetection) would be a nice-to-have.

[Toni Wilen]

That is valid reason. Everyone else only talked about unnamed "roms"..
(not that there is any difference compared to ancient versions, configuration files still work and rom scanner didn't exist..)

I guess *.rom files can be scanned in root dir too. (="plain" files only, no archives)

[cosmicfrog]

bloody cold, my roms and configs are in .\WinUAE\Kickstarts & .\WinUAE\configs
just ignore me think I`ll go back to bed till my nose stops running