1

(4 replies, posted in General discussion)

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.

2

(4 replies, posted in General discussion)

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.

3

(4 replies, posted in General discussion)

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.

4

(9 replies, posted in General discussion)

...and I assume there's no way to get around that =/

Well, that certainly looks to be the case, anyway. Thanks a lot for all the input, you sure helped out.

5

(9 replies, posted in General discussion)

Are you sure that the problem is with hidden files? You've tried FFX on your setup and it shows more than 13 files? If so, I need to find out how to get my system to show hidden files, or try Winhex.

6

(9 replies, posted in General discussion)

Hidden files and system files are enabled, and still nothing. This is a very odd case indeed. Can anyone copy the files from the Final Fantasy X disc / image successfully?

7

(9 replies, posted in General discussion)

Ah, okay, I'll have to hop onto my girlfriend's Windows 7 computer and try this out. Thanks. And what's the difference between the file systems? In IsoBuster's explorer, all the same files appear in both file systems. Is there some difference in extracting them from the UDF file system vs. the other file system?

EDIT: Okay, so this gets even stranger. I'm on a Windows 7 computer now and I create an ISO file of Final Fantasy X, hash check it, okay, it matches up with Redump. Then I mount it with DAEMON Tools and open it in Windows explorer and I get 13 files whose total file size added together is 5.03MB. Yet the ISO is 4.19GB like it should be. I really just don't understand it. It doesn't make any sense.

8

(9 replies, posted in General discussion)

When ripping Final Fantasy X to my drive, I encountered an odd discrepancy in the size of the files vs. the size of the disc. The size of the disc should be just around 4.2GB, and if I simply create an image of the disc from Track 01 then I'll get that. But if I right-click on FINAL_FANTASY_X under Track 01 and do Extract, the resulting files I'm given barely scratch 5MB in total. Final Fantasy X is currently the only disc giving me this problem after about 20 or so discs, CD and DVD. Does anybody know why IsoBuster is behaving so oddly?

Also, I know it's weird to extract to files. I'm doing it for a personal project and just want to know if I'm doing something wrong before I continue on. I'm using the "registered" version of IsoBuster 3.2 ("registered" meaning it still bugs you for a key and tells you that you can't do certain things without registering). It also happened on 3.0 "registered", which is what caused me to update. I'd appreciate anyone's insight on this, I have no idea what's going on.