EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: Dullaron on 21 February 2012, 09:02
-
OK I'm posting my issue here.
If you taken one of the CHD and then put into the ROM's folder. Run scan. The scanner will freezes at 0% and then sit there. It haven't moved it into the CHD folder with it name or anything. The cmpro and cmpro64 will say it is running on the Task Manager screen. But what is it doing actually? Fixing the CHD? It blink on the rest of the screen. Just showing the CHD name on the screen. The program isn't frozen up.
The other problem is that I had two bad CHD's. I fix that issue already. Both are deleted.
-
Do you have Scanner->advanced->allow chds in rompath root enabled or disabled?
Depending on that setting, maybe you simply don't see the prompt asking you if you want to move the chd somewhere else.
I did a quick test on this and there is no freeze or crash here.
Anyone else with test results?
-
OK now it crashing. I will wait.
-
Please answer my question regarding the allow-chds-on-rompath-root option.
-
Please answer my question regarding the allow-chds-on-rompath-root option.
It's also possible he's using the old command-line syntax for updating CHD's (v4 vs. v5), in which case it would likely appear that nothing is happening since clrmame didn't get the validation text from CHDMAN to continue? Just a guess...
-
chdman is only called when you got the deep verification enabled and you do see the cmdline window and if cmpro can't run it, you will see an error message.
-
Enabled or not. Still the same issue. Windows 7 64-Bit Home.
-
please use above sticky topic.
I can't reproduce your issue here. In you mameboard screenshot I see "usagui" listed as unneeded. This is not a set of MAME.
So what chds did you move to a rompath root?
-
I will install those and then see that the problem. I didn't install any of it.
usagui was in it folder in the ROM's folder.
-
Erm...what? what are you talking about?
How can you repeat the issue? Which chd did you move to a rompath root and usagui is what? it has nothing to do with cmpro or mame...so I guess just an unneeded file which gets listed as unneeded hopefully.
-
I don't have the cmpro and cmpro64 in the Program Files. Both on a slave part of the drive.
-
why do you want to move it???? Keep it as it is (and especially keep it in a non-UAC folder)
You said, you moved a chd on rompath root level, so which chd? That'S all I want to know...keep your setup as it is... and try to reproduce the problem by moving 1 (or more chd). Let me know the details.
-
OK I got it halfway working. Cmpro64 will crash with the 3ga000.chd in the ROM's folder. But it did moved it into sfiii2 folder this time. I think it the scanner issue on my end and don't know why. Scanning the ROM's will work. Anyway I already install it into the C:\Program Files\clrmamepro and set to Run as Admin...
-
OK all fix. It have to be in the C:\Program Files\clrmamepro and problem solve. =)
-
It is not recommended to put cmpro in an uac controlled folder.
What OS do you run?
Is your used user an admin?
Where did you place cmpro when it was crashing?
Where did you place the roms when it was crashing?
-
The program was in the I:\clrmamepro when it crash.
ROM's here at I:\MAME\roms.
Windows 7 Home Premium with SP1
I will move it to C:\ from the C:\Program Files\ and then try again.
-
OK not working now. Crashing again.
Like I said the program have to be in the C:\Program Files\ in order not to crash.
-
Are you logged in as an administrator user?
Did you run cmpro without any additional "run as administrator"?
Does it always crash? Is the position where it crashes always the same? (You might be able to see that by monitoring the progress window)
-
Heh I gave up. I'm sick of it crashes only because of the CHD's. I bet it gotta be the chdman that is causing this. I made all of the MAME files. I'm holding off for now.
Yes I'm a administrator user. Only one is using this computer.
I did try the run as administrator and without it. Same issue.
Same crashing.
-
it is definetly NOT caused by chdman since chdman is only called when you got the scanner advanced option enabled to do an unpack and calculation of sha1/md5 files....looking at your screenshot I see that it crashes during the uneeded checks.
You can send me your cmpro.ini file and the belonging .cmp file from cmpro's settings folder for your used profile.
-
Dullaron
I know you keep your roms here
I:\MAME\roms
But I must ask, do you have CHDs in a different folder, on a different drive ?
Are any of these drives external ?
Please help see this bug report through
-
I did try CHD on drive C and it did the same thing. I put all back on Drive I and then redone cmpro64.
Here the files.
-
I forgot to tell you that I'm using mame64.exe.
If you want me test the mame.exe then let me know.
-
Files that help describe the problem:
C:\Users\Mitchell\AppData\Local\Temp\WERA038.tmp.WERInternalMetadata.xml
C:\Users\Mitchell\AppData\Local\Temp\WERE303.tmp.appcompat.txt
C:\Users\Mitchell\AppData\Local\Temp\WERE313.tmp.mdmp
Here is the report from my Windows 7 Home 64-bit.
I don't know this will help or not.
-
I will do further checking next week.
-
OK on the MAME 0.145u3. It now crashes on the ROM's scanning this time around. I believe this have something to do with the MAME changes that is braking the cmpro64 scanning.
I will say hold off on the cmpro fix until the 0.146 released. This will drive you nuts trying to fix this issue if they keep on changing something.
-
I can't repeat your issue and it seems that noone else can...
There is a known crash when cmpro adds rompaths for you for sysdefpaths...maybe you ran into that one..
you can try this build, it fixes *that* issue:
http://mamedev.emulab.it/clrmamepro/binaries/cmpro20120227.zip (http://mamedev.emulab.it/clrmamepro/binaries/cmpro20120227.zip)
-
Same issue. Let me rebuild some of the ROM's to see the problem go away. What I do is rename the folder to back up and then make a new ROM's folder (roms).
-
you should enable "ask before fixing" so it will prompt you the set before fixing it....and maybe *that* set causes the issue.
-
OK now I see what is going on now. It seem that the stuff have to be drop into the window scanning mode in order it to stop crashing. I don't see this will help on the CHD's when those can't be drop into it. Same thing as for samples. The zips have to be rebuild so it know those are there. Other wise crashes. Sad part is have to be done on every new MAME released.
I did check the Ask before fixing. The issue still there.
-
???
Can you explain again when it is crashing for you. When you drag'n drop files?
Again, this is used daily by a lot of people and noone reported an issue with it.
Tell me what you're doing and when and where it crashes.
-
It crashing at the beginning of the scan this time. Not at CHD's names. On the ROM's names. It check the ROM's then the CHD's.
But if I drop the ROM's into the Scan Results | MAME window and then it will go away because the ROM's are re-zip.
It like cmpro doesn't even see the zips and CHD's fully until after drop into that window and rebuild. Now CHD's the only problem because it can't be done this way.
-
Could it be the firewall?
-
Of course other programs can interfear but it should not cause cmpro to crash.
The start of the scan is the set-unneeded scan....it checks all files in all rompaths and checks if the found name matches a setname...
...something weird happens at this point on your system...of course it could be a cmpro bug but as long as I can't repeat it, I can't find it (as mentioned, it works fine here).
You can try a clean install and only copy set by set to your romfolder....copy one set, scan, copy another, scan..and so on...or 10 or 100...
-
Do you have some kind of debug tool or something that will help to show what is going on?
-
as mentioned, the best way to get it fixed is a repeatable issue within a minium environment. If that environment can then be compressed and uploaded somewhere, I can test it.
-
since it's most likely the unneeded or name check which crashes for you, you can e.g. turn it off and run a scan without it...to see if it still crashes...
-
What is e.g.? How I turn it off?
-
exempli gratia
-
OK I rescan the rebuild ROM's with the other cmpro. This one is clean installed into it own folder. No freezes and crashes. But if I replace the ROM's with the non-rebuild then it will freezes and crashes. Pretty weird.
-
try to minimize the amount of romsets to 1...and then, send me the file.
by the way, I just found one maybe related issue....some assertion during removal of files from zips....when I got a new build, I will let you know
-
I'm not sending the ROM's here.
Anyway here what the message said after I have just this ROM's by it self in the ROM's folder. This is the one that the cmpro crashes on. I did check for corrupted ROM's and it all are fine.
-
now 7z up your complete cmpro folder plus rompath with that one file and let me know where I can grab it....
-
This is the one that I use. http://downloads.sourceforge.net/sevenzip/7z920-x64.msi (http://downloads.sourceforge.net/sevenzip/7z920-x64.msi)
WinRAR as well. http://www.rarlab.com/rar/winrar-x64-411.exe (http://www.rarlab.com/rar/winrar-x64-411.exe)
OK I have a question. Where did you install WinRAR and 7-Zip at? Mine is in the C:\Program Files area.
-
This has nothing to do with cmpro. Install it wherever you want.
I asked you to send me a compressed version of your environment.
-
The ROM's? Old build and new build?
-
you said you made a clean cmpro install and you showed a screenshot where altbeast or something seems to had issues....so I assume you can repeat the issue with just 1 set in your rompath...
If you can, compress everything (program and rompaths) and send it.
If not, try to minimize your environment even more.
-
Sent through PM.
I:\MAME\roms
I:\clrmamepro\32
I:\clrmamepro\64
-
thanks...I will look at it tomorrow...nearly 3am here...need sleep
-
I'm doing checking disk right now. This be done over night.
-
I tried this out today and the scanning works. http://www.emulab.it/forum/index.php?topic=342.0 (http://www.emulab.it/forum/index.php?topic=342.0)
The bug is the "Mark disabled set as unneeded" checked. Seem broken here.
OK to everyone that have this problem going have to unchecked that box before scanning. Then enabled it for fixing. =/
Oh ya. Checking disk found nothing wrong on my Windows 7 and hard drive.
-
yep...that seems to cause it somehow....I can repeat your crash with your setup now...
So I take your setup, run scan -> crash
I start again, change the advanced option to keep not enabled sets as unneeded to disabled -> no crash
reenable that option -> no crash
now that's something to work with ;) Thanks for providing the files...guess it gets fixed today
-
Cool. I did a research on Google on the crash. Lucky that report found. :)
-
found and fixed