Jump to content

slipkid

Members
  • Content Count

    29
  • Joined

  • Last visited

About slipkid

  • Rank
    ISF Newbie
  1. slipkid

    Write error question

    Thanks very much! I will try upgrading his firmware. Didn't realize it wasn't the latest. Also he is not at 2.5 yet, think he was still at 2.4.4, will have to upgrade that for him too. I installed the drive for him a couple months ago and gave him both EAC and IMGBURN at that time, and it tested out fine on media that I brought with me. I'm really thinking that the media he is using is just bad (seems like over 50% of the time it bombs out).
  2. slipkid

    Write error question

    I'm trying to help my cousin with some CDR write issues. This is not an IMGBURN problem per se. I think this error is either due to the media he is using (which from what I have figured out he has had lying around for several years), or his CDR burner may be dying, or he may be writing too fast for his media. Curious what you guys think....thanks! >>>>>>>>>>>>> I 22:05:31 Operation Started! I 22:05:31 Source File: C:\! CD\EAC rips\the quick.cue I 22:05:31 Source File Sectors: 349,840 (AUDIO/2352) I 22:05:31 Source File Size: 822,823,680 bytes I 22:05:31 Source File File System(s): None I 22:05:31 Destination Device: [1:0:0] PLEXTOR CD-R PX-W4012A 1.06 (D:) (ATA) I 22:05:31 Destination Media Type: CD-R (Disc ID: 97m26s66f) I 22:05:31 Destination Media Sectors: 359,849 I 22:05:31 Write Mode: CD I 22:05:31 Write Type: SAO I 22:05:31 Write Speed: 32x I 22:05:31 Lock Volume: Yes I 22:05:31 Test Mode: No I 22:05:31 OPC: No I 22:05:31 BURN-Proof: Enabled I 22:05:31 Advanced Settings - PowerRec: Yes I 22:05:31 Filling Buffer... (40 MB) I 22:05:33 Writing LeadIn... I 22:06:07 Writing Session 1 of 1... (22 Tracks, LBA: 0 - 349839) I 22:06:07 Writing Track 1 of 22... (AUDIO/2352, WAVE, LBA: 0 - 14763) I 22:06:18 Writing Track 2 of 22... (AUDIO/2352, WAVE, LBA: 14764 - 29240) I 22:06:30 Writing Track 3 of 22... (AUDIO/2352, WAVE, LBA: 29241 - 40870) I 22:06:40 Writing Track 4 of 22... (AUDIO/2352, WAVE, LBA: 40871 - 56957) I 22:06:53 Writing Track 5 of 22... (AUDIO/2352, WAVE, LBA: 56958 - 69336) I 22:07:03 Writing Track 6 of 22... (AUDIO/2352, WAVE, LBA: 69337 - 90013) I 22:07:21 Writing Track 7 of 22... (AUDIO/2352, WAVE, LBA: 90014 - 106223) I 22:07:34 Writing Track 8 of 22... (AUDIO/2352, WAVE, LBA: 106224 - 123509) I 22:07:49 Writing Track 9 of 22... (AUDIO/2352, WAVE, LBA: 123510 - 128135) I 22:07:52 Writing Track 10 of 22... (AUDIO/2352, WAVE, LBA: 128136 - 149675) W 22:08:01 Failed to Write Sectors 138666 - 138692 - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (1 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (2 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (3 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (4 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (5 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (6 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (7 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (8 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (9 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:01 Retrying (10 of 20)... W 22:08:01 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (11 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (12 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (13 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (14 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (15 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (16 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (17 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (18 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (19 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:08:02 Retrying (20 of 20)... W 22:08:02 Retry Failed - Reason: Write Error - Recovery Needed W 22:09:58 Retrying (21)... W 22:09:58 Retry Failed - Reason: Write Error - Recovery Needed W 22:09:59 Retrying (22)... W 22:09:59 Retry Failed - Reason: Write Error - Recovery Needed E 22:10:01 Failed to Write Sectors 138666 - 138692 - Reason: Write Error - Recovery Needed I 22:10:01 Synchronising Cache... W 22:10:06 User opted to skip the 'Close Track/Session/Disc' functions. E 22:10:06 Failed to Write Image! E 22:10:08 Operation Failed! - Duration: 00:04:35 I 22:10:08 Average Write Rate: 1,361 KB/s (7.9x) - Maximum Write Rate: 2,790 KB/s (16.2x) I 22:11:12 Close Request Acknowledged I 22:11:12 Closing Down... I 22:11:12 Shutting down SPTI... I 22:11:12 ImgBurn closed! <<<<<<<<<<<<<<<<<<<<
  3. slipkid

    IMGBURN always opens multiple "handles"????

    THX, this is a tough one to nail down, it is not reproducable at all, so I understand. I can burn 20-30 disc without it happening. Then next day I might burn 5 (or 10 like what happened to last time) and then it crops up. Exiting IMGBURN seems to get it back to a clean slate. The only other thing I can thing of to mention is that it never happens with burning CDs (where I use Write mode). I occasionally have a couple ISO files for DVDs to burn in Write mode and I don't recall it ever happening there either. Just with folders to burn to DVD in Build mode.
  4. slipkid

    IMGBURN always opens multiple "handles"????

    Just came back up here since having the problem now & will capture some logs etc. Saw this post that I'll reply to first: I'm not aborting out of verify or anything like that. Just doing a bunch of Build/write commands in succession. Here's what happened this time when I got the error. I burned 10 discs in a row with no problems. All came from using Build command on different directory trees on same hard drive. Then on the eleventh disc I got the locked volume error message. There are no other programs that are trying to access the drive. In IMGBURN I have the eject tray option on by default and for this disc I know that I had leaned over the PC and took out the burned DVD and put in a new one BEFORE I had clicked on the OK prompt acknowledging the previous disc. Don't know if that has anything to do with anything because sometimes I do it this way, whereas other times I click on that prompt first b4 putting in DVD for next burn, but am just mentioning that since I see it is the case now. Both Unlocker and Process Explorer show IMGBURN with 5 open handles on the drive now during the problem. I am pasting in a copy of Unlocker's screen; that program shows the handle numbers (Process Exp only shows the PID). After I clicked the CANCEL option in IMGBURN one of those handles closed (#752), and it now shows as having 4 open handles (one of them closed). Am attaching Unlocker's screen of that. Then after trying to burn again, I get the same error. Looking again in Unlocker, it shows that handle #752 has opened again, giving IMGBURN 5 handles open. At this point I am closing IMGBURN, then restarting it. After IMGBURN is running and has spun up the drive after I close the door with a new disc loaded, I checked the same drive with Unlocker, prior to telling IMBURN to do anything, and it shows no open handles on the drive with any program. I am now going into BUILD mode and selecting the same directory to burn as b4. Checking with Unlocker again, IMGBURN now has one handle open on the drive. After then starting the burn, checking with Unlocker again shows IMGBURN with 2 handles open. After the burn completed, I checked Unlocker again and this time it showed no handles open. Went back into BUILD mode and selected another dir to burn, and checked again with Unlocker and it showed 1 handle open. Then started burn, and can see 2 handles again. Hope any of this is helpful. Let me know if you have any other questions/insights or tests I should try to further diagnose. Again, this is not a big deal, but is a minor annoyance that I would love to know how to avoid if possible. Am on 3rd disc right now after exiting/restarting and the problem has not reoccured. It happens to me sporadically and I still can't pin down why. Here is the complete IMGBURN log, showing the first successful burns then the locked volume error (twice) after which I then exited the program: >>>>>>>>>>>>> ; //****************************************\\ ; ImgBurn Version 2.4.2.0 - Log ; Wednesday, 18 March 2009, 17:56:16 ; \\****************************************// ; ; I 14:44:44 ImgBurn Version 2.4.2.0 started! I 14:44:44 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3) I 14:44:44 Total Physical Memory: 1,047,564 KB - Available: 570,212 KB I 14:44:44 Initialising SPTI... I 14:44:44 Searching for SCSI / ATAPI devices... I 14:44:45 Found 1 DVD
  5. slipkid

    IMGBURN always opens multiple "handles"????

    Yes, I understand, thanks for looking into it so far though. It is hard to reproduce, only seems to happen to me when I don't want it to (of course that is always the way with hard to diagnose PC problems). Today I burned about 7 discs in a row and it didn't happen at all. A couple days ago it cropped up when I burned 3 discs..... I do have a screen shot of the problem back from when I first posted the other day, from Process Explorer, that I will attach here. Don't think it will be very useful though. I'll try to document it more thoroughly with PE & Unlocker, IMGBURN logs, etc, next time. Thanks again for this great program and your time in the forums. This unlocker problem is annoying but not a big deal (exiting IMGBURN and coming back in fixes it everytime for me so far; also although I can't remember for sure I think if I just tell it to "continue" anyway it just goes ahead and seems to work ok - I usually exit though).
  6. slipkid

    IMGBURN always opens multiple "handles"????

    "YES" to all 3 questions Lightning. Could this be some kind of XP issue on my PC? I should mention that my PC also frequently has problems with thinking that large AVI type files, or the directories that hold them, are "open" even when they are not and then give me problems trying to delete them. I have to either reboot, use unlock, or GIPO utilities moveonboot to fix things when that happens. I would love to know how to turn off the XP function that "sniffs" files when you hover over them since I believe this issue is related to that feature of the operating system (almost ALWAYS if I try to delete a large AVI the opsys will not let me, but if I hover over it long enough to have it add the file information on the bottom of the screen I can THEN delete it, but not before - and even when doing that, sometimes it won't let me delete it, no matter what, unless i reboot/unlock/etc).
  7. slipkid

    IMGBURN always opens multiple "handles"????

    The only thing(s) I can think of off top of my head is that when I use IMGBURN for burning DVDs it is after I have a bunch of stuff piled up that I want to burn. All the directories that correspond to each DVD are usually all subdirectories of the same parent directory. I burn one after the other with the build function, taking out the burned discs and replacing them with new ones, then selecting the next target subdir to burn then tell it to go once the prompt indicates the drive is ready. I notice that the drive spins up with each new disc that I put in. I sometimes click "OK" after each disc is done THEN put in a new disc and other times I replace the disc first then click OK (depending on if I am in front of the keyboard or in front of the PC replacing the disc). Somewhere along that sequence IMGBURN then gives me the locked volume error message. Maybe I need to slow down as far as clicking OK, changing the discs, starting the next one? Should I wait until after the drive sounds like it finishes spinning before moving on?? I haven't been able to pin any one thing down as what causes this - sometimes I can burn 10+ discs in this fashion without the error coming up. Other times I keep getting plagued by it. I'll try to keep my behavior one specific way and try it & see what happens (clicking OK before putting in the new disc vs. changing the disc then clicking OK etc). THANKS!
  8. I have a question about the "locked volume" error, which occurs fairly often on my PC with IMGBURN. Since I know that I have no other processes running accessing the drive(s) other than IMGBURN, to clear the error I just exit IMGBURN and restart it and then things are fine (until it decides to happen again later for unknown reasons). I've read the FAQ regarding this issue and have examined things on my PC with both Process Explorer and Unlocker, both when the problem occurs and when IMGBURN works normally. What I've noticed on my PC is that when IMGBURN is NOT giving the error, while it is actively writing it always creates 2 seperate "handles" (both same PID# and identified as process "IMGBURN") accessing my DVD drive that it is writing to. When the program is at rest it only has one "handle" though. But when the crazy locked volume error happens there are at least FOUR seperate IMGBURN applications running with the same PID and different handles. I can get around the problem when it happens by exiting IMGBURN & restarting it (or selecting the "Continue" choice to just go ahead and burn anyways) but I'm very curious as to what this problem is due to or if there is anything that I can do on my PC to fix this? I am running WinXP SP2. This same problem used to happen with SP1, and has happened on all 3 of the drives I've used. Not a big deal, but it is an annoyance that I'd like to solve if possible. here is an example IMGBURN log when the problem recently occured: >>>>>> I 15:10:25 Average Write Rate: 10,497 KB/s (7.6x) - Maximum Write Rate: 11,443 KB/s (8.3x) I 15:11:59 Operation Started! I 15:11:59 Building Image Tree... I 15:12:00 Checking Directory Depth... I 15:12:00 Calculating Totals... I 15:12:00 Preparing Image... I 15:12:00 Checking Path Length... I 15:12:00 Contents: 63 Files, 2 Folders I 15:12:00 Size: 4,503,171,072 bytes I 15:12:00 Sectors: 2,198,814 I 15:12:00 Image Size: 4,503,863,296 bytes I 15:12:00 Image Sectors: 2,199,152 I 15:12:01 Operation Successfully Completed! - Duration: 00:00:02 I 15:12:01 Operation Started! I 15:12:01 Source File: -==/\/[bUILD IMAGE]\/\==- I 15:12:01 Source File Sectors: 2,199,152 (MODE1/2048) I 15:12:01 Source File Size: 4,503,863,296 bytes I 15:12:01 Source File Volume Identifier: 0417F I 15:12:01 Source File Application Identifier: IMGBURN V2.4.2.0 - THE ULTIMATE IMAGE BURNER! I 15:12:01 Source File Implementation Identifier: ImgBurn I 15:12:01 Source File File System(s): ISO9660, UDF (1.02) I 15:12:01 Destination Device: [1:0:0] PIONEER DVD-RW DVR-115D 1.22 (Z:) (ATA) I 15:12:01 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x, 20x) I 15:12:01 Destination Media Sectors: 2,295,104 I 15:12:01 Write Mode: DVD I 15:12:01 Write Type: Incremental I 15:12:01 Write Speed: 8x I 15:12:01 DVD+R Reserve Track: No I 15:12:01 Link Size: Auto I 15:12:01 Test Mode: No I 15:12:01 OPC: Yes I 15:12:01 BURN-Proof: Enabled E 15:16:15 Failed to lock volume for exclusive access. E 15:16:15 Reason: Access is denied. E 15:16:17 Operation Aborted! - Duration: 00:04:13 I 15:16:17 Average Write Rate: N/A - Maximum Write Rate: N/A I 15:16:18 Close Request Acknowledged I 15:16:18 Closing Down... I 15:16:18 Shutting down SPTI... I 15:16:18 ImgBurn closed! <<<<<<<< Thanks for any clues!
  9. Just wanted to say that I removed the PFC filter, rebooted, and all looked good. I went a couple days that way, checking blank CDRs every so often, and all came up as 79+ plus as seen by IMGBURN. Thought maybe the problem was solved, but just checked again now and - it is back to seeing only 55min instead of 79min. Am still very much scratching my head over this. Over at another forum they tell me to try downgrading the firmware, but I have to research that further to even see how to do it, and at the same time am reluctant to do so for fear of that hurting the drive's performance with various DVD media types. At this point I probably am giving up but if I ever do figure this out I will try to post what it was in this thread for anyone curious.
  10. Things are acting up again so I did that capture you mentioned. Here's some of the log with a T-Y blank - I've removed some of the duplicate entries to make this smaller - if you want me to post the whole log just let me know: I 01:52:39 ImgBurn Version 2.4.2.0 started! I 01:52:39 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3) I 01:52:39 Total Physical Memory: 1,047,564 KB - Available: 590,888 KB I 01:52:39 Initialising SPTI... I 01:52:39 Searching for SCSI / ATAPI devices... I 01:52:39 Found 1 DVD
  11. THANKS. I am definitely leaning towards removing it. The link I posted above was where I saw some people say they couldn't see their drives after doing that, but the more I've been reading the more this filter thing seems unnecessary and possibly more problematic than it's worth. I think if I do lose the drives after removing this filter I should be able to get them back again just removing the from drives from device manager & rebooting & letting XP reinstall what it needs. And as far as some apps possibly breaking or complaining, *hopefully* I would be able to reinstall any apps to fix them, provided of course I can find their original install discs/files. I have found more threads googling around with people asking how to get rid of it more than I have people asking how to get it though so I take that as a definite sign it is expendable!
  12. THANKS! I may try that. In the meantime I have been trying to learn/understand what that filter is. I confess to not really understanding what it does or what uses it but from what I've read so far it I think is used by a bunch of different applications as some kind of way for them to communicate with CD/DVD drives. Looks like it could have come from anything I have including stuff like CONVERTXtoDVD, ADOBE AUDITION, CDRWIN, DVDSHRINK, anything like that. I'm not sure if my PC might need it for anything or not (?). This one link I found has people commenting about the driver, discussing if it is malware (it's not), and I noticed several complained that if they removed it they couldn't get to their DVD drives anymore, so that makes me nervous about deleting it: http://www.neuber.com/taskmanager/process/pfc.sys.html If I use IMGBURN to remove it, is there a way to reinstall it if I still need it? Maybe I'll find I still need it right away (?), or maybe I won't know until I try a function in some other app months down the road, so I'm a bit skittish about removing it since I really don't understand fully what it is. And what does IMGBURN do when removing it - deleting it from the registry and deleting the files too? Again, sorry for dumb questions. I have tried searching around for a couple hours to learn what this driver/filter is but I'm still confused.
  13. No, I've never heard of it!!! I will google it, see if I can learn anything about it to jog my memory, and try to find out how to remove or update that filter. This is a new topic for me. As much of a pain that this is I like learning about this stuff though. I will try that once I notice this wierdness again & get back to you in this thread. What I'll do is just keep checking discs once or twice a day even if I am not trying to burn anything, in hopes of catching this thing in action. THANKS!
  14. Thanks. The way it is a transient thing is what really makes me scratch my head. If a firmware bug why would it be OK sometimes and not others? But maybe that is just the nature of this bug. Does anyone know what other programs I can use that also issues that READ TRACK INFORMATION command and then shows me what it sees? Because so far when this is happening I have double-checked the discs with both EAC's write interface and NeroDiscSpeed but they think the blanks are about 80 minutes (are they only reading the leadout spot?). Cheers.
×

Important Information

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