Semi-OT: I have 13 arcade games in my basement, most non-working when I got them. The video monitors in some of them are mounted "sideways" (long axis of the tube is vertical). These old units (early 1980's) all have the HV generated from the horizontal deflection, naturally. So a thin white line running vertically is actually a loss of *vertical* deflection.
Just to further confuse things :)
-Charles
> For the 7970 tape drive there ARE the full schematics on bitsavers...
the 7970 series was built by HP, the 7879 is was OEM-ed from STC .
I may have an STC manual somewhere, though it will take some digging.
They weren't particularly reliable even when they were new.
fwiw
By the mid 80s, almost none of HP's 'service' manuals had schematics.
> Seems to me back then there was at least one vendor of a
> vector-scanned (as opposed to rasterized) game. Or at least
> the product announcement was made--I don't think I ever saw
> one up close.
>
> Cheers,
> Chuck
Wells-Gardner or some such manufactured a color vector monitor for the
Atari game Tempest. It had problems with some heat and some caps. Most
Tempest games have had their monitors "Re-Cap'd."
Tony wrote:
> > I have, it's a Biomation K100-D. When I first set it up
> > Sunday afternoon,
>
> Amazingly that's what I have... I didn't get the pods with
> mine, but a bit of work and some 10124 TTL-ECL translators
> got the thing useable with TTL level signals
>
> [...]
>
> Be careful!. I have in the back of my mind the idea that the
> 8008 has an internal (8-ish level) return stack and doesn't
> use RAM for this. So you could still have RAM problems.
>
> -tony
Making your own pod...! Again, points earned Tony! Chapeau! :-)
Jim already told me that the 8008 uses an internal stack, but
I am now not so sure that the RAM is OK, so I will connect the
other 8 LA probes to the databus, to see what is taken out of
the RAM to put on the displays.
Yesterday evening was short. Much to do ... but I managed to
look at the matrix signals. It sort-of looks OK, but I admit
that I must make some better measurements to be 100% sure that
it is not there where my problem lies. The outputs of the 8881's
(on page 4, KY11-LB console board) look as described before, and
that is also what I see on the inputs of the 8093 (page KY-3).
But taking samples on the outputs is more work, as that is the
databus (input). So I see a lot of pulses are on those lines, and
it needs more setup work to find out if a stuck bit is messing
things up.
It is not likely a problem of a stuck bit on the address or data
bus, because that would corrupt the program execution of the
ROM code. I still have the feeling that there is no problem with
the RAM, ROM, CPU, 3-state transceiver, and the decoding logic.
This evening I hope to check out (thoroughly) the keypad circuits.
thanks for the input!
- Henk.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
> I'm still nearsighted, but since then, I've also learned double bass and am
> setting my sights on learning viola this year. Just another noise to
> torment the dogs...
Wow, double bass, I'd like to play that one! :)
>
> Are musically-minded people still as commonplace in the computer business
> as they once were?
>
Well yeah, playing bass guitar and piano, composing classical music. Last piece was for orchestra,
the current one I'm writing is for piano and cello.
Didn't somebody say on the list that he plays the cello?
Anyhow, lots of people how are envolved in science/engineering share music as a passion as well.
Regards,
Pierre
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsst?rkeren E-Mail-Postfach!
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
> > Someone should create brief lisings under IBM and Univac catagories
> > stainge that their drives are actually Fujitsu drives and redirecting the
> > reader to the Fujitsu folder.
> And perhaps also the Memorex relabel.
>
Yes, that a nice idea.
> Pierre: Merci and danke! :)
I only contributed the BT3200 documents, not the actual Fujitsu manuals, which certainly are of big help!
Though the full schematics are still missing... will be scanned during next year when I'm getting back to Germany so that the complete set will be online. Tore, you'll have to wait a little bit in case you want to repair your broken drives if it's an electronic problem...
Al, thanks once more for your amazing efforts on maintaining bitsavers!
Regards,
Pierre
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsst?rkeren E-Mail-Postfach!
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
>From: "Chuck Guzis" <cclist at sydex.com>
>
>On 11/8/2005 at 7:36 AM Allison wrote:
>
>>NEC and DEC but never Datapoint.
>
>Darn--I've wondered about a design link between Datapoint and Beehive
>terminals. The Beehive design resembled the Datapoint more than
>trivially--it used no static ram, but rather dynamic shift registers as
>screen and working memory for the 8008. Since that was a pretty formidable
>design for its time, I wondered if Beehive had recruited Datapoint talent
>to do it, since DP would have had the best knowledge of the wiorkings of
>the 8008.
>
>Cheers,
>Chuck
>
Hi
All I know is the Datapoint keyboards were not
easy to use while the Beehive's used the Hall effect
keys from Microswitch.
Dwight
>From: "Allison" <ajp166 at bellatlantic.net>
>
>>
>>Subject: Re: help - 11/34 console problem -- first LA output
>> From: "Chuck Guzis" <cclist at sydex.com>
>> Date: Mon, 07 Nov 2005 20:18:21 -0800
>> To: cctalk at classiccmp.org
>>
>>On 11/7/2005 at 9:31 PM Allison wrote:
>>
>>>Well save for wrap around. The stack on 8008 is strictly address and
>>>as already said 14bits (the 8008 only addresses 16k!!) and 8 levels deep.
>>>It was a challenge programming it to figure out where you came from and
>>>also not blow the stack. Still it beat the design we had before it as
>>>that was around 220 pcs of TTL sequential logic.
>
>Well my 8008 experience predates DEC and the TTL horror was pre 8008!
>
>I'll say it this way. The 8008 was a ground breaking micro. From a
>programmers perspective it wasn't too bad but from a hardware designers
>and debug perspective it was nasty. It was enough to be a micro but as
>feature free as one can get. However for the time it was pushing the
>limit for integration at around 5000 transistors in Pmos.
>
>The number of chips with limited internal stacks would amaze you. The
>8048/9 series is a fairly well known one, TMS1000 4 bitters, NEC uCOM4
>4 bitters, NEC uCOM75 series, National COPs and even the PIC all come
>to mind. And in every one them if you exceed the stack something falls
>off the bottom. Stack red zone hardware is truly a big machine thing.
Hi
I thought I might add that many current day DSP chips also
have internal stacks. Of course the Forth chip, the NC4000
used external stacks but had 3 busses to handle them so that
one could have all being active at one time. Two were stacks
and one was for instruction/data.
The 2100 family DSP by ADI has a limited internal stack as well
but it seems like I remember it would generate an interrupt if
it overflowed.
Most tools for these have a method of indicating if the code
your running has a combination of main flow and interrupts
that would cause an overflow. Although, it doesn't seen so,
the worst case is predictable.
Dwight
>
>>I always wondered why a carry or borrow from the stack pointer couldn't
>>have at least generated a branch to some known location. It may not have
>>exactly told you where your code went bonkers, but it'd be better than
>>letting the program run wild! How many micros used a local stack? The
>>Natoinal PACE is the only other one that comes to mind, but at least it had
>>a "stack about to overflow" interrupt and a way to access the stack
>>directly.
>>
>>Were you a Datapoint employee?
>
>NEC and DEC but never Datapoint.
>
>
>Allison
>
>
>
>Subject: Re: help - 11/34 console problem -- first LA output
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Tue, 08 Nov 2005 07:20:06 -0800
> To: cctalk at classiccmp.org
>
>On 11/8/2005 at 7:36 AM Allison wrote:
>
>>NEC and DEC but never Datapoint.
>
>Darn--I've wondered about a design link between Datapoint and Beehive
>terminals. The Beehive design resembled the Datapoint more than
>trivially--it used no static ram, but rather dynamic shift registers as
>screen and working memory for the 8008. Since that was a pretty formidable
>design for its time, I wondered if Beehive had recruited Datapoint talent
>to do it, since DP would have had the best knowledge of the wiorkings of
>the 8008.
>
>Cheers,
>Chuck
That was technology of the era. hasiltine H1000 and H2000 terminals
and I think the VT05(hard memory test) did as well. Static rams were
expensive and small and since screen ram was by nature circular as
part of the raster scan it makes sense to keep the whole mess as
shift registers.
Never worked much with terminals printing systems were more my thing.
Allison
Hey folks,
The Fujitsu M2436 manuals are now online on bitsavers.
You can find them in the Fujitsu folder M243X as well as in the univac folder: BT3200 disk drives.
They are just relabeled Fujitsu drives.
IBM relabeled them as well as we found out on a recent discussion.
Regards,
Pierre
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>
>Subject: Re: help - 11/34 console problem -- first LA output
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Mon, 07 Nov 2005 20:18:21 -0800
> To: cctalk at classiccmp.org
>
>On 11/7/2005 at 9:31 PM Allison wrote:
>
>>Well save for wrap around. The stack on 8008 is strictly address and
>>as already said 14bits (the 8008 only addresses 16k!!) and 8 levels deep.
>>It was a challenge programming it to figure out where you came from and
>>also not blow the stack. Still it beat the design we had before it as
>>that was around 220 pcs of TTL sequential logic.
Well my 8008 experience predates DEC and the TTL horror was pre 8008!
I'll say it this way. The 8008 was a ground breaking micro. From a
programmers perspective it wasn't too bad but from a hardware designers
and debug perspective it was nasty. It was enough to be a micro but as
feature free as one can get. However for the time it was pushing the
limit for integration at around 5000 transistors in Pmos.
The number of chips with limited internal stacks would amaze you. The
8048/9 series is a fairly well known one, TMS1000 4 bitters, NEC uCOM4
4 bitters, NEC uCOM75 series, National COPs and even the PIC all come
to mind. And in every one them if you exceed the stack something falls
off the bottom. Stack red zone hardware is truly a big machine thing.
>I always wondered why a carry or borrow from the stack pointer couldn't
>have at least generated a branch to some known location. It may not have
>exactly told you where your code went bonkers, but it'd be better than
>letting the program run wild! How many micros used a local stack? The
>Natoinal PACE is the only other one that comes to mind, but at least it had
>a "stack about to overflow" interrupt and a way to access the stack
>directly.
>
>Were you a Datapoint employee?
NEC and DEC but never Datapoint.
Allison
>
>Subject: Re: MSCP SCSI controller speed
> From: "Tim Shoppa" <tshoppa at wmata.com>
> Date: Tue, 08 Nov 2005 08:52:24 -0500
> To: <cctalk at classiccmp.org>
>
>>From a post I made to the PDP-11 newsgroups in the previous
>millenium:
>
>The benchmarks were done under RT11FB 5.7 doing 1, 2, 4, 8, 16,
>32, and 64 block-at-a-time READW's and WRITW's to 16384-block
>data files. A KDJ11B (PDP-11/73) CPU with 2 Megabytes of Clearpoint
>non-PMI memory was used for the bencharmks. With the SCSI
>controllers a Barracuda 7200 RPM ST15230N drive was used; with
>the RQDX3 a RD52 drive was used.
>
>
>Here are the peak data rates measured for read and write 64
>blocks-at-a-time:
>
>
> Read Write
> ---------- ----------
>Andromeda SCDC 2.298 MB/s 1.131 MB/s
>CMD CQD440 2.397 MB/s 1.525 MB/s
>CMD CQD220 1.418 MB/s 0.882 MB/s
>CMD CQD220A 2.088 MB/s 1.409 MB/s
>DEC RQZX1 1.379 MB/s 1.097 MB/s
>Viking QDT 0.846 MB/s 0.704 MB/s
>DEC RQDX3 0.164 MB/s 0.161 MB/s
>
>From using the RQDX3 on PDP-11 and microVAXII against the
Viking QDT and CMD220 I can say the RQDX is glacially slow.
Allison
I went scrounging again last weekend and came home with this. It looks
like this one from an old Ebay auction.
<http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=7530644273>.
It has two HH floppy drives and it is DIGITAL storage so it's somewhat on
topic. Does anyone know anything about these? I've figured out some
controls but I don't have a clue what others do. I'm also trying to figure
out how to use the disk storage and recall function. I inserted a 360k
MS-DOS disk and it displays E7 and it also says ERR if I try to store or
recall anything so I don't think it likes that format and it doesn't seem
to be capable of formatting it's own disks. Does anyone have any idea what
format it's looking for?
Joe
Allison wrote:
> Well save for wrap around. The stack on 8008 is strictly
> address and as already said 14bits (the 8008 only addresses
> 16k!!) and 8 levels deep.
> It was a challenge programming it to figure out where you
> came from and also not blow the stack. Still it beat the
> design we had before it as that was around 220 pcs of TTL
> sequential logic.
>
> The interrupt/reset logic was pretty strange too.
>
> Allison
I am glad that DEC threw away the 220 ICs design,
and put in the 8008 :-)
- Henk.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
There's some M4 data 9914 tape drives on ebay, but the guy only wants to
sell them in a group of 4 (ie, lots o money).
Anyone want to go in together and buy the lot of 4 and split them up? They
appear to be pertec units, but I just need one for parts so that doesn't
matter.
Contact me off-list if interested!
Jay
>
>Subject: Re: help - 11/34 console problem -- first LA output
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Mon, 07 Nov 2005 17:47:26 -0800
> To: cctalk at classiccmp.org
>
>On 11/7/2005 at 11:57 PM ard at p850ug1.demon.co.uk wrote:
>
>>Be careful!. I have in the back of my mind the idea that the 8008 has an
>>internal (8-ish level) return stack and doesn't use RAM for this. So you
>>could still have RAM problems.
>
>Exactly--and they're 14 bits (not 16) wide--and overflow and underflow are
>not checked for. It's sometimes easier just to think of it as 8 14-bit
>P-counters, with the CALL and RET simply incrementing and decrementing the
>pointer to the appropriate P-counter (with CALL performing a jump to load
>the current P-counter).
>
>Cheers,
>Chuck
Well save for wrap around. The stack on 8008 is strictly address and
as already said 14bits (the 8008 only addresses 16k!!) and 8 levels deep.
It was a challenge programming it to figure out where you came from and
also not blow the stack. Still it beat the design we had before it as
that was around 220 pcs of TTL sequential logic.
The interrupt/reset logic was pretty strange too.
Allison
I have this dead XT here, and I wanted to replace its motherboard with a
newish ATX beastie. Anyone know where I might be able to find some
pointers?
Peace... Sridhar
Tony wrote:
> Do you have a logic analyser? If so, then I would try looking at the 8080
> address bus. See what bit of the program it's executing, see if it does
> the right things when you press the keys, etc.
I have, it's a Biomation K100-D. When I first set it up Sunday afternoon,
and turned the LA on, the screen moves vertically. So I had to get the LA
in good working order first! As I have the operator & service manual, the
location of the vertical freq. adjustment was quickly found. The screen is
now steady.
I connected the pod B, 8 data inputs to the ROM address lines A0-A7, and
gave it a manual trigger to capture all it sees. At first I got too much
detail (address repeats several times), but after setting the clock of the
LA to sample at 10 ?s I got almost always consecutive addresses.
That depends on the length of the instruction. Anyway, I see the addresses
60-110 (octal) in the correct order and see the address jump at 101 to the
address 335 (a subroutine). I see the complete execution of the subroutine
and the return. Indeed going to address 105. That means the stackpointer
and the memory must be OK! ReturnPC stored in RAM, and retrieved correctly.
However, I can not check everything. Need to connect pod A, and have 8 more
data input lines to measure interesting things. And trigger facilities!
It's time to read the user manual of the LA, to do advanced measurements.
I still haven't got a clue what's going wrong ...
- Henk.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
At 09:57 07/11/2005 -0500, you wrote:
>Re: " What does a single vertical line in the middle of a display indicate?"
>
>This is a symptom that is normally never seen.
>
>It would, in theory, indicate loss of horizontal deflection. The problem is
>that loss of horizontal deflection in virtually all monitors also causes
>loss of high voltage, which keeps you from seeing ANYTHING. [The high
>voltage is obtained from the horizontal output transformer ("flyback"
>transformer) in virtually every TV set and monitor made.)
>
>One possibility: If the horizontal deflection yoke was open, there could be
>a loss of horizontal deflection while you still had output from the
>horizontal output transformer. Usually, an open yoke would shut down the
>horizontal output and high voltage, but it's the only way I can think of
>that you might get loss of horizontal deflection and still have high
>voltage.
I have a MAC Plus with the same symptom - seemed odd to me as well, so I asked
a local guy who used to repair monitors. He didn't think it was that odd, here
is what he responded with (I haven't had time to look further at it yet):
>#2 - I've got a Mac Plus which displays a thin VERTICAL line - I've not
>seen this before, because since it has HV, the horizontal oscillator must
>be running! - any guesses?
This obviously has separate circuits for EHT and horizontal
drive/deflection, and the deflection circuit has a bad drive component or
bad solder joint. Usually the HOT goes due to high ESR caps in the primary
side of the transformer driving the HOT, or the solder joints go bad because
of the high drive currents and heat. Also check the flyback transformer
(actually, all) solder joints with a 10x loupe. You really need an ESR
meter and to go through all the electrolytics on the board. I regret selling
mine a few years back; that was an invaluable piece of test gear.
Regards,
Dave
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html
>
>Subject: TI 99/4A Power Supply
> From: "Harriman, JT" <jharriman at waff.com>
> Date: Mon, 07 Nov 2005 12:34:39 -0600
> To: <cctech at classiccmp.org>
>
>Good afternoon
>
>
>
>Can you tell me if the TI 59 calculator requires a DC or AC wall-wart?
>
>
>
>Thanks
>
>
>
>JT
The 99/4a is AC the 59 is DC
Allison
Hello folks,
somebody has uploaded some useful information about these drives to
bitsavers - thank you!
There is only a kind of technical overview manual for my drive at the
moment.
But I still and urgently need the schematics for the 7978 drive. My
power supply has broken down and I cannot get it back working. I also
don't know how to repolace it because I don't know where to connect
+/-12V and power good etc....
Thank you very much!
Philipp :-)
P.S.: Shouldn't my Honeywell software be hosted on bitsavers, too?
I forget. What does a single vertical line in the
middle of a display indicate? It might be something
entirely different from an image that collapses into a
horizontal line, but I seem to remember one of them
representing a definitive component failure. If it
makes a difference, the unit is a compact Mac, a
Classic I think. Can any (and all) *new* display
components still be had for such a unit. Substitutes?
Reasonable facsimiles? Yo thanks.
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
Hi,
I seem to remember that I have a copy of the UCSD p-System for a PC. I also
have a z-80 cross-assembler for that environment.
I'll have a look in the storage room tonight and see if I can find the
media. From memory, it was distributed on 5.25", 360K floppies.
What are the re-distribution rules? I believe that UCSD still exists, so it
is probably not abandonware.
Regards
Doug Jackson
Hey, does anyone here have a black 1.2MB floppy drive? I'm going to
make it a permanent addition to my current PC for data transfer to/from
my pdp-11 and DECmate.
I have a Digital Equipment Corporation AlphaServer 1000 4/266 for sale.
The price is negotiable, but I'd really like to get around $100 for it if
possible.
This unit has a StorageWorks SCSI expansion chassis as well as a ton of
manuals - mostly VMS.
It comes with the owners manual and VMS CDs.
The unit worked perfectly when pulled from service but we had to junk the
drives in order to protect sensitive data thereon (per previous threads.)
The unit takes common SCSI drives, however, so getting it going will be a
snap. All of the drive caddies for both the system unit and the
StorageWorks cabinet are present.
Here's the rub - the unit is heavy, Especially with all of the manuals,
so this is a pick-up only deal in San Jose, CA. I don't have any time to
pack and ship this beast.
Please email me directly with offers.
Thanks!
--
Erik Klein
www.vintage-computer.comwww.vintage-computer.com/vcforum
The Vintage Computer Forum
With all of this ragging on audio nut who spend obscene amounts of money on
wire, I decided to at a look. I don't know why we call them crazy, they
don't have 1975 computer running in the basement.
The guy in the next office is in to high end audio. (Although he claims that
he is in the lower end of the people in his audio club.) I asked if he had
a power cord so I could take some pictures. He had a spare PS Audio xStream
Statement Power Cable, the 2 meter version lists for $550. This is 6 gauge
oxygen free copper with machined connectors. The cord has a ferrite
impregnated jacket.
Here is my short review of the power cord
http://www.swtpc.com/mholley/MP_F/PS_Audio.htm
I took it home and hooked it up to my new custom case computer which also
cost me about $550. It is a modern 3 GHz Pentium that looks like a 1975
SWTPC 6800.
http://www.swtpc.com/mholley/MP_F/MP_F.htm#NewCover
Chris,
I hope I'm safe in assuming that this is a CRT monitor... otherwise,
disregard the following:
(1) a vertical line means no horizontal deflection, but
(2) a visible line means there is high voltage on the CRT, meaning the
horizontal oscillator is buzzing merrily along.
Chances are that the horizontal deflection coil on the yoke is open.
If you're lucky, a wire may have broken running to the
electromagnet-thingy clamped on the neck of the tube - if not, getting a
replacement yoke depends on how much support you can get from Apple.
Alternatively, find a similar monitor that died of a different problem
and mug it for the replacement. Chances are that the display will look
distorted, since each yoke has little permanent magnets glued to it that
linearize that particular yoke for its CRT. This is the issue even for
a brand-new yoke.
Bob Maxwell
Acquired this card with no docs. It bears the "TELETEK" logo on the
front and back along with "(C)1981 rev2 0601-0112" on the back. I don't
have any other model information.
Top 1/2 of card has two regulators with heat sinks on the left, and two
rows of 16 16k DRAMs each extending to the right side.
Bottom 1/2 of the card has mostly TTL, an AMD2964B (40 pin), three TTL
delay line devices, one open "jumper socket", and jumpers sprinkled
around, with a row of 14 jumpers at the lower right hand corner.
(All views described looking at component side with S-100 connector
at the bottom.
Anyone got one of these cards?
Any info on jumper settings etc. would be greatly appreciated.
Regards,
Dave
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html
sent it too soon, sorry..
Item #7559862560
> -----Original Message-----
> From: Ram Meenakshisundaram
> Sent: Monday, November 07, 2005 2:39 PM
> To: 'cctech at classiccmp.org'
> Subject: Databooks on EBAY (Belgium)
>
>
> Here is a lad who is selling about 300 databooks for 5Euros per book:
>
>
Re: " What does a single vertical line in the middle of a display indicate?"
This is a symptom that is normally never seen.
It would, in theory, indicate loss of horizontal deflection. The problem is
that loss of horizontal deflection in virtually all monitors also causes
loss of high voltage, which keeps you from seeing ANYTHING. [The high
voltage is obtained from the horizontal output transformer ("flyback"
transformer) in virtually every TV set and monitor made.)
One possibility: If the horizontal deflection yoke was open, there could be
a loss of horizontal deflection while you still had output from the
horizontal output transformer. Usually, an open yoke would shut down the
horizontal output and high voltage, but it's the only way I can think of
that you might get loss of horizontal deflection and still have high
voltage.
Once again, I was too busy to take photos at the VCF of all the exhibitors
:( Hopefully someone took nice ones with the exhibitor standing in front
of the exhibit, but I'll take whatever you have.
Please contact me if you have any.
P.S. I'm unsubscribing from the CC list so any communications should come
directly to me.
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
I enjoy retrocomputing on my old IBM 5150 but sadly my trusty 5151 is dead as is my 5152.
I am using a terribly screen burnt amber "1998" monitor. I have both EGA and MDA IBM
adapters so I can use any screen type.
If anyone around wisconsin has some extra 9pin monitors Monochrome, color or whatever
or knows of a good source I would be thankfull.
Also my IBM XT keyboard is pretty much dead as well. I am willing to boot some cash
if needed and travel to pickup if your local.
For my other projects I need some 1mx4 20pin dipp memory and a Quantum Prodrive 50pin
scsi 270mb hard drive (it must be that exact model) I can't seem to find a source of that stuff
either. My site displaying my old photography computers from the 80's is here
http://www.colortron.tk but someone here says it has non-worksafe popups, my suggestion use Mozilla, though the popups seemed to all be for either vonage when I checked. I am looking for any information on INnovion (the company that made the units) and their older Computer Photo systems from the early 70's. The original Apollo VP1 used a 4 bit processor and printed photos in 8pt text on oversized paper.
I used to be able to get old pcs from computer recycling places but they have all closed shop, if anyone here knows of some wisconsin based companies that recycle old pcs and would let someone take a few post a line. My hobby is getting harder to support without parts :(
On a plus note although retro computing is getting a little less common at least uncreativelabs.org is back :)
Thank You For Any Info
Ryan
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
Hello,
I did a search for the IIBM 5360 and you came up. I have one sitting in
my warehouse and was wondering if it has any value? Thank you, Dawn
Dawn Goodloe
Shipping and Recycling Coordinator
317-545-4747x33
317-710-0386 cell
www.goldsmithgroup.comwww.usedprinters.com
>
>Subject: RE: help - 11/34 console problem - first measurement results
> From: "Gooijen, Henk" <henk.gooijen at oce.com>
> Date: Sun, 06 Nov 2005 18:06:41 +0100
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
> Cc: "Gooijen, Henk" <henk.gooijen at oce.com>
>
>------_=_NextPart_001_01C5E2F4.74FC0C20
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>Allison wrote:
> =
>
>> I'd consider that the 8008 is getting bad input data from a bad scan line=
>
>> which it will output or that it's outputing correctly and the data is
>> corrupted after output due to bad latch or other hardware.
>>
>> One likely possibility is not ram as a prblem but a I/O port that has a
>> stuck bit. Or the control for that port is stuck. This is most likely
>> if the basic fuctions are there (8008 program runs) but some parts of
>> the data used to control the 11/34 or display it's status is not correct.=
>
>>
>> FYI the 8008 can be single stepped if you pull the "READY" line each
>> cycle and just look at the bus with a simple logic probe or clip.
>
>Thanks for the good input Allison!
>I hooked a logic analyzer to the address lines A0-A7 on one of the program
>ROMs, and simply sampled the data without any trigger. With the display in
>octal mode, I can see the executed address sequence. The 8008 executes the
>main loop and calls SHFT1 *and* returns to the correct PC. That means that
>the ROM, RAM (to store the return address) and associated circuits must be =
>OK.
Ok rom for sure and may be on the ram. The 8008 has an internal push
down stack that is 8 deep for call/return.
Allison
I have developing somewhat of an interest in Japanese computers lately,
and recently on a.f.c., someone pointed to the museum at:
http://www.ipsj.or.jp/katsudou/museum/
Great pictures!
I noticed that some of the pictures appear to be of survivors - old
machines from the 60s and 70s that are still around. Does anyone, perhaps
a Japanese list member (are there any?) know anything about the computer
museum scene in Japan?
William Donzelli
aw288 at osfn.org
>
>Subject: Re: FPGA VAX update
> From: woodelf <bfranchuk at jetnet.ab.ca>
> Date: Sun, 23 Oct 2005 15:10:44 -0600
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Michael Sokolov wrote:
>
>>Chuck Guzis <cclist at sydex.com> wrote:
>>
>>
>>
>>>If PC-based emulators are fast enough, why bother with the IC version?
>>>
>>>
>>
>>1. I don't want an emulator, I want The Real Thing (tm).
>>
>>2. A pee sea based emulator requires a pee sea. I refuse to contaminate
>>my house with a pee sea.
>>
>>
>FPGA software requires a pee sea sadly enough. I suspect a 8080 could do
>PCB or CUSTOM
>IC design if you could use a programable character set on a terminal.
>When you think about it
>it is the hidden documentaion in closed hardware that is the problem. I
>open source FPGA
>could be done as a custom chip but getting around the hardware patents
>is the problem..
An 8080 could not do it and graphics has little to do with it.
FPGA P&R is a really large array problem that eats memory and cpu.
The PC is a common choice as it's become fast enough and common
as houseflies. After PCs what s the next most common hardware?
A vendor of hardware (FPGAs) really only provides software so they
can sell the part, I doubt that software is a money maker for them.
So with that in minds if you not running a PC then likely the
alternate hardware is from the small list:
VAX or Alpha running UNIX
AS400?
Something PowerPC based?
SUN?
What else is out there that's not wintel, fast enough and can address
a large memory that runs a fairly current UNIX. That also assumes
the software that can P&R the FPGA is available as source.
Allison
> > By that period, HP comptuers were 'repaired' by board-swapping. If you're
> > lucky there will be _some_ useful info in the boardswapper guide, like
> > pinouts or testpoints.
> You are too pessimistic :-) I hope to find good documentation of
> everything I need.
Optimism is important, but unfortunately in the past, losts of machines came up but no reasonable service documentation
are at least without full schematics published.
Or they were never published later on, as companys were in business to shortly.
ONYX and Plessey come directly to my mind.
I've never seen documents of Emulex boards as well.
Maybe somebody can correct me, that would be nice to hear.
Pierre
______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130
>
>Subject: Re: FPGA VAX update
> From: William Donzelli <aw288 at osfn.org>
> Date: Sun, 06 Nov 2005 09:38:47 -0500 (EST)
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
I posted that the EGO homebuilt comnputer was in 1985 and there
was another article on the TOY.
Well I found it. BYTE January 1987, Phil Koopman Microcoded vs Hardwired Control
The deisgn is a 16bit fairly minimal machine that could actually run real code
if built. The article does not fully discuss the the total machine but the control
logic is covered. The rest is almost obvious. Likely chip count for the entire
machine could be under 60 TTL peices if octal latches and Tristate gates plus the
74181s were used. If GALs were used the likely chip count could be smaller.
TOY itself was 16 bits, 4 bit instruction and 12 bit address, Single accumulator.
The ALU was 74181 so the basic arithmetic and logical instructions are native to
that chip and the remainder are jmpz (jump if zero) and load (put value in Acc)
and Store (save Acc at location). Oddly enough 4 no-ops, so theres room for
instruction set improvement.
A machine like this goes far to demystify how computers work.
An aside to all this is one of the annoying things when I was studying
computers early one (3++ decades ago) was "computer books" would endlessly
detail logic at the gate and flipflop level. Maybe discuss arithmetic and
sequential logic. They never quite cross the line to how these blocks form
computers. It wasn't until the PDP-8 handbooks that there was a connection
of the ideas of sequential logic controlling arithmetic and logical blocks.
Allison
> -----Original Message-----
> From: William Donzelli [mailto:aw288 at osfn.org]
> Sent: Sunday, November 06, 2005 10:02 AM
> Forwarded:
>
> > From: William Donzelli [mailto:aw288 at osfn.org]
> > Sent: Thursday, November 03, 2005 8:01 AM
> > To: Don Reaves W5OR
> > Subject: RE: National SW-54 bites the big one
> >
> > > What should I do with my PDP-11/24, PDP-11/03-L, and RL02 bits?
> > > Send me a buyer/trader as I need to get them off my carport
> > before winter.
> > > No racks, no interconnect cables, just the units as they
> > were removed from
> > > the rack years ago.
> > >
> > > If I must I'll put them on 'bay, as a precursor to carting
> > them to the
> > > smelter.
> >
> > Can I post this to another list?
>
>
>
Who has it? Where in Arkansas? Based on the call sign, I'd guess it was Don
Reaves in Little Rock, but I'd like to verify before contacting him.
Kelly
Yes, the diagnostics disks are used for CMOS setup on the AT. 'DEBUG'
>from DOS can also be used, but that's a little too (warning - bad pun
alert .. ) hard core for me.
The Advanced Diagnostics that I mentioned is for the PC and XT, and came
with the hardware maintenance and service manual. It has the low level
format routine for the 10MB XT hard disk, which is useful if your
controller doesn't have an onboard routine to do it. (I'm not sure
which ones do and don't.)
The regular Diagnostics disk are for the PC and XT, and are also a good
test of clone compatibility. Do not run them on a PCjr. :-)
Mike
I wasn't able to get Jim version 2.02, but 2.05 was close enough.
I have images of the following if anybody needs them:
Diagnostics 2.05
Diagnostics 2.23
Advanced Diagnostics 2.20
Diagnostics PC AT 1.00
Diagnostics PC AT 1.02
Diagnostics PC AT 2.06
As an IBM employee I feel responsible for keeping these old machines
running. ;-)
Mike
Hi All,
I wonder if anyone here could help us. We have an analog computer in our
collection that was built by LAN-Electronics in England in the mid-1960's.
It has a number of unusual features including a phone dial on the front of each
of the patchboards (for data entry?) and some very small inputs for the
patchcords (the patchcords for the PACE TR-10 or TR-20 are way too big). Anyone
have any information on this or any ideas about the computer? We'd appreciate
the help. You can find pics of it at www.earlycomputers.com.
thanks,
Michael
Hi, Don,
Thank you! The alternative address path you provided worked just fine.
I apologize for an erroneous initial assumption that GoDaddy's DNS was screwed up. My new conclusion is that my browser is not understanding the redirection you mention. Good thing I didn't fill out a trouble ticket just yet. ;-)
Thanks again.
*********** REPLY SEPARATOR ***********
On 06-Nov-05 at 00:11 Don North wrote:
>Bruce, are you still seeing this problem? If so, what browser/OS are you
>using?
>I've used Firefox, Netscape8, IE6 on WinXP and Win2K, and Safari on the
>Mac.
>
>The background is that www.ak6dn.com is not a top level website, but hosted
>in a subdirectory (ie, www.ak6dn.com/blah... =>
>www.slowdeath.com/AK6DN/blah...).
>References to www.ak6dn.com are redirected via an HTTP 'Location: ...'
>directive.
>If your browser does not grok this it could be an issue.
>
>If you are still having problems, you can get there by the alternate
>path using:
> http://www.slowdeath.com/AK6DN/PDP-11/M9312/
>instead. As you note going direct to http://www.slowdeath.com is another
>beast altogether...
>
>Don
>
>Bruce Lane wrote:
>
>>Hi, Don,
>>
>>*********** REPLY SEPARATOR ***********
>>
>>On 04-Nov-05 at 00:33 Don North wrote:
>>
>>
>>
>>>I've posted a web page <http://www.AK6DN.com/PDP-11/M9312/> that has
>>>M9312 PROM images in Intel HEX format as well as commented source and
>>>assembly listings of all the well-known devices, both boot and console.
>>>
>>>
>>
>> <snippety>
>>
>> I tried to get to these this evening. Your web site address seems to be
>rerouting to something called 'slowdeath.com,' and is demanding a password
>to get any farther than the front page.
>>
>> Please advise. Thanks much.
>>
>>
>>-=-=-=-=-=-=-=-=-=-=-=-
>>Bruce Lane, Owner & Head Hardware Heavy,
>>Blue Feather Technologies -- http://www.bluefeathertech.com
>>kyrrin (at) bluefeathertech do/t c=o=m
>>"If Salvador Dali had owned a computer, would it have been equipped with
>surreal ports?"
>>
>>
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Bruce Lane, Owner & Head Hardware Heavy,
Blue Feather Technologies -- http://www.bluefeathertech.com
kyrrin (at) bluefeathertech do/t c=o=m
"If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"
Wai-Sun,
I've been trying to get hold of you, but have not gotten any response (it's possible that your mail may have bounced due to our spam filtering).
I have received the Data I/O conductive pad that you wanted. Do you still need it?
If your return mail is bouncing, try my backup address of kc7gr (at) qsl dot net.
Thanks much.
-=-=-=-=-=-=-=-=-=-=-=-
Bruce Lane, Owner & Head Hardware Heavy,
Blue Feather Technologies -- http://www.bluefeathertech.com
kyrrin (at) bluefeathertech do/t c=o=m
"If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"
Allison wrote:
> I'd consider that the 8008 is getting bad input data from a bad scan line
> which it will output or that it's outputing correctly and the data is
> corrupted after output due to bad latch or other hardware.
>
> One likely possibility is not ram as a prblem but a I/O port that has a
> stuck bit. Or the control for that port is stuck. This is most likely
> if the basic fuctions are there (8008 program runs) but some parts of
> the data used to control the 11/34 or display it's status is not correct.
>
> FYI the 8008 can be single stepped if you pull the "READY" line each
> cycle and just look at the bus with a simple logic probe or clip.
Thanks for the good input Allison!
I hooked a logic analyzer to the address lines A0-A7 on one of the program
ROMs, and simply sampled the data without any trigger. With the display in
octal mode, I can see the executed address sequence. The 8008 executes the
main loop and calls SHFT1 *and* returns to the correct PC. That means that
the ROM, RAM (to store the return address) and associated circuits must be OK.
Thanks for the tip, but I hope (after studying the LA usage) that cycle stepping
will not be needed. Now that I have the LA set up (first time use!), and checked
the program execution, I will refocus on the scan matrix. With the 'scope, I had 2
time traces at best, with the LA I can have 16, thus *all* signals for the keyboard
and the display (because scan keyboard drive == common display drive).
I will post any progress!
- Henk, PA8PDP.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
I found one of the rom images I put up was a bad prom. Another one read
consistently but didn't match two other sources. The images have been
replaced. Affected images : 752A9, 248F1, 616F1. I replaced them after
getting multiple other images and comparing, so I'm confident the ones up
now are all correct.
I'd like to post source listings for the boot programs. Anyone got a program
to re-arrange the bits correctly, then disassemble?
Jay
>
>Subject: RE: help - 11/34 console problem - first measurement results
> From: "Gooijen, Henk" <henk.gooijen at oce.com>
> Date: Sun, 06 Nov 2005 09:20:27 +0100
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>
>Content-Transfer-Encoding: quoted-printable
>
>Tony wrote:
>
>> Interesting, the LSB is being lost somewhere (that would explain why
>> 1 does nothing, why 5 behaves as 4, etc).
>>
>> What sort of RAM is on this board (I can't be bothered to find the
>> prints tonight ;-)), do you know if it's good. I've found old SRAM
>> to be notoriously unreliable.
> =
>
>Interesting, I had not thought of that, may be a stuck bit.
>I must have a better look at the program code listing. Checking out
>the RAM is a bit difficult. It consists of two 4-bit chips with
>separate data IN and data OUT pins, type 86586 (?).
>If the 8008 uses the RAM for storage of variables, I guess that I can
>safely say that the RAM (plus associated circuitry to read/write) must
>be OK.
>
>> Since I have a logic analyser 'to hand', I would start looking at those
>> 3 inputs to the '47. Where do they come from on the M7859? An output
>> port on the 8008? Do we know that port is latching correctly? Or more
>> likely, the 8008 is writing the wrong values to it.
> =
I'd consider that the 8008 is getting bad input data from a bad scan line
which it will output or that it's outputing correctly and the data is
corrupted after output due to bad latch or other hardware.
>Page KY-4 has all the decode logic. There is a second post to this list
>on its way, posted Friday morning ... it's now Sunday morning ...
>The signal KY4 READ INPUT 5L from the 74154 is used on page KY-3 to
>enable 8093 AND gates to read the scan matrix lines. =
>
>The signal KY4 LD REG 0H via a 7404 from the 74154 is used on page KY-6
>to enable a 74175 latch of which the outputs drive the scan matrix.
>Likewise, KY4 LD REG 1H drives the 3 NUM lines for the 7447.
> =
>
>Before I go on writing long stories here, I think it is best to wait
>for the e-mail from last Friday to appear here.
>Thanks for working with me Tony, it helps keeping focussed ...
> =
>
>- Henk, PA8PDP.
One likely possibility is not ram as a prblem but a I/O port that has a
stuck bit. Or the control for that port is stuck. This is most likely
if the basic fuctions are there (8008 program runs) but some parts of
the data used to control the 11/34 or display it's status is not correct.
FYI the 8008 can be single stepped if you pull the "READY" line each
cycle and just look at the bus with a simple logic probe or clip.
Allison
Forwarded:
> From: William Donzelli [mailto:aw288 at osfn.org]
> Sent: Thursday, November 03, 2005 8:01 AM
> To: Don Reaves W5OR
> Subject: RE: National SW-54 bites the big one
>
> > What should I do with my PDP-11/24, PDP-11/03-L, and RL02 bits?
> > Send me a buyer/trader as I need to get them off my carport
> before winter.
> > No racks, no interconnect cables, just the units as they
> were removed from
> > the rack years ago.
> >
> > If I must I'll put them on 'bay, as a precursor to carting
> them to the
> > smelter.
>
> Can I post this to another list?
On Nov 1 2005, 16:09, Jules Richardson wrote:
> Chuck Guzis wrote:
> > This may be appropriate for another list, but it seems to me that
there's
> > plenty of applicable knowledge here.
> >
> > Right now, we're using an older Compaq Deskpro P3-600 box as our
incoming
> > Linux server. Basically, it connects with the DSL modem and
contains IP
> > masquerading, DNS caching, firewall and fetchmail/procmail/qmail
tasks
> > (SpamAssassin included). It runs 24x7 with no problem, as it has
for the
> > last 5 or 6 years. Built like a tank.
>
> Would an offering from one of the various UNIX vendors be a
possibility?
> Sun / SGI / HP or something? I'm thinking that getting away from any
> kind of Intel CPU would be a good place to start, plus of course you
> don't need any kind of framebuffer then either (unlike a PC) and can
> just use a serial console on the (very rare) occassions when you'd
need
> to be physically at the machine.
>
> Cut memory to bare minimum too as that's probably a major culprit of
> current draw.
>
> If the machine's not doing any logging to local disk then you can
> eliminate the hard drive too
I disagree with a few points there. Firstly, SpamAssassin is very
resource-hungry. It works best with a fair amount of memory. It also
tends to be very slow - I've seen it take 4-10 seconds *per message* on
a slow machine. That might not matter on a machine handling a very
small amount of mail, of course.
Then you can't really have your incoming-mail handler run diskless,
because if you do, something else will have to run 24/7 to store the
mail. Better to have just one machine. But find a modern slow drive
rather than an old slow drive; slow drives use less power than fast
ones, but modern ones use less than older ones. Laptop drives are
often pretty low-power.
However, many of the Sun/SGI/HP type of machine might run more quietly
since they don't need big fans for CPU and PSU. They also don't need a
framebuffer as Jules said, *and* no keyboard. But they will tend to be
slow, and you'll have fun trying to doing all the IP masquerading
firewally stuff on anything but Linux or BSD, which is going to be more
trouble than it's worth on most of the above.
FWIW, I think Tim's suggestion (mini-ITX) is amongst the best.
--
Pete Peter Turnbull
Network Manager
University of York
Tony wrote:
> Interesting, the LSB is being lost somewhere (that would explain why
> 1 does nothing, why 5 behaves as 4, etc).
>
> What sort of RAM is on this board (I can't be bothered to find the
> prints tonight ;-)), do you know if it's good. I've found old SRAM
> to be notoriously unreliable.
Interesting, I had not thought of that, may be a stuck bit.
I must have a better look at the program code listing. Checking out
the RAM is a bit difficult. It consists of two 4-bit chips with
separate data IN and data OUT pins, type 86586 (?).
If the 8008 uses the RAM for storage of variables, I guess that I can
safely say that the RAM (plus associated circuitry to read/write) must
be OK.
> Since I have a logic analyser 'to hand', I would start looking at those
> 3 inputs to the '47. Where do they come from on the M7859? An output
> port on the 8008? Do we know that port is latching correctly? Or more
> likely, the 8008 is writing the wrong values to it.
Page KY-4 has all the decode logic. There is a second post to this list
on its way, posted Friday morning ... it's now Sunday morning ...
The signal KY4 READ INPUT 5L from the 74154 is used on page KY-3 to
enable 8093 AND gates to read the scan matrix lines.
The signal KY4 LD REG 0H via a 7404 from the 74154 is used on page KY-6
to enable a 74175 latch of which the outputs drive the scan matrix.
Likewise, KY4 LD REG 1H drives the 3 NUM lines for the 7447.
Before I go on writing long stories here, I think it is best to wait
for the e-mail from last Friday to appear here.
Thanks for working with me Tony, it helps keeping focussed ...
- Henk, PA8PDP.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
>
>Subject: Re: FPGA VAX update, now DIY TTL computers
> From: woodelf <bfranchuk at jetnet.ab.ca>
> Date: Fri, 04 Nov 2005 10:19:25 -0700
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Allison wrote:
>
>>There is also the matter of fault tolerence. Parity doen't provide that
>>unless the OS can map out the offending bank and the offending bank
>>isn't in a critical location. ECC can keep you going if you have a
>>stuck bit but it's up to the user/maintence to fix asap.
>>
>>
>>
>But does any software even consider being able to be rolled back from a
>check point nowdays?
>With a well designed virtual memory system ( no gui stuff I guess ) a
>process that takes several
>days? or more to process needs to interuptable and saveable.
I think VMS and a few of the real OSs do but PCs nah.
Allison
I won this disk in an auction:
"IBM Personal Computer Hardware Reference Library | Diagnostics | v2.02"
...only to find that it had been reformatted and filled with someone's Turbo C
homework assignments (argh!). Does anyone have this diskette image available
for download? I'd like to restore it to the original diskette to make it whole
again.
--
Jim Leonard (trixter at oldskool.org) http://www.oldskool.org/
Want to help an ambitious games project? http://www.mobygames.com/
Or check out some trippy MindCandy at http://www.mindcandydvd.com/
Tony wrote:
> This suggests it is correctly counting the digits you enter (or shifting
> them into a register), but is not displaying them correctly. And it is
> only updating the bottom 8 bits.
> As you probably know, the console is controlled by an 8008
> microprocessor. Of course it's an 8 bit device. Maybe some 'carry' is not
> working correctly.
>
> What does it do if you press 4 repeatedly? Does it flash the bottom 3 or
> bottom 2 digits? If it's only updating the bottom 8 bits, you see, then
> only 2 digits will flash from 0.
Indeed, pressing the "4" only flashes the last two digits!
How did you know that ?!
Anyway, here are the results of this evening. I write down everything,
so you can read the good and the bad things I found ...
First the BA11K box configuration.
slot position board(s)
--------------------------------
1 A - F M8266
2 A - F M8265
3 C - D G7273
4 A-B C-F M9312,M7859
5 C - D G7273
6 C - D G7273
7 C - D G7273
8 C - D G7273
9 A-B C-D M9302,G7273
Next, the response on the display from the keypad. I always
started with pressing "CLR", then repeatedly the same key.
The rightmost (lsb) display is called "A", the one next to it
is called "B", the leftmost (msb) display is called "F".
button display reaction (1st time, 2nd, 3rd, etc)
--------------------------------------------------------
0 nothing to see
1 nothing to see
2 A , B , C , C , C, etc.
3 A , B , C , C , C, etc.
4 A , B , B , B , B, etc. (as Tony predicted!)
5 A , B , B , B , B, etc.
6 A , B , C , C , C, etc.
7 nothing to see
LSR SR DISP LED goes on
The LAD, DIS AD, EXAM, and DEP keys seems to give no response.
However, if I pressed LSR, and the SR DISP LED is on, pressing
any key will turn of that LED. Even the CNTRL key ...!
The printset was my lead, so I started from the beginning: the
flat cable from the console to the M7859 module.
All 20 wires check out OK, so one problem source eliminated.
3rd page of the printset.
I checked the +5V and GND faston, and measured a clean 5.15 V.
4th page of the printset.
Here are all keypad switches and the console LEDs connected to
the flat cable. The switches are grouped connected to NAND
gates (8881), and 4 gates are stobed by a signal "READ x H",
where "x" is 1,2,3,4,5. They form a scanned matrix as follows:
signal | J1 #6 J1 #7 J1 #8 J1 #9
---------+---------------------------------------
READ 1 H | START BOOT CONT HLT/SS
READ 2 H | CNTRL 3 6 DEP
READ 3 H | INIT 2 5 EXAM
READ 4 H | 0 1 4 7
READ 5 H | CLR LSR LAD DIS AD
The "READ x H" signal is derived from the pins 18 (READ 1 H) thru
pin 13 (READ 5 H) on connector J1, via 7404 inverters, and they
all have the following wave form:
<---- 22 msec ---->
_____ _____________________
| | |
| | |
|____| |__
--> <---
4 ms
I didn't check the timing relation between the "READ x H" signals.
The signals on the combined output of the 8881's have the following
wave form:
[1] [2] [3] [4] [5]
________ __ __ __ __ __________
| | | | | | | | | |
| | | | | | | | | |
|_____| |_____| |_____| |_____| |_____|
The number between the square brackets indicates the "READ x H"
signal. So when "BOOT" is pressed the low signal during the time
interval [1] goes logic high. Likewise, when I press the EXAM key
time interval [3] goes logic high.
So, keypad scanning looks OK to me, as the X-Y matrix works fine.
5th page of the printset.
Pin 19 of the connector J1 carries 5,04 V. That's OK.
This page shows the six 7-segment displays with the 7447 decoder,
the mentioned 7404 inverters for the scanning matrix signal, and
the "DRIVE xL" which are also derived from connector J1, pins 18
thru 13, via a buffer 7417.
Since "READ x H" is OK, I assume that "DRIVE x L" is also OK ...
it must be, otherwise the six 7-segment displays would not be lit !
Last 3 signals are the display values (3-bit) to the 7447 input
A, B, and C. On connector J1 pins 12, 11, and 10 respectively.
As always, the last thing to check should have been the first!
These 3 signals are continously 0 V. That explains why the display
always shows "000000". I can see a short positive pulse when a key
of the keypad is pressed.
This leads me to the following (early) conclusions.
1) the keypad is scanned. All "X" signals of the matrix (READ x H)
are OK, and all "Y" signals of the matrix (the 8881 outputs) are
all valid, and give the correct information when a key is pressed.
2) When a key is pressed it is momentarily shown on the display, but
then the value returns to all zero. I can not see the value, so
it could be any garbage ...
6th page of the printset.
This shows the component layout of the M7859 module.
Noteworthy is the connector J1, top left. This is the pinning when
viewed at the component side of the module:
________________________________________
| #19 . . . . . . . . #1 card edge
| #20 . . . . . . . . #2
|
|
card edge
Further, from the diagrams (up till now) I see the the following
pins on J1 (console) are connected to these pins on J1 (M7859).
J1 ---> J1
(console) (M7859)
-------------------------------------------------
20 A GND
19 B +5V
18 C SCAN 1 L (READ/DRIVE 1)
17 D SCAN 2 L (READ/DRIVE 2)
16 E SCAN 3 L (READ/DRIVE 3)
15 F SCAN 4 L (READ/DRIVE 4)
14 H SCAN 5 L (READ/DRIVE 5)
13 J SCAN 6 L (READ/DRIVE 6)
12 K NUM 1 H (A input 7447)
11 L NUM 2 H (B input 7447)
10 M NUM 3 H (C input 7447)
Tomorrow I will dive into the diagram of the M7859 ...
Any hints or comments on this scribbling are welcome !
- Henk.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
Hi George
My Name is Glen Graham
I am also looking for a copy of 10391B Inverse Assembler Files
Did you ever do any good finding a copy?
I you did can you please pass on the information.
I have included a copy of files that you may be interested in
Operating system files for
2/ HP1650B
3/ HP1660A
4/ HP16500B
5/ HP16500C
6/ LIF Utility Software (very handy) use this program in DOS to convert the
files into LIF format
This is the format that the equipment uses except the 16500B/C units they
use DOS files
To load software into 16500B/C use these instructions
Double-click the executable file and unzip the contents to a
folder on your hard drive.
1. You will need five blank floppy disks to complete this step. Label
the floppies 1, 2, 3, 4, and PVTEST. In Windows Explorer, copy the contents
of the DISK1 folder to the disk labeled 1. Repeat for the remaining folders.
Note that it is not necessary to copy the DEMO folder in the 16500C file set
to the 16500C for proper operation.
2. Boot your 16500B/C from Disk 1 (insert the disk into the floppy
drive and turn on the power).
3. Copy all the files from Disk 1 and the rest of the disks you
created into the logic analyzer's \SYSTEM directory. To do this, start in
the System window, click Configuration, and select Flexible Disk. Then enter
the command Copy file: *.* type: DOS to: \SYSTEM on: Hard Disk and click
Execute. Click Continue if you are prompted to overwrite any files.
4. Remove the last floppy disk from the drive and cycle power on the
16500B/C. The analyzer will now boot from the new operating system files you
just copied.
Hi folks,
I have recently got a HP 7978 9-track tape drive with HPIB (IEEE 488,
GPIB) interface.
Now I'm looking for documentation. Does anybody have documentation for
that drive? Would be glad to hear from your....Thanks.
Any experience with interfacing these monsters to modern PCs?? I think
of writing a linux driver for it......
Best regards,
Philipp :-)
>
>Subject: Re: RX01 felt pad (Tim)
> From: David Gesswein <djg at drs-c4i.com>
> Date: Tue, 25 Oct 2005 18:22:26 -0400
> To: cctalk at classiccmp.org
>
> I just took apart my RX02 to clean them since they were getting
>flakey. On a previous drive I just went to a craft store and bought the
>closest material I could find, cut it to a small dot to fit in the
>cup. Put a drop of glue in the cup and push the material in.
>
>To get the drive out for access.
>1) Remove from outer shell if you have the desktop unit. The top cover
>comes off with obvious screws then ones along the side free the internal
>unit.
>2) Disconnect the cables to the controller board and motor power connector
>on the back of the drive hidden by the air baffle.
>3) Remove drive from rest of assembly. 2 screws through the air baffle
>at the back and 4 from the top down. If you tilt the upper board up
>on the hinge they are accesible through holes in the lower PCB.
>
>That should free the drive. You can then lift up the little presure arm
>to easly get at the pad.
>
>I don't have any real RX01's so they might be slightly different for
>disassembly.
RX01 drives and RX02 drives are the same. Only the logic differs.
Allison
LC[x] and Classic both use the SuperDrive/3.5HD floppy mechanism, Lisa 3.5" uses the SSDD Apple 400k (hacked up from the standard 360k so Apple wouldn't have to redo the ROMs when they dropped Twiggy). a 800k external drive can be plugged into the classic, possibly (other compact Macs take it, as does the IIcx/ci), or a non-FDHD SE, original II, or <= Mac Plus machine come standard with 800k (or 400k) drives.
Reminder for people who don't work with Macs much - stuff gets written to disk (When a System 6 disk is put in a System 7 Mac, the desktop file is immediately recreated) without the explicit intervention of the operator. If this is done on a SuperDrive Mac, and the disk is then put back in a 400/800k Mac, it won't be able to read/mount the disk. Write protect all 800k floppies if you use them in a 1.4 MB Mac.
With the sad passing of Don S last year, one of the founders of the
Wisconsin Computer Society in the 70's, his window finds she must finally
begin the process of disposing of a basement full of stuff. Don was a
life-long experimenter and user of computing equipment which has mostly
found its way into the classification of "classic." Don and I
used/programmed DEC PDP-11 and Altos CP/M and MP/M machines together at
more than one job.
Here's a list of items that must go. Ideally, a small number of people
would take this collection, so as to not divide it all up and make
shipping/pickup complicated. If the person who wants the Altos computer
wants the disks, I will probably fish out all the Altos, MP/M and
application (not the Milenium Systems disks) and bundle that with the
computer.
The drive cabinet can go separately. Anything I suspect is DEC-related can
go separately. The Millenium stuff is probably a separate item as well,
unless someone wants all of it. If there's no interest in this collection
as large units, it will go in smaller chunks to whomever wants it.
She's not looking for money for this material, but can't bear any costs, so
S&H is on you, plus some $$ for packing materials. Local pickup would be
much, much better.
Estate of Don S.
Photos are available for a few items: http://my.athenet.net/~uuhhuu/altos/
Content listing based solely on written or printed labels, may be
inaccurate, no further information (e.g. version numbers) is
available. ?Assy? = Assembler
Hardware: http://my.athenet.net/~uuhhuu/altos
Altos Z80 based computer, CP/M, MP/M or ?, 208k memory, dual 8? Floppy,
serial, parallel, etc.
Second Altos cabinet, dual Shugart 801 floppy drives, fan, and power supply
only. No motherboard. Was used in a rack for DEC drives.
Manuals
Manual, Shugart 1610-4 Intelligent Disk Drive Controller
MP/M II Programmer?s Guide (photo)
MP/M II User?s Guide (photo)
MP/M II System Guide (photo)
Digital Research CP/Net Network Reference Manual (photo)
Link-80 Operator?s Guide
Digital (DEC) Logic Handbook 1970
Manual: Adaptec ACB-4000 Series Disk Controller
Eight-Inch Floppy disks on East wall shelves
Utilities (shareware)
dBase II
Ashton-Tate ZIP
CP/M modem programs
PL1 BASIC 80
Supercalc V1.12
9250 Diagnostic
LK Link Parsing Util
Turbo Tutor
Pascal MT+
MP/M 1.14 (Millenium Systems)
Wordstar (Millenium Systems)
Z80 assembler (Millenium Systems)
MP/M 1.16 (Millenium Systems)
MP/M 1.16 + Wordstar 2.10 + MSI Utils (Millenium Systems)
6809 Assy + 8048 Assy + Z8000 Assy + MSI util (Millenium Systems)
Z80 Assembly (Millenium Systems)
Convert.com + Convert.prl (Millenium Systems)
9516 software release (Millenium Systems)
9520 demo programs (Millenium Systems)
9520 diagnostic (Millenium Systems)
Pascal Mt+ (Millenium Systems)
CP/M (Millenium Systems)
Wordstar ver 3.0
Wordstar 950 (possibly for Televideo 950?)
CP/M (Millenium Systems)
ZAS.COM + ZLK.COM + Z8TINS (Millenium Systems)
6800/6802 Assy (Millenium Systems)
UCSD PASCAL
SA 120-1 Alignment Diskette (Shugart?)
Utils
Wordstar 3.0 + Mailmerge + Spellstar
Supercalc
ISIS V4.2 System
TCS Accounting (9 disks)
Adventure
Eight-Inch Floppy Disks on North Wall Shelves
Altos Diagnostic (2 disks)
MP/M (Altos)
CP/M 2.02
Box of approx 80 disks, some RX01, some CP/M or MP/M, e.g. games, utils,
Zork, JRT Pascal, etc.
Box of approx 40 disks, mostly CP/M MP/M, e.g. dBase II, Modem 7, BDS C
1.44, user group software, terminal programs, terminal programs, ALGOL,
FORTH, BASIC, Fortran, Tiny C, Mp/M, Dazzler, PALASM
Osbourn Accounting
CP/M 2.24
DEC disks, probably RX01: TECO etc (black cardboard box)
CP/M + Wordstar
Altos
CP/M 2.24
Turbo for Altos
dBase II
Altos Diagnostic Executive 1.10 (original disk! pink box)
RT-11 boot disk (DEC)
Pascal
CP/M-86
Wordstar-86
Mailmerge-86
Spellstar-86
Jade Computer Products Double-D Disk Controller CP/M 2.2
[Love] Men like to pursue an elusive woman, like a cake of wet soap
in a bathtub - even men who hate baths. --Gelett Burgess (1866-1951)
--... ...-- -.. . -. ----. --.- --.- -...
tpeters at nospam.mixcom.com (remove "nospam") N9QQB (amateur radio)
"HEY YOU" (loud shouting) WEB ADDRESS http//www.mixweb.com/tpeters
43? 7' 17.2" N by 88? 6' 28.9" W, Elevation 815', Grid Square EN53wc
WAN/LAN/Telcom Analyst, Tech Writer, MCP, CCNA, Registered Linux User 385531
Hello Spike,
I found your beautiful schematics from the TI59 several years ago on the
Internet. I would aks you to send me a link or a copy of this page.
It would be very useful for me.
Thank you very much in advance
Christof from Austria
--
Highspeed-Freiheit. Bei GMX superg?nstig, z.B. GMX DSL_Cityflat,
DSL-Flatrate f?r nur 4,99 Euro/Monat* http://www.gmx.net/de/go/dsl
>
>Subject: Re: FPGA VAX update
> From: "Dwight K. Elvey" <dwight at ca2h0430.amd.com>
> Date: Wed, 02 Nov 2005 15:56:32 -0800 (PST)
> To: cctalk at classiccmp.org
>
>>From: "Allison" <ajp166 at bellatlantic.net>
>---snip---
>>>Depending on how much 'from scratch' people feel is necessary, it's also
>interesting to roll your own computer using an off-the-shelf processor (or
>multiples). I have a simple 8088-based SBC design wired up and waiting for
>motivation to put together some test firmware. The main thing that has kept me
>from bringing it up is the difficulty in getting x86-based machine language
>development tools going. I'm used to little 4 and 8-bit assemblers where you
>can plop down a few ORG statements and have it all resident in a ROM, and almost
>all the x86 asm tools start from the assumption you are running on DOS and have
>no direct control of the memory map.
Not from me, you misquoted.
However I also have built using:
8008,8080,8085,8088,80C188
8048/9,8051
Z80, Z180, Z280, Z8000,
6800, 6809,
6502,65C02
1802
SC/MP (8a-500 8a600)
TI9900,
T11 (pdp-11),
2900 bitslice, raw TTL
And a assortment of NEC single chips (uCom4, uCOM8)
One addball I'm considering is taking an 8749 and programming it to emulate
another processor. With it's IO and internal eprom it's possible to treat
it as a microprogrammed system to emulate other hardware. Speed would be
low but for example emulating an 8008 (20uS instruction time) should be
near real time using an 11mhz 8749. Of course the goal could be to emulate
something else or create a new thing.
>Hi
> Of course you could learn Forth and use a program called TCOM
>that runs under FPC. Both are in the public domain.
Never played much with FORTH, may have to change that.
Allison
As someone who has worked on TV's since the 1960's, and who worked as an
engineer in TV stations for many years, I think you are being paranoid and
getting far too worked up over nothing.
Connect an alligator clip from the metal blade of a (normal) screwdriver
(with a plastic handle) to ground (normally, chassis ground is also grounded
to the aquadag conductive coating on the outside of the CRT). Stick the
blade under the 2nd anode cap and touch the actual 2nd anode connector.
Yes, use only one hand. There may or may not be a spark, which you may or
may not hear. Leave it connected for a second or two, wait a second or two
and do it again or even 2 more times.
If you want to use a resistor in series with the ground lead, fine, I rarely
do and have never damaged anything (and many of the CRTs I've worked on are
a lot bigger and have a lot more voltage than any monochrome computer
monitor), but it's not a bad idea. However, don't go overboard on the value
of the resistor. You do not want "tens or hundreds of megohms", it would
take too long to discharge the voltage. There is only about 10,000 volts or
so on a 9" to 12" monochrome CRT (compared to more like 30,000 volts on a
large screen color CRT), so a one megohm resistor will limit the current to
10 ma. If you do use a resistor, always do a final discharge without a
resistor.
Also, if the unit has not been powered up in weeks or months, there probably
isn't anything there to begin with, although this would depend on the design
and components of the individual unit in question.
I have finally gotten around to scanning my manuals for my VAX 11/750.
However, the web hosting company for my domain has low disk space limits
compared to the size of the scanned manuals. Is there somewhere that I
can put the scanned manuals where people can get to them?
Also, I have been using manx to determine what manuals need to be
scanned. Are the references to online docs on manx complete as far as
what manuals are available online?
alan
>From: "Chuck Guzis" <cclist at sydex.com>
---snip---
>
>I've always thought that 24 bits is a nice word size for a small computer.
>Divisible by 2, 3, 4, 6, 8 and 12 bits. An instruction could use 6 bits
>for opcode and 3 register addresses out of a 64 register file...
Hi
My thought is to make a variable word length processor using
a single bit ALU. Of course, I've been thinking in terms of a relay
based machine.
Dwight
Hello all,
For many reasons, which I don't care to detail, I'm getting out of the
"business" of vintage computing (In fact, I'm no longer subscribed, so don't
reply to the list, because I won't get it). 95% of my collection has been
sold, given away, or dumped, and I only have a few more items, plus the
components listed below.
I am offering these components to the best offer, plus shipping from MA, USA,
Zip Code 01473. I *strongly* prefer PayPal, but will take USPS Money Order
(*no other payment methods, please*).
These components have been stored cool and dry, but are untested. Also, many
of them have *not* been stored in anti-stat drawers, so please keep that in
mind. I will ship on anti-stat foam if posible, or wrapped in foil if I am
unable to put them in anti-stat foam. Vast majority of date codes are in the
late 70' to early 80's. I'm not sure what a lot of these even do, and I
don't have datasheets, so you're on your own identifying them :-)
I'll keep the bidding open until 10/31, midnight, my time.
If you are interested, please contact me *off-list*
(richard.beaudry at gmail.com) with offers, and let me know your ZIP or country,
so I can estimate shipping. I will let the final list of people know on 11/1
(or thereabouts) by email what they can get.
Part 2 will be listed in a week or two, when I finish cataloging it...
Here's the list:
Qty. Item.
6 HP 5082-7340 Hexadecimal Display
8 TI TIL311 Display
2 7812 TO-220 CASE
6 LM-317T TO-220 CASE
5 UA741CP (TI) 8-PIN DIP
68 UA7912UC TO-220 CASE
14 UA78H05SC TO-3 CASE
12 UA78H12ASC TO-3 CASE
20 VH248 FULL-WAVE BRIDGE RECTIFIER
76 TL780-05CKC TO-220 (HIGH-CURRENT 5V REG., I THINK)
10 1A 250V FAST-BLOW 3AG FUSE
6 40-PIN Augat Socket (white plastic, gold machined-pin) labeled
"Microprocessor Carrier"
28 18-pin Augat machined-pin wire wrap socket
4 40-pin Augat machined-pin wire wrap socket
9 28-pin Augat machined-pin wire wrap socket
34 18-pin Augat machined-pin wire wrap socket
4 16-pin single-row header, wire-wrap tail
35 30-pin dual-row header (15-pins per row), solder-tail
11 spst momentary push-button switches (6 black, 5 red), button dia. 1/4"
25 spdt mini-toggle switches, 3A 125VAC, 3/8" toggle length
45 spdt toggle switches, marked with both 2A 250VAC and 5A 120VAC, C&K UII,
7/16" toggle length
1 AD7506SD
2 AD521JD
4 DAC 888 FX
2 DAC 08 BC
1 DAC 0800 LCN
4 AI-2625-5
15 UGN3203
24 ULN2004A
11 ULN2068B
73 AM26LS31PC
71 AM26LS33PC
11 N82S103N (some late 70's date codes)
19 1489 RS-232 (mixed vendors)
41 1488 RS-232 (mixed vendors)
7 N8T95
1 N8X320N
4 N8T97N
12 N8T32N
1 TRW 08HUJ5C
39 TRW TDC-1006J
9 SAA1027
8 MC10H166P
4 TCM29C13J
25 N8T30N
1 WD2010B-PL
1 SMC FDC 1795
1 SAB 1797-02P
1 WD8250CL-20
1 WD10C20B-PH
1 WD1100-CE
1 WD1010PL-05
1 WD1015-PL
1 Adaptec AIC-100
1 Adaptec AIC-250
4 AY-3-8910A
2 ISD 1000AP ('93-'94 date) voice recorder IC
3 N8S100N
9 MM58167AN
25 N82S129N
2 UM8397
2 2122CN (logo looks like "XR")
3 2120CP (same "XR" looking logo)
6 AMD AM9264DPC
1 Rockwell (?) 10464-13
1 SC87C51 CGN40
1 NCR 90C98
1 VTI VL82C50-PC
1 Intel p82586
1 HM82C11C
2 AY-5-1013A UART
1 R68561P
1 COM9026BI
1 R2121A-01
2 8153C (logo looks like "EA")
2 8151C (again, "EA" logo)
1 Intel P89027
1 TLC 32040CN
2 N9403N
1 N8X305I
6 N8X300I
1 Intel 8288
1 Intel 8284
2 LM311N
7 9643TC
6 MC10H161P
3 DG201ACJ
4 MM5280N
2 MCM6164C55
1 Analog Devices ADLH0033G (circular can, 12-pin)
1 LM319N
1 LM101AD
1 XEBEC 104648D
8 Intel P5101L-1
5 NEC marked D780C-1
3 unused PAL16L8A-2CN
10 MC14050BCP
1 VH048 Bridge Rectifier
6 VH448 Bridge Rectifier
1 VARO IN4436, TO-3 case w/ what looks like a heat sink
Thanks,
Rich B.
>
>Subject: Re: FPGA VAX update, now DIY TTL computers
> From: Paul Koning <pkoning at equallogic.com>
> Date: Fri, 04 Nov 2005 10:09:17 -0500
> To: cctalk at classiccmp.org
>
>>>>>> "Kevin" == Kevin Handy <kth at srv.net> writes:
>
> Kevin> Allison wrote:
> >> If you ask me the real horror of parity memory is it only tells
> >> you disaster
> >> happend just as your about to crash. ...
>
> Kevin> Parity depends on if you would prefer a crash to silently
> Kevin> generating incorrect results.
>
> Kevin> ECC tries to hide the errors, but can still cause a crash if
> Kevin> too many bits change.
>
>Correct. And all error checking codes will fail to detect certain
>errors.
>
>Which is the right answer depends on what kind of errors you consider
>likely enough to worry about, and what recovery you require.
>
> paul
There is also the matter of fault tolerence. Parity doen't provide that
unless the OS can map out the offending bank and the offending bank
isn't in a critical location. ECC can keep you going if you have a
stuck bit but it's up to the user/maintence to fix asap.
Allison
I've been playing classical piano for quite a few years and started
taking lessons about 15 years ago from someone who was good. We became
friends as well, and I'd still be taking lessons if she hadn't died 5
years ago (89 years old.) It would be nice to have the time to learn to
sight read :).
On 11/3/2005 at 9:13 PM Fred Cisin wrote:
>I stopped playing the tuba 40 years ago.
>My hearing is way too bad to subject anybody to listening to it.
I took up the tuba in 1997, being a nearsighted piano player since I was
a
kid. My wife encouraged me to take up an instrument that I could be
more
"sociable" with.
I'm still nearsighted, but since then, I've also learned double bass and
am
setting my sights on learning viola this year. Just another noise to
torment the dogs...
Are musically-minded people still as commonplace in the computer
business
as they once were?
Cheers,
Chuck
>
>Subject: Re: TEAC FD-55GFR = Quad Density?
> From: Fred Cisin <cisin at xenosoft.com>
> Date: Fri, 07 Oct 2005 16:34:17 -0700 (PDT)
> To: "General Discussion: On-Topic and Off-Topic Posts" <cctalk at classiccmp.org>
>BOTH.
>The 55F is "720K" only; 55G and GFR are 1.2M.
>The 55GFR is a reliable and versatile drive.
FD55A single sided 48tpi 300rpm
FD55B Two sided 48tpi 300 rpm
FD55E single sided 96tpi 300rpm
FD55F two sided 96tpi 300rpm
FD55G two sides 96tpi 300/360rpm
>It is not so good with hard-sectored, or NO-index reading.
Works great with NS* hard sector controller at 300rpm.
>The difference between 1.2M and "720K", sometimes called "QUAD density" by
>the marketing people, are 360 v 300 RPM, 250K v 500K sata transfer rate,
>and different current levels at the heads (controlleable on the
>interface). They are both 96TPI.
QD is for those systems that DD was 360k (48tpi). QD system could be 720k,
780k(amproLB).
>To do "quad" in an "HD" drive requires stepping at 96TPI, but the data
>transfer rate, and current levels at "360K" levels.
Or the common QD systems I have the data rate is same as DD (still 300rpm)
but there are twice as many tracks or quad. 5.25 floppies started at 80k
(sa400 single density one side 40 tracks (48tpi) all the way to near 800k
(FD55F, DD, two sides 96tpi). There were enough marketing names to the
capacity jumps to confuse even the marketers. however once the data rates
hit DD there were SSDD(160K raw), DSDD(400k raw) and then DSQD(800k raw)
and there was even a SSQD(400K raw) (yep 96tpi DD data rate and only one side).
that last one was know widely as RX50 and also appeared using FD55E on
Visual 1050. There was the 1.2mb PC thing.
This is why 5.25 floppy was so much confusion as it morphed from the 35 track
SA400 through the FD55GFR.
There there were the formats applied.. [open can, worms!, run!]
Allison
>
>Subject: Re: FPGA VAX update, now DIY TTL computers
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Thu, 03 Nov 2005 15:22:03 -0800
> To: cctalk at classiccmp.org
>
>On 11/3/2005 at 7:53 PM ard at p850ug1.demon.co.uk wrote:
>
>>There was a hrrible thing called fake parity memory. It stored 8 bits and
>>calaculted the parity bit on a read (ignored the incoming parity bit on a
>>write) to keep the memory controller happy. Of course you can't store 9
>>bits in that type of device.
>
>Of course you can, as long as the bits you're storing agree with the parity
>of the 8 bits...
>
>:)
If you ask me the real horror of parity memory is it only tells you disaster
happend just as your about to crash. It offers little to system reliability
and data integrity that real ECC can provide. Like Tim O' said years ago
it's all a plot to sell more ram.
Allison
Currently looking for 3-D Display System & Game Tool (by Bill Budge) which
also had an Atari version (by Paul Lutus). The Atari version may have
also been called Atari SuperGraphics.
Anyone have it? Contact me ASAP (directly via e-mail). I need it soon :)
Thanks!
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
>
>Subject: Re: FPGA VAX update
> From: woodelf <bfranchuk at jetnet.ab.ca>
> Date: Wed, 02 Nov 2005 13:24:07 -0700
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Allison wrote:
>
>>Ego a 16bit machine September 1985. There was another article whose
>>focus was microprogramming vs sequential machine control and that used
>>the TOY1 archetecture. There were others described in TCJ Dave Brooks
>>simplex III comes to mind. There are others.
>>
>>
>>
>Toy I had forgotton.
>Since TJC is now defunct are there any on-line copies of it I have read
>the simplex web site.
Dave Brooks has the simplex story on his site (along with the P112).
There is also a web ring for homebrew CPUs, quite a bit of diversity
out there but PDP-8 is common along with minimalist machines for teaching.
However the most interesting is the Block 1 AGC (apollo guidence computer).
Allison
Hi all,
I don't know why, but my mails seem to delay at least 30 hours before
they appear on the list. I have sent an update on my troubleshooting
findings and a reply on Julian's e-mail about the Flip Chips, *all*
yesterday (writing this e-mail Friday morning ...).
Anyway, here are my new findings, and conslusions.
On diagram KY-4, I checked the address decoder E34, and the 74154.
As expected, the outputs KY4 LD REG 0H and KY4 LD REG 1H are active
(otherwise keypad scanning and the display would not work at all).
The address decoder also puts out select signals to the RAM and
the 'KY ROM 2 EN L'. At first, I did not see any pulses on the output
'KY4 ROM 1 EN L', and I thought "AHA"! Too early, but that's OK!
I grabbed the 8008 code source listing and checked. ROM 2, E33/E39
on page KY-2 are almost continuously addressed, because the monitor
program loop sits in these 2 ROMs (address range 000-777 octal).
Checking the listing, I see that the first code in ROM 1, E3/E21,
is the processing of the LSR button, and the code comment actually
says "turn on SR DISP". When I press the LSR button, both ROM 1's
are addressed.
My conclusion is that all 4 ROMs are OK, as is the address decoder
(which is also a ROM) and the 74154 (all with the associated logic).
On page KY-1, the 8008 state output lines, S0, S1, and S2, go to
a 7442 decoder. The documentation explains the decoded states, and
mentions that pin 2 of the 7442 ('KY1 STOP L') is asserted when the
8008 crashes (in fact, when the 8008 executes a HALT instruction,
which is octal 0, or 1, or 377). When STOP L is activated, the 8008
will restart itself. I scoped pin 2, and can say that 'STOP L' is
never asserted.
That means that the 8008 is continuously executing its program,
without any restarts. The clock signal at TP1 is a nice square wave
with a duty cycle of approx 50%, cycle time a bit more than 1 uSec.
>From the above I conclude that more parts are functioning correctly:
- the 8008 CPU + clock and power-up/restart logic
- the transceivers E16/E17 that buffer the multiplexed addr/data bus
- the 2 RAMs (E11/E27)
- the 4 ROMs (E3/E21/E33/E39)
- the address latches (E5/E4) because they buffer the ROM addresses
- address decoder ROM (E34)
- "register" selector 74154 (E48)
It is time to find out why only the 3 lsb displays flicker brief
when I press a button, and why the msb 3 displays do not react at all.
I also saw that sometimes the RUN LED is turned on.
Pressing the CNTRL (only that button!) the BUS ERR LED goes on (???).
Normally CNTRL must be used in conjunction with another button ...
Pressing CLR makes BUS ERR turn off.
Also, I noted that at some point the display showed "666666", but I
can not change the value. For now, I am not too worried about this.
I contribute this behaviour to the less-than-perfect contacts, now
that the M7859 is on top op 2 dual width extender boards (so that I
can probe pins of the ICs on the M7859).
Again, any comments or hints are highly appreciated!
- Henk, PA8PDP.
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.
>
>Subject: Re: That darn Intel jingle...
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Thu, 03 Nov 2005 17:11:30 -0800
> To: cctalk at classiccmp.org
>
>On 11/3/2005 at 8:01 PM Allison wrote:
>
>>8274 is the intel branded NEC D7201, and it's not essentually a Z80 sio
>>it's IS a SIO save for it supports 8080/8085/8088 interrutpts instead.
>>Even the register addresses and functions are the same save those for
>>the interrupts.
>
>Someone once told me (could be urban legend) that the same guy designed
>both chips--once for Zilong and then for Intel..
>
>Cheers,
>Chuck
Definately urban legend. If only because it was licensed to Intel from
NEC who designed it. Early intel 8272s were old NEC mask. I even cleaved
an early Intel marked ceramic part for a customer to prove it. The design
came from NEC Japan.
Stuff you learn by being there.
Allison
>
>Subject: Re: That darn Intel jingle...
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Thu, 03 Nov 2005 15:32:44 -0800
> To: cctalk at classiccmp.org
>
>On 11/3/2005 at 6:22 PM ard at p850ug1.demon.co.uk wrote:
>
>>The worst, by far, has to tbe the 8255 parallel chip. That was clearly
>>designed by soembody who didn't think what he was doing. For those of you
>>who've not read the data sheets, any write to the mode control register
>>clears all output port lines to 0.
>
>For what it is and WHEN it was developed, the 8255 is a pretty good device.
> There are still new products made that use it (very popular in the data
>acquisition area). I can't think of any other single parallel interface
>chip from the 70's that's still puffing along.
Z80 PIO.
However the 8255 is of the 8080/8085/z80/ and general Intel lineup and
due to that also the most widely multiply sourced. It's ugly but what
comes in to do better?
>I wish the thing was faster. The NEC 82C55AC variant is good to 10 Mhz,
>but that's pretty slow when you're talking about a PCI bus.
D72055 the last version of the part hit 12mhz. If your going on PCI
why bother and just put a gate array to work.
>There are precious few of the really good peripheral chips from the early
>days of the microprocessor that are still as useful. The Signetics 2651
>USART, maybe?
Well there are plenty of 8251, 8253, 8259 around, then there are the 2681s
and (gag) 8250 series.
Not many but then what do you need after lots of ram?
Allison
>
>Subject: Re: That darn Intel jingle...
> From: "Chuck Guzis" <cclist at sydex.com>
> Date: Thu, 03 Nov 2005 16:17:54 -0800
> To: cctalk at classiccmp.org
>
>On 11/3/2005 at 6:45 PM Allison wrote:
>
>>Z80 PIO.
>
>16 measily bits of I/O in a 40 pin package. :( What a waste of real
>estate.
But long lived.
>>D72055 the last version of the part hit 12mhz. If your going on PCI
>>why bother and just put a gate array to work
>
>Mostly laziness. I could probably also just buy a PCI data acquisition
>board, if I didn't want Mode 2 I/O (which I do).
I used 8155s but then again I also use 8085s which work nicely with it.
>>Well there are plenty of 8251, 8253, 8259 around, then there are the 2681s
>>and (gag) 8250 series.
>
>Well, the 8259's a CPU support chip, and I tend to think of the
>8253/54/57/37 the same way.
the 53 (timer),54(Timer), 57(DMA) and 37(better DMA) are not strongly
related to any specific CPU and work fine with Z80, 808x even 8048.
>The 51's a peripheral chip that's had its share of warts, however.
8251 is wartly enough but ok. The Leading Edge Model D XT clone used
it rather than the icky 8250.
> The 8250 is a ridiculous National product that
>can't do sync in a single-channel 40 pin package yet. The Z80 SIO and the
>Intel 8274 are essentially the same chip that should have probably been
>made part of the PC instead of the 8250.
8274 is the intel branded NEC D7201, and it's not essentually a Z80 sio
it's IS a SIO save for it supports 8080/8085/8088 interrutpts instead.
Even the register addresses and functions are the same save those for
the interrupts.
>Speaking of which--I've got a bunch of Z80 DART chips. I've been told that
>these are really derated Z80 SIO chips. Will they do synchronous I/O or
>has that part been disabled? I can't find my databook for the things any
>more.
>
>Cheers,
>Chuck
>
DART is Async only, still a good part.
Allison
> If you ask me the real horror of parity memory is it only tells
> you disaster happend just as your about to crash.
And 1/9th of the time it's a false positive.
Lee.
..
___________________________________________________________
How much free photo storage do you get? Store your holiday
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com
Folks,
While looking for the Lisa PASCAL workshop for one of my site visitors I
discovered the 7-disk floppy set for Lisa XENIX
Anybody want? It's only 1.2mb. I don't have the means of easily writing 400k
floppies so I'll not be putting it on my Lisa any time soon.....hmm...wait a
minute....I've just spotted a Mac Classic on the floor.....and an LCII.
*thinks*
Cheers
Adrian @ BinaryDinosaurs
Okay, so I FINALLY worked out my BA11-K power supply issues and got
everything sorted out and installed again.
However, I'm back to where I started when I got this thing (which I never
got past) - I turn it on, the display comes up at 173536. However, whenever
I try to EXAM anything, it displays 000000 and the BUS ERR light comes on.
I can clear, but I get that BUS ERR no matter what I do. I haven't got a
serial console connected to it yet - I got this info by going through the
11/34 diagnostics in the manual.
Here's my setup:
BA11-K box
DD11-PK backplane
UNIBUS layout:
A B C D E F
M8266 M8266 M8266 M8266 M8266 M8266 1
M8265 M8265 M8265 M8265 M8265 M8265 2
M9301 M9301 M7800 M7800 M7800 M7800 3
H222A H222A H222A H222A H222A H222A 4
blank blank blank GRANT blank blank 5
H222A H222A H222A H222A H222A H222A 6
blank blank blank GRANT blank blank 7
M7850 M7850 M7859 M7859 M7859 M7859 8
M9302 blank blank GRANT blank blank 9
I've tried switching some boards around, no help.
All grant cards are installed where you could read FLIP CHIP from the
processor side.
I have NO idea what's wrong. Is the memory possibly bad? That's the only
thing I could think of.
Any help, as always, would be much appreciated.
TIA
Julian
>
>Subject: Re: FPGA VAX update, now DIY TTL computers
> From: Sridhar Ayengar <ploopster at gmail.com>
> Date: Thu, 03 Nov 2005 11:04:58 -0500
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>woodelf wrote:
>> Chuck Guzis wrote:
>>
>>> Consider the very old Packard Bell PB250--22 bit words, fewer than 400
>>> transistors and 2500 diodes, 63 instructions. Power consumption about 40
>>> watts, exclusive of I/O:
>>>
>>> http://ed-thelen.org/comp-hist/BRL61-p.html
>>> The trick, of course, is to use bit-serial methods. It seems to me that
>>> one could greatly simplify construction of a homebrew machine that way.
>>> We're not doing this for speed, right?
>>>
>>>
>>>
>> That is interesting reading. Are there any of the large 48 bit
>> processors still around?
>> Also TTL and memory is easy to use in 4 bit sizes, a odd size like 18
>> bits is not so
>> easy to work with.
>
>How does parity memory work? Must one use the extra bit for parity or
>could one use it as a ninth data bit?
>
>Peace... Sridhar
Parity required an extra bit to stor the parity so that it could be compared
on read. That bit may or may not have been part of the data path logic.
Allison
>
>Subject: RE: FPGA VAX update, now DIY TTL computers
> From: "a.carlini at ntlworld.com" <arcarlini at iee.org>
> Date: Thu, 03 Nov 2005 19:08:04 +0000
> To: "'General Discussion: On-Topic and Off-Topic Posts'" <cctalk at classiccmp.org>
>
>Allison wrote:
>
>> Parity required an extra bit to stor the parity so that it could be
>> compared on read. That bit may or may not have been part of the data
>> path logic.
>
>But on the memory chips, that bit must have been readable for the
>system hardware to do its comparions. I guess that the memory could
>send back a GO/NO_GO signal but supplying the parity bit must
>be easier and cheaper?
Actually the system does not have to see the parity bit. Only the
result of comparing the stored (at write time) parity in the 9th bit
with the result of the read parity hardware. If there is a difference
there was a "hit". So the rest of the system gets the data and the
interrupt system sees the parity if there is a fail. There is no need
(in most if not all) to actually read and write the parity bit as that
is a memory subsystem task (hardware). PDP-11 Qbus ram is of the
case where parity is stored as a 9th bit but is not directly accessable
by the CPU.
In the extreme is the ECC ram where there are many bits per byte/word
to store a coded form of the data (hamming or other compression) so that
the ECC hardware can "repair" corrupted data.
>There was a spate of "fake parity" memory around some time in
>the 90s. Quite why it was cheaper to add a chip that always
>supplied "correct" parity rather than simply using additional
>memory was something that I never understood. But if you
>end up with one these "fake parity" memories it may well
>cause your 9-bit machine some issues!!
If it were a real 9bitter it certainly would. In the case of PCs
it was a matter of satisfying a motherboard configuration rather than
real "bits".
Allison
Hi
I have a bunch of what I believe are TTL parts.
They all have inhouse numbers that start with 55xxx.
Does anyone know what 'house' these belong to and
is there a table anywhere to translate them to
standard TTL names( a few do shouw both names ).
These seem to be someones spare parts bins. They
are all unused.
Dwight
>
>Subject: Re: FPGA VAX update
> From: Paul Koning <pkoning at equallogic.com>
> Date: Thu, 03 Nov 2005 11:40:57 -0500
> To: cctalk at classiccmp.org
>
>>>>>> "Chuck" == Chuck Guzis <cclist at sydex.com> writes:
>
> Chuck> On 11/3/2005 at 9:49 AM Paul Koning wrote:
> >> If you're going to go the 3 address route, it sounds like you're
> >> well on your way towards reinventing the CDC 6000 architecture.
> >> And of course that would be a fine thing to do -- if you're going
> >> to explore computer architectures, what better path to take than
> >> the one first walked by the foremost computer architecture genius
> >> of the 20th century?
>
> Chuck> ...or one could use a MIPS chip...
>
> Chuck> To me, the genius (and unrecognized at the time) of the 6600
> Chuck> architecture was Cray's discarding the idea of a "condition
> Chuck> code" in the IBM sense, wherein the state of a result is
> Chuck> actually divorced from the result itself.
>
>That's useful indeed, though there were plenty of other machines back
>then where this was true. I believe the more significant innovations
>were the extensive parallelism and the quantity of registers.
A lot of those ideas were result of experimental machines that preceeded
them. TX2 came to mind as it had fast registers and core. Other ideas
embodied were dual ALU, it could be used as 18bits or two 9bit alu.
While the machine was a test bed to transistor logic it was also a
system archetecture test bed as well.
>Sure was. 600 timesharing terminals on a pair of 10 MHz processors is
>pretty slick. (Come to think of it, over 9000 timesharing terminals
>on a single Alpha-based descendant of that system is mighty
>impressive, too.)
>
> paul
I remember the BOCES LIRICS (LI NY) PDP-10 system in 1971 running around
500users at anyone time. Used to run a lot of idle cycles even them.
Allison
Something is missing my message was:
> , I am getting a TRS-80 Mod 16 but no keyboard but I have a Mod II keyboard
> and wonder if it will work till I find one fof the Mod 16.
> Thanks for any help, Al DePermentier
Alwrcker82 at wmconnect.com
>
>Subject: Re: OT: Lowest-power small server solutions
> Date: Tue, 01 Nov 2005 16:09:01 +0000
> To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
>
>Chuck Guzis wrote:
>> This may be appropriate for another list, but it seems to me that there's
>> plenty of applicable knowledge here.
>>
>> Right now, we're using an older Compaq Deskpro P3-600 box as our incoming
>> Linux server. Basically, it connects with the DSL modem and contains IP
>> masquerading, DNS caching, firewall and fetchmail/procmail/qmail tasks
>> (SpamAssassin included). It runs 24x7 with no problem, as it has for the
>> last 5 or 6 years. Built like a tank.
I wonder if you even need a P200 for that. I used to manage a
networks that had a 486dx/66 doing all but SpamaAssassin. For the rate it
had to handle on the DSL port (actually fractional T1 256kb/S) it never
seemed to be working hard. The PS in it was only 200W and nowhere was
it ever stressed. It's claim to fame was running at room temp over a
weekend in the summer with both PS and CPU fan siezed without melting
or even getting upset.
Also an older 500mb-1gb drive will use less power than a newer fast
spinning drive. Or better yet netboot it and only keep a floppy. Pull
all the IO you don't need and run the video at 640x480x256 as a further
power reduction. Use a monitor (or KVM switch) as you don't need
a monitor save to check on it.
Allison
Scott,
>I have a simple 8088-based SBC design wired up and waiting for motivation to
>put together some test firmware. The main thing that has kept me from bringing
>it up is the difficulty in getting x86-based machine language development tools
>going. I'm used to little 4 and 8-bit assemblers where you can plop down a few
>ORG statements and have it all resident in a ROM, and almost all the x86 asm
>tools start from the assumption you are running on DOS and have no direct control
>of the memory map.
My ASM86 assembler is a "bare metal" assembler, it uses ORG, and outputs Intel (or
Motorola) hex format download records (which can be converted by my HEXFMT into a
pure binary file if that is your preference). It does not assume any OS, and does
not require any special/weird setup sequences - just translates instructions into
opcodes. ASM86 is a simple command line .EXE, runs under DOS up, does not require
any installation or other such stuff - very easy to get going.
I also have two 8086 debuggers that go with it:
HDM86 is a "Hardware Debug Monitor" it gives you basic read/write/dump, but the
nice thing about it is that it need NO memory - as long as you have the ROM and
UART working, you can run it (even if you don't have the UART working, you can
use it's polling to debug, so all you really need to get started is the ROM).
Takes about 1.25k of ROM
MON86 is a much more powerful monitor, which features all the goodies, memory and
register dump/edit, breakpoints, single-step, disassembler, lots more... (It does
need 160 bytes of RAM and about 3k of ROM).
These tools should be all that you need to get your 8088 system up and running,
and I'll be happy to send them to ya - contact me off-list if you would like them.
I also have a decent disassembler for the 8086 instruction set which will let you
define memory areas/types, build symbol tables for you etc. Also for "bare metal",
but it doesn't sound like you will need this as you are writing "all new" code.
In case you are also a 'C' programmer, I also have a 8086 "bare metal" version of
my Micro-C compiler - much of what I said about the assembler applies to this (in
fact, the C compiler produces assembly source which it them runs through the ASM86
assembler).
FWIW, I have similar assemblers for a couple dozen other small processor
architectures, as well as monitors, disassemblers and C compilers for many of
them.
Regards,
Dave
--
dave04a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools: www.dunfield.com
com Collector of vintage computing equipment:
http://www.parse.com/~ddunfield/museum/index.html
Thanks to all who replied to me, I going to have a busy Friday.!
For the benefit of all my fellow lurkers, here is a website many mentioned as a great place to start looking for surplus electonics stores (and was in some earlier cctalk messages a few months back, shame on me!)
http://www.bluefeathertech.com/technoid/calswapindex.html
Gary Fisher
This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. Unless otherwise stated, opinions expressed in this e-mail are those of the author and are not endorsed by the author's employer.
Okay, I'm going to try and take another crack at replacing the flyback on my
VT100. A few months ago I almost did, and chickened out. I'm very very
afraid to do so, as the idea of trying to discharge the CRT scares me very
much. The terminal has been off and disconnected from power for at least
2-3 months now.
This is what I've learned so far from reading:
Put one hand in your back pocket. Use an insulated screwdriver with
alligator clips on either end, one to the screwdriver blade, one to the
frame (VT100 service manual says the frame right above the CRT is where you
should ground to). Place the screwdriver under the anode cap and touch the
metal connection underneath. Wait till the crackling stops. Remove the
anode cap.
Can anyone reassure me that this is a semi-safe procedure? Has anyone done
this sort of thing before?
Thanks
Julian
>
>Subject: Re: FPGA VAX update
> From: Holger Veit <holger.veit at ais.fraunhofer.de>
> Date: Thu, 03 Nov 2005 14:08:04 +0100
> To: General Discussion: On-Topic Posts Only <cctech at classiccmp.org>
>
>woodelf wrote:
>
>> Bj?rn Vermo wrote:
>>
>>>
>>> Apple comes to mind. You can pick up a G4 really cheap these days.
>>> Whether you want to run BSD (OS X) or Linux is a matter of taste.
>>> IBM have some PPc development systems (Walnut if I recall right)
>>> which can run both Linux and QNX, but I have no idea how to get one
>>> or what they sell for.
>>
>>
>> I guess nobody even considers building a computer from scratch. :(
>>
>About thirty years ago, when I was pretty much younger :-), I built a
>classical TTL computer (with 74181 ALUs etc.) almost from scratch,
>basically from schematic fragments from the TTL databook and TTL
>cookbook and some electronics magazines; well - if it were really from
>scratch, then even so "highly integrated chips" like the 74181 were
>prohibited as well. Looking back, this had almost all characteristics of
>a real computer.
>
>There are two aspects IMHO why this does no longer happen today:
>- what was a known magazine in the past, would today perhaps
>realistically called "Un-Popular Electronics", the knowledge of
>electronics from the ground up is dying out; and with the continuing
>"digitalization" of technology, it is an ever increasing hurdle to get
>started - the classical AM detector radio I built as a newbie will
>nowadays no longer attract anyone - you can get a gadget which is better
>by several magnitudes for a fraction of the expenses you'd have for
>soldering your thing.
>- The tools you have are too user friendly (!); i.e. you could rather
>easily click something together, be it software or VHDL code for an FPGA
>without ever needing to understand what is really going on. The "soul of
>a new machine" guys that traced glitches with a logic analyzer in a
>large wire-wrapped TTL graveyard are gone - such a machine had the
>necessary wow factor. No surprise when a VAX in an FPGA - see subject -
>is not really interesting. It is possible - that's it. But what does one
>gain? It is like solving a 10000 pieces puzzle; spend time and don't
>learn really much.
>When Hillary climbed the Mount Everest 50 years ago, it was something
>new, extraordinary. When tourist nowadays use sort of stairways to reach
>the top (okay, it's not *that* extreme now), it is just uninteresting.
>But standing on the top, is still a challenge and an experience for the
>individual. However, what we lost now is a sense of wonder - that small
>ALU based TTL circuit was built by myself, and I did it, and it is
>irrelevant that some idiot could download a digital simulator and click
>the same circuit together on a PC screen. I guess this is what makes the
>difference between a real PDP-11 with some ridiculous 5MB storage disks
>compared to a SIMH emulator running on a 3GHz Pentium.
>Watch the blinkenlights.
>
>Holger
Ah, for the adventure of it all. Well put.
Another extreme is those that seem to be interested in building usable
minimalist machines with TTL using the fewest packages.
Allison
> -----Original Message-----
> From: cctalk-bounces at classiccmp.org
> [mailto:cctalk-bounces at classiccmp.org] On Behalf Of Holger Veit
> Sent: donderdag 3 november 2005 14:08
> To: On-Topic Posts Only
> Subject: Re: FPGA VAX update
>
> woodelf wrote:
>
> > Bj?rn Vermo wrote:
> >
> >>
> >> Apple comes to mind. You can pick up a G4 really cheap these days.
> >> Whether you want to run BSD (OS X) or Linux is a matter of taste.
> >> IBM have some PPc development systems (Walnut if I recall right)
> >> which can run both Linux and QNX, but I have no idea how
> to get one
> >> or what they sell for.
> >
> >
> > I guess nobody even considers building a computer from scratch. :(
> >
> About thirty years ago, when I was pretty much younger :-), I
> built a classical TTL computer (with 74181 ALUs etc.) almost
> from scratch, basically from schematic fragments from the TTL
> databook and TTL cookbook and some electronics magazines;
> well - if it were really from scratch, then even so "highly
> integrated chips" like the 74181 were prohibited as well.
> Looking back, this had almost all characteristics of a real computer.
>
> There are two aspects IMHO why this does no longer happen today:
> - what was a known magazine in the past, would today perhaps
> realistically called "Un-Popular Electronics", the knowledge
> of electronics from the ground up is dying out; and with the
> continuing "digitalization" of technology, it is an ever
> increasing hurdle to get started - the classical AM detector
> radio I built as a newbie will nowadays no longer attract
> anyone - you can get a gadget which is better by several
> magnitudes for a fraction of the expenses you'd have for
> soldering your thing.
> - The tools you have are too user friendly (!); i.e. you
> could rather easily click something together, be it software
> or VHDL code for an FPGA without ever needing to understand
> what is really going on. The "soul of a new machine" guys
> that traced glitches with a logic analyzer in a large
> wire-wrapped TTL graveyard are gone - such a machine had the
> necessary wow factor. No surprise when a VAX in an FPGA - see
> subject - is not really interesting. It is possible - that's
> it. But what does one gain? It is like solving a 10000 pieces
> puzzle; spend time and don't learn really much.
> When Hillary climbed the Mount Everest 50 years ago, it was
> something new, extraordinary. When tourist nowadays use sort
> of stairways to reach the top (okay, it's not *that* extreme
> now), it is just uninteresting.
> But standing on the top, is still a challenge and an
> experience for the individual. However, what we lost now is a
> sense of wonder - that small ALU based TTL circuit was built
> by myself, and I did it, and it is irrelevant that some idiot
> could download a digital simulator and click the same circuit
> together on a PC screen. I guess this is what makes the
> difference between a real PDP-11 with some ridiculous 5MB
> storage disks compared to a SIMH emulator running on a 3GHz Pentium.
> Watch the blinkenlights.
>
> Holger
Actually, I don't need to comment on this. Being a HAM radio amateur,
I did built a diode detector with a high-impedance headphone and a
varco plus coil. The experience *I made that*, and the first time
you hear a radio station are unforgettable impressions.
To add to your last sentence: I agree, but I have built something
that sits "in between". I use the SIMH software, but *added* a real
blinkenlight console! See my website. I do have several real PDP-11
models, but the blinkenlight SIMH is fun too (well, sort of).
Perhaps most of the fun was building it ...
- Henk, PA8PDP.
>
>
This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.
Thank you for your cooperation.