WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

1.3K

At work, an old machine running Win2k and an Atari emulator is still used because reasons. The emulator always prints to the standard printer and that worked fine for decades.

Now our new masters, in their wisdom, decided to put all of our file servers into the cloud with SMB shares version 3.1.1 (Through a shaky 6-30 Mbit connection no less but that's another story.) The old W2k machine only speaks SMB1 and needs to be replaced. I got a replacement with a COM port (Yes we need that too) and got everything to work except for the printing. The software sends raw PCL/Epson code to the parallel port of the emulated Atari. (I should know, I wrote it)

This used to 'just work', now the print jobs just seem to vanish into thin air. Not even a blip in the spooler. I thought of redirecting LPT1: to an IP address, because our printers are just listening to raw data at port 9100.

There's a syntax on the net, something like 'net use LPT1: \server\blabla' I tried that after work today and got error 66, then gave up for today. I'm spent and will probably break more than I can fix. Just wondering if any of you have encountered a similar challenge and can point in the direction of a solution.

At work, an old machine running Win2k and an Atari emulator is still used because reasons. The emulator always prints to the standard printer and that worked fine for decades. Now our new masters, in their wisdom, decided to put all of our file servers into the cloud with SMB shares version 3.1.1 (Through a shaky 6-30 Mbit connection no less but that's another story.) The old W2k machine only speaks SMB1 and needs to be replaced. I got a replacement with a COM port (Yes we need that too) and got everything to work except for the printing. The software sends raw PCL/Epson code to the parallel port of the emulated Atari. (I should know, I wrote it) This used to 'just work', now the print jobs just seem to vanish into thin air. Not even a blip in the spooler. I thought of redirecting LPT1: to an IP address, because our printers are just listening to raw data at port 9100. There's a syntax on the net, something like 'net use LPT1: \\server\blabla' I tried that after work today and got error 66, then gave up for today. I'm spent and will probably break more than I can fix. Just wondering if any of you have encountered a similar challenge and can point in the direction of a solution.

(post is archived)

[–] 1 pt (edited )

Windows: Re-inventing Unix, poorly, since 1985

[–] 1 pt

After recruiting/poaching Dave Cutler from Digital, they really had something with NT. They slowly threw it all away after Windows 2000/NT 5 (IMO).

[–] 2 pts

Agree. NT shared a lot from the OS/2 collaboration days and was rock solid. I was an OS/2 guy until it was obvious Warp had been abandoned. It's not about technical innovation anymore in Redmond. It's about control, lock-in, and data harvesting. My work Windows 10 box is such a pitiful regression of kludgery.