|
|
Post by Haldrie on Oct 9, 2007 13:29:11 GMT -5
Yeah that would help a bit as I use the swap trick that uses an actual PSX CD to boot a copy so I don't think just burning that file to a CD won't work. I did manage to hack my copy of Tomb Raider (Greatest Hits) by padding your program and overwriting the TOMBRAID.EXE file with it so that when I choose "Start Game" instead of Tomb Raider starting it loads your program which I must say works great.
|
|
ShendoXT
Full Member
Prototype
Posts: 124
|
Post by ShendoXT on Oct 9, 2007 13:56:23 GMT -5
When the cd lid is closed (with cd in off course) psx first searches for a SYSTEM.CNF file on a disc.
If the file is not found psx checks for psx.exe.
As the psx.exe is present swap method, with PSX CD you mentioned should work.
But I'm glad that you got it working with your own way.
Post if you need any help with dumping.
|
|
|
|
Post by Haldrie on Oct 9, 2007 14:19:42 GMT -5
Well I guess I could try that. That would explain how the codebreaker and gameshark games work without a serial file. Anyway I figured out by comparing downloaded bios I had to the parts that I got from your program what parts I had to remove to get the true bios data so below is checksum info for the PSX and PSOne consoles I dumped the bios for with shendo's program. There is no text representation in the files to be able to tell the difference between them (by just viewing them in notepad they look almost identical) so I feel checksum info is the best way to identify them.
SCPH101
Console Type: PSOne
Region: US
Size: 524288 (512KB)
CRC-32: 171bdcec
MD5: 6e3735ff4c7dc899ee98981385f6f3d0
SHA-1: dcffe16bd90a723499ad46c641424981338d8378
SCPH9001
Console Type: Original PSX (with serial I/O)
Region: US
Size: 524288 (512KB)
CRC-32: 502224b6
MD5: 1e68c231d0896b7eadcad1d7d8e76129
SHA-1: 14df4f6c1e367ce097c11deae21566b4fe5647a9
Hopefully someone can find this info useful.
|
|
ShendoXT
Full Member
Prototype
Posts: 124
|
Post by ShendoXT on Oct 9, 2007 14:41:49 GMT -5
Reread the first post by Gamesoul Master, he explained how to find relevant data. In my gude I explained where the data is stored, so you didn't have to compare it to the existing BIOSes. As I sad already I'm glad you got everything working  |
|
|
|
Post by Haldrie on Oct 9, 2007 14:52:22 GMT -5
Oh ok I found it now. Well since the SCPH101 info has been posted I'll post the SCPH9001 info.
SCPH9001
CEX-3000/1001/1002 by K.S.
System ROM Version 4.1 12/16/97 A
|
|
|
|
Post by Gamesoul Master on Oct 10, 2007 21:23:02 GMT -5
Actually (as a note to everybody), feel free to list the information for any BIOS that I haven't listed as "verified", because as far as I know, the current list (except for one entry) was made using downloaded BIOS images. So at this point, any information that needs to be verified or isn't on the list would be greatly appreciated...  |
|
|
|
Post by Haldrie on Oct 16, 2007 14:06:52 GMT -5
Well in that case I can say that my SCPH-101 is verified.
|
|
|
|
Post by Gamesoul Master on Oct 16, 2007 20:09:15 GMT -5
I'm assuming that, one way or another, you mean that your SCPH-101 matches up with what's on the list. Either way, I'll put it down as verified... |
|
vigi
New Member
Posts: 2
|
Post by vigi on Oct 17, 2007 17:38:10 GMT -5
Hi, first of all I'd like to thank shendo for this terrific tool. I waited a very long time for being able to dump the bios from my SCPH-102. Now that I did, I can confirm that it contains the following strings: Sony Computer Entertainment Inc.....CEX-3000/1001/1002 by K.S System ROM Version 4.4 03/24/00 E.Copyright 1993-2000 (C) Sony Computer Entertainment Inc It also matches the checksum of the 4.4 dump by the MESS project. A lot of the bioses have already been dumped by them. Maybe it's good to add all their dumps and checksums to the first post? I'm a dumper for the Redump.org project (previously PSXDB). We included a clrmame bios datfile (info taken from MESS psx.c notes: mess.dorando.at/svn/?rev=867) which has all bioses listed that are currently available: redump.org/datfile/psx-bios/This is the bios that I dumped myself: game ( name "psone-44e" description "SCPH-102 (Version 4.4 03/24/00 E)" rom ( name psone-44e.bin size 524288 crc 0bad7ea9 md5 b10f5e0e3d9eb60e5159690680b1e774 sha1 beb0ac693c0dc26daf5665b3314db81480fa5c7c ) ) Also, here's another list by F1ReB4LL: f1reb4ll.dremora.com/ps1bios_mess.txtGrtz |
|
|
|
Post by Sune on Oct 17, 2007 20:10:46 GMT -5
Can you tell me why the naming convention in the datfile was changed?
To me, names like "psxe20" are completely useless. I have no idea what BIOS that is.
I like names the like "Sony PlayStation BIOS (E)(v4.1)(1997-12-16)[SCPH-7502 + SCPH-9002].bin" that the old .dat file generated.
|
|
|
|
Post by Gamesoul Master on Oct 17, 2007 21:12:59 GMT -5
vigi: In that datfile, am I to assume that all the models listed under "description" are all the models that bear that exact BIOS version? And... by no means am I meaning to disrespect you or the group, but... are the results credible? Either way, thanks for your contribution...
|
|
vigi
New Member
Posts: 2
|
Post by vigi on Oct 18, 2007 5:36:40 GMT -5
vigi: In that datfile, am I to assume that all the models listed under "description" are all the models that bear that exact BIOS version? And... by no means am I meaning to disrespect you or the group, but... are the results credible? Either way, thanks for your contribution... That's correct. I think most of the new bios dumps from MESS come from smf, who has done a lot of work on the PSX hardware drivers in MAME also. He mentioned on MESS forums that he had his own tool to dump the bios to memcard. I assume it has the same functionality as shendo's tool. I'm pretty sure that all their info is correct and that dumps can be trusted, but of course there's no harm in verifying them with our own dumps. Sune, I understand your criticism, but we thought the previous filenames were just too long. Also, we thought that the MESS filenames made more sense than the scph***.bin filenames. We might change the filenames again whenever we get to update the datfile with new bioses. |
|
|
|
Post by Sune on Oct 18, 2007 17:30:16 GMT -5
Sune, I understand your criticism, but we thought the previous filenames were just too long. Long, yes but at least they were "descriptive"...which can not be said about the MESS filenames. I didn't mean to come off as rude in the previous post, just stating my opinion. |
|
|
|
Post by Gamesoul Master on Oct 18, 2007 19:00:42 GMT -5
I agree though... as much as I don't like having extremely long filenames, they really need to mean something more than a name that means almost nothing. A filename containing the version (or date) and the console(s) the BIOS is on would be a lot more beneficial to everybody, without making the filename too long.
|
|
ShendoXT
Full Member
Prototype
Posts: 124
|
Post by ShendoXT on Oct 21, 2007 10:26:46 GMT -5
To me, names like "psxe20" are completely useless. I have no idea what BIOS that is. Although the name seems a little strange it makes sense. (psx - the console, e - region, 20 - version) In my opinion it would be great if people would accept that naming scheme. Naming a BIOS after a model is not good as different models can have same bioses and same models can have different bioses. |
|
