Re: send more than 8 bits with parallel port




Jonathan Kirwan wrote:
On Tue, 21 Feb 2006 14:15:56 GMT, NoSpam@xxxxxxxxxxx (Bob Masta)
wrote:

<snip>

Others have answered the hardware aspect of your
question. However, note that if you plan to use this
on PCs running Windows versions later than 9x,
you will have to use a special ring 0 device driver to have
access to the printer port. (GIVEIO and USERPORT are
two that I have heard of, put haven't tried myself.)
That might be one advantage for using the serial
port, which can be accessed through more-or-less
standard Windows API functions.

Another thing to think about is that parallel printer ports
are rumored to be slated for extinction... but then again,
aren't we all!

You know? What bugs me about this very true point is that we are
losing all of the really good hobbyist interfaces for adapting a PC.
The ISA bus was really nice and not too complex for a serious hobbyist
to use, in adding boards. Gone now, or nearly so. Ever consider
trying to do a PCI card as a hobbyist? Reflection wave bus, 2ns clock
skew on 33MHz and 1ns clock skew on 66MHz with a 1.5" +/- 0.1" trace
length for the clock (often serpentined in order to get there), etc.
Just getting equipment to monitor the analog characteristics for
debugging a design is a fortune. Lose the parallel, lose the serial,
add USB 2.0, replace the old IDE controller cables with SATA 2, and
what are you left with to use, anymore? It's getting to be a pain in
the ...

Well, of course, there are microcontroller boards. But then you lose
out on the excellent and easy availability of very excellent and well
documented development tools.

Jon

Contrivers of contrivances are going to have a more difficult time when
the ol' parallel port is no more, Jon. Of course, we can squirrel away
more older PCs (that is, until the War Department issues the Ultimatum
again). I would guess, though, you'll be seeing more standardized USB
experimenter-type interfaces to replace the parallel port for classroom
and hobbyist work. You'll also see more use of PCI DIO type boards for
the parallel I/O. You will be seeing a lot less hobbyist bus
interface.

But it should still beat those "thrilling days of yesteryear" (early
'80s), when PCs cost thousands, you had to wait in line for one, and
you took your career in your hands every time you turned on the power
for a new prototype, consigning it as well as everything else in the
box and possibly your job to the tender(?) mercies of a harsh 85 watt
switching power supply.

I learned about the advantages of the trailing edge back then, picking
up cheapie Kaypro IIs for their serial and parallel ports as IBM and
Micro Soft (two words back then) cleaned Kaypro's and CP/M's clocks.
Everyone who wanted to replace VisiCalc with Lotus had their first
obsolete computer (aaaaww!), and after having it sit around unused for
a few months, was willing to practically give it away (for a couple
hundred dollars).

Those were the days. Womenfolk swooned as real engineers and techs
walked by, TI-57s bobbling suggestively from their belt loops. ;-)

Cheers
Chris

.



Relevant Pages

  • Re: Q about (ab)using a PCs parallel port
    ... Bought a LPT isa card to 'fix' it. ... running NT 3.51 - and no LPT on the server. ... the server, he hooked up a parallel port Zip drive to a PC, ... He toasted three parallel ports on three different PCs before ...
    (sci.electronics.design)
  • Has anyone yet made a routine...?
    ... to treat a parallel port as a synchonous ... perhaps using the system clock (counted-down appropriately for the bps ... is there a more speed-efficient way of doing ASCII to EBCDIC ...
    (comp.lang.c)
  • Re: How to produce a fast clock output?
    ... the system would no longer work. ... I needn't keep the clock running continuous. ... KHz) since the parallel port contains 74LS374 chips as buffers/latches, ... the "rdtsc" which is an extremely precise CPU ...
    (comp.unix.programmer)
  • Re: How to produce a fast clock output?
    ... >> I want to produce a clock output on the pin of parallel port. ... > subject to time-slicing, meaning that you can only use so much ...
    (comp.unix.programmer)