3.12 has a mind of its own....

[aarono]

Having issues with dear old 3.12....

1. Have a few Win98SE workstations that are running the latest Novell Client. The users have shortcuts on their desktop that point off to a Windows 2000 server, and work fine, but when they log off and back on again, the shortcuts dissapear and I have to keep adding them back. Anyone got any ideas as to how to stop this from happening? If I remove the Novell Client all is well and no issues. Unfortunately I have to run the Novell Client otherwise there are issues with the mission critical app that can only run on Novell 3.12

2. One or two different Win98SE workstations are fine with regard to desktops, but when the user tries to open a document on a Windows 2000 mapped drive, Novell 'takes over' the drive mapping, and claims it as its own, effectively stopping the user from opening the document, because the drive mapping is suddenly changed from u:\files (where u: = \\windows 2000 server\shared folder) to u:\yucky Novell (where u: = \\Novell 3.12 server\SYS)

Any helpful ideas gratefully accepted!!

Cheers

 

[AnanthaP]

Its probable that there is Novell logon (oops sorry login) script running that has taken over the mappings. In this case, it might be part of your "mission critical" app that can run only on NW 3.12.

You can check this out with your administrator. If you don't need the drive mapping (u: in your example), you could get the administrator to create a custom login script with no entries. (This will supersede all other login scripts).

For W2000, if your application doesn't expect a single drive letter (say u please see whether you need to use drive mappings at all.

Also, to solve problem no 1, a work around could be a batch file in the "StartUp" folder that forcibly restores drive mappings to what u: want it to be. Eg:

Net use u: = \\windows 2000 server\share name\folder ...

HTH.

End of mail.