-
Posts
30,521 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LIGHTNING UK!
-
The non-working disc doesn't appear to have been closed/finalised properly. It's status is still 'Incomplete'. ImgBurn never mentions anything about 'Lead-Out', you're getting confused between different programs. 'Closing Track / Closing Session / Finalising Disc' are the terms used by ImgBurn.
-
What's your CPU% usage at when burning?
-
Ok, it turns out that all the PECompact compressed ImgBurn.exe files will error out with that same access violation. UPX compressed ImgBurn.exe's do not suffer the same fate but then they won't run on Windows 98! So really, that only leaves me with 1 option.... to stop compressing the exe until either of the problems are fixed.
-
No, this is not something ImgBurn does.
-
Compatibility problem with the build function
LIGHTNING UK! replied to erco's topic in ImgBurn Support
There is 1 little bug in the build code but it only affects discs with lots of files in a folder - and only certain players probably care about it. If you're just building a DVD Video with a couple of VTS's, you wouldn't run into it - in which case, it's hard to say what the problem is. The bug has of course been fixed for the next version. -
It would help if you told us what YOU believe the problem is that you're having! Do you get any info in the panel on the right that you can copy + paste? How about some text from the statusbar, what does that say?
-
I see there that you've got a couple of system hooks. If you can live without the AOL stuff, remove it. Same goes for the Plaxo rubbish (if you can find it to remove it!) The AV after... ... should NOT be happening.
-
Ok, at the point you're getting to, the program hasn't really loaded. In the 'Debug' menu, click 'Go' (or just press F5). Once you've done that, loads more stuff will scroll up on the screen.
-
You might need to start up a debugger - i.e. Microsoft's WinDbg and then load ImgBurn from within that. It should capture where the error is coming from.
-
Come back when you're a real person and not a joke spamming bot. Thanks.
-
My mate's had nothing but problems with that LiteOn drive too. I have the LH-18A1H model and since performing the initial firmware update, mine has been fine - it wouldn't burn MCC's before that. Oh and the filesystem is only wrong if it's a DVD Video disc - which I'm guessing it's not? If it is a DVD Video one, stop using the program that created/built the iso in the first place - it certainly doesn't look like ImgBurn did it.
-
Changing the order might have meant the OS had to redetect the drives - and hence fixed DMA.
-
It means your drive can't initialise the disc - this is an internal function and nothing to do with any software. Either the disc is just screwed or your drive's firmware can't cope - try updating it.
-
VCD/SVCD's contain multiple tracks and ImgBurn only supports images with 1 track / session.
-
It all really depends on where the errors are. If the drive has corrected some data in the EDC/ECC regions, it's done so because it's wrong in the image. However, the CD/Player might actually require incorrect data in those regions and so the 'fixed' disc might not work as expected. To make the drive burn uncorrected data you have to make it use the 'RAW' write type - which ImgBurn does not do/support.
-
When is doesn't list any supported write speeds, it's normally because the media id isn't in the firmware table at all - i.e. it has no idea HOW to burn that media (it's not supported).
-
Just one more.... I found some leftover debugging code in this newer 2.2.1 release that was stopping the emails from being delivered.
-
Ok, I've just cleared out the SQL tables so you can all start again from scratch now!
-
@zacoz, He means the 'count' of how many discs ImgBurn has burnt. @Peter, You're quite right, the program reads the current count from the registry when it starts and then writes back the new count at the end. If you run 2 copies of the program at the same time, whichever one you close last will be the one who's count is stored in the registry / ini file. The stats are not important enough to bother messing around with, they're simply there as gimmick.
-
It's a burning tool....so probably not, no.
-
Basically, Samsumg (using the identifier 'TSSTcorp') and LG (using the identifier 'HL-DT-ST') drive owners will automatically (and by default) have all their +R / +RW / +R DL media changed to look like a DVDROM disc via bitsetting. It's an ON/OFF option. (Again, ON by default) Either the program tells the drive to change the book type to DVDROM or it doesn't and the drive will do whatever it had already been told to do by other programs (or by ImgBurn's 'Change Book Type' screen). (Note: +RW bitsetting isn't supported by the LG drives though - so far as I can tell) The booktype commands are sent to the drive before each and every burn the program makes.
-
Yup, it sure will.
-
I found 5 mins to implement it, so DVDROM booktyping is now automatic for Samsung and LG drives - as they're the only ones that don't remember their settings.
-
I've got some 2-3x Panasonic ones and some 5x Verbatims. Both seem perfectly fine to be honest mate! What I'd really like are those super fast (10x or 12x, can't remember!) discs - but they're not available in Europe Anyone want to send me some?