We are running AREV 3.12 in Novell 4.1 with proper NLM installed and have had no problems in Windows 95, but are beginning to use Windows NT on a few workstations. Trying to print from the AREV application on the NT workstation causes the local port to become disabled. After exiting AREV application the printer is also not available any longer for any Windows application. Have deleted and reinstalled print driver with no effect. Get no messages that anything is wrong when trying to print from within the AREV application, but after leaving and trying to print from Windows receive message that the system cannot find the path to LPT1. Help is appreciated.

Two ideas.

(1) From shortcut run

FORCEDOS C:\AREV C:\AREV\AREV.EXE …..

(2) Try PDISK PRN in your VOC LOGON script

Steve

PS You may need to (in a batch file which calls your

AREV app call ahead of Arev NET USE LPT1 …devicename /PERSISTENT=Y

to get the printer to work reliably all the time.

Many thanks for the assist. After some experimentation your suggested solution of PDISK PRN worked. We execute this statement in each defined printer just before the basic PCL program call. Thanks again.

Your solution worked until we tried to print to a file. When the print PCL file is called it redirects the output back to LPT1. Final solution was to remove all "hardware" instructions from the printer initialization string and simply run the PCL program by itself. In our applications (PWS IDEAS - international accounting system) we must remember that NT takes over the hardware calls from the application and some of the extras added for hardware control are simply not needed. In the future I will approach problems with NT by first removing hardware instructions rather than adding them. Thanks again for your assistance, it really helped get us on the right track.

View this thread on the forum...