Re: Remote Boot Service



embedded_msit
07-09-2005, 09:23 PM
KM,
we have created a minimal .sdi file of 100MB and we could load the
ramdisk from the development system.. After it was loaded , gave the eroor:

Windows could not start because the following file missing or corrupt:

<Windows root>\system32\ntoskernel.exe
Please re-install a copy of the above file.

We have checked the ntoskernel.exe file in System32 in my image. What could
be the reason for the eroor. What does <Windows root> means ?

KM
07-09-2005, 09:24 PM
embedded_msit,

<Windows root> means the folder where your system files goes (usually
\Windows).

If you provided you own boot.ini in RBS, please check out what ARC path you
used there.

If you didn't provid the boot.ini (default one used from RBS download
directory), you must have \Windows dir specified as is in TD.

KM

> KM,
> we have created a minimal .sdi file of 100MB and we could load the
> ramdisk from the development system.. After it was loaded , gave the
> eroor:
>
> Windows could not start because the following file missing or corrupt:
>
> <Windows root>\system32\ntoskernel.exe
> Please re-install a copy of the above file.
>
> We have checked the ntoskernel.exe file in System32 in my image. What
> could
> be the reason for the eroor. What does <Windows root> means ?

embedded_msit
07-09-2005, 09:24 PM
KM
i have checked boot.ini in Downlaods folder of RBS, i m using the default
one.It sill gives

Windows could not start because the following file missing or corrupt:

<Windows root>\system32\hal.dll
Please re-install a copy of the above file.

KM
07-09-2005, 09:24 PM
embedded_msit,

What is your Windows folder path? (the exact path at run time)
What was the image directory layout when you captured it in the SDI file?

Also show us the output of command like "sdimgr <your sdi file>".

KM


> KM
> i have checked boot.ini in Downlaods folder of RBS, i m using the default
> one.It sill gives
>
> Windows could not start because the following file missing or corrupt:
>
> <Windows root>\system32\hal.dll
> Please re-install a copy of the above file.
>

embedded_msit
07-09-2005, 09:24 PM
KM,

Drive E is my SDI virtual drive and i have copied all my files on to E. So
we have E:\WINDOWS,E:\Documents and Settings etc. Then used the cmd

sdimgr /new image.sdi It gave output

SDI File Manager version 1.00.621
Copyright <c> 1999-2001 Microsoft Corp.

Sdi File : c:\Program Files\Windowd Embedded\utilities\image.sdi
MDB Type: ---
Boot Code Offset : 0x00000000.00000000
Boot COde Size : 0x00000000.00000000
Vendor ID : 0x0000 <0>
Device ID : 0x0000 <0>
Device Model : <00000000-0000-0000-0000-000000000000>
Device Role: 0
Runtime GUID : <00000000-0000-0000-0000-000000000000>
Runtime OEM Rev :0
Page Alignment : 1 <4096 bytes>

Then i used the cmd

sdimgr image.sdi /readpart:e: It gave output

SDI File Manager version 1.00.621
Copyright <c> 1999-2001 Microsoft Corp.

*Reading from volume: "\\.\E:" ...

image.sdi was successfully created and i copied it to C:\Program
Files\Windows Embedded\Remote Boot Service\Downloads folder

I used the default boot.ini is that folder.Its contents are
[boot loader]
default=ramdisk(0)\WINDOWS
[operating systems]
ramdisk(0)\WINDOWS="Windows Embedded XP" /fastdetect

Then i booted the deployment from LAN.

KM
07-09-2005, 09:24 PM
embedded_msit,

Actually I have asked for the output of "SDIMgr <your sdi file>" command only.
But regardless, your steps looks good to me so, I think, the image is ok. (Only caveat: please add "SDIMgr yourSDIfile.sdi /pack"
command at the end)

What do you specify as Boot Image and Boot Parameters in the RBM GUI? (Remote Boot Manager)
You should specify the Boot Image at least since the boot.ini you used is the default one and doesn't use the /rdpath switch.

--
Regards,
KM, BSquare Corp.

PS. Btw, you can "test" your image locally on the device.
Just copy the SDI image to root of partitioned and formatted local HDD. Also put ntldr, ntdetect and boot.ini there.
The boot.ini ARC path should be include this:
/rdpath=multi(0)disk(0)rdisk(0)partition(1)\yourSDIfile.s-di /rdimageoffsett=4096

KM

> KM,
>
> Drive E is my SDI virtual drive and i have copied all my files on to E. So
> we have E:\WINDOWS,E:\Documents and Settings etc. Then used the cmd
>
> sdimgr /new image.sdi It gave output
>
> SDI File Manager version 1.00.621
> Copyright <c> 1999-2001 Microsoft Corp.
>
> Sdi File : c:\Program Files\Windowd Embedded\utilities\image.sdi
> MDB Type: ---
> Boot Code Offset : 0x00000000.00000000
> Boot COde Size : 0x00000000.00000000
> Vendor ID : 0x0000 <0>
> Device ID : 0x0000 <0>
> Device Model : <00000000-0000-0000-0000-000000000000>
> Device Role: 0
> Runtime GUID : <00000000-0000-0000-0000-000000000000>
> Runtime OEM Rev :0
> Page Alignment : 1 <4096 bytes>
>
> Then i used the cmd
>
> sdimgr image.sdi /readpart:e: It gave output
>
> SDI File Manager version 1.00.621
> Copyright <c> 1999-2001 Microsoft Corp.
>
> *Reading from volume: "\\.\E:" ...
>
> image.sdi was successfully created and i copied it to C:\Program
> Files\Windows Embedded\Remote Boot Service\Downloads folder
>
> I used the default boot.ini is that folder.Its contents are
> [boot loader]
> default=ramdisk(0)\WINDOWS
> [operating systems]
> ramdisk(0)\WINDOWS="Windows Embedded XP" /fastdetect
>
> Then i booted the deployment from LAN.
>
>
>

ibali
07-09-2005, 09:27 PM
Hi;

I have been reading your thread about the problems you are having
trying to deploy a custom Windows XP Embedded OS. Our problems are
exactly the same as yours and you seem to have gone through the same
steps and errors that we have. I have raised a support request with
Microsoft, but that may take some time. I just though I would see if
you had any luck in getting a Windows XPe system deployed.

Please contact me on ian.iball@cardium.co.uk of you have any
information, likewise if i get any information back from Microsoft I
will post it into this thread.

Thanks in advance

Ian


--
ibaliPosted from http://www.pcreview.co.uk/ newsgroup access


Re: Remote Boot Service