EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: scan status not saved  (Read 7056 times)

donnyj

  • Karma: 0
  • Offline Offline
  • Posts: 43
  • Operating System:
  • Windows Vista Windows Vista
  • Browser:
  • Firefox 3.6.3 Firefox 3.6.3
    • View Profile
scan status not saved
« on: 09 April 2010, 08:35 »

Newest version 3.133

When I do a "new scan", switch profiles, then go back to the first profile, my only choice is a "new scan" and not just "scan"
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 113
  • Offline Offline
  • Posts: 3292
  • Operating System:
  • Windows XP Windows XP
  • Browser:
  • Firefox 3.6.3 Firefox 3.6.3
    • View Profile
Re: scan status not saved (edit)
« Reply #1 on: 09 April 2010, 09:24 »

Not repeatable here.

Sounds a bit like cmpro wasn't able to save/load the fastscan information in the belonging cmpro fastscan folder. Be sure you:

1) got enough free diskspace
2) got full access rights for the cmpro folder and subfolders
3) did not install cmpro in an UAC controlled folder (Vista/Win7 only)

So you can monitor it a bit by looking in the fastscan folder (or its subfolders) to see if the belonging .fsc is written after a scan. That file holds information about which sets need a rescan *and* it also holds a checksum over the used datfile/mame import. So if the datfile/MAME import changed in the meantime for the used profile, you won't be able to do a SCAN without first doing a NEW SCAN.

Like: Scanning MAME .137u1, then updating to .137u2 -> You need to do a NEW_SCAN
Doing a NEW SCAN for MAME .137u1, loading a different profile (e.g. MESS), then loading MAME .137u1 again -> SCAN (not only NEW_SCAN) should be available.
« Last Edit: 09 April 2010, 13:08 by Roman »
Logged
Pages: [1]   Go Up
 

Page created in 0.155 seconds with 19 queries.