Setup Leaves Windows .INI Files in Root of the Novell Server (96541)
The information in this article applies to:
• Microsoft MS-DOS operating system 6.0
This article was previously published under Q96541
If you run MS-DOS 6 Setup when you are logged onto a Novell server,
Setup may leave your Windows initialization (.INI) files in the root
This problem occurs when all the following conditions are exist:
• You are logged on as a supervisor or a user with full access
privileges to the root of the file server.
• You are using a shared installation of Windows (installed with the
SETUP /N command).
• Your Windows initialization files are in a user directory that is
being accessed with a search drive.
• You have installed the Windows-based optional utilities.
If these conditions exist, MS-DOS 6 Setup leaves the following
initialization files in the root of the Novell file server:
Setup also leaves the backup (.BAK) files for those files in the root
of the Novell file server.
Use one of the following techniques to correct this situation:
Do not use a search drive to specify the location of your Windows
initialization files. A search drive represents its drive letter as
"<drive>:." instead of "<drive>:\<pathname>." MS-DOS 6 looks at
"<drive>:.", changes to the root of the drive, and then looks for the
current (.) directory. This is why MS-DOS 6 writes the files to the
root of the server.
If you are logged on as a user without write access privileges to the
root of the file server (as is generally the case with a user on a
Novell network), the same approach as described in the second
technique applies. If you don't have privileges in the root directory,
the temporary initialization files (.$$$) are written to your user
directory. No changes are been made to your original initialization
files. You can safely delete these .$$$ files. Use the second
technique and then restart the MS-DOS 6 Setup program.
The following three .$$$ files may be left in your user directory:
If Setup detects that it did not need to modify one or more of the
initialization files, you may not have all three of these in your user
NOTE: This information applies to both the SETUP and SETUP /E
commands. (SETUP /E is used to install the optional components.)
| Modification Type:
|| Last Reviewed: