Dolt
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Dolt
-
-
Manual deletions is how I have always run my queues, once all is ok it's quick and easy to do
He might as well remove the damned option since it's so useless. Nobody can safely use it.
Everyone here says they the besy thing is to NOT use the damned delete option since it's too
dangerous. I thought only Microsoft was dumb enough to leave in defective code that can
cause the user to unwittingly damage their data.
-
If you get a BSOD you should be able to examine the memory dump in WinDbg and find which driver is causing the issue.
It crashed but there's NO DUMP! It hits the system so hard that it fails to dump ANYTHING.
No memory dumps! NOTHING but a BSOD !!! It justs says something useless like "The
previous systen shutdown was unexpected." I have some old error claiming "an error
was detected on \Devide\CdRom0 during a pagging operation" and it says it about 100
times over a 1-2 second period back on the 5th of February.
-
As donta said the DVD-R DLs are near enough useless unless the original layer break happens to be in the exact same position as the fixed layer break on the blank media.....
Do as donta said return em as shite and get Verbatim DVD+R DL's....
well i just ordered + r verbatim , ok guys this forum is great : in france nobody wanted to answer me : i hate frenchies..
I've had good results with Memorex media which is made by Ritek "RITEK-D01-01" but better quality then their own RiData line, "RITEKG04" & RITEKG05". They have a dark purple unlike the Ritek's I've had problems with. RiData's are at about 10% failure for any media type, I forget the disk ID fro their DL ones. The Maxell's I have say RITEKG04 for their descriptor ID.
I had 8 of 10 Verbatim DL's fail "MKM-001-00" but only 4 of 50 SL ones "MCC 02RG20" fail. I've had similar results with PlayO, only more extreme, 20 for 20 DL failures "RICOH00-?00-01" and maybe 4-5 out of 50 for their SL ones "MCC 03RG20" and half of those were from a BSOD during a burn.
-
The 'Device Buffer' in the Verify stage is not the same as the one in the Write stage.
In Write, the device buffer is the drives internal cache - ImgBurn has no control over it. The drive will use its cache as it sees fit and it often empties when burning due to WOPC - that's what's supposed to happen.
In Verify it's the programs internal buffer that's caching the data read from the drive - where the 'Image Buffer' is then caching the data read from the file. The data within these two buffer is what gets compared.
As reading from the HDD should be far faster than reading from the CD/DVD drive, Verify mode's 'Device Buffer' should remain on 0% and the 'Image Buffer' should be on 100%.
Is there any way to turn off WOPC so I stop getting errors on my DVDs.
99% of the time it results in damaged PGC data.
That's often the case but sometimes there's a small amount in the cache which is confusing
but I usually only do very low damnding operations during burning and I do moderate activities,
like going here or checking e-mail during verification since it doesn't risk damaging data stored
on the DVD.
At 2X the WOPC only drops the internal device buffer to 60-70% but at 4X it drops to 7% and
then the drive stops burning for about a second then the light goes on again. With the Lit-On
drives it happens ALL the time so the drive slow to a crawl. They are crap. My NEC will only
do it half a dozen times not zillions like the crappy Lite-On drive.
At this point I'd pay triple for a Plextor if I was convinced they didn't have the same crappy
design or if they simply used a 8 or 16MB buffer and not a microscopic 2 MB one. I suspect
it would solve everything since it works fine at 2X. A 2 MB buffer simply doesn't hold enough
data to allow it to not empty at 5.54 MB/sec., an 8MB, or ideally a 16MB, buffer should hold
enough data just like 2MB does for a 2X burn.
As you may guess by now I find may products to be designed by idiots. ImgBurn is an
exception. DVD ReMake Pro is an even better product. It's almost magical. DVD burners
are mostly junk but then Windows is crap itself. Every week there's another zillion bugs.
-
If you get a BSOD you should be able to examine the memory dump in WinDbg and find which driver is causing the issue.
Yeah, I just reactivated all that. I'm sure now that it's set up it will take a week to crash again, which is a mixed blessing, I guess. Then again, it may crash tomorrow. Also, I do not do 4X burns anymore so I'm having problems locating an OLD .IBG.
I do know that usually when Windows 2003 starts again I often get messages about PowerDVD having crashed but I'm not sure it that old stuff from weeks ago I never sent or what. I've turned those but turn on the dumps. I know that having ImgBurn eject a DVD when it finishes helps because sometimes a DVD would finish and the it would be read by the system and PowerDVD would then try and play it via Windows F'g annoying autoplay. S#!+ I F'g hate that Damn annoying "feature" every time I stick a disk in it statrs pestering me!!! I check the always box and select DO NOTHING EVRY TIME but the retarded function NEVER remembers. Anyhow, that usually leads to a BSOD. I have NOTHING cause BSODs on 2003 but F'g DVDs.
-
Hmm I hadn't really thought about that particular situation/issue DoIt.
All it does before deleting the image is:
1. Check the last burn was successful.
2. Check there are no other queued burns that need the image.
It doesn't take into account failed burns within a multi copy burn that you may or may not want to retry.
The image deletion code is in a different part of the program (and it's run first) to the bit that asks if you want to retry failed burns.
So it's not a case of it failing to check properly, just at the time when it does check, so far as the program is concerned, the image is finished with.
SAO is the naming scheme for CD, for DVD it's DAO. That's just what the MMC specs say. They're the same thing in reality.
"It doesn't take into account failed burns within a multi copy burn that you may or may not want to retry."
"The image deletion code is in a different part of the program (and it's run first) to the bit that asks if you want to retry failed burns."
That's a bad design. You should swap the order of execution.
It seems that the problem is you do not redo the first disk so the count is wrong. You have only 1 successful image of 2 then
you simple should NOT advance the count when a verification fails. You should wait until a verification passes and returns a passing value when that condition is set on before advancing to the next image. Instead you apparently do so when the burn finishes. It's bad logic. I do programming myself and bad logic is the cause of most serious bugs. I suppose if you were designing a washing machine you'd start filling it with water once the first quarter is placed in the machine expecting the others will go in as well. What we have here is someone only put two quarters in for a $1 washing machine and you went ahead and said that was "close enough" and ran the wash anyway. It's bad code, period.
Actually SAO mean Session At Once. It does NOT finalize a CD like a DAO would. A DAO burn burns one session and then finalizes the CD. A SAO burn burns one sseesion and does NOT finalize the CD so more sessions can be added to the media.
This also means once can actually remove data from the index for the next session and then finalize the CD with the data in the CD but not accessible when loaded into windows. Believe me, I've done dozens of multi-session CDs at this point. You can even do Multi-Session CD-DA CDs where a CD player will only see the first session but a CD-ROM drive will see more tracks that a CD player will not. I've done it. You need either an older version of Win-On-CD to do it.
-
As it (kinda) says, pxhelp20 is part of the driver system installed by software using the 'Sonic Solutions' I/O interface. LOADS of programs use it and I see it all the time (even on my own PC's). It won't be the cause of your buffer emptying all the time.
Do you have an IBG / DVDInfoPro screenshot showing what you're seeing?
As I've mentioned several times before, it's normal for the buffer to empty out every so often (due to WOPC). This is especially true on NEC drives.
From your previous post I'd have to say you have much bigger issues! It's certainly not the drives at fault here. I've got a cupboard full of drives and I've never had buffer issues on any of them. You're barking up the wrong tree.
I click on the Upload button but all I get is the swirling pattern and no activity.
-
1. It should already work like that. When it's done burning, the 'Close Program' and 'Shutdown Computer' options kick in.
2. See above.
3. Save queue on close is already an option in the settings.
4. It does that already
5. The option to put a job on hold could indeed be useful. Currently if I don't want to burn something, I just remove it from the queue!
6. I would expect the majority of people to either be in favour of always ejecting discs or not ejecting them. I can't see why you'd want to burn 10 different images and only have a few of them eject the disc.
7. Not likely any time soon.
1.
It does, it's under Verify. He can also just manually check the boxes if he wants,
after it starts, and walk away. I usually leave them off just like DELETE IMAGE and
then manually turn them on, during a burn, if desired.
6. Agreed
7. Personally, I'm suspicious of anyone who needs to burn 10 copies of the same DVD.
-
burn proof has always worked for me so I really dont know why you dislike it so much its a positive thing and with it enabled you dont make coasters when and if the burffers empty .
If you hate Burnproof so much then go Tools ,Settings ,Write and remove the check from "enable burnproof".Other than checking the boxes that open the tray after read ,write and verify all my settings are default IMGburn works best with defaults
Nec makes a very good drive in my opinion and my 3500 just makes great burns time after time I haven't bought another newer one because I'm not going to fix whats not broken I also have a 2500 and it works perfectly also and a Sony dru 510A my first burner and it also turns out beautifull burns .Its a real Sony when they were actually making their own drives Lite ON makes drives for them now that they rebadge
Its important to keep your firmware up to date so that it supports the latest media codes and the other little tweaks they make with the newer versions
the discs that you say burn ok and can't be read with your player I dont believe is the fault of burnproof ,its usually down to media ,overcompression or a player that might be old enough to not support some of the formats ,its suggested that you booktype your dvd's to dvd-rom for compatibility but the 3500 wont support booktyping SL + meddia although you can use a cracked firmware which will support it www.liggydee.cdfreaks.com
If you can burn an ISO and then verify it OK then thats checking the burned disc against the ISO on your hard drive ,you should take note of where on the burned discs you have a problem and then Download Daemon tools ,its a virtual drive which you can mount the ISO in and watch it and see if the errors are in the ISO itself
I wish I had a 3540A, everything I can read shows they didn't have the buffer problems of the 3550A.
The best drive I ever had was a DRW-3S163 which burned 6X perfectly, the buffer never got empty,
but the Lite-On drives I tried that they market under their own name are crap. The buffer empties
and it slows down to 1.2X or some junk. Utter garbage! I've tried the SHM-160P6S, SHM-160H6S
AND SHM-165H6S and they're all junk. Interestingly, the DRW-3S163 weighs 4 pounds instead of
the 2 pounds of the other drives. I suspect it uses metal parts instead of cheap plastic. Also, the
Pioneer DVR-110D fails to keep it's buffer full as well. Only the DRW-3S163 seems to respond
and fill it's buffer before it gets too empty at anything above 2X. So, I'm stuck using an NEC
3550A at only 2X which can manage to keep it buffer full. This seems to happen under Windows
2000 Pro., 2000 Adv. Server, XP and 2003. I currently don't have XP/2003 x64 installed but I
expect it to be a similar problem.
-
If you look at the top blue line you'll see that your CPU %usage was at 100% whenever the device buffer goes mad. So the two are linked, you just need to find out what's causing it.
Next time it does it, bring up task manager and find which process is using all the CPU time.
As for filter drivers, you should remove this one: siremfil.sys
It's known to cause problems.
Upper Device Filter: redbook
Device Object: NERO IMAGEDRIVE2 SCSI CdRom Device
Lower Class Filter: PxHelp20
Driver Name: redbook.sys
File Location: l:\win2003\system32\drivers
File Description: Redbook Audio Filter Driver
File Version: 5.2.3790.1830
Product Name: Microsoft? Windows? Operating System
Product Version: 5.2.3790.1830 [5.2.3790.1830]
Company Name: Microsoft Corporation
Driver Name: pxhelp20.sys
File Location: l:\win2003\system32\drivers
File Description: Px Engine Device Driver for Windows 2000/XP
File Version: 2.03.28a [2.3.28.0]
Product Name: PxHelp20
Product Version: [2.0.0.0]
Company Name: Sonic Solutions
Should I remove pxhelp20.sys and what they heck does it do?
Also, HOW do I disable if that's appropriate. I'm sick of my buffer
getting empty when I use 4X or faster.
OOPS! Wrong device but same question ...
Upper Device Filter: redbook
Device Object: _NEC DVD_RW ND-3550A
Lower Class Filter: PxHelp20
Lower Device Filter: imapi
Driver Name: redbook.sys
File Location: l:\win2003\system32\drivers
File Description: Redbook Audio Filter Driver
File Version: 5.2.3790.1830
Product Name: Microsoft? Windows? Operating System
Product Version: 5.2.3790.1830 [5.2.3790.1830]
Company Name: Microsoft Corporation
Driver Name: pxhelp20.sys
File Location: l:\win2003\system32\drivers
File Description: Px Engine Device Driver for Windows 2000/XP
File Version: 2.03.28a [2.3.28.0]
Product Name: PxHelp20
Product Version: [2.0.0.0]
Company Name: Sonic Solutions
Driver Name: imapi.sys
File Location: l:\win2003\system32\drivers
File Description: IMAPI Kernel Driver
File Version: 5.2.3790.1830
Product Name: Microsoft? Windows? Operating System
Product Version: 5.2.3790.1830 [5.2.3790.1830]
Company Name: Microsoft Corporation
-
If you look at the top blue line you'll see that your CPU %usage was at 100% whenever the device buffer goes mad. So the two are linked, you just need to find out what's causing it.
Next time it does it, bring up task manager and find which process is using all the CPU time.
As for filter drivers, you should remove this one: siremfil.sys
It's known to cause problems.
Upper Device Filter: redbook
Device Object: NERO IMAGEDRIVE2 SCSI CdRom Device
Lower Class Filter: PxHelp20
Driver Name: redbook.sys
File Location: l:\win2003\system32\drivers
File Description: Redbook Audio Filter Driver
File Version: 5.2.3790.1830
Product Name: Microsoft? Windows? Operating System
Product Version: 5.2.3790.1830 [5.2.3790.1830]
Company Name: Microsoft Corporation
Driver Name: pxhelp20.sys
File Location: l:\win2003\system32\drivers
File Description: Px Engine Device Driver for Windows 2000/XP
File Version: 2.03.28a [2.3.28.0]
Product Name: PxHelp20
Product Version: [2.0.0.0]
Company Name: Sonic Solutions
Should I remove pxhelp20.sys and what they heck does it do?
Also, HOW do I disable if that's appropriate. I'm sick of my buffer
getting empty when I use 4X or faster.
-
As mentioned in a previous post, there must be some issue with sending data to the drive then - and it's out of ImgBurn's hands.
Check your filter drivers using the free tool from http://www.bustrace.com and remove any rubbish you find.
You can put it's info in the clipboard and paste it on here if you like, then we'll help point out the bad ones (if there are any).
You really don't need a 256MB buffer, as you've seen, normally when there are problems it's the 'software buffer -> drive' communication that suffers, not 'hdd -> software buffer'. The default values work best, that's why they're default! I have 4GB of RAM and I still only use a 20MB one (or 40MB in the newer version of ImgBurn - as yet unreleased).
Again, if you can get us a DVDInfoPro screenshot of the 'ImgBurn Graph Data' it would help use to see what you're seeing. NEC drives perform WOPC as they burn so I'd expect the device buffer to drop to 0 every now and then anyway.
bustrace sucks!!!
You need to be a F'g corporation with a web site to even download their damned demo !!!
-
i know this thread is old, but i just had the same problem. except with a cd.
i was burning a cd at 8x on my laptop with an NEC ND-6650A dvd burner.
device buffer was a solid 0%, image buffer was 100% with a very stable burn speed, and perfectly burnt cd.
Actually, when the burn progress hit about 80%, the device buffer shot up to 100% till the end of the burn.
It was on a fresh install of Windows Vista, which I have used before and never had this problem.
anyway, GREAT program!! It is the only burning software that i use for the most part.
Thanks.
I've seem similar odd behavior using an NEC-3550A under Windows 2003. I haven't bothered
keeping too many details. Also, sometimes it will sit at some odd value like 30% and then later
on it will shoot up BUT this odd behavior seems to occur during the verification stage NOT during
burning stage, as I recall.
-
Oh right, I thought nvidia had their own sata controller, I didn't realise they were using Uli chips, sorry.
You can try the 6.2.2.1 driver from http://www.techpowerup.com/downloads/408 but that's all I can suggest.
I've been using an SATA drive all day on an nForce 4 AMD board without any issues so it's not a general SATA thing.
I've never had an issue with any SATA drive but but NEC-3550A is always the source of BSOD's which seems to occur every few days in the middle of making a DVD (using ImgBurn or Nero), never on CDs (usually Nero) and usually during verification, especially when late in the process if the drive is spinning over 10X while verifying (in Nero or ImgBurn). Using the limited speed option of ImgBurn has cut way down on BSODs but they STILL occur but ONLY with DVD disks. My SATA HD's run and 40-120 MB/sec. depending on the fragmentation (obviously from my performance speeds I do defrag fairly often), and whether the other HD is on the other SATA sets, I have two (4 SATA-I and 4 SATA-II) on the MB (only 2 SATA-II HDs in use) plus a Promise Tech. RAID-5 card, or if the other HD an older PATA drive, etc. I also use a 1.87 GHz Athlon 64 so I doubt it's the CPU being too slow either.
-
It's not a unicode application so this is to be expected.
Also, on a udf only image, only the udf field is available when I change the volume label. The other two are greyed out and the edit boxes contain 'N/A'.
So either it's something I've fixed without knowing it or whatever's making your udf image isn't actually making it udf only.
Will ImgBurn ever support Unicode ?
I want to burn with unicode volume labels.
Nero apparently can handle Unicode filenames and volume labels right. However, Nero CANNOT go pass its 16 character limit for volume labels. I've tried finding other software but its the same, either 16 character limit or no unicode..and I am using CJK languages and I'm making DVD/UDF images. The contents also includes unicode filenames.
It would be nice if unicode is supported.
Anyone have any recommendations to help me with this ?
I've had ImgBurn change filenames when trying to make DVD-ROM disks, e.g. making an installer DVD from multple installer CDs using Orca, so I use Nero to build the image without mangling filenames but it has crappy handling of VOLUME names so I then have to use ImgBurn's ISO Tool to fix the volume's name to match the value that installer is looking for since Nero will screw it up. These are mostly ISO/JOLIET volumes but the same problem exists with UDF where it truncates volume names.
-
I never choose delete image for that reason (failed burn) although its been years since I made a coaster .When I'm happy that all has burned fine then I go back to my HD (D ) and delete from there ,its easy enough and you can delete 10 iso's in less than a minute
Apparently, since it fails to properly check when making multiple copies I now have to do the same.
P.S. ? How come CD?s use SAO instead of DAO???
-
It's doesn't delete it if the burn fails.
....but, a failure on the sync cache / finalise disc bits is not considered a burn failure.
Hence why it says operation completed successfully in the log.
That's the bit I need to fix, not the delete bit so to speak.
Thank you for the clarification. I'll consider this a caveat for now.
BTW, I never check the 'Delete Image' button unless it's an image I can recreate, so I was more of an annoyance that the process seemed to fail but deleted the image. Most of my 'test' burns use 'Delete Image' since I'm always riding on the edge of a full HD. (Which is silly, since its 500 GB
)I just wanted to notify the appropriate parties should there be something that could be looked at, improved, or at least documented here in the forums.
Cheers on the excellent proggie!
It fails to properly check the status of all burns associate with an image before deleting that image when burning multiple copies as well !!!
I've had it delete the image when I'm doing multiple copies and there's a failure. Here's EXACTLY what happens!! It will fail on the first image; it will then burn the second copy. If the second copy fails it will not delete it but if the second copy goes OK it WILL delete the image!!! ALWAYS! It does NOT matter what media or drive is involved! It's a logical bug. He only checks the last burn and not all burns before deleting!! It will then ask if you want to re-burn copy 1 you say yes and it queues up to burn it but it has already DELETED it so it FAILS since the image NO LONGER EXISTS since it was deleted by ImgBurn itself. I've had this happen consistently. NEVER use the DELETE IMAGE option when making MULTIPLE COPIES of the same image until he fixes the bug!!!!
It's particularly annoying since I once do multiple copies of important material.
-
The program is called 'ImgBurn'. By the very nature of that, it burns disc images.
If you have a bunch of files, they're NOT an image, hence you have to 'Build' one.
Sorry but it stays as it is.
So a full-on finalized VIDEO_TS folder doesn't count as a Writeable thing?
I appreciate your product, but your attitude seems to be kind of stand-offish.
NO! It does NOT count as burnable anymore than a web page!
You burn images! It's not called VideoFilesToDVDMagicalBurner for a reason.
You are simply ignorant. However, an image can then be directly burned to
a device instead of a file but it already does that.
-
Someone was nice enough to explain about how to use BUILD to create a VIDEO DVD from either a list of VOB files or a VIDEO_TS folder. If they had not, I never would have figured it out because just like an ISO burn, I expected to find it under the WRITE area. I expected to see it there because the files were already created and not in an ISO. So I thought in my mind "If it would be anywhere, it would be in the Tools area under the WRITE mode because that is where the CREATE DVD MDS file" is.
What about adding to the TOOLS menu an option for CREATE DVD VIDEO DISK or something, and then prompt the user to select the existing VOB/IFO/BUP project files or a VIDEO_TS folder containing a compiled DVD Video project that is ready to burn to disk?
Maybe from the SOURCE box there, you could add an icon right next to the BROWSE FOR FILE and QUEUE icons that would say "DVD Project Files or Folder" or something like that? You know, to make it more obvious?
I don't really know all the ins and outs on why it is under the BUILD area, but I assumed (I know, dangerous to do) that because the project was already built, it would seem more logical to put it under the WRITE area, which would also make it more visible because it would be an option right there in the TOOLS menu, spelled out clearly so that folks would know instantly "Hey, that option means make a DVD Video from files on my drive".
Maybe I'm not explaining it well, but I just wanted to get it out there for discussion.
I hope that is ok. Not trying to criticize, just honestly trying to offer a suggestion for maybe making it a bit easier for noobs and folks to grasp.
Thanks - I look forward to some discussion.
What a complete waste of time! Just create a directory and put the VIDEO_TS directory (with the files in it) in that directory and go into Build Mode and then use the Browse For A Folder icon and select that directory.
There's a tab on the left where you set the disks label, etc. I've done it zillions of times. There's nothing special about a DVD-Video disk other than the file names and location. Of course, the files that are included have certain specifications themselves.
-
Just found other links in forums covering this. Would be awesome, but seems unlikely.
Awesome program though
I came across this program because I was searching for something with a Burn Queue.
So far, its worked wonderfully for any images i want to burn, but would like to see it go a step further
It would be great to throw a VIDEO_TS folder at the Queue, add a Volume name, and then have it burnt off as a video DVD
Just a thought.
Will be making a contribution for sure in the near future
I'm not sure what you are trying to do bt it pretty mcuh already does what you want but in two simple steps and you can always set the target to a device and not an image while in Build mode if you want to cut it down to one step.
-
Is it possible to have imgburn cycle the disc after a full erase?
I ask because i had to do a full erase on a DVD which imgubrn was reporting as being 600 or so MB. However after the full erase it was still reporting it at being 600 or so MB, after i cycled the tray it was again reporting it as being a full size DVD.
Yep, it already it there.
-
do sony dvd's in the US have French labeling on them like in Canada.
Mostly they are in English...sometimes with the French and Spanish alongside...
mostly depends on where you buy them.The only effective way to alter the burn speeds is to patch the drives BIOS.
There are several such programs out there that do just that. You can than
remove the higher burn speeds for that disk ID type and erapply the patched
BIOS to your drive. I've had to patch a Toshiba to have it use a faster default
speed of unidentified media since it was burning newer 8X and 16X media at
1X and not 2X or 4X (it's an older 4X drive) and I patched my 16X NEC so it
can do bit setting just like Lite-On drives. It's BIOS recognizes over 900 disk
IDs.
-
I defrag my drives quite frequently (if I don't set a schedule to do it for me), but what I mean is that I don't take note of which files are fragmented and which aren't.
I do tend to do drive c: a lot more often than my other drives though and I never use c: for building / burning images.
So long as all the pretty little blocks are up one end of the drive I'm happy
I defragment anywhere for daily to every thre months depending in the partition.
In general I'd recommend you do it at least monthly and if you use a good program
like Perfect Disk you can do it weekly (since most data will already be optimized) on
drive partitions you use regularly.
I only defragment my ISO target partition more than weekly. I don't want to be
burning from a fragmented image file. Perfect Disk is especially nice at lining up
the blocks for contiguous sequential access and leaving an unfragmented space
at the end of the disk for new image files to be stored without them getting all
fragmented. Diskeeper is HORRIBLE at defragmenting free space.
-
It actually told me defragging would be a good idea..... which I did. 90 minutes later and the drive looks the same now as it did before. I knew there was a reason I just don't bother anymore.
1. Your drive will defragment better IF it has more free space. The window defragmenter will not even do anything unless a drive has 20% free space.
2. Buy Perfect Disk 8.0, it's 100 times better than what you get from Microsoft.
P.S. - I do not work for them.
Burner Buffer 0%
in ImgBurn Bugs
Posted · Edited by Dolt
It a crappy NEC 3550A which came with nothing. Oddly the BIOS recognizes over 900 media signatures instead of the usual puny 50 - 100 of most drives. I was able to get a patched version so now it's region free and more importantly I can set the Book Type via the NEC tool in ImgBurn so I can now burn playable DVD+R media but still no WOPC utility that I know of. It's excellent with CDs and burns at 16X and 48X with perfection but it's junky when burning DVDs and can only handle 2X due to the crappy WOPC always slowing it down.
Do you know of such a utility for a Lite-On Drive. Those things are useless. It's calibrating every billionth of a second and runs as slow as heck. My pioneer 110D is crap too. I miss burning at 4X since 2X take eons by comparison. Even 2.4X DVD+R disks are much nicer than s sluggish 2X burn.