***** charles wrote:

That's what is making it so difficult, getting anything Apple to work
in a Windows world.

At the time that printer came out, there wasn't much of a Windows world.
In 1994, there was Windows 3.1, and most people were still running DOS.

Apple has always seen the Microsoft world as "the enemy".

I would say that as "Microsoft has always seen the world as their
enemy", but it works out the same way.

Problem is MS has 95 percent of the market. If it would realize that
it is better to work with them than against them Apple would get a lot
farther.

The manual for that printer actually has very detailed installation
instructions for the most popular systems and networks of the time, Mac,
DOS, Windows, Novell, and Unix.

Just plug it in and it works, that should be the goal.

There were initial steps in that direction at the time, but it was just
getting started.

Linux is having that problem now but it is getting better. I went
into adding all the extras in the add/remove location so I am sure
that if it is there, I have it installed. I always thought that
AppleTalk was a seperate protocol that wasn't needed if the printer
was a tcp/ip postscript printer. Guess I have more reading to do. I
have set up HP net printers that were a LOT easier. Set the IP and
install the client software and go.

I bet those HP printers were a lot newer, also. From what the manual
for the 16/600 says, it does not need AppleTalk or EtherTalk, but should
handle TCP/IP fine. It probably does not support port 9100 printing,
so you should set it to lpr/lpd. And the manual suggests that it prints
a startup page showing configuration; maybe that's been disabled,
though.

--
Warren Block * Rapid City, South Dakota * USA