Hi Nick
Thank you for the reply.
The first option you suggested (Unetbootin) didn't work for me.
Although the bootable floppy was created, it failed during the boot
because of a lack of initrd image.
But, the "dd for Windows" option worked great.
Unfortunately, when I booted to this floppy, no network devices were
found.
Next, as you had suggested for my EeePC 901, I enabled the Onboard LAN
Rom.
This time, the netboot failed as usual because of lack of boot
filename. However, unlike on the EeePC, no network devices were found
when the floppy took over.
I presume this means that whatever network driver was left by the PXE
bootloader, didn't get on so well with the bootloader on the floppy.
When the netboot attempt bailed out, what appeared on the screen was:
"Loading ROM
Image.......................................................
gPXE Initializing devices............."
and there it stayed. I left it for up to 30 minutes but nothing
changed.
The network card on this computer is a SiS190.
One difference I've noticed from the EeePC experience is that, when
netbooting, no opportunity to configure the SiS1901 PXE Boot ROM
appears whereas I had to change a couple of parameters in the Atheros
Boot ROM device before it worked on the EeePC. I'll investigate this.
Any more cards in the sleeve?
On Sep 11, 4:07 am, Nick Johnson <
arach...@notdot.net> wrote:
> Hi Paul,
>
> I haven't yet straightened out all the wrinkles regarding using unetbootin,
> since I don't have a windows machine to use as a test platform. In the
> meantime, your best option is either:
> - Downloadhttp://
static.netboot.me/gpxe/netbootme.lkrnand set it as the