12 Sep
2000
12 Sep
'00
10:47 a.m.
Zane writes:
What happens if that MV2 CPU board dies?
You stick another MV2 CPU in. On early Vax hardware the cpu ID is either
backplane wirewraps, a DIP switch, or just the same for all CPU's of
the same model. (Pro350's used a ROM on the motherboard -- so I guess
there may be Vaxes done that way...)
DEC did dip switch CPUid's back to the PDP11's.
On a Sparc (which was brought up in I believe the original question), it's
possible to take a new system and change its hardware ID to match that of
the original system. Is there any way to do this on a VAX, or are you does
your business now go under because you can no longer run this app.
Yup. Depending on model or CPU type. The 11/780's were all wire wrap.
As were the 785's. The 750's were dip switch.
Another example would be what if I want to move this
app from a MV2 to say a
VAXstation 4000/VLC as I've got space problems and I want it to run faster.
Of course this example is of questionable legality since you're licensed to
run this app on a MV2. However, the first example should be perfectly legal
and something you'd want to be able to do.
You don't want to try to change an 11/780 into a 750 since the busses and
instructions may differ.
For example, giving a Sparc4c (Sparc1/1+/2 or similar Sparc -- like the
SparcUp upgrade doubleclocked 4c's) a Sparc10 (Sparc4m) ID may render
them useless because of bus and architecture differences.
The Vaxes are similar, in that you can't switch between families of Vax.
Making a VaxStation 3100 into Microvax2000 may or may not work
correctly.
I wish I could take my Sparc4c's and run Solaris8 on 'em. Sun took
out Support and they supposedly won't even boot it.
Wonder if I lie about the system ID and change the NVRAM, hmm...
Zane
Bill
--
bpechter(a)monmouth.com | Microsoft: Where do you want to go today?
| Linux: Where do you want to go tomorrow?
| BSD: Are you guys coming, or what?