Jump to content

Flawless115

Members
  • Posts

    97
  • Joined

  • Last visited

Everything posted by Flawless115

  1. I'm sorry "the olde," but I found that to be truly hilarious. At least your "quality rating" percentage is up from your other post. http://forum.imgburn.com/index.php?showtopic=1161 Forgive me, everyone, If I seem to have a "warped" sense of humor.
  2. Groundrush, not that there's any room for doubt, but I agree with LUK! I recently had a similar experience where I received similar error messages (and not just with ImgBurn, but with other software applications claiming it was bad media that was causing the problem). Although DELL support (and I purposely use their name, so that others may learn from my mistakes) kept telling me it was the type of media I was using (mind you, I was using Yuden and MCC [Verbatim branded] media), I finally convinced them to replace my drive and now I am "back in business" (figuratively speaking, of course).
  3. No, I wasn't around back then.
  4. It has only occured when I back up this particular movie. I haven't tried it at 4X, but I have tried burning the image with other software and the same thing happens.
  5. Thanks for the infor chewy. I started to think I had f&*@#$ up my burner with the crossflash.
  6. You'll have to forgive me kevdriver, but I don't get the joke.
  7. I thought I'd share my experience with the "BenQ 1640" and YUDEN000-T02-00 media. I just replaced my Philips 8631 (same drive as BenQ 1620 with different faceplate) with a Philips 8701 (BenQ 1640). I cross-flashed the Philips 8701 and turned it into the BenQ 1640. I've backed up two different DVDs so far since doing so. When I try to play back the first DVD on my stand-alone players, the time meter takes about 15-20 seconds before it reaches the 0:01 second mark. From there, it takes about another minute before the movie starts playing at normal speed. Its as if the disc hangs for a couple of minutes at two different places before it plays at normal speed. However, I've burned the same image three times and each time it has burned "successfully," yet all three discs behave the same on playback. So, I cannot see what could be going wrong. At first I thought the problem might be the image itself, so I deleted the original image and created another one, re-burned it, and the results were the same. Here's the log. I 19:51:02 ImgBurn Version 1.2.0.0 started! I 19:51:02 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) I 19:51:02 Initialising SPTI... I 19:51:02 Searching for SCSI / ATAPI devices... I 19:51:02 Found 7 DVD-ROMs and 1 DVD?RW! I 19:51:13 Operation Started! I 19:51:13 Source File: C:\CAPOTE.ISO I 19:51:13 Source File Sectors: 2,246,936 (MODE1/2048) I 19:51:13 Source File Size: 4,601,724,928 bytes I 19:51:13 Source File Implementation Identifier: DVD Shrink I 19:51:13 Destination Device: [1:1:0] BENQ DVD DD DW1640 BSOB (E:) (ATA) I 19:51:13 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 2.4x, 4x, 8x) I 19:51:13 Destination Media Sectors: 2,295,104 I 19:51:13 Write Mode: DVD I 19:51:13 Write Type: DAO I 19:51:13 Write Speed: 8x I 19:51:13 Link Size: Auto I 19:51:13 Test Mode: No I 19:51:13 BURN-Proof: Enabled I 19:51:14 Filling Buffer... I 19:51:14 Writing LeadIn... I 19:51:29 Writing Image... I 20:00:26 Synchronising Cache... I 20:00:27 Closing Track... I 20:00:31 Finalising Disc... I 20:00:50 Operation Successfully Completed! - Duration: 00:09:32 I 20:00:50 Average Write Rate: 8,384 KB/s (6.1x) - Maximum Write Rate: 11,172 KB/s (8.1x) The other DVD I backed up plays perfectly fine. All the discs are YUDEN000-T02-00 media, so I don't think its the media (which is why I found your post somewhat intruiguing Rippraff). Also, gonwk, for the record, I, too, updated the firmware to BSOB, installed Qsuite 2.1, and I use it on Default settings. I mention that for comparative purposes.
  8. That's what I meant to say. I phrased it incorrectly.
  9. He was actually wearing a white hat. I think you mixed the logic up a bit. Otherwise, you would have gotten it correct. The first man would have had to have seen either a black and a white hat or two white hats. If he saw two black hats, he would have known he had a white one on since the black hats would have been exhausted. The second man couldn't tell what hat he had on either so that means the third man had to have on a white hat. If the third man had on a black hat, the second man would have automatically known he had a white had (since the "two black hat" combination would have given it away for the first man).
  10. I was wondering if anyone had any opinions on cross-flashing. I ran across some information on cross-flashing a Philips 8701 to a BenQ 1640 and I'm not sure if doing so will make any improvements to my drive. Further, I'm not sure I want to take the risk if there won't be any added benefit. The biggest advantage that is evident is that upon flashing the drive I would, supposedly, have access to BenQ's Qsuite tools and Qscan (which are not available using Philips firmware). Does anyone have any opinions/comments/suggestions?
  11. There are three men in prison. Two are sighted and one is blind. The warden approaches them one day and says "I have a proposition for the three of you. I have here five hats (two black and three white). I'm going to put a hat on each one of you. You won't be able to see what hat you're wearing, only the hats on the other two men. If you can DEDUCE what hat YOU are wearing correctly, I'll set you free." He places three of the five hats on the three men (without permitting them to see what hat they each receive). The warden asks the first man, who is sighted, what color hat he has on. The man looks at the hats on the other two and says "I can't tell." The warden asks the second man, who is also sighted, what color hat he has on. He looks at the hats on the other two men and says "I can't tell either." The warden turns to the third man, the blind man, and asks him the same question. The thid man says "Well, I'm blind, but I know what color my hat is." The third man tells the warden his answer, guesses correctly, and is set free. What color was the third man's hat and how could he tell?
  12. Well, here's the long and short of it all (for those interested). A technician from DELL finally came out and replaced my Philips 8631 with a Philips 8701 (not exactly what I anticipated, but it's better than nothing). Thus far, I've burned seven different discs using three different media types (breakdown shown below) and all seven burns have been successful (using both ImgBurn and CloneDVD). Verbatim 16X DVD-R (MCC 03RG20) [1 disc burned] Verbatim 16X DVD+R (MCC-004-000) [4 discs burned] Taiyo Yuden 8X DVD+R (YUDEN000-T02-000) [2 disc burned] Therefore, my conclusion is the following: Although DELL support kept telling me that they believed it was the media that was causing the problem, I believe it was the drive. While I cannot prove my case beyond any doubt, the evidence is strongly in my favor.
  13. I've contacted Dell about my problem. After going through the loops they put you through, they're convinced its the medai and not the drive. Is YUDEN000-T02-00 media that bad of a media that I should have a bunch of coasters, cause that's what I'm getting? My burner can write CDs perfectly fine. Is that a sign that the burner works fine and it could be the media that's causing the problem?
  14. OK, I'm completely baffled! I just got a fresh batch of TYs (YUDEN000-T02-00) today. I tried to re-burn one of the images that had failed before. I burned it at 8x and I still got the same problem. I reset the maximum writing speed on all of my burning applications to 4x. Then, I used CloneDVD to burn the same image (in File mode, not ISO) and it supposedly burned successfully (according to CloneDVD). When I tried to play the disc in my stand-alone players it didn't work. I wanted to try and back-up a completely different disc, so I created a new image and tried to burn it with ImgBurn at 4x (thinking that writing at 8x might have been the problem) and I keep getting the same type of error as before (I won't bother posting the log since it is, essentially, the same type of error that shows up). My question now is, has my burner seen its last days? I've read on other forums that the Philips 8631 has caused headaches for many people. They've been forced to call Dell and have the drive replaced. Up until this point, I've been pretty lucky, I suppose. HELP!
  15. I thought I'd throw my two cents in since I just recently encountered some burning problems. I've been using YUDEN000-T02-00 since I got my burner and have had perfectly burned discs. I just recently bought a batch of Riteks and they've all turned out to be coasters except for one.
  16. All, I did some "testing" and here's what I came up with. First of all, I managed to successfully upgrade my firmware to GD30. I read somewhere that you can't upgrade firmware while virtual drives are enabled. I disabled all of my virtual drives and the firmware upgrade worked fine. To rule out the possibility that my dilemma was firmware-related, I tried to burn another image. This time ImgBurn managed to burn 14% before bombing out like before. Therefore, although the image wasn't completely recorded, I did manage to get further along. Here's the log: I 19:00:59 ImgBurn Version 1.2.0.0 started! I 19:00:59 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 19:00:59 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 19:00:59 Initialising SPTI... I 19:00:59 Searching for SCSI / ATAPI devices... I 19:01:00 Found 1 DVD-ROM and 1 DVD?RW! I 19:02:06 Operation Started! I 19:02:06 Source File: C:\MUMMY43.ISO I 19:02:06 Source File Sectors: 2,141,504 (MODE1/2048) I 19:02:06 Source File Size: 4,385,800,192 bytes I 19:02:06 Source File Implementation Identifier: DVD Shrink I 19:02:06 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 GD30 (E:) (ATA) I 19:02:06 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 19:02:06 Destination Media Sectors: 2,295,104 I 19:02:06 Write Mode: DVD I 19:02:06 Write Type: DAO I 19:02:06 Write Speed: 8x I 19:02:06 Link Size: Auto I 19:02:06 Test Mode: No I 19:02:06 BURN-Proof: Enabled I 19:02:06 Filling Buffer... I 19:02:10 Writing LeadIn... W 19:04:28 Failed to Write Sectors 0 - 31 - Power Calibration Area Is Full W 19:04:28 Retrying (1 of 20)... W 19:05:03 Retry Failed - Session Fixation Error Writing Lead In W 19:05:03 Retrying (2 of 20)... I 19:05:21 Writing LeadIn... I 19:05:22 Writing Image... W 19:08:59 Failed to Write Sectors 314528 - 314559 - Write Error W 19:09:00 Retrying (1 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (2 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (3 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (4 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (5 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (6 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (7 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (8 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (9 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (10 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (11 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (12 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (13 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (14 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (15 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (16 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (17 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (18 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (19 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:00 Retrying (20 of 20)... W 19:09:00 Retry Failed - Invalid Address For Write W 19:09:14 Retrying (21)... W 19:09:14 Retry Failed - Invalid Address For Write E 19:09:17 Failed to Write Sectors 314528 - 314559 - Write Error I 19:09:17 Synchronising Cache... I 19:09:18 Closing Track... I 19:09:28 Finalising Disc... E 19:10:09 Failed to Write Image! E 19:10:10 Operation Failed! - Duration: 00:08:02 I 19:10:10 Average Write Rate: 2,688 KB/s (1.9x) - Maximum Write Rate: 3,326 KB/s (2.4x) Secondly, I went back and check some of my previously-burned discs that were successful (these were discs from prior batches, not the current batch of discs). DVD Decrypter gives the Disc ID of the disc upon insertion, and as it turned out, the previous discs were Taiyo Yudens (see example below under Disc ID). Here's the tricky part. I checked the very last successful burn I had (the first disc out of the current batch) and it had a Disc ID of RITEK-R03-02 (like the one used above in the log). This was the only successful burn I had out of the current batch of RITEKs. Therefore, my conclusion is this: the successful RITEK burn was purely coincidental since every single RITEC disc I've used up to this point has resulted in a coaster and all of the discs I used prior to this batch have all been Tayio Yudens and they've all burned "flawlessly." Up until now, I didn't know too much about Media ID's so I simply went to a local retailer (here in the U.S.) and bought a pack of Fujifilm DVD+R's thinking they were good discs since they were Fujifilm. This is a classic example of how brands make no difference. Once batch of Fujifilm discs could be RITEKs and another could be Tayio Yudens. I ordered a new batch of authentic Tayio Yudens today from the internet, so when they come, if my burner starts burning properly again, I suppose I can conclude that it was the media that was the root of the problem. What say you?
  17. As a matter of fact, it is a new batch. As far as whether I've been able to burn any successfully, probably only one. I'll try another batch. Should I move to a different brand? Or should I continue to buy the same kind in hopes that it is just a bad batch that I bought? To confirm that DMA is enabled I went to the following window. No, the buffers are pretty clean. Questions questions questions.
  18. I changed the I/O setting from ASPI to SPTI and I still got the same error as before (log shown below) along with the following window: Also, I tried to upgrade my firmware, and for some reason, when I tried to execute the gd30.exe file, it wouldn't execute. I 17:24:36 ImgBurn Version 1.2.0.0 started! I 17:24:36 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 17:24:36 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 17:24:36 Initialising SPTI... I 17:24:36 Searching for SCSI / ATAPI devices... I 17:24:36 Found 10 DVD-ROMs and 1 DVD?RW! I 17:25:20 Operation Started! I 17:25:20 Source File: C:\Documents and Settings\My Documents\VAREKAI.ISO I 17:25:20 Source File Sectors: 2,142,230 (MODE1/2048) I 17:25:20 Source File Size: 4,387,287,040 bytes I 17:25:20 Source File Application Identifier: ELBY CLONEDVD I 17:25:20 Source File Implementation Identifier: ELABORATE BYTES I 17:25:20 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 CD21 (E:) (ATA) I 17:25:20 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 17:25:20 Destination Media Sectors: 2,295,104 I 17:25:20 Write Mode: DVD I 17:25:20 Write Type: DAO I 17:25:20 Write Speed: 8x I 17:25:20 Link Size: Auto I 17:25:20 Test Mode: No I 17:25:20 BURN-Proof: Enabled I 17:25:20 Filling Buffer... I 17:25:20 Writing LeadIn... I 17:26:37 Writing Image... W 17:26:46 Failed to Write Sectors 7040 - 7071 - Write Error W 17:26:46 Retrying (1 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (2 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (3 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (4 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (5 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (6 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (7 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (8 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (9 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (10 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (11 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (12 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (13 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (14 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (15 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (16 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (17 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (18 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (19 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write W 17:26:46 Retrying (20 of 20)... W 17:26:46 Retry Failed - Invalid Address For Write E 17:27:23 Failed to Write Sectors 7040 - 7071 - Write Error I 17:27:23 Synchronising Cache... I 17:27:24 Closing Track...
  19. I suppose there is no particular reason I'm using ASPI as opposed to SPTI. I'll try that. As far as the media, this is the same media I've been using for the past year and it's worked well--I haven't had any problems up to this point. I considered updating my firmware, but I've read that unless you know what you're doing, you may potentially damage the drive. The last thing I want to do is have to go and buy a new DVD Writer. As far as the DMA settings, DMA is enabled.
  20. I bought my PC about one year ago and have backed up several DVDs fine up to this point, even the "hard-to-back-up" DVDs that other people have had trouble with. However, within the past week, I have had error messages come up while burning an image from two different movies. When I use CloneDVD, the message I get says that the media is bad and that I should change the media and try again. I have included an ImgBurn log from the latest disc I tried to back up. Any help with this problem is greatly appreciated. I 12:17:04 ImgBurn Version 1.2.0.0 started! I 12:17:04 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 12:17:04 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! I 12:17:04 Initialising ASPI... I 12:17:04 WNASPI32.DLL - Adaptec's ASPI Layer - ASPI for Win32 (95/NT) DLL - Version 4.6.0.1021 I 12:17:04 Searching for SCSI / ATAPI devices... I 12:17:04 Found 10 DVD-ROMs and 1 DVD?RW! I 12:17:29 Operation Started! I 12:17:29 Source File: C:\Documents and Settings\My Documents\VAREKAI.ISO I 12:17:29 Source File Sectors: 2,142,230 (MODE1/2048) I 12:17:29 Source File Size: 4,387,287,040 bytes I 12:17:29 Source File Application Identifier: ELBY CLONEDVD I 12:17:29 Source File Implementation Identifier: ELABORATE BYTES I 12:17:29 Destination Device: [1:1:0] PHILIPS DVD+-RW DVD8631 CD21 (E:) (ATA) I 12:17:29 Destination Media Type: DVD+R (Disc ID: RITEK-R03-02) (Speeds: 2.4x, 4x, 8x, 12x) I 12:17:29 Destination Media Sectors: 2,295,104 I 12:17:29 Write Mode: DVD I 12:17:29 Write Type: DAO I 12:17:29 Write Speed: 8x I 12:17:29 Link Size: Auto I 12:17:29 Test Mode: No I 12:17:29 BURN-Proof: Enabled I 12:17:29 Filling Buffer... I 12:17:30 Writing LeadIn... I 12:19:49 Writing Image... W 12:20:12 Failed to Write Sectors 24992 - 25023 - Write Error W 12:20:12 Retrying (1 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (2 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (3 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (4 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (5 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (6 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (7 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (8 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (9 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (10 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (11 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (12 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (13 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (14 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (15 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (16 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (17 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (18 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (19 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write W 12:20:12 Retrying (20 of 20)... W 12:20:12 Retry Failed - Invalid Address For Write E 12:20:24 Failed to Write Sectors 24992 - 25023 - Write Error I 12:20:24 Synchronising Cache... I 12:20:25 Closing Track... I 12:20:31 Finalising Disc... E 12:20:54 Failed to Write Image! E 12:20:59 Operation Failed! - Duration: 00:03:25 I 12:20:59 Average Write Rate: 1,470 KB/s (1.1x) - Maximum Write Rate: 3,324 KB/s (2.4x)
×
×
  • Create New...

Important Information

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