SCO Merge 5.1 for OpenServer

This optional service provides users the capability of running Microsoft Windows 95 and Windows 98 sessions on SCO OpenServer^TM. This version of SCO Merge is also available for UnixWare® 7. These release notes provide important information about SCO Merge and pointers on where to find further information.

SCO Merge Features

SCO Merge 5.1 has the following features:

Windows 95 and 98 support (American and European)
Choice of networking: "Winsock" or "VNET".
Graphical configuration interface.
Support for Microsoft Office 2000 and earlier versions
Support for Microsoft Internet Explorer 4 and 5
Support for Netscape 4.x

New SCO Merge Features

SCO Merge 5.1 is an updated version of SCO Merge 5.0. This new version includes some new features and improvements as well as some bug fixes. New major features since 5.0:

Improved support for European language versions of Windows
Added support for Norton AntiVirus 2000.
Added support for Glyph Index Fonts. This fixes the display errors with some Eastern European and Asian fonts as well as the "symbol" font.
Reduced per user memory requirements.

Installation Requirements

SCO OpenServer Release 5.0.5 or later, using the X desktop.
For SCO OpenServer Release 5.0.5 it is necessary to install OSS615a before installing SCO Merge. OSS615a is available from the SCO public website using the URL: http://www.sco.com/support/ftplists/osr5list.html
Windows 95 or Windows 98 installation media.
A Pentium or better CPU.
RAM requirements are determined by how many simultaneous DOS or Windows sessions are in use. A single Windows session can be run on a standard 64MB SCO OpenServer system. Additional Windows sessions need to be able to claim an additional 32Mb per Windows session. A single DOS session can be run on a standard 32Mb SCO OpenServer system with an additional 3Mb required for each additional DOS session.

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). 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.

Windows language versions that can be installed:

             95       95     98      98
             Classic  OSR2   OE      SE
 --------    ---      ---    ---     ---
 Basque      Yes       -      -       -
 Brazilian   Yes      Yes    Yes      -
 Czech        -       Yes    Yes     Yes
 Danish      Yes      Yes    Yes     Yes
 Dutch       Yes      Yes    Yes     Yes
 English     Yes      Yes    Yes     Yes
 Finnish     Yes      Yes    Yes     Yes
 French      Yes      Yes    Yes     Yes
 German      Yes      Yes    Yes     Yes
 Greek        -       Yes    Yes     Yes
 Hungarian    -       Yes     -      Yes
 Italian      -       Yes    Yes     Yes
 Norwegian   Yes      Yes    Yes     Yes
 Panama       -       Yes     -       -
 Polish       -       Yes     -      Yes
 Portugese   Yes      Yes     -       -
 Russian      -       Yes     -      Yes
 Slovak       -       Yes    Yes     Yes
 Sloveni      -        -     Yes     Yes
 Spanish     Yes      Yes    Yes     Yes
 Swedish     Yes      Yes    Yes     Yes
 Turkish     Yes      Yes     -       -

(Note, not all of these language versions have been tested to verify proper operation.)

Filesystem Space Requirements:

SCO Merge installation requires approximately 15 MB (in /opt/K)

Windows requirements:

   Windows Version      To Load the CD.       Per-User.
                        Space in /usr/merge   Space in $HOME
   Win95 Classic             40 MB                41 MB
   Win95 OSR2                69 MB                93 MB
   Win98 First Edition      115 MB               148 MB
   Win98 Second Edition     132 MB               195 MB

(If you do not have enough space in your /usr filesystem then use symbolic links to cause "/usr/merge" to be on another filesystem.)

Windows Temporary Space - each session of Windows requires 50-100MB of temporary space on $HOME.
Typical Windows Application filesystem requirements for $HOME using default install options:
- Office '97 116 MB
- Office 2000 60 MB to over 400 MB

(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 used. You use the SCO License Manager to install or remove the SCO Merge licenses. If you do not have an SCO Merge license, you may use the following SCO Merge evaluation license free for 60 days:

     License Number: EVLMERGE5
     License Code:   tdrthlid
     License Data:   d60;k0;q0;mmbr90w

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
Troubleshooting Guide

These release notes are available via the SCO Merge User's Guide when SCO Merge is installed, and they are also available on the installation CD in directory info/merge regardless of whether SCO Merge is installed. The SCO Merge User's Guide is available through SCOHelp after SCO Merge is installed.

Known Product Limitations

This product release is only available in English, although it does support non-English Windows 95/98.
The complete Windows 95/98 networking (VNET) requires that each Merge session be assigned and configured with a unique IP address. DHCP is not supported. When using the Winsock networking instead of VNET, a unique IP is NOT needed, but only the standard Winsock 1.1 interface is supported, not Winsock 2.
When installing German Windows with VNET selected, an extra network adapter named "DFU" may be mistakenly installed. In addition to being useless and confusing, it also can cause performance problems. Remove this using the Windows networking control panel. (The only network adapter that should be installed is named "Merge NIC".)
Novell networking is NOT supported.
Root user is not allowed to install Windows.

Known Problems and Troubleshooting

When installing Windows, when it seems to be finished installing, you have Windows running in a Window on your desktop. The final step requires that you immediately shutdown the session by clicking on the "Start" button, then clicking "Shut Down" and then clicking "OK". If this is not done then Internet Explorer will not be properly set up and your installation may otherwise not be completely installed.
X Cut & Paste may not always work properly. It may be necessary to have no more than one Merge session displayed per console in use. Use of X Cut & Paste may also require repeated attempts in order to successfully place text on the clipboard. Try Cutting & Pasting from Unix to Unix or Windows to Windows first. Instructions for configuring X Cut & Paste are in the on line Merge User's Guide in Chapter 3 under "Cutting and Pasting."
After exiting your Windows session in which you enabled X Cut & Paste, to return the X clipboard to normal operation you may have to kill the "clipman" process. To do this follow these steps:
1. Find the id number of the process. The following command does this. (Use this command exactly):
```
      ps -e | grep " clipman$"
  
```
  (The above command has a space between the double quote and the "c" and has the $ symbol between the "n" and the double quote.) If there is a clipman process running then this command prints out something like this:
```
      2134 ttyp2 00:00:00 clipman
  
```
2. The first number is the process id that you use with the kill command. For example if the process id is 2134 you use this command:
```
      kill 2134
  
```
Caps Lock and Num Lock keys may not work properly. This may happen when you use an X display server that does the Caps Lock and Num Lock keys differently than the standard SCO console X server on your system. For instance, the OpenServer X server does it differently than the UnixWare X server.
The setting MERGE_X_LOCK_KEYS_TOGGLE configures Merge to expect one style or the other by setting it to "on" or "off". The default setting is in the file /etc/default/merge, and each user can configure it by putting this setting in their UNIX environment.
For the OpenServer X server, the setting should be:
```
      MERGE_X_LOCK_KEYS_TOGGLE=on
```
For the UnixWare 7 X server and the XFree86 X server it should be:
```
     MERGE_X_LOCK_KEYS_TOGGLE=off
```
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.
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).
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.
Emptying the Recycle Bin can result in error messages in certain situations. The error message:
```
   Cannot delete file:  File system error (1026).
```
happens when Windows is trying to create a RECYCLED directory on a drive where it does not have permission to do so. The standard J drive is located at /usr/merge/dosroot, so you should log in as root and then create the directory /usr/merge/dosroot/RECYCLED if it does not already exist. (E.g. with the command "mkdir /usr/merge/dosroot/RECYCLED"). For all the other "drives" that are used that do not already have a RECYCLED directory, you should create one.
Another error message occurs as a result of moving a read-only file that is not owned by you into the recyle bin. This error happens later when you "empty" the recycle bin:
```
   Cannot Delete DCxx: Access is denied
```
(where 'xx' is a number). Windows fails to delete this file the from the Recycle Bin, but Windows shows an empty recycle bin. To actually remove the DCxx files, you must use the Unix 'rm' command to remove the files.
Problem installing Netscape. When installing Netscape, do NOT restart Windows when given the choice. Defer the restart until after the Netscape installer has completely finished.
Printing problems. If you experience printing problems, make sure you have the latest printer drivers from the printer manufacturer.
In certain siutations, the Microsoft Internet Explorer Internet Configuration Wizard may seem to only allow using a modem to access the internet. If this happens, with the right mouse button click on the Internet Explorer icon on your Windows desktop and then click on Properites. Then click the "Connections" tab, and then on the "Setup" button for the Connection Wizard. Select "I want to connect though a local aread network (LAN)", or similarly worded option, and then click Next. For some versions another window pops up and you have to select "I connect through a local area network (LAN)" and click Next again. If you have NOT installed windows with VNET, and the Wizard starts to install files, you MUST cancel it, otherwise the Winsock networking will be damaged. Do NOT click OK with the Internet Connection Wizard unless you installed Windows with VNET networking.