20 replies to this topic

[Nonominator]

I have done A LOT of reading on these forums and googled the hell out of it but I cannot find the answer/understanding... of how to get BartPE to load with Xboot. I have the latest Xboot, I have found things about firadisk and other things and still don't get how to get this to boot right!


I get a 0x7B on load up. Something is up and I don't get how to fix it.

I was able to get the companies MDT (Already created ISO), in both X64 and X32 versions loaded and they work great!

I got Dell Diagnostics and MemTestx86 flawlessly also.

However we use the Ghost program in BartPE and another utility called "G-Disk" to wipe drives. I work mainly with deployment, but I suck at creating PE environments and such.

Does anyone know how to add BartPE to Xboot and make it work?!! I am at a end of trying to find the answers and nothing I have tried has worked.

[Nonominator]

Seriously need some help. I will PAY someone to help me via paypal. It can't be this hard for the expert...

[maanu]

open your bartpe iso with ultra iso and post screen shot here . is it image based ?

i dont know what XBOOT is , but anyhow give me its configuration . i ll see .

OR

give me your iso etc , upload to mediafire and pm me the link . i ll correct it and send back to you.

oh and i dont need money

[Nonominator]

open your bartpe iso with ultra iso and post screen shot here . is it image based ?

i dont know what XBOOT is , but anyhow give me its configuration . i ll see .

OR

give me your iso etc , upload to mediafire and pm me the link . i ll correct it and send back to you.

oh and i dont need money

I have a working bartpe from a corporation, if I write it to a USB/CDR I have no problems booting directly from it. I can't send you the ISO as it's official sensitive information and I would be fired and sued... The configs and such I can...

[maanu]

I have a working bartpe from a corporation, if I write it to a USB/CDR I have no problems booting directly from it. I can't send you the ISO as it's official sensitive information and I would be fired and sued... The configs and such I can...

show me the XBOOT configuration file . .

disregard my pm reply.

[Nonominator]

show me the XBOOT configuration file . .

disregard my pm reply.

color magenta/white white/magenta black/white black/white

 

timeout 10

 

 

### MENU START

title Boot from hard drive

map (hd0) (hd1)

map (hd1) (hd0)

map --hook

chainloader (hd0,0)

### MENU END

 

 

### MENU START

title bartpe\n

ls /images/bartpe.iso || find --set-root /images/bartpe.iso

map --heads=0 --sectors-per-track=0 /images/bartpe.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/bartpe.iso (0xff)

map --hook

chainloader (0xff)

### MENU END

 

 

### MENU START

title Help!\n

ls /images/help.iso || find --set-root /images/help.iso

map --heads=0 --sectors-per-track=0 /images/help.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/help.iso (0xff)

map --hook

chainloader (0xff)

### MENU END

Edited by Nonominator, 18 September 2011 - 07:19 PM.

[cdob]

Add a windows driver supporting ISO files, e.g. firadisk
http://reboot.pro/10...dpost__p__93165

[maanu]

OR

replace


title bartpe\n
ls /images/bartpe.iso || find --set-root /images/bartpe.iso
map --heads=0 --sectors-per-track=0 /images/bartpe.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/bartpe.iso (0xff)
map --hook
chainloader (0xff)

with


title bartpe\n
ls /images/bartpe.iso || find --set-root /images/bartpe.iso
map --mem /images/bartpe.iso (0xff)
map --hook
chainloader (0xff)

or you can extract the bartpe.iso as it is , and load the setupldr.bin from grub4dos.

title bartppe
chainloader /(path to setupldr.bin/setupldr.bin


and i take it as , you can use bartpe.iso all right if using alone./ but when you add it to XBOOT , it gives 0x7B ???

or with old configuration , you can use WINVBLOCK based floppy image to be loaded into memory before loading the iso

map --mem /WINVBLK.IMG (fd0)
map --mem /WINVBLK.IMG (fd1)
map /IMAGES/BARTPE.ISO (0xff)
map --hook
chainloader (0xff)

[Nonominator]

OR

replace


title bartpe\n
ls /images/bartpe.iso || find --set-root /images/bartpe.iso
map --heads=0 --sectors-per-track=0 /images/bartpe.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/bartpe.iso (0xff)
map --hook
chainloader (0xff)

with


title bartpe\n
ls /images/bartpe.iso || find --set-root /images/bartpe.iso
map --mem /images/bartpe.iso (0xff)
map --hook
chainloader (0xff)

or you can extract the bartpe.iso as it is , and load the setupldr.bin from grub4dos.

title bartppe
chainloader /(path to setupldr.bin/setupldr.bin


and i take it as , you can use bartpe.iso all right if using alone./ but when you add it to XBOOT , it gives 0x7B ???

or with old configuration , you can use WINVBLOCK based floppy image to be loaded into memory before loading the iso

map --mem /WINVBLK.IMG (fd0)
map --mem /WINVBLK.IMG (fd1)
map /IMAGES/BARTPE.ISO (0xff)
map --hook
chainloader (0xff)

Lets remove the top part it didn't work and for future generations when we all figure this out... I don't want them to have the wrong information. I bolded what you should remove cause it doesnt work, NOT that I don't appreciate it. I absolutely love the support here. Just for documentation purposes.

"and i take it as , you can use bartpe.iso all right if using alone./ but when you add it to XBOOT , it gives 0x7B ???" = That is correct.


I don't get the bottom part... Can you show me more or explain it?

Edit:

NVM!

Edited by Nonominator, 18 September 2011 - 08:28 PM.

[Nonominator]

Here is the new menu:

color magenta/white white/magenta black/white black/white 

timeout 10

 

 

### MENU START

title Boot from hard drive

map (hd0) (hd1)

map (hd1) (hd0)

map --hook

chainloader (hd0,0)

### MENU END

 

 

### MENU START

title bartpe

chainloader /images/bartpe/I386/setupldr.bin

map --hook

chainloader (0xff)

### MENU END

 

 

### MENU START

title Help!\n

ls /images/help.iso || find --set-root /images/help.iso

map --heads=0 --sectors-per-track=0 /images/help.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/help.iso (0xff)

map --hook

chainloader (0xff)

### MENU END

Still BSOD 0x7b

[Nonominator]

Also tried:

color magenta/white white/magenta black/white black/white

timeout 10



### MENU START

title Boot from hard drive

map (hd0) (hd1)

map (hd1) (hd0)

map --hook

chainloader (hd0,0)

### MENU END



### MENU START

title BartPE

map --mem /images/FIRADISK.IMG (fd0)

map --hook

map --mem /IMAGES/BARTPE/I386/setupldr.bin (0xff)

map --hook

chainloader (0xff)

### MENU END



### MENU START

title Help!\n

ls /images/help.iso || find --set-root /images/help.iso

map --heads=0 --sectors-per-track=0 /images/help.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /images/help.iso (0xff)

map --hook

chainloader (0xff)

### MENU END

Same error message.

[cdob]

Lets remove the top part it didn't work

Well, your current ISO conditions are unknown.
ISO file booting is impossible without proper drivers.

Include a proper driver to BartPE first. http://www.911cd.net...ndpost&p=162216
Bolded parts are valid then.

Or load a proper driver from vitual floppy image.

[Nonominator]

Well, your current ISO conditions are unknown.
ISO file booting is impossible without proper drivers.

Include a proper driver to BartPE first. http://www.911cd.net...ndpost&p=162216
Bolded parts are valid then.

Or load a proper driver from vitual floppy image.

HEY, thanks again for your help... I am still not getting it though... I have tried to load firadisk and its not working still I must be doing something wrong. If someone would like to connect via teamviewer (Advanced Users on this forum please only... due to being trusted on this site... I trust you then.) And help me out.

[maanu]

i am rushing to the office now , when i ll come back , i MIGHT be available for team viewer session with you , ofc if you trust me.

also

why dont you try with


title BartPE
map --mem /images/FIRADISK.IMG (fd0)
map --hook
map --mem /IMAGES/BARTPE.ISO (0xff)
map --hook
chainloader (0xff)




show what is the error message you get this time , on a side note DISABLE any SATA hdd mode from motherboard if you have any SATA, change its mode to NATIVE or LEGACY from Motherboard setup.

and as my friend cdob has explained earlier , verify following

what is the version of setupldr.bin and ramdisk.sys you are using , is it win 2003 SP1 ?

what was the method , you used to build bartpe , or ask who made it . show us at least the root directory of your iso . screen shot i mean .

[cdob]

Yes, RAM disk approach is prefered. Works at all BIOS.
Contrary requires RAM. And USB 2.0 BIOS speed is recommended.

There is a file disk approach possible in addition.
Compare http://reboot.pro/88...737#entry121737

title BartPE file based- firadisk.ima

map --mem (md)0x800+4 (99)

map /firadisk.ima (fd0)

map /firadisk.ima (fd1)

map /BartPE.iso (0xff)

map --hook

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/BartPE.iso;floppy,vmem=find:/firadisk.ima;\n\0

chainloader (0xff)

This require a USB boot friendly BIOS.

Add both: RAM disk approach and file disk approach to menu.lst.

[Nonominator]

Yes, RAM disk approach is prefered. Works at all BIOS.
Contrary requires RAM. And USB 2.0 BIOS speed is recommended.

There is a file disk approach possible in addition.
Compare http://reboot.pro/88...737#entry121737

title BartPE file based- firadisk.ima

map --mem (md)0x800+4 (99)

map /firadisk.ima (fd0)

map /firadisk.ima (fd1)

map /BartPE.iso (0xff)

map --hook

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/BartPE.iso;floppy,vmem=find:/firadisk.ima;\n\0

chainloader (0xff)

This require a USB boot friendly BIOS.

Add both: RAM disk approach and file disk approach to menu.lst.

Yeah it's gotta be the driver to AHCI or RAID. I need to add those both to my BartPE or something... ANYONE got any clues on where/how to do that? It's booting just fine with Firadisk.img just gets to the middle of Windows XP "loading" bar (Blue Bar) and then 0X7B!

So it's gotta be it! I am so close to having a full build that does it all at work!

[maanu]

try with WINVBLOCK instead of FIRADISK .

if you could boot this iso on SAME system via CD , then it is not SATA driver issue.

try with Dietmer's modded NTDETECT.COM as well

http://www.911cd.net...showtopic=24097

[cdob]

@Nonominator
What about the recommended RAM disk approach?
File disk approach is less likely. Try RAM disk first.

Which hardware do you use?
Which boot device do you use?
Do create a CD/DVD?
Do you build a USB drive? Which one do you use? How partitioned? Which port do you use?
Did you adjusted menu.lst or moved files? Which menu.lst do you use?

[Nonominator]

@Nonominator
What about the recommended RAM disk approach?
File disk approach is less likely. Try RAM disk first.

Which hardware do you use?
Which boot device do you use?
Do create a CD/DVD?
Do you build a USB drive? Which one do you use? How partitioned? Which port do you use?
Did you adjusted menu.lst or moved files? Which menu.lst do you use?

try with WINVBLOCK instead of FIRADISK .

if you could boot this iso on SAME system via CD , then it is not SATA driver issue.

try with Dietmer's modded NTDETECT.COM as well

http://www.911cd.net...showtopic=24097

I'll see if I can do that modded NTDETECT.COM approach. I am still such a N00B at this stuff, ask me to fix a broken piece of software or hardware... I'm your man! (I do it professionaly as a System Administrator/Deskside Support above our Helpdesk...) But this stuff is just so new to me.


Which hardware do you use? (Mainly for work it's Dell's and HP's)
Which boot device do you use? (USB Thumbdrive = Lexar 8GB *With a storage meter on it...)
Do create a CD/DVD? (Negative, the point is to use a universal USB Thumbdrive with our MDTS/Images 32 and 64 Bit (I don't create them.) and 5 separate CD/DVD's or Thumbdrives was the previous process, I am trying to consolidate it down to just 1 for simplicity because we do A LOT of re-imaging.)
Do you build a USB drive? Which one do you use? How partitioned? Which port do you use? (FAT32-1 Partition Default Allocation Table, Above is Thumbdrive Specs)
Did you adjusted menu.lst or moved files? Which menu.lst do you use? I use the one generated by XBoot (SysLinux I think...?)

I got 4 out of 5 to boot just fine MDTs X2/MemTest 4.20/Dell Diagnostics (version that is default from Dell, hasn't been updated since 2006. When I figure out the BARTPE I would like to use the same method for all booting so we avoid any conflicts on hardware. (Example:Plugging it into a docking station.) But we aren't gonna worry about that now.

[cdob]

Did you adjusted menu.lst or moved files? Which menu.lst do you use? I use the one generated by XBoot (SysLinux I think...?)

Can you quote and answer parts?

There is a communication conflict.

A default XBoot menu.lst seems to fail currently.
There had been suggestions to edit menu.lst yourself. Edit menu.lst.

Don't use flat file solution at Dell machines with default XP files.
Certain Dell use USB boot unfriendly BIOS.
A patched ntdetect.com is required because of strange Dell BIOS.

Try the suggested RAM load approach.

I would like to use the same method for all booting so we avoid any conflicts on hardware.

There is no one size all solution.

[futuro13]

do it in xp, or with administrator righs in vista and up
1-put your bartpe with PeToUSB
2-run grup4dos
better explanation in http://florian.freundt.org/blog/?p=161
3-go a head with Xboot, all the time choose grup4dos for each image you add the pendrive

it works for me