Hello, I am having trouble getting a image to boot from a PXE.

Right after PXE on the client PC has loaded something happens... Something
on the client PC screen tells me "hal.dll" is corrupted or missing.

This is what I tried so far:
I searched for it in the "Target designer" and it was in my image under
"Standard PC". So, that should be right.
I disabled the cdrom and hardisk on the client. I also tried different
"Target Device Settings". Boot path as "ramdisk(0)" or
"multi(0)disk(1)rdisk(0)partition(1)" did not make any difference. I tried
boot device as "C:", but other driver letters too.
I tried copying the image to a mounted SDI and the to the "Remote Boot"
"Downloads" directory, but I also tried this as a bat:
del c:\ramdisk.sdi
cscript sdimgr.wsf /new c:\ramdisk.sdi
cscript sdimgr.wsf c:\ramdisk.sdi /readpart:e:
cscript sdimgr.wsf c:\ramdisk.sdi /import:BOOT,0,"C:\Program Files\Windows
Embedded\Remote Boot Service\Downloads\startrom.com"
cscript sdimgr.wsf c:\ramdisk.sdi /import:LOAD,0,"C:\Program Files\Windows
Embedded\Remote Boot Service\Downloads\ntldr"
cscript sdimgr.wsf c:\ramdisk.sdi /pack
cscript sdimgr.wsf c:\ramdisk.sdi
copy c:\ramdisk.sdi "C:\Program Files\Windows Embedded\Remote Boot
Service\Downloads\".

Can anyone help me? Thanks in advance.

Did you add the Windows Ram Disk driver component. You dont need to have the
LOAD, BOOT blob in your SDI if you are trying to remote boot. Follow the
steps outlined in this document.
http://msdn.microsoft.com/library/de...otoverview.asp

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


"julien langeveld" <(E-Mail Removed)> wrote in message
news:uG9Gjm%(E-Mail Removed)...
> Hello, I am having trouble getting a image to boot from a PXE.
>
> Right after PXE on the client PC has loaded something happens... Something
> on the client PC screen tells me "hal.dll" is corrupted or missing.
>
> This is what I tried so far:
> I searched for it in the "Target designer" and it was in my image under
> "Standard PC". So, that should be right.
> I disabled the cdrom and hardisk on the client. I also tried different
> "Target Device Settings". Boot path as "ramdisk(0)" or
> "multi(0)disk(1)rdisk(0)partition(1)" did not make any difference. I tried
> boot device as "C:", but other driver letters too.
> I tried copying the image to a mounted SDI and the to the "Remote Boot"
> "Downloads" directory, but I also tried this as a bat:
> del c:\ramdisk.sdi
> cscript sdimgr.wsf /new c:\ramdisk.sdi
> cscript sdimgr.wsf c:\ramdisk.sdi /readpart:e:
> cscript sdimgr.wsf c:\ramdisk.sdi /import:BOOT,0,"C:\Program Files\Windows
> Embedded\Remote Boot Service\Downloads\startrom.com"
> cscript sdimgr.wsf c:\ramdisk.sdi /import:LOAD,0,"C:\Program Files\Windows
> Embedded\Remote Boot Service\Downloads\ntldr"
> cscript sdimgr.wsf c:\ramdisk.sdi /pack
> cscript sdimgr.wsf c:\ramdisk.sdi
> copy c:\ramdisk.sdi "C:\Program Files\Windows Embedded\Remote Boot
> Service\Downloads\".
>
> Can anyone help me? Thanks in advance.
>
>
>
>
>

Thank you for you help. I am now booting into FBA, but it hangs at
"initializing profiles". I am trying to figure out how to solve this. If you
have any ideas. Please let me know.



(will this mgs be posted under my post or as a new topic? will see)

"greg" <(E-Mail Removed)> wrote in message
news:086601c36cad$925b12d0$(E-Mail Removed)...
> Hi,
>
> I had the same problem. For me, it was because my SDI
> image was corrupted. I transfered it from my development
> PC to my TFTP server by using ftp (but in ASCII
> mode !!!). When I transfered it in binary mode, no
> problem.
>
> Hope it could help...
>
> Greg
>
>
> >-----Original Message-----
> >Did you add the Windows Ram Disk driver component. You
> dont need to have the
> >LOAD, BOOT blob in your SDI if you are trying to remote
> boot. Follow the
> >steps outlined in this document.
> >http://msdn.microsoft.com/library/default.asp
> url=/library/en-
> us/remboot/html/xpconremotebootoverview.asp
> >
> >Nandini
> >This posting is provided "AS IS" with no warranties, and
> confers no rights
> >
> >
> >"julien langeveld" <(E-Mail Removed)> wrote in
> message
> >news:uG9Gjm%(E-Mail Removed)...
> >> Hello, I am having trouble getting a image to boot
> from a PXE.
> >>
> >> Right after PXE on the client PC has loaded something
> happens... Something
> >> on the client PC screen tells me "hal.dll" is
> corrupted or missing.
> >>
> >> This is what I tried so far:
> >> I searched for it in the "Target designer" and it was
> in my image under
> >> "Standard PC". So, that should be right.
> >> I disabled the cdrom and hardisk on the client. I also
> tried different
> >> "Target Device Settings". Boot path as "ramdisk(0)" or
> >> "multi(0)disk(1)rdisk(0)partition(1)" did not make any
> difference. I tried
> >> boot device as "C:", but other driver letters too.
> >> I tried copying the image to a mounted SDI and the to
> the "Remote Boot"
> >> "Downloads" directory, but I also tried this as a bat:
> >> del c:\ramdisk.sdi
> >> cscript sdimgr.wsf /new c:\ramdisk.sdi
> >> cscript sdimgr.wsf c:\ramdisk.sdi /readpart:e:
> >> cscript sdimgr.wsf
> c:\ramdisk.sdi /import:BOOT,0,"C:\Program Files\Windows
> >> Embedded\Remote Boot Service\Downloads\startrom.com"
> >> cscript sdimgr.wsf
> c:\ramdisk.sdi /import:LOAD,0,"C:\Program Files\Windows
> >> Embedded\Remote Boot Service\Downloads\ntldr"
> >> cscript sdimgr.wsf c:\ramdisk.sdi /pack
> >> cscript sdimgr.wsf c:\ramdisk.sdi
> >> copy c:\ramdisk.sdi "C:\Program Files\Windows
> Embedded\Remote Boot
> >> Service\Downloads\".
> >>
> >> Can anyone help me? Thanks in advance.
> >>
> >>
> >>
> >>
> >>
> >
> >
> >.
> >