OOO Posted June 25, 2007 Share Posted June 25, 2007 (edited) Hello I try to use ImgBurn burn CD/DVD with an external driver with IEEE1394. Initial it is all ok. But after one or two minutes, the recorder rate was down to 0. The disc and driver is still rotate (I can hear sound). But the LED of driver not light anymore. And the process stops increasing. There is no error message. the only way I can stop ImgBurn is turn off the driver. If I burn discs with USB, by iTunes with IEEE1394 or on a iBook with IEEE1394. It works all well. So I think there is something not compatible with imgburn in my PC. Driver: ASUS 1608P2S-D OS: Windsows XP Pro 32bit english MB: ASUS P5k-E it uses Agere IEEE1394 Edited June 25, 2007 by OOO Link to comment Share on other sites More sharing options...
chewy Posted June 25, 2007 Share Posted June 25, 2007 imgburn has this great feature called 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: ElbyCDFL 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: Redbook Audio Filter Driver Product Name: Microsoft Link to comment Share on other sites More sharing options...
OOO Posted June 25, 2007 Author Share Posted June 25, 2007 (edited) imgburn has this great feature called filter driver load order Thanks for remind. ===============================================Filter Driver Load Order - ImgBurn v2.3.2.0 =============================================== Upper Device Filter: redbook Upper Class Filter: GEARAspiWDM Device: CD/DVD-ROM Device Lower Class Filter: PxHelp20 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: Redbook Audio Filter Driver Product Name: MicrosoftR WindowsR Operating System Product Version: 5.1.2600.2180 Company Name: Microsoft Corporation Copyright: c Microsoft Corporation. All rights reserved. Filter Name: GEARAspiWDM File Name: C:\WINDOWS\System32\Drivers\GEARAspiWDM.sys File Version: 2.0.6.1 File Description: CD/DVD Class Filter Driver Product Name: GEAR.wrks Product Version: 8.xx [2.0.6.1] Company Name: GEAR Software Inc. Copyright: Copyright ? GEAR Software Inc. 2006 Filter Name: PxHelp20 File Name: C:\WINDOWS\System32\Drivers\PxHelp20.sys File Version: 3.00.41a [3.0.41.0] File Description: Px Engine Device Driver for Windows 2000/XP Product Name: PxHelp20 Product Version: [2.0.0.0] Company Name: Sonic Solutions Copyright: Copyright c Sonic Solutions Filter Name: imapi File Name: C:\WINDOWS\system32\DRIVERS\imapi.sys File Version: 5.1.2600.2714 (xpsp.050705-1524) File Description: IMAPI Kernel Driver Product Name: MicrosoftR WindowsR Operating System Product Version: 5.1.2600.2714 Company Name: Microsoft Corporation Copyright: c Microsoft Corporation. All rights reserved. Edited June 25, 2007 by OOO Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted June 25, 2007 Share Posted June 25, 2007 What bit is it stopping on? Writing the leadin or when writing the actual image? (look in the log window) It wouldn't hurt if you actually copied the log to your next post so we can see what's up. The program only ever submits commands and waits for a response. If it doesn't get one, there's nothing I can do about it, it's just some glitch with the I/O interface. Link to comment Share on other sites More sharing options...
dontasciime Posted June 26, 2007 Share Posted June 26, 2007 I had that error and sorry to say sounds indentical to mine. I fixed mine by using the 1394 on my soundblaster audigy 2 platinum instead of the the built in via one on my msi 975x board. The chipset in my enclosure may have also been responsible prolific 3507 Keep checking the 1394 hardware in device manager if after a couple of minutes you get yellow then maybe see if you can get a pci firewire card and hopefully they get along. Link to comment Share on other sites More sharing options...
OOO Posted June 28, 2007 Author Share Posted June 28, 2007 This is my log, hope helpful : I 00:33:10 ImgBurn Version 2.3.2.0 started!I 00:33:10 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)I 00:33:10 Total Physical Memory: 2,096,144 KB - Available: 1,025,432 KBI 00:33:10 Initialising SPTI...I 00:33:10 Searching for SCSI / ATAPI devices...I 00:33:11 Found 1 DVD Link to comment Share on other sites More sharing options...
mmalves Posted June 28, 2007 Share Posted June 28, 2007 Have you tried using the USB interface? Also, there's a firmware update for your burner (1.41), but I wouldn't recommend updating it through that enclosure. Link to comment Share on other sites More sharing options...
mironicus Posted September 3, 2008 Share Posted September 3, 2008 (edited) I have the same problem with my external DVD-writer Pioneer DVR-112d. I am also using a enclosure with Profilic 3507b chipset. Burning with firewire Imageburn starts the burn but the writing speed falls immediatly to 0x. (Burning with other applications like Nero works fine with my external burner) With USB connected I get the following error messages: I 12:49:03 ImgBurn Version 2.4.2.0 started!I 12:49:03 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 12:49:03 Total Physical Memory: 1.562.992 KB - Available: 993.388 KB I 12:49:03 Initialising SPTI... I 12:49:03 Searching for SCSI / ATAPI devices... I 12:49:03 Found 1 DVD Edited September 3, 2008 by mironicus Link to comment Share on other sites More sharing options...
dontasciime Posted September 3, 2008 Share Posted September 3, 2008 Thats a not exactly the same error as the original poster, yours is purely semaphore timeout error, try using wnaspi32.dll as ~IO interface instead of SPTI try using the 1394 on the enclosure instead of USB. see if you can update the chipset in enclosure from prolific site but don't hold your breath for being able to fix this. I have to tell you this is not an ImgBurn error but a chipset/IO interface error. you may still see it in NERO yet as it is very very very very random. Using Wnaspi32 might get rid of it full stop and that may happen NERO uses Wnaspi32 as its IO but you still can get semaphore timeout error using Wnaspi32 but it has stopped STE on many of my chipsets/enclosures. So switch to wnaspi32 in ImgBurn I/O settings actually I have re read your post and you said you already tried 1394 , you will have to see if a firmware update to enclosure chipset will fix it, not ImgBurn causing this problem though cannot say why Nero works on 1394 maybe fluke and random or down to wnaspi32 (sure I tried wnaspi32 as IO when my 1394 was acting odd but did not make any difference) Link to comment Share on other sites More sharing options...
mironicus Posted September 3, 2008 Share Posted September 3, 2008 I had already the latest firmware from Profilic installed. If I use wnaspi.dll (Nero ASPI) there is no change. It freezes while burning with firewire. On USB I get different error messages. I 14:05:25 ImgBurn Version 2.4.2.0 started!I 14:05:25 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 14:05:25 Total Physical Memory: 1.562.992 KB - Available: 1.156.348 KB I 14:05:25 Initialising ASPI... I 14:05:25 WNASPI32.DLL - Nero WnAspi32 - Win32 Nero Aspi Library - Version 2.0.1.80 I 14:05:25 Searching for SCSI / ATAPI devices... I 14:05:26 Found 1 DVD Link to comment Share on other sites More sharing options...
mmalves Posted September 3, 2008 Share Posted September 3, 2008 CopytToDVD uses Patin-Couffin interface and CloneDVD uses ElbyCDIO interface, both available as options in ImgBurn's I/O settings, so try with them and see if it works. Link to comment Share on other sites More sharing options...
mironicus Posted September 3, 2008 Share Posted September 3, 2008 I also tried all available ASPI-drivers. No change. Link to comment Share on other sites More sharing options...
dontasciime Posted September 3, 2008 Share Posted September 3, 2008 Buy a new enclosure , try enclosure on another computer as driver corruption can do it as well. No good just keep saying it works with other software. If that is 100% true then use those, not in my instance or lots of other users examples either and blaming one piece of software usually is arrogance on behalf of user (not that I am saying that about you just stating the facts as I see them) try pl2507 enclosure with pioneer products Link to comment Share on other sites More sharing options...
mironicus Posted September 3, 2008 Share Posted September 3, 2008 I installed a whole new system (Win XP SP3) yesterday evening because of this issue. I just copied a DVD with CloneDVD 2 - works. I wrote a DVD with Nero using 16x - took 5 minutes 45 seconds - works. I tried to burn a DVD with CDBurnerXP - freezes. I tried to burn a DVD with ImgBurn - freezes. Don't you think there might be a bug in ImgBurn? I can show you screenshots of the successful burns with Nero and CloneDVD, if you want proof. Link to comment Share on other sites More sharing options...
LOCOENG Posted September 3, 2008 Share Posted September 3, 2008 Two programs work and two programs don't, wouldn't that mean there is a bug in your machine? Link to comment Share on other sites More sharing options...
dontasciime Posted September 3, 2008 Share Posted September 3, 2008 You might be right but I doubt it cos when I have issues like that with firewire it's not on every burn where it does not work just a lot of them and when it works with other software it eventually does not work with that software as well. Maybe do not use service pack 3 as that might have an issue. or maybe edit use sp1 then 2 see if it makes a difference. Its down to chipset in enclosure/driver/dvd writer conflicts or if your texas inst firewire or maybe via as the one i had stinks Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted September 3, 2008 Share Posted September 3, 2008 As mentioned above, you can tell ImgBurn to use ElbyCDIO for its I/O interface. You could also try telling it to use the 'Incremental' write type in the settings. Link to comment Share on other sites More sharing options...
mironicus Posted September 3, 2008 Share Posted September 3, 2008 As mentioned above, you can tell ImgBurn to use ElbyCDIO for its I/O interface. You could also try telling it to use the 'Incremental' write type in the settings. Thank you for help - but it did not work. Same behaviour. Imageburn starts writing and after some seconds the writing speed drops to zero. The drive is still spinning. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted September 3, 2008 Share Posted September 3, 2008 I'd say to give up then and stick to using the software that works on your system. Link to comment Share on other sites More sharing options...
dontasciime Posted September 3, 2008 Share Posted September 3, 2008 did you try setting incremental as write type Link to comment Share on other sites More sharing options...
Recommended Posts