|
|
Post by dennis on Oct 19, 2021 22:28:46 GMT 1
Jos -- Got 2021.05.01 running will all the old setting then added the ADMIM = ON. Still the same issue -- no printing to the shared Epson printers.
Dennis
|
|
|
|
Post by Jos on Oct 19, 2021 23:25:25 GMT 1
Dennis,
You started vDos elevated?
ADMIN = ON doesn't do that, it only allows you to do so...
Jos
|
|
|
|
Post by steve on Oct 20, 2021 0:25:12 GMT 1
|
|
|
|
Post by dennis on Oct 21, 2021 14:36:19 GMT 1
Dennis, You started vDos elevated? ADMIN = ON doesn't do that, it only allows you to do so... Jos Hi Jos, When you say elevated does that mean to run vDOS as the administrator (run as administrator)? If that's true, then when I try to 'run as administrator' the app doesn't start. Dennis |
|
|
|
Post by Jos on Oct 21, 2021 15:00:00 GMT 1
Yes, I suggest starting vDos as administrator.
Though no idea why your app would then not start.
Jos
|
|
|
|
Post by dennis on Oct 21, 2021 15:33:45 GMT 1
Jos,
I keep trying, but it still won't start under 'run as administrator' -- I'll do some research on that and get back to you. The following is the message I get from the DOS app when I try to print.
A dialog box comes up saying -- Could not initialize printer; \\FlorinServer\Invoice. The invoice Epson printer is set-up on the server using LPT2 and is mapped using 'net use'; individual workstations have the same printer set-up. I just can't figure out why the connection to the printers are failing, even after removing those two MS updates.
Dennis
|
|
|
|
Post by dennis on Oct 24, 2021 18:28:59 GMT 1
Jos,
This what I tried -- brought up an Administrator Command Prompt; remapped two drives and three LPTx printers using NET USE; changed directories to where vDOS.exe is located then ran the app. Our app came up find and is now running under administrator (ADMIN = ON has been added to the config file). Tried printing to the LPT2 & LPT3 printers with the same issue coming up. Could not initialize printer; \\FlorinServer\Invoice. Any suggestions on what to do next?
Dennis
|
|
|
|
Post by Jos on Oct 24, 2021 19:19:37 GMT 1
Can you print at the Windows Command Prompt, e.g. COPY some_file LPT2?
Or directly COPY some_file \\FlorinServer\Invoice?
Jos
|
|
|
|
Post by dennis on Oct 24, 2021 20:49:25 GMT 1
Jos,
I did both of your suggestions -- each printed on the LPT2 printer.
Dennis
|
|
|
|
Post by Jos on Oct 24, 2021 21:02:36 GMT 1
Assuming you use the RAW option, you could try the same suggestions for vDos printing, something like:
LPT2 = "COPY" [HIDE] #LPT2.asc \\FlorinServer\Invoice
Until MS solves this issue…
Jos
|
|
|
|
Post by dennis on Oct 26, 2021 15:03:50 GMT 1
Jos,
Back at it again -- I commented out the following --
REM LPT3 = SEL:"\\FlorinServer\Pickslip" RAW
REM LPT2 = SEL:"\\FlorinServer\Invoice" RAW
Replaced with --
LPT3 = "COPY" [HIDE] #LPT3.asc \\FlorinServer\Pickslip
LPT2 = "COPY" [HIDE] #LPT2.asc \\FlorinServer\Invoice
Got error message --
Could not start
C:\vDOS - 2021\vDOS\COPY
Do I have the updated lines miscoded or do I need to build a sub-directory called 'COPY"?
Dennis
|
|
|
|
Post by Jos on Oct 26, 2021 17:07:46 GMT 1
Sorry, my bad.
Forgot to specify CMD and discovered that isn’t trapped by this directive (have to look into that).
For now it would have to be:
LPT2 = "%ComSpec%" [HIDE] /C COPY #LPT2.asc \\FlorinServer\Invoice
For first testing, so the command window stays open and visible:
LPT2 = "%ComSpec%" /K COPY #LPT2.asc \\FlorinServer\Invoice
Jos
|
|
|
|
Post by dennis on Oct 26, 2021 19:58:22 GMT 1
Jos, I tried that first testing command line and could see the copy line in the command prompt -- and it printed! Went to the command where it doesn't throw up the prompt and it again printed just fine. So, what you suggested worked and I'm one happy camper!  So, this is a work around until MS pushes another fix out, but do you know what the cause was? Dennis |
|
|
|
Post by Jos on Oct 26, 2021 20:20:29 GMT 1
Glad it worked.
MS seems to be in the process of fixing vulnerabilities in network printing. Hopefully they get it right shortly…
Jos
|
|
|
|
Post by steve on Oct 27, 2021 17:15:24 GMT 1
Well done Dennis & Jos!!!
Do you still need the ADMIN = ON in the config file?
Steve
|
|
So, this is a work around until MS pushes another fix out, but do you know what the cause was?