101

(22 replies, posted in News)

69 more dumps at the moment in 24 remaining days... that's about 3 discs per day. We can do that big_smile

102

(4 replies, posted in General discussion)

Thanks, that's the kind of statement I was waiting for big_smile

103

(4 replies, posted in General discussion)

All right, I think IsoBuster would have worked just as fine for your dump. The CRCs wouldn't have matched, though, because ddump fills erroneous sectors with 55, IsoBuster with 00. So I wonder which of these methods is officially suggested; I don't want the database to be flooded with duplicate dumps just because of how different programs handle corrupt sectors differently.

104

(4 replies, posted in General discussion)

Hi,

I've come across a PC disc protected with LaserLok (v5, if that matters). What is the proper way to dump this? It contains corrupt sectors, as it seems. Should I read it with IsoBuster and replace the unreadable sectors with zeroes? Or is it better to use ddump, which I believe overwrites unreadable sectors with 55's?

I guess there is no way (and it won't make much sense) to recover the actual data inside the sectors, is there?

Thanks smile

If the disc itself is valid (i.e. not burned and dumped correctly) I think it should be added to the database, regardless how negligible the differences to other editions of the same game may seem. Yes, even if that means we'd have 20+ versions of the same game in the DB.

But that's not even the topic; I'd still like to know how to add these magazine discs.

Hi,

I have a bunch of PC gaming related magazines with discs. Some of the discs contain only demos and videos and some contain full versions. How should I add this stuff? Are the demo discs relevant at all or should I just dump the full versions?

Furthermore, how do I name such a disc? After the magazine+issue or after the game that's on it? The latter could be problematic since there are even discs with multiple full versions, I think.

Well, it may not be that complicated but you can make horribly many mistakes, especially with the gaps (which EAC more often than not fails to detect properly). Furthermore, you'll need a drive capable of overreading - many people probably don't have one.

But anyway, this discussion does not really belong here smile

.

After all, this project used to be PSXDB smile I think most people focus on dumping whatever can be dumped the easiest way, which would be single track PSX, PS2 and (non copy-protected) PC discs. Just wait until all these "low hanging fruits" have been grabbed and you'll actually see some of the more interesting, harder-to-dump stuff appear ^^

It's quite similar to the MAME's situation, where basic, widely available games like Pacman or Space Invaders were taken care of at the beginning of the project, leaving the more obscure stuff for today.

110

(4 replies, posted in General discussion)

It varies indeed. I've pakkiso'd many PS2 isos lately and some games just can be compressed incredibly well due to huge dummy files on the disc. Metal Slug 4, for example, compresses to about 2% of its uncompressed size. Disc 3 of Metal Gear Solid 3, on the other hand, stays 94% the size of its uncompressed counterpart.

If I were to estimate I'd say that on average PS2 games can be compressed some 40-60% with PakkIso (or plain 7zip, of course).

A) In EAC you enter the value from the sector view, which in this case is +8. This is called the combined read and write offset.
B) You submit just the write offset, which can be determined as follows: write offset = sector view - drive offset. In this case it's +8 - +6 = +2.

Edit: Screw it, Rocknroms beat me to it smile

112

(6 replies, posted in General discussion)

If the data track was 7-zipped & ecm'd and the audio tracks were in ape format, the game was most likely compressed with PakkISO. To uncompress it, simply un-PakkISO it smile By dragging the game's folder onto unpakkIso.exe it decompresses the 7-zip with the data track, unecms it and converts the apes to bin which you can easily burn afterwards.
Hope I could help smile

Wouldn't it be enough to upload checksums of the MDS file? Every dumper with access to the disc could easily make them himself, and redump.org wouldn't have to risk legal problems. On the other hand, I don't know if the MDS files are consistent, i.e. if the same disc dumped by several dumpers yields the exact same MDS file.

114

(19 replies, posted in General discussion)

It is possible and also very reliable. You'll need a "special" drive, though, like the LG 8164b (or the 8161-8163b, as far as I know; other drives have been reported to work as well, though). Then you need friidump for the actual dumping process. Search for friidump 0.4 since earlier versions can't dump dual layer Wii discs properly AFAIR. Just give it a try, it's not very hard if you've got a compatible drive big_smile

115

(5 replies, posted in General discussion)

Actually this information is already available in the recent changes rss feed. Try to open it in Opera or IE; Firefox doesn't seem to recognize the relevant "author" (which is in our case the mod who changes/adds something) field.
Inconveniently, you'll have to update it regularly so you won't miss any changes. A more permanent solution - maybe a "changelog" on the dump page itself - would definitely be advantageous.

116

(8 replies, posted in News)

Congratulations big_smile
I sure hope progress won't slow down once PSX gets close to completion. There's plenty of other systems which are IMO being neglected somewhat. Maybe the obscurer systems are being added to TOSEC rather than redump, who knows. Well, still it's an impressive effort which I'm proud being part of big_smile

http://www.emulab.it/forum/index.php?topic=96.0

Now that's some great news big_smile My files are being scanned correctly now big_smile

I see you've managed to rip that 5th volume as well - congratulations big_smile

Oh well, it looks like I got my hopes up too soon sad

I guess I'm lucky big_smile Roman investigated the problem and according to him, the new version of the 7z SDK fixes the problem big_smile I hope he'll release a new version soon.

Then it would be the best to contact Roman directly and write a 'bug report' on the clrmame forums

Just did that smile

4gb is exactly limit of addressing with 32-bit...
but I assume you are using 64-bit version cmpro64.exe ?

I'm using 64 bit clrmamepro and 64 bit 7-zip.

if so, the only solution would be replace lzma compressor within clrmame with newer one that supports large files

How would I do that? Does such an updated compressor even exist? sad

I'm quite sure there were only 7 of them [source].

Extracting them directly via 7-zip works like a charm. The files don't seem to be corrupt - I've dumped and packed the games myself. Also, the problem occurs with all 7-zipped isos >4 GB I have, also the wii ones! This means ~10 files which all happen to be >4 GB would have to be corrupt smile And no, I'm not on FAT, I use Vista64 on an NTFS partition.
Good ideas so far, but I guess either clrmamepro or its implementation of 7z is the culprit smile

So I'm not alone smile Man, I'd love to use RomCenter anyway, if only it could read 7z...

Hi,
like many of you, I use clrmamepro to rename and check my roms/isos. I think my version is quite up-to-date (3.123); I can't check that though since the official page seems to be down. Anyway, I'm having trouble reading files over 4 GB. All my isos are 7-zipped, so the bug might be related to this? When I scan my PS2 folder, for example, I get this warning:

Corrupt Archive File:C:\Emulation\Dumps\Sony Playstation 2\Champions_E.7z | Reason: NO ENTRIES
Corrupt Archive File:C:\Emulation\Dumps\Sony Playstation 2\God of War.7z | Reason: NO ENTRIES

Both the compressed and uncompressed files are well over 4 GB. Does anyone have the same problem? Are there maybe newer versions of clrmamepro fixing this?