17 Aug
2016
17 Aug
'16
8:37 p.m.
I've brought up a MicroVax II and installed VMS 5.5-2 on a SCSI2SD disk
and it is fun to work with. (I also installed openvms 7.2 without much
drama)
The problem I am having is that is has a TK50 tape drive and controller,
but it never has shown up in the device list. I even swapped in a
different controller.
The DHV11 did show up initially but has now disappeared from the device
list. Did I do this by removing boards and putting them back in?
A RQDX2 board was put back in at a secondary CSR address and that shows
up (it is connected to an RX50 which shows up in the device list).
Does Autogen recognize new hardware?
Doug
18 Aug
18 Aug
6:29 a.m.
On Aug 17, 2016, at 11:37 PM, Douglas Taylor
<dj.taylor4 at comcast.net> wrote:
I've brought up a MicroVax II and installed VMS 5.5-2 on a SCSI2SD disk and it is fun
to work with. (I also installed openvms 7.2 without much drama)
The problem I am having is that is has a TK50 tape drive and controller, but it never has
shown up in the device list. I even swapped in a different controller.
The DHV11 did show up initially but has now disappeared from the device list. Did I do
this by removing boards and putting them back in?
A RQDX2 board was put back in at a secondary CSR address and that shows up (it is
connected to an RX50 which shows up in the device list).
Does Autogen recognize new hardware?
A lot of Unibus/Qbus devices have "floating CSRs" which means they don't
have fixed address assignments. Instead, the correct address is based on a set of rules,
which puts devices in an ordered list and assigns addresses in sequence. There are tools
to help with that. If you get the address wrong, the system will see the device as the
wrong type, and either fail to talk to it, or not talk to it at all (if it's not
something the OS supports).
paul
2:12 p.m.
On 18/08/2016 04:37, "Douglas Taylor" <dj.taylor4 at comcast.net> wrote:
I've brought up a MicroVax II and installed VMS
5.5-2 on a SCSI2SD disk
and it is fun to work with. (I also installed openvms 7.2 without much
drama)
The problem I am having is that is has a TK50 tape drive and controller,
but it never has shown up in the device list. I even swapped in a
different controller.
What type of cab? BA23 or BA123 'world box'? In the BA123 the left 4 slots
from the left are CD interconnect, in a BA23 just the
left 2. CD
interconnect means you can put a half-height card in the 'top' of
slots 1-4
(or 1-2) and not need anything in the bottom. Which slot are you putting the
TQK50 in?
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
19 Aug
19 Aug
8:58 a.m.
On 8/18/2016 5:12 PM, Adrian Graham wrote:
On 18/08/2016 04:37, "Douglas Taylor"
<dj.taylor4 at comcast.net> wrote:
It is the World Box, BA123 and I have hardware manuals that came with
the MVII.
When I got it this was the configuration:
Slot 1 - CPU
Slot 2 - Memory
Slot 3 - Bus Grant Card M9047
Slot 4 - DHV11
Slot 5 - TQK50 (upper) M9047 (lower)
Slot 6 - RQDX2
The new configuration is:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - DHV11
Slot 5 - TQK50 (upper) VIKING (lower)
Slot 6 - RQDX2
I even tried moving the cards:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - Bus Grant M9047
Slot 5 - DHV11
Slot 6 - TQK50 (upper) VIKING (lower)
Slot 7 - RQDX2
In the last two configurations VMS sees the disk/floppy controller just
fine but not the tape or serial ports.
Today I will pull the DHV11 and put it in the MV4000 and see if it shows
up just to check if the board is OK.
If there is none, or a faulty, TK50 drive attached the controller does
VMS react to this?
Doug
I've brought up a MicroVax II and installed
VMS 5.5-2 on a SCSI2SD disk
and it is fun to work with. (I also installed openvms 7.2 without much
drama)
The problem I am having is that is has a TK50 tape drive and controller,
but it never has shown up in the device list. I even swapped in a
different controller.
What type of cab? BA23 or BA123 'world box'? In the
BA123 the left 4 slots
from the left are CD interconnect, in a BA23 just the left 2. CD
interconnect means you can put a half-height card in the 'top' of slots 1-4
(or 1-2) and not need anything in the bottom. Which slot are you putting the
TQK50 in?
9:19 a.m.
On Aug 19, 2016, at 11:58 AM, Douglas Taylor
<dj.taylor4 at comcast.net> wrote:
So you added a "Viking", if I see right. What sort of device is that?
If it's an MSCP controller, it would go into the UDA50 floating CSR position. DHV11
and TMSCP rank later than UDA50 in the floating CSR order, so if you added a MSCP
controller without adjusting the CSR address switches of those two cards, they would not
be correctly recognized as I discussed in my earlier mail today. The order of the cards
in the chassis does not affect that; device identification in Unibus and Qbus has no
connection to physical card position.
paul
...
It is the World Box, BA123 and I have
hardware manuals that came with the MVII.
When I got it this was the configuration:
Slot 1 - CPU
Slot 2 - Memory
Slot 3 - Bus Grant Card M9047
Slot 4 - DHV11
Slot 5 - TQK50 (upper) M9047 (lower)
Slot 6 - RQDX2
The new configuration is:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - DHV11
Slot 5 - TQK50 (upper) VIKING (lower)
Slot 6 - RQDX2
I even tried moving the cards:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - Bus Grant M9047
Slot 5 - DHV11
Slot 6 - TQK50 (upper) VIKING (lower)
Slot 7 - RQDX2
In the last two configurations VMS sees the disk/floppy controller just fine but not the
tape or serial ports.
Today I will pull the DHV11 and put it in the MV4000 and see if it shows up just to check
if the board is OK.
If there is none, or a faulty, TK50 drive attached the controller does VMS react to this?
11:55 a.m.
On 8/19/2016 12:19 PM, Paul Koning wrote:
Yes, it is an MSCP disk controller, and it seems to work OK. I boot
On Aug 19,
2016, at 11:58 AM, Douglas Taylor <dj.taylor4 at comcast.net> wrote:
So you added a "Viking", if I see right. What sort of device is that?
If it's an MSCP controller, it would go into the UDA50 floating CSR position. DHV11
and TMSCP rank later than UDA50 in the floating CSR order, so if you added a MSCP
controller without adjusting the CSR address switches of those two cards, they would not
be correctly recognized as I discussed in my earlier mail today. The order of the cards
in the chassis does not affect that; device identification in Unibus and Qbus has no
connection to physical card position.
paul
...
It is the World Box, BA123 and I have
hardware manuals that came with the MVII.
When I got it this was the configuration:
Slot 1 - CPU
Slot 2 - Memory
Slot 3 - Bus Grant Card M9047
Slot 4 - DHV11
Slot 5 - TQK50 (upper) M9047 (lower)
Slot 6 - RQDX2
The new configuration is:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - DHV11
Slot 5 - TQK50 (upper) VIKING (lower)
Slot 6 - RQDX2
I even tried moving the cards:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - Bus Grant M9047
Slot 5 - DHV11
Slot 6 - TQK50 (upper) VIKING (lower)
Slot 7 - RQDX2
In the last two configurations VMS sees the disk/floppy controller just fine but not the
tape or serial ports.
Today I will pull the DHV11 and put it in the MV4000 and see if it shows up just to check
if the board is OK.
If there is none, or a faulty, TK50 drive attached the controller does VMS react to this?
from it and the CSR is at the standard 1st address, it
is connected to a
SCSI2SD board.
I think you have a good point about CSR addresses. There is a CONFIGURE
tool that tells you what set the addresses to for a particular
collection of options, I need to run that and then check that all the
devices are set to the proper addresses.
I suspect that I don't see MUA0 show up because the tape drive is not
working properly.
Doug
noon
On Aug 19, 2016, at 2:55 PM, Douglas Taylor
<dj.taylor4 at comcast.net> wrote:
On 8/19/2016 12:19 PM, Paul Koning wrote:
Yes, it is an MSCP disk controller, and it seems to work OK. I boot from it and
the CSR is at the standard 1st address, it is connected to a SCSI2SD board.
I think you have a good point about CSR addresses. There is a CONFIGURE tool that tells
you what set the addresses to for a particular collection of options, I need to run that
and then check that all the devices are set to the proper addresses.
I suspect that I don't see MUA0 show up because the tape drive is not working
properly.
To make matters confusing, there's an aspect of floating CSRs I did not mention
before. Some devices -- MSCP disk is one, TMSCP tape also I think -- have floating CSRS
for the second and subsequent units, but the first is fixed. Others, like the DHV11, are
all floating (including the first unit).
paul
On Aug
19, 2016, at 11:58 AM, Douglas Taylor <dj.taylor4 at comcast.net> wrote:
So you added a "Viking", if I see right. What sort of device is that?
If it's an MSCP controller, it would go into the UDA50 floating CSR position. DHV11
and TMSCP rank later than UDA50 in the floating CSR order, so if you added a MSCP
controller without adjusting the CSR address switches of those two cards, they would not
be correctly recognized as I discussed in my earlier mail today. The order of the cards
in the chassis does not affect that; device identification in Unibus and Qbus has no
connection to physical card position.
paul
...
It is the World Box, BA123 and I have
hardware manuals that came with the MVII.
When I got it this was the configuration:
Slot 1 - CPU
Slot 2 - Memory
Slot 3 - Bus Grant Card M9047
Slot 4 - DHV11
Slot 5 - TQK50 (upper) M9047 (lower)
Slot 6 - RQDX2
The new configuration is:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - DHV11
Slot 5 - TQK50 (upper) VIKING (lower)
Slot 6 - RQDX2
I even tried moving the cards:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - Bus Grant M9047
Slot 5 - DHV11
Slot 6 - TQK50 (upper) VIKING (lower)
Slot 7 - RQDX2
In the last two configurations VMS sees the disk/floppy controller just fine but not the
tape or serial ports.
Today I will pull the DHV11 and put it in the MV4000 and see if it shows up just to check
if the board is OK.
If there is none, or a faulty, TK50 drive attached the controller does VMS react to this?
1:55 p.m.
Yes, it is an
MSCP disk controller, and it seems to work OK. I boot from it and the CSR is at the
standard 1st address, it is connected to a SCSI2SD board.
I think you have a good point about CSR addresses. There is a CONFIGURE tool that tells
you what set the addresses to for a particular collection of options, I need to run that
and then check that all the devices are set to the proper addresses.
I suspect that I don't see MUA0 show up because the tape drive is not working
properly.
To make matters confusing, there's an aspect of floating CSRs I did
not mention before. Some devices -- MSCP disk is one, TMSCP tape also I think -- have
floating CSRS for the second and subsequent units, but the first is fixed. Others, like
the DHV11, are all floating (including the first unit).
paul
9:13 p.m.
On 8/19/2016 4:55 PM, Douglas Taylor wrote:
These comments have been very helpful, it has be over 10 years since I
did these things with VAXes. It is starting to come back, little by
little. Re-visiting the VAX is turning out to be fun, it is somewhat
like a treasure hunt.
When I run CONFIGURE I will post what the CSR's should be and what I
had them set to.
Doug
Here are the results:
Before - the CSR, VEC were set as follows
VIKING MSCP Disk controller : CSR 772150 VEC 154
RQDX2 MSCP Disk controller : CSR 760334 VEC 300
DHV11 Serial Mux : CSR 760460 VEC 300
TQK50 TMSCP controller : CSR 774500 VEC 260
After -
$ run sys$system:sysgen
SYSGEN> CONFIG
DEVICE> uda,2
DEVICE> tu81
DEVICE> dhv11
DEVICE>^Z
Device: UDA Name: PUA CSR: 772150 Vector: 154 Support: yes
Device: TU81 Name: PTA CSR: 774500 Vector: 260
Support: yes
Device: UDA Name: PUB CSR: 760334* Vector: 300* Support: yes
Device: DHV11 Name: TXA CSR: 760500* Vector: 310*
Support: yes
SYSGEN> EXIT
After changing the CSR and VEC of the DHV11 and rebooting :
$ show edev
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DUA0: Online 0
DUA1: Mounted 0 VAXVMSV055 1954644 126 1
DUB0: Online 0
DUB1: Online 0
Device Device Error
Name Status Count
FTA0: Offline 0
OPA0: Online 0
TXA0: Online 0
TXA1: Online 0
TXA2: Online 0
TXA3: Online 0
TXA4: Online 0
TXA5: Online 0
TXA6: Online 0
TXA7: Online 0
Device Device Error
Name Status Count
PTA0: Online 1
PUA0: Online 1
PUB0: Online 1
WSA0: Offline 0
$
The TK50 still does not show up, I think it is because the tape drive is
not functioning (can't move the lever to allow a tape to be loaded).
However, I do have functional RX50 floppys, just need some media. I
have a couple spare TK50's and will try those to see what happens.
Doug
Yes, it
is an MSCP disk controller, and it seems to work OK. I boot
from it and the CSR is at the standard 1st address, it is connected
to a SCSI2SD board.
I think you have a good point about CSR addresses. There is a
CONFIGURE tool that tells you what set the addresses to for a
particular collection of options, I need to run that and then check
that all the devices are set to the proper addresses.
I suspect that I don't see MUA0 show up because the tape drive is
not working properly.
To make matters confusing, there's an aspect of floating
CSRs I did
not mention before. Some devices -- MSCP disk is one, TMSCP tape
also I think -- have floating CSRS for the second and subsequent
units, but the first is fixed. Others, like the DHV11, are all
floating (including the first unit).
paul
3:49 p.m.
On Fri, Aug 19, 2016 at 8:58 AM, Douglas Taylor <dj.taylor4 at comcast.net> wrote:
It is the World Box, BA123 and I have hardware manuals that came with the
MVII.
When I got it this was the configuration:
Slot 1 - CPU
Slot 2 - Memory
Slot 3 - Bus Grant Card M9047
Slot 4 - DHV11
Slot 5 - TQK50 (upper) M9047 (lower)
Slot 6 - RQDX2
The new configuration is:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - DHV11
Slot 5 - TQK50 (upper) VIKING (lower)
Slot 6 - RQDX2
I even tried moving the cards:
Slot 1 - CPU
Slot 2 - Memory (Clearpoint)
Slot 3 - Memory (DEC)
Slot 4 - Bus Grant M9047
Slot 5 - DHV11
Slot 6 - TQK50 (upper) VIKING (lower)
Slot 7 - RQDX2
In the last two configurations VMS sees the disk/floppy controller just fine
but not the tape or serial ports.
Today I will pull the DHV11 and put it in the MV4000 and see if it shows up
just to check if the board is OK.
If there is none, or a faulty, TK50 drive attached the controller does VMS
react to this?
Doug
Here is one example of how the expected floating CSR address and
vector for a DHV11 will shift depending on whether a system contains 2
MSCP controllers instead of 1:
C:\simh-4.0-Beta--2015-10-16-5c117caa>MicroVAX3900.exe
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 5c117caa
sim> boot cpu
Loading boot code from internal ka655x.bin
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>configure
Enter device configuration,
HELP, or EXIT
Device,Number? help
Devices:
LPV11 KXJ11 DLV11J DZQ11 DZV11 DFA01
RLV12 TSV05 RXV21 DRV11W DRV11B DPV11
DMV11 DELQA DEQNA DESQA RQDX3 KDA50
RRD50 RQC25 KFQSA-DISK TQK50 TQK70 TU81E
RV20 KFQSA-TAPE KMV11 IEQ11 DHQ11 DHV11
CXA16 CXB16 CXY08 VCB01 QVSS LNV11
LNV21 QPSS DSV11 ADV11C AAV11C AXV11C
KWV11C ADV11D AAV11D VCB02 QDSS DRV11J
DRQ3B VSV21 IBQ01 IDV11A IDV11B IDV11C
IDV11D IAV11A IAV11B MIRA ADQ32 DTC04
DESNA IGQ11
Numbers:
1 to 255, default is 1
Device,Number? dhv11,1
Device,Number? tqk50,1
Device,Number? rqdx3,1
Device,Number? exit
Address/Vector Assignments
-772150/154 RQDX3
-774500/260 TQK50
-760440/300 DHV11
>>configure
Enter device configuration,
HELP, or EXIT
Device,Number? dhv11,1
Device,Number? tqk50,1
Device,Number? rqdx3,2
Device,Number? exit
Address/Vector Assignments
-772150/154 RQDX3
-760334/300 RQDX3
-774500/260 TQK50
-760500/310 DHV11
20 Aug
20 Aug
8:27 a.m.
On 8/19/2016 6:49 PM, Glen Slick wrote:
Device,Number? dhv11,1
Device,Number? tqk50,1
Device,Number? rqdx3,1
Device,Number? exit
Address/Vector Assignments
-772150/154 RQDX3
-774500/260 TQK50
-760440/300 DHV11
When I started this I hadn't put the RQDX2 back in, so I had only one
UDA controller and that's how I saw the DHV11 show up. When I put the
RQDX2 back in that's when I lost the DHV11.
I did the configure from VMS 5.5, it was a lot less verbose than what
you showed.
At this point I am wondering why I am fussing over such useless
interchange medium as the RX50 diskettes and the TK50 tape cassettes.
Of course to the hobbyist the answer is "Because they are there!" and
you better get them working. I would be better off with a DELQA, BTW
will the cabinet kit from a DEQNA work with the DELQA?
Doug
>> configure
Enter device
configuration, HELP, or EXIT
Device,Number? dhv11,1
Device,Number? tqk50,1
Device,Number? rqdx3,2
Device,Number? exit
Address/Vector Assignments
-772150/154 RQDX3
-760334/300 RQDX3
-774500/260 TQK50
-760500/310 DHV11 
7:35 p.m.
On Aug 20, 2016, at 10:27 AM, Douglas Taylor
<dj.taylor4 at comcast.net> wrote:
When I started this I hadn't put the RQDX2 back in, so I had only one UDA controller
and that's how I saw the DHV11 show up. When I put the RQDX2 back in that's when
I lost the DHV11.
I did the configure from VMS 5.5, it was a lot less verbose than what you showed.
At this point I am wondering why I am fussing over such useless interchange medium as the
RX50 diskettes and the TK50 tape cassettes. Of course to the hobbyist the answer is
"Because they are there!" and you better get them working. I would be better
off with a DELQA, BTW will the cabinet kit from a DEQNA work with the DELQA?
Yes, I?ve used a cabinet kit from a DEQNA on a DELQA using 11/73?s.
In the Microsystem Options http://vaxhaven.com/images/1/16/EK-192AA-MG-001.pdf
<http://vaxhaven.com/images/1/16/EK-192AA-MG-001.pdf> it appears the cable set is
the same for both.
Jerry
21 Aug
21 Aug
8 a.m.
On 8/20/2016 10:35 PM, Jerry Weiss wrote:
I found a cabinet kit that appears to be for the BA123 and on the plate
with the AUI connector it is labeled 'DEQNA'. I became suspicious that
DEC would sell the same hardware, but with the label 'DELQA', and charge
you more, of course. I think that I got this one because when a DEQNA
was upgraded to a DELQA that cabinet kit was 'upgraded' also. Ha.
Doug
On Aug 20,
2016, at 10:27 AM, Douglas Taylor <dj.taylor4 at comcast.net> wrote:
When I started this I hadn't put the RQDX2 back in, so I had only one UDA controller
and that's how I saw the DHV11 show up. When I put the RQDX2 back in that's when
I lost the DHV11.
I did the configure from VMS 5.5, it was a lot less verbose than what you showed.
At this point I am wondering why I am fussing over such useless interchange medium as the
RX50 diskettes and the TK50 tape cassettes. Of course to the hobbyist the answer is
"Because they are there!" and you better get them working. I would be better
off with a DELQA, BTW will the cabinet kit from a DEQNA work with the DELQA?
Yes, I?ve used a cabinet kit from a DEQNA on a DELQA using 11/73?s.
In the Microsystem Options http://vaxhaven.com/images/1/16/EK-192AA-MG-001.pdf
<http://vaxhaven.com/images/1/16/EK-192AA-MG-001.pdf> it appears the cable set is
the same for both.
Jerry
18 Aug
18 Aug
4:25 p.m.
On Aug 17, 2016, at 10:37 PM, Douglas Taylor <dj.taylor4 at comcast.net> wrote:
I've brought up a MicroVax II and installed VMS 5.5-2 on a SCSI2SD disk and it is fun
to work with. (I also installed openvms 7.2 without much drama)
The problem I am having is that is has a TK50 tape drive and controller, but it never has
shown up in the device list. I even swapped in a different controller.
The DHV11 did show up initially but has now disappeared from the device list. Did I do
this by removing boards and putting them back in?
A RQDX2 board was put back in at a secondary CSR address and that shows up (it is
connected to an RX50 which shows up in the device list).
Does Autogen recognize new hardware?
If you are not familiar with the BA23 or BA123 enclosures, make sure you aren?t plugging
the controllers in the PMI slots.
This would be 1-3 CD on the BA23 and 1-4 CD on the BA213. Things will be very unhappy if
you accidentally do this.
see http://decvax.50megs.com/doc/qbus/tutorial.html
<http://decvax.50megs.com/doc/qbus/tutorial.html>
Jerry
6:55 p.m.
On 08/17/2016 10:37 PM, Douglas Taylor wrote:
I've brought up a MicroVax II and installed VMS
5.5-2 on a
SCSI2SD disk and it is fun to work with. (I also
installed openvms 7.2 without much drama)
The problem I am having is that is has a TK50 tape drive
and controller, but it never has shown up in the device
list. I even swapped in a different controller.
The DHV11 did show up initially but has now disappeared
from the device list. Did I do this by removing boards
and putting them back in?
A RQDX2 board was put back in at a secondary CSR address
and that shows up (it is connected to an RX50 which shows
up in the device list).
Does Autogen recognize new hardware?
Yes, definitely. Some older devices have switches (or even
soldered jumpers) to set the CSR address. If some of these
are wrong, it could mess up the automatic address assignment
of later MSCP hardware.
Another possibility is dirty backplane/board contracts.
Also, some LSI-11/uVAX hardware may be in the age where they
are dying. Many later devices will not show up on the bus
if their internal microcontroller fails.
If the peripherals have socketed chips, you might try
reseating those chips.
Jon
19 Aug
19 Aug
1:56 a.m.
Does Autogen recognize new hardware?
Yes, definitely. Some older devices have switches (or even
soldered jumpers) to set the CSR address. If some of these
are wrong, it could mess up the automatic address assignment
of later MSCP hardware.
9:25 a.m.
On 19/08/2016 09:56, "Peter Coghlan" <cctalk at beyondthepale.ie> wrote:
Not exactly.
VMS automatically looks for and initialises I/O devices at startup
time. (There are exceptions to this but these do not come into
play in this particular situation.)
Autogen is another thing entirely. It is a tool which you run
manually to set system parameters. You don't have to run autogen
to pick up changes in your I/O setup. You just have to have your
device configured the way VMS expects them to be and VMS will find
them when you boot.
It won't if you do a minimum/conversational boot (STARTUP_P1 set to "MIN"),
devices won't be discovered unless the STARTUP CONFIGURE process runs. After
a minimum boot you need to MC SYSGEN AUTO ALL/LOG to pick up devices. Or
just do a full boot.
--
Adrian/Witchy
Binary Dinosaurs creator/curator
Www.binarydinosaurs.co.uk - the UK's biggest private home computer
collection?
Does Autogen recognize new hardware?
Yes, definitely. Some older devices have switches (or even
soldered jumpers) to set the CSR address. If some of these
are wrong, it could mess up the automatic address assignment
of later MSCP hardware.
3045
days inactive
3048
days old
16 comments
8 participants
participants (8)
-
cctalk＠beyondthepale.ie -
dj.taylor4＠comcast.net -
dj.taylor4＠verizon.net -
elson＠pico-systems.com -
glen.slick＠gmail.com -
jsw＠ieee.org -
paulkoning＠comcast.net -
witchy＠binarydinosaurs.co.uk