Posts posted by Night_Raven
I second the suggestion. If safety is your concern, maybe there can be confirmation dialog window when such an option is checked, or maybe the checkbox could appear only after it's enabled somewhere in the settings. Still, an option to delete the files/folder being burnt would be a nice feature.
It's located in your \ImgBurn\Sounds folder (by default it's C:\Program Files\ImgBurn\Sounds).
Personally I couldn't disagree more - especially with the first post which seems way OTT to me. This is LUK you're talking about, fgs, not some sniveling little tosser out to make a quick buck. The whole community owes him big time, in my view, for all the years of work and effort he's put in, and he certainly deserves better than what I've read here.
I don't know his reasons for the Ask toolbar, but whever they are, I trust the bloke to do the right thing in the situation he's in.
I'm well aware who we are talking about and realize what he has done for the community. And that's exactly why it hurts more than usual. If it were some "sniveling little tosser out to make a quick buck" than it would be expected. But coming from LUK it's like out of the blue. One of the last things to have ever crossed my mind would be an ASK Toolbar in ImgBurn.
Including a toolbar is a rather sneaky trick. It's based on expoloitation of the click-happy mentality of the average user who just clicks Next until the installation is done. As I said, it's something I would've expected from other lame excuses for software developers but not from LUK. If someone had told me about the ASK Toolbar in the installer, without me actually seeing it with my own eyes, I would've said "Yeah, riiight, an ASK Toolbar in ImgBurn...".
if you want the ASK bar removed, DONATE to ImgBurn.....
As a matter of fact I have, although indirectly. I'm asked from time to time by a friend which program I would like so he can buy it for me, as a present for some favors/work I do for him. One of those times I gave it a rather long thought and decided that I don't want him to buy me a license for a paid product, and instead to donate the same amount to ImgBurn, which he did. It was $30 or $40. With the risk of sounding impudent I consider this to be a fairly nice donation. Well, it's only safe to say I wouldn't consider any more donations. Why? Because this whole ASK Toolbar-thing has shaken my trust a bit and has disappointed me. Also with the ASK Toolbar in place there is no need for donations, as the toolbar will be a much better source of income than donations.
Why would I want to donate to someone who already has enough money AND he gets it via a not-so-ethical-and-nice means? Also why would people want to donate to a program whose author doesn't care very much what the users want? The latter isn't here to say he must or should implement every request he gets. LUK has every right to refuse to change his software because it is exactly that: HIS software. But doing things this way also means fewer donations. It comes with the territory. Either one goes the more commercial way to please users/customers so they'd be more willing to donate or one does only what he/she wants to do and accept the consequences of fewer pleased users and thus fewer donations.
Also... what guarantees are there that if donations increase the toolbar will be indeed removed?
Edit: removed a redundant word and fixed some spelling mistakes.
For the record ASK Toolbar isn't that much a piece of malware, as it is more of a piece of crapware. It doesn't actually do damage. Still it's crap. And CCleaner has both a version with ASK Toolbar and a version without. The latter is called "slim".
As far as the rest of the post goes, I reluctantly agree. So few programs are left that haven't given in. The author of WinPatrol, Bill Pytlovany, had been offered twice to include ASK Toolbar in his installer, and both times he had rejected it. Tall Emu, authors of Online Armor, had also rejected an offer.
I myself was quite happy that there was a program that was not just effective (uncompromising product that is straight to the point, like a professional silent assassin or something) but also clean of all kind of crapware. It basically stood as an example to other products. An emblem, a hero if you will. In this ocean of software that is either bundled with crapware, or just badly written,... or both, there was ImgBurn - one of the few products that served as a beacon of light, if I can put it like that. Now the waves of this ocean have managed to bring down this beacon and extinguish its light.
Yeah, it sounds kind of corny, I know, but it expresses my feelings well. I'm not trying to change anyone's mind on the matter (LUK's in particular) as it's already done and the decision has been made. I was simply trying to get this off my chest, as it really saddens me. I'm still using, and most likely continue to use, ImgBurn as it's still the best. I'm just disappointed it had to come to this.
I guess donations weren't enough. I myself have donated (even though indirectly) but there seems no need for donations now, even if the button does remain there. ASK Toolbar can supply all the money LUK/ImgBurn could ever need.
A good idea and generally good points. Here a few remarks, if I may.Update your device drivers, BIOS, enable DMA, OS updates and patches etc: Well although Imgburn is more than capable to work flawlessly on legacy systems as old as windows 95 if there is any degradation or failure in the operation of imgburn most probably it is due to generalized degradation in system performance.
The way I see it few drivers affect burning performance. These are mostly IDE and SATA drivers in my opinion. In the first case I'd advise not to install any drivers whatsoever. Use Microsoft's buil-in drivers instead. SATA drivers might be updated if they are required for proper operation of SATA controller in the first place and there are some issues. Otherwise, if performance is already satisfactory, I don't think it's all that important to update drivers.
BIOS should only be updated if there is some kind of major issue with burning which does or might originate from the BIOS. It, however should be left alone in any other case, which is almost always since such cases are rare in my opinion. A good rule to follow concerning the BIOS: if it isn't broken, don't fix it. Kind of like the drivers situation but to a much greater extent.
DMA should actually be enabled by default so there isn't really any need for that. Perhaps the controller could be uninstalled and then the system rebooted (as described in the FAQ section) IF there are problems with burning even when no other programs are running.
OS updates don't really have much say in this. They are mostly, important to security.Avoid using the computer extensively while burning: Although we like the luxury of having dual,quad and soon hexacore core rigs giving us the ability to multitask I still recommend waiting for a few minutes and giving imgburn enough memory to burn successfully.
It's not the processor that's the problem. It's the hard disk that's always striving to catch up with the rest of the system hardware. The hard disk has been the general bottleneck of a computer system for QUITE some time. And it's getting more and more noticeable since different hardware evolves at a different pace. When we look at the evolution pace of all the hardware that has anything to do with performance it's the hard drive by far that's at the tail. Hard drives haven't evolved nearly as much as any other hardware component in terms of speed. Well, there are 10 000 RPM drives and there is also RAID but these are hardly mainstream and beyond the average user's reach (unlike other rather powerful hardware), due to very bad capacaty/price ratio and increased complexity and price, respectively. Actually even then the hard drive would be the bottleneck, it's just going be less noticeable.
So it's basically the I/O tasks that should be avoided: copying/moving, extracting, scanning for malware, etc. Bascially anything that makes the hard drive work a lot. CPU intensive tasks aren't much of a problem. You can encode a video/audio (which is a very CPU intensive process usually) and have no issues burning whatsoever, because then it's the CPU that does the work, whereas the hard drive has an easy time and can supply the data for burning quickly enough.
Perhaps a tip to defragment the hard drive from time to time can be added. For example once a month or something like that. Depends how much activity there is on the hard drive.
Bulgarian translation of the base 126.96.36.199 for ImgBurn 188.8.131.52.
Updates/improvements to the translation are possible. I'll post them here, if any.
Like, who ever uses Verify disk and Discovery options?
I for example do. I always leave the verify option checked with but a few exceptions - whenever I'm burning an image that I've already burned a few times on my RW or when I'm REALLY in a hurry and every second counts. In all other situations I let ImgBurn verify the burned disc. In fact I consider a verification option a must for every self-respecting burning program.
EDIT: I'm not saying "delete and write again the write-once media". I'm saying "just burn the heck out of it, regardless of what's already on it." I'm talking about a destructive operation. The end result is not a coherent data track, just a disk with no readable information on it. This should be entirely doable in principle, just spin the disk, turn on the laser, and destroy the data.
If you want to destroy a disc, you can simply break it in half. There: problem solved. If you prefer a more fancy method, use your microwave oven. Since no burner is forever and every burn affects the drive's longevity more or less, I see no reason for me to waste my valuable burn cycles on an operation that can be done more easily and quickly another way.
There is no way to write again to write-once media. Why else would be called write-once? It's like asking if there is a way to write Blu-ray discs in DVD-RW drives. Not possible.
I'm sorry for bumping an old thread, but I decided to reply here instead of creating a new thread.
So, since DT and Alcohol support ISZ and specification is public, are there any chances for adding ISZ support ? I'm interested in burning ISZ files only (not converting, creating, editing etc.).
I have almost all CD/DVD images in ISZ and currently I need to: use Ultraiso for burning or use it to convert ISZ>ISO and then burn with Imgburn.
I fail to see the point. If almost all your images are ISZ, then it's either of the following cases:
1) your "collection" of images is rather consistent - you don't create new images and you don't delete images;
2) you keep creating new images with UltraISO and maybe some of them deleting as well.
In the first scenario just convert all your ISZ to ISO (or whatever) and be done with it once and for all.
In the second scenario... well, you are already using UltraISO as your primary image creation software. Why not keep using it for burning as well. Why need to switch to ImgBurn, especially if you already paid money for UltraISO?
Just a quick question. Do translators need to update their translations, is there something new in there?
True - but throwing a few dollars at the author will give you a warm, fuzzy feeling.
I can vouch for that. I donated $30 and it did give me a nice warm and fuzzy feeling deep inside. I'm not sorry for a dime of it, and even wish I could give more.
ImgBurn doesn't have its own support for those formats. It uses the systems' codecs for that. If you have an ACM codec or DirectShow filter installed, then ImgBurn should be able to burn the given audio format.
Unfortunately I believe there is neither an ACM codec available, nor a DirectShow filter. You'll have to decompress your files to WAV in this case.
To add to Cynthia's post. Nero (or whatever other burning program you're comfortable with) might still be required if you need to burn multisession discs since ImgBurn isn't capable of doing that. That aside however ImgBurn can do everything Nero can.
Actually I have found a workaround for this problem for WMP9: right click on the playlist dropdown menu and untick CD Drives. After that WMP no longer creates a handle for the drives and ImgBurn can do its thing. Here's a shot just in case:
I installed WMP10 and WMP11 on a virtual PC (since on my real PC I use WMP9) to check if this would work for those versions as well but no luck.
Thank you for your effort. Very nice to know all this.
in ImgBurn Translations
Translatation updated for ImgBurn 184.108.40.206. Sorry about the late upload but I hadn't noticed there was a new base file for this version.