Anyone famillar with a Samsung S300? The e-mail address is
julief(a)nytimes.com.
>Dear Mr. Coward,
>Just visited your museum web site. Very nice. Unfortunately, it didn't
>contain the information I was seeking, namely, the retail price of a
>Samsung S300 back in 1988. I'm with the New York Times and I need the
>information for a story I'm working on. If you have an idea where I can
>look, please message me. Otherwise, good luck with your museum.
>Cheers,
>Julie Flaherty
=========================================
Doug Coward dcoward(a)pressstart.com
Senior Software Engineer
Press Start Inc.
Sunnyvale,CA
Curator
Museum of Personal Computing Machinery
http://www.best.com/~dcoward/museum
=========================================
I thought this might be of interest to the Brits on the list. I have
asked him for a couple of them so leave some for me :-)
Regards
Pete
On Tue, 10 Mar 1998 12:48:15 -0000, in comp.sys.dec "Jeff Chambers"
<jeff(a)admswood.demon.co.uk> wrote:
>I have 11 VT320's surplus to my requirements, which are free to a good
>home - ie not for resale by a broker.
>
>My only requirements are that this is a UK offer (I am Leicestershire based)
>and the prospective owner(s) collects or arranges carriage. The least hassle
>you offer me the better chance you can have one/them!
>
>Jeff
>
>
>> and I am interested in something that had a processor that
>> interacted w/the user and a separate one to do the
processing
>> (ie a real-time system capable of doing all that a normal
one can)
The earliest machine I know of that did this on a large scale
was the 6000 series from CDC, starting with the CDC 6600 in late
60's, designed by Seymour Cray. The main CPU was a superscalar
60 bit processor with no I/O instructions or ports, just memory.
All I/O was handled by PPUs (peripheral processor units), which
if I recall were 24 bit CPUs, (very hazy recall here) using an
older CDC 924 type instruction set. The PPUs had direct memory
channels into the main CPU. The operating system posted
messages to the PPUs for I/O requests. The PPUs were not user
programmable, but could be programmed at the system programmer
level.
More recently, Intel designed the 8089 I/O co-processor as part
of the 8086 family. It had an instruction set optimized for I/O
functions. I vaguely recall someone made an S-100 board with an
8089 on it (was it Godbout?) but it never caught on.
Jack Peacock
At 08:22 AM 3/10/98, you wrote:
> Was it your mailbox that filled up and was bouncing messages all over the
>place?
I sure hope not! If it was, I truly apologize! But I download mail
everyday, (although on weekends I don't always get to read it right away.)
I did get the NEC stuff. Thanks!
--------------------------------------------------------------------- O-
Uncle Roger "There is pleasure pure in being mad
roger(a)sinasohn.com that none but madmen know."
Roger Louis Sinasohn & Associates
San Francisco, California http://www.sinasohn.com/
At 04:00 PM 3/9/98 PST, you wrote:
> and I am interested in something that had a processor that
> interacted w/the user and a separate one to do the processing
> (ie a real-time system capable of doing all that a normal one can)
Godbout (CompuPro) made a processor board that had both an 80286 and an
8085. I know, because I worked on such a system in the early 80's.
Meanwhile, in that same box, the disk controller had a Z80 on it.
(I am *so* sorry I didn't go back and snag that system after we (the
employees) left en masse due to not having been paid for several months.)
In the early '80s, I felt rather strongly that the ideal system would be
based on a z8000 (or 80x86 if you must) for number crunching and general
processing and a 68000 for graphics and interface stuff. Put in two
processors and let 'em do what they're best at. Still feel the same, only
these days its the '586/'060 combo (or whatever the latest is).
--------------------------------------------------------------------- O-
Uncle Roger "There is pleasure pure in being mad
roger(a)sinasohn.com that none but madmen know."
Roger Louis Sinasohn & Associates
San Francisco, California http://www.sinasohn.com/
I found an Amstrad PCW-8256 word proccessor this morning. It uses CF-2
floppy disks. Are these the same small disks that everyone was looking for
a few weeks ago?
Joe
I went and started the System/34 yesterday... Gave it a good looking-over
first. The PSU is really interesting - There's a transfomer bigger than my
head, wires about a quarter-inch thick, and stickers all over that say
"DANGER! 580 VOLTS!" and "LINE POWER HERE WITH MACHINE POWERED OFF"
But I found one little note inside which makes me think that it's single-phase
reading "INPUT POWER 208V/1PH".
Anyway, the previous owner gave me a userid and password, so I started
it up - It's all menuized. Cute. The MACHINE IN USE light is burned out too.
Oh - On the CE panel thee's a LAMP TEST button. It turns on ALL the lamps,
not the the CE-panel lamps. Also, on power-on, you have to push LOAD to
read in the bootstrap. Then supply it with a username and password.
I was tld MJR was the system manager - Is that standard on all IBM stuff?
-------
On Fri, 6 Mar 1998 00:50:19 +0000 (GMT) Tony Duell said:
Tim said about bit-rot
>> In the first stages of bit rot, single bits go "flaky" and will not
>> read reliably. So the first thing to do is read the 1702A's multiple
>> times and see if any are going bad in this way. Of course, be sure
>> to save the results of each read pass...
Tony replied with:
>With _most_ EPROMs, bit-rot causes 0's to turn into 1's, but not the
>reverse, since the fully erased (=discharged) state of the chip is full
>of FF's. Thus if you start to detect flakyness, you read the chip n times
>and logically AND the dumps. This is not hard to do given another
>computer, of course.
Tony, this didn't sound right to me so I looked it up and my book is
saying that 1702A (and the 5204) erase to all 0s. Is this wrong?
And I thought I'd pass along this neat table that I found on DataI/O
web page while looking for device code for my Series 22.
I reduced it on the xerox machine and taped it to my programmer.
DEVICE DECIMAL DECIMAL HEX HEX HEX
SIZE NO. BITS ADDR RANGE NO. BYTES CHECKSUM(1)
===========================================================================
2708 1K X 8 8K 0 ---- 3FF 400 3FC00
2716 2K X 8 16K 0 ---- 7FF 800 7F800
2732 4K X 8 32K 0 ---- FFF 1000 FF000
2764 8K X 8 64K 0 --- 1FFF 2000 1FE000
27128 16K X 8 128K 0 --- 3FFF 4000 3FC000
27256 32K X 8 256K 0 --- 7FFF 8000 7F8000
27512 64K X 8 512K 0 --- FFFF 10000 FF0000
27010 128K X 8 1M 0 -- 1FFFF 20000 1FE0000
27020 256K X 8 2M 0 -- 3FFFF 40000 3FC0000
27040 512K X 8 4M 0 -- 7FFFF 80000 7F80000
27080 1024K X 8 8M 0 -- FFFFF 100000 FF00000
2048K X 8 16M 0 - 1FFFFF 200000 1FE00000
4096K X 8 32M 0 - 3FFFFF 400000 3FC00000
8192K X 8 64M 0 - 7FFFFF 800000 7F800000
(1) Represents the checksum of a blank EPROM where memory locations contain
FF hex.
=========================================
Doug Coward dcoward(a)pressstart.com
Senior Software Engineer
Press Start Inc.
Sunnyvale,CA
Curator
Museum of Personal Computing Machinery
http://www.best.com/~dcoward/museum
=========================================
At 08:16 AM 3/10/98, Joe wrote:
> The technical reference manuals sound interesting. How big are they? I
>might get one just to add to my documentation library.
There are two of them each about 250 pgs.
> Is there a command to show the amount of memory in the HX-20? I'll try
>it with and without the expansion unit connected and see what they do. BTW
>is it normal for the HX-20 to turn on and show a menu for: 1) Monitor 2)
>BASIC ? That's what these do. Do you have any user documentation for the
>monitor and BASIC for the HX-20?
Don't really see one. HX-20's came with 16k and I think the expansion
doubled that to 32k. It looks like the command "STAT ALL" should
give you what your looking for.
Les
<Nobody has ever made a Turing machine (it's that nasty infinitely long
<tape that keeps getting in the way), but that reminds me of something I'v
<been looking for. Didn't Danny Hillis make a computer from TinkerToys
<(TM) as part of his PhD thesis or something? I've been looking for the
<schematics....
Yes I know but it has been done. Back when shift registers were commonly
available with lengths of 1024 bits it was very trivial to string a few
and get really long serial memory. With moden megabit rams it's not that
much more difficult. The tape was not so much the problem but the
programing...
Allison
