> All I wanted was a way with nothing but Windows to read a VMS
> distro disc. I am now firmly convinced that no such thing is
> possible without buying *some* piece of software.
Did you check http://www.softresint.com/charon-vax/Tools_and_tips.htm like
I'd suggested? I'm not sure what the mkdisk v1.2 is, but I think it might
be what you need. I *KNOW* they had a utility for doing this. If this
isn't it, send me an email asking me to check my Virtual PC system to see if
I've still got a copy of the utility.
Zane
In a message dated 02/28/2003 2:09:28 PM Pacific Standard Time,
thodgson(a)pnc.com.au writes:
> Motorola MCM6665BP20, a 16pin chip with a
> secondary code of FQD8432.
>
64K DRAM 200 ns. made in 1984/32
Paxton
Astoria, OR
Hi all,
does anybody of you know if there is a chance to get a DECNA adapter for my
Pro-350 ? I've got the insane idea to install 2.9bsd with the Pro-3xx
modifications, including the support for the DECNA...
...
Franco Tassone
It's just a little thing, but it's going to bother me when I mount my RX01
in my nice white rack...
Does anyone have a spare white front panel for an RX01 floppy unit? Mine
came without one, I believe because the previous owner (the US Air Force, I
believe) removed it so that the door on the front of the H960 rack it was
mounted in would be able to close.
--
Owen Robertson
> From: ard(a)p850ug1.demon.co.uk (Tony Duell)
Thanks for all of your corrections, it's been some
time since I worked daily with a TRS-80 Model
I/III/IV.
I sold my 4p several years ago (where most of my Model
IV experience comes from).
I agree with you vis-a-vis the floppies. Maybe the
drive is just off speed, and needs a head cleaning.
It could be worse off.
Drive speed can be roughly adjusted using the decal on
the motor and adjusting the pot on the speed board
with a non-ferrous screwdriver (like a TV Adjustment
tool).
I think when I go to Trenton next May, I'll keep my
eye out for a Model III or IV.
Thanks again!
Al
On Feb 28, 10:23, Jochen Kunz wrote:
>
> [ plain text
> Encoded with "quoted-printable" ] :
On 2003.02.28 07:00 Stuart Johnson wrote:
>
> > Jonathan, what I want to know is how do you connect the RX50 and
> > RD(whatever) hard drive to the RQDX3?
> There are different distribution panels that split the 50 pin cable
from
> the RQDXx. The M9058 dist panel for the BA123 looks like a double
QBus
> card and sits in "QBus slot 13" in the BA123. The BA23 dist panel is
> mounted inside the enclosure on the back of the QBus backplane. I
have
> the wiring of this panel, I can mail it to you when you want to build
> your own dist panel. There is a BA213 dist panel that replaces the
front
> panel in a BA213 and has some additional switches LEDs to reset the
CPU
> etc. I think it is not that easy to rebuild this.
It's not that hard to make something that will work. The distribution
panels that split up the signals from the RXDX1/2/3 boards to connect
to RDxx or RX50 are mostly just rerouting signals (some include some
buffering). I've made up two of my own; one simple one, on Veroboard
(stripboard), and one as a PCB. If you look in
http://www.dunnington.u-net.com/public/RQDX/
you'll find the PCB layout and component overlay, along with the RQDX
pinouts, for the larger of the two I made. It includes provision for
switches or jumpers to do the job of the front panel switches. The
circuits for the switches, inbcidentally, are very simple -- a latching
switch, LED, one transistor (to invert the signal, as I recall) and a
few resistors. It needn't even be as complex as that.
I once traced out and re-drew the schematic of the M9058 board, but I
can't find the PostScript file now :-( If I ever do, I'll post it on
the website as well.
--
Pete Peter Turnbull
Network Manager
University of York
Hi Steve
Here they are:
:F0: - :F3: Primary diskettes
:F4: - :F5: Single density on double-density systems
:T1: Teletype keyboard
:T0: Teletype printer
:TP: Teletype Punch
:TR: Teletype reader
:VI: Video term Keyboard
:VO: Video term screen
:HP: High-speed paper tape punch
:HR: High-speed paper tape reader
:LP: Line printer
:CI: Console in
:CO: Console out
:BB: Byte bucket
>From: "Steve Thatcher" <melamy(a)earthlink.net>
>
>
>Hi Dwight, thanks for the reminder email. I had remembered DELETE
>and COPY, but I could not remember all the details. One thing
>that is missing though is what deisgnator was device designator
>was used for the serial connectors on the back. I seem to remember
>console was :CO: and :CI:... if that is correct?
>
>Thanks again.
>
>best regards, Steve
>
>>--- Original Message ---
>>From: "Dwight K. Elvey" <dwightk.elvey(a)amd.com>
>>To: cctalk(a)classiccmp.org
>>Date: 2/28/03 2:37:41 PM
>>
>>From: "Steve Thatcher" <melamy(a)earthlink.net>
>>>
>>>Hi all, I got my Intel MDS225 working today, but I only have
>>>a single double density drive on it. I seem to recall that
>it
>>>would read single density, but you accessed by a different
>drive
>>>specifier. I can't seem to find one bit of documentation on
>the
>>>ISIS command at home. Does anyone have a summary page they
>could
>>>scan and send?
>>>
>>>I am also looking for the 50 pin connection wiring so I can
>connect
>>>a drive externally.
>>>
>>>It was fun booting up ISIS-II version 4.2 and seeing the prompt
>>>come up. I also had a CP/M 2.2 version that booted perfectly!
>>>
>>>best regards, Steve Thatcher
>>>
>>
>>Hi
>> I thought I'd add a list of commands from the users
>>manual for the archives:
>>
>>IDISK <device> <label> [S]
>> S = System
>>FORMAT <device> <label> [<switch>]
>> switch: A = Copy all files from :F0:
>> S = Copy only files with system attribute
>>DEBUG [<progname> [ <parameters> ]]
>>SUBMIT <name>[.<extension>][(<parameter0>,<parameter1>...<parameter9>)]
>> paramters are %0 to %9 in script
>>DIR [FOR <file>][TO <listfile>][<switch>]
>> switch: 0 - 5 = :F0: to :F5:
>> I = List all files including invisible attrib
>> F = Fast listing
>> P = Single drive to DIR second disk
>>COPY <oldfile1>[,<oldfile2>,<oldfile3>...] TO <newfile>[<switch>]
>> switch: U = update but don't change attrib and don't print
>> "ALREADY EXITS"
>> S = System files only when wild card used.
>> N = Non-system files only when wild card used.
>> P = pause for single drive with two floppies
>> Q = Query
>> C = Copy attribs
>> B = Replace, regardless
>>DELETE <file1>[Q}[,<file2>[Q],<file3>[Q]...][P]
>> Q = query confirm
>> P = pause to change disk
>>ATTRIB <file> <attriblist> [Q]
>> Attrib: I0 = Reset invisible
>> I1 = Set invisible
>> W0 = Reset Write protect
>> W1 = Set Write protect
>> F0 = Reset Format attrb F1 = Set Format
>attrb \ Don't mess with this
>> S0 = Reset Syst attrib
>> S1 = Set Syst attrib
>>BINOBJ <binfile> TO <absfile>
>>HEXOBJ <hexfile> TO <absfile>[ START(addr)]
>>OBJHEX <absfile> TO <hexfile>
>>EDIT Tico like commands
>> B$$ = begin of text
>> Z$$ = end of text
>> [n]L$$ = n lines
>> [n]C$$ = n characters
>> Ftext$$ = find "text"
>> Itext$$ = insert "text"
>> Soldtext$[newtext]$$ = find "oldtext" and replace with "newtext
>> [n]D$$ = delete n characters
>> [n]K$$ = delete n lines
>> [n]T$$ = Type n lines 0TT$$ entire line with cursor in line
>> E$$ = Exit
>> Q$$ = quit
>> [n]W$$ = write n lines
>> A$$ = Append
>> M$$ = decimal space available
>> n<commandstring>$$ = Does commandstring n times
>>
>>
>>
>>Hope this helps future ISIS-II users.
>>Dwight
>From: "Steve Thatcher" <melamy(a)earthlink.net>
>
>Hi all, I got my Intel MDS225 working today, but I only have
>a single double density drive on it. I seem to recall that it
>would read single density, but you accessed by a different drive
>specifier. I can't seem to find one bit of documentation on the
>ISIS command at home. Does anyone have a summary page they could
>scan and send?
>
>I am also looking for the 50 pin connection wiring so I can connect
>a drive externally.
>
>It was fun booting up ISIS-II version 4.2 and seeing the prompt
>come up. I also had a CP/M 2.2 version that booted perfectly!
>
>best regards, Steve Thatcher
>
Hi
I thought I'd add a list of commands from the users
manual for the archives:
IDISK <device> <label> [S]
S = System
FORMAT <device> <label> [<switch>]
switch: A = Copy all files from :F0:
S = Copy only files with system attribute
DEBUG [<progname> [ <parameters> ]]
SUBMIT <name>[.<extension>][(<parameter0>,<parameter1>...<parameter9>)]
paramters are %0 to %9 in script
DIR [FOR <file>][TO <listfile>][<switch>]
switch: 0 - 5 = :F0: to :F5:
I = List all files including invisible attrib
F = Fast listing
P = Single drive to DIR second disk
COPY <oldfile1>[,<oldfile2>,<oldfile3>...] TO <newfile>[<switch>]
switch: U = update but don't change attrib and don't print
"ALREADY EXITS"
S = System files only when wild card used.
N = Non-system files only when wild card used.
P = pause for single drive with two floppies
Q = Query
C = Copy attribs
B = Replace, regardless
DELETE <file1>[Q}[,<file2>[Q],<file3>[Q]...][P]
Q = query confirm
P = pause to change disk
ATTRIB <file> <Attriblist> [Q]
Attrib: I0 = Reset invisible
I1 = Set invisible
W0 = Reset Write protect
W1 = Set Write protect
F0 = Reset Format attrb \
F1 = Set Format attrb \ Don't mess with this
S0 = Reset Syst attrib
S1 = Set Syst attrib
BINOBJ <binfile> TO <absfile>
HEXOBJ <hexfile> TO <absfile>[ START(addr)]
OBJHEX <absfile> TO <hexfile>
EDIT Tico like commands
B$$ = begin of text
Z$$ = end of text
[n]L$$ = n lines
[n]C$$ = n characters
Ftext$$ = find "text"
Itext$$ = insert "text"
Soldtext$[newtext]$$ = find "oldtext" and replace with "newtext
[n]D$$ = delete n characters
[n]K$$ = delete n lines
[n]T$$ = Type n lines 0TT$$ entire line with cursor in line
E$$ = Exit
Q$$ = quit
[n]W$$ = write n lines
A$$ = Append
M$$ = decimal space available
n<commandstring>$$ = Does commandstring n times
Hope this helps future ISIS-II users.
Dwight
> Patrick Finnegan <pat(a)purdueriots.com>
Pat,
I tried to boot my Model I to see if I could make you
a good boot disk using SuperUtility.
It seems my Model I is no more.
My friend who I had traded it to (and then gave it
back) has modified it quite a bit, and it became
delicate.
It no longer works at all..
I can use the cassette unit fine, but the E/I is bad,
and the LNW E/I I have doesn't seem to work with the
unit either.
I suspect the keyboard unit more than 2 E/I's are bad.
I'm trying to find a Model III or IV locally. If I
can, I'll get in touch with you about getting you a
boot disk.
I might be able to make you one with my Coco and using
a Disk Copy Utility on the Coco...
I haven't tried yet, and would have no way to test
it..
Regards,
Al Hartman
