rom scanner

[hoborg]

Hello - just small info.
Oficial WinUAE 1.4.1 stoped detecting ROMs files named "kick34005.A500, kick40068.A1200, ...".I used this filenames, becouse of WHDLoad. In previous versions, this works fine.

Sorry for my english

[StevenJGore]

Originally Posted by hoborg

Oficial WinUAE 1.4.1 stoped detecting ROMs files named "kick34005.A500, kick40068.A1200, ...".I used this filenames, becouse of WHDLoad. In previous versions, this works fine.

I experience something similar. The first time I scan for ROMs, WinUAE will find about 75% of them. If I scan again, it will find all but the A500 1.2 ROM. If I close WinUAE, open again, and rescan for ROMs, then it will find 100% of them. Weird!

Steve.

[Toni Wilen]

Official WinUAE 1.4.1 stoped detecting ROMs files named "kick34005.A500, kick40068.A1200, ...".I used this filenames, becouse of WHDLoad.

1.4.1 ignores if file extension is not .rom, .key, or any supported archive. (because some users store other crap in rom directory or don't even have rom directory resulting in really long scan..)

I'll think about something..

The first time I scan for ROMs, WinUAE will find about 75% of them. If I scan again, it will find all but the A500 1.2 ROM. If I close WinUAE, open again, and rescan for ROMs, then it will find 100% of them. Weird!

You sure you aren't confused by "feature" (ok, it is a oldish bug and still not fixed) that requires winuae restart before scanned roms work.