New
#11
Uh, well the thing is that the employee who uses that printer also does other stuff for the company, most of which needs networking/Internet. We're upgrading everybody to Windows 10, so I didn't think there would be any issue with it.
Easier to restart a COM port because of a bug than to give him a WHOLE SEPARATE COMPUTER just for occasional printing...
I also don't think the error has anything to do with the specific drivers. The Seagull ones did it too. Disabling the COM port and re-enabling it fixed the error, so it's a Windows bug if anything, not something Nice would be able to control.