Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ptsfa!ihnp4!homxb!houxm!whuts!whuxm!davew
From: davew@whuxm.UUCP
Newsgroups: comp.os.cpm
Subject: configuring CP/M with ddsysgen
Message-ID: <533@whuxm.UUCP>
Date: Tue, 5-May-87 15:41:40 EDT
Article-I.D.: whuxm.533
Posted: Tue May  5 15:41:40 1987
Date-Received: Fri, 8-May-87 05:18:30 EDT
Organization: AT&T Bell Laboratories
Lines: 45
Keywords: HELP needed

I've got an ATR8000 CP/M system, and I'm having trouble adding new drives.
I'm not sure how much of the following is true on other CP/M 2.2 systems,
and how much is specific to my machine.

The ATR8000 can use several types of drives, single or double sided, 5 1/4
or 8 inch, all at once.  The manual instructs you to patch CP/M with
the "ddsysgen" program to configure it for the drives you install.
ddsysgen is a variant of "sysgen" for double density, which has an option
called "generate custom CP/M".  I got a new disk drive a while back, set
the drive number on it, and plugged it in... so far, so good.

So I tried to patch CP/M with "ddsysgen".  I read in the system tracks,
and then selected the option to customize CP/M.  It requested the file
"SYSTEM.SWP", (SWP, INC. makes the machine).  According to the manual,
this file contains the symbolic names of all the parameters you might need
to change.  I was then prompted for names of locations within CP/M, and
I was shown the contents to each location, and allowed to change it.

The problem came when I looked at some of the parameters, like "ONEDSK"
(which makes the system use only one drive), or "RATEB" (which controls
the step rate of drive B), or the parameter which controls the number of
tracks on a drive (I've forgotten the name).  Some of the values there
didn't seem to agree with what the manual said should be there.  And
when I changed them, strange things happened.  They happened even when I
took the new drive off the system, but not when I went back to my backup
copy of CP/M.

It sounds a bit like I've got a bad copy of "SYSTEM.SWP", and I was just
trashing random parts of the OS when I changed things.  What I want to
know is: 

1) Has anyone out there had any similar problems, and what did you do?

2) What might be the problem, other than a bad system file?

3) What can I do about it?  I've done some hacking of disassembled code
on micros before, and I'd rather not do it again.

HELP!

-- 
David Wonnacott			"They said Van Gogh was crazy, didn't they?"
whuxm!davew  or  rz3bb!davew
AT&T Corporate Education
The above opinions are not necessarily those of AT&T, or of anyone else anywhere