Re: S100 Floppy Controller Question
- From: no.spam@xxxxxxxxxxxxxxxxxxxxxxx
- Date: Thu, 14 Feb 2008 12:51:32 GMT
On Thu, 14 Feb 2008 05:58:39 -0600, "Robert J. Stevens"
<ztrebora@xxxxxxxxxx> wrote:
Richard A. Cini wrote:
Following up, I just found a Morrow DiskJockey 2D/B in one of my boxes. ThisI also have a SSSD Floppy marked CP/M 2.2 24K
model only has a 50-pin connector and the manual talks about the SA800, so
I'm assuming it's an 8"-only controller.
The label on the left says 24K vs CPM 2.2 of 2-4-82
BIOS For 2 FD STD Console and Printer
Serial # 2020-1688
copyright 1983 digital research
I got this from Don Tarbell when I purchased a system from him.
This together with the D/J floppy certainly would make it possible to
generate a system for the D/J
I would need a Couple of GOOD SSSD 8" floppies to make copies on
TIA
Bob
If the goal is to make a working system you need to do things. One is
have a copy of some (any!) CP/M2.2 media with a known system on it.
That is the CCP, BDOS, and some BIOS. You ned to be able to read that
disk at the sector level and save the results in ram. This will allow
you to capture the useful ccp and bdos. However unless the bios is
for teh machie your using and I mean specifically the FDC don't
bother with it. If the FDC in use matches the BIOS then it's
reasonable to grab the bios and with a DDT like tool or similar
hand edit the console IO to match the system in use.
BDOS and CCP are generic. The BIOS MUST match all I/O be it disk
or terminal I/O. Within the BIOS if the disk I/O is a match but the
console is wrong it's possible and doable (tools permiting) to patch
the I/O for the I/O in use.
Now, to make a point. nearly all of the above can be done on a PC.
You can download CCP/BDOS and mayb even a bios. The challange is
getting it in the box so you can boot it. If the bos has a Rom
monitor it's easier, if not you need to get a rom monitor going or
your either stuck with a front panel if it has one or your own
devices..
In the end PC can be handy as there are enough SIMs to run, test and
even create new code including a BIOS. Getting it in the box and on a
working disk is usually far less frustrating is you have a working
system even if it's not the target system.
FOR S100:
For years I used my NS* system by transplanting the controller in to
others to boot and then copy needed new system, code into place
to create new boot media and all. usually rather than put the NS*
controller in a new crate I would install the target systems FDC and
I/O if there wer no conclicts in the NS* crate. Boot NSdos or NS*
CP/M
and start testing and building the BIOS for the new FDC or
copy a know "system" to that floppy is I already had it. This works
well as the NS* was memory mapped and most other FDCs are
I/O mapped. However IF I/O addresses are not in conflict I've put the
new FDC in my CCS and did the needed work to test and build
media as needed.
For non S100 you really need a monitor program to get and put bytes
into ram.
Allison
.
- References:
- Re: S100 Floppy Controller Question
- From: Robert J. Stevens
- Re: S100 Floppy Controller Question
- Prev by Date: Re: S100 Floppy Controller Question
- Next by Date: Re: WTB a copy of MS-DOS by Gifford for the COMPUPRO 816
- Previous by thread: Re: S100 Floppy Controller Question
- Next by thread: Re: WTB a copy of MS-DOS by Gifford for the COMPUPRO 816
- Index(es):
Relevant Pages
|
