elryno Posted June 12, 2007 Report Share Posted June 12, 2007 I am experiencing a similar issue. I had not used my burner very frequently as of late. However, previously, I was able to burn data disc without problems. Now, when I attempt to burn a data disc (just some jpg's and avi's), it completes the Table of Contents and then freezes. I have Windows XP Pro SP2, ECD&DVDC6 and Plextor PX-712A drive. The exact error I get is E80041930: TrackWriter error - Wait failed - [T7123] I am anxious to see how this is resolved. Please respond with any fix/resolution. Thanks. -Ryan Link to comment Share on other sites More sharing options...
gi7omy Posted June 12, 2007 Report Share Posted June 12, 2007 That is a drive error (hardware and not software). The drive may need cleaned (or even replaced) Link to comment Share on other sites More sharing options...
elryno Posted June 14, 2007 Author Report Share Posted June 14, 2007 I do not think that this is a hardware issue. I am able to read CD/DVD's just fine. I can successfully burn a data disc using Realplayer burning functions (NTI burning engine). This appears to be an issue with the software. Is there a way to look at logs or more detailed error messages? Once again, the symptoms are that it shows the progress of and burns the TOC (orange light flashing on the drive to indicating writing). Upon reaching the final number of blocks for the TOC, it stops progressing and the drive light turns green (indicating that it is not writing). After waiting for a long time (no progress), it will give me the "Wait Failed" error message. Has anybody experienced something like this before? Link to comment Share on other sites More sharing options...
gi7omy Posted June 14, 2007 Report Share Posted June 14, 2007 "Track Writer Error" is a drive error report. What you could try is either a different brand of media or upgrade the drive firmware - but it is NOT a software error: check these websites for more info (and reports) http://forums.windrivers.com/showthread.ph...goto=nextnewest http://www.windowskb.com/Uwe/Forum.aspx/wi...r/30012/Burn-CD The last one said he also has a problem with Nero giving similar errors Link to comment Share on other sites More sharing options...
CadillacMike Posted October 9, 2007 Report Share Posted October 9, 2007 "Track Writer Error" is a drive error report. What you could try is either a different brand of media or upgrade the drive firmware - but it is NOT a software error: check these websites for more info (and reports) http://forums.windrivers.com/showthread.ph...goto=nextnewest http://www.windowskb.com/Uwe/Forum.aspx/wi...r/30012/Burn-CD The last one said he also has a problem with Nero giving similar errors Beg to differ but not necessarily so. If it IS a hardware error, then why - in my case can one program (RecordNow or disc Copier) write a full 700MB of data to a disc and another program (DVD builder) can't get past a TOC write on the same drive using the same media out of the same box??? My logic tells me this is NOT a hardware fault but an interaction b/w the hardware and software - i.e a SOFTWARE fault. And I'm a logical sort of person with 21+ years in the IT industry. Link to comment Share on other sites More sharing options...
gi7omy Posted October 9, 2007 Report Share Posted October 9, 2007 If you have that much experience then you should know that a track writer error is exactly what it says it is - the drive has failed to write the track. This is a drive error and could be caused by either the media or the drive itself. Read the articles on those two websites or google for 'track writer error' and see what you can come up with Link to comment Share on other sites More sharing options...
CadillacMike Posted October 10, 2007 Report Share Posted October 10, 2007 If you have that much experience then you should know that a track writer error is exactly what it says it is - the drive has failed to write the track. This is a drive error and could be caused by either the media or the drive itself. Read the articles on those two websites or google for 'track writer error' and see what you can come up with Sure that's the error message but it does not verify WHY that error was returned. it could have been that the drive was interrupted by some other errant routine or the routing running was itself interrupter or locked up so that it did not see or acknowledge the drive's status. I've been down this road before (on the other end as a support analyst) etc dozens of time in the past and know that with windows, nothing is ever as it seems. My computer will still lose 1 hour WHEN RUNNING if I am in a DOS full screen box running an old game, Are you goung to tell me THAT is a hardware error as well??? No, it's this POS called winblows getting too wrapped up around itself to keep track of everything all the time and DLLs & drivers overwriting each other without ever informing the user. To provide an off used analogy - we will try a variation on the my car won't start problem. My boat won't start. The error "message" i get is absolute silence. 999 out of 1000 peopple will say that it is a dead battery. Well two months ago the battery was quite well charged and the absolute silence was caused by the starter motor breaking off from the block (corroded bolts) - out in the middle of Tampa bay of course. Now, after getting the starter replaced and ensuring that i have a fully charged battery, i am again experiencing the "error message" of absolute silence when i turn the key. Are you going to tell me that the starter broke off - again? Nope it's bolted in good. So, i need to look elsewhere. Get the picture??? I'm wondering if there is an unneeded process running that is either causing the drive to not report status or a routine to not get proper status. This is all quite possible with all the stuff loaded onto this machine that my wife uses. If I post a list of all processes (not applications - because I can ensure that all other apps are closed) will anyone care to look at it and perhaps notice a "problem" process that can mess up DVD builder and be killed before attempting a DVD build. I can think of one right away, ACS.exe which the D-link wireless ethernet card suppossedly "needs". We don't use the wireless ethernet at home, but de-installing a d re-installing the software is a pain. But I've already killed that process as a test and the error still persists. Maybe the stupid norton liveupdates which is running like ten times per second is getting in the way??? I'm going to try killing liveupdate.exe and writing a disc... By the way don't suggest killing kernel.exe or explore.exe, I'm not that stupid. Link to comment Share on other sites More sharing options...
CadillacMike Posted October 10, 2007 Report Share Posted October 10, 2007 If you have that much experience then you should know that a track writer error is exactly what it says it is - the drive has failed to write the track. This is a drive error and could be caused by either the media or the drive itself. Read the articles on those two websites or google for 'track writer error' and see what you can come up with Just so that you know, I DID read those two message threads a few days ago. Not the same problem. One user mentioned getting errors in every program. I only get the error in roxio DVD Builder. other programs are writing the SAME brand / lot of discs to the same writers with no errors. The second user noticed a problem with a particular lot of discs. I'm getting this error across multiple brands or discs (and drives), but only in ONE program. The problem is the program - more likely its interaction with the drivers and other routines running in the system. Link to comment Share on other sites More sharing options...
james_hardin Posted October 10, 2007 Report Share Posted October 10, 2007 Just so that you know, I DID read those two message threads a few days ago. Not the same problem. One user mentioned getting errors in every program. I only get the error in roxio DVD Builder. other programs are writing the SAME brand / lot of discs to the same writers with no errors. The second user noticed a problem with a particular lot of discs. I'm getting this error across multiple brands or discs (and drives), but only in ONE program. The problem is the program - more likely its interaction with the drivers and other routines running in the system. I think we have established that you have taken the "latest version" and degraded it by installing updates that were never intended for it… Link to comment Share on other sites More sharing options...
gi7omy Posted October 10, 2007 Report Share Posted October 10, 2007 Well as some people seem to completely fail to understand that a track write error is something which is generated by the drive and not the software in that tyhe drive is saying 'I can NOT write to this disc', there's no point in continuing this discussion Link to comment Share on other sites More sharing options...
CadillacMike Posted October 10, 2007 Report Share Posted October 10, 2007 Well as some people seem to completely fail to understand that a track write error is something which is generated by the drive and not the software in that tyhe drive is saying 'I can NOT write to this disc', there's no point in continuing this discussion I believe that the detailed text of the error message mentioned that the program did not get a response back in a defined time frame, so my analysis is correct. Doesn't solve the problem though. To lynn98109, the thread was the exact same error message, so i do not see a problem. Additionaly. the initial poster's problem was never resolved - although his logic of stating that his drive can read ok means that it will write ok is flawed. My drive reads AND writes with no errors EXCEPT with DVD builder. I'm going to flush roxio and reinstall without the roxio web site "updates" but that will certainly leave me where i started on Saturday. got to go, the flight is boarding...Spain is nice this time of year.... Link to comment Share on other sites More sharing options...
elryno Posted October 11, 2007 Author Report Share Posted October 11, 2007 I am still tracking the progress of this thread. It is sad that no useful suggestions have been provided to date, only repetitious curt responses that seem to fail to acknowledge the content of any other responses. Instead of merely stating that the problem is a hardware problem, listen to what the other posters are saying. Then, provide a useful suggestion tailored to their specific problem. If this is too much to ask, kindly refrain from adding noise to a thread that seeks a solution. After looking for answers elsewhere, I was able to find the procedure to make my Plextor drive perform a burning self-test. Unfortunately, I have not had the bandwidth to perform this test yet (it involves disconnecting the IDE cable and rebooting while holding a button, etc...). Someday... Meanwhile, my situation remains. I am unable to burn anything from within Roxio. However, using other programs (such as Realplayer), as stated above, works flawlessly. I am not convinced that this is simply a hardware problem. Searching Google indicates that this error message is caused by the following: Easy CD Creator was waiting for acknowledgement that a command it sent to the recorder had been completed, but did not receive this acknowledgement. This error could be the result of any of the following situations: -Roxio does not correctly issue the command to the driver -The driver does not correctly receive the command -The driver does not correctly issue the command to the drive -The drive does not correctly receive the command -The drive hardware malfunctions and hangs -The drive does not correctly issue the acknowledment -The driver does not correctly receive the acknowledgement from the drive -The driver does not correctly issue the acknowledgement to Roxio -Roxio does not correctly receive the acknowledgement from the driver I tend to agree with CadillacMike. This error only indicates the symptom of the problem. It does not indicate what the problem is. As far as I know, Roxio does not directly issue ATA commands to the drive. I assume that there are some intermediate levels of software in between Roxio and the drive. For example, it is likely that a driver (maybe Roxio specific or a general Microsoft-provided one) is used. Needless to say, the problem is not as cut and dry as some would have us believe. Link to comment Share on other sites More sharing options...
james_hardin Posted October 11, 2007 Report Share Posted October 11, 2007 You and Mike are in denial. You are using 3 year old, out of production software. If you really think it is the software, remove it and install Nero 5 and see what happens. If it were mine, I would uninstall the software, delete the upper/lower filters from the Registry, delete the drive and reboot. Link to comment Share on other sites More sharing options...
CadillacMike Posted October 21, 2007 Report Share Posted October 21, 2007 You and Mike are in denial. You are using 3 year old, out of production software. If you really think it is the software, remove it and install Nero 5 and see what happens. If it were mine, I would uninstall the software, delete the upper/lower filters from the Registry, delete the drive and reboot. Jim, Before we left for Spain, I did all that you suggested and the problem remained. My next step is the drastic action of using the restore partition and having the "fun" of re-installing EVERY app and patch. But it will verify that the original config of the computer does work and that Something - a patch or other ap stomped my red box v6, which by the way I only bought last year - not three years ago. If it was so old, it should have been pulled from the shelves, not sold as a fairly expensive - as i recall - package. I'll start on it next week after i get back home. Then we'll see how hard the "hardware error" really is. Before I do that though - does anyone know if symantec's live update can mess up Roxio? It's constantly bugging me to update and i can see process threads starting and stopping continously - maybe it's getting in the way of the drive I/O routines... I might start there - less drastic... Link to comment Share on other sites More sharing options...
elryno Posted February 11, 2008 Author Report Share Posted February 11, 2008 Sorry to resurrect this thread. However, I felt that it would be appropriate to post the final chapter to this story. I finally found time to perform the internal burning test on my burner. It turned out just as I had suspected - no problems to report. I immediately uninstalled my Roxio product and installed a free alternative - CDBurnerXP. While the program may not be as feature-laden as Roxio's product, it performs the one feature I need it to - it burns CDs and DVDs flawlessly. Needless to say, I am thrilled. One word of advice to any who may read this thread. Don't just blindly follow the advice of those that profess to know, without a doubt, what the solution to a particular problem is. I could have been using my Plextor drive for the past several months. Thank you to all that put time and energy into this. Link to comment Share on other sites More sharing options...
Guest ml Posted February 11, 2008 Report Share Posted February 11, 2008 Sorry to resurrect this thread. However, I felt that it would be appropriate to post the final chapter to this story. I finally found time to perform the internal burning test on my burner. It turned out just as I had suspected - no problems to report. I immediately uninstalled my Roxio product and installed a free alternative - CDBurnerXP. While the program may not be as feature-laden as Roxio's product, it performs the one feature I need it to - it burns CDs and DVDs flawlessly. Needless to say, I am thrilled. One word of advice to any who may read this thread. Don't just blindly follow the advice of those that profess to know, without a doubt, what the solution to a particular problem is. I could have been using my Plextor drive for the past several months. Thank you to all that put time and energy into this. Roxio lost my drives too and I had to use the drivefix install.exe file on this Roxio Knowledgebase article to get them back. http://kb.roxio.com/content/kb/Creator/EEZ000005 The problem on one of my computers was a conflict between Nero and Roxio. I never did figure out what the problem was on the other two. For those with a new copy of Roxio, you probably should start with Roxio Tech Support. We're all just users of the product. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.