Microsoft KB Archive/90993

= Problems Caused by Setup Changing LASTDRIVE= Statement =

Article ID: 90993

Article Last Modified on 9/24/1999

-

APPLIES TO


 * Microsoft Windows for Workgroups 3.1

-



This article was previously published under Q90993



SUMMARY
Windows for Workgroups Setup changes the &quot;LASTDRIVE=&quot; setting in CONFIG.SYS to LASTDRIVE=Z when no other network is present, or to LASTDRIVE=P when installed with Novell NetWare as the &quot;other&quot; network.

If your custom network setup depends on certain drive letters always being available, the above changes may cause problems.



MORE INFORMATION
For example, if your existing LAN Manager logon script depends on being able to use certain high drive letters during the logon, and the Windows for Workgroups Setup changed &quot;LASTDRIVE&quot; from &quot;W&quot; to &quot;P&quot;, you may receive the following errors:


 * Error 85 - local device name already in use
 * Error 15 - System cannot find drive specified

Changing the LASTDRIVE= statement does not ordinarily cause problems like this. If you are running Novell NetWare and LAN Manager, and experience drive mapping problems after installing Windows for Workgroups, try setting the LASTDRIVE statement in the CONFIG.SYS file to the previous value, which should be in CONFIG.00x.

The NetWare product included here is manufactured by Novell, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: 3.10 net ware novell last drive

Keywords: KB90993

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.