Forum: IDE HDD Discussion - Discussion about the use of the IDE HDD Interface and hdloader related discussion.


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: GI files to ISO?
  

Results 1 to 2 of 2
  1. #1 GI files to ISO? 
    mrm83 is offline Registered User
    Join Date
    Nov 2003
    Posts
    20
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    hi
    i got these 3 GI files, and they are around 4gig in size
    and in the readme file that came with it, it says to use this command to get them into ISO form

    Copy /B x.GI + x.GI + x.GI [destination].iso

    i did that, and i got the iso file thats 4+ gig.. but when i open it up, the files inside are only 4MB??

    is it suppose to be like that?? cuz i need the iso file to put onto the HDD..
    Reply With Quote  

  2. #2  
    dlanor is offline Member
    Join Date
    Sep 2004
    Location
    Sweden
    Posts
    10,107
    Downloads
    5
    Uploads
    0
    Mentioned
    1 Post(s)
    Tagged
    2 Thread(s)
    Likes Given
    0
    Likes Received
    126
    I have no idea what kind of content that ISO is supposed to have, but some manufacturers do 'hide' the real content of their discs, so that very little of it is apparent when you look at the 'officially' stored files, in the normal disc TOC.

    Only the game program itself can access the 'hidden' files, as it knows the LBA addresses of the data blocks used by those files.

    Squaresoft (nowdays Square-Enix) have used this technique for all of their PS2 releases that I know of, for example, and I'm sure they are not alone in doing so.

    The only real requirement for the visible TOC is that it must contain a SYSTEM.CNF, and the program file indicated in that file's BOOT2 statement. As long as those two files are visible the disc can boot, and the program booted can then proceed to work with the 'hidden' files. (Which may also include additional programs, of course.)

    Best regards: dlanor
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •