Jump to content

BoSox2882

Members
  • Posts

    84
  • Joined

  • Last visited

Everything posted by BoSox2882

  1. LUK, what do you mean by it makes things worse? Do you mean because of the verify or do you mean AnyDVD simply shouldn't be running during the burning process? I also had a question about the interface. STPI or ElbyCDIO?
  2. I dont know very much at all about defrag and such. But here is the report. I have never seen somethin like this. My computer overall is running fine, but something is amiss here.
  3. I have ran both the windows defrag and even IObit smart Defrag and neither fixed it. Should I post a screen shot of it after I analyze? There is a lot of red fragmented files.
  4. Im not sure what that means? When I try to defrag it is basically saying my whole hard drive is fragmented. Is there way to fix this?
  5. I just tried a 16X burn. It did not do the "waiting for buffers to recover", however, it never went above 8X burn? This isnt't a media problem as I use Verbs, I use these Mags on less important stuff. I 00:04:32 ImgBurn Version 2.3.2.0 started! I 00:04:32 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) I 00:04:32 Total Physical Memory: 1,039,856 KB - Available: 714,052 KB I 00:04:32 Initialising SPTI... I 00:04:32 Searching for SCSI / ATAPI devices... I 00:04:32 Found 1 DVD±RW and 1 DVD±RW/RAM! I 00:04:43 Operation Started! I 00:04:43 Building Image Tree... I 00:04:43 Checking Directory Depth... I 00:04:43 Calculating Totals... I 00:04:43 Preparing Image... I 00:04:43 Checking Path Length... I 00:04:43 Image Size: 4,346,937,344 bytes I 00:04:43 Image Sectors: 2,122,528 I 00:04:43 Operation Successfully Completed! - Duration: 00:00:00 I 00:04:54 Operation Started! I 00:04:54 Building Image Tree... I 00:04:56 Checking Directory Depth... I 00:04:56 Calculating Totals... I 00:04:56 Preparing Image... I 00:04:56 Checking Path Length... I 00:04:56 Image Size: 4,346,937,344 bytes I 00:04:56 Image Sectors: 2,122,528 I 00:04:58 Operation Successfully Completed! - Duration: 00:00:03 I 00:04:58 Operation Started! I 00:04:58 Source File: -==/\/[bUILD IMAGE]\/\==- I 00:04:58 Source File Sectors: 2,122,528 (MODE1/2048) I 00:04:58 Source File Size: 4,346,937,344 bytes I 00:04:58 Source File Volume Identifier: WCW_NITRO_D10 I 00:04:58 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER! I 00:04:58 Source File Implementation Identifier: ImgBurn I 00:04:58 Source File File System(s): ISO9660, UDF (1.02) I 00:04:58 Destination Device: [1:0:0] BENQ DVD DD DW1620 B7W9 (E:) (ATA) I 00:04:58 Destination Media Type: DVD-R (Disc ID: CMC MAG. AM3) (Speeds: 2.4x, 4x, 8x, 12x, 16x) I 00:04:58 Destination Media Sectors: 2,298,496 I 00:04:58 Write Mode: DVD I 00:04:58 Write Type: DAO I 00:04:58 Write Speed: 16x I 00:04:58 Link Size: Auto I 00:04:58 Test Mode: No I 00:04:58 BURN-Proof: Enabled I 00:04:58 Filling Buffer... (40 MB) I 00:05:00 Writing LeadIn... I 00:05:35 Writing Image... (LBA: 0 - 2122527) I 00:12:30 Synchronising Cache... I 00:12:57 Image MD5: d7aa950be94ae5823630924a2114ee0e I 00:12:57 Operation Successfully Completed! - Duration: 00:07:59 I 00:12:57 Average Write Rate: 10,253 KB/s (7.4x) - Maximum Write Rate: 11,106 KB/s (8.0x)
  6. I just went to a defrag and the after analyzing it is showing me mostly red. I am very concerned is there away to fix this?
  7. Yes, I had no problems burning above 8X before hand. In the log I posted that was a 12X burn, but the first two I did with the buffer recovering problem were 8X burns. I will defrag and see if that helps. Do you guys recommend IO Defrag or standard defrag that comes with computer?
  8. My first thought was that my harddrive was full, but it wasn't. Also I turned everything off, and my CPU usage was its usual 2%. Anything else this could be?
  9. Everything had been going fine, then all of the sudden I kept getting the message "waiting for buffers to recover." The burn would drop down 8X and gradually hit zero, before eventually going back up toward 8X and then falling again. Here is the log. I 19:56:35 ImgBurn Version 2.3.2.0 started! I 19:56:35 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) I 19:56:35 Total Physical Memory: 1,039,856 KB - Available: 679,400 KB I 19:56:35 Initialising SPTI... I 19:56:35 Searching for SCSI / ATAPI devices... I 19:56:45 Found 1 DVD±RW and 1 DVD±RW/RAM! I 19:57:06 Operation Started! I 19:57:06 Source File Sectors: 2,266,688 (MODE1/2048) I 19:57:06 Source File Size: 4,642,177,024 bytes I 19:57:06 Source File Volume Identifier: I 19:57:06 Source File Application Identifier: IMGBURN V2.3.2.0 - THE ULTIMATE IMAGE BURNER! I 19:57:06 Source File Implementation Identifier: ImgBurn I 19:57:06 Source File File System(s): ISO9660, UDF (1.02) I 19:57:07 Destination Device: [1:1:0] LITE-ON DVDRW SHM-165H6S HS0E (D:) (ATA) I 19:57:07 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 6x, 8x, 12x, 16x) I 19:57:07 Destination Media Sectors: 2,295,104 I 19:57:07 Write Mode: DVD I 19:57:07 Write Type: DAO I 19:57:07 Write Speed: 12x I 19:57:07 Link Size: Auto I 19:57:07 Test Mode: No I 19:57:07 BURN-Proof: Enabled I 19:57:07 Filling Buffer... (40 MB) I 19:57:18 Writing LeadIn... I 19:57:58 Writing Image... (LBA: 0 - 2266687) W 19:58:14 Waiting for buffers to recover... W 19:58:28 Waiting for hard disk activity to reach threshold level... I 19:58:29 Writing Image... W 19:58:51 Waiting for buffers to recover... W 19:59:04 Waiting for hard disk activity to reach threshold level... I 19:59:05 Writing Image... W 19:59:24 Waiting for buffers to recover... W 19:59:37 Waiting for hard disk activity to reach threshold level... I 19:59:38 Writing Image... W 19:59:56 Waiting for buffers to recover... W 20:00:10 Waiting for hard disk activity to reach threshold level... I 20:00:11 Writing Image... W 20:00:33 Waiting for buffers to recover... W 20:00:41 Waiting for hard disk activity to reach threshold level... I 20:00:42 Writing Image... W 20:01:03 Waiting for buffers to recover... W 20:01:14 Waiting for hard disk activity to reach threshold level... I 20:01:15 Writing Image... W 20:01:35 Waiting for buffers to recover... W 20:01:41 Waiting for hard disk activity to reach threshold level... I 20:01:42 Writing Image... W 20:02:50 Waiting for buffers to recover... W 20:02:56 Waiting for hard disk activity to reach threshold level... I 20:02:57 Writing Image... I 20:09:34 Synchronising Cache... I 20:09:39 Closing Track... I 20:09:40 Finalising Disc... I 20:09:57 Image MD5: 71e78b73e513019312c8b7e24521c921 I 20:09:57 Operation Successfully Completed! - Duration: 00:12:50 I 20:09:57 Average Write Rate: 6,522 KB/s (4.7x) - Maximum Write Rate: 9,369 KB/s (6.8x) I 20:10:04 Close Request Acknowledged I 20:10:04 Closing Down... I 20:10:04 Shutting down SPTI... I 20:10:04 ImgBurn closed!
  10. So if the ISO wad made correct the first time, for example if you use read mode, and kept the same layerbreak, would it be ok to burn without the MDS? I am guessing it would bring up the layer break box, but the only option would be the original wouldn't it?
  11. From looking at the log, you have write type as incremental. Set it to DAO. Your burning at 8X so that is good. One other thing is I don't know how good Ritekf1 media is, but some might tell you to try Verbatim or Taiyo Yuden. I would try the DAO first.
  12. How are people allowed to talk about backing up xbox games, but we can't talk about ripping? Thats crazy to me.
  13. I dont believe you can burn mpeg files. I believe you would have to use another program to convert to dvd files, such as DVDFlick or AVI to DVD.
  14. Why bother? Well, to make the read speed twice as fast. But I am kind of liking the BenQ20 at 8X read speed. Averages 5.5 and maxes at 8X, takes around 15 mins.
  15. The guides cover from the VIDEO_TS on the harddrive, not from the original disc dont they? Unless AnyDVD is used the originals DVD and VIDEO_TS would be copy protected?
  16. Would it be possible to use Build mode from the VIDEO_TS directly from the disc? Open build mode, and browse for file, go to my computer, select dvd that is in drive, drop down, and then video_ts? I did this and it lets me use build mode and everything, but I haven't tried to burn. Has anyone tried this?
  17. I will try it soon, but am currently out of Verb DVD+R DL media. LUK! can probably answer, but I hope to find a way to do this. As seamless is a nifty feature and "read" mode should be a great way to back up DL discs.
  18. Thank you Tach. I thought the MDS contained the layer break for the ISO? Or is the LB also stored in the ISO? Do I need to create MDS file or can I select under "read" settings to not create an MDS?
  19. Ah. Is there a way to use "read" mode while making the ISO seamless? Thanks LUK!
  20. Under settings and general you can select "seamless" playback. I know this will automatically check seamless in the box when using build mode. However, if under settings I have this checked, while in "read" mode will it make the ISO seamless?
  21. I believe with MCSE I could modify the firmware in the BenQ 1620, that would allow it to start 6X and finish over 14X. I dont mind reading at my current 8X, but would it be best to patch the firmware, and then still set it at 8X? The BenQ 1620 at 8X read speed only took around 15 mins to rip a full DVD+R DL.
  22. I know it will only read at 16X toward the end, but when done it said max read rate 8x and for the Litey 8.2x.
  23. I was just testing my two drives to check read speed. I have a BenQ1620 and LiteOn H6S, they both should read at 16X right? I tested them with read speed set at 16X, MAX, and 8X. When I set the BenQ1620 to 16X and started reading, it prompted me I selected 16X while actual read speed will be 8X. On all three settings the BenQ reached a max read of 8X, and an average of 5.5 for all three reads. Shouldnt it be reading at 16X? As for the LiteOn tested it on all three settings as well. It prompted me that actual read speed would be 12.1. However, on all three settings it topped out at 8.2 and averaged 5.7. Is this right? Or is something amiss?
×
×
  • Create New...

Important Information

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