First off, what Michael asked for:

>>> e/i 3e
  I 0000003E 12000003

>>> e/p 20040004
  P 20040004 04140001

>>> 

>> And NetBSD mostly works, provided I use the 20010509-1.5.1_BETA2
>> snapshot kernel.  (The 1.4.2 kernel hiccups badly with the serial
>> line, doesn't find the SCSI interface at all, and panics as soon as
>> I try to "Enter pathname of shell or RETURN for sh: "; I haven't
>> tried my 1.4T source tree's GENERIC kernel yet.)
> That machine wasn't supported by 1.4.

I've reached that conclusion already. :-)

> Why are you trying to run that old release? :-)

Because it's what all my other machines run.

I may be able to get away with doing a mass switch to 2000-03-09
sources; I may have to backport...I don't yet know.

>> [...OS calls it a KA46, a 4000/60...]
> It probably doesn't matter at all.  The identification part is just
> cosmetic,

Okay, I won't lose any sleep over that.

> but I assume that Michael will ask you about some valuse soon and
> then it will be fixed :-)

See above :-)

>> WARNING: you must update your boot blocks.
> Yes, you are using 1.4 boot blocks with an 1.5 kernel.
>> 	2) The booter doesn't know how to do timeouts; I see
> Because you are using a too old boot. Update your boot blocks :-)

Which brings up another issue: I have a disk in the machine, but I've
been unable to render it bootable:

>>> boot dka100

 
-DKA100
  83 BOOT SYS
 
Is this just another artifact of the age of the bootblocks I'm using?
The network booter (">> NetBSD/vax boot [Mar  7 2000 04:32:44] <<")
seems perfectly happy, except as noted above, but it seems plausible
that disk bootblocks would be touchier than network bootblocks.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B