Jump to content

Handler

Members
  • Content Count

    66
  • Joined

  • Last visited

Everything posted by Handler

  1. Handler

    DVD or BR For Archiving

    Hi, Our family pictures that I've taken over the years are consuming about 40 GBs and are currently sitting on a older hard drive. The hard drive is fine now, but you never know. It's time that the pictures get archived. I'm not interested in a cloud solution, so instead I'm thinking about burning multiple discs, but which type? As for DVD; it's a mature technology. Discs are cheap and I already own the burner. The downside is the available free space per disc, and how many discs would be required to backup the data and make copies of the backup discs. And, I'm concerned to some degree about 'Disc Rot'. As for Blu-ray; the technology hasn't been around as long as DVD, so 'Disc Rot' or other decaying factors perhaps aren't fully realized yet. I don't own a Blu-ray burner and even though the discs are not as cheap as blank DVDs, they are reasonably affordable. Certainly the capacity is a big plus, where the required discs to backup and make copies of the backup discs would be few and easily stored. What's your thoughts? Would you use DVD or BR for archiving? Thanks.
  2. Do Blu-ray burners make for better DVD burners?
  3. Handler

    DVD or BR For Archiving

    You're right, I wouldn't rely on discs alone. Right now I have a chance to replace one or both burners in this computer. The old Pioneer DVR-108 has trouble reading some burned discs and while it burns okay, the drawer on the Plextor PX-740a won't always open when the button is pushed. Concerns over archiving the photos has sped up their replacement. Is it fair to say that due to the greater accuracies of the Blu-ray format, does a Blu-ray burner make for a better DVD burner? If so, which Blu-ray burner would you recommend?
  4. Handler

    Windows 8 Consumer Preview

    This has been my experience (red indicating not good): Windows 3.1, Windows 98se, Windows ME, Windows XP, Vista, Windows 7. From what I've read, I think Windows 8 will do nicely to continue the pattern. My favorite Microsoft OS is Windows XP. As for Windows 7, there are a lot of little things that are annoying, but I put up with it because of the few improvements and it came pre-installed on my laptop. The desktop and me are quite happy with XP.
  5. Handler

    DVD or BR For Archiving

    Oh, poo. Sorry, I keep forgetting to scroll down far enough in the main index to see the Chat forum, where this question would have likely been more on-topic. I didn't see a way to delete so I could recreate it there.
  6. 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.
  7. Handler

    ISO Contains Multiple Phantom Duplicate Files

    No I haven't, what's that?
  8. Handler

    ISO Contains Multiple Phantom Duplicate Files

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

    ISO Contains Multiple Phantom Duplicate Files

    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: The number of VTSs stored in VIDEO_TS.IFO (16) doesn't match the real number if Title Sets stored on disk (17). 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). 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). Warning: There are 21 discrepancies in some VMGM/VTSI_MAT tables. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 3. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 4. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 4. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 5. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 5. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 6. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 6. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 8. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 8. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 9. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 9. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 10. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 10. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 11. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 11. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 13. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 13. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 14. There is one subpic stream defined for the Menu domain in the VTSI_MAT table of VTS 14. There are 1 audio stream defined for the Menu domain in VTSI_MAT table of VTS 15. 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.
  10. Handler

    ISO Contains Multiple Phantom Duplicate Files

    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.
  11. Handler

    ISO Contains Multiple Phantom Duplicate Files

    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. 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.
  12. Handler

    ISO Contains Multiple Phantom Duplicate Files

    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. 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?
  13. Handler

    ISO Contains Multiple Phantom Duplicate Files

    When I look at that area, after a fresh reload, it reads the same layer break as before, 1667264. 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. 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.
  14. Handler

    ISO Contains Multiple Phantom Duplicate Files

    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.
  15. Handler

    ISO Contains Multiple Phantom Duplicate Files

    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?
  16. Handler

    Is The Drive Failing

    Howdy, Finally burned my first DVD+R DL disc with a Plextor PX-740A (v1.02) set to x2.4 and it failed almost immediately. Rebooted the computer. The second attempt I changed the speed to MAX and the write completed and verified successfully. That burn looked like this: Not changing the settings, I went to burn an additional disc and while the write completed, the third disc had a verify that failed. Split the difference in write speed and set AWS to 4x and fourth disc failed somewhere around 30 percent into the write. It failed with a "Check Condition" and "Write Error". The error box looked like this: Doing a search here turned up a lot of threads with the single most response being to get Verbatim discs. Well, these are Verbatim discs. Specifically Verbatim P/M 95123 (Disc ID: MKM-001-00) printable discs. While I have every confidence that Verbatim discs are good, that is a 75% failure rate. Even though the Plextor PX-740A is an older drive, it doesn't have a lot of miles on it and has never, until now, burned a DL disc. No issues with single layer discs. However, I suspect that there might be something wrong with the Plextor PX-740A even though it has the latest Firmware. I think the Plextor PX-740A is a rebadge BenQ drive. Would you agree that the Plextor PX-740A is the root cause? And if so, what would you recommend as a ATA drive replacement? Or, would using the BenQ(?) firmware help make a difference? Here is the log: I 13:47:29 ImgBurn Version 2.5.1.0 started! I 13:47:29 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 13:47:29 Total Physical Memory: 2,095,852 KB - Available: 1,476,992 KB I 13:47:29 Initialising SPTI... I 13:47:29 Searching for SCSI / ATAPI devices... I 13:47:29 -> Drive 1 - Info: PIONEER DVD-RW DVR-108 1.18 (F:) (ATA) I 13:47:30 -> Drive 2 - Info: PLEXTOR DVDR PX-740A 1.02 (G:) (ATA) I 13:47:30 -> Drive 3 - Info: Generic DVD-ROM 1.0 (H:) (SCSI) I 13:47:30 Found 1 DVD-ROM and 2 DVD±RWs! I 14:13:42 Operation Started! I 14:13:42 Building Image Tree... I 14:13:42 Checking Directory Depth... I 14:13:42 Calculating Totals... I 14:13:42 Preparing Image... I 14:13:50 Using Layer Break LBA: 1963708 -> 1963712 (VTS_01, PGC: 1, Chapter: 11, Cell: 11, Vob/Cell ID: 1/11, Time: 00:53:01, SPLIP: No) I 14:13:50 Checking Path Length... I 14:13:50 Contents: 18 Files, 3 Folders I 14:13:50 Content Type: DVD Video I 14:13:50 Data Type: MODE1/2048 I 14:13:50 File System(s): ISO9660, UDF (1.02) I 14:13:50 Volume Label: XXXXXX I 14:13:50 IFO/BUP 32K Padding: Enabled I 14:13:50 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 14:13:50 TV System: PAL I 14:13:50 Size: 7,412,082,247 bytes I 14:13:50 Sectors: 3,619,184 I 14:13:50 Image Size: 7,412,744,192 bytes I 14:13:50 Image Sectors: 3,619,504 I 14:13:50 Operation Successfully Completed! - Duration: 00:00:08 I 14:26:31 Operation Started! I 14:26:31 Building Image Tree... I 14:26:31 Checking Directory Depth... I 14:26:31 Calculating Totals... I 14:26:31 Preparing Image... I 14:26:35 Using Layer Break LBA: 1963708 -> 1963712 (VTS_01, PGC: 1, Chapter: 11, Cell: 11, Vob/Cell ID: 1/11, Time: 00:53:01, SPLIP: No) I 14:26:35 Checking Path Length... I 14:26:35 Contents: 18 Files, 3 Folders I 14:26:35 Content Type: DVD Video I 14:26:35 Data Type: MODE1/2048 I 14:26:35 File System(s): ISO9660, UDF (1.02) I 14:26:35 Volume Label: XXXXXX I 14:26:35 IFO/BUP 32K Padding: Enabled I 14:26:35 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 14:26:35 TV System: PAL I 14:26:35 Size: 7,412,082,247 bytes I 14:26:35 Sectors: 3,619,184 I 14:26:35 Image Size: 7,412,744,192 bytes I 14:26:35 Image Sectors: 3,619,504 I 14:26:37 Operation Successfully Completed! - Duration: 00:00:05 I 14:26:37 Operation Started! I 14:26:37 Source File: -==/\/[bUILD IMAGE]\/\==- I 14:26:37 Source File Sectors: 3,619,504 (MODE1/2048) I 14:26:37 Source File Size: 7,412,744,192 bytes I 14:26:37 Source File Volume Identifier: XXXXXX I 14:26:37 Source File Application Identifier: IMGBURN V2.5.1.0 - THE ULTIMATE IMAGE BURNER! I 14:26:37 Source File Implementation Identifier: ImgBurn I 14:26:37 Source File File System(s): ISO9660, UDF (1.02) I 14:26:37 Destination Device: [3:1:0] PLEXTOR DVDR PX-740A 1.02 (G:) (ATA) I 14:26:37 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x, 8x) I 14:26:37 Destination Media Sectors: 4,173,824 I 14:26:37 Write Mode: DVD I 14:26:37 Write Type: DAO I 14:26:37 Write Speed: 4x I 14:26:37 Link Size: Auto I 14:26:37 Lock Volume: Yes I 14:26:37 Test Mode: No I 14:26:37 OPC: No I 14:26:37 BURN-Proof: Enabled I 14:26:37 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x) I 14:26:37 Book Type Setting: N/A I 14:26:37 Optimal L0 Data Zone Capacity: 1,963,712 I 14:26:37 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set I 14:26:37 Set L0 Data Zone Capacity Succeeded! I 14:26:37 Filling Buffer... (40 MB) I 14:26:38 Writing LeadIn... I 14:26:47 Writing Session 1 of 1... (1 Track, LBA: 0 - 3619503) I 14:26:47 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3619503) I 14:26:47 Writing Layer 0... (LBA: 0 - 1963711) W 14:35:57 Failed to Write Sectors 1429856 - 1429887 - Reason: Write Error W 14:35:57 Retrying (1 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (2 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (3 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (4 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (5 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (6 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (7 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (8 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (9 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (10 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (11 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (12 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (13 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (14 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (15 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (16 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (17 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (18 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (19 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 14:35:57 Retrying (20 of 20)... W 14:35:57 Retry Failed - Reason: Invalid Address For Write W 15:04:59 Retrying (21)... W 15:04:59 Retry Failed - Reason: Invalid Address For Write E 15:05:04 Failed to Write Sectors 1429856 - 1429887 - Reason: Write Error E 15:05:04 Next Writable Address: 1429552 I 15:05:04 Synchronising Cache... W 15:05:17 User opted to skip the 'Close Track/Session/Disc' functions. E 15:05:17 Failed to Write Image! E 15:05:17 Operation Failed! - Duration: 00:38:40 I 15:05:17 Average Write Rate: 1,244 KB/s (0.9x) - Maximum Write Rate: 5,592 KB/s (4.0x) Thanks.
  17. Handler

    Is The Drive Failing

    I guess if three distinguished people are saying Sony, maybe there's something to it. Looking over at the Egg, they have the AD-7260S-0B and the AD-7261S-0B. Specification wise, can't really tell the difference other than the 7260 has more reviews and the 7261 appears to be disliked more. Both are rated 4 out of 5 eggs. Naturally I'm concerned about the very low reviews compared to the ASUS and Lite-On models previously mentioned. Is there a preference between the 7260 and the 7261? Thanks.
  18. Handler

    Is The Drive Failing

    Since I only purchase Taiyo Yuden Single Layer DVD-R and Verbatim Double Layer DVD+R printable discs, if you had a choice between the ASUS DRW-24B1ST/BLK/B/AS and the Lite-On iHAS424-98, which one would be considered the better burner?
  19. Handler

    BurnPlot

    You may have to look in the Temp directory as they are not saved here in the specified directory with the chosen filename template. And, without the chosen filename working, there will only be one, titled "ImgBurn.ibg".
  20. Handler

    Is The Drive Failing

    Thanks for the suggestions. However, Sony's reputation and my recent experience with Plextor has dampened my willingness to purchase those brands. Sorry, I should have made that clearer before asking.
  21. Handler

    BurnPlot

    In Settings, under the Graph Data tab, did you set BurnPlot? I don't keep BurnPlot in the ImgBurn directory and it works.
  22. Handler

    Is The Drive Failing

    The Motherboard is a ASUS P4C800-E Deluxe and both ICH5R SATA ports are currently being used for two Western Digital 1TB RE3 drives. The other two SATA ports are for RAID on the Promise controller and are not being used, but also can't be used in this situation. The on-board PATA controllers consist of the boot drive, Plextor PX-740A and Pioneer DVR-108. I bought a Promise SATA300-TX4 SATA four port PCI card over a year ago, but never installed it. IIRC, there were two reasons I didn't install it. One, ASUS and other available sources at the time said that it was highly doubtful that a 1TB drive would work on the on-board SATA controller. As it turned out, they work fine. Two, since the SATA300-TX4 wasn't needed and after installing the new GFX card, I decided to leave a couple PCI slots empty to allow it to better breathe. So, I do have a unused Promise SATA300-TX4 card I could throw in there. While inside I could remove the old 57K MODEM, since we no longer have a phone line. Maybe move the sound card down a slot and then put the SATA300-TX4 in the old sound card slot. That would still give the GFX card some space. Okay, you sold me on the idea. Under this scenario, what would be a good SATA burner? P.S. The information in your reply is priceless and much appreciated. Without it, I might have purchased a less than stellar burner and would likely have been back asking more questions. Thank you.
  23. Handler

    Is The Drive Failing

    Does anyone know what would be a good ATA replacement?
  24. Handler

    Is The Drive Failing

    Not only did the laptop burn the same files without error, but the laptop drive reported different information about the discs and never allowed it to burn greater than 2.4x, the same for the verify speed. While it was like watching paint dry, it was successful. So I guess the PX-740A drive is dying of premature old age. So, going back to my unanswered question in my first post, what would you recommend as a ATA drive replacement? Thanks.
  25. Handler

    Is The Drive Failing

    The disc cleaner I have is made by TDK and it's a dry system. After placing the disc in the drive, I used WinAMP to select the necessary audio tracks to clean the lens. This time the Verbatim disc failed at 53 percent, just one percent before the layer break. I'd add a new picture of the error dialog or a ImgBurn log, but the failure is nearly identical as the first post. Failure rate is now 80 percent. Later next week I might try cross-flashing the drive with the BenQ firmware. The BenQ firmware is at least a year newer. Even though the PX-740A hasn't been used a lot, perhaps it's age is showing. Over at Newegg there's a IDE LG-GH22NP20 for 24.99 USD. At this time I know nothing about that LG drive other than it's the most reviewed drive. Since I have 35 more blanks to waste, I might as well see if my laptop can burn a Verbatim disc. Perhaps the Verbatim discs are defective. If you have any other suggestions regarding this issue, please reply. Thanks.
×

Important Information

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