Erick_ImgBurn

I know, and thanks for that info, even though I don't understand it. I just checked. Windows PE doesn't have 16-bit DOS support, so forget my idea.

Couldn't I just boot Windows PE 3.0 with a USB stick or external hard drive attached to the system, and simply click dldiag5.exe to use the DOS program?

I'm up for the challenge. Please explain how to do it. I want to learn. This way I can help others with this difficult issue. Thanks, Lightning.

I need to run a DOS hard disk diagnostics tool. The problem is the manufacturer doesn't provide a simple .ISO. Instead, I'm given a DOS executable. I need to know how do I take this .exe and using ImgBurn make a CD that boots and runs the tool? I couldn't find a clear answer anywhere on the Internet. Thank you.

Where do I find the MID of the discs? These are 2003 Verbatims in a green box.

Does anybody know if the Lite-On Ihap322-98 burner can write to 2.4x DVD+RWs? It's maximum DVD+RW write speed is 8x.

Oh, that's right, the direct overwriting. It all makes complete sense now. Thanks, Lightning.

I finally understand the purpose of the Quick Erase. Does DVD-RW require a full erase (format) too when brand new? Does ImgBurn also perform a Quick Erase on CD-RW and DVD+RW discs with existing data on them before writing new data? Does DVD-RW support direct overwrite?

See, that's the only part I don't get. Why would you ever want to erase just 800 sectors instead of all sectors on a disc? The only two reasons I can think of are (1) to make the disc unreadable, to protect private information and (2) to completely erase a disc that has no more than 800 sectors of data, like one or two small files. Surely not to erase a disc that has over 800 sectors of data, as you would overwrite only some of the data and the rest of it would still be on the disc, requiring a full erase the next time you want to write new data to the disc.

So the Quick Erase button is useless, because ImgBurn automatically deletes any existing data on the target rewritable media before burning new data?

Thanks for that, Lightning. Please answer the second part of my question about when to use Quick Erase. Thank you. I have spent the last three days learning everything about burning, from file systems to sector types. I now feel I can use ImgBurn with complete confidence.

Does a brand new CD-R, CD-RW, DVD-R or DVD-RW (and all + variants) require a quick or full erase? If so, why? Aren't they full of zeroes and formatted at the factory? Why would you use a Quick Erase instead of a Full Erase? All I got is either to delete the first 800 sectors of data to make a disc unreadable, or delete small files that are no larger than 800 sectors of disc storage capacity. For all else, use a full erase. Am I correct?

Good to know, meaning I must build BartPE again.

I learned it is "possible" to update a BartPE disc, but it's best to start from scratch. Just thought I'd ask while I had your attention. Of course, I'll be using ImgBurn to burn the disc, so there is a relationship.

I use ImgBurn to burn everything. Does BartPE store configuration files for each plug-in? If so, couldn't I just edit the file versions in each config file and reburn the disc using the proposed method? All the other settings would stay the same and just the newer file versions would be changed.

I burnt a BartPE disc last year using Windows XP with SP3 and even added third-party SATA drivers using ImgBurn. Well, now I have newer file versions for one of my plug-ins, so I want to reburn the disc. But I have a few questions: 1. Is it possible to simply delete the older file versions inside a subfolder of BartPE's "plugins" folder and drag and drop the newer file versions in their place, without having to do the whole make-a-Bart-PE process again? 2. What modes and settings do I use? 3. Do I have to set the disc as bootable in ImgBurn, even though the disc is already bootable? And if so, how?

Thank you very much.

How do you burn Microsoft security patches or any other files or folders to a DVD+RW and what are the correct settings? I searched the guides, but unless I overlooked one of them, the instructions for this basic task aren't there. ImgBurn is so small and reliable. I've burnt two Windows XP installation discs and a BartPE rescue disc with success.

Yep, now to spend the next four years reading the ImgBurn guides. LOL

The Lite-On tops that NEC in every which way. Not a read or write issue yet.

That's it! I've had it with this piece of ish! I smashed it good with a hammer. Never have I had a computer device so terrible as this HP (NEC) DVD and CD-RW burner. I might have used it ten times in 7 years, and I've had nothing but problems with it from the first time I used it. I'm buying that Lite-On IHAP right now...

BLUK, I knew all that. I would just like to know if these errors are caused by a copyright protection on Windows XP? BartPE burned fine, so I hope that elimates the drive as the problem.

Good news. I just successfully burned, verified and tested a BartPE disc. That means this disc is good and the burner is okay, right? Still waiting for an answer about the verify errors with the Windows XP SP3 ISO.

Updated to current version; same issues. I 19:51:11 Verifying Session 1 of 1... (1 Track, LBA: 0 - 289137) I 19:51:11 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 289137) W 19:54:08 Failed to Read Sector 171360 - Reason: Illegal Mode For This Track W 19:54:08 Sector 171360 maps to File: \I386\SP3.CAB Is this error because the ISO of Windows XP is copyrighted, or is this a bad burn? I 18:58:42 Verifying Session 1 of 1... (1 Track, LBA: 0 - 289137) I 18:58:42 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 289137) W 19:01:21 Failed to Read Sector 230470 - Reason: Unrecovered Read Error W 19:01:21 Sector 230470 maps to File: \I386\LANG\IMJPST.DI_ Is this a bad burn, or am I doing something wrong, such as not configuring the software properly?

A couple new drives? I don't want "a" new drive. I already use first-class Verbatim media and have tried different speeds and formats. My money's on the drive, but I need to be sure before I invest in a new drive. I'm only a version or two behind. Again, that's not the issue.