If you include a third-party driver in the Windows 95 Preinstallation
Express Mode using the technique described in the OPK User's Guide, you
might receive the following error during preinstallation:
Cannot open <INF filename>. The file may be missing or damaged or
there may not be enough memory to continue. Free some memory or
increase your swapfile size, and then try running Setup again.
After clicking OK, preinstallation stops, and returns to a DOS prompt. The
driver might install properly under different conditions, in either audit
mode or normal operation.
One of the following causes might apply:
- SIGNATURE line in the vendor's .inf file was incorrectly parsed, as well
as a [load_inf] section in the Custom.inf file.
- An .inf file is missing or damaged.
To resolve the first cause listed in the previous section, you can do one
of the following:
- Change the SIGNATURE line in the vendor's main .inf file to read as
You will find this line in the [Version] section of the .inf file.
- Remove the name of vendor's .inf file from the [Load_Inf] section of the
To resolve the second cause listed in the previous section, you need to
verify that the vendor's .inf file is present and formatted correctly.
Replace the .inf file with a known good copy if necessary.
Windows 95 driver .inf files might have one of the following SIGNATURE
The Custom.inf section [Load_Inf] causes the .inf files listed to be loaded
into memory and parsed during the Hardware Detection phase of Setup. During
this phase, the Signature="$Windows 95" line is parsed incorrectly and
considered invalid. The .inf file is not loaded, and Setup returns an
In most cases, the [Load_Inf] section is not required to properly detect
and install software support for third-party hardware devices.
Drivers with either of the two preceding signatures in the .inf file
install correctly under Windows 95, except in the early Hardware Detection
phase noted above.