EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: donnyj on 14 January 2010, 10:02
-
I remember posting about this before, but I cannot remember what the answer was. Anyways, it has been awhile....
When doing a rebuild, I get the error "Source: E:\keep\iLogicAll_Esspa+|ol.tzx doesn't exist!" and an ok box. Click on ok and the entire rebuild is canceled.
The filename is NOT normal. However, can't an error message be given and a regular cancel or ok box allowing the rebuild to continue?
The aforementioned file is in the attached archive.
Thanks
-
Works fine here.
I've create a dummy dat
game ( name "test" description "blubb" rom ( name "1" size 74133 crc 1837600b ) )
and it rebuilds fine. Maybe some oem2ansi conversion issue with the dat you've used....so...please send it.
-
did you unpack the file?
it happens to me on EVERY dat. It's the filename itself that is giving cmpro fits.
---------------------------
Path Error
---------------------------
Source: E:\keep\iLogicAll_Espa+¦ol.tzx
doesn't exist!
---------------------------
OK
---------------------------
-
Well the pipe symbol "¦" is definetly an illegal filename character since it's used for well..piping. But I don't see that character here at all. Which codepage is your Windows using?
Here it's shown as: "iLogicAll_Espa+Ôûîol.tzx" (now I hope this messageboard does no character translation,too ;)...guess I have to make a screenshot then.
-
wait a second..you unpacked it....I used the full archive....lemme test it...
-
ah ok....opening the file fails.....well...I will check what the System calls return in that case.
-
Ehe...looks like various windows programs have issues to open it...funnily enough notepad opens it....hmmm...interesting case.
edit: ok...simply putting quotes around it or using a short name conversion doesn't help to open the file. Unfortunalety "DragQueryFile" which is used e.g. when drag'n dropping a file returns the pipe symbol...wonder what else can be used to open it.
Anyway....guess it's a pretty weird filename and I wonder how it was created anyway.....maybe some unicode weirdness....nothing really to care about, isn't it :)
-
is there a way to ignore/skip the invalid names? or an ok/cancel warning? similar to the log/status window saying that a file is locked/in use
-
Well....they get skipped since they cannot be opened with the normal open functions of the win32 api....normally you don't even see a message prompt.
So I guess a prompt here and there (no idea which call produced yours) is not that hard...
Guess it's some unicode thingie....and it already depends which zip program you're using to unpack the file. With one I get a filename without the pipe (and so working on the file works fine), with a different one I get an not printable character in the filename which gets converted to a pipe as soon as you query the name.