16 Sep
2007
16 Sep
'07
7:37 p.m.
Subject: RE: Kaypro movcpm.com
From: "Chuck Guzis" <cclist at sydex.com>
Date: Sat, 15 Sep 2007 09:50:08 -0700
To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at
classiccmp.org>
On 15 Sep 2007 at 6:49, dwight elvey wrote:
I don't know about a copy of CP/M but it does ahve a table of all
the addresses inside CP/M (CCP, BDOS and BIOS)that get relocated.
If the system and MOVCPM are from differnt systems (say kayII and
a 4/84) it's very likely the BIOS varies enough that the BIOS
will get mashed. The serial numbmer (besides copyright) was to keep
the two matched or prevent a mess.
My understanding of movcpm.com is that it needs
to be the
exact one that comes with that version. I beleive it has
tables of addresses to replace.
Just so. Since MOVCPM contains a copy of CP/M itself, said copy also
contains a serial number, which must match the one of the system
you're executing MOVCPM on. If you've got a debugger, the point
where the check is made is easy to find and disable, however. Part of DRI's OEM agreement was that each copy of
CP/M had to be
serialized.
There is that but it's a seperate issue.
Allison
Cheers,
Chuck
17 Sep
17 Sep
8:34 a.m.
On 16 Sep 2007 at 14:37, Allison wrote:
Same difference. MOVCPM checks the serial number and quits if the
system S/N doesn't match. Whether or not there was a deeper purpose
is immaterial to the original query. It's what's keep MOVCPM from
running--and is easily circumvented.
Cheers,
Chuck
Part of
DRI's OEM agreement was that each copy of CP/M had to be
serialized.
There is that but it's a seperate issue.
6331
days inactive
6332
days old
1 comments
2 participants
participants (2)
-
ajp166＠bellatlantic.net -
cclist＠sydex.com