1 Topic by Lorem__Ipsum (edited by Lorem__Ipsum 2013-08-23 01:11:13)

  • Registered: 2012-10-29
  • Posts: 8

A few of them.

1. What is the significance of the EXE file date? Why take note of the date for that specific file? I don't see what relevance it has to anything.

2. Why use the Local Time Stamp option in IsoBuster? I've read IsoBuster's explanation of these two options (Local and Relative) several times, and I just can't understand what it's saying. Does Local tell me what time it was in the location the disc was made, and does Relative tell me what time it was in my location? If not, I can't understand it.

3. I have it set to Local, but I don't always match up with the database. Take Forever Kingdom USA for example, my file date says 2001-12-04, I'm pretty sure the database says 2001-12-03. So who did it wrong, me, or the other submitter(s)?

EDIT: Addition to this question, sometimes it doesn't match up at all. Take Orphen: Scion of Sorcery USA for example. We have 2000-08-17, I have 2000-09-03.
http://img854.imageshack.us/img854/6831/59xd.jpg
I used the SLUS_200.11 file, the database is currently using the SYSTEM.CNF file which POINTS to the SLUS_200.11 file. That's a no-no, right? Just checking to see I'm doing it right.

  • From: Sevilla - España
  • Registered: 2011-05-16
  • Posts: 1,006

1: Maybe to document the build date/time of PS1/PS2 discs, like the header of Mega-CD/Saturn games.

2: We have to use the local time stamp so that any user can report the same date/time for a given disc. If not, users from different time zones would report different dates/times for a given disc.

3: Exe date must be taken from the SLES/SCES/SLUS/SCUS/SLPM... file, not from the SYSTEM.CNF file.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot
  • Registered: 2012-10-29
  • Posts: 8

Okay, 2 and 3 were answered perfectly, thanks. I still kind of don't understand the answer to question 1, since I don't really know what you mean by build date. My best assumption is that it's when the disc was "completed" so to speak, but in most cases the system EXE file is not the file with the latest time stamp on the disc. I guess that, in my mind, for a disc to be "built" with files created after the disc was built is chronologically impossible. The disc would have had to go into the future to get those files tongue And that probably just shows you how little I know about the whole thing.

  • From: Sevilla - España
  • Registered: 2011-05-16
  • Posts: 1,006

I mean the build date of the executable file of the disc.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot
  • Registered: 2012-10-29
  • Posts: 8

Honestly, I may resort to using that date to organize my PS2 game collection. Originally I'd wanted to do release date, but that information is inconsistent across the web, and some of the dates are just downright silly, like Q-Ball Billiards Master being released in February 2000. Not only is that 8 months before the PS2 was even released, but it's 7 months before the EXE date on the disc. THAT disc really WOULD have had to go into the future like I joked. So then I had the idea to arrange by latest file date on the disc (the date the disc was "completed"), but that seems to be impossible to determine due to hidden files. So, maybe I'll use the EXE dates. Alphabetical order is just so... boring.

Well, thanks again pablogm123.