You know, if there is one good the about Pee Cees, it is that whatever can
run on a 12MHz 386 can run on a PIII Xeon 500MHz box.  It may not be
optimized (at that speed, who could tell?), but atleast it will work!  As
great as the vax is, this is something that could have been better.  Low
level stuff.  There is so much work that must be put into getting it to
run on the next model, it just isn't even funny.

No wonder VMS isn't "The Greatest<tm>".  There is a ton of crap in the
low-level stuff that is specific to certain models, all billion and three
or so.  The only good part about this is that when DEC made the screwed up
hardware, it worked, and it usually worked very well.  I guess that is the
price we pay for advancement?

Regards,
John Havard

> > bootserver and the path to the kernel and tries to start the kernel 
> > displaying a row of different numbers and a rotating "/" to indicate work i 
> > progress but crashes as i should ?
> > With out the necessary support for the CPU in the kernel ? Am I on the 
> > right track ?
> 
> So, i just screwed in a bit of CPU support, for now without cache, i should
> know if it works this way, before enabling the cache stuff. Very interesting
> facts are: is QBus working, are the devices detected. So, if someone has some
> QBus cards, no matter what, maybe a DHV-11 or a TQK50 or so, i want to know
> if the kernel sees the devices.
> 
> CPU support is now only added for VAX 4000/500 (KA680), the 4000/200 and
> 4000/105 need some further information, i'll try to find out why the booter
> crashes on these machines.
> 
> So, testers: download the following URL to get a fresh test kernel:
> 
> http://www.camaronet.de/download/netbsd-990911.zip
> 
> Results wanted.
> 
> so long... Michael
> 
>