Unable to boot from USBdevice

[Guest]

I'm trying to use the new "USB 2.0 Boot" feature/component (in the Feature
Pack 2007) but unable to get it working. My hardware just says "Disk error"
when I start up my PC.

The motherboard is a VIA EPIA-SP8000EG, EDEN/800Mhz, with a TwinMOS PC3200
DDR-DIMM 1024MB.

There is nothing other than VGA kabel, USB mouse, PS/2 keyboard connected to
the motherboard.

My USB device is a Corsair Flash Voyager 4096MB USB2.0 13/19MB sec.

Motherboard discovers the USB device in the BIOS and allows me to choose it
in boot priority, i've also successfully booted from the USB device using
Windows 98 boot disk file.

Is there a guideance, blog post, or anything like that, that shows how to
utilize the new USB boot feature? I've been waiting for this for quite a
while and really want it to work.

 

[Guest]

Sondre,

I haven't tried the USB boot yself yet. But the 'Disk Error' genarlly points
to the format of geometry of the disk.

1. Is the USB key FAT16 - if so you will have to go through the
'BootPrep.exe' process.

2. If your usb key is FAT32 then you may like to try booting the machine
from a win 98 cdrom and try formatting the usb key on the device. Our
experience is that XPe likes it's booot device to be formatted on the target.

Cheers

Darrem

 

[Bing.Chen]

Dear Darren,

FP2007 has its own format tool, formatufd.exe.

It will take over the format job.

--
Best Regards,
Bing Chen
Advantech Co., Ltd.

¬ãµØ - ·L³n¥xÆW°Ï´O¤J¦¡§@·~¨t²Î¸g¾P°Ó
http://www.advantech.com.tw/epc/newsletter/ATW/2005MS/

 

[Bing.Chen]

Dear Sondre,

Due to "USB 2.0 Boot" function needs BIOS INT13 natively support, you
need to check the BIOS support.

Otherwise, do you reference the help file, it shows the steps to achieve
this goal.

PS. I also met "Disk error" yesterday.
After changing BIOS, the problem was gone.
This function is really BIOS sensitive.

--
Best Regards,
Bing Chen
Advantech Co., Ltd.

¬ãµØ - ·L³n¥xÆW°Ï´O¤J¦¡§@·~¨t²Î¸g¾P°Ó
http://www.advantech.com.tw/epc/newsletter/ATW/2005MS/

 

[Guest]

I didn't know of formatufd.exe so thanks for mentioning. I have previously
used other alternatives to format the USB device as bootable.

Now I'm trying to boot using USB device on a Dell Optiplex GX620 machine and
it starts loading Windows XP (shows the loading screen) .. and after a while
I hit a bluescreen (doesn't even come close to a full boot-up).

STOP: 0x0000007B (0xF789E524, 0XC0000034, 0X00000000, 0X00000000)

The same machine boots fine using a standard SATA drive, and I built the
image using the exact same machine.

 

[Andy Allred [MS]]

I tried responding to your query via our blog yesterday but you did not
provide an e-mail address, i did respond to your web site's 'public' e-mail
though.

Be sure to follow the USB Boot steps in the xpehelp.chm, the procedure is
not fully baked yet and requires some manual intervention on your part when
building the configuration and manually disabling conflicting components.

If you follow the steps to disable appropriate components after you get past
step 4, you can build your runtime with the USB Boot 2.0 components, drop it
onto your key and boot the full image. If you get an error 7B and have the
USB Boot components (not likely based on our tests), then NTOSKRNL is not
seeing the DOK (but the BIOS did). If this happens then your NTDETECT did
not pass the DOK drive parameters to NTOSKRNL. To verify that this is or is
not the problem, replace NTDETECT.COM with USBNTD.CHK (rename it to
NTDETECT.COM). The checked version will output USB DOK'S found and their
geometry.

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.

"Sondre - MSFT Regional Director"

 

[Andy Allred [MS]]

Oh, one other thing, please communicate your Feature Pack issues and
questions to the beta newsgroup so everyone participating can more easily
find FP content.

Sign up for the NG via the connect site, it will take about 4 hours to
propagate the permissions to the NG:
microsoft.beta.xp_embedded_sp2.feature_pack_2007

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.

"Sondre - MSFT Regional Director"

 

[Guest]

Thanks a lot, this seems to have helped a bit.

I was looking at xpehelp.chm within the installation folder, E:\Program
Files\Windows Embedded\help, and not the xpehelp.chm that came with the
download. Found information on USB boot easily in the updated .chm.

I have signed up on the beta forum and will continue my discussions there.

Not able to get a full boot yet, the PC restarts when the white on black
progressbar has come to 40%.

Regards,
Sondre

 

[Dietmar]

Hi all,

I tested the new "Future Pack" for USB boot.
I noticed, that on i875 Intel based motherboards you cant boot from an USB
stick formatted with FAT 32. FAT 32 works on AMD motherboards and my
Shuttle Barebone with Intel chipset.

The same stick boots on all motherboards that I tested formatted with
FAT16.

I choose the HP format utility which gives for me always
the best results for USB boot from USB pendrives.

AND: You cant choose now the possibilty to modify
boot.ini because ntldr gives you then the message: Bad boot.ini found.

The CriticalDeviceDatabase is nearly exact the same as mine for USB
boot...hihi.

On thing in USB* entry in Registry services is others than mine: Start = 0
is clear, because the USB driver have to be present at boottime.
But this USB boot from Microsoft works with Group = Base entry.
I have to choose Group = System Reserved .

I make a try to change the NTLDR against it from
XP SP1 because I often need different boot.ini
entries.

Nice to hear from you
Dietmar

PS: I use simple the Minlogon Macrocomponent for testing USB Boot.
The Pendrive is LEXAR Jumpdrive with 500MB.
This stick is shown at once as a harddrive (not
removable device, because the harddrive Bit is set there from factory) so
it is best for testing.

 

[Dietmar]

Hi all,

the message through boot

NTLDR: Bad boot.ini found

belongs to the i875 chipset AND the
HP format utility. This message is gone if you use the FAT16 from XP.
You will have no luck if you try to boot from
USB with OHCI USB driver (SIS Chipset) because there is no entry in the
CriticalDeviceDatabase for it.
Also there is no entry for booting from USB 1.1.

For those people, add (doubleclick) the following to the registry of your
USB bootdevice
BEFORE FBA name it Critica.reg in system AND system.sav

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase]


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0c0300]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbuhci"


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#cc_0c0310]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbohci"



And also you have to add named serv.reg


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\USBUHCI]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\

72,00,69,00,76,00,65,00,72,00,73,00,5c,00,55,00,53,00,42,00,55,00,48,00,43,\
00,49,00,2e,00,53,00,59,00,53,00,00,00
"Group"="Base"
"DisplayName"="USB 2.0 Bus Driver"
"Description"="USB 2.0 Bus Driver"


[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\USBOHCI]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\

72,00,69,00,76,00,65,00,72,00,73,00,5c,00,55,00,53,00,42,00,4f,00,48,00,43,\
00,49,00,2e,00,53,00,59,00,53,00,00,00
"Group"="Base"
"DisplayName"="USB 2.0 Bus Driver"
"Description"="USB 2.0 Bus Driver"



After that, copy the drivers usbohci.sys and
usbuhci.sys to windows\system32\drivers.

Good luck
Dietmar

 

[Dietmar]

Hi all,

no pagefile and no hibernation works on "Microsofts USB BOOT solution".

For that, you have to modify the driver disk.sys.
This can be done, because in the WINDDK there is
the C source code of it.

The 'safely remove hardware' icon is gone.

Nice to hear from you
Dietmar

 

[Guest]

I’m having the same problems as Sondra with the XPE USB\CD drives, I made the
changes to XPE and still no luck with the Dells. The Dell’s are the only
computers that I’m having problems with, Optiplex GX620, GX260, GX270, and
Dimension E510. The rest on the computers in my inventory are not having the
same problems as the Dell’s. (HP d220, 5150, 7100, Gateway, E-series, 600,
510, 720, Compaq’s, and NCS Apollo). The USB drive is FAT16, it’s getting the
same error code as Sondra: STOP: 0x0000007B (0xF789E524, 0XC0000034,
0X00000000, 0X00000000) BSoD
It seems to be more of a system driver problem than an NTDETECT.COM problem.

Dose anyone have a solution to this?