20020606104358.A6029@mas1.ats.ucla.edu">Not exactly. My code is:/......./netboot/bootrom/netdrvr/pktdrvr/packet.S (not setup.S).
Do you mean add the one line:
setmd5: mov ah,#SET_RCV_MODE
mov cx,#MODE_DIRECTED
stc <<<--- added
call callpkt
jnc setmd9
cmp dh,#ERR_BAD_COMMAND
je setmd9
setmd5: mov ah,#SET_RCV_MODEsetmd6: .....
mov cx,#MODE_DIRECTED
stc
20020606104358.A6029@mas1.ats.ucla.edu">
I'll try it, but I don't see how that will help as I'm not getting any
error message nor any packets being sent. This change to the code is
in the part which sets receive mode. I'd guess it's possible that if
setting receive mode fails then netboot just dies or loops. But I would
expect that netboot would either issue some error message about a failure
or still send packets and then be unable to receive them
20020606104358.A6029@mas1.ats.ucla.edu">
Since I want to use a floppy to start a PXE boot I need 0.9.3 or else
I'd have to have support multiple ways to boot. New machines can boot
PXE right from their BIOS, this is to enable old machines to use the
same PXE server by being booted from a floppy.
A third case is to have a modified netboot which allows overriding the
TFTP server host manually to allow booting a machine from a server on
a different subnet without any boot "helpers". This part doesn't need
PXE support, but I'd rather have the latest netboot (or at least the
same netboot).
===========================================================================
This Mail was sent to netboot mailing list by:
Michael Stein <mas@ucla.edu>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.
For requests or suggestions regarding this mailing list archive please write to netboot@gkminix.han.de.