Re: network booting

[Jonno Downes <jonnosan@gmail.com>]

On Jan 15, 12:56 am, ol...@web.de (Oliver Schmidt) wrote:
> >Some other obvious
> >enhancements are:
> >- a menu driven directory so you can select from all the files on the
> >server
>
> But this would beyond DCHP/TFTP specs...

Yes, I am creating a seperate protocol (tentatively called "trivial
network disk protocol") that will do the following
1) provide a catalogue of all "volumes" (i.e. dsk & d64 images) hosted
on a server
2) allow individual sectors on a hosted volume to be read/written

then I intend to create a DOS image that
1) has a command to allow the catalogue of volumes to be d/led from
the server and a dsk selected
2) has RWTS patched to redirect  sector read/write requests to the
server.

The full bootstrap then would be
1) DHCP to get IP address
2) TFTP to d/l and execute the patched DOS 3.3 image
3) Patched DOS 3.3. pops up a menu from which one of the dsks served
from the netboot65 server can be selected
4) the HELLO from the selected dsk is executed (or if there is  no
HELLO, then a catalogue is displayed, and the user can RUN/BRUN as
necessary).

>
> - WinPcap works fine with the "Microsoft Loopback Adapter".
> - Both VICE and AppleWin put the WinPcap into promiscuous mode which
> doesn't work with many/most WiFi drivers.

If I connect Vice/AppleWin to "Microsoft Loopback Adapter", does that
mean I could only talk to the host machine that the emulator is
running on?

My challenge is, I want to get a DHCP address dished out by my
broadband router, and then talk TFTP and my custom protocol to a
server running on the host machine.