wonder why is not yet possible to download PS1 Libcrypt LSD package instead of SBI. I think that could be easily implemented feature for the redump community.
1 2023-08-02 14:44:08
Re: To Do: Redump.org Software Updates (14 replies, posted in General discussion)
2 2021-08-22 19:33:14
Re: [Resolved] Baldur's Gate region question (3 replies, posted in General discussion)
I have the same edition (along with others) and the problem is that latest dvd editions of bioware games are mutlilanguage while expansions are only in one language, so they made a mistake with these collections, in fact you can only mix games in english language if you're using discs from these boxsets. If you share hashes i can compare for you with mines.
3 2019-09-24 14:55:55
Re: About MODE1/2448 PlayStation (1 replies, posted in General discussion)
I've found while googling that suchannels are interlaced when burnt on the cds, so the true raw data differs from sub file that is deinterlaced, explaining what i've said in the previous post. Found also a smart tool from themabus that does what I wanted to do, it's called 2352to2448, it scrambles raw 2352 and 96 subs sector to sector (with interleaving or not). So i've been able to create a 2448 image.
I've done many experiments and found that alcohol is able to create such a file starting from a ccd/img/sub set, and results are identical in case of monotrack disc, while in mixed data/audio it eats 150 sectors from the first audio track and generates a mdf file shorter than expected.
Now i have to manage 2448 binary file, cuesheet doesn't seem to support this kind of binary well (at least this says alcohol when burning), even if contains MODE2/2448. What is the correct writing mode that can burn a set of cue/iso?
4 2019-09-23 05:17:47
Topic: About MODE1/2448 PlayStation (1 replies, posted in General discussion)
Hi everyone, i was wondering if there's possibility to use 2448 standard for PlayStation images. You well know that some ps1 europe games have libcrypt protection and a simple cue/bin in mode2/2352 couldn't handle the protection correctly. In recent homebrew scene of ps3 has been developed a payload by aldostools:
https://github.com/aldostools/COBRA/tree/master/485
It supports ps1 different image formats:
[ Aldo's changes ]
Improved PSX media type support, now it supports following disc types
2048 // 2352 // 2336 // 2448 // 2328 // 2340 // 2368 (PLAYSTATION and regular CD ISOs)
According to what seen on homebrew scene forums binary images are supported from ps3 backup managers only on single image binary (i think iso/bin) and works with metadata given by correspondant cue (i think with the same filename of the binary file in the same folder of the cue, and with the correct binary name into the cuefile). Also well known from you all that some games have libcrypt, some have multitrack entries (cd-xa), so there are games that have them both, and i wonder if it's possible to manage them correctly without applying that crappy hashbroker ppf patches for libcrypt.
I downloaded SBITools by Kippykip, a recent tool based on psxtoolz that uses lsd files in combo with cue/bins to generate a redump matching ccd/img/sub/cue:
https://github.com/Kippykip/SBITools/releases
The tool works awesome but again we have img binary and sub subcode files separated. I was wondering if it were possible to combine img and sub into a single file that could be mounted into ps3 games manager. Ps1 binaries have MODE1/2352 format, subcode is 96 format, so i thougth i could mix those two files togheter and obtain a MODE1/2448 binary+subcode that matches correctly the structure of ps1 cds. After some research i found that Alcohol 120% uses mds/mdf in 2448 without cue, so i thought that i could mount ccd/img/sub in alcohol and create a new mds/mdf in 2448 mode with correct settings for PlayStation, so i did it.
Then i checked mdf size and was effectively 2448xNumberOfSectors, so i thought i could copy that file and rename it as .iso, and try to generate a cue with ImgBurn. It detected the 2448 format and created the cuefile (MediEvil (Italy)):
FILE "SCES-01494.iso" BINARY
TRACK 01 MODE2/2448
INDEX 01 00:00:00
So to check all the things i used alcohol to see the sectors in search of libcrypt data, but i realised that subcode has a different pattern in iso than in sub (posted sector where first libcrypt sector should be and even is not there (?)):
Alcohol sector viewer
004000000000004000000000000000400000000000000040000000000000404000000000400000000000000000400040000000000000000000000000000040400000004000000000000000000040004040004040000040000040000000000040
ISO
004000000000004000000000000000400000000000000040000000000000404000000000400000000000000000400040000000000000000000000000000040400000004000000000000000000040004040004040000040000040000000000040
SUB
00000000000000000000000041010103080500031005B241000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Alcohol sector viewer shows licrypt Q formatted sectors and it matches the 41010103080500031005B241 from the sub, apparently the libcrypt sector seems to be shifted somewhere else than sector 14105. I can't understand how it works, but about a year ago someone on this forum told me that alcohol shifts something, however sector
14105 03:08:05 41 01 01 07 06 05 00 23 08 05 ff b8
is always present but in another location. In fact i found that sector 0 has MSF 00:02:00, so it's shifted of two seconds. why does sbi2sub shifts the msf of 150 frames? in fact the original cd has libcypt shifted in the same way, so i guess sbi2sub is making the right work.
The main thing i can't understand is the way subcode on the disc differs from the content of the sub file. is there a way to scramble img and sub (command line or little executable) into a 2448 iso file as a sequence of 2352,96,2352,96...? Or maybe i have to use alcohol to mount ccd/img/sub and generate a mds/mdf, then delete mds and edit cue to point to iso and force MODE1/2448? I'm getting mad!
5 2019-09-23 00:04:45
Re: UmdImageCreator (53 replies, posted in General discussion)
Do all psp UMDs have default layerbreak? Is there a sort of file like .dvd that stores layerbreak info? I'm working on my psp collection and reorganising to match redump checksums and being possibly closest to perfect dump, so i need to know how umd layerbreak works. In ps2 DVD9s layerbreak is not constant. Is there a tool that can verify if all psp dumps have the same layerbreak (or maybe if you know this i don't need such tool)?
6 2018-02-05 09:57:44
Re: Dumping, matching and burning (15 replies, posted in General discussion)
I think i'm understanding how all this works. The pregap on PS1 audio tracks is nearly always 2SS on audio tracks. Assuming that i decided to store my images in CCD/IMG/SUB if i have to do with a monotrack game the resulting img has the same size and the same checksum of redump. In case of multitrack games (assuming that all the games have 1 data track and X audio track each with 2SS pregap -but i read that is not always happening-) the resulting files are:
img > [redumptotalsize]+(2352*75*2*X) with inserted bytes between the tracks zeroed
sub > [redumptotalsize]/2352*96+(96*X) with bytes added in standard subchannel layout
ccd > LBA shifted of 150 sectors each track
However this is really complicated because to verify an image i have to create a custom cuesheet (because imgburn always uses a 00:02:00 pregap for the first audio track, setting 0 as pregap mode and deleting audio pregap from the generated cuesheet's first audio track), and convert cue/bin/wav into ccd/img7sub. The result is a img with the same total size of redump.org database, that could match. Then i have to create another cuesheet with 2SS pregaps and generate a ccd/img/sub that has the above specs for storing in my hdd.
Now this is the answer: if i dump an original ps1 multitrack disc the resulting ccd/img/sub has the same size of redump database or size is the one i said above [redumptotalsize]+(2352*75*2*X)?
If my burner shifts the audio of Y sectors (+6 in my case) the generated image from burned media won't match that of original disc?
7 2018-02-04 07:19:07
Re: Dumping, matching and burning (15 replies, posted in General discussion)
Tried burning disc http://redump.org/disc/5595/ Bugs Bunny: Lost in Time from a perfect dump, the result is the same for Alcohol 120% and CloneCD, the burned disc generated images matches both the redump CRC-32, so my problem is not this. I think the problem i have is what TossEAC said above, so the audio shifting gave by drive. I noticed that by mounting disc http://redump.org/disc/1130/ Castlevania: Symphony of the Night for generating a CCD/IMG/SUB to store in my personal HDD. Used Alcohol Virtual Drive to mount cue/bin (1bin with data and audio merged), or cue/bins (1bin for data, 1bin for audio) and i found that the resulting imgs for these two methods are the same, even if i merge with HexWorkshop the two bin tracks. So it seems that Virtual Drive does the same thing a burner does, shifting the audio tracks forwards or backwards. I manually deleted the resulting SLES-00524.img and used old merged CSOTN.bin renamed in SLES-00524.img to store in my hdd.
So is there a simple solution to mount/burn images without shifting audio tracks? I mean: i understand that a burner has its own audio correction offset called x, so to get a 1:1 copy i have to set a proper -(x) offset in burner software. Which burning software supports the setting of a custom offset to neutralize the drive one? Or do I have to manually do this for every track? For Castlevania is not a problem, but many games have high number of audio tracks, i could get mad doing this manually!
8 2018-02-03 05:23:15
Re: Dumping, matching and burning (15 replies, posted in General discussion)
Good news for us. Tried burning Grand Theft Auto: San Andreas v2.01 with Alcohol 120%. Here is the result:
ORIGINAL IMAGE CHECKED WITH REDUMP DB:
SLES-52541.iso
Sectors 2207136
Size 4520214528
CRC-32 13a51f88
IMAGE DUMPED WITH ALCOHOL 120% FROM DISC BURNED WITH ALCOHOL 120%.
ALCOHOL120.iso
Size 4520214528
CRC-32 13a51f88
Burned it with PlayStation2 profile on Alcohol 120%. No size and data mismatch, so it seems that my drive is working properly at least with dvd5 mode1/2048. Next one is a PS2 dvd9 game.
EDIT
Burned Metal Gear Solid 2: Substance v1.02 with Alcohol 120%. Dumped and still matches.
SLES-82009.iso CRC-32 0333ed63
ALCOHOL120.iso CRC-32 0333ed63
Next one: PS1 monotrack disc!
9 2018-02-03 02:58:23
Re: Dumping, matching and burning (15 replies, posted in General discussion)
Their is a problem when burning audio cds, your drive will adjust the files slightly to do with the drive offset, meaning when you read in your backup the audio will be slightly shifted by a few bytes, you can correct this, by working out how many bytes your burning drive shifts the audio on a burnt disc. Once you have that amount (x) you can adjust the audio by x but in the opposite direction before you burn, So when you burn and x is applied you get the audio exactly right. Then when you read your backups the audio will no be shifted.
According to DriveDiscOffset, mine has +6. Will it affect dumping or burning or both?
I think that is better starting with dvds for ps2, let's see what i get from those. I really don't want to waste cdrs and dvdrs, but also understanding what is the real problem. ps2 dvds are mode1/2048, so if my drive/support combination generates random errors in the burning process, they should be nearly always detected and corrected comparing to mode2 specs.
10 2018-02-03 02:56:42
Re: Dumping, matching and burning (15 replies, posted in General discussion)
http://wiki.redump.org/index.php?title=Setting_Up
What is the specific purpose of this cpp profile?
I'll start burning some ps2 dvd5 isos and see if this matches with crc after generating an iso from the burned disc. Gonna try with Alcohol 120%, ImgBurn. Any other burning software adviced?
11 2018-02-01 22:02:20
Re: Dumping, matching and burning (15 replies, posted in General discussion)
No possible way to properly preserve your PSX discs unless your own a supported Plextor drive that is compatiable with DiscImageCreator.
So it seems that i have to buy a Plextor drive. Is there any AIO solution by plextor that is bd/dvd/cd read/write capable and compatible with DIC? That’s because i own some ps3 bd games and i want to backup these in the future.
12 2018-02-01 16:58:59
Re: Dumping, matching and burning (15 replies, posted in General discussion)
If i remember correctly i’m having mismatch also in monotrack (data) ps1 games burned from matching imgs and cues burned with alchol or clonecd? Is my drive faulty? I don’t want to waste cdrs and dvdrs, so i need to be sure of what method i have to use. Let’s start with ps2 dvd5 isos that are for sure mode1 and less problematic: could alcohol120% manage the thing correctly? Or you advice imgburn for this purpose? Answer me so that i can burn something and verify the backups. Thanks for interestment!
13 2018-02-01 16:42:26
Re: Dumping, matching and burning (15 replies, posted in General discussion)
I was talking about desidered errors container into retail copies of ps1 games, such as dino crisis, syphon filter 2 and final fantasy origins. Clonecd corrects these sectors in read mode thus resulting in data mismatch with redump data. I avoided the problem just replacing the img with another one got on the internet that matched the crc, but only because i found it on the web. Could clonecd be configured to dump these games correct way? Or i just need to get another software?
Burning backups is another problem. Which software is the best? I want to generate a 1:1 copy of my dumps. I know that subchannels don’t have correction, but data and audio should have it, so if i’m starting from a perfect dump there is no reason in getting a shifted audio or mismatched data in backups. I created 4 different profiles in clonecd: psx standard (no libcrypt) with subchannels regenerating, psx standard with errors (no libcrypt and no data regeneration), psx libcrypt (no subcode regeneration) and psx libcrypt with errors (no sub regen and no data regen), however this method doesn’t seem to have effect, cause clonecd corrects data even if i configure it to not do so. EG i want to dump Dino Crisis that contains audio, libcrypt and errors. And then burn it. what should i do?
14 2018-02-01 05:18:00
Topic: Dumping, matching and burning (15 replies, posted in General discussion)
Hi, i'm not new to the world of redump.org, but now i have a strange problem. Basically i'm interested in preserving games for PlayStation and PlayStation2, so i decided to dump some games i own and make my personal backup for playing on that gaming systems.
PlayStation2 is not the real problem, burning softwares will manage correctly isos. Well, I decided to take a look at the dats and cuesheets and noticed that very very few games for this system use multitrack cdda (about 10 titles), so i eventually decided to use iso as file standard. in this case i had no problems with dvd9s, dvd5s and monotrack data cds (the ones with blue layer).
PlayStation is really a big problem because of multitrack cddas, tracks with errors, libcrypt protection, different versions and so on. Well, i decided to use ccd/img/sub (to make possible storing libcrypt protection) for all my psx backups, but i noticed differences on different software such as clonecd, alcohol120%, imgburn on pregaps, errors and cuesheets. monotrack cds with errour count=0 never gave me problems. for libcrypt protection i added it manually hexediting the sub file with sectors gave on redump instead of dumping from my discs (i tried also sbi2sub utility but seems to generate altered data in the last sectors of sub file, maybe it's the pregap?). so i create my monotrack backup files generating a bin with any software, then creating a cuesheet with imgburn, mounting the disc on a virtual drive, then create a ccd/img/sub from that with clonecd, last if libcrypted game editing sub with sbi2sub. So the data and the libcrypt is not the problem.
What exactly i have to do with cddas and error count different from 0? i read something about c1/c2 errors, compatible drives and so on, but i haven't understood. audio tracks are more sensitive to disc scratches, thus resulting in nearly always crc mismatch (only in audio tracks, first data track always matches). i tried discimagecreator but it's not compatible with my drive. is there any software able to perfectly dump each audio track after first data track without the need of getting a new plextor drive? If yes, maybe you can explain how to configure that, if it is alcohol, clonecd or imgburn?
After dumping i need to burn backups to play (i don't want to use original cds in my playstation), but i noticed that from a perfect dump my drive always generates a bad backup when redumped from burned copy (crc mismatch in img and sub). is it due to pregap and c1/c2 errors? i use clonecd at minimum possible speed (10x, 3x) and verbatim cd/dvv5/dvd9s
15 2013-04-29 16:34:41
Re: LibCrypt method two (4 replies, posted in General discussion)
well, it seems weird but --libcryptdrvfast generates only "regenerated" sectors. this means that it recognizes modified sectors (even correct number of modified sectors and their correct position) but outputs an "original" copy of modified sectors in sectors.log
-----------------------------------------------------------------------------
Medievil 2 (SCES-02545) (E-P-I):
MSF: 03:08:05 Q-Data: 41 01 01 03 06 06 00 03 08 06 66 89
MSF: 03:08:10 Q-Data: 41 01 01 03 06 11 00 03 08 11 67 d1
MSF: 03:13:10 Q-Data: 41 01 01 03 11 11 00 03 13 11 6a 9d
MSF: 03:13:15 Q-Data: 41 01 01 03 11 16 00 03 13 16 7d ae
MSF: 03:15:24 Q-Data: 41 01 01 03 13 25 00 03 15 25 b8 44
MSF: 03:15:29 Q-Data: 41 01 01 03 13 30 00 03 15 30 dd dd
MSF: 03:21:55 Q-Data: 41 01 01 03 19 56 00 03 21 56 4a b7
MSF: 03:21:60 Q-Data: 41 01 01 03 19 61 00 03 21 61 67 39
MSF: 03:24:12 Q-Data: 41 01 01 03 22 13 00 03 24 13 73 32
MSF: 03:24:17 Q-Data: 41 01 01 03 22 18 00 03 24 18 2e a6
MSF: 03:25:03 Q-Data: 41 01 01 03 27 04 00 03 25 04 04 fb
MSF: 03:25:08 Q-Data: 41 01 01 03 23 09 00 03 25 09 f4 2c
MSF: 03:32:19 Q-Data: 41 01 01 03 30 20 00 03 32 20 af 2f
MSF: 03:32:24 Q-Data: 41 01 01 03 30 25 00 03 32 25 dc dd
MSF: 03:33:56 Q-Data: 41 01 01 03 31 57 00 03 33 57 ad 9c
MSF: 03:33:61 Q-Data: 41 01 01 03 31 62 00 03 33 62 e4 d3
MSF: 09:20:45 Q-Data: 41 01 01 09 18 46 00 09 20 46 1e c2
MSF: 09:20:50 Q-Data: 41 01 01 09 18 51 00 09 20 51 1f 9a
MSF: 09:25:57 Q-Data: 41 01 01 09 23 58 00 09 25 58 35 14
MSF: 09:25:62 Q-Data: 41 01 01 09 23 63 00 09 25 63 52 3d
MSF: 09:28:71 Q-Data: 41 01 01 09 26 72 00 09 28 72 cb 7b
MSF: 09:29:01 Q-Data: 41 01 01 09 27 02 00 09 29 02 de fb
MSF: 09:30:68 Q-Data: 41 01 01 09 28 69 00 09 30 69 8a fd
MSF: 09:35:52 Q-Data: 41 01 01 09 33 53 00 09 35 53 71 77
MSF: 09:35:57 Q-Data: 41 01 01 09 33 58 00 09 35 58 2c e3
MSF: 09:38:04 Q-Data: 41 01 01 09 36 05 00 09 38 05 a6 ae
MSF: 09:38:09 Q-Data: 41 01 01 09 36 10 00 09 38 10 c3 37
MSF: 09:38:58 Q-Data: 41 01 01 09 36 59 00 09 38 59 a3 ce
MSF: 09:38:63 Q-Data: 41 01 01 09 36 64 00 09 38 64 69 a4
MSF: 09:46:13 Q-Data: 41 01 01 09 44 14 00 09 46 14 ef 3f
MSF: 09:46:18 Q-Data: 41 01 01 09 44 19 00 09 46 19 1f e8
MSF: 09:47:29 Q-Data: 41 01 01 09 45 30 00 09 47 30 7c fa
MSF: 09:47:34 Q-Data: 41 01 01 09 45 35 00 09 47 35 0f 08
Original sectors: 31
LC1 sectors: 0
LC2 sectors: 0
Other sectors: 33
while redump.org dump has for SCES-02545 http://redump.org/disc/1547/:
14105 03:08:05 41 01 01 07 06 05 00 23 08 05 38 39
14110 03:08:10 41 01 01 03 06 11 00 03 08 90 5d a0
14485 03:13:10 41 01 01 03 13 10 00 03 53 10 50 ec
14490 03:13:15 41 01 01 43 11 15 00 01 13 15 23 1e
and so on....
(doesn't matter 32/32 31/33 modified/original sectors)
-----------------------------------------------------------------------------
Medievil (SCES-01494) (I):
MSF: 03:08:05 Q-Data: 41 01 01 03 06 06 00 03 08 06 66 89
MSF: 03:13:10 Q-Data: 41 01 01 03 11 11 00 03 13 11 6a 9d
MSF: 03:15:24 Q-Data: 41 01 01 03 13 25 00 03 15 25 b8 44
MSF: 03:20:56 Q-Data: 41 01 01 03 18 57 00 03 20 57 86 56
MSF: 03:23:17 Q-Data: 41 01 01 03 21 18 00 03 23 18 79 d1
MSF: 03:25:03 Q-Data: 41 01 01 03 23 04 00 03 25 04 04 fb
MSF: 03:33:56 Q-Data: 41 01 01 03 31 57 00 03 33 57 ad 9c
MSF: 03:34:51 Q-Data: 41 01 01 03 32 52 00 03 34 52 89 19
MSF: 09:20:45 Q-Data: 41 01 01 09 18 46 00 09 20 46 1e c2
MSF: 09:25:57 Q-Data: 41 01 01 09 23 58 00 09 25 58 35 14
MSF: 09:28:71 Q-Data: 41 01 01 09 26 72 00 09 28 72 cb 7b
MSF: 09:33:37 Q-Data: 41 01 01 09 31 38 00 09 33 38 78 7f
MSF: 09:37:14 Q-Data: 41 01 01 09 35 15 00 09 37 15 6e 1b
MSF: 09:38:58 Q-Data: 41 01 01 09 36 59 00 09 38 59 a3 ce
MSF: 09:47:29 Q-Data: 41 01 01 09 45 30 00 09 47 30 7c fa
MSF: 09:48:59 Q-Data: 41 01 01 09 46 60 00 09 48 60 ed e3
Original sectors: 48
LC1 sectors: 0
LC2 sectors: 0
Other sectors: 16
-----------------------------------------------------------------------------
As you could clearly see, i get the same sector from different games, it's like the drive corrects subchannels for itself, while months ago it worked well! BTW i'm using psxt001z v0.21-b1 and Slimtype DVD A DS8A5SH ATA Device. Any suggestion?
16 2013-04-23 13:16:46
Re: LibCrypt method two (4 replies, posted in General discussion)
--libcryptdrvfast is better
i know that method but for some reason it doesn't recognize sectors as libcrypted, but modified (sometimes even misses some of the 16-32 sectors, as result i got 31/32/33 modified sectors), i tried to clean lens disc and so on, no way... i can't really understand how to get the correct Sectors with LibCrypt protection table:
Sector MSF Contents XOR Comments
14105 03:08:05 41 01 01 07 06 05 00 23 08 05 38 39 8001 c701 LC1 sector, no errors in data & CRC-16
...
44059 09:47:34 41 01 01 09 05 34 00 09 45 34 35 79 8001 8c73 LC1 sector, no errors in data & CRC-16
Total: 32 sectors
I can't believe everybody have discs in perfect conditions, there should be a working method to get a correct subchannel dump from a slightly used psx libcrypted disc... Maybe the main problem is that i'm using a slimtype dvd...
17 2013-04-21 15:53:51
Topic: LibCrypt method two (4 replies, posted in General discussion)
PSXtools makes nothing when i run this (no sectors.log output, CPU idles):
"C:\psxt001z.exe" --libcrypt "C:\1.sub">sectors.log
1.sub and psxt001z.exe are actually in the root, and i'm running psxt001z v0.21-b1
sub was generated by clonecd last version, without any issue, gamecd profile
any ideas?
18 2013-01-27 18:24:17
Re: About Libcrypt sectors (3 replies, posted in General discussion)
I understood how it works, actually i patched manually with HexEdit some games like FFVIII or CTR, but what about dumping correctly subchannels (even if they haven't ECC)? The thing i can't really understand it's how same discs have different subchannels dumped on same drive (i own 3 CTR discs, one is black label, two platinums). The infos that are shared on http://redump.org/disc/897/ are for sure correct, now i own several discs that are missing in the list, so how can i obtain correct libcrypt sectors as on redump page infos?
p.s. i always receive modified sector when i am supposed to receive LC1/LC2 sector from libcryptdrvfast command!
19 2012-09-19 16:43:15
Topic: About Libcrypt sectors (3 replies, posted in General discussion)
I own both CTR Original & Platinum, why are my sectors.log dumped from original discs different from sectors found in Discs>PlayStation section?