I think this sort of thing would be great!
-Linc Fessenden
In The Beginning there was nothing, which exploded - Yeah right...
Calculating in binary code is as easy as 01,10,11.
we are looking to buy 30-50 pcs 3m dc-100a magnetic tape cartridge.
please advise if you can recomaned us from where to buy.
best rgds
a. abraham
ab-ad tech&eng ltd israel
tel: 972-9-7660932
fax: 972-9-7660933
e-mail: abrahama(a)netvision.net.il
Well, I'm not sure that the S-100 "standard" was all that rigidly adhered to either, not to mention that everything else was proprietary at that time (not to mention IBM's infamous Slot 8, PS/1's and MCA, non-standard memory modules, etc.)...
New PSU fans are still abundantly available up here in Toronto; if ya really need one, or a complete PSU (especially an odd-sized one) or anything else for an old PC, drop me a line.
mike
-----------------Original Message---------------
Date: Sat, 27 Oct 2001 17:19:50 -0600
From: "Richard Erlacher" <edick(a)idcomm.com>
Subject: Re: VLB SCSI?
<snip>
because IBM no longer provided a firm ISA-equipped standard that everyone else could
clone, there was nothing but chaos, and that's the way it's been ever since.
The whole concept of "standard" was corrupted in the course of this evolutionary
step, and it was a step into the quagmire we're all swimming in today. <snip>
<snip>
BTW, if that "bulky old PSU" still works, I'd happily relieve you of the fan and
PSU board, and pay you for the freight, except for where you're located. I find
them harder and harder to get,
<snip>
---- On Sat, 27 Oct 2001, Chris (mythtech(a)Mac.com) wrote:
> >Does anyone know anything about an ATEX system?
>
> Ok... ignore me. I over zealously posted this question to the list
> because you people are just so damn smart.
>
> If I had bothered to even LOOK for myself, I would have found ATEX.com,
>
> which even has a press release mentioning how The Record (the paper my
> friend works at) has been a user of theirs for over 25 years.
>
> So I think I found at least a strong pointer in the right direction.
> (Although, if anyone has a list of commands an ATEX system accepts, that
>
> would also be helpful... however, it seems they have a number of
> different systems available)
>
> Sorry for wasting the bandwidth.
>
> -chris
>
> <http://www.mythtech.net>
>
>
>
>
This wouldn't happen to have been the Bergen Record...
Used to work for one of their papers as a reporter back before I got into
PDP11's at DEC.
--
Bill Pechter
Systems Administrator
uReach Technologies
732-335-5432 (Work)
877-661-2126 (Fax)
Hi,
has anyone of you ever disassembled an HSC cabinet? I am looking
pretty stupid right now. It's not the first piece of DEC iron
equipment that I have moved in pieces, I did two VAX6000 and one
TU81+. But this one is different. While being half-height like the
TU81, it's quite a bit deeper. The side-walls appear to be just
locked at the bottom and then hooked such that one can lift it
up and off, like the TU81's side walls. However, they do not move
no matter how hard I try. I don't find any screws holding them,
though. And with the sidewalls on, I cannot remove the top-cover
either.
So, I was hoping I could at least take it into two pieces by
moving the whole core out in one piece. Apparently that central
unit is just screwed on the front, like a rack-mount device.
Indeed I can move it out quite far. But then it stops at a
protruding piece of the backplane circuit board! There seems
to be no way to move that core all the way out other than by
removing the backplane circuite board. And I'm not going to do
that.
Other DEC equipment was quite straight forward to disassemble,
but this one beats the auto-assembies in difficulty level.
I appreciate every advice. My suspicion is that the sidewalls
are indeed removable, but mine are just stuck. Someone seen
it?
regards
-Gunther
--
Gunther Schadow, M.D., Ph.D. gschadow(a)regenstrief.org
Medical Information Scientist Regenstrief Institute for Health Care
Adjunct Assistant Professor Indiana University School of Medicine
tel:1(317)630-7960 http://aurora.regenstrief.org
In a message dated 10/28/01 10:50:27 PM Eastern Standard Time,
vze2wsvr(a)verizon.net writes:
<< One day your collectionwill be sold off, as you can't take it with you.
Don't
you want to get the most from your collection/investment?
Eric >>
I would think that most of us collect for reasons OTHER than specifically for
monetary value...
Collecting anything almost always is a piss-poor investment. There are better
ways to invest money.
--
DB Young Team OS/2
old computers, hot rod pinto and more at:
www.nothingtodo.org
> Gunther Schadow wrote:
>
> it still doesn't work. I booted again VMS from TK (takes hours)
Why not load up VMS at least for now - it should
boot somewhat more quickly! (Althoug, quite
worryingly, so should a TK50-based standalone backup!)
>trying various combinations of hardware and no success. I have
>given the RA90 a device address of 1. I have tried it on both
>the KDB50 and the KDM70 without success. Now I am wondering
>whether the SDI cable crossover issue is the problem? But
>why can Geoff run his RA90 in the basement of his 6000?
>
>The specifications clearly say that you can do this:
>
>KDB50---->VAXbulkhead---->SA800bulkhead---->RA90
>
>and Geoff does this
>
>KDB50---->VAXbulkhead---->RA90.
Does he? I recall him saying that he has
an RA9x in the bottom of his 6000 but I
do not recall him stating that he used
an even number of cables to do this.
>So, the swapping issue seems more complicated than just
>an uneven number of SDI cables! But I did exactly what
>Geoff did! Or did he do it differently? How? May be there
>are two sorts of SDI cables with or without cross-over?
AFAIK, *all* SDI cables are the same. Even never
works, odd works if everything else is right.
> However, VMS never detects any actual drive. So how could I
> possibly test this link between KDB50 and drive. It could be
> any of this:
>
> - KDB50 SDI interface damaged but in a way that is not
> detected by the self-test
> - KDB50 backplane cabling not screwed on tightly enough
> - SDI cabling broken
> - SDI cabling mismatched (crossover issue)
> - RA90 SDI interface damaged but in a way that is not
> detected by the self-test
>
>Is there any resident test that will check the drive/host
>interaction without requiring me to wait for another VMS
>boot cycle. Each attempt at rewiring and rebooting costs me
>about one hour for the VMS to boot from TK again so I need
>to keep this minimal.
OK. If standalone backup does not see the
drive before you get to the $ prompt then something
is clearly wrong (it should report a set of available
drives, one of which should be DUAn: where n is
the unit number).
Check the drive first. Press the TEST switch - the
TEST light should come on. Press the FAULT switch
and *all* lights should come on. Now you know the
lights work - press the TEST switch to leave test mode.
You can run a set of drive tests as follows:
- Power up: you'll setle with a display of R AB
- Deselect A & B
- press TEST
- press Write Protect
Now the display is T 00 with the
rightmost 0 flashing
- Use A & B to select a test number
- Start the test by pressing Write Protect
The display changes to S NN
Once the test has finished the display changes
to C NN
- Stop the test by pressing A or B
- Press TEST to leave test mode.
One suggested set of diags is:
- Spin *down* the drive
- Select T 60
- Press Write Protect to start the test
- The display does something like:
S 60
LOT
C 60
T 00
- T 60 has not done anything - it will simply
loop the next test.
- Select T 00
- Press Write Protect
This will run a set of diags repeatedly.
Leave to simmer for 5 minutes.
Repeat the above with the drive spun up.
(It performs a different set of diags).
If all that uncovers no fault, there is a
good chance that your drive is OK.
You have tried a KDB50 and a KDM70 -
assuming those are installed according to the
manual, and the processor can see them,
then that leaves just the cabling. If you
have a KDM70, I would try to use that rather
than the KDB50 since that way you do not
depend on a working VAXBI bus.
>Do we know the pinouts and signal patterns of the SDI (and
>BTW the KLESI) so that I oculd use my scope to detect if
>the wiring is O.K.? I didn't find pinouts and signals in
>the KDB50, RA9x user manual (or the KLESI user manual
>respectively).
I've never come across a broken SDI
cable, but it may be worthwhile doing
a simple continuity check - each should
be eight cables (four differential signals IIRC).
Antonio
An aside and definatly OTis a lot of that found its way into RTTY
and a lot of those old M15s and ASR33s printed it.
Allison
-----Original Message-----
From: Greg Ewing <greg(a)cosc.canterbury.ac.nz>
To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org>
Date: Sunday, October 28, 2001 8:43 PM
Subject: Re: [OT] New toy...
>John Lawson:
>
>> FB OM YR SIGS 599 RPT 599 QSL VIA BURO TNX ES 73 DE KB6SCO
>
>pete(a)dunnington.u-net.com (Pete Turnbull):
>
>> It's (mostly standard) radio ham CW (continuous wave) abbreviations,
used
>> to save keying too much morse.
>
>To those dismayed at the mangulations of language being
>used by some people in email these days, this just goes
>to show that there's nothing new under the sun. :-)
>
>Greg Ewing, Computer Science Dept,
+--------------------------------------+
>University of Canterbury, | A citizen of NewZealandCorp, a |
>Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. |
>greg(a)cosc.canterbury.ac.nz +--------------------------------------+
> TOPS the OS vs TOPS the network, are they related?
If you're wanting to know about TOPS-10 or TOPS-20 then I recommend my
PDP-10 emulation web page as a starting point:
http://www.aracnet.com/~healyzh/pdp10emu.html
If you're wanting to know about the network, isn't that some sort of ancient
Macintosh thing?
Zane