Starting BartPE . . fail . . Starting BartPE . . . fail Options

[oscar]

Do not use a Dell OEM XP CD as the source.

Disable plugins, one at a time, till ISO boots OK in MOBA.

[castile]

Do not use a Dell OEM XP CD as the source.

Disable plugins, one at a time, till ISO boots OK in MOBA.

Sounds good but . . . .
I only have this one Dell OEM XP CD.

[Ed_P]

If your PEBuilder is still a fresh install with only the DellFix plugin added I think you have a bad driver, probably a video one. And I think it implies a corrupt file on your Dell CD. How to isolate that and what to do about it I'm not sure.

Did you per chance run the infCacheBuild utility after you created the BartPE folder and before creating the ISO?

[cdob]

All except one of these disks will run when I place the CD into the drive after the machine is booted.

Replace the broken hardware or software.

Try slipstream XP SP3.

Use ImgBurn to burn the ISO image. Use good quality media, burn at half max speed.

[oscar]

MOBA Qemu has not broken hardware.
Try Virtualbox and MS VirtualPC 2007 too (both free). If the ISO does not work either there is not problem with hardware.

SP3 has problems with mountmgr.sys.

[castile]

Ed,

"Did you per chance run the infCacheBuild utility after you created the BartPE folder and before creating the ISO?"

I don't know what the infCacheBuild utility is or what it might do.

I sure would like to have one of these BartPE CD's but that may not be in the cards.

Thanks for giving this some thought.

Dan

[dog]

I don't know what the infCacheBuild utility is or what it might do.

First hit from google:
http://sourceforge.net/projects/winpe/file...cheBuild%202.0/
You'd need to run it if you're adding drivers as plugins, otherwise you'd need to manually remove the CopyFiles lines from the .inf(s)
But you say you're tried a fresh build with nothing added, so this shouldn't apply.
For a non-dell source, you could use the server 2003 trial.

[Ed_P]

I don't know what the infCacheBuild utility is or what it might do.

Did you check the Adding driver's link in my sig? No quarantee it will solve your problem currently but will be helpful if you need to add or replace drivers to resolve the looping.

Have you copied the CD folders/files to a hard drive folder and used them from there with PEBuilder?

[castile]

First hit from google:
http://sourceforge.net/projects/winpe/file...cheBuild%202.0/
You'd need to run it if you're adding drivers as plugins, otherwise you'd need to manually remove the CopyFiles lines from the .inf(s)
But you say you're tried a fresh build with nothing added, so this shouldn't apply.
For a non-dell source, you could use the server 2003 trial.

Thank you for an explaination of what I would do with InfCacheBuild if I obtained it.
I never went to look for it. Mostly because I wouldn't know what to do with it if I had it.

I am more interested in your suggestion that I can get a trial install copy of a non-dell windows install.
I did go and apply for a copy and now I need to ask.
When I get that 2003 trial, do I just use it in the same way as I have been trying to use my Dell XP source?
By the way, I did copy the Dell XP source files to my C: drive.
I had to do that because I needed to correct some trouble I had early on with "hiv" files.
From what I have read that is a common problem with the Dell source disk.

Anyway, I am on the path to use 2003 trial install as you suggested.

Thanks

[castile]

Did you check the Adding driver's link in my sig? No quarantee it will solve your problem currently but will be helpful if you need to add or replace drivers to resolve the looping.

Have you copied the CD folders/files to a hard drive folder and used them from there with PEBuilder?

I had not noticed your link to the Adding Drivers but I did visit there after I read this reply from you.
I must tell you in all truth . . . the info that link points to seems to be so far over my head.
I see the information but, again, have no idea how to use it.
Where do those little snippets of code go? Into which directory? And to what end?

It seems to me that with such little guidance about the use of that information I could do
little else but to dig myself deeper into the mire.

I thank you for trying to point me in the right direction.
I think I should apologize for being so dense.
I just don't see anything there that I would know how to attempt to use.

[dog]

I never went to look for it. Mostly because I wouldn't know what to do with it if I had it.

People here can ask questions and make suggestions, but I doubt you'll find everything you ever need to know in this one thread.
If the learning curve is too steep, you could try ubcd4win, like I suggested earlier.

When I get that 2003 trial, do I just use it in the same way as I have been trying to use my Dell XP source?

Yes, but make just a default build without adding anything yet, try it in a VM as well as your hardware, and if things go wrong, write down all the details.

[Ed_P]

I think I should apologize for being so dense.

Why? We all started the same way.

An alternate method to accomplish your goal mighjt be to try the UBCD4WIN approach. It includes a ream of helpful apps. It may not include the DellFix so you might still have to add something to address that situation.

Keep us posted.

haha cross posted with dog. Same ideas.

This post has been edited by Ed_P: Nov 5 2009, 12:18 PM

[castile]

People here can ask questions and make suggestions, but I doubt you'll find everything you ever need to know in this one thread.
If the learning curve is too steep, you could try ubcd4win, like I suggested earlier.

Yes, but make just a default build without adding anything yet, try it in a VM as well as your hardware, and if things go wrong, write down all the details.

OK. I downloaded Disk 1 of the Win Server 2003 package you told me about and
I can hardly believe it but I have a working, bootable BartPE disk that runs Macrium Reflect and everything.

( The download from Microsoft came as a .img file. Any idea WHY that is. I had to find an IMG-to-ISO converter before I could use the download. )

Anyway, it is doing what I need to do now and I thank EVERYONE for all the support.

Thanks

[castile]

Why? We all started the same way.

An alternate method to accomplish your goal mighjt be to try the UBCD4WIN approach. It includes a ream of helpful apps. It may not include the DellFix so you might still have to add something to address that situation.

Keep us posted.

haha cross posted with dog. Same ideas.

I downloaded Disk 1 of the Win Server 2003 package that "dog" talked about and
I can hardly believe it but I have a working, bootable BartPE disk that runs Macrium Reflect and everything.

( The download from Microsoft came as a .img file. Any idea WHY that is. I had to find an IMG-to-ISO converter before I could use the download. )

Anyway, it is doing what I need to do now and I thank EVERYONE for all the support.

Thanks

[Ed_P]

[cdob]

The download from Microsoft came as a .img file. Any idea WHY that is.

It's just a name: a ISO image with the name .img.
Feel free to rename the file.

[castile]

It's just a name: a ISO image with the name .img.
Feel free to rename the file.

Actually, that is the first thing I tried. I renamed to .img to .iso and every time
I asked Nero to load that renamed file Nero hung up in a way that I had to
power off and restart everything. At that point I decided I must need a converter.
After conversion everything went smoothly.
I'd rather not disagree, but simple renaming didn't seem to work for me.

[paraglider]

All goes to show that Dell OEM XP CD's are best avoided unless you enjoy pain.

[cdob]

I asked Nero to load that renamed file Nero hung

Try ImgBurn.

[castile]

All goes to show that Dell OEM XP CD's are best avoided unless you enjoy pain.

Greater truth was never spoken.