|
Post by steve on Oct 14, 2021 9:02:49 GMT 1
This is really strange. We have had network printing successfully for years now but today it is coming up with a Windows message "Could not initialize printer."
CONFIG.TXT has not been changed since May: --- MOUSE = ON
WINDOW = 100
LPT1 = SEL:"\\OPS-1\OPS-INVOICE" RAW TIO:0
LPT2 = SEL:"\\OPS-1\OPS-HARDCOPY" RAW TIO:0
LPT3 = SEL:"\\SVR-1\OPS-PREPSHEETS" RAW TIO:0
---
The printers all work Windows, i.e. if I bring up a CMD window and type DIR >LPT1 is is printed.
The recent changes to the system have been changing Drive Mapping from \\SVR-1 (another workstation) to a NAS \\OPS-NAS
This workstation is still running vDos dated 07-MAY-2019.
|
|
|
Post by steve on Oct 14, 2021 9:24:09 GMT 1
The AUTOEXEC.TXT file has drive mapping
USE C: C:\OPS\ USE O: O:\ USE S: S:\
O:\ and S:\ used to be mapped by NET USE to a workstation and are now mapped to the NAS. (This mapping was changed a few days ago, but it seemed to work fine). I think the workstation was rebooted yesterday which is when the printer problems arose.
|
|
|
Post by steve on Oct 14, 2021 10:33:05 GMT 1
Could this have been caused by a Windows update being installed?
|
|
|
Post by Jos on Oct 14, 2021 11:05:06 GMT 1
The "Could not initialize printer" message indicates vDos could not connect to the specified printer. So for instance \\OPS-1\OPS-INVOICE isn’t valid (anymore). The name of OPS-1 or the printer share changed?
Better to use UNC references with USE, instead of mapped drive letters. USE O: O:\ isn’t conclusive.
Jos
|
|
|
Post by steve on Oct 14, 2021 11:34:35 GMT 1
It is strange that DIR >LPT1 from Windows cmd works (proving not a problem with hardware/connection) but vDos cannot see/reach the printer. No changes have been made to the printer sharing.
The drive mapping is probably irrelevant, it works with the NAS ok.
It could be that Win10 update 21H1 that was installed last night may have some side effects. We may have to rewind that to see if that cures the problem.
Steve
|
|
|
Post by Jos on Oct 14, 2021 11:40:37 GMT 1
What if you omit SEL:, so you get the Printer Selection dialog?
Jos
|
|
|
Post by steve on Oct 14, 2021 12:19:35 GMT 1
|
|
|
Post by steve on Oct 19, 2021 18:43:01 GMT 1
TO ANYONE READING THIS THREAD - IF you have experienced the same problem, the PLEASE leave a message together with the vDos version you were using AND how you cured it. Thanks, Steve
|
|
|
Post by dennis on Oct 19, 2021 21:12:49 GMT 1
Hi Steve -- We're having the same issue as you. We've uninstalled MS updates KB5005565 and KB4006670, but we still can't print to our shared Epson printer for our invoices and pick slips. No changes to any of our vDOS settings or how the printers are mapped (net use). If you come across with any ideas let me know and I will do the same.
Dennis
|
|
|
Post by Jos on Oct 19, 2021 21:30:10 GMT 1
What if you run vDos elevated? Add ADMIN=ON to config.txt so vDos will allow that.
Assuming you have something like LPT1 = SEL: "….
Jos
|
|
|
Post by jnoblin on Oct 19, 2021 21:33:53 GMT 1
I don't have this problem but there was a .net framework update released about a week ago. Might check to see if it is causing the problem. October 12, 2021-KB5005539 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 I had problems years ago with printing (not with vDos) and found it was caused by the .NET Framework update.
Nob
|
|
|
Post by dennis on Oct 19, 2021 21:54:17 GMT 1
What if you run vDos elevated? Add ADMIN=ON to config.txt so vDos will allow that. Assuming you have something like LPT1 = SEL: "…. Jos
|
|
|
Post by dennis on Oct 19, 2021 22:04:55 GMT 1
Jos -- Sorry, trying to getting use to the forum settings. So, I guess that I'm running an older version of vDOS because it rejects the 'ADMIN' keyword at startup. In the past I tried vDosPlus (2015.11.01), but could never get it to work. What version should I be running? Thanks.
Dennis
|
|
|
Post by Jos on Oct 19, 2021 22:11:42 GMT 1
That’s a no brainer: The latest version, now 2021.05.01.
Jos
|
|
|
Post by dennis on Oct 19, 2021 22:14:56 GMT 1
Jos -- Looks like I should be running version 2021.05.01 -- I've downloaded and run the setup. I will make the updates to the config file and see if it works, then add in the ADMIN keyword.
Dennis
|
|