INF: Trouble-shooting Win32s 1.1 Installation Problems

PSS ID Number: Q108721
Article last modified on 12-29-1993

3.10
WINDOWS

----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Win32 Software Development Kit (SDK) for Windows NT
   version 3.1
----------------------------------------------------------------------

SUMMARY
=======
The installation guide for Win32s from the Win32 SDK Final Release CD
recommends running Freecell to verify the installation. This article
contains some of the errors that may occur when trying to run Freecell. The
article also contains a list of corrective actions to help you reinstall
Win32s.

MORE INFORMATION
================

Trouble-Shooting Win32s 1.1 Installation Problems
-------------------------------------------------
One of the following errors may occur when running Freecell if the
installation was not successful:
   File Error: Cannot find OLECLI.DLL
   Win32s - Error:
   Improper installation. Win32s requires WIN32S.EXE and WIN32S16.DLL to
   run.
   Reinstall Win32s.
   Win32s - Error:
   Improper installation.  Windows requires w32s.386 in order to run.
   Reinstall Win32s.
   Error: Cannot find file freecell.exe (or one of its components)...
The following is a list of things to check when Win32s does not install
correctly:
 - If you have a printer driver by LaserMaster™, delete it or comment it
   out because it interferes with installing Win32s. Then reboot the
   computer so that the changes you made will take effect. After you
   successfully reinstall Win32s, you can then reinstall the driver or
   remove the comment characters. The reason the driver interferes with
   installing Win32s is that the LaserMaster drivers create a device
   "winspool". The extension is ignored when the filename portion of a
   pathname matches a device name. As a result, when Setup tries to write
   to WINSPOOL.DRV, it fails, because it attempts to write to winspool. In
   fact, any Win32 application that tries to link to WINSPOOL.DRV will also
   fail, but most Win32 applications that print under Win32s do not use the
   WinSpool APIs since they are not supported in Win32s. As a result, you
   can usually just disable this driver while installing Win32s and then
   re-enable it afterwards.
 - Delete the \WIN32S directory and all files in that directory, the
   \WIN32APP directory and everything in that directory, W32SYS.DLL,
   W32S16.DLL, WIN32S.EXE from your hard drive. Although it is possible to
   install Win32s on top of an old installation of Win32s, it is better to
   remove the old files before installing the new ones.
 - Edit the WIN32S.INI file on your hard drive. Change the line(s)
   SETUP = 1 to read SETUP = 0.
 - Make sure paging is enabled. Go to the Control Panel, select the 386
   Enhanced icon, click the Virtual Memory button, and click the Change
   button. Verify that the drive type is not set to "none". The type can be
   set to either "temporary" or "permanent".
 - Make sure Share is enabled. Edit AUTOEXEC.BAT and add the following if
   it is not already there:  C:\DOS\SHARE.EXE
 - Reboot your computer and re-install Win32s.
If you still get errors when running Freecell, compare the binaries on your
hard drive with those on the CD. Use the MS-DOS program FILECOMP.EXE,
COMP.EXE, or FC.EXE and do a binary compare. For example, if you have the
Win32 SDK CD type:
   fc /b <windir>\win32s\w32s.386 <cd>:\mstools\win32s\nodebug\w32s.386
Or, if you have the 32bit Visual C++ CD type:
   fc /b <windir>\win32s\w32s.386 <cd>:\msvc32s\win32s\retail\w32s.386
The results of the compare will be, "FC: no differences encountered" if the
binaries were correctly installed. If the binaries are not the same, you
might have a bad copy of the files or a bad CD.
As a last resort, you can try re-installing Win32s from the 32bit Visual
C++ CD. There seems to be a slight difference between the SETUP.EXE program
on the Win32 SDK CD and the SETUP.EXE on the 32bit Visual C++ CD. If you
try installing from the 32bit Visual C++ CD, you should NOT remove the
\WIN32APP or \FREECELL directories or any of the Freecell files. The 32-bit
Visual C++ CD does not contain Freecell.
NOTE: Using Freecell Help will generate errors, in particular, "Routine Not
Found" or "Help Topic Does Not Exist." This has nothing to do with whether
Win32s is installed correctly or not.
FREECELL.HLP was meant to be used with WINHLP32.EXE. FREECELL.HLP uses the
advanced features of WinHlp32 for full-text searching. WINHELP.EXE, which
runs on Windows 3.1, does not support this. As a result, every time
FREECELL.HLP tries to bind the Find button to the Full Text searching APIs,
it fails, and WinHelp pops up the message box. You can still read most of
the information in the help file. You can use the Search button to do
keyword searches.

Additional reference words:
KBCategory:
KBSubcategory:
Copyright Microsoft Corporation 1993.