Jump to content

nu1mlock

Members
  • Posts

    8
  • Joined

  • Last visited

nu1mlock's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. I'm sorry, but I can't check the voltage with any tool, since I don't have one of those. Strangest thing happened yesterday. Well, since ImgBurn wouldn't burn my backups, I tried CloneCD. So far I have burned five working discs with CloneCD without any errors. I think it's strange that CloneCD do work when ImgBurn doesn't, don't you? nu1mlock
  2. Yes, I've changed OS's, changed drives and changed media. I tested the memory last night with Memtest (both the original Memtest and then Memtest+) from a USB-stick. I let it run three loops but it couldn't find any errors. Yes, the cable is alright, I even changed it to another cable. The drive is set to Master and with no other IDE-drives on the same cable (I don't have any IDE's at all). The power supply works as it should with the correct voltage and such. nu1mlock
  3. Yeah, well I don't need a solution for that - I already know what it is. My problem is that I can't burn any DL discs. The "Access Denied-problem" doesn't happen all the time. nu1mlock
  4. Yeah, I've burned a lot of Verbs at 2,4x too, but over 200 Verbatim +DL at 8x with only 2 of them not working (yes, I've counted), not counting those that woudln't burn the last day or two. I still get the same error when burning at 2.4x speed. Åtkomst nekad means "Access Denied". I belive that only means that ImgBurn can't lock the drive before burning. It doesn't happen all the time though. I get the other errors even without the Access Denied-error.
  5. A firmware bug for both 111D and 112D makes it that 6-8x gives a much higher quality of the disc than burning at 2,4x. This is the second batch and second brand I've tried with the new Pioneer 112D. I've tried burning just after installing either Windows Vista and Windows XP but this still gives me the error. Here's the filter driver load order: =============================================== Filter Driver Load Order - ImgBurn v2.3.2.0 =============================================== Upper Device Filter: redbook Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: [None Found] Lower Device Filter: imapi Filter Name: redbook File Name: C:\WINDOWS\system32\DRIVERS\redbook.sys File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) File Description: Drivrutin för Redbook-ljudfilter Product Name: Operativsystemet Microsoft® Windows® Product Version: 5.1.2600.2180 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. Med ensamrätt. Filter Name: imapi File Name: C:\WINDOWS\system32\DRIVERS\imapi.sys File Version: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) File Description: IMAPI Kernel Driver Product Name: Microsoft® Windows® Operating System Product Version: 5.1.2600.2180 Company Name: Microsoft Corporation Copyright: © Microsoft Corporation. All rights reserved. Thanks! nu1mlock
  6. Hey guys! I've got a problem and I have no idea what could be wrong. Here's the deal: First of all, I was using a Pioneer 111D. A couple of weeks ago my problems began with not being able to burn DL discs sometimes. About one of three discs never made it through the burning process. I've always used Verbatim for my Xbox 360 backups. Then it got worse. When burning, ImgBurn errored out something about TOC and never got past the buffer-filling. Nothing got written to the disc but no matter how many times I re-tried that disc I always got the same error. When trying to burn the same disc on another computer it worked fine. More things started to happen - my burner recognized some +R as +DL and gave me the same error as on the DL-discs. I tried upgrade the firmware of the 111D to the latest official firmware and also the latest TDB-firmware but with no luck. I'm guessing the drive was f*cked, so I bought a new, Pioneer 112D instead. Well, now it gives me another error. This time, no matter what brand of +DL-discs I'm using I always get the same error (image below) and the same log from ImgBurn (code below). I was using Windows Vista, so I thought it could have something to do with that, so I changed back to XP SP2 but still got the same error. I've tried burning the discs from three different HDD's (all SATA2's) but still got the same error. About one of five discs get burned correctly and the backup works just fine on that disc, so I know there isn't anything wrong with the image I've got. I've tried both Verbatims and Aone/XB discs but both brands give me the very same error. Sometimes I get the errormessage after 64%, sometimes after 88%. It's always different, but still the same error. Just to clear things up: Right now, I'm using a Pioneer 112D (official firmware 1.22). This is the specifications of my computer if it helps: AMD Athlon 64 5600+ X2, 2GB DDR2 800MHz Kingston ValueRam, 2x160GB, 1x320GB, 1x500GB (all SATA2), Pioneer 112D with latest official firmware (1.22). I've lost 10 discs the latest 24h, so I'd prefer if I wouldn't waste too many more just to "try this and that" unless I really need to. I'd rather gather as much information and alternatives before re-trying to burn on my Verb's right now. I 07:55:09 Operation Started! I 07:55:09 Source File: G:\GAMES\NBASTREETHOMECOURT\dnl-nsh.dvd I 07:55:09 Source File Sectors: 3 697 696 (MODE1/2048) I 07:55:09 Source File Size: 7 572 881 408 bytes I 07:55:09 Source File Volume Identifier: XBOX360 I 07:55:09 Source File Implementation Identifier: Daikin U.S. Comtec Lab I 07:55:09 Source File File System(s): ISO9660; UDF (1.02) I 07:55:09 Destination Device: [0:0:0] PIONEER DVD-RW DVR-112D 1.22 (E:) (ATA) I 07:55:09 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 2,4x; 4x; 6x; 8x) I 07:55:09 Destination Media Sectors: 4 173 824 I 07:55:09 Write Mode: DVD I 07:55:09 Write Type: DAO I 07:55:09 Write Speed: 8x I 07:55:09 Link Size: Auto I 07:55:09 Test Mode: No I 07:55:09 BURN-Proof: Enabled W 07:55:16 DeviceIoControl(FSCTL_LOCK_VOLUME) Failed! - Reason: Åtkomst nekad. W 07:55:16 DeviceIoControl(FSCTL_DISMOUNT_VOLUME) Failed! - Reason: Åtkomst nekad. I 07:55:16 User Specified L0 Data Zone Capacity: 1 913 760 I 07:55:44 Filling Buffer... (40 MB) I 07:55:45 Writing LeadIn... I 07:55:46 Writing Image... (LBA: 0 - 3697695) I 07:55:46 Writing Layer 0... (LBA: 0 - 1913759) I 08:03:03 Writing Layer 1... (LBA: 1913760 - 3697695) W 08:06:55 Failed to Write Sectors 2573856 - 2573887 - Write Error W 08:06:55 Retrying (1 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (2 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (3 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (4 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (5 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (6 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (7 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (8 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (9 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (10 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (11 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (12 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (13 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (14 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (15 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (16 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (17 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (18 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (19 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write W 08:07:01 Retrying (20 of 20)... W 08:07:01 Retry Failed - Invalid Address For Write E 08:20:00 Failed to Write Sectors 2573856 - 2573887 - Write Error I 08:20:00 Synchronising Cache... I 08:20:01 Closing Track... I 08:20:12 Finalising Disc... W 08:20:50 Potential 'WaitImmediateIO' Deferred Error - (1/2) - Session Fixation Error E 08:23:12 Finalise Disc Failed! - Reason: Session Fixation Error I 08:23:12 Finalising Disc (Last Attempt!)... E 08:23:45 Finalise Disc Failed! - Reason: Session Fixation Error E 08:23:45 Failed to Write Image! E 08:23:45 Operation Failed! - Duration: 00:28:36 Thanks alot! nu1mlock
  7. Thanks for the answer! It might not be such a bad idea for me to "invest" in a sata-burner, since they only cost about $35. I already have two seperate sata-harddrives, so that wont be a problem. I tried using Nero and burning two sets of iso files and it worked great. So I thought I'd try it with ImgBurn again. It worked - kinda. I burned two sets of isos at 2.4x. Burner1 got 100% buffer the whole time, while Burner2 got 90% down to 10% and then up to 90% again (over and over again). It still worked. I only wanted to burn two sets of isos if I had to burn at 2.4x (Xbox 360 backups), but I'll try to add some speed to my Verbatim discs next time instead. If I get it right at 8x, I wont bother with two writers. Thanks again!
  8. Hello! NOTE: I'm NOT trying to make two backups of an original nor a backup of a backup. I'm just trying to burn two files at the same time with my two burners. I just bought myself a new burner to be able to burn multiple backups at the same time. So I opened up two instances of ImgBurn and choose the right burner for the right instance. I also choose two different files from two different harddrives and started the burnprocess. Both buffers went from 0% to 100% on drive1 while drive2 went from 100% to 0% and vice versa every two seconds. Max burningspeed got up to 1.5x on each drive (so 3.0x total) while both burners support 16x and the both discs support 8x (which I choose). Both burners are on the same IDE-cable, but that shouldn't be a problem, since a friend of mine has the same setup (though different burners) and it works fine for him. So this is my setup: Burner1 burns file1 from hdd1. Burner2 burns file2 from hdd2. Both burners are on the same IDE-cable. The hdds are on different sata-ports. Burner1 (master) is a Pioneer 111D (flashed to 111L with the latest Dangerous Brothers fw). Burner2 is a Samsung SH-S182D. I also only have ONE IDE-port on my mobo, so another cable is not an option. Both burners are set to Ultra DMA. Pioneer is Master and Samsung is Slave. My computer specs is this: AMD 4600+ X2, 2GB DDR2 PC2-5300, 2x250GB Samsung Spinpoint HDDs. The rest isn't of relevance. Thanks in advance!
×
×
  • Create New...

Important Information

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