Along with the additional UYK-20 computers I found some parts of some AN/UYK-44s. I know that they were used similar to the UYK-20s. Does anyone have any detailed info about them? FWIW they also use core memory. I found that they use the Quadri core memory blocks that I was asking about and posted the picture of about two months ago.
Picture at: <http://216.239.39.100/search?q=cache:kY3RwZ-3HjUC:www.lockheedmartin.com/se…>
One of the parts that I got was the operator/programmer's console. There's a close up picture of one at: <http://216.239.39.100/search?q=cache:GI46Okw7ah4C:www.newbegin.com/itemmis_…>
Joe
FYI:
AN/UYK-44(V) Computer
The AN/UYK-44 computer is the standard 16-bit computer installed in U.S. Navy surface, submarine, and ground C4I platforms. The UYK-44 provides computing power for more than 40 different command, control, communications, and weapon systems. Tactical Systems has been under contract to NAVSEASYSCOM since 1980 and has delivered more than 2,500 computers through September 2000, including UYK-44 open-system modules and enhanced processors.
> > review claimed the VR201 was compatable with the VT102.
>
> Considering the former is a composite mono monitor and the latter is a
> terminal, that's just impossible.
I seem to recall that many/most VT100's had composite video out - mine
do - and this was frequently used in the classroom to drive a larger
monitor, or distributed to several monitors/terminals throughout the
classroom. This way my Data Structures professor could show us *exactly*
what she was on about.
Perhaps there was an adapter to use the VR201 in this manner? I can
remember staring at the displays, but not what was rendering them. I
know she was working on a VT100, but can't "see" the slaved monitor in
memory...
--Steve.
From: "Lawrence Walker" <lgwalker(a)mts.net>
To: cctalk(a)classiccmp.org
Date sent: Sat, 2 Nov 2002 18:01:05 -0600
Subject: Re: DEC Rainbow
Send reply to: lgwalker(a)mts.net
Priority: normal
> > >
> > If it has a graphic card you can also use it with a VR241. The original
> > Byte
>
> Actually, you can use a VR241 without the graphics card. Just connect the
> green input to the mono video output of the 'Bow. You'll get perfectly good
> green text.
>
> OK, it's a waste of a colour monitor, but if it's all you have...
>
Good tip. It's certainly not in the Rainbow site archive and I might have been
able to get my 'bow up and running earlier with a VR241.
> > review claimed the VR201 was compatable with the VT102.
>
> Considering the former is a composite mono monitor and the latter is a
> terminal, that's just impossible.
>
I was quoting one of the 2 reviews Byte did on the "bow. They generally
slagged the Rainbow and were likely possible for part of it's lack of success.
The other part was the DEC executives who never really liked the venture and
saddled it with a bunch of prohibitives so as to not threaten their mini-market
including the PRO and DECMate.
> I think, though, that the 'Bow + VR201 will emulate a VT102.
>
> > Jeff Armstrong who wrote the Rainbow FAQ claimed there was a built-in
> > terminal that could be accessed at the start-up menu by typing T altho I
> > have never tried it. He also said a friend of his was using it for a
> > terminal on his VAX II.
>
> There is, and it works. It's a pretty good VT100/VT102 emulation.
>
> > Tony Duell posted the pin-outs for both mono and color a while back on the
> > list to make a monitor cable, which can be hard-to-find. The LK201's are
>
> Has this been archived anywhere? If not, should I post it again?
>
Well it should be in CC archives and of course I have it in mine. It would be
good to have it on the Swedish Archives however. Hopefully the maintainer who
answered Antonio Carlini's offer of the service manual, will also put it onto
the site as it was a very comprehensive pinout listing.
> As I've said several times before, if I put something on this list, then
> you're welcome to stick copies on appropriate web sites, etc. I've essentially
> made it public by posting it here. Note, I don't regard it as legally public
> domain (I would not be at all happy if somebody else claimed ownership, for
> example), but I am not going to object to it being shared.
>
> -tony
>
Lawrence
lgwalker(a)mts.net
bigwalk_ca(a)yahoo.com
------- End of forwarded message -------
lgwalker(a)mts.net
bigwalk_ca(a)yahoo.com
On Nov 3, 15:55, John Allain wrote:
> A while back I noticed that sometimes after setting an encoding and
> sending to the list that the encoding was lost to UTF-7 anyway. This
> was about the same time as the list software change so back them I
> assumed incorrectly that the new software was setting UTF-7 headers
> (Content-Type: text/plain; charset="utf-7") and loosing my ISO ones
> (...charset="iso-8859-1"). Now it seems that the way the setting was
> getting lost was by saving and recalling message drafts in MS OExpress.
> It is very possible that there are other ways MS will mess this up but
for
> now I think it's fixed.
Well, it seems to be, for this message at least. Thanks for persevering
with this, I almost added an <aol>metoo</aol> to Sellam's message :-)
> FYI here is my file entry on the subject.
> "List of Encoding Problems with Outlook Express:
> You can't shut off charset encoding.
> (Two choices: MIME and UUEncode.
> There is a "MIME: encode text using None"
> option which doesn't work, it still encodes.)
> You can't set an encoding 'for once and for all'.
> There is no clear indicator of the encoding in use
> (have to go down two menus to check/set each message).
> Selecting a useful encoding [Western European (ISO)]
> results in display using an undesirable proportional
> width font.
> Manually selected encodings are easily lost and overridden
> to UTF-7 (example: set ISO, save as Draft, recall, send,
> it will be UTF-7**)
> The appearance of an encoding is buggy; what appears when
> reviewing a saved message is sometimes decoded, sometimes
> not, with the same message.
> Can't check a message header on an unsent message."
> so Sellam aggravation is nothing compared to this <g>
I can imagine! But other people use OE without these problems. My mailbox
currently contains 47 messages created with OE, including some from at
least ten other listmembers, and only yours have the UTF-7 problem(s).
Some are version 4.72, some 5, some 5.50, some 6.00, etc. I even found
several with exactly the same version you have (5.00.2615.200), so it looks
like there's something else in your setup that's making OE prefer UTF-7. I
don't know much about Outlook or Express, but doesn't it have two or three
places for these settings? One for current, one for default, and maybe
something for per-recipient preferences (as in "this user prefers to
receive fancy text" or something similar)?
--
Pete Peter Turnbull
Network Manager
University of York
Bob,
If it's not too late, I would like to sign up for a PBC and CPU chip as
well.
regards
Doug Jackson
Director, Managed Security Services
Citadel Securix
+61 (0)2 6290 9011 (Ph)
+61 (0)2 6262 6152 (Fax)
+61 (0)414 986 878 (Mobile)
Web: <www.citadel.com.au>
Offices in Melbourne, Sydney, Canberra, Hong Kong, Boston
> -----Original Message-----
> From: bob(a)jfcl.com [mailto:bob@jfcl.com]
> Sent: Saturday, November 02, 2002 2:55 AM
> To: classiccmp(a)classiccmp.org
> Subject: Re: Build your own PDP-8!
>
>
>
> In about twenty four hours eleven people have signed up for
> 13 PC boards.
> This is far more than I ever expected, and I'm glad to see so
> many people
> interested in PDP-8s and the SBC6120. I plan to keep taking
> sign ups until
> Monday, or we get to 20, which ever is first.
>
> BTW, the number of people signed up for our cooperative so
> far is enough
> to guarantee a PCB price somewhere in the low $30 range.
>
> Thanks again,
> Bob Armstrong
>
> > If you're one of those people who wants a PDP-8 but can't
> find one, don't
> >despair - you can always build your own! The SBC6120 is a
> complete PDP-8
> >built around the venerable Harris HM6120 CPU and modern
> programmable logic
> >devices. All parts used except the 6120 are contemporary,
> easily available
> >devices.
> >
> > The entire system fits on a PC board 6.2" by 4.2" and has
> approximately the
> >same footprint as a 3.5" hard disk. The SBC6120 has an IDE
> disk interface,
> >an optional 2Mb non-volatile RAM disk (that's as big as an
> RK05!), and a true
> >KL8/E compatible console terminal interface. OS/8 device
> handlers are
> >available for the IDE and RAM disks, and the system will run standard
> >OS/8 V3D. There's even an expansion bus so you can design
> and build your
> >own daughter cards to plug into it.
> >
> > To find out more, visit the SBC6120 web page at
> >
> > http://www.SpareTimeGizmos.com/Hardware/SBC6120-2.htm
> >
> > I've recently had two requests to buy SBC6120 PC boards.
> These are four
> >layer boards with plated holes and are quite expensive in
> quantity one or two,
> >but the price falls per piece falls dramatically for
> quantities as small as
> >four or six. I'd like to find a few other people who would
> be interested in
> >building their own SBC6120 and going in together on a PCB
> order. The price
> >for a SBC6120 PC board would be something like:
> >
> > Two boards ==> $100 per board
> > Four " ==> $60 per board
> > Six " ==> $45 per board
> > Ten " ==> $36 per board
> >
> > I also have about four spare 6120 chips, which I'm willing
> to sell at my
> >cost of $50 each. Believe it or not, it is still possible
> to buy new old
> >stock 6120s, at $50 each, with a minimum order of ten (!!),
> but if enough
> >people want SBC6120s we could always go this route.
> >
> > If you're interested, please write to me at bob(a)jfcl.com.
> >
> >Bob Armstrong
>
CAUTION - The information in this message may be of a privileged or confidential nature intended only for the use of the addressee or someone authorised to receive the addressee's e-mail. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this email in error please notify postmaster(a)citadel.com.au. Any views expressed in this message are those of the individual
sender and may not necessarily reflect the views of Citadel Securix.
Feel free to visit the Citadel Securix website! Click below.
http://www.citadel.com.au
Actually, here's an even better list:
http://bbscorner.cjb.net/
----------
> From: Doc Shipley <doc(a)mdrconsult.com>
> To: classiccmp <cctalk(a)classiccmp.org>
> Subject: Re: BBSs & PPP
> Date: Sunday, November 03, 2002 12:43 PM
>
> Glen,
> Sorry, I was swamped when you posted the original query, and
> accidentally deleted it too.
> For a dialup shell account, there's Realtime in Austin, and I think
> they are regional if not national. www.bga.com
> There are also a bunch (8-12) active FidoNet nodes here. I remember
> having to beat Google pretty hard to find the listing, though.
> Good luck with active BBS dialups. If you find a current listing, I'd
> really like to see it. I get free long-distance on my cellphone; I
> might set up IrDA and do some 9600bps BBSing. Just for nostalgia's
> sake. :)
>
> Doc
>
Doc --
Looks like bga.com is local only :>(
I found a BBS list, and there actually are some dialups left. It's at
http://www.usbbs.org/
Later --
Glen
0/0
----------
> From: Doc Shipley <doc(a)mdrconsult.com>
> To: classiccmp <cctalk(a)classiccmp.org>
> Subject: Re: BBSs & PPP
> Date: Sunday, November 03, 2002 12:43 PM
>
> Glen,
> Sorry, I was swamped when you posted the original query, and
> accidentally deleted it too.
> For a dialup shell account, there's Realtime in Austin, and I think
> they are regional if not national. www.bga.com
> There are also a bunch (8-12) active FidoNet nodes here. I remember
> having to beat Google pretty hard to find the listing, though.
> Good luck with active BBS dialups. If you find a current listing, I'd
> really like to see it. I get free long-distance on my cellphone; I
> might set up IrDA and do some 9600bps BBSing. Just for nostalgia's
> sake. :)
>
> Doc
>
FWIW, I manually copied the 4 character UTF encodings
into that last message and MS decoded them back to
single characters "for me". C'est lavvie*!
John A.
*intentional (Spelling right, Tony?)
(It means "For You", yes. yes, that's what it means <g>)
For those wondering where my bad escape sequences came
from, or why, here is a partial explanation.
I used to get ISO encoded messages when I originated a message
to Classiccmp and UTF-7 encodings ($ = '$', = = '=',
_ = '_', etc.)** when I used "Reply".
A while back I noticed that sometimes after setting an encoding and
sending to the list that the encoding was lost to UTF-7 anyway. This
was about the same time as the list software change so back them I
assumed incorrectly that the new software was setting UTF-7 headers
(Content-Type: text/plain; charset="utf-7") and loosing my ISO ones
(...charset="iso-8859-1"). Now it seems that the way the setting was
getting lost was by saving and recalling message drafts in MS OExpress.
It is very possible that there are other ways MS will mess this up but for
now I think it's fixed.
FYI here is my file entry on the subject.
"List of Encoding Problems with Outlook Express:
You can't shut off charset encoding.
(Two choices: MIME and UUEncode.
There is a "MIME: encode text using None"
option which doesn't work, it still encodes.)
You can't set an encoding 'for once and for all'.
There is no clear indicator of the encoding in use
(have to go down two menus to check/set each message).
Selecting a useful encoding [Western European (ISO)]
results in display using an undesirable proportional
width font.
Manually selected encodings are easily lost and overridden
to UTF-7 (example: set ISO, save as Draft, recall, send,
it will be UTF-7**)
The appearance of an encoding is buggy; what appears when
reviewing a saved message is sometimes decoded, sometimes
not, with the same message.
Can't check a message header on an unsent message."
so Sellam aggravation is nothing compared to this <g>
If somebody wants to help, why is one of my messages today
(Sunday, November 03, 2002)
1:07 PM, BBS..., about Panix, appearing as proportoional font
and
1:53 PM, about vcfban.gif, appearing as fixed width font,
to me anyway. MS-UGH!
John A.
** hope this displays correctly, the sequences will probably be lost.
