ROMLister Help Needed: Rom Scan crashes

[P.H.U.]

Hey NOP,

I have never been able to get ROMLister to work. The strange thing is that I have attempted to use it on two different computers; one running Win7 x64, the other running XP 32-bit. My initial attempts were on the Win7 machine. But after reading that ROMLister runs better in XP, I tried in XP without any luck. In every instance, it crashes the moment I run Rom Scan (after specifying the roms dir and specifying the save location of the subsequent file). Below is the screenshot.

My roms set for MAME is not complete but is still pretty hefty at around 165GB. I am able to successfully create the merge file. But can not get any further. Is there something I am doing wrong? Note that I am scanning from an external drive connected via USB. On the XP machine, I was sure to install dotnet framework prior to the attempt. If it makes any difference, both systems I used were Dell laptops.

Help?!

[P.H.U.]

Here is the error from Win7's report, if it helps any.

Code: [Select]

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: RomLister.exe
  Application Version: 1.0.0.1
  Application Timestamp: 534abc18
  Fault Module Name: ntdll.dll
  Fault Module Version: 6.1.7601.17514
  Fault Module Timestamp: 4ce7ba58
  Exception Code: c0000005
  Exception Offset: 000222c2
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Information 1: f2bb
  Additional Information 2: f2bbd34b964449eec8d3bfe2cbc6c36f
  Additional Information 3: a9ca
  Additional Information 4: a9caaf0f330b1f98e98a5c1a2028cac7

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


[P.H.U.]

Cancel the cry for help here. I somehow got Don's HyperSpin Tools to work (finally). Strange that ROMLister never worked for me, but I was able to complete the task using an alternative.

Thanks!

[Slippyblade]

165gb??  What the heck?  I thought the entire .149 romset was only 40gb-ish...  Are you including CHD's or something?

[NOP]

even though you have a solution here, I'd still like to try and debug it.  (the info above is no help)
Question for you though: are you trying to scan a full rom set?  If so, there really is no need to do such a thing.
the rom scan tool is where you turn to when you have say, 40-400 roms that you've culled from a full rom set that you have on your machine.
You scan those roms against the input XML file, and romlister discards any game entry in the XML that does not match a physical file.
when it is done, you now have an XML file that matches your smaller collection of roms.  You can then output that list to another format for example, which is how people can move from one FE to another without losing their game list.

if you're scanning against a complete rom set, then all you're doing is spending a lot of time and energy re-creating a full XML file.

Does that make sense?

[P.H.U.]

Yep, completely understood. My roms directory includes the CHD's, yes. I have the full set for 1.49 and it is close to 200 gigs, which I have tucked away in safe storage on my NAS. I transfered that set to a local machine and made a half-hearted attempt to delete some roms (and the CHD's) and got down to 160gigs. Then I went through the steps to Rom Scan against those roms (and CHD's) and that is when I encountered the errors.

What would you like me to do to produce a troubleshooting log so you can debug this?

[NOP]

here's a test version of romlister which outputs a few message boxes as to what step in the rom scan tool it is in.
let me know which step it crashes on.  ie, let me know what the last message says.