ClassicConnect

[parasquared]

i was setting up a Windows 95 machine in 86Box, then while printing something using the emulated PostScript printer, i had an idea. how old is the JetDirect protocol, anyway?

for context, HP's JetDirect system was a line of either external units or addon cards for their printers that would turn parallel (in the case of external models) printers into network-equipped ones. turns out, this protocol is pretty old, and my HP Photosmart from ~mid-late 2000s does actually still support it over Wi-Fi. so i thought, what if i got a driver for Windows 95 and tried printing to it over the network?

turns out, this works! here's how i did it:

- grab a JetDirect driver (i used this driver disc)
- on this particular driver, select "Specify a printer by address," then enter the printer's IP address

- when asked, go with the default TCP/IP communication mode

- in my case, i said Yes when asked this. i'm not sure if there's some reason not to pick it, but if so let me know

- when asked for a printer driver, i selected the HP PaintJet XL 300, as that's also an inkjet printer, and it happened to work. you may need to pick something else, so try experimenting with drivers i suppose

- with any luck, you should be able to get a printer added and get a test page like this:


boom. now you can print on your printer from a Windows 95 machine. the driver disc i linked also has drivers for classic Mac OS and Unixes, although i haven't tried those. apparently the protocol is even still supported in modern HP printers, so that might be a fun thing to try.
_________________
- parasquared

"In space there is no center, we're always off to the side"
- Ballad of Reverend War Character, Silver Jews

[parasquared]

i just tried doing it under Mac OS 9, however i think due to SLiRP the os doesn't detect printers on the network, and i'm unable to put an IP in manually. maybe if i can be bothered to set up my titanium PowerBook again i'll try it on there
_________________
- parasquared

"In space there is no center, we're always off to the side"
- Ballad of Reverend War Character, Silver Jews

[europa]

So I tried this on my ThinkPad 760 and I kept getting an error about differing configurations between the printer and the computer

I have Solaris machines (of course) and also some Macs laying around. I'll try those at a later date. I'm hoping for more luck with the Sun machines, as I've always wanted to try printing from those
_________________
Your System ate a SPARC! Gah!

[VCSMaster]

FWIW If your printer supports PostScript, a generic PostScript driver will work fine to control them as well, since the protocol has stayed virtually the same and has largely retained backwards compatibility.

There is a strong liklihood that every printer you are liable to run into in the modern era also supports PCL6. A generic PCL6 driver probably exists for Windows 9x, and if not, I think there is a good chance that a PCL5 driver will probably work.

Typically, given my collection, I am interested in doing the reverse, using very old printers on (comparatively) new machines. You may have spotted my thread about running daisy wheel stuff in Windows XP. That said, I have also gotten my 2012 Toshiba eSTUDIO 5520C to print from Windows Me over the network.

[europa]

So coincidentally that was my next course of action! I've had luck installing generic PCL drivers in the past, and it just so happens that the LaserJet 4 driver on Windows 95 is a good generic PCL5 driver to use.

I also found this website, which details how to set up an LPR spooler on 95 to allow you to add IP printers through the Windows Add Printer wizard, as Windows 95 doesn't support that by default (it only supports adding local printers, or printers accessible through a Windows share).

I was able to get a test page printing with little fuss after that!
_________________
Your System ate a SPARC! Gah!

[VCSMaster]