Hello everyone,
Looks like Canadian Government Surplus has a large pile of old radar items
including a DG Eclipse S/230 system and some version of a Nova. In the
picture you can see these items along with a number of large disks and a lot
of documentation.
Auction closes a couple of days from now and I'm in Canada but 3000 miles
away from it.
The pile is in Ucluelet BC.
Heres a link:
If you can't get right to the item, just use the search term "radar".
http://crownassets.pwgsc.gc.ca/mn-eng.cfm?snc=wfsav&sc=enc-bid&scn=69424&lcn
=213328&lct=L&srchtype=&so=ASC&sf=ferm-clos&lci=&str=1<nf=1&test=1
Hi,
I'm restoring an IBM 3340-A2 winchester disk drive that is part of our
new IBM 4331 system[1]; so far so good. It still needs some cleaning and
visual inspection; it was incredibly dirty (I've even found a mouse trap
inside on top of the air filter housing!) but looks fine otherwise. We
also have almost all manuals for the system, except one for the 3340: the
first of six volumes, i.e. volume R01 that contains the sections INDEX,
MLX, LGND, START, FSI, MSG, SENSE, OLT and OPER. All other manuals will be
scanned bit by bit and put on our FTP server.
Question: does anybody have that manual? I'd be interested in a scan; i
can then put it online if desired.
Christian
[1] The system consists of a 4331-2, four 3278 terminals including
console, a 3287 matrix printer, a 3262 steel band printer, a 8809 tape
drive, and a string of one 3340-A2 and one 3344-B2 drive. There were also
several 3370 drives that went to the nearby IBM museum.
>
>By necessity: any retelling of 80's era networking will have so much
>source information available from UUCP mapping projects and Usenet
>and mailing lists, than any other more closed sections of the network.
>(BITNET and later NSFNet are also up there in terms of preserved
>message/map volume but by no means as huge).
>
Where are the preserved BITNET maps to be found? I went looking for BITNET
topography related material a few months ago and found only a few examples.
One of the people I contacted recently came back to me with a stash of files
previously thought to be lost but I would be pleasantly surprised to know if
there is more material out there.
Regards,
Peter Coghlan.
>
>What OS is it supposed to be
>running (the starting host seems to be a sort of hybrid of TOPS-10,
>Unix and VM/CMS)?
>
What bit is like VM/CMS? - I've never come across anything else that
reminds me of VM/CMS to any degree :-)
Regards,
Peter Coghlan.
> BTW, anyone looking for a good sunday talk?
>
> Incredible I have no one from this list on MSN. If you're looking for
> some chatting, add webmaster at pinball-taito.com.br to your MSN and lets
> have a bit of talking :D
>
> Boring day...
>
> Greetings from Brazil
> Alexandre Souza, PU1BZZ
Maybe somebody should set up an irc channel on freenode if there isn't one
already...that sounds like a good idea to me!
>
> I will add some diagnostic wires to the board as you suggest, I don't
> remember a lot about TTL chips, is there a convention about which are the
> power pins?
>
> In the meantime someone else told me that the click I would hear when
> connecting to the mains (before switching it on with the key) was some
kind
> of relay. I don't hear that anymore, would that help to isolate the
problem
> at all?
OK, I am looking at the schemaitcs... I will take the referenes from this
manual on bitsavers, since I guess we all have access to it.
http://www.bitsavers.org/pdf/dec/pdp11/1124/MP01018_1124schem_Aug80.pdf
This is a complex PSU, and it is not obvious at first sight what is going
on,
but I will try... I will put page references (to that PDF) in brackets.
The relay is K1 (p70). It shorts out a soft-start resistor in series with
the
input to the mains bridge rectifier. This produces 350V across C1/C2 in
series.
Now much of the PSU circuitry runs off a little SMPSU. The chopper
transformer is T1 (p82). It provides about 12V across C3 (p82).
Now we need to look at the 'Bias and Interface Board'. The relay is driven
by
E4 (p86). It's essentially a 'mains OK' circuit, the relay is energised when
the votlage across the mains smoothing capacitors is high enough to trigger
E3a. E3a is on the mains side of the isolation barrier, of course. But the
relay driver (E4) is powered from a signal called '+5V'. This is not the +5V
that you're expecting. It comes from the 7805 regulator E1 (p87). The input
to that comes from that little SMPSU I've been talking about. This is
isolated
>from the mains.
The control circuitry for that is on page 88. Be warned that this circuitry
is
NOT isolated from the mains. It's a relatively conventional SMPSU with the
control circuitry powered straight from the mains. Q1 (p88) is the chopper
transistor.
So, if everything's working right, this SMPSU starts up when you apply
mains
to the machine, the 'mains OK' circuit triggers and the relay pulls in.
I would start by checking that '5V' supply, remember it's not the one to
the
backplane. Check it at the output of E1, for example. If it's missing, as I
think it will be, you need to sort out the SMPSU I've been talking about.
But
let's find out if you need to do that.
-tony
Regards
Rob
--------------------------------------------------------------------
mail2web.com ? What can On Demand Business Solutions do for you?
http://link.mail2web.com/Business/SharePoint
Hi guys,
I'm going to stick my neck out a bit, and assume you all saw the
screenshots I posted this week. If you didn't, well... you missed a treat :)
I've just committed the current "development alpha" of the DiscFerret
software to the DiscFerret Mercurial repository. You can access the
files at the following address:
http://hg.discferret.com/software/merlin/
Hit the "zip," "gz" or "bz2" link on the top toolbar and you can
download a ZIP, tar-gzip or tar-bzip2 file containing all the current
source files.
At the moment, I've only tested Merlin on Linux (specifically, Ubuntu
10.10 "Maverick Meerkat"), although *in theory* it should also build on
the various BSDs and Mac OS X, as long as you have a working copy of the
GCC C++ compiler, and the wxWidgets libraries for your system (note that
'wx-config' must be on the PATH).
At the moment, it'll only read "Catweasel IMG" files. These are
basically dumps of the Catweasel data buffer, sampled at 28MHz, in the
following format:
File := 1 or more "Track" blocks
Track :=
uchar cylinder // physical cylinder (track)
uchar head // physical head (side)
uint32le payload_length
uchar[] payload // length specified by payload_length
uchar = unsigned char, an 8 bit unsigned value
uint32le = unsigned integer, 32 bit, little endian.
Data is exactly as extracted from the Catweasel memory; 28MHz clock
rate, index in the MSbit, bits 6..0 contain the timing value.
Please feel free to post your comments on-list, or email me in private
if you prefer.
Thanks,
--
Phil.
philpem at philpem.me.uk
http://www.philpem.me.uk/
Hi guys,
I'm going to stick my neck out a bit, and assume you all saw the
screenshots I posted this week. If you didn't, well... you missed a treat :)
I've just committed the current "development alpha" of the DiscFerret
software to the DiscFerret Mercurial repository. You can access the
files at the following address:
http://hg.discferret.com/software/merlin/
Hit the "zip," "gz" or "bz2" link on the top toolbar and you can
download a ZIP, tar-gzip or tar-bzip2 file containing all the current
source files.
At the moment, I've only tested Merlin on Linux (specifically, Ubuntu
10.10 "Maverick Meerkat"), although *in theory* it should also build on
the various BSDs and Mac OS X, as long as you have a working copy of the
GCC C++ compiler, and the wxWidgets libraries for your system (note that
'wx-config' must be on the PATH).
At the moment, it'll only read "Catweasel IMG" files. These are
basically dumps of the Catweasel data buffer, sampled at 28MHz, in the
following format:
File := 1 or more "Track" blocks
Track :=
uchar cylinder // physical cylinder (track)
uchar head // physical head (side)
uint32le payload_length
uchar[] payload // length specified by payload_length
uchar = unsigned char, an 8 bit unsigned value
uint32le = unsigned integer, 32 bit, little endian.
Data is exactly as extracted from the Catweasel memory; 28MHz clock
rate, index in the MSbit, bits 6..0 contain the timing value.
Please feel free to post your comments on-list, or email me in private
if you prefer.
Thanks,
--
Phil.
philpem at philpem.me.uk
http://www.philpem.me.uk/
Thus spake dave.thearchivist at gmail.com on Sun May 1 19:19:04
> we are on #classiccmp om freenode....been there for years
>
> Dave Caroline (archivist)
Thanks Dave. Probably good to send that out once in awhile for us newbies
so we don't irritate Ian :D