Defenestration

You guessed right Compared to a 3.5" desktop HD, a laptop HD drive (even though it's 7200rpm) seems to struggle a bit when doing a few things at once (shame my system doesn't multi-task as well as me )

Hi LUK, I trust you've had a good weekend so far. Will the new buffer underrun feature (ie. if buffer empties during burn, don't resume burn until buffer is full and Avg Disk Queue Length is 1) also work during the Verify Stage ? I know it won't improve the burn quality, but the verify stage can also be very disk intensive and so this feature would come in handy to stop disk thrashing when other apps are making heavy use of the disk. The other benefit is that it may also speed up the verify stage during this scenario.

=))

Atthay ancay obablypray ebay arrangedway, utbay itway illway ebay Englishway onlyway otay artstay ithway. Ethay aimway ofway ethay uidegay isway otay ollatecay allway elevantray informationway ogethertay inway away inglesay esourceray, includingway ebway inkslay. Oinkway!

If I had to recommend one, it would be UltraISO (http://www.ezbsystems.com/ultraiso/) One-time purchase (as you get lifetime upgrades), and great support (eg. a few minor suggestions I made were implemented and made available within a few hours.)

I hope so as I've got no nails left LUK - I've got a basic CHM skeleton with a few of the sections done, although it still needs a fair bit of work. I can send it to you if you like so you can add the relevant menu item and function call to ImgBurn.

UltraISO has a similar format called ISZ (ie. ISO Zipped), but only UltraISO can read it.

I don't have access to the new version 2 which has some new features/options, and wanted to get it ready so it can be included when version 2 is released.

OK, I'll probably use Cynthia's guide as the basis, if that's OK with her. Some updated screenshots of any windows/tabs that have changed since 1.3 would also be handy when you've got a spare moment LUK.

Happy Birthday Cynthia! Many Happy returns! Make sure it's a great one! A time to wish only comes about once a year, so make it a good one

I thought I'd post this in a separate thread so all relevant info can be correlated in one place.... I don't expect any praise for doing it, and to show everyone I'm not just after blood, I'm willing to put together (and maintain when needed) an in-built CHM file for ImgBurn. If it's OK with the relevant authors of the info (and LUK, the almighty himself), I will base the help file on the FAQ, Guide, and posts from the forum. I would appreciate any descriptive information on particular features/functions of ImgBurn that will then be used in the help document, with the aim of producing an informative guide on how to use ImgBurn. It might be basic to start with, but I envisage a reference guide on all functionality, coupled with tutorials for particular features. PS. Has anyone noticed.... England are shit at penalties! PPS. Bet on France to lift the World Cup 2006!!

One to add to the grocery list...... An app called CDCheck (http://www.elpros.si/CDCheck/) has the great ability to check a disc for readability errors, without the need for saparate hash files (ie. you can insert any disc and check it for readability, without any previous knowledge of that disc). I often use this on "VIP" discs to verify that the all the data is still readable. I am not that bothered about the extra functionality offered by CDCheck, since ImgB/urn already offers the MDS functionality. This feature would give the option of checking aall discs.

OK. I apologise if I came across as overbearing - that was not my intent. I must've forgotten to take my medication

Sorry I've given you that impression, and just to live up to your impression of me I need to say "Your loss"

I understand it's a hobby and appreciate the amount of work LUK puts in to developing such a great application, as I have said before. It seems odd that an "old timer" does not even know what this forum is for - you say it is only for support of those who use ImgBurn, but if that's the case then why are there sub-forums for posting/discussing bugs and suggestions ? You say above that ImgBurn is the brainchild and hobby of LUK, but yet you come across as considering ImgBurn to be your app which no-one else is allowed to comment on. Without change, ImgBurn would not be what it is today! Where did I say I didn't like the way LUK codes ? I didn't! Where did I say I don't like the compiler he uses ? I didn't! I merely suggested the RAM usage may be reduced by using the Win32 API (which can be done with Borland) or WTL (which I don't believe can be done with Borland). You'd be great to have in a game of Chinese whisper's. Read/Hear one thing, and it suddenly has a completely different meaning. I have posted my suggestions (and possible ways to implement it on occassions) because, even though you don't want to hear them, the author of ImgBurn, LUK, apparently does. I can honestly say I'm glad you are not developing ImgBurn! Maybe you're feeling insecure from someone else coming on these forums and "taking your thunder", and if that's the way you perceive me then that's your problem. Jump on the bandwagon why don't you If you never ask for something, you may never get it! Forums are places for open discussion (not that you'd know that if you listened to Shamus).

Your point being ? I know that's how a drive works. My original post (if you actually bothered to read it) was about trying to improve the quality of a burn during times of high disk activity. I can't see the problem of building some protection against intermittent burning into ImgBurn so that it temporarily stops requesting data until the free-for-all with the hard-disk is over.

I can write a program that prints "Hello World" I think it would be pointless to write another burning app when LUK has already done such a superb job with ImgBurn. I would consider helping LUK out with the programming side of things if he so wished, although I couldn't guarantee how much time I could spend working on it. While ImgBurn is already pretty light on RAM resources, I think it could be improved by switching from Borland windows framework to Win32 or WTL (probably the better option, but I think it only works with VC++ at the moment), but doing this is certainly not a necessity, more a nicety. Other than that, the only new features I would like to see in ImgBurn would be 1) Burn files/folders (- being implemented in version 2) 2) Multi-session support for RW discs 3) Copy unprotected CD/DVD, with ability to specify number of copies (ie. create ISO image and then burn it X number of times). It shouldn't just use the files/folders, instead copying sectors so all information is retained (eg. boot information with bootable discs) 4) Support for burning Audio CD's 5) Blue Ray/HD-DVD support (don't have a drive now, but will no doubt have one in the future) and maybe a couple of other things I can't remember at the moment. That would probably suffice for me and allow me to get rid of Nero. I'd be interested to hear from LUK what his plans are for ImgBurn and how far he intends to take it.

Even better

I most certainly have This is a more minor point since it's unlikely users will uninstall it very often, but if I use software a lot then I like to report any bugs/suggestions so I can get the software working to my satisfaction. Do you not find that the burn continues intermittently (ie. the LED on the drives flickers on/off) so, while it will finish the burn successfully, it will take a lot of burn cycles ? The improvements I suggested were aimed at reducing the number of burn cycles (ie. zeroless links required) during times when the source disk is under high load, in the hope that the burn quality would be increased. BTW LUK, would I be right in thinking that setting these new values to 0 will effectively disable this new feature, so the original behaviour can be obtained again ? While I will keep it enabled most of the time, I will try to do some test burns during high disk load to see if the quality is indeed affected by increased link stages.

Just done a few tests, and it is only created after it's been run for the first time. BTW, DVDInfoPro does not do a very thorough uninstall as it leaves behind HKEY_CURRENT_USER\Software\SWN in the registry and also the DVdInfoPro program folder.

I'm also using DVDInfoPro 4.61.4. Maybe it only creates the key after it's been run for the first time, and not during installation.

I agree, specialy when it's just because "you can". Indeed. I also don't want IB to become bloatware adding useless features.

You may already be aware of this, but I thought I'd let you know about a security update to IPB. The version number stays at 2.1.6 but has a HTML injection flaw fixed. http://forums.invisionpower.com/index.php?showtopic=219126

Give me something that can't be broken, and you can be sure I'll break it. It's a gift I possess.

Since I'm the only one who seems to suffer from these problems, maybe I can get a copy to test this new buffer underrun feature ? Well..., you can't blame me for trying.