***** charles wrote:
"Warren Block" wrote in message
...

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.

True but not for Windows 2000 Pro. The Windows they talk about
is 95 the consumer side. NT/2000/XP grew up to be the business
side which took over.

Well, yes, but you can't really expect them to have written instructions
for Windows 2000 five years before it existed. Windows NT came out in
1993, but it was pretty rare for a while.

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.

Yes, the startup page is disabled. The IP for the printer is set to
something but I can't figure out what it is. I wonder if I can get
LaserWriter Utility for Windows (95) to work in Windows 2000, if I can
even find it any more?

One of the links in my other post goes to the Windows 95 driver, which
looked like it included the utility.

The HP printers I have set up were at least 5 years old and more like
10. So they were not THAT much newer. The net box I am using has DHCP
built in (it assigns 192.168.1.100 to my Windows machine. But the
printer doesn't use it. The IP has to be hard coded to the printer.

DHCP came out in late 1993, so that's not surprising. That printer is
old. The manual shows that one of the ways the IP address can be set is
by pinging the printer.

I guess I could try to boot to Knoppix and see if I can get anywhere
with that. But that is for another day when I am not under the gun.

I'd start with the Win95 driver package; don't install the driver (if
you can avoid it), just run the utility from the archive.

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