Printer Port

[Rich Grise]

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...

On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.
Unless your BASIC interpreter does it different - for example,
FF AND 04 yields 04 on every system I've ever used, and every
book about it that I've read.

Or maybe 37A is open-collector (I'd have to look it up), in
which case if there are pullups, those bits will go high -
but not because of what's been output. (outputted? )

And some of the bits are inverted, I also would have to look
up which bits - but the value of the data is as I said.

Thanks,
Rich

 

[Jan Panteltje]

On a sunny day (Fri, 14 May 2004 03:22:49 GMT) it happened "Rich Grise"
<null@example.net> wrote in <dYWoc.71159$sK3.49034@nwrddc03.gnilink.net>:

"budgie" <me@privacy.net> wrote in message
news:3e78a0hh74msr1042ooftfju2e5hjc35b6@4ax.com...
On 13 May 2004 16:45:41 -0700, tatto0_2000@yahoo.com (Wong) wrote:

Sound so simple to manage par port since I can have direct control
over the signals.

It is once you get to grips with the functions of each of the three
registers.

So if I have the following C code:
outp(37A, 0x04); // Would this reset the printer ?

I make a practice of (Basic code, I don't speak C)

OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all! You want this:

TEMP = INP(37A)
TEMP = TEMP AND FB
TEMP = TEMP OR (MYDATA AND 04)
OUT 37A, TEMP

It could all be written in one line, but that's too cryptic - when I
go back and look at code a year later, I like to be able to read it. ;-)

Cheers!
Rich

Here is the C version (I use 2 strings off i2c chips on the parport (6 pins in use plus ground):

sdal()
{
register a;
a = inb(par_port_address);
a = a & 0xbf; /* reset bit 6 (d6 on pin 8) */
outb(a, par_port_address);
busdly(IIC_BUS_DELAY);
}


sdah()
{
register char a;
a = inb(par_port_address);
a = a | 0x40; /* set bit 6 (d6 on pin 8) */
outb(a, par_port_address);
busdly(IIC_BUS_DELAY);
}

 

[Jan Panteltje]

On a sunny day (Fri, 14 May 2004 02:06:50 GMT) it happened "R. Steve Walz"
<rstevew@armory.com> wrote in <40A42A8C.191A@armory.com>:

John G wrote:

"R. Steve Walz" <rstevew@armory.com> wrote in message
news:40A30A36.1E91@armory.com...
John G wrote:

"Wong" <tatto0_2000@yahoo.com> wrote in message
news:509bfe22.0405121950.1a927c85@posting.google.com...
Hi,
Address of 378 is normally define for printer port,
LPT.
Then what is the purpose to use the address of 379,
37A
?
I am confuse and hope someone can shed me a light.
Thanks.

All these hardware addresses can be used by printer
adapters
and at boot time the Operating system checks to see
which
are present and allocates them to LPT1 then 2 then 3 as
they are found.
--
John G

Wot's Your Real Problem?
-------------
No, the port base addresses are 378, 278, and 3BC Hex.

The addresses 379 and 37A Hex are the other two addresses
that are part of the LPT1 port at 378 Hex.

-Steve

You are absolutly correct.
It is so long since I needed to care about this I jumped to
the wrong conclusion.
But 378H will only be LPT1 if there is something there.
If 278H is the hardware address of the only print adapter
the it will become LPT1
This may be rare but it did confuse many people long ago.
(Remember DOS)
The Monchrome and Print adapter had one address and the
Print adapter had another.
--
John G
----------------
Actually, the original LPT1 port base address on the PC was 3BC Hex,
but it is only assigned LPT1 status in DOS/Win if it is found active,
using a loopback data test, since it was only implemented on the early
mono-text-only-printer cards, and mono-graphic-printer cards and
Hercules cards and a few of the earliest higher level graphic cards.

The second LPT2 was originally the 378 Hex addrsss, and the 278 Hex
was the LPT3, but only if 3BC Hex was found and assigned to LPT1,
and without 3BC Hex being found, then 378 Hex defaults to LPT1 and
278 Hex defaults to LPT 2.

-Steve
It is for this reason and things that one should ask the BIOS what the address is.

JP

 

[Florian]

"Rich Grise" <null@example.net> writes:

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.

s/sets/leaves untouched/

(snip)
--
fecit quoque Dominus Deus Adam et uxori eius tunicas pellicias et
induit eos

 

[R. Steve Walz]

Bob Masta wrote:

On 12 May 2004 20:50:11 -0700, tatto0_2000@yahoo.com (Wong) wrote:

Hi,
Address of 378 is normally define for printer port, LPT.
Then what is the purpose to use the address of 379, 37A ?
I am confuse and hope someone can shed me a light. Thanks.

To enlarge on what others have posted, note that you need Win9x
or earlier to access the printer port without a special driver. For
NT, 2K, or XP you need a kernel driver. See Jan Axelson's site
at <www.lvr.com> for more info.

Also note that it's good programming practice in DOS to never
assume the port address is 378h or anything else. Instead,
you should read it from the BIOS. The word at 0:408h is the
base address of LPT1, 40Ah is the address of LPT2, 40C is
LPT3, and 40E is LPT4. Of course, most systems never had
more than one LPT anyway, but it's location wasn't always a
sure thing. In the early days it was a separate card, and could
be jumpered to various addresses. You might have had an
LPT on a graphics adapter as well.

Hope this helps!

Bob Masta
dqatechATdaqartaDOTcom

D A Q A R T A
Data AcQuisition And Real-Time Analysis
www.daqarta.com
-----------

Yup, even more correct.

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[R. Steve Walz]

Rich Grise wrote:

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.
Unless your BASIC interpreter does it different - for example,
FF AND 04 yields 04 on every system I've ever used, and every
book about it that I've read.

Or maybe 37A is open-collector (I'd have to look it up), in
which case if there are pullups, those bits will go high -
but not because of what's been output. (outputted? )

And some of the bits are inverted, I also would have to look
up which bits - but the value of the data is as I said.

Thanks,
Rich
-----------

All pins serviced by 37A ( ar any LPT base + 2 control address) are
open-collector outputs, and bits -C0, -C1, -C3 are inverted, while
C2, the "4's" bit in binary, is not.

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[Rich Grise]

"Rich Grise" <null@example.net> wrote in message
news:tz4pc.127409$G_.23892@nwrddc02.gnilink.net...

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.
Unless your BASIC interpreter does it different - for example,
FF AND 04 yields 04 on every system I've ever used, and every
book about it that I've read.

Or maybe 37A is open-collector (I'd have to look it up), in
which case if there are pullups, those bits will go high -
but not because of what's been output. (outputted? )

NO, Dangit! That's wrong! An open collector is a current
sink when it's set to 0. Duh! And I was sober when I posted
that! I'm ashamed of myself.

I might have been thinking of the inverted bits, see next
sentence. Just now I thought of using thinking of tri-state
as an excuse, but that's even lamer.

And some of the bits are inverted, I also would have to look
up which bits - but the value of the data is as I said.

Thanks,
Rich




A thousand pardons, sirs and mesdames.

Rich

 

[budgie]

On Fri, 14 May 2004 14:19:05 GMT, "Rich Grise" <null@example.net> wrote:

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.
Unless your BASIC interpreter does it different - for example,
FF AND 04 yields 04 on every system I've ever used, and every
book about it that I've read.

Whoops - red face time :-((

Should have been OR not AND.

OUT 37A, (INP(37A) OR 04)

Or maybe 37A is open-collector (I'd have to look it up), in
which case if there are pullups, those bits will go high -
but not because of what's been output. (outputted? )

And some of the bits are inverted, I also would have to look
up which bits - but the value of the data is as I said.

Thanks,
Rich

 

[R. Steve Walz]

Jan Panteltje wrote:

On a sunny day (Fri, 14 May 2004 02:06:50 GMT) it happened "R. Steve Walz"
rstevew@armory.com> wrote in <40A42A8C.191A@armory.com>:

John G wrote:

"R. Steve Walz" <rstevew@armory.com> wrote in message
news:40A30A36.1E91@armory.com...
John G wrote:

"Wong" <tatto0_2000@yahoo.com> wrote in message
news:509bfe22.0405121950.1a927c85@posting.google.com...
Hi,
Address of 378 is normally define for printer port,
LPT.
Then what is the purpose to use the address of 379,
37A
?
I am confuse and hope someone can shed me a light.
Thanks.

All these hardware addresses can be used by printer
adapters
and at boot time the Operating system checks to see
which
are present and allocates them to LPT1 then 2 then 3 as
they are found.
--
John G

Wot's Your Real Problem?
-------------
No, the port base addresses are 378, 278, and 3BC Hex.

The addresses 379 and 37A Hex are the other two addresses
that are part of the LPT1 port at 378 Hex.

-Steve

You are absolutly correct.
It is so long since I needed to care about this I jumped to
the wrong conclusion.
But 378H will only be LPT1 if there is something there.
If 278H is the hardware address of the only print adapter
the it will become LPT1
This may be rare but it did confuse many people long ago.
(Remember DOS)
The Monchrome and Print adapter had one address and the
Print adapter had another.
--
John G
----------------
Actually, the original LPT1 port base address on the PC was 3BC Hex,
but it is only assigned LPT1 status in DOS/Win if it is found active,
using a loopback data test, since it was only implemented on the early
mono-text-only-printer cards, and mono-graphic-printer cards and
Hercules cards and a few of the earliest higher level graphic cards.

The second LPT2 was originally the 378 Hex addrsss, and the 278 Hex
was the LPT3, but only if 3BC Hex was found and assigned to LPT1,
and without 3BC Hex being found, then 378 Hex defaults to LPT1 and
278 Hex defaults to LPT 2.

-Steve
It is for this reason and things that one should ask the BIOS what the address is.
JP
-----------

Yes, agreed, unless you happen to know already.
Any generalized software should do this by looking at RAM address
408 Hex :

debug
-d 0040:0008 L8

0040:0008 78 03 78 02 00 00 00 00

Note, the address is listed LO byte then HI byte
"78 03" instead of 0378 Hex, as Intel is Little Endian first.

Or in BASIC:

10 For i = 8 to 15
20 Print Peek(1024 + i)" ";
30 Next i
40 Print

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[R. Steve Walz]

Florian wrote:

"Rich Grise" <null@example.net> writes:

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.

s/sets/leaves untouched/
------------------------

Since it is the only one not inverted, a 1 in the "4's" but
SETS its output HI.

fecit quoque Dominus Deus Adam et uxori eius tunicas pellicias et
induit eos
----------------------

God didn't make anybody any clothing. Don't be stupid. Has God
ever made you a suit?

Did you know that "Genesis" was not original, that it was actually a
child's tale from Balylonian scrolls much older than Judaism?? The
Jews just picked it up during their slavery in Iraq! It's not some
"holy" book, it was meant to make kids keep their clothes on, because
the rich kids who were told it could only be identified and protected
if they wore clothes, which ONLY the rich of the king's court could
afford!!

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[Florian]

"R. Steve Walz" <rstevew@armory.com> writes:

Florian wrote:

"Rich Grise" <null@example.net> writes:

"budgie" <me@privacy.net> wrote in message
news:rll8a016ba5b73cga5ghn59krhukj2laep@4ax.com...
On Fri, 14 May 2004 03:22:49 GMT, "Rich Grise" <null@example.net> wrote:
"budgie" <me@privacy.net> wrote in message
OUT 37A, (INP(37A) AND 04)

That way, whatever other bits are set/clear remain that way.

Actually, they don't - that code clears them all!

It doesn't actually. Try it some time.

OK, it clears them all except the 04 bit, which it sets.

s/sets/leaves untouched/
------------------------
Since it is the only one not inverted, a 1 in the "4's" but
SETS its output HI.

I'm not following you. Nothing's being inverted anywhere, and nothing's
being set high. It's a simple AND. Are you saying a PC parallel port will
perform some unexpected transformation on the values read and written?
That's contrary to my experience. I'm confused.

fecit quoque Dominus Deus Adam et uxori eius tunicas pellicias et
induit eos
----------------------
God didn't make anybody any clothing. Don't be stupid.

Heck, how would you know? Were you there?

Has God ever made you a suit?

Not personally, no. You?

(snip rest)
--
quadam autem die cum venissent filii Dei ut adsisterent coram Domino
adfuit inter eos etiam Satan

 

[Rich Grise]

"R. Steve Walz" <rstevew@armory.com> wrote in message
news:40A5B0E8.6E9E@armory.com...

God didn't make anybody any clothing. Don't be stupid. Has God
ever made you a suit?

Of course. He's also built me five computers, a Winnebago LeSharo, MAME,
TV, he grows me food and Marijuana, he brings me the words of all these
fine people on electrical telephone lines that he had built for me, ...
It's so fucking obvious that that's probably why it escapes you.

The part that hasn't been obvious, and has been made unobvious for very
many years for reasons that are just as unobvious, is the part that Will
plays in all this.

I have been given that answer, ergo, I am categorically insane.

Cheers!
Rich

 

[R. Steve Walz]

Rich Grise wrote:

"R. Steve Walz" <rstevew@armory.com> wrote in message
news:40A5B0E8.6E9E@armory.com...

God didn't make anybody any clothing. Don't be stupid. Has God
ever made you a suit?

Of course. He's also built me five computers, a Winnebago LeSharo, MAME,
TV, he grows me food and Marijuana,
---------------

Ah, I see the problem.

I have been given that answer, ergo, I am categorically insane.
Cheers!
Rich
-------------

Yup.

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[Jan Panteltje]

On a sunny day (12 May 2004 20:50:11 -0700) it happened tatto0_2000@yahoo.com
(Wong) wrote in <509bfe22.0405121950.1a927c85@posting.google.com>:

Hi,
Address of 378 is normally define for printer port, LPT.
Then what is the purpose to use the address of 379, 37A ?
I am confuse and hope someone can shed me a light. Thanks.
379 hex is actually also a part of the par port (registers), for example

bit 3 0x379 =pin 15 (ERROR) is there
In the old day par port was a 8255 PPI IIRC.
So a peek in the 8255 registers should show you something.
But things did become more complicated when PPC, ECP capable ports came.

If it makes any sense to you:
#define LPT1_BASE_ADDR0x378
#define LPT2_BASE_ADDR0x278
#define LPT3_BASE_ADDR0x3BC

/* Offsets from the base address for the various registers */
#define STATUS_OFFSET0x01
#define CONTROL_OFFSET0x02

/* define ECP register offsets */
#define ECP_DATA0x00/* Data Register*/
#define ECP_A_FIFO0x00/* ECP Address FIFO*/
#define ECP_DSR0x01/* Device Status Register*/
#define ECP_DCR0x02/* Device Control Register*/
#define ECP_C_FIFO0x400/* Compatiblity mode FIFO */
#define ECP_D_FIFO0x400/* ECP Data FIFO*/
#define ECP_T_FIFO0x400/* ECP Test FIFO*/
#define ECP_CNFG_A0x400/* Config Register A*/
#define ECP_CNFG_B0x401/* Config Register B*/
#define ECP_ECR0x402/* Extended Control Reg.*/

#define ECP_FIFO_SIZE16

/* define some constants for used by the hardcoded functions */
#define BASE_LPT1 LPT1_BASE_ADDR
#define DATA_LPT1(LPT1_BASE_ADDR)
#defineSTATUS_LPT1(LPT1_BASE_ADDR+STATUS_OFFSET)
#defineCONTROL_LPT1(LPT1_BASE_ADDR+CONTROL_OFFSET)
#defineDATA_FIFO_LPT1(LPT1_BASE_ADDR+ECP_D_FIFO)
#defineECR_LPT1(LPT1_BASE_ADDR+ECP_ECR)

#define BASE_LPT2 LPT2_BASE_ADDR
#define DATA_LPT2(LPT2_BASE_ADDR)
#defineSTATUS_LPT2(LPT2_BASE_ADDR+STATUS_OFFSET)
#defineCONTROL_LPT2(LPT2_BASE_ADDR+CONTROL_OFFSET)
#defineDATA_FIFO_LPT2(LPT2_BASE_ADDR+ECP_D_FIFO)
#defineECR_LPT2(LPT2_BASE_ADDR+ECP_ECR)

#define BASE_LPT3 LPT3_BASE_ADDR
#define DATA_LPT3(LPT3_BASE_ADDR)
#defineSTATUS_LPT3(LPT3_BASE_ADDR+STATUS_OFFSET)
#defineCONTROL_LPT3(LPT3_BASE_ADDR+CONTROL_OFFSET)
#defineDATA_FIFO_LPT3(LPT3_BASE_ADDR+ECP_D_FIFO)
#defineECR_LPT3(LPT3_BASE_ADDR+ECP_ECR)


#define WRITECTRL(portaddress,val)outb((BYTE )(val), (portaddress))
#define READDATA(portaddress)(BYTE )inb((portaddress))
#define READSTATUS(portaddress)(BYTE )inb((portaddress))


/* the following define the bits within the ECR register */
#define ECR_mode0xE0
#define ECR_nErrIntrEn0x10
#define ECR_dmaEn0x08
#define ECR_serviceIntr0x04
#define ECR_full0x02
#define ECR_empty0x01

#define ECP_STANDARD_MODE0x00
#define ECP_PS2_MODE0x20
#define ECP_FIFO_MODE0x40
#define ECP_ECP_MODE0x60
#define RESERVED_10x80
#define RESERVED_20xA0
#define ECP_TEST_MODE0xC0
#define ECP_CNFG_MODE0xE0

There is some info somehere on the Microsoft site about how ECP
protocol works, but I forgot immediatly after writing some of the code...
JP

 

[R. Steve Walz]

Jan Panteltje wrote:

In the old day par port was a 8255 PPI IIRC.
---------------

Nope, never ever was on any computer from the AT, XT, and PC, back
through all the CP/M machines.

You're guessing, and that's silly.

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[Jan Panteltje]

On a sunny day (Mon, 17 May 2004 01:44:31 GMT) it happened "R. Steve Walz"
<rstevew@armory.com> wrote in <40A819D5.5554@armory.com>:

Jan Panteltje wrote:


In the old day par port was a 8255 PPI IIRC.
---------------
Nope, never ever was on any computer from the AT, XT, and PC, back
through all the CP/M machines.

You're guessing, and that's silly.
Nope, not guessin, in the 80ties I had the IBM BIOS listing.

And full diagrams of cause (company workled with IBM).
The Keyboard was one half of the 8255 PPI, 8 bit parallel in,
and that was fed from some shift registers, serial clock to the keyboard,
data from / to the keyboard.
Some other bits were control I think. But was not the other half of
that 8255 used for the printer port?
Or was the printer port just a latch?

OK, I just googled a bit I see you already knew this:
http://www.xs4all.nl/~ganswijk/chipdir/abc/keyboard/keyboard.faq
Version 0.9a IBM Keyboard/Scancode FAQ File Richard STEVEn Walz
rel 10 June 1994 *please retain this banner* rstevew@armory.com

Oh well ;-)
JP

 

[Rich Grise]

"Jan Panteltje" <pNaonStpealmtje@yahoo.com> wrote in message
news:c8av91$rj5$1@news.epidc.co.kr...

Nope, not guessin, in the 80ties I had the IBM BIOS listing.
And full diagrams of cause (company workled with IBM).
The Keyboard was one half of the 8255 PPI, 8 bit parallel in,
and that was fed from some shift registers, serial clock to the keyboard,
data from / to the keyboard.
Some other bits were control I think. But was not the other half of
that 8255 used for the printer port?
Or was the printer port just a latch?

OK, I just googled a bit I see you already knew this:
http://www.xs4all.nl/~ganswijk/chipdir/abc/keyboard/keyboard.faq
Version 0.9a IBM Keyboard/Scancode FAQ File Richard STEVEn Walz
rel 10 June 1994 *please retain this banner* rstevew@armory.com

I used to have "The IBM Personal Computer Technical Reference," which
was pretty cool - the whole BIOS listing, and the whole schematic.
I didn't do much with the keyboard, but ISTR seeing an 8048 or so -
and the LPT port was straight TTL. When third parties came up with
Chinese COM/LPT ports, they used some custom chip that blew out if
you looked at it wrong - I finally got tired of replacing them, and
built a little daughterboard where I exactly duplicated IBM's LPT
port. Then, realizing that the chip I'd supplanted had the clocks for
the UARTs, I built a little Pierce xtal oscillator with the collector
choke made of about 150 turns of magnet wire on a toothpick, with
pieces of resistor lead glued into tiny holes on the ends, so it
looked like it had leads like any other part.

But I've never seen or heard of an 8255 used for LPT.

Cheers!
Rich

 

[Jan Panteltje]

On a sunny day (Mon, 17 May 2004 19:06:04 GMT) it happened "Rich Grise"
<null@example.net> wrote in <w28qc.135750$G_.109221@nwrddc02.gnilink.net>:

"Jan Panteltje" <pNaonStpealmtje@yahoo.com> wrote in message
news:c8av91$rj5$1@news.epidc.co.kr...

Nope, not guessin, in the 80ties I had the IBM BIOS listing.
And full diagrams of cause (company workled with IBM).
The Keyboard was one half of the 8255 PPI, 8 bit parallel in,
and that was fed from some shift registers, serial clock to the keyboard,
data from / to the keyboard.
Some other bits were control I think. But was not the other half of
that 8255 used for the printer port?
Or was the printer port just a latch?

OK, I just googled a bit I see you already knew this:
http://www.xs4all.nl/~ganswijk/chipdir/abc/keyboard/keyboard.faq
Version 0.9a IBM Keyboard/Scancode FAQ File Richard STEVEn Walz
rel 10 June 1994 *please retain this banner* rstevew@armory.com

I used to have "The IBM Personal Computer Technical Reference," which
was pretty cool - the whole BIOS listing, and the whole schematic.
I didn't do much with the keyboard, but ISTR seeing an 8048 or so -
and the LPT port was straight TTL. When third parties came up with
Chinese COM/LPT ports, they used some custom chip that blew out if
you looked at it wrong - I finally got tired of replacing them, and
built a little daughterboard where I exactly duplicated IBM's LPT
port. Then, realizing that the chip I'd supplanted had the clocks for
the UARTs, I built a little Pierce xtal oscillator with the collector
choke made of about 150 turns of magnet wire on a toothpick, with
pieces of resistor lead glued into tiny holes on the ends, so it
looked like it had leads like any other part.

But I've never seen or heard of an 8255 used for LPT.

Cheers!
Rich
Yea, it seems it was a normal TTl latch (Sam will have to help us here).

I actually designed cards for in the PC in that company.
I made a soundcard, and it was used, and told the boss: 'Why don't you
patent this?' (It had wavetable too), but he did not want to do that.
He REALLY should have
JP

 

[R. Steve Walz]

Jan Panteltje wrote:

On a sunny day (Mon, 17 May 2004 01:44:31 GMT) it happened "R. Steve Walz"
rstevew@armory.com> wrote in <40A819D5.5554@armory.com>:

Jan Panteltje wrote:


In the old day par port was a 8255 PPI IIRC.
---------------
Nope, never ever was on any computer from the AT, XT, and PC, back
through all the CP/M machines.

You're guessing, and that's silly.
Nope, not guessin, in the 80ties I had the IBM BIOS listing.
And full diagrams of cause (company workled with IBM).
The Keyboard was one half of the 8255 PPI, 8 bit parallel in,
and that was fed from some shift registers, serial clock to the keyboard,
data from / to the keyboard.
Some other bits were control I think. But was not the other half of
that 8255 used for the printer port?
--------------------------

Nope, the keyboard only. I have all the early PC schematics.

Or was the printer port just a latch?
--------------------------

The original PC-LPT was the circuit I presented years ago,
it was taken from a MGP video card 3BC Hex port LPT, and
it is representative of the original PC LPT card.

http://www.armory.com/~rstevew/Public/LPT/LPTskmtc_wid.html

OK, I just googled a bit I see you already knew this:
http://www.xs4all.nl/~ganswijk/chipdir/abc/keyboard/keyboard.faq
Version 0.9a IBM Keyboard/Scancode FAQ File Richard STEVEn Walz
rel 10 June 1994 *please retain this banner* rstevew@armory.com

Oh well ;-)
JP
-----------

Yup. I never say what I don't know.

-Steve
--
-Steve Walz rstevew@armory.com ftp://ftp.armory.com/pub/user/rstevew
Electronics Site!! 1000's of Files and Dirs!! With Schematics Galore!!
http://www.armory.com/~rstevew or http://www.armory.com/~rstevew/Public

 

[Jan Panteltje]

On a sunny day (Tue, 18 May 2004 01:16:55 GMT) it happened "R. Steve Walz"
<rstevew@armory.com> wrote in <40A964DD.7F4D@armory.com>:

Or was the printer port just a latch?
--------------------------
The original PC-LPT was the circuit I presented years ago,
it was taken from a MGP video card 3BC Hex port LPT, and
it is representative of the original PC LPT card.

http://www.armory.com/~rstevew/Public/LPT/LPTskmtc_wid.html
Good I see AEN is in decode too.

Good work
JP