H
Harald Jennerich
Hi,
Is it possible to boot MSDOS Operating system which is stored on an SDI
Image?
I have a working network solution based on BFD107 Network Bootdisk including
USB 2.0 Disk and CD Support for Cloning XPE Images with Symantec Ghost or
Powerquest PQDI.
I want to keep all the server related stuff (Ghost...) in one image to be
able to deploy
updates of my XPE - Images on either USB Harddisk, Net. or CD..
I think if i could build a SDI image and boot it with ntldr I could use
exactly
one image ( >2.8MB incl. PQDI ) for this purpose.
I tried to create a SDI image with a "bootsect.dos" in the C:\ Drive .
boot.ini: Disk
ramdisk(0)\bootsect.dos="hda1:MSDOS for PQDI" /sos
/rdpath=multi(0)disk(0)rdisk(0)partition(1)\bfd107.sdi /rdimageoffset=4096
/noguiboot
boot.ini: Network
ramdisk(0)\bootsect.dos="net0:MSDOS for PQDI" /sos
/rdpath=net(0)\bfd107.sdi /rdimageoffset=4096 /noguiboot
I guess that my "bootsect.dos" cannot be used to start from NT-Ramdisk and
I have to
write a special SDI loader.
If I try the Ramdisk boot from network with the above entry in "boot.ini"
the
ntldr was never seen to read the file "bootsect.dos" when i logged the
network
traffic with Ethereal. Instead ntldr trys to find a ntoskrl in the RAMDISK.
Is that correct?
Any idea to get a working solution?
kind regards
Harald
Is it possible to boot MSDOS Operating system which is stored on an SDI
Image?
I have a working network solution based on BFD107 Network Bootdisk including
USB 2.0 Disk and CD Support for Cloning XPE Images with Symantec Ghost or
Powerquest PQDI.
I want to keep all the server related stuff (Ghost...) in one image to be
able to deploy
updates of my XPE - Images on either USB Harddisk, Net. or CD..
I think if i could build a SDI image and boot it with ntldr I could use
exactly
one image ( >2.8MB incl. PQDI ) for this purpose.
I tried to create a SDI image with a "bootsect.dos" in the C:\ Drive .
boot.ini: Disk
ramdisk(0)\bootsect.dos="hda1:MSDOS for PQDI" /sos
/rdpath=multi(0)disk(0)rdisk(0)partition(1)\bfd107.sdi /rdimageoffset=4096
/noguiboot
boot.ini: Network
ramdisk(0)\bootsect.dos="net0:MSDOS for PQDI" /sos
/rdpath=net(0)\bfd107.sdi /rdimageoffset=4096 /noguiboot
I guess that my "bootsect.dos" cannot be used to start from NT-Ramdisk and
I have to
write a special SDI loader.
If I try the Ramdisk boot from network with the above entry in "boot.ini"
the
ntldr was never seen to read the file "bootsect.dos" when i logged the
network
traffic with Ethereal. Instead ntldr trys to find a ntoskrl in the RAMDISK.
Is that correct?
Any idea to get a working solution?
kind regards
Harald