Hi,

> I'm using a Linux box as the MOP server. I followed the instructions for
> setting it up here:
>
> http://linux-vax.sourceforge.net/download/README.vaxroot-20010920

Try:
http://www.netbsd.org/Documentation/network/netboot/
and
http://world.std.com/~bdc/projects/vaxen/VAX-netboot-HOWTO.html

Maybe they have something different that you've missed.


> I've been watching the downloads - the machines are at least starting to
> grab the image. I do not know if the image is getting messed up in the
> transfer process.
>
> I also have a working InfoServer 100 that does handles MOP requests to VAX.
> I may have to burn a CD with the various kernels and attempt to boot from
> this DEC InfoServer if everything else fails.
>
> *Something* is making to the VAXen. It's attempting to execute whatever
> came across the network......

Maybe try to re-fetch the binary kernels. Make sure ftp is in binary mode.

I know that when I set up my VAX, mopd was not exactly easy to get
working, but it wasn't really all that hard - but there were a few things
that could've been better documented.

And I do notice that the Linux how-to only lists support for the various
3100s and the 4000/60, and the 4000/60 is vastly different from the
4000/300 and 4000/500.

But since your problems are pretty consistent, it could be an issue with
the binary files (re-fetch), or the only other thing I can think of at the
moment is a possible problem with your network. The VAX aren't connected
to an auto-switching 10/100-base-T hub, are they? I've had problems with
them...

You might also be interested in a quick mopd how-to I wrote a while ago:
http://mail-index.netbsd.org/port-vax/2001/06/04/0022.html
(replace NetBSD-1.5 in those URLs with 1.5.2, of course)

John Klos
Sixgirls Computing Labs