The CD Forum > Editing the BCD store on a USB disk w/BCDEdit (WinPE 2.0)

Full Version: Editing the BCD store on a USB disk w/BCDEdit (WinPE 2.0)

The CD Forum > The CD Forum > Windows PE

netarc

Aug 10 2007, 05:15 PM

I've successfully used the steps below to copy the files from a WinPE 2.0 (Vista) boot ISO to USB drive to boot PE2 from USB; now I would like to add some additional boot environments, and was hoping to do so via Vista's BCDEdit tool.

However, I've been unable to figure out how to view (much less alter!) the boot sector on the USB drive - by default, running BCDEdit only shows the active HD partition (i.e., C:\). I would think there's some way to switch it so that it's referring to the USB media boot partition?! Haven't had any luck searching for a method to do this via google - if anyone knows the secret, please advise ... thanks!

---

To create a bootable UFD

1. During a running Windows Vista operation system or Windows PE session, insert your UFD device.

2. At a command prompt, use Diskpart to format the device as FAT32 spanning the entire device, setting the partition to active. For example,

CODE
diskpart
list disk
select disk <FLASH_DISK_INDEX>
clean
create partition primary size=<size of device>
select partition 1
active
format fs=fat32
assign
exit

paraglider

Aug 10 2007, 05:51 PM

Just add /store <PathtoBCDfile> i.e.:

bcdedit.exe /store c:\boot\bcd /enum osloader

netarc

Aug 11 2007, 12:44 AM

QUOTE (paraglider @ Aug 10 2007, 03:51 PM)

Just add /store <PathtoBCDfile> i.e.:

bcdedit.exe /store c:\boot\bcd /enum osloader

Thanks, that worked ... specifically, to enumerate the USB store I found...

bcdedit /store E:\boot\bcd /enum

...where E: is the drive letter of the USB flash boot drive.

Unfortunately, when I then tried to use the /store parameter in conjunction with the /createstore param (the latter to start the process of adding a new BCD entry on the USB drive to point to the BartPE boot location - [boot]\i386\setupldr.bin), I got an error indicating that "/store" can't be used in conjunction with the "/createstore" option?!

Any tips on how to add a BCD entry to USB boot flash media would be appreciated ... thanks!

netarc

Aug 11 2007, 01:00 AM

Some more detail ... basically, I'm attempting to follow the info from the Boot Windows PE from Hard Disk Walkthru; instead of modifying the BCD on the C:\ system store, I'm hoping I can use steps similar to this to modify the BCD on the USB (e.g., E:\boot\bcd).

I figure the BCDEdit steps, modified for the USB drive (E:), will apparently be...

Bcdedit –createstore c:\temp\BCD
Bcdedit –store c:\temp\BCD –create {bootmgr} /d “Boot Manager”
Bcdedit –store c:\temp\BCD –set {bootmgr} device boot
Bcdedit –store c:\temp\BCD –create /d “WINPE” –application osloader
Bcdedit –import c:\temp\BCD

This returns a GUID value, which is substituted in the below...

Bcdedit –store E:\boot\BCD –set <GUID> osdevice partition=boot
Bcdedit –store E:\boot\BCD –set <GUID> device partition=boot
Bcdedit –store E:\boot\BCD –set <GUID> path \i386\setupldr.bin
Bcdedit –store E:\boot\BCD –set <GUID> systemroot \windows
Bcdedit –store E:\boot\BCD –set <GUID> winpe yes
Bcdedit –store E:\boot\BCD –set <GUID> detecthal yes
Bcdedit –store E:\boot\BCD –displayorder <GUID> -addlast

Do the above steps look accurate, or am I off?

paraglider

Aug 11 2007, 06:46 AM

/store is not required with /createstore as you have already specified the location of the BCD file.

Creating an entry for XP is different for creating an entry for Vista - you will need to use {ntldr} instead of {bootmgr}. Not sure what you are trying to achieve with the /import.

Everytime I have tried a line that contains partition=boot I get an error. I think it should be:

Bcdedit –store E:\boot\BCD –set <GUID> osdevice boot

There is extensive help built into bcdedit using /?.

A doc to read about bcdedit can be downloaded here:

http://www.microsoft.com/whdc/system/platf...rmware/bcd.mspx

http://www.microsoft.com/whdc/system/platf...dedit_reff.mspx

netarc

Aug 14 2007, 05:50 PM

QUOTE (paraglider @ Aug 11 2007, 04:46 AM)

Creating an entry for XP is different for creating an entry for Vista - you will need to use {ntldr} instead of {bootmgr}. Not sure what you are trying to achieve with the /import.

Everytime I have tried a line that contains partition=boot I get an error. I think it should be:

Bcdedit /store E:\boot\BCD /set <GUID> osdevice boot

After digesting the docs and your suggestions, I've gotten a little farther, but haven't quite hit success yet; here's an update...

TRIAL 1
Upon querying the BCD for my working WinPE 2.0 USB flash boot drive, I noticed that the default boot loader settings read:

Windows Boot Loader
-------------------
identifier {default}
device ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path \windows\system32\boot\winload.exe
description Windows Setup
locale en-US
inherit {bootloadersettings}
osdevice ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot \windows
detecthal Yes
winpe Yes
ems Yes

In trying to create the new boot loader for BartPE, I did at first try the "osdevice partition=boot" param, and found that this did produce an error, as you said, ParaG. So I modified the method - based on the fact that the above "devices" pointed to "ramdisk" - to the following (where E: is the USB drive under Vista):

bcdedit /store E:\boot\BCD /create {ntldr} /d "Legacy OS Loader"
bcdedit /store E:\boot\BCD /set {ntldr} device boot
bcdedit /store E:\boot\BCD /create /d BartPE /application osloader

This last step returns a GUID, which is used in the following steps...

bcdedit /store E:\boot\BCD /set <GUID> osdevice boot
bcdedit /store E:\boot\BCD /set <GUID> device ramdisk=[boot]
bcdedit /store E:\boot\BCD /set <GUID> path \i386\setupldr.bin
bcdedit /store E:\boot\BCD /set <GUID> systemroot \windows
bcdedit /store E:\boot\BCD /set <GUID> winpe yes
bcdedit /store E:\boot\BCD /set <GUID> detecthal yes
bcdedit /store E:\boot\BCD /displayorder <GUID> /addlast

I figured this was a long shot ... and predictably, upon booting from this USB drive - although I did see the BartPE option appear in the boot options - selecting Bart caused the error:

"Windows failed to start"
Status: 0xc000000d
Info: The boot selection failed because a required device is inaccessible

TRIAL 2
Next I tried to replace all partition and drive pointers with the "boot" device, as so:

bcdedit /store E:\boot\BCD /create {ntldr} /d "Legacy OS Loader"
bcdedit /store E:\boot\BCD /set {ntldr} device boot
bcdedit /store E:\boot\BCD /create /d BartPE /application osloader

Last step returns GUID ... set bcdGUID = {...}

bcdedit /store E:\boot\BCD /set %bcdGUID% osdevice boot
bcdedit /store E:\boot\BCD /set %bcdGUID% device boot
bcdedit /store E:\boot\BCD /set %bcdGUID% path \i386\setupldr.bin
bcdedit /store E:\boot\BCD /set %bcdGUID% systemroot \i386
bcdedit /store E:\boot\BCD /set %bcdGUID% winpe no
bcdedit /store E:\boot\BCD /set %bcdGUID% detecthal yes
bcdedit /store E:\boot\BCD /displayorder %bcdGUID% /addlast

Boot into this USB config, access BartPE, and this time I got quite a bit further; the following message flashed on the screen, indicating BartPE was at least now trying to boot ... but it merely flashed on screen for 1/2 sec, followed immediately by a reboot:

Setup is inspecting your computer's hardware configuration...
NTDETECT failed

TRIAL 3
I then added (rather than replacing the prior boot entry) the following:

Bcdedit /store e:\boot\bcd /create {legacy} /d “BartPE-legacy”
Bcdedit /store e:\boot\bcd /set {legacy} device boot
Bcdedit /store e:\boot\bcd /set {legacy} path \i386\setupldr.bin
Bcdedit /store e:\boot\bcd /displayorder {legacy} /addlast

No change - same result as before, "NTDETECT Failed."

So now I'm stuck, and for that matter tired of thinking of this for the day - if anyone has any suggestions, I'm all ears! Thanks!

Oh, the current state of the BCD is as follows:

CODE

[b]C:\>bcdedit /store e:\boot\bcd /enum[/b]

Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {9e7b4fe9-4ab0-11dc-b10b-0016412825bd}
                        {ntldr}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows Setup
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     Yes

Windows Boot Loader
-------------------
identifier              {9e7b4fe9-4ab0-11dc-b10b-0016412825bd}
device                  boot
path                    \i386\setupldr.bin
description             BartPE
osdevice                boot
systemroot              \i386
detecthal               Yes
winpe                   No

Windows Legacy OS Loader
------------------------
identifier              {ntldr}
device                  boot
path                    \i386\setupldr.bin
description             Legacy OS Loader

netarc

Aug 14 2007, 05:58 PM

BTW, note that NTDETECT.COM does exist in the \i386 directory of the USB, which is where the bulk of the BartPE files are as well. Too, note that even though the two current "BartPE" entries are not working, the original Vista/WinPE 2.0 continues to boot fine.

netarc

Aug 14 2007, 06:42 PM

Ok, closer still ... I removed all of the old non-bootmgr entries (via bcdedit /delete), and recreated the {ntldr} BCD entry for BartPE as follows:

bcdedit /store E:\boot\BCD /create {ntldr} /d "Legacy OS Loader"
bcdedit /store E:\boot\BCD /set {ntldr} device boot
bcdedit /store E:\boot\BCD /create /d BartPE /application osloader

Returns GUID, save in variable bcdGUID

bcdedit /store E:\boot\BCD /set %bcdGUID% osdevice boot
bcdedit /store E:\boot\BCD /set %bcdGUID% device boot
bcdedit /store E:\boot\BCD /set %bcdGUID% path \i386\setupldr.bin
bcdedit /store E:\boot\BCD /set %bcdGUID% systemroot \i386
bcdedit /store E:\boot\BCD /set %bcdGUID% winpe yes
bcdedit /store E:\boot\BCD /set %bcdGUID% detecthal yes
bcdedit /store E:\boot\BCD /displayorder %bcdGUID% /addlast

I then copied NTDETECT.COM from the \I386 directory to the root of the USB drive; boot into the BartPE entry and this time the system displays Setup is inspecting your computer's hardware configuration... for several seconds, followed shortly by the error...

CODE

INF file txtsetup.sif is corrupt or missing, status 18
Setup cannot continue. Press any key to exit.

Ok, obviously this has to do with the SYSTEMROOT variable - before attacking that, I set WINPE to "off" ... same result. Then once again blew away the {ntldr} BCD entry and recreated from scratch, this time ignoring the SYSTEMROOT parameter entirely. Alas, no luck ... the INF file txtsetup.sif is corrupt or missing, status 18 persists

It appears that the system, once the OS load attempt starts, cannot figure out that the OS is in the \i386 directory of the USB drive ... any thoughts?

paraglider

Aug 14 2007, 07:06 PM

Havce you proved that you can boot XP based PE from your USB drive when its the only PE on the drive and is using the XP bootsector instead of the vista boot sector? Until that works then there is no point with messing with Vista boot sectors.

netarc

Aug 15 2007, 12:29 PM

QUOTE (paraglider @ Aug 14 2007, 05:06 PM)

We've been able to boot into BartPE from CD-ROM, so to that extent, yes, the BartPE folder structure does work.

When I started this, though, I'd made the assumption that copying the BartPE files from the CD to the USB drive, and then modifying the Vista BCD to properly call/locate the BartPE files, would be sufficient to boot BartPE.

paraglider

Aug 15 2007, 05:53 PM

Booting bartpe from USB is much harder than booting it from CD. Only way I could get it to work on my Nforce3 ultra motherboard was to format the USB drive as a zip drive and use the sdi approach to boot into ram. Even then it boots at usb 1 speed and hence is very slow. Never could get the direct boot working with all the files copied to the usb drive. Vista PE however worked much better and worked first time.

ktp

Sep 9 2007, 09:30 AM

For information following are the BCD status on my USB key.
The output from EasyBCD has more guid values than bcd one.

From bcdedit /store f:\boot\bcd /enum output:

CODE

Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows Setup
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
detecthal               Yes
winpe                   Yes
quietboot               Yes
ems                     Yes

From EasyBCD 1.7 (freeware) detailed view:

CODE

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader
-------------------
identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows Setup
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
detecthal               Yes
winpe                   Yes
quietboot               Yes
ems                     Yes

EasyBCD allows to change the BCD data, maybe you want to try it.

ktp

Sep 10 2007, 08:18 AM

@netarc.
I found that using grub4dos is much easier to invoke multiple environments from an USB key.

1) Get grub_for_dos-0.4.2 package.

2) Run bootlace.com (under DOS) to put grub4dos to mbr of your key or (maybe easier):

Change your boot.ini on the key to:

CODE

[boot loader]
timeout=-1
default=C:\grldr
[operating systems]
C:\grldr="Grub4Dos"
C:\="Previous Operating System on C:\"

3) copy grldr to root of USB key

4) create menu.lst on the root of your key:

CODE

# ntldr from USB key
title ntldr from USB key
find --set-root /ntldr
chainloader /ntldr

# bootmgr from USB key
title bootmgr from USB key
find --set-root /bootmgr
chainloader /bootmgr

5) Run bootsect /nt52 e: (where e: is your USB key drive). This set the boot sector to invoke ntldr (instead of bootmgr).

By using grub4dos you can also boot other environments (Linux, DOS etc...).

6) Boot the key, choose Grub4dos, then you got to menu.lst choices.

RBCC

Mar 14 2009, 03:52 AM

Where do I put the Images and the fonts for BOOTMGR.XSL? John

jaclaz

Mar 14 2009, 12:33 PM

QUOTE (RBCC @ Mar 14 2009, 09:52 AM)

Where do I put the Images and the fonts for BOOTMGR.XSL? John

I am not sure to understand how your question is connected with the thread.

AFAIK BOOTMGR.XSL is a resource inside c:\boot\<yourlocalisation>\bootmgr.exe.mui
http://www.geocities.com/jadoxa/bootscrn/bootmgr.htm

Images are in winload.exe.mui, see link on the given page.....

Fonts should be in \boot\fonts, but have no idea about how they can be "changed".

jaclaz

RBCC

Mar 28 2009, 10:03 PM

If I want to true type fonrts in my boot screen, graphics in my bootscreen and in the Bootmgr.XSL file. Where do I put these files? John

BartPEorDie

Apr 1 2009, 07:33 PM

QUOTE (ktp @ Sep 10 2007, 07:18 AM)

5) Run bootsect /nt52 e: (where e: is your USB key drive). This set the boot sector to invoke ntldr (instead of bootmgr).

I wouldn't recommend telling anyone to use bootsect on a UFD...

I did that myself yesterday, ran that exact command, except with the appropriate drive letter of course in my case, and it completely screwed up the bootsector my UFD volume, to the point that I was not able access and browse its file structure after.

The message I got at the end, after running that command, in the CP output, said something to the affect that it was unable to "lock" the volume, whatever that means.

I ended up having to use TestDisk to fix it.

So yeah...bootsect.exe isn't a tool I would recommend to anyone for using on a UFD.

Ed_P

Apr 1 2009, 11:06 PM

QUOTE (RBCC @ Mar 28 2009, 11:03 PM)

If I want to true type fonrts in my boot screen

TTBOMK the boot process doesn't use True Type fonts.

QUOTE (BartPEInstallationFailed @ Apr 1 2009, 08:33 PM)

So yeah...bootsect.exe isn't a tool I would recommend to anyone for using on a UFD.

I think you'll find it's designed to be run on bootable UFD's which you didn't have at the time.

BartPEorDie

Apr 2 2009, 12:55 AM

QUOTE (Ed_P @ Apr 1 2009, 10:06 PM)

I think you'll find it's designed to be run on bootable UFD's which you didn't have at the time.

Hmm, maybe so...but the whole reason I needed to use bootsect.exe in the first place is to *make* it bootable.

If the tool can't be used on a non-bootable bootsector, then what good is it? The whole point of using a tool like bootsect.exe is to make a volume bootable, so if it can't do that, then why use it at all?

paraglider

Apr 2 2009, 06:36 AM

This is what the WIndows AIK docs say about bootsect:

Bootsect.exe updates the master boot code for hard disk partitions to switch between BOOTMGR and NTLDR. You can use this tool to restore the boot sector on your computer. This tool replaces FixFAT and FixNTFS.

jaclaz

Apr 2 2009, 11:02 AM

To avoid the already common enough misunderstanding, in that article:
http://technet.microsoft.com/en-us/library/cc749177.aspx
by "master boot code" it is intended (with an apparent utter and total disregard to the common ways the bootsector code is called, even in ALL the rest of MS docs), the actual loading code of the bootsector, and it has NOTHING to do with the "master boot record" or MBR.
The use of "master boot code for hard disk partitions" should probably have in the (IMHO contorted) mind of the Author, clarified the thing.
(the Master Boot Record "belongs" to the WHOLE device/harddisk, while the bootsector "belongs" to a partition/volume)

As is the sentence, though perfectly accurate, has led to a great number of misunderstandings.

Some details are given here:
http://neosmart.net/blog/2007/bootsectexe-...or-not-the-mbr/

@BartPEInstallationFailed
NO, you got this wrong.
You don't use bootsect.exe to make "bootable" anything, you use it to make it boot "something else".

The error/problem you experienced is most probably due to other reasons, most probably a somehow "malformed" bootsector (doesn't matter whether bootable or not) before the use of bootsect.exe or a erroneus usage of it.

Just for the record, while they can exist non-bootable bootsectors for FAT (16 and 32), if formatted from DOS, it is NOT possible to have non-bootable NTFS bootsectors, as ANY utility will always make the bootsector a bootable bootsector when using Format command under NT/2K/XP/2003 (and Vista/2008). (unless of course you have a "special" formatting utility for NTFS that does not write the bootable code).

jaclaz

BartPEorDie

Apr 2 2009, 11:35 AM

QUOTE (jaclaz @ Apr 2 2009, 10:02 AM)

@BartPEInstallationFailed
NO, you got this wrong.
You don't use bootsect.exe to make "bootable" anything, you use it to make it boot "something else".

The error/problem you experienced is most probably due to other reasons, most probably a somehow "malformed" bootsector (doesn't matter whether bootable or not) before the use of bootsect.exe or a erroneus usage of it.

Just for the record, while they can exist non-bootable bootsectors for FAT (16 and 32), if formatted from DOS, it is NOT possible to have non-bootable NTFS bootsectors, as ANY utility will always make the bootsector a bootable bootsector when using Format command under NT/2K/XP/2003 (and Vista/2008). (unless of course you have a "special" formatting utility for NTFS that does not write the bootable code).

jaclaz

Actually, since it writes the bootsector code to the partition (which the IPL in the MBR chains to), which is then used to call up "bootmgr" in the case of Vista, or "ntldr" in the case of XP, I would say it is used to make a partition "bootable"...

As for the error/problem that I experienced, it was not due to "other reasons, most probably a somehow malformed bootsector". First of all, I need to add that my UFD was practically brand-new when I ran that command on the volume's bootsector, and so I am quite sure the bootsector was perfectly fine.

Secondly, since the bootsector was for a Fat 32 volume, and that was the first time I used any such tool on the device, most likely it was a non-bootable bootsector to start off with, and I already know for a fact it was...

So that answers that comment about bootsect.exe too. Still not a tool I would recommend for people to use on a UFD volume...

jaclaz

Apr 2 2009, 11:55 AM

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 06:35 PM)

First of all, I need to add that my UFD was practically brand-new when I ran that command on the volume's bootsector, and so I am quite sure the bootsector was perfectly fine.

Secondly, since the bootsector was for a Fat 32 volume, and that was the first time I used any such tool on the device, most likely it was a non-bootable bootsector, and I already know for a fact it was...

Well, again, not really.

You see, most (read ALL

) "brand new" sticks are pre-formatted as superfloppies, i.e. the first absolute sector of the device is the volume bootsector (and the volume spans over the ENTIRE device), or in other words, the device is un-partitioned.

Bootsect.exe is a tool intended to modify a bootsector of a volume on a partitioned device.

Whether the original bootsector on the device was a bootable one or not is of course debatable

, but some (read most if not all

) motherboards will simply refuse to boot from a superfloppy device (read unpartitioned device), no matter whether the actual bootsector is a valid bootable one or only has some data and an ending 55AA signature.

Moreover, it is possible that it was bootable (and would have booted) if you added the "right " OS loader/system file/kernel to it, i.e. the one hypothetically invoked by the hypothetically bootable bootsector.

I guess we'll never know.....

jaclaz

BartPEorDie

Apr 2 2009, 12:03 PM

QUOTE (jaclaz @ Apr 2 2009, 10:55 AM)

Well, again, not really.

You see, most (read ALL

FYI, my UFD had two volumes when I first bought it (still does, btw), one the normal Fat 32 one, and the other a CDFS volume that holds my U3 launchpad.

QUOTE

Bootsect.exe is a tool intended to modify a bootsector of a volume on a partitioned device.

Whether the original bootsector on the device was a bootable one or not is of course debatable

, but some (read most if not all

jaclaz

Maybe so...but why then did Pe2USB give me the error "Bootsector type is "Raw" The inspect option only supports Fat or NTFS bootsectors" or something to that effect when I tried to install BartPE on it the first time (after getting past all the other errors, I might add..)? Its quite obvious to me that there was no bootsector code written to the UFD volume originally. And right after getting that error is when I tried using bootsect.exe on it, but it screwed up my bootsector, and I had to use TestDisk to repair it.

So yes, the bootsector was a "non-bootable" one...

Click to view attachment

Ed_P

Apr 2 2009, 12:21 PM

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 12:35 PM)

Actually, since it writes the bootsector code to the partition

No. I MODIFIES the existing bootsector code. If the bootsector code is missing or not "normal" it isn't going to make it normal.

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 01:03 PM)

The inspect option only supports Fat or NTFS bootsectors" or something to that effect when I tried to install BartPE on it the first time

Wasn't that before you ran PEBuilder?

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 01:03 PM)

<attachment=1177:BartPE_error.JPG>

Any particular reason why your CMD window needs so much blank white space around it?

BartPEorDie

Apr 2 2009, 12:32 PM

QUOTE (Ed_P @ Apr 2 2009, 11:21 AM)

No. I MODIFIES the existing bootsector code. If the bootsector code is missing or not "normal" it isn't going to make it normal.

AHA! Well, that certainly explains it then. I thought it was supposed to write bootsector code, even if there was no existing code in the bootsector.

QUOTE

Wasn't that before you ran PEBuilder?

Yes, but my point is it wouldn't have given me that message if there was already bootsector code on the volume.

QUOTE

Any particular reason why your CMD window needs so much blank white space around it?

No reason. I just didn't expect people here to make such a big deal about little tiny matters like this, so I didn't think there was anything wrong with posting a pic with part of it blank, due to there being no cropping tool in MSPaint...

Anyone else feel like nitpicking?

nuMe

Apr 2 2009, 12:53 PM

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 12:32 PM)

Anyone else feel like nitpicking?

Have you looked in a mirror??

This whole forum is about precision, it's what is required to make the things do that we want them to do.

And btw your extremely long name messes up my view of topics you post in. Could you shorten it to simply IFailed??

jaclaz

Apr 2 2009, 01:34 PM

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 07:03 PM)

FYI, my UFD had two volumes when I first bought it (still does, btw), one the normal Fat 32 one, and the other a CDFS volume that holds my U3 launchpad.

Yep

,
FYI

your stick is a (possibly U3 enabled) one that has a controller that shows TWO devices, if you are familiar with SCSI terms two LUN's, the first a CD-like device (Read Only and with a CDFS filesystem) and the second an unpartitioned Read/Write HD-like device, formatted as superfloppy with a FAT32 filesystem.

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 07:32 PM)

Anyone else feel like nitpicking?

If I nitpick on a different topic, do I become eligible as "someone else"?

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 07:32 PM)

Again, not really, it has not a cropping tool

, but that doesn't mean you cannot make cropped images with it.

Set MSPAINT to start with a fairly smallish blank image, say 150x150.
Press PrtScreen to capture the display to clipboard.
Start MSPaint, and paste on the "smallish" opened blank the contents of the clipboard, image will be resized.
Use the rectangular selection tool to select the area you are interested in.
Cut it to the clipboard. (Ctrl+X)
Close MSPaint without saving.
Re-start MSPaint.
Paste on the "smallish" opened blank the contents of the clipboard, image will be resized.
Save the "cropped" image.

QUOTE (nuMe @ Apr 2 2009, 07:53 PM)

And btw your extremely long name messes up my view of topics you post in. Could you shorten it to simply IFailed??

I guess that I "Imadeit" would be more accurate.

jaclaz

BartPEorDie

Apr 2 2009, 04:51 PM

QUOTE (nuMe @ Apr 2 2009, 11:53 AM)

Have you looked in a mirror??

This whole forum is about precision, it's what is required to make the things do that we want them to do.

And btw your extremely long name messes up my view of topics you post in. Could you shorten it to simply IFailed??

NO thanks. Why should I shorten it just so you can view the topics better?

Maybe I should lengthen it to "nuMEmakeslamejokesandprobablyneverevengothisownBartPEinstallationtowork"...

And how can making a big deal out of nothing (i.e. me not cropping a image) be defined as "precision", and "what is required to make the things do what we them to do"?

Explain that one to me.

QUOTE (jaclaz @ Apr 2 2009, 12:34 PM)

Yep

,
FYI

No, you became eligible as "Anyone else", because that is what I said, not "someone else".

*cracks up laughing*

QUOTE

Again, not really, it has not a cropping tool

, but that doesn't mean you cannot make cropped images with it.

Did I say you "can't make cropped images with it"??? NO, I don't think I did...
I said it doesn't have a cropping tool, and it doesn't. Sure, I know I can do what you suggested, but here we go again...making a big deal out of nothing. Seems to be a trait of regular members on these forums...
FYI, if I knew everyone here was going to have a hissy fit over it, I would have certainly made sure to crop the stupid image...

QUOTE

I guess that I "Imadeit" would be more accurate.

jaclaz

I made what?

hilander999

Apr 2 2009, 08:15 PM

QUOTE (BartPEInstallationFailed @ Apr 2 2009, 05:51 PM)

I made what?

Man you need to RELAX.

Imadeit
as in succeeded, finished, GotItWorking
or more to the point.... BartPEInstallationFinallyWorked

QUOTE (nuMe @ Apr 2 2009, 01:53 PM)

Have you looked in a mirror??

This whole forum is about precision, it's what is required to make the things do that we want them to do.

Could not agree with you more.

Sometimes a lack of precision could be painful.

BartPEorDie

Apr 2 2009, 08:25 PM

QUOTE (hilander999 @ Apr 2 2009, 07:15 PM)

Man you need to RELAX.

Imadeit
as in succeeded, finished, GotItWorking
or more to the point.... BartPEInstallationFinallyWorked

Ok, I apologize...
I thought he meant to say "Imadeitfail" but left out the rest of it. He was responding after all to nuME's comment, who made the joke about that I should change my username to "Ifailed". I thought he meant it as another insult. But maybe he was only saying I had got it to work...
Sorry for any hard feelings I may have caused.

I've kinda been on edge lately, and not my usual joking self.

jaclaz

Apr 3 2009, 04:54 AM

QUOTE (BartPEInstallationFailed @ Apr 3 2009, 03:25 AM)

I've kinda been on edge lately, and not my usual joking self.

Yep, just trying to point out that your board name, besides being longish was also not reflecting the current status of your BartPE build.

You are carrying an outdated name!

Rest assured, no hard feelings of any sort

, we all have shifted into "joking" mode in this thread, last "serious" post being #21.

Yours truly,

Anyone else

BartPEorDie

Apr 3 2009, 03:41 PM

QUOTE (jaclaz @ Apr 3 2009, 03:54 AM)

Yep, just trying to point out that your board name, besides being longish was also not reflecting the current status of your BartPE build.

You are carrying an outdated name!

Very true.

I will change it (if I can), thanks.

EDIT: It seems this forum doesn't have that feature for normal users...

Ed_P

Apr 3 2009, 10:44 PM

QUOTE (BartPEInstallationFailed @ Apr 3 2009, 04:41 PM)

EDIT: It seems this forum doesn't have that feature for normal users...

True, but I can change it. PM me what you'd like it to be.

BartPEorDie

Apr 4 2009, 12:41 AM

Two PMs sent.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.