Arev on NT server, accessing from win95 and printing (AREV Specific)
At 22 JUL 1999 04:46:16PM DSJones wrote:
1) Upon using a PIF on the win95 client, it takes an unusable amount of time to open AREV. Thats the first problem.
2) Our people used to hit the enter key when accessing Novell, and there lable would print right out. Now that we moved the AREV app to NT they have to wait at least a minute before they even know its working on printing. What am I doing wrong?
The NT service is installed and the performance pack, the config.nt has files=200. Whats next? Maybe the time out should be set to something shorter than it is.
At 22 JUL 1999 11:04PM Jocelyn Amon wrote:
Regarding the amount of time logging on - we had the same problem but then disabled the virus checker, end of the long wait!
It does take appear to take NT awhile to tell the printer to kick off the print job. I am currently working on a solution to the problem within the an Arev NT print utility I am developing. The answer appears to be to issue a NET disconnect then reconnect command - use the / YES flag to prevent unwanted output messages from NT (ie. Are you sure?).
I don't have all the info at my fingertips but if you want to know more email me and I'll be more specific.
Jocelyn