This optional service provides users the capability of running
Microsoft Windows 95 and Windows 98 sessions on
SCO OpenServer(tm).
These release notes provide
important information about SCO Merge and
pointers on where to find further information.
RAM requirements are determined by how many simultaneous DOS or Windows
sessions are used.
A single Windows 95 session can be run on a standard
32MB SCO OpenServer system.
For best performance for a small number of Windows 95 or 98 sessions,
64MB is recommended.
SCO Merge itself is shared by all users, but each user must install
a separate copy of Windows and Windows applications.
Supported versions of Windows:
- Windows 95 "classic" (aka "retail")
- Windows 95 OSR2
- Windows 98
- Windows 98 second edition.
- Windows 98 Upgrade CD
SCO Merge does not support the following:
- Installation from a Windows "Companion" CD is not supported.
- Installation from a pre-installed native partition is not supported.
- Upgrading existing installations of Windows 95
to Windows 98 is not supported.
- Other Windows "upgrades" may not work.
For Windows 95 you must also supply a matching Windows 95 boot floppy
(also known as a Windows Startup Disk). (You can also use a "dd" image
file of such a boot floppy instead if you do not have a floppy drive
in the machine you are installing on.)
If you have a bootable Windows 98 CDROM, you do not need a boot floppy.
If you do not have a bootable Windows 98 CD, you must supply a Windows
98 boot floppy.
Note:
SCO Merge only supports the "Windows 95 to Windows 98 Upgrade" CD
for fresh installation of Windows. Plus in order to install Windows
from this you must have a qualifying Windows 95 installation CD to prove
that you are allowed to use the upgrade.
You must supply a Windows 95 or Windows 98 boot floppy because this CD
is not bootable.
Filesystem Space Requirements:
(The above requirements for $HOME are based on the "C:" drive location
being mapped by default to $HOME/win.
You can change where this is mapped using the
SCO Merge "winsetup" configuration utility,
or you can use symbolic links to cause $HOME/win to be located elsewhere.)
Installing SCO Merge
To install SCO Merge, use the Software Manager. See Chapter 4,
"Installing and managing software components" in the
SCO OpenServer Handbook for details.
If you are upgrading from an earlier version of SCO Merge,
we recommend that you remove the old version of SCO Merge first
and then install the new SCO Merge.
(When you remove the previous version of SCO Merge, your Windows
installations, applications and configuration settings are not removed.)
It is important that there must not be anyone using Merge while Merge
is being removed or upgraded.
It is possible to upgrade existing Merge sessions from the standard Winsock 1.1
style of networking to the new VNET style of networking. VNET supports
full Microsoft Networking Services over TCP/IP. See the
SCO Merge User's Guide for details on how to do this.
Licenses
SCO Merge 5 requires a license to be installed before it can be fully used.
You use the SCO License Manager to install or remove the SCO Merge licenses.
If you do not have an SCO Merge 5 license, you can use the following evaluation
license:
License Number: EVLMERGE5
License Code: tdrthlid
License Data: d60;k0;q0;mmbr90w
The license is for evaluation purposes only. It expires 60 days after it is
installed and may not be reused or replaced by another evaluation license.
After Installing
Once you have installed SCO Merge, refer to the on-line
SCO Merge User's Guide,
which will guide you through the following steps:
- Loading the Windows CD.
- Installing Windows for personal use.
SCO Merge Documentation
A variety of on-line documentation is provided
as part of the SCO Merge product:
- SCO Merge User's Guide
- On-line Help
- Manual Pages
- Trouble Shooting Guide
This release note is available via the
SCO Merge User's Guide
when SCO Merge is installed, and it is also available on the
installation CD in directory info/merge regardless of
whether SCO Merge is installed.
Known Product Limitations
- This product release is only available in English,
although it does support Western European DOS and Windows.
- Merge 5.0 now supports complete Windows 95/98 networking (VNET)
in addition to the standard Winsock 1.1 support found in previous
releases. The VNET networking requires that each Merge session be
assigned and configured with a unique IP address. DHCP is not supported.
- Novell networking is NOT supported.
- Windows 3.1 is NOT supported.
- Root user is not allowed to install Windows.
Known Problems and Troubleshooting
-
Using the Hide Menu or Show Menu option
under X might cause the Merge window
to creep toward the upper left corner of the screen
with some windows managers, including the
UnixWare 7 CDE Desktop window manager (dtwm).
-
When running Windows on the X desktop,
the Caps Lock LED might not reflect the true state
of the Caps Lock setting in some locales.
Certain Windows locales require the user
to use the "Shift" key to toggle Caps Lock off.
Caps Lock will be turned off for the Windows session;
however, the Caps Lock LED will not change.
(When running Windows in a "full-screen" configuration,
the LED matches the state of the Caps Lock setting.)
- SCO Termlite and SCO TermVision are not supported from within SCO Merge.
- Lotus SmartSuite 96 "SmartCenter" does not work properly.
- Older versions of Adobe Acrobat Reader do not work properly.
Use at least version 3.01 instead.
- The file hypertrm.dll is not get installed automatically.
You can use the Windows command "extract.exe" to extract
this file from the Windows "cab" distribution files from
the J:\wincabs directory or from the Windows installation CD.
Find the first ".cab" file with a name that starts with "win9".
The following table shows the typical first win9 cab file:
Windows Version First WIN9 cab file
------------------- -------------------
Windows 95 Upgrade win95_02.cab
Windows 95 Original win95_03.cab
Windows 95 OSR2 win95_02.cab
Windows 98 win98_22.cab
Windows 98 SE win98_21.cab
So for example if you have Win98SE and the cab files are in
J:\wincabs, then to extract the hypertrm.dll file,
from your Windows session start a "MS-DOS Prompt" box.
Then type this command:
extract /a j:\wincabs\win98_21.cab hypertrm.dll