Recently changed out a computer on the Network using Windows 98 SE running under Netware 3.12. Configured the computer the same as the others on the Network. Accessing Arev from a shortcut on the Desktop. When you click the Batch program the screen flickers then goes back to to Desktop, if you unclick on the close at exit the screen flickers then goes to the Dos prompt M:\MM<exit. No error messages appear, does anyone have any advice where I could check next.

Thank You,

Mark

Did you install the Novell client? Is the LH NLM in use?

List the commands in the bat file, open a DOS command window and type in each command in the bat file and see what responses you get. Be sure to change to the working directory as specified in the shortcut first.

Did you install the Novell client? Is the LH NLM in use?

List the commands in the bat file, open a DOS command window and type in each command in the bat file and see what responses you get. Be sure to change to the working directory as specified in the shortcut first.

Thank you for your reply. This system has been in use since 1990, I believe the Novell Netware was upgraded in 1998, this was done by a third party, I can't say whether the LH or NLM was installed I do see files with the extension NLM. We are using the Microsoft Client for Netware Networks, I believe the reason was printing issues with the Novell Client. We have 15 computers using this configuration, all had been working fine untill we upgraded the one station. Could it be a Windows vs Dos issue? The computer is a Gateway. The batch program is: cls

   Arev (s)

   cls

   exit

This is the original Batch program to call Arev, Am I correct if I assume Arev (s) is calling AREV.EXE with no parameters? ran each command from the working folder and got the same result it goes immediately to exit. Clicked directly on AREV.EXE same results. Removed and reinstalled Microsoft Client for Netware Networks, same result. Any help would be appreciated.

Thanks,

Mark

Forgot to mention using AREV 1.16. Looking through the discussions I guess the NLM you were asking about is for AREV not Novell, is it available for AREV 1.16??

The minimum release for the NLM is v2.03 which I don't think is supported or available so you'd have to step up to v2.12 at the very least to use it.

I would say just back up any local files like documents or whatever and just ghost the drive from one of the workings workstations.

Otherwise I would check or copy from a working system:

CONFIG.SYS

AUTOEXEC.BAT

also check the settings on _DEFAULT.PIF or DOSPRMPT.PIF

I'd also go through any of the Novell login scripts as it maybe looking for or mapping to directories on the C: drive that don't exist.

I'm assuming the workstation in question is attaching to the Novell server - you can see and access all the mapped drives and directories that the login has rights to?

Are you able to print from the workstation? From the command prompt type:

SET ] lpt1:

Map ] lpt1:

And compare the printouts from the same commands run on a working station with the same login. Most relevant are the COMSPEC, PATH, search path and network map settings.

Thanks very much Warren,

Checked the autoexecbat and made a few changes and the workstation will login now, it was always seeing the drives on the network.

Thanks again,

Mark

View this thread on the forum...