QuickPlay Frontend

QuickPlay generates a valid path and launches this ROM normally on my NTFS-formatted SSD:

"C:\roms\Bandai\Bandai - WonderSwan\Crazy Climber (Japan).zip"

But it doesn't work on my exFAT-formatted external HD:
"E:\roms\Bandai\Bandai - WonderSwan\Crazy Climber (Japan).zip"

Emulator: Mednafen Bandai WonderSwan Color (configurated automatically by QuickPlay)
QuickPlay 4.6.6
Windows 10 64-bit

Hi - could you give me any more details - why doesn't it work, what happens? any error messages? any screenshots you could show?

Without knowing more i'd probably be interested in: What is the contents of that zip file? if you unzip the contents, and link directly to that in quickplay (make a temporary romdata that just loads that), does it work then?
also if you rightclick the rom and go to 'run as', what is shown in the runas dialog? Again a screenshot would really help

The title of the topic says 'wrong path generated' - in what way is the path wrong?

Sorry, I've forgotten to include the screenshot. These are simple zip files with clean No-Intro .ws roms. The problem is that everything after the first space is cut off. Mednafen says: This happens with %SHORTROM%. If I change it to %ROM%, it doesn't work on either filesystems.

Have a read of this: https://docs.microsoft.com/en-gb/window ... ing-a-file

Note that there is MAX_PATH, a limit on how long a windows path can be. In order to accomodate potentially very-long rom filenames, I often have tried to use the 8:3 name of the emulator and/or the rom in command line calls. However, also note in that link that you can't assume that your drive allows for 8:3 naming (since it slows things down). You'll find I think that your EXFAT volume has 8:3 disabled, so instead windows is using the fullpath and cutting off the first space. really I think i should have put all the %SHORTROM% calls in the mednafen efind file in quote marks: "%SHORTROM%" in case of this circumstance. Feel free to do that to the file and send it back to me to include in the next release! Another alternative you could do, if you DO have rom paths that come to over 260 characters (fairly likely) is to enable 8:3 naming if that's supported - see https://msirevolution.wordpress.com/201 ... n-windows/

(also: this is why %ROM% didn't work for you, because it always needs to be "%ROM%" because of spaces in file paths)

Thanks for the explanation!

thanks i'll make sure this makes the next realease!