Chuca, (off-topic) of running Windows 95 programs on Windows 3.1
Not that straight forward, so for those you know that want to,
then either dig into it or ask a computer type for help.
Send to printer this post for reference or to show someone.
As I mentioned, ok for me to experiment since for my small hard disk
I have backed'up twice on Zip drives, and data corruption for me ok.
Follows are general information, and at the end of this post are
two Microsoft official web links.
Microsoft Win32s
Win32s is a Microsoft product that allows 32-bit applications, such as
Transcend, to run on 16-bit operating systems (Windows 3.1x and Windows
3.11 for Workgroups). If you wish to run Transcend on one of these
operating systems, you must install Win32s first. You can download a
copy of Win32s by clicking here.
If you are running on Windows NT or Windows 95, you do not need to
install Win32s because these are 32-bit operating systems.
Installing Win32s v1.30
-----------------------
1. Download OLE32S13.EXE (3,072,788 Bytes) into a temporary directory.
(ie. c:\install)
2. With the File Manager open the temporary directory.
3. Double click on OLE32S13.EXE
4. Double click on Install.bat
5. Follow the instructions from the setup program.
Win32s v1.30 is now installed and you will be able to run Win32
applications.
Extra Information for Windows 3.1x Installations
If you are running Windows 3.1 or 3.11 (Windows for WorkGroups), you can
still install the Commander client software as described in the PC
installation instructions, but first you will need to download the
Win32s (32-bit) extensions if you do not already have them. If you do
already have these installed (WIN32S and OLE32) then you should make
sure that you have version 1.3. You can check which version you have by
looking in the file WIN32S.INI in your WINDOWS\SYSTEM directory - if you
have version 1.3, it should contain the lines:
[Win32s]
Version=1.30.xxx.x
If you already have Win32s but it is the wrong version, the best thing
to do is to remove it completely - see further instructions.
Now you can install Win32s as follows:
1.Run the self-extracting file WIN32S_S.EXE which you downloaded earlier
(use 'File' then 'Run' from Windows Program Manager). This will extract
a sub-directory, WIN32S_S (which itself contains a sub-directory called
SETUP, containing three sub-directories, DISK1, DISK2 and DISK3) into a
directory of your choice on your hard drive. If you are installing
Win32s on a network, then it is best to make sure that all users are
logged off before you start. 2.Now run the file
WIN32S_S\SETUP\DISK1\SETUP.EXE. 3.If you already have an old version of
Win32s which you have not removed as described above, it will prompt
you, and should overwrite the old version. 4.You will get a message
telling you if Win32s has been successfully installed. OLE32 is also
installed at the same time, unlike previous versions of Win32s.
Finally, you can install the Beilstein Commander:
1.Download the client software if you have not already done so. 2.Run
the self-extracting file bc40_set.EXE. You will be prompted for a
directory to unzip the files to. Six further sub-directories will be
created; these are 'Disk1' to 'Disk6'. Run the file
bcsetup\Disk1\Setup.EXE to start the InstallShield Wizard. 3.The
InstallShield Wizard starts up. It automatically detects the version of
Windows you are running, and will warn you if you are running the wrong
version of Win32s. 4.You can now choose whether to do a standalone or
network installation; see the installation instructions for Win95; from
this point onwards, the procedure is very similar.
Removing Win32s
If Win32s has not installed properly, you may want to remove it and
reinstall. You can check to see if Win32s is properly installed by
running the Freecell program that can be installed at the same time as
Win32s. Freecell is a 32-bit game program, and it will not run if Win32s
is not properly installed.
1.In your C:\WINDOWS directory, locate filename SYSTEM.INI. Double-click
on SYSTEM.INI to open the file in Notepad. 2.Within SYSTEM.INI, locate
the section beginning with the header [386Enh]. Delete the following
line from the [386Enh] section:
device=c:\windows\system\win32s\w32s.386
3.Delete the following files from your C:\WINDOWS\SYSTEM directory.
W32SYS.DLL WIN32S16.DLL WIN32S.INI
4.Delete the entire WIN32S subdirectory from your C:\WINDOWS\SYSTEM
directory. 5.Exit and restart Windows.
If a message displays stating that you cannot remove Win32s files, exit
to the MS-DOS prompt and completely remove Win32s.
4. Delete the following files from the <WINDOWS>\<SYSTEM> subdirectory
or from the SYSTEM directory in network installations:
W32SYS.DLL
WIN32S16.DLL
WIN32S.INI
WINMM16.DLL
5. Delete all the files in the <WINDOWS>\<SYSTEM>\WIN32S subdirectory or
the <SYSTEM>\WIN32S subdirectory in network installations. Then delete
the WIN32S directory itself.
The above changes will take effect the next time Windows is run.
NOTE: <WINDOWS> refers to the Windows installation directory. On a
networked Windows installation, the system directory may be located on a
shared remote volume. If you are removing only WIN32s from your machine,
then you do not need to remove the shared files in <SYSTEM> and
<SYSTEM>\WIN32S. Before removing these files from the shared network,
make sure that all users that use WIN32s have removed the references to
WIN32s from the SYSTEM.INI file.
------------------------------------------------------------------------
Removing Win32s:
----------------
The following steps can be taken to remove Win32s v1.25a from your
Windows 3.1x or Windows for Workgroups 3.1x environment.
1. Remove the following line from the [386Enh] section of your
system.ini file. The sysedit.exe application in you /windows/system
directory will open an ascii editor to all your system files.
device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386
2. Modify the following line from the [BOOT] section in the
SYSTEM.INI file:
drivers=mmsystem.dll winmm16.dll
to the following (remove winmm16.dll):
drivers=mmsystem.dll
3. Delete the following files from your c:\windows\system subdirectory or
from the SYSTEM directory in network installations:
W32SYS.DLL
WIN32S16.DLL
WIN32S.INI
4. Delete all files in the c:\windows\system\win32s subdirectory.
5. Delete the c:\windows\system\win32s directory
6. Reboot your machine.
Your system is now Win32s free. You will not be able to run Win32
applications.
microsoft.com
microsoft.com
microsoft.com |
