Uncontrollable drive mapping of I: to SYS

[peobody]

I recently had to reinstall Client 3.3 on a Win98SE machine. Before the reinstall, "I:" was used by an external Zip. Now "I:" is getting mapped to SYS at startup. First network drive is set to "G:". This mapping does not appear to be login related. I can disconnect it, login as a different user then log back in as myself without the map reoccurring. Besides, no login scripts exist. I've deleted the Zip drive and uninstalled its drivers then reinstalled from scratch with no change. Tried temporarily setting it to "F:", but "I:" still gets mapped to SYS. I really need it on "I:" as it is a shared drive used by several batch files for file maintenance. Any help would be appreciated.

 

[dan]

It is possible it is mapped in Windows and not in Novell. In Window Explorer, choose tool \ disconnect network drive. Choose I and delete it.
Other than that, the network login looks at:
Container login script
Profile login script
User login script or default login script
Look at each of these.
While you cannot see the default login script, you can put NO DEFAULT in one of the first 2 scripts.
Dan

 

[peobody]

Disconnect via Windows Explorer hasn't been permanent. A container login script at the OU object where all user objects reside, containing NO_DEFAULT as the only entry, didn't solve the problem. It appears that the default login script still executes regardless of whether that container login script exists or the "Run Scripts" option in Login/Advanced is disabled. To confirm this, I disconnected the drive mapping of "G:" to SYS and restarted. As I suspected, "G:" was mapped to SYS instead of "I:". Since "G:" is designated as the first network drive and "H:" is mapped to /USERS, the default login script was assigning the first available drive,"I:", to SYS. Now I'm wondering why NO_DEFAULT isn't working and why a reinstall of the same Client caused this problem since "G:" has always been mapped to SYS. May never know the answer to either one of those.

 

[TheLad]

Do you have any LASTDRIVE statements in your C:\CONFIG.SYS? If you do, rem them out -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------