> In all that is the collective geek-dome of classic computers, I find it
> boggling to see that no one has (or wishes to share... you greedy SOB ;-)
> the technical manual and/or jumper settings for the elusive DEC KZQSA Qbus
> to SCSI adapter boards.... come on, I challenge the collective knowledge
> base of the DEC geeks to come up with this mysterious and treasured
> knowledge and share it with the list. The winner gets a free 6 pak of
> JOLT soda for those looooonnnnngggggggg caffeine induced late nights ;-)
Courtesy of Google (first entry I found):
There are three sets of jumpers on the KZQSA:
1) W1 to W7 select the CSR address; the interrupt vector is programmable,
so there are no jumpers to set it. Since it sounds like your setup is
fairly simple, I'll guess that your CSR is at or near the default
address and list a few corresponding jumper settings ... if the CSR that
CONFIGURE gives you is not below, you might want to post it, so that one
us can verify the correct jumper settings, just to be on the safe side.
CSR W7 W6 W5 W4 W3 W2 W1
------ -- -- -- -- -- -- --
761300 0 0 0 1 0 1 1 (default)
761400 0 0 0 1 1 0 0
761500 0 0 0 1 1 0 1
But generally, you can work out the jumper settings as follows: if W7 is
0 (not set), the CSR is 76xy00, but it it is set (1), the CSR is 77xy00;
the octal digit "x" is determined by the settings of W6 to W4, and the
digit "y" is determined by W3 to W1 as illustrated by a few examples:
760100 0 0 0 0 0 0 1
760400 0 0 0 0 1 0 0
761000 0 0 0 1 0 0 0
764000 0 1 0 0 0 0 0
770000 1 0 0 0 0 0 0
2) W9 to W13 determine the memory base address; the default is the
address range 01000000-01377777 for the 128 KB memory on the KZQSA,
for which only W10 is set and the others are not. You need to
arrange for all modules that use Qbus memory space to have unique
address ranges ... but this is normally not such a problem, since
not so many modules use Qbus memory space. To see if it is a problem
in your configuration, issue a SHOW QBUS command from the console
prompt (>>>); at the end of the output (after the scan of IO space),
you will find the Scan of Qbus Memory Space, which shows which
address ranges are in use. If 01000000-01377777 does not overlap
any range currently in use (if any), you have no problem and can
just use the default jumper setting here.
Otherwise, the address selection jumpers just increase the base
address of the KZQSA's 128 KB memory in steps of 128 KB; i.e.,
address range W13 W12 W11 W10 W9
----------------- --- --- --- --- ---
00000000-00377777 0 0 0 0 0
00400000-00777777 0 0 0 0 1
01000000-01377777 0 0 0 1 0 (default)
01400000-01777777 0 0 0 1 1
...
17400000-17777777 1 1 1 1 1
Also note that W8 is in the same jumper block as W9-W13; I have no
idea what it does, probably best to leave it alone...
3) W14 to W16 set the SCSI ID of the KZQSA; W14 sets the MSB (4)
and W16 the LSB (1). The default is 7, which should be OK for most
purposes.
--
Eric Dittman
dittman(a)dittman.net
Check out the DEC Enthusiasts Club at http://www.dittman.net/
Does anyone want some 486 motherboards? I'm not sure who makes them (made
in Tiawan, SiS chipset).
They have the CPU (486 DX/2 50Mhz); 6 ISA slots, 2- 72pin SIMM slots and
8- 30 pin slots, AMI bios, AT keyboard, SiS chipset. And I'll throw in
the VGA card and I/O cards that are currently installed with them (I/O
card has FDD, IDE, LPT, 2- Com). Both are ISA cards, but have a 2nd
connector that looks a bit like AGP and hangs off the back end of the ISA
slots (3 of the 6 slots have this addition connector, so these two cards
fit into 2 of those).
CMOS batteries are soldered on, and corroded, but were working and
holding power as of not too long ago (these machines were last used a
month or so ago).
If anyone wants them (there are 4), let me know before I pull all the
jumpers off and toss the motherboards.
Or if anyone just wants 486 CPUs, let me know. I have the 4 listed above
with the boards, and another 3 or 4 pulled from other boards (not sure on
the specs for them, if there is interest, I'll check).
-chris
<http://www.mythtech.net>
could fit in there.
>
> Here is a picture of the (almost) final results...
>
Naturally, I forgot to post the link to the picture...
http://www.oz.net/~otter/geekworks/Crysta-00.JPG
-- Scarletdown
>I just a couple of days ago picked up a VAX 11/750. This machine has
>been stored in a damp shed for ten years or so, has had mice living in it,
Sounds like you are in for a bunch of fun !
If the mice chewed through the docs you can find a set of prints
and a few manuals at:
http://208.190.133.201/decimages/moremanuals.htm
I don't think the Installation and Acceptance manual covers
infestation in great depth though :-)
Antonio
Hi all,
OK, so here I am sitting at my computer with a stack of 100 or so disks
to reformat. Unfortunately most of said disks have been labelled using
felt-tip pen. And the labels are the nasty kind that don't come off without
a fight. Sooo... Has anyone got a method that will get these stupid things
off without leaving a gummy, sticky residue or damaging my disks? I've tried
WD40 (didn't work at all), 3-in-1 oil (don't ask), an upside down airblaster
(freeze spray for half the price) and a few other things and nothing works!
Anyone want to share their secret?
Thanks.
--
Phil.
philpem(a)dsl.pipex.com
http://www.philpem.dsl.pipex.com/
Ok, anyone know of a safe way of removing a glued on heatsink? I have a
few of these 486 CPUs where the heatsink is glued down. I could just jam
a screwdriver in and snap it off, but that just doesn't seem very good
for the chip.
-chris
<http://www.mythtech.net>
> Hmmmm, unobtainium huh??? Thats similar to Kryptonite I think ;-)
No.. Kryptonite is sugar compared to Un. If you ever find someone
you suspect of having, they'll fiercefully deny that... and then
smile...
--f
> I just a couple of days ago picked up a VAX 11/750. This machine has
Cool!
> been stored
> in a damp shed for ten years or so, has had mice living in it, and the
> usual assortment of spiders, etc.
Oh, SHUDDER! It sounds like you're in for an interesting restoration
process.
> to the control panel and TU58 tape drive. I'm in the process of cleaning
> all the components,
> but am in search of some advice on this process, especially the power
> supply. How long
> should I let the power supply dry out from its prior damp condition, and
> what should
> I do to bring it up for testing without risking damage to other
> components? I wish to
> do this methodically and carefully.
Unless this is a powersupply that needs a load on it when you power it on
(anyone know?), I'd recommend having it totally disconnected when you power
it on. I'd also recommend you have someone else standing by with a C02 Fire
Extinguisher for safety.
As for how long it needs to dry before powering up, I'm not really sure, if
you've got it in a warm, heated location, I'd say a week or two should be
plenty (probably doesn't need that much but it's better to ere on the side
of caution).
Something to do in the mean time is to look for corrosion and to get
everything good and clean. I'm most concerned about your powersupply and
backplane. Also take a look at the rollers in your TU58. While the
following is for a PDP-8, you might find it useful.
http://pdp-8.org/revive.htm Definitly read up on what Aaron has to say
about Backplanes.
Zane
> gil smith asked:
> I am curious what your favorite cp/m system might be.
My first 8bit CP/M machine was made by putting a Microsoft Softcard into my
Apple ][ Plus, early 1981.
After sitting there for a few years, the Softcard was moved to a new Apple
//f. That's an Apple //e, where I had the Rom software patched by my dealer,
to prevent the hard reset routine from overwriting a few bytes in every xx
KB's. And, of course, the startup text on the top line of the screen changed
to Apple //f to make it my "personal" machine.
The //f machine was upgraded with serial and parallel cards, a
clock/interrupt card, extra RAM, and finally a SASI interface card,
connected to a 10 MB Xebec harddisk. For that SASI harddisk, as sold by my
dealer, I wrote the boot prom, patches and drivers for Microsoft CP/M 2.2,
ALS CP/M Plus, Apple DOS, Apple Pascal and finally Prodos.
In the end, it was a system that could run not only two flavors of CP/M, but
also all other OS's that were available for the Apple - all with megabytes
of harddisk space. CP/M Plus was my favorite OS as it was the fastest one,
mainly due to the large numbers of disk buffers that were possible in CP/M Plus.
Sometimes I feel sorry that I sold all this for about fifty dollars...
Freek.
Hi,
> > curious. Mine's definitely a Diablo unit and plugs into its own
> > card within the
>
> Yes, a Diablo Hitype II.
ha ha - just me being stoopid :)
> > cardcage in the system unit. But there's also a seperate card
> > in there (oddly,
>
> How many wires in the cable between the printer and this card?
right, just taken another look...
yes, it is 50 pins - but not connected to anything; the printer connects via a
serial cable to a seperate SIO board (which seems capable of supporting 2
devices). A post-sale upgrade I assume, but they left the original Diablo board
in the machine too. The SIO board has DIP-switches on it whereas configuration
on the other cards seems to be solder-contact only.
do you remember if your unit shows anything on the display prior to putting the
system disc in? Be useful if it did in terms of tracing the fault with this
machine.
there's more cards in the cardcage than I originally remembered:
disc #4 drive (x 2)
disc #4 read/write
disc #4 control
64K ram
SIO interface
3 mode VDU output
3 mode VDU counter
VDU memory
CPU #9
Z80 RTC
keyboard interface
diablo interface
The 3 VDU boards are coupled on the outer edge as well as on the backplane.
Backplane connections are via 88 contacts, with the component-side of the cards
being purely ground. Not sure if the layout was to any recognised design;
probably proprietary though.
cheers,
Jules
88
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
>from News and Sport to Email and Music Charts
http://uk.my.yahoo.com