Jump to content
Sign in to follow this  
Handler

ISO Contains Multiple Phantom Duplicate Files

Recommended Posts

Hello,

 

I have this DVD ISO (with it's MDS file) that's 6.3 GBs in size and regardless whether the ISO is extracted with ISOBuster, UltraISO or WinRAR, or the image is mounted, internally the ISO is 37.7 GBs in size.

 

When I use ImgBurn (latest version), ImgBurn only reports the actual size of the ISO file itself, not the internal size. ImgBurn doesn't appear to detect a problem, so it offers no warning and I suppose, believes that the ISO can fit onto a DVD9.

 

When the contents of the ISO is viewed with any of the previously mentioned programs, while the VTS order is correct, there are six (6) complete duplicate sets of the main and extras. Everything else appears normal.

 

Does ImgBurn know how to handle this kind of problem or should these multiple phantom duplicate files get stripped first? And, if the phantom files should be stripped first, which program should I use?

 

Thanks.

Edited by Handler

Share this post


Link to post
Share on other sites

If you're working with a pre-built ISO, it really doesn't matter what's inside it.

 

When you ask if ImgBurn can handle it, are you talking about looking for a layer break etc?

 

As you're in charge of the one that gets used, just make sure you select one from the correct VTS set.

Share this post


Link to post
Share on other sites

Yikes, that's another issue I hadn't even considered, what to do about the layer break. I pretty much stopped when I found out there were six (6) of nearly everything inside the ISO. I prefer to take ISO's apart, do further work, and then burn the VIDEO_TS directory. I've never seen anything like this before. BTW, the latest version of PgcEdit butchered the extracted directory.

 

Not sure how to pick the correct VTS set, since there are six (6) complete duplicates that are each 5.89s GB in size (VTS_04, VTS_05, VTS_06, VTS_07, VTS_08 and VTS_09). However, If I understand this correctly, if it doesn't matter what's inside the ISO, then it also won't matter which VTS is picked. Does that sound about right?

Edited by Handler

Share this post


Link to post
Share on other sites

Oh hang on, you have the MDS file too... so maybe it already contains the LB position.

 

So don't mess with this one, just burn it.

 

I can't say how the possible LB detection stuff will work on this (i.e. if you were working with the MDS).

Share this post


Link to post
Share on other sites

It doesn't look like the MDS file is going to help or matter. I loaded the ISO with and without the MDS file. According to "Display IFO Layer Break Information", loaded either way, there is only one "Very Good" layer break and that's at VTS_07 (LBA 1667264 or 370:30:14 (MM:SS:FF)), which is around the 15 GB mark. If I'm understanding this correctly, it would seem that ImgBurn is not discarding the phantom files and is going to try to burn a 6.3 GBs DVD ISO, internally 37.7 GBs, to a DVD9.

 

Unfortunately, I don't have enough blank DVD9 Verbatim's to experiment. I suspect ImgBurn is going to run out of disc long before even getting to the layer break.

Edited by Handler

Share this post


Link to post
Share on other sites

You can't look at it like that - or at least you don't have to/shouldn't.

 

The LB ImgBurn will use is displayed on the main window in Write mode (next to where it says 'Sectors') if it's present in the DVD/MDS/NRG file in the first place.

 

If you burn the ISO, it doesn't look inside at the collective size of the files, that's just not how burning an ISO works.

 

I simply read 2048 bytes from the image file and burn it to sector 0, read the next 2048 bytes and burn sector 1 etc etc. (well, something along those lines anyway - 64k chunks typically)

Share this post


Link to post
Share on other sites

The LB ImgBurn will use is displayed on the main window in Write mode (next to where it says 'Sectors') if it's present in the DVD/MDS/NRG file in the first place.

When I look at that area, after a fresh reload, it reads the same layer break as before, 1667264.

 

 

If you burn the ISO, it doesn't look inside at the collective size of the files, that's just not how burning an ISO works.

I guess what's confusing me the most is that every ISO I've ever seen, until now, whether extracted, viewed internally or mounted, has always had the correct representation of the files. This ISO displays 97 files, of which 2/3 are phantoms.

 

 

I simply read 2048 bytes from the image file and burn it to sector 0, read the next 2048 bytes and burn sector 1 etc etc. (well, something along those lines anyway - 64k chunks typically)

Doesn't Test Mode just go through the motions of burning a disc without actually writing a single bit of data to the disc, right? With my limited amount of blank discs, and no source for DVD+RW DL, I suppose I could use that to test the ISO.

Share this post


Link to post
Share on other sites
When I look at that area, after a fresh reload, it reads the same layer break as before, 1667264.

 

Ah well that's not 15GB then is it :)

 

1667264 (sectors) * 2048 (bytes per sector) = 3414556672 bytes = 3334528 KB = 3256.375 MB = 3.1800537109375 GB

 

Test mode doesn't work on DVD+ format media (unless you've got an old BenQ 1620/1640/1650/1655 laying around).

Share this post


Link to post
Share on other sites
When I look at that area, after a fresh reload, it reads the same layer break as before, 1667264.

 

Ah well that's not 15GB then is it :)

 

1667264 (sectors) * 2048 (bytes per sector) = 3414556672 bytes = 3334528 KB = 3256.375 MB = 3.1800537109375 GB

Shucks, I suppose not. Damn you math, with your figures and facts. :doh:

 

 

Test mode doesn't work on DVD+ format media (unless you've got an old BenQ 1620/1640/1650/1655 laying around).

That would be great, but unfortunately I don't own any of those drives. Oh wait, I have a old Plextor PX-740A, which is suppose to be a rebadged BenQ DW1640. Oh wait, it probably needs to be cross-flashed and it's not. Oh well.

 

Shouldn't ImgBurn's drive and blank disc detection ghost out that option? How would you get the correct file structure extracted without burning this odd ISO to a disc?

Edited by Handler

Share this post


Link to post
Share on other sites

Ghost it out... no. It tells you it's not supported if it's ticked and you try to burn.

 

Getting the correct file structure - no idea.

 

Less messing with this one and more burning me thinks!

Share this post


Link to post
Share on other sites

Ghost it out... no. It tells you it's not supported if it's ticked and you try to burn.

Ah, I see. Sort of like putting a stop sign in the middle of the next street, rather than at the previous intersection. Of course, you only need to drive through the intersection once to know to stop. ;)

 

 

Getting the correct file structure - no idea.

 

Less messing with this one and more burning me thinks!

While it wasn't as simple as finding an application that would extract it correctly on it's own, I did eventually fix it last night. Can't say that the same treatment would work as well on the next odd structured ISO's, but this time it turned out okay.

 

Thanks for all your help, it was very much appreciated.

Share this post


Link to post
Share on other sites

Maybe I'm missing something here, but, it seems to me the easiest way around this rather unique problem is to point DVDShrink to the extracted contents folder. Shrink should then be able to pick out what to keep and what duplicates not to keep. Then, just Shrink to a VIDEO_TS folder with no compression and load that VIDEO_TS into ImgBurn's Build mode to see how the layer break goes.

Share this post


Link to post
Share on other sites

Maybe I'm missing something here, but, it seems to me the easiest way around this rather unique problem is to point DVDShrink to the extracted contents folder. Shrink should then be able to pick out what to keep and what duplicates not to keep. Then, just Shrink to a VIDEO_TS folder with no compression and load that VIDEO_TS into ImgBurn's Build mode to see how the layer break goes.

Thanks for the suggestion. I tried DVD Shrink around the same time I tried PgcEdit. While opening the VIDEO_TS directory, DVD Shrink encountered a "Invalid Data" error and couldn't continue. The same thing happened opening the MSD file. Even though PgcEdit butchered the extracted directory, at least PgcEdit was able to open the VIDEO_TS directory without error.

Edited by Handler

Share this post


Link to post
Share on other sites

Is that ISO from a commercial DVD or some home made stuff? It it's the first, it might be part of a copy protection targeting DVD Shrink.

 

Tried to see what happens if you select DVD-> Remove Useless Stuff in PgcEdit?

Share this post


Link to post
Share on other sites

Tried to see what happens if you select DVD-> Remove Useless Stuff in PgcEdit?

 

The option "Remove Useless Stuff" cleans up most of the butchery, but not all. What follows is a complete rundown of what happens when loading the extracted directory into PgcEdit. List of open errors:

 

  1. The number of VTSs stored in VIDEO_TS.IFO (16) doesn't match the real number if Title Sets stored on disk (17).
  2. The number of VOB IDs stored in the VTS_C_ADT table of VTS 7 (18) doesn't match the real number of VOB IDs in the table (11).
  3. The number of VOB IDs stored in the VTS_C_ADT table of VTS 12 (12) doesn't match the real number of VOB IDs in the table (5).
  4. Warning: There are 21 discrepancies in some VMGM/VTSI_MAT tables.
  5. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 3.
  6. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 4.
  7. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 4.
  8. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 5.
  9. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 5.
  10. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 6.
  11. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 6.
  12. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 8.
  13. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 8.
  14. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 9.
  15. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 9.
  16. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 10.
  17. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 10.
  18. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 11.
  19. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 11.
  20. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 13.
  21. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 13.
  22. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 14.
  23. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 14.
  24. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 15.
  25. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 15.

All errors were corrected.

 

Finally, the BOV scan. Then PgcEdit says, "There are some VOB files in your DVD folder that are not referenced by the current IFOs" and recommends they be removed. Note that none of the VOB files to be removed include any of the VTS_XX_1.VOB files. These VOB files are:

 

VTS_03_0.VOB   VTS_05_3.VOB   VTS_06_6.VOB   VTS_09_3.VOB
VTS_04_0.VOB   VTS_05_4.VOB   VTS_08_0.VOB   VTS_09_4.VOB
VTS_04_2.VOB   VTS_05_5.VOB   VTS_08_2.VOB   VTS_09_5.VOB
VTS_04_3.VOB   VTS_05_6.VOB   VTS_08_3.VOB   VTS_09_6.VOB
VTS_04_4.VOB   VTS_06_0.VOB   VTS_08_4.VOB   VTS_10_0.VOB
VTS_04_5.VOB   VTS_06_2.VOB   VTS_08_5.VOB   VTS_11_0.VOB
VTS_04_6.VOB   VTS_06_3.VOB   VTS_08_6.VOB   VTS_13_0.VOB
VTS_05_0.VOB   VTS_06_4.VOB   VTS_09_0.VOB   VTS_14_0.VOB
VTS_05_2.VOB   VTS_06_5.VOB   VTS_09_2.VOB   VTS_15_0.VOB

Finally, PgcEdit warns that it has detected multiple sets of menu buttons or BOVs in VMGM and cannot correctly handle multiple sets of Buttons/BOVs. Then explains what shouldn't be edited or remapped.

 

At this point PgcEdit is done loading the extracted directory. We haven't even gotten to "Remove Useless Stuff" yet and the extracted directory is already a mess at this point. The "Remove Useless Stuff" option cleans it up some, but leaves displaced phantom files.

Edited by Handler

Share this post


Link to post
Share on other sites

Unless I'm using it wrong, as you can see PgcEdit wasn't much help.

Edited by Handler

Share this post


Link to post
Share on other sites

It should remove the "stripped" video that PgcEdit has removed fromthe ifo files. This program will remove it from the .vob files also.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.