uDOC boot issues

[John Coyne \(JC\)]

Hey guys,

Looking to see if anyone out there has run into this.

Booting uDOC from an Intel based chipset. TAP went fine, dependency checks
fine, build fine, blah blah blah...

so when the uDOC boots FBA comes up, does it's thing, and reboots the system
like it's supposed to. so now when the reboot happens, the uDOC tries to
boot, and I get an "invalid boot.ini, Booting from C:\Windows" message... it
churns for a second and then comes up with "hall.dll is missing or corrupt,
please install a new copy of the hal.dll"

I have tried this on 2 different uDOC's (different firmware revisions) and
always the same thing. Mind you this is the 4th piece of hardware I have
tried it on as well

anyone... anyone... Bueller... Bueller...

Appreciate any insight
thanks,
JC

 

[Andy Allred [MS]]

Here's some random things based on similar topics in this NG over the years:
- Can it be related to the bios and how it's identifying the boot device?
Try a different PC perhaps as a test.
- Is this the M Systems solution? You should definitely try asking them or
Slobodan.
- Did you have other OS drives (like with xp pro) plugged in and 'visible'
to FBA? Try going through FBA without any other drives attached, don't let
FBA enumerate them, i'm wondering if doing so is messing with the perception
of what the OS *thinks* the ARC path should be post FBA.

--
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.

 

[John Coyne \(eMVP\)]

Hi Andy,

this is the 3rd PC I have tried it with, and the 2nd uDOC.
I do have another OS drive, but I have tried it with all drives unplugged,
and the same result.
M-Systems is stumped. they said the hardware should be OK, since it goes to
FBA in the first place.
I just sent email to Slobodan... we'll see if he can save the day
thanks for the help, though...