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] 2 3 4 5 6 ... 10
 1 
 on: Yesterday at 04:51 
Started by vikbez - Last post by Stiletto
Sorry, missed this.

If you still have the original hardware, some general advice:

- photograph or scan every PCB, good enough to read all the component numbers and printing. If you cannot, jot it all down by hand. An exact motherboard model name and number *may* be good enough.

- dump ANY firmware: motherboard BIOS, video card BIOS, and any other ROMs

- get a list of every component inside the PC, period. Exact manufacturers and model numbers.

- instead of just copying the game files, image the hard drive (if it is still pristine and untouched by you), if via a USB adapter ideally with a write-blocker like "thumbscrew" to prevent whatever host OS you interface it with from writing back to it (Windows 7+ is known to do this for certain). Make a note of the CHS settings in the BIOS and get the exact make and model number of the drive. Linux "dd" can work to make an image. Or WinHex (registered) on Windows. These days we also want to get the ATA ID string when we can.

- also, make a note of the CMOS settings.

The security dongle, if it contains a ROM, will need to be dumped. At the very least, an attempt to disassemble it. Hopefully it is not filled with epoxy.

The button input board might also have a ROM on it or a microcontroller that has internal ROM which will need to be dumped. Unlikely based on your description but we'd need to see.

Some tutorials:
http://www.citylan.it/wiki/index.php/How_to_correctly_document_a_PCB
http://www.citylan.it/wiki/index.php/Dumping_roms
http://www.citylan.it/wiki/index.php/Taking_pictures_and_other_medias

For more in-depth advice you will want to contact The Dumping Union. The best way is via Smitdogg at MAMEWorld: http://www.mameworld.info/ubbthreads/showprofile.php?Cat=&User=2

 2 
 on: Yesterday at 04:05 
Started by Worluk - Last post by Stiletto
Added your image and notes to https://mamedev.emulab.it/undumped/index.php?title=Voyager_(Tehkan) and https://mamedev.emulab.it/undumped/index.php?title=Voyager.

 3 
 on: 12 June 2019, 09:42 
Started by Roman - Last post by Roman
I may think about a quick way to detect changes on startup (e.g. looking and comparing at the last write date of the datfiles folder ) and doing a refresh then......but currently I have zero time for cmpro coding

 4 
 on: 12 June 2019, 09:38 
Started by Roman - Last post by f205v
aha! OK, I didn't realise there are people with thousands of datfiles. I only have a few dozens. Of course for them it would be annoying!
I'll use the drag-and-drop going forward.

 5 
 on: 12 June 2019, 09:35 
Started by Roman - Last post by Roman
Yes of course something changed.
People with 1000000000 datfiles were pretty annoyed that during startup it took ages to run through all datfiles. Even if no new ones were added.
Cmpro now caches the data and reloads the cache only (plus auto refresh when new datfiles were added correclty and not manually).

If you use the official way to add datfiles (drag'n drop, add button, www profiler), it acts like before.

 6 
 on: 12 June 2019, 09:27 
Started by Roman - Last post by f205v
OK, thank you for explanation.
But something has changed never-the-less, because with the regular build (using the same procedure) there is no need to hit refresh, it does it by itself.
You can clearly see it: when you launch regular build first things there is a percentage bar called "looking for datfiles.." that pops up, and after that it goes to profiler screen.
With nightly there is NO percentage bar, and the program goes straight to profiler.

 7 
 on: 12 June 2019, 09:18 
Started by Roman - Last post by Roman
As I said, you need to add datfiles via drag'n drop (in the profiler window) or www profier or the add button.
If you do what you do (copying them manually while cmpro is closed), you need to click the refresh button

 8 
 on: 12 June 2019, 09:17 
Started by Roman - Last post by f205v
well, I usually add datfiles when cmpro is CLOSED! I put them in the datfile directory, open cmpro, and it goes automatically through refresh.
The nightly build doesn't do refresh by it's own, I'm forced to press the refresh button.

I've just done a clean install on a different disk on my PC: first downloading the official build, and it works correctly, after I downloaded the nightly and overwrite it to the regular build, and it doesn't perform the refresh. All the rest is working fine.

 9 
 on: 12 June 2019, 09:07 
Started by Roman - Last post by Roman
hmm....weird...works fine for me....how do you add new datfiles? (if you only put them manually in the datfiles folder you have to press "refresh". If you add them via drag'n drop or the add button it should work fine

 10 
 on: 12 June 2019, 08:54 
Started by Roman - Last post by f205v
hi Roman,
I'm using your latest nightly build post here, and I have a problem.
Each time I open cmpro64.exe it goes to "profile" windows (as I set it in options), but it does NOT refresh list automatically as it did in the past. I'm forced to hit the "refresh" button after launching the program, other wise new datfiles will not be seen and already existing ones will not work.

Pages: [1] 2 3 4 5 6 ... 10

Page created in 0.12 seconds with 18 queries.

anything