Wadger Posted May 3, 2008 Share Posted May 3, 2008 I 19:49:32 ImgBurn Version 2.4.0.0 started! I 19:49:32 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 19:49:32 Total Physical Memory: 785,644 KB - Available: 345,680 KB I 19:49:33 Initialising SPTI... I 19:49:33 Searching for SCSI / ATAPI devices... I 19:49:33 Found 2 DVD-ROMs and 1 DVD Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 3, 2008 Share Posted May 3, 2008 If you can't avoid putting the via drivers on and the via drivers kill your burner, you'll probably have to invest in a Link to comment Share on other sites More sharing options...
Wadger Posted May 4, 2008 Author Share Posted May 4, 2008 If you can't avoid putting the via drivers on and the via drivers kill your burner, you'll probably have to invest in a Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 4, 2008 Share Posted May 4, 2008 If it works fine one minute, you install the drivers and it stops working, of course it's the drivers. Try changing the I/O transfer length to 'Manual' and set it to 32k if it's not already on it. That ASPI manager you've installed is not recommended. You should remove it. It might also be useful to see what's in your filter driver list. Please access it via the Tools menu, then click the clipboard button and just 'paste' into your reply here. Link to comment Share on other sites More sharing options...
Wadger Posted May 4, 2008 Author Share Posted May 4, 2008 =============================================== Filter Driver Load Order - ImgBurn v2.4.0.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: ElbyDelay Lower Class Filter: AnyDVD Lower Class Filter: PxHelp20 Lower Class Filter: ElbyCDFL Lower Device Filter: [None Found] Filter Name: ElbyDelay File Name: C:\WINDOWS\System32\Drivers\ElbyDelay.sys File Version: 5, 1, 0, 1 [5.1.0.1] File Description: Elby Delay Lower Filter Driver Product Name: CDRTools Product Version: 5, 1, 0, 1 [5.1.0.1] Company Name: Elaborate Bytes AG Copyright: Copyright © 2003 - 2006 Elaborate Bytes AG Filter Name: AnyDVD File Name: C:\WINDOWS\System32\Drivers\AnyDVD.sys File Version: 6.1.7.0 File Description: AnyDVD Filter Driver Product Name: AnyDVD Product Version: 6.1.7.0 Company Name: SlySoft, Inc. Copyright: Copyright 2002 - 2007 SlySoft, Inc. Filter Name: PxHelp20 File Name: C:\WINDOWS\System32\Drivers\PxHelp20.sys File Version: 3.00.56a [3.0.56.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 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 4, 2008 Share Posted May 4, 2008 It needs to be on 'Manual' for the 32k to actually come into play. Auto will use whatever your driver reports... but that might not be 100% correct. Your version of ImgBurn is out of date, as are some of those Elby/Slysoft filter drivers. You should update all the apps. Link to comment Share on other sites More sharing options...
Wadger Posted May 4, 2008 Author Share Posted May 4, 2008 ok most of the filters i dont have the apps any more so i removed em all, I updated the imgburn to latest and i set manual 32k, The buffer fills to about 30% before it stops, a test burn still completes 100% =============================================== Filter Driver Load Order - ImgBurn v2.4.1.0 =============================================== Upper Device Filter: [None Found] Upper Class Filter: [None Found] Device: CD/DVD-ROM Device Lower Class Filter: [None Found] Lower Device Filter: [None Found] I 13:44:31 ImgBurn Version 2.4.1.0 started! I 13:44:31 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) I 13:44:31 Total Physical Memory: 785,644 KB - Available: 262,396 KB I 13:44:31 Initialising SPTI... I 13:44:31 Searching for SCSI / ATAPI devices... I 13:44:32 Found 2 DVD-ROMs and 1 DVD Link to comment Share on other sites More sharing options...
Wadger Posted May 4, 2008 Author Share Posted May 4, 2008 forgot to add the reason im using a cdrw is because the leadin seems to be burnt so any other media tested results in a coaster Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 4, 2008 Share Posted May 4, 2008 The buffer won't go over 30%, your image is 7meg and the buffer is 20meg What controller is your drive connected to? Have you made sure it's drivers are up-to-date? If the controller isn't part of the motherboard chipset (i.e. it's 3rd party chip like jmicron), make sure your motherboard bios / card bios are up-to-date too. Do you have anything like DAEMON Tools / Alcohol 120% installed? Is so, make sure they're up-to-date and that the SPTD interface they use is too. Finally, try uninstalling the controller from within Device Manager and reboot. Link to comment Share on other sites More sharing options...
Wadger Posted May 5, 2008 Author Share Posted May 5, 2008 lol ye silly me, Well after doing what you said the controller reverts back to the drivers i first put on when i installed the mobo, It asked me for these drivers and i had to go get em from the mobo website, Now its back on the old driver burning works but the driver is too old for other sata operations to work correctly ie i cant flash any fws cos the drives arent fully recognised , Looking round the forum alot of people seem to have probs with sata and imgburn, Ive also seen io errors like Potential 'WaitImmediateIO' Deferred Error with this old driver and duel layers sometimes crap out Finalising Disc with this error but they always verify 100% so it hasnt bothered me that much, Its a real shame im gonna have to drop imgburn cos i love it so much but but other burning softs work fine under the new drivers so drop it i must Link to comment Share on other sites More sharing options...
Wadger Posted May 12, 2008 Author Share Posted May 12, 2008 Well i wasnt content with imgburn not working so i never gave up, I got it all working now and im glad i didnt What i did first was download all the updated drivers and try them from the first to last(about 10) and noticed the via_hyperionpro_v517a still has the 4 in 1 drivers but also some other crap so i manually updated the adaptor pointed it at the driver folder and it took just 1 of the 4 drivers and hay presto all working, JUst thought id tell you the good news and maybe help someone else with a similar prob, via_hyperionpro drivers was the problem but manually installing just the parts you need is the answer Thanks for your time and the App thats a pleasure to burn with Link to comment Share on other sites More sharing options...
Recommended Posts