12 Sep
2000
12 Sep
'00
11:02 a.m.
From: John Allain <John.Allain(a)donnelley.infousa.com>
The HWID I speak of is a Unique ID per individual CPU.
True. And it identifies the basic hardware and CPU.
Think relicence.
Keep in mind the basic "kits" carry no license or other
machine locked stuff. The license is applied during or
after the install. Even then I've built and installed systems
on my MVII and then carried the media to the MV2000
as both bootable and complete (even licensed if that
is within the written license terms). That was how we
cloned VMS sustems at DEC as it was faster than
using TK50 tapes.
I've put the VMS 7.2kit (cdrom) on everythingt from
MVII and VS2000 through 3100m76 and would expect
it to load and run on most any other VAX as well.
The biggest problem of installing on older hardware
is the minimum system (ram and disk) has grown
during the years and early version coulld fit on 30mb
disk and 1mb ram that has grown to over 150mb
disk and 4mb ram. Though it is possible to shoehorn
the latest version is to less than the specified disk
and ram it is a exercise fort the experienced and will
produce a system of limited utility.
So, Any old copy of VMS can be relicenced for a
matching or nearly matching architecture machine?
Well since all VAX are by definition matching hardware
there is little issue. However there are exceptions
like the RTVAX which is not totally cpu compatable
VAX and differs in the translate tables, it never ran VMS.
Tell me, is that through Montagar?
The VMS7.2 Hobbiest version is available there. Note
HOBBIEST version does not mean stripped or limited.
It means it's packaged with many hobbiest desireable
packages besides VMS itself.
P.S. Can users fo VMSbuilds?
VMSbuild is a standard utility and is used often to configure
custom installs once you have a configureation you want
to standardize on. Anotehr useful VMS utility for small
systems is VMStailor which allows trimming off or adding in
libraries, fonts and other peices to tailor a system.
Allison
12 Sep
12 Sep
12:11 p.m.
Allison wrote:
From: John Allain
<John.Allain(a)donnelley.infousa.com>
I think the real question that was asked might be the following. For
example I might have an old MicroVAX II running some ancient, but mission
critical app. Now suppose the company that wrote this app is no longer in
business, and there is quite literally no source for thier software. It
wasn't resold it just vanished. Now further suppose that they had issued a
license PAK based on the hardware ID of that MV2 you've been running the app
on.
What happens if that MV2 CPU board dies?
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.
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.
Zane
The HWID I speak of is a Unique ID per individual
CPU.
True. And it identifies the basic hardware and CPU.
Think relicence.
Keep in mind the basic "kits" carry no license or other
machine locked stuff. The license is applied during or
after the install. Even then I've built and installed systems
on my MVII and then carried the media to the MV2000
as both bootable and complete (even licensed if that
is within the written license terms). That was how we
cloned VMS sustems at DEC as it was faster than
using TK50 tapes. 
2:47 p.m.
New subject: Vax CPU ID change - Possible? Sparc Model change?
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?
8884
days inactive
8884
days old
2 comments
3 participants
participants (3)
-
ajp166＠bellatlantic.net -
healyzh＠aracnet.com -
pechter＠pechter.dyndns.org