The first thing to check is that boot.mop is not corrupted. Look at the MD5 
signature and compare it with the output of MD5 boot.mop on the server. If 
they are different then the most likely cause is corruption due to an ASCII 
mode FTP transfer rather than a BINARY mode transfer.

--Chuck

At 11:28 AM 6/20/02, Braamse, Joop wrote:

>Today I tested netboot.
>
>I downloaded the bootfile (june 18) from the netboot directory and I 
>copied it to my linux box which is the bootserver.
>
>My Vax 3100-M48 does not load boot.mop, it hangs after ">>>b esa0"
>
>My Vax 4000-105a does not load it either, it produces a message: ?HLT INST 
>PC00000001
>
>Both of them used to be happy with the 1.5.x boot.mop.