On Tue, 20 Apr 1999, Daniel A. Seagraves wrote:

> Here's what I've got so far, this is on a 3100 of unknown model, (How
> do I tell which model I have anyway?), 1 Gb SCSI-2 disk, (Micropolis
> 2112 if it matters), and 4 meg of RAM.

If it just says VAXstation 3100 on the front, then it's going to be either
an M30 or an M40.  The M40 just having a taller case than the M30 to allow
for more storage.  You can also tell from the kernel boot messages.  One
of the first things which happens during kernel boot is the identification
of the CPU type.

Of course, I suppose you may have a VAXserver 3100 or MicroVAX 3100 which
are different than the VAXstation 3100, but are like eachother.  I don't
know if anyone's tested SCSI support in a MicroVAX 3100 system (like the,
10, 20, 10e, or 20e).  It may not work there, and you'd certainly have
problems with any of the newer MicroVAX 3100s.

> 1.	disklabels don't work.  They have no effect.
> 	The bootloader doesn't appear to get installed right either.

Haven't played with this just yet on any of my VS3100's.

> 2.	I occasionally get (about 50% of the time really) the message:
> 	"ptelen fault in system space: addr xxxxxxx pc xxxxxxxx"
> 	and a halt.  This mostly happens at random points during
> 	the boot, but it's happened while running twice now.
> 
> And that's it...  I'm gonna try a different VAX in a second, another 3100
> but a different model.  I'm gonna use another 2112 (Don't wanna wax
> VMS just yet...) and see what happens.  The other one has more memory
> I think.
> 
> Anyone else with a 3100 have any luck?

I've had really good luck so far in netbooting 1.4_ALPHA on the VAXstation
3100 M30, M38, and M76.   I can't vouch for the SCSI support yet.

-brian.
---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!