Knowledge Base

Problems Accessing or Writing to the SYSTEM.INI File

Article ID: 119782

Article Last Modified on 12/5/2003

Microsoft Windows 3.1 Standard Edition
Microsoft Windows 3.11 Standard Edition
Microsoft Windows for Workgroups 3.1
Microsoft Windows for Workgroups 3.11

This article was previously published under Q119782

SYMPTOMS

Programs that modify the SYSTEM.INI file during installation stop responding (hang) or produce an error message similar to the following:
Cannot read file <path> SYSTEM.INI
When you use MS-DOS Editor (EDIT.COM) in an MS-DOS session to edit the SYSTEM.INI file, the system hangs.
You are unable to modify the virtual-memory settings on your computer.

CAUSE

Close-Up version 6.0 from Norton-Lambert assigns write protection to the SYSTEM.INI file so that other applications cannot write to it.

WORKAROUND

The only work around is to disable Close-Up with the following steps:

Open the AUTOEXEC.BAT file using a text editor, such as Windows Notepad.

Remark out (using the REM command) the statement that loads CHOST.EXE.

Change

     <path>\chost.exe

      rem <path>\chost.exe

Save your changes and reboot your computer.

MORE INFORMATION

Close-Up version 6.0 from Norton-Lambert is a modem host program that uses "unobtrusive technology." This technology allows Close-Up to operate without having its setup program make changes to the SYSTEM.INI file. After Close-Up is running, it makes changes to the copy of the SYSTEM.INI file that is in memory. Close-Up then locks the SYSTEM.INI file so that no other changes can be made.

Close-Up is manufactured by Norton-Lambert, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: setup err msg chost

Keywords: KB119782