ImgBurn 2.2.0.0 -> DL ISO -> NERO BURN

vbimport

#1

If I create a DL ISO of a movie using ImgBurn, whereby ImgBurn has assisted with layer breaks - Can a different burning program burn the ISO with the layer breaks staying exactly the way ImgBurn has alocated?

My burners (Pioneer DVR-108 & DVR-112L) don’t seem to like ImgBurn 2.2.0.0 but like any other burning app. I through at it. I want ImgBurn to make the ISO’s since I’ve heard it’s the bomb where DL is concerned, but I don’t want to burn with it since DL isn’t cheap when it locks up on me.

Currently UltraISO and NERO 7 are burning my ISO’s perfectly, but I haven’t tried them with DL as of yet.

TIA


#2

I’m amazed you’re still having issues!

I got myself a 112 lastweek and it’s been burning fine. Are you sure you’ve even tested it with ImgBurn?! Do you have a log of the burn?

As I’ve said in your previous thread, the program isn’t locking up, your I/O subsystem is. The second it gets a response back for the command issued, it’ll continue with whatever it’s doing. It really isn’t ImgBurn’s problem if it never gets that response - once submitted, it’s out of my hands.

Here’s a log of one I burnt earlier to add to my ‘Drives and Media’ forum. There are other burns in there using this same drive with various Verbatim and Taiyo Yuden media. I’ve not gotten round to testing all the other MID’s yet. Even so, it’s enough to show the problem isn’t a global one.

I 16:11:25 ImgBurn Version 2.2.0.3 Beta started!
I 16:11:25 Microsoft Windows Server 2003, Standard Edition (5.2, Build 3790 : Service Pack 1)
I 16:11:25 Total Physical Memory: 2,094,396 KB  -  Available: 695,660 KB
I 16:11:25 Initialising SPTI...
I 16:11:25 Searching for SCSI / ATAPI devices...
I 16:11:25 Found 2 DVD-ROMs, 2 DVD±RWs and 4 DVD±RW/RAMs!
I 16:11:28 Operation Started!
I 16:11:28 Source File: -==/\/[DISCOVERY IMAGE]\/\==-
I 16:11:28 Source File Sectors: 2,297,888 (MODE1/2048)
I 16:11:28 Source File Size: 4,706,074,624 bytes
I 16:11:28 Source File Volume Identifier: DISCOVERY_IMAGE
I 16:11:28 Source File File System(s): None
I 16:11:28 Destination Device: [4:1:0] PIONEER DVD-RW  DVR-112L 8.09 (I:) (SCSI)
I 16:11:28 Destination Media Type: DVD-R (Disc ID: TYG02) (Speeds: 4x, 6x, 8x, 12x)
I 16:11:28 Destination Media Sectors: 2,297,888
I 16:11:28 Write Mode: DVD
I 16:11:28 Write Type: DAO
I 16:11:28 Write Speed: MAX
I 16:11:28 Link Size: Auto
I 16:11:28 Test Mode: No
I 16:11:28 BURN-Proof: Enabled
I 16:11:28 Filling Buffer... (40 MB)
I 16:11:28 Writing LeadIn...
I 16:11:59 Writing Image... (LBA: 0 - 2297887)
I 16:18:17 Synchronising Cache...
I 16:18:27 Exporting Graph Data...
I 16:18:27 Graph Data File: C:\IBG\PIONEER_DVD-RW_DVR-112L_8.09_15-MARCH-2007_16-11_TYG02_MAX.ibg
I 16:18:27 Export Successfully Completed!
I 16:18:27 Operation Successfully Completed! - Duration: 00:06:58
I 16:18:27 Average Write Rate: 12,158 KB/s (8.8x) - Maximum Write Rate: 17,407 KB/s (12.6x)
I 16:18:27 Cycling Tray before Verify...
I 16:18:49 Device Ready!
I 16:18:49 Operation Started!
I 16:18:49 Source Device: [4:1:0] PIONEER DVD-RW  DVR-112L 8.09 (I:) (SCSI)
I 16:18:49 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: TYG02) (Speeds: 4x, 6x, 8x, 12x)
I 16:18:49 Image File: -==/\/[DISCOVERY IMAGE]\/\==-
I 16:18:49 Image File Sectors: 2,297,888 (MODE1/2048)
I 16:18:49 Image File Size: 4,706,074,624 bytes
I 16:18:49 Image File Volume Identifier: DISCOVERY_IMAGE
I 16:18:49 Image File File System(s): None
I 16:18:49 Verifying Sectors... (LBA: 0 - 2297887)
I 16:25:23 Exporting Graph Data...
I 16:25:23 Graph Data File: C:\IBG\PIONEER_DVD-RW_DVR-112L_8.09_15-MARCH-2007_16-11_TYG02_MAX.ibg
I 16:25:23 Export Successfully Completed!
I 16:25:23 Operation Successfully Completed! - Duration: 00:06:33
I 16:25:23 Average Verify Rate: 11,694 KB/s (8.4x) - Maximum Verify Rate: 17,329 KB/s (12.5x)





#3

I’m not amazed, but I am disappointed.

I assure you I have no reason to lie about it, I want it to work and sometimes it does.

Yes I read the last response and I understood that. This thread was posted because I want to know;


#4

The only software that’ll do it properly is something that can read the MDS file.

Did you try changing over to ‘incremental’ for the write type? Although that of course won’t fix your hanging problems.

How about changing the I/O interface to something other than SPTI?

If you’re saying Nero works, set ImgBurn to use ASPI (you might need to search out the wnaspi32.dll and put it in the ImgBurn folder). Or if you have any of the Elby / Slysoft tools installed, set it to use ElbyCDIO. You get the idea :wink:

I’d also examine your Filter drivers via the new feature in the ‘Tools’ menu. Bad ones can cause issues so it’s a good idea to clean them out - especially if they’ve not been updated in years.


#5

Actually I do feel it’s probably an ASPI/SPTI issue. I did look through the settings when I first started having problems but I didn’t find an option for ASPI. Some others were there but not the ASPI. When I get back home this weekend, I’ll re-visit the settings and see if I simply over looked it. Do I need to install the ASPI before the option will show?


#6

Okay, so I got home and copied the wnaspi.dll from my NERO folder to the ImgBurn folder. Then I changed the I/O setting on ImgBurn and checked the log file. It recognized the new setting so I’ll give it a shot this weekend and see what happens. At the very least, now I have 2 settings I can play with.


#7

Don’t forget to post up your filter driver stuff. It only takes 2 seconds to view it, copy it to the clipboard and then paste it.


#8

what causes the i/o to lock up?..i have had soo many(15/20 discs) of these for the last few weeks and i can’t understand why?most of what i’ve used has been imageburn but a small percentage has been nero or other apps…none have been dual layer discs but 1 yesterday was a verbatim 16x…popped up with an i/o error 79% of the way through then it said i didn’t have any cd/dvd drives etc…i looked in my computer and they disappeared…i restarted and everything was back to normal…would using aspi be a better option or spti?


#9

Who knows?!

Bad drivers, bad firmware, bad media, bad cables… it could be anything!

I use SPTI 100% of the time. If your machine is working as it should be, there’s no reason for it to fail or attempt to use anything else.


#10

this could be the stupidist question of the year but…is this a windows issues maybe? i got 2 new burners for this issue and had to use them on this older pc…my newer one laughs at me and the burns are horrid…this old pc w/ burns at 4x are perfect…i did a DL early this morning that turned out ok…the newer burners are way better than my NEC’s but…man this i/o error thing is a pain in the a**


#11

===============================================
Filter Driver Load Order - ImgBurn v2.2.0.0

Upper Device Filter: redbook
Upper Class Filter: [None Found]
Device: CD/DVD-ROM Device
Lower Class Filter: PxHelp20
Lower Device Filter: [None Found]

    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® Windows® Operating System
Product Version: 5.1.2600.2180
Company Name: Microsoft Corporation
Copyright: © Microsoft Corporation. All rights reserved.

    Filter Name:  PxHelp20
      File Name:  C:\WINDOWS\System32\Drivers\PxHelp20.sys
   File Version:  2.03.18a [2.3.18.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 © Sonic Solutions


#12

I’ve done about 20 test burns this morning on +RW media. Using SPTI all of the burns completed fine, but 3 faild to varify.

Using ASPI from NERO 10 burns were fine, 10 varified fine.

I used the same exact RW disc in each test.

I noticed that when using SPTI the buffers were erratic and dipping very low at times, when using ASPI the buffers remained above 97% at all times.

I would like to note that in each case that the varify failed, it was consistantly the DVR-108 that failed to varify. It gave a device error when this happend and when given the option to retry it worked on one instance. I think it could be my DVR-108 that’s having the problem.

All burns were done at 4x on Maxell DVD+RW (Phillips) media.

It does seem that ASPI is the smoother way to go for me so far.


#13

By all means get rid of that pxhelp20 thing, it caused all sorts of trouble for me, like bad quality of burns, BSODs and so on. After I deleted it and cleaned all refernces to it in registry, my burns are fine again.

edit:
I forgot to mention, that it gets installed with Winamp 5, Sonic My DVD and other programs, but even if you uninstall those programs, this driver will remain on your system and you have to get rid of it manualy.


#14

That is actually an old pxhelp20 but the filter driver itself is very common - I have it too. Mine is v3.00.42a

So I wouldn’t say you need to remove it, perhaps just update it instead by installing WinAmp or something (as mentioned above). You can always remove the WinAmp application afterwards, we’re just interested in updating your drivers!


#15

Actually, it probably got installed with Sony Vegas 7, or DVD Architect. I’ve never had winamp or sonic dvd installed on this system.

Since I already have the latest version of both of these apps, is there any other way to update the file?


#16

Erm yeah, as we both just said, install WinAmp!

You can take it off again straight away if it bothers you.


#17

Okay, so I installed WinAmp 5.33 and it shows the same as before from what I can tell…

===============================================
Filter Driver Load Order - ImgBurn v2.2.0.0

Upper Device Filter: redbook
Upper Class Filter: [None Found]
Device: CD/DVD-ROM Device
Lower Class Filter: PxHelp20
Lower Device Filter: [None Found]

    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® Windows® Operating System
Product Version: 5.1.2600.2180
Company Name: Microsoft Corporation
Copyright: © Microsoft Corporation. All rights reserved.

    Filter Name:  PxHelp20
      File Name:  C:\WINDOWS\System32\Drivers\PxHelp20.sys
   File Version:  2.03.18a [2.3.18.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 © Sonic Solutions


#18

Maybe you didn’t install the correct winamp, or did it with the wrong options.

If you examine the WinAmp 5.33 installer (winamp533_full_emusic-7plus.exe) with 7-zip, you’ll see a directory called $PLUGINSDIR.

Open that and you’ll see all the PX Engine files.

The version of Pxhelp20.dll in that folder is 3.0.33.0. So when installed correctly, yours should at least be on that version.

You might like to try extracting the folder manually and running ‘pxsetup /uninstall’ from a command prompt window (and then rebooting) before then running pxsetup normally to install the newer drivers.

Perhaps after the uninstall + reboot, and before the reinstall you could checkout c:\windows\system32\drivers and manually remove the pxhelp20 dll if it still exists.


#19

Downloaded the installer you quoted above. pxhelp20 now updated. What exactly does a filter driver do anyways?

Filter Driver Load Order - ImgBurn v2.2.0.0

Upper Device Filter: redbook
Upper Class Filter: [None Found]
Device: CD/DVD-ROM Device
Lower Class Filter: PxHelp20
Lower Device Filter: [None Found]

    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® Windows® Operating System
Product Version: 5.1.2600.2180
Company Name: Microsoft Corporation
Copyright: © Microsoft Corporation. All rights reserved.

    Filter Name:  PxHelp20
      File Name:  C:\WINDOWS\System32\Drivers\PxHelp20.sys
   File Version:  3.00.33a [3.0.33.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 © Sonic Solutions


#20

an ISO file is an image file - any burning software should write it fine does not matter which software created the image. However, if you have lockup problems maybe your box is o’ced causing instability issues?