J
John F. Davis
Hello
I thought I had remote boot working, but I don't. Instead, I can
netboot the startrom.n12 file and it will boot embedded off my hard
disk. If I remove my hard disk I can no longer "netboot". The reason
it appeared to work was that my embedded image that I netbooted was
the same as the one on the hard disk. I had to run fba right? So
when I did the test where I didn't have the disk installed it failed.
Testing the setup.
When I power on the target, it contacts the dhcp server to get its
ipaddress, then it downloads these files from my development machine
in this order using tftp:
startrom.n12
ntldr
(bootfont.bin)
( it tries to download it but its not there. I don't
know where to find this file.)
boot.ini
ntdetect.com
ramdisk.sdi
During this time I see the following screens on the target:
It shows the netboot screen where it displays the tftp
transfers, then it shows the boot.ini screen, then it shows the
"loading RAMDISK image" with the black and white scroll bar. This
screen will go on for a long time because its transferring the ~100mb
ramdisk image. Finally it shows the Windows XP graphic and its
progress bar. Shortly afterwards, it goes into the blue screen with a
message that a problem has been detected and windows has been
shutdown. It tells me there is a problem with my disks? I dn't have
any disks so I am confused.
Here is my setup:
o Creating the ram disk:
1. Create a target filesystem.
2. Copy filesystem to target computer.
3. Boot the target so it runs fba.
4. copy the result to a ramdisk created using sdi
5. run the scripts to create a second ramdisk using the first one.
see earlier posts in this group for more info.
o Setting up the dhcp server:
filename "startrom.n12"
next-server "ip address where the ramdisk is located"
Do not specify the option PXE.mtftp-ip because it will cause
ftp to be invoked instead of tftp on the next-server.
o Setting up the remote boot manager:
This part does not seem to matter to me, but I didn't tweak
the defaults. See an earlier post for more info.
o Setting up the boot.ini:
[boot loader]
timeout=30
default=ramdisk(0)\windows
[operating systems]
ramdisk(0)\windows="default" /fastdetect /rdpath=net(0)\ramdisk.sdi
/rdimageoffset=4096
I thought I had remote boot working, but I don't. Instead, I can
netboot the startrom.n12 file and it will boot embedded off my hard
disk. If I remove my hard disk I can no longer "netboot". The reason
it appeared to work was that my embedded image that I netbooted was
the same as the one on the hard disk. I had to run fba right? So
when I did the test where I didn't have the disk installed it failed.
Testing the setup.
When I power on the target, it contacts the dhcp server to get its
ipaddress, then it downloads these files from my development machine
in this order using tftp:
startrom.n12
ntldr
(bootfont.bin)
( it tries to download it but its not there. I don't
know where to find this file.)
boot.ini
ntdetect.com
ramdisk.sdi
During this time I see the following screens on the target:
It shows the netboot screen where it displays the tftp
transfers, then it shows the boot.ini screen, then it shows the
"loading RAMDISK image" with the black and white scroll bar. This
screen will go on for a long time because its transferring the ~100mb
ramdisk image. Finally it shows the Windows XP graphic and its
progress bar. Shortly afterwards, it goes into the blue screen with a
message that a problem has been detected and windows has been
shutdown. It tells me there is a problem with my disks? I dn't have
any disks so I am confused.
Here is my setup:
o Creating the ram disk:
1. Create a target filesystem.
2. Copy filesystem to target computer.
3. Boot the target so it runs fba.
4. copy the result to a ramdisk created using sdi
5. run the scripts to create a second ramdisk using the first one.
see earlier posts in this group for more info.
o Setting up the dhcp server:
filename "startrom.n12"
next-server "ip address where the ramdisk is located"
Do not specify the option PXE.mtftp-ip because it will cause
ftp to be invoked instead of tftp on the next-server.
o Setting up the remote boot manager:
This part does not seem to matter to me, but I didn't tweak
the defaults. See an earlier post for more info.
o Setting up the boot.ini:
[boot loader]
timeout=30
default=ramdisk(0)\windows
[operating systems]
ramdisk(0)\windows="default" /fastdetect /rdpath=net(0)\ramdisk.sdi
/rdimageoffset=4096