Forgot to add: yes, the Amish ARE peace-loving people, and I'm really trying
to learn their way. I really am trying, it's just hard for me sometimes
when I let myself go overboard.
Blessed Be everyone again, and Blessed Ostara to those who know what it
means :-)
MS
I didn?t reply to CCTech, I replied off list, but I am 50-54 also.
Is a new compilation coming up? I?m curious.
Kevin J Andres
Senior Technician
Engineered Protection Systems Inc.
HYPERLINK "mailto:kandres at epssecurity.com"mailto:kandres at epssecurity.com
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 3/15/2005
Paxton Hoag wrote:
>> When this survey started I really enjoyed the list of early computers
>> used that people added.
>> It would be both on topic and fun to continue.
Yes!
Earliest experience SWTP. Bootloader binary from switches to run a cassette
file loader.
Vaguely remember an IMSAI something, Believe it was 8088. Also a weird little strip printer
in a wood side case with smoked glass cover that went with either
the SWTP or the IMSAI.
Commodore PET ?Chiclet?, still have it, run issues.
Ohio Scientific Superboard used as an embedded device
for alarm system printing. Still have one, haven?t run in years.
Dual 5.25 floppies in case that were connected to Superboard at
one time in office. Most of what we did was cassette loaded due to
field volatility of disk drives, (heavy handed field personnel).
8088 dedicated processor for audible coding of fire system
and graphic LED displays.
Various DEC over the years. 11/23 comes to mind. Think I still
have manuals in a drawer with schematics for older DEC equipment
here somewhere.
Data General Micro Nova used as a central Station monitoring system.
Have the processor, lost the 10 Meg disk drives. Big on serial ports,
All printers and terminals were serial LSI?s. Had one of those for a while,
Eventually caved to ?wife? and got rid of the terminal.
Various embedded 8749 machines over the last 14 years. I tend to
do the hardware and another gent here writes the code.
I learned in 6502 machine code, completely missed the assembly era.
I have no idea where I was. Then jumped into various compilers.
Kevin J Andres
Senior Technician
Engineered Protection Systems Inc.
HYPERLINK "mailto:kandres at epssecurity.com"mailto:kandres at epssecurity.com
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 3/15/2005
I need an EPROM eraser, and I found a Logical Devices UV Eprom eraser
QUV-T8 for just under $100 shipped. Is this a good deal?
I'll get it tonite if I'm not getting bent over... ;-)
Thanks,
Roger "Merch" Merchberger
--
Roger "Merch" Merchberger | "Bugs of a feather flock together."
sysadmin, Iceberg Computers | Russell Nelson
zmerch at 30below.com |
-------------Original Message:
From: "Steven Canning" <cannings at earthlink.net>
Subject: Re: Byte sizes, still tastes like nothing
Tom,
Though I am inclined to agree with you in principle..... how can we discuss
technology if we do not agree on the terminology?
<snip>
-------------Reply:
Doesn't look like we're about to _agree_ on this any more than anything else
(except maybe our appreciation of Jay & the others toiling on our behalf);
no shortage of opinions though...
mike
-----------Original Message:
Date: Tue, 15 Mar 2005 15:58:16 -0600
From: "Keys" <jrkeys at concentric.net>
Subject: ProComm Plus
Was someone looking for ProComm Plus awhile back? I found a copy on 3.5 FD
today in the warehouse along with several manuals of different versions.
Let me know what you need from it. John
----------------------
That might have been me; thanks muchly, but I was (and still am) looking for
a comm package called ProCALL. Anybody ever heard of it?
Thanks,
mike
Hi!
This is another test. I couldn't send emails to cctech either, but I've
even got hardware to offer, which is hard if one cannot even send emails
that reach their recipients...
MfG, JBG
--
Jan-Benedict Glaw jbglaw at lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Hi!
I wasn't able to send emails to cctalk, so here's another test. I've
even got some hardware to offer, but that's hard to do if one's emails
just disappear...
MfG, JBG
--
Jan-Benedict Glaw jbglaw at lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier B?rger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
On Tue, 15 Mar 2005 Roger Merchberger <zmerch at 30below.com> wrote:
> Rumor has it that William Donzelli may have mentioned these words:
>
> >Parity checking is the job of the memory controller, not the processor. In
> >fact, I am having a hard time thinking of a processor that did its own
> >parity checking in software (yes, I know any processor could do it, but
> >did any really do it?).
>
> 8085? There's a P bit in the condition code register (in 6809 speak) -- I
> think it's called the PSW -- Program Status Word? I'm just beginning
> learning assembly on my Tandy 10x/200 machines... Anyway, there are several
> arithmetic operations that automatically set the Parity bit and there are
> branch and return instructions that utilize the status of the P bit.
Unless the 8085 differs from the Z80 (which both come from the 8080) this
P-bit is used as parity very loosely speaking.
It's actually P/V-bit. For arithmetic operations, it indicates overflow
(V), while for logical operations it indicates parity of the result (P).
Logic ops simply count the number of "1"s in the result, and set the P bit
if the number is odd.
Can be useful if you want to generate or check parity for data you're
communicating. (Serial communication sometimes don't have hardware parity
implemented for example).
Parity for memory is never something dealt with by software. It would be a
chicken and egg situation.
> > Even if the parity checking is a lowly 74180, like
> >in a microcomputer - it is still not boggin down the processor. The
> >processor really doesn't need to know about parity, unless things go bad.
>
> Altho it's not a *huge* need, it can be handy for serial I/O... that would
> be a function that uses parity, but is not reliant on the memory controller.
Yes.
But this is two different parity issues. Parity for memory is dealt with
by hardware. Parity for communication might be dealt with by hardware or
software.
Johnny
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at update.uu.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol