We are in transition migrating from Novell to NT. AREV is on an NT server and print services have recently been moved to an NT print server. The WINDOWS95 workstations have both the Microsoft and Netware clients installed. Our AREV applications issue NET USE commands on startup, but include menu processes that allow the users to select another printer (more NET USE commands). The commands are:

    PERFORM 'SUSPEND EXIT NET USE LPT2: /D'

    PERFORM 'SUSPEND EXIT NET USE LPT2: \\NTSERVER\PRINTER'

    PERFORM 'SETPRINTER 2'

With the NETWARE client installed on the workstation we experience various problems with the NET USE commands where the NET USE delete will not delete the connection or we have multiple LPT2 connections which will cause the workstations to lock up and require rebooting.

We removed the NETWARE client on a few workstations and testing has shown that many of the abnormalities mentioned above disappear, but when the user tries to select another printer and issues more NET USE commands the workstation will still lock up. The first set of NET USE commands will work on startup, but the if we try to issue another set the workstation bombs.

The same processes work perfectly from a Windows NT workstation. We see the OS messages "The Command completed successfully", "LPT2 deleted successfully", etc.

Any ideas?

Try calling a bat file instead of executing the command directly.

Investigate the use of the /PERSISTENT=YES flag on the NET USE … LPT1… command - this can be called ahead of launching AREV from a batch file.

There are some hints in this regard at www.jsiinc.com in the registry hacks and tips section

Steve

View this thread on the forum...