R
Roger Levy
My device will have no attached mass storage of any kind and it will be
headless, keyboardless, mouseless, etc. -- it is just a number cruncher. I want
to boot via Boot Manager over a network although later I might use BXP or
another method. My device is PXE enabled. I am having trouble closing on the
TD configuration I need. I also have not been able to find any discussion of
this configuration in old NG postings or the documentation.
I attach a small disk drive for the FBA process but I want to remove it for
final deployment. Must I therefore always specify a configuration that has disk
drive, IDE controller components, etc. just to avoid Stop 0x7B before FBA? In
order to reduce final footprint, can I remove these components after FBA and
reseal? How will I know exactly what to remove since the components are
realized as a collection of DLLs?
Do I absolutely need EWF in this configuration or since I must have a ramdisk
can "disk" I/O be directed to the ramdisk? When I try to configure EWF I am
asked to select whether it's providing an overlay for an IDE or SCSI device but
my actual final target has neither so what is the interpretation of that
selection?
Finally, when I keep the disk related components in the configuration along with
FAT and FAT Format and then try my network boot, the target's RAMDISK gets is
loaded as evidenced by the progress bar and the transfer of over 100,000 UDP
packets but I get a Stop 6B. I read the FAQ which says this may be caused by
the file system component not matching the actual format of the file system.
But at this point the only file system I actually have is ramdisk. How can I
avoid Stop 0x6B in this instance?
Roger Levy
headless, keyboardless, mouseless, etc. -- it is just a number cruncher. I want
to boot via Boot Manager over a network although later I might use BXP or
another method. My device is PXE enabled. I am having trouble closing on the
TD configuration I need. I also have not been able to find any discussion of
this configuration in old NG postings or the documentation.
I attach a small disk drive for the FBA process but I want to remove it for
final deployment. Must I therefore always specify a configuration that has disk
drive, IDE controller components, etc. just to avoid Stop 0x7B before FBA? In
order to reduce final footprint, can I remove these components after FBA and
reseal? How will I know exactly what to remove since the components are
realized as a collection of DLLs?
Do I absolutely need EWF in this configuration or since I must have a ramdisk
can "disk" I/O be directed to the ramdisk? When I try to configure EWF I am
asked to select whether it's providing an overlay for an IDE or SCSI device but
my actual final target has neither so what is the interpretation of that
selection?
Finally, when I keep the disk related components in the configuration along with
FAT and FAT Format and then try my network boot, the target's RAMDISK gets is
loaded as evidenced by the progress bar and the transfer of over 100,000 UDP
packets but I get a Stop 6B. I read the FAQ which says this may be caused by
the file system component not matching the actual format of the file system.
But at this point the only file system I actually have is ramdisk. How can I
avoid Stop 0x6B in this instance?
Roger Levy