NeTraverse Win4LinTM 3.0.0 Release Notes
Thank you for choosing to use Win4Lin from NeTraverse. Win4Lin 3.0.0
Desktop software integrates the Microsoft® Windows® 95/98 operating systems
into the Linux environment, allowing users to access both Linux and
Windows® applications simultaneously.
Table of Contents
Major new features in the the 3.0.0 release
Viewing the Win4Lin Documentation
System Requirements
Windows Versions
Disk Space Requirements
Support for Audio Playback
Customizable drive labels
Loading the Windows installation files from CD
Loading Windows installation files from Windows partition
Access to floppy disk drive during Windows installation
Networking Support
Windows Application Support
Windows 95 Y2K update
This release, 3.0, is a major update to the previous version, Win4Lin 2.0.
This document provides release specific information that is supplemental to
the Installation and Operations Guide, and the User's Guide and other
on-line help documents contained in the distribution.
Major new features in the 3.0.0 release
- Support for Linux 2.4 kernels.
- Support for Network Neighborhood and Microsoft Exhange server access, via
the new VNET feature.
This gives your Windows session a virtual network connection, that uses a
unique IP address. This feature includes DHCP support.
- New Graphical installation.
- Easy sizing of the Windows window:
- Winsetup "Window Resize".
In winsetup, under "Personal Windows Session Configuration",
the display tab now has a "Window Resize" control and a new option, "Window
Resize". When this option is checked, it activates the "Window Resize"
control that provides two settings, "Automatic" and "Custom". When Automatic
is selected the Windows window size is automatically set to be the next
smaller standard size resoltion from the real display resolution. And
when Custom is checked you control exactly what the Window size will be
either by using the slider bars (either with the mouse or the keyboard
arrow keys), or by using the "Manual Resize" control.
- Winsetup "Full Screen Resize".
In winsetup, under "Personal Windows Session Configuration",
the display tab now has a "Full Screen Resize" option. When this option
is checked, and you start a "full screen" session with the "fwin" command,
Windows is resized as needed to completely fill the screen.
- New "-g" option for the win command.
A "-g" option can now be used to specify the exact resolution to use when
you want to start your Windows session. For instance, to have a 1000 by
700 window size, you would use the command "win -g 1000x700".
- Automatic creation of D: drive for user data
When you install Windows, the "D" drive is automatically created and provides
access to the new Linux directory "$HOME/mydata". This drive is intended to
be the place where the user keeps their documents and other data files. It
provides a convenient place for sharing or moving files between Linux and
your Windows session, and makes it easy to create backups of your data. In
addition, the directory "$HOME/mydata/MyDocuments" is created and the Windows
98 desktop "My Documents" icon takes you directly to this directory.
- Raw printer definition
There is a new printer definition named "default-raw" that is similar to the
standard "default" printer definition. This new printer definition uses the
Linux command "lpr -o raw" instead of just "lpr" as used by "default" (the
names "default" and "default-raw" show up as printer port choices when you
set up a printer in Windows). For certain types of printers the "-o raw" is
required for correct printing from Windows. It is recommended that you initially
select the "default-raw" printer definition whenever you add a Linux
printer to your Windows configuration. Only if you have problems with that
printer definition should you try using original "default" printer definition.
Viewing the Win4Lin Documentation
This product provides an Installation and Operations Guide,
and on-line help documentation that includes a User's Guide, Trouble
Shooting Guide, Manual Pages, and this Release Note.
Electronic versions of the Installation and Operations Guide, in PDF
and HTML formats, are located on the Win4Lin 3.0 CD in the doc/W4L3.0-guide
directory.
The on-line help documentation is located on the Win4Lin 3.0 CD in the Win4Lin/help
directory. After installing the Win4Lin package, these files are located under
/opt/win4lin/help:
- /opt/win4lin/help/guide -- User's Guide
- /opt/win4lin/help/trouble -- Trouble Shooting Guide
- /opt/win4lin/help/man -- Manual pages for Win4Lin commands
All the on-line help documentation is in standard HTML format. The Linux man
command cannot be used to display the manual pages.
The Help button in Win4Lin windows provide access to all the on-line
help documentation.
To display the on-line help documentation from within
a Win4Lin session, use Shift-F12 to display the menu bar, then choose
the desired topic from the Help menu
During installation, Win4Lin locates an HTML browser on the Linux system for
use when displaying the documentation. If you do not like the choice of HTML
browser, or the installation process was unable to find a suitable browser,
you can specify the browser of your choice by editing the MERGE_HELP_BROWSER
setting in /etc/default/merge.
NOTE: A user can override the default in /etc/default/merge by
setting MERGE_HELP_BROWSER in their Linux shell environment.
If you have trouble installing Win4lin or Windows, or encounter other problems,
please consult the Installation and Operations Guide, User's Guide
and the Trouble Shooting Guide. Please note that you can always find
the most up-to-date technical documentation, as well as the latest product
updates, on our website at http://www.netraverse.com/support/.
System Requirements
- Pentium-class processor
- 32 MB ram or better
- Linux 2.2.X or 2.4.X kernel
- RPM package management system
- An X Windowing System (1024x768 pixels resolution, 16-bit color depth (64K
colors) recommended) with preferably with backing store enabled.
NOTE: The default configuration of XFree86-4.0.x does not have backing
store enabled.
Some X Servers require a customized keyboard mapping configuration file for
full functionality, especially for non-U.S. keyboards. Refer to Appendix A
of the Win4Lin User's Guide for information on the configuration of keyboard
mapping files.
- Ability to run as root and install a new kernel
- A US English or European language version of Windows 95, 98, or 98 Second
Edition installation media
Windows Versions
Windows language versions that can be installed.
| Win95-Classic | Win95-OSR2 | Win98-Original | Win98-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.)
Disk Space Requirements
- Win4Lin RPM installation requires approximately 10 MB,
mostly in /opt/win4lin.
If you do not have enough space in your /opt filesystem then
use symbolic links to map /opt/win4lin to another filesystem.
NOTE: If you need to build your own Win4Lin capable Linux kernel, you
will require an additional 70 MB to 90 MB for the Linux build
tree, depending on your Linux version.
- Windows disk space requirements:
Windows Version |
To load CD in
/var/win4lin
|
Per-user 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 /var filesystem, use
symbolic links to map /var/win4lin to 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 default mapping of the
C: drive location to $HOME/win. The Win4Lin winsetup configuration
utility can be used to change this mapping. Alternatively, you can use symbolic
links to map $HOME/win to another location.
Supplement to the On-line Help Documentation
Support for Audio Playback
Win4Lin now supports audio playback through Windows 95 and Windows 98. Sound recording,
midi, volume control and Music CD playback are not supported.
It is required that you have sound hardware supported by your Linux Operating
System.
The interface used to play audio is the Open Sound System (OSS) API (the standard
on most Linux distributions) through the /dev/dsp device. If you are using a different
sound driver architecture such as ALSA, please make sure you have enabled OSS
compatibility.
Known limitations in this release are:
- Audio and video can lose synchronization depending on the hardware and
drivers used and on the workload of your Linux system.
- If the Win4Lin sound server cannot open the /dev/dsp
device, Windows applications may become unresponsive, and your Windows session
may terminate.
- Win4Lin only provides sound output plugins for /dev/dsp
devices (OSS API) at the current time. ALSA and EsounD are not supported in
this release.
If you have upgraded from a previous release of Win4Lin and have not reinstalled
your personal copy of Windows, please follow these instructions (these are based
on English versions of Windows):
- Make sure your configuration file /etc/default/merge contains the
line MERGE_AUDIO_PLUGIN=/opt/win4lin/libossplugin.so
- Start your Windows Session and open the Control Panel by clicking on Start->Settings->Control
Panel.
- Launch the Hardware Wizard by clicking on the 'Add new Hardware'
Icon.
- Follow the Wizard's instructions and when asked whether you want Windows
to search for new hardware, choose 'No'.
- From the 'Hardware Types' list, choose 'Sound, video and game
controllers'. When the Manufacturers and Models are displayed, click the
'Have Disk' button, and when prompted to 'Install from Disk'
click the 'Browse' button.
- In the 'Open' window select the J: drive from the Drives
selection list. Select mwin95 from the Folders list. The 'File name'
text field will now show mss.inf.
- Click the 'OK' button on the 'Open' and the 'Install from
Disk' windows. You will be prompted to select a device. The only device
displayed will be 'Merge Sound Switch'.
- Click 'OK'. Finish the 'Hardware Wizard'
and restart you windows session.
To disable sound, set the environment variable MERGE_AUDIO_PLUGIN=none,
or make this a permanent setting in /etc/default/merge.
Customizable drive labels
A new feature of this release is "customizable labels" for the Windows drives.
The default labels have changed and now reflect the location of the drive mapping
in to the Linux filesystem.
NOTE: The "~" character refers to $HOME.
To customize the drive label do the following: create a directory named .labeldosdrive
in the directory at the root of the drive and in that directory create an empty
file with your chosen name for the drive label.
Known limitations in this release:
- The drive label cannot be changed using native DOS and Windows tools.
- Windows 95 and some versions of Windows 98 restrict the label to 11 characters.
Loading the Windows installation files from CD
Once Win4Lin is installed you need to load the Windows installation files from
a Windows installation CD. 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.
The on-line help for this step explains how to create one of these floppy
disks if you do not already have one, or how to use an "image copy" file of
such a floppy if you do not have a floppy drive on your machine. You must
login as root and be running in graphical mode to perform this operation.
Win4Lin supports the following versions of Windows:
- Windows 95 "classic" (a.k.a. "retail")
- Windows 95 OSR2
- Windows 98
- Windows 98 Second Edition.
- Windows 95 to Windows 98 Upgrade CD
NOTE: The Windows 95 to Windows 98 Upgrade CD can be used for fresh
installations of Windows. In order to install Windows form this CD, you
must have a qualifying Windows 95 installation CD. Also, since the CD is
not bootable, you will require a Windows 95 or Windows 98 boot floppy.
Win4Lin does not support the following:
- Installation from a Windows "Companion" CD
- Upgrading existing installations of Windows 95 to Windows 98
- Windows upgrades other than the one from Windows
95 to Windows 98 may not work.
Loading Windows installation files from Windows partition
With this release, you now have the option of loading the Windows installation
files (.cab files) from the native Windows partition on your hard disk
(the DOS C: drive).
If you do not have a Windows installation CD, but you do have a dual boot
system with Windows on another partition, it is possible to load the required
installation files from that partition. For this to work, all the installation
files need to be in a single directory on the native Windows partition (typically
C:\windows\options\cabs). In addition to the .cab files, the directory
must contain the extract.exe file and a "setup" command file. For English
versions of Windows, the "setup" command file is called setup.exe. Other
language versions of Windows may instead use one of the following: install.exe,
config.exe, instalar.exe, asenna.exe, installa.exe setupcur.exe, kur.exe.
To load Windows installation files from a Windows partition,
perform the following steps:
- Change to the root user:
su root
- Load the installation files:
loadwindowsCD dosc
Access to floppy disk drive during Windows installation
Access to the floppy disk drive is prevented while Windows is being installed.
This is done because on some Linux systems, when there is no floppy disk drive
or no floppy disk in the drive, the Linux driver malfunctions and hangs until
a floppy disk drive is installed and/or a floppy disk is put in the drive. Normally
access to the floppy disk drive is not needed while installing Windows. If you
need access to the floppy disk drive, type the following command:
installwindows floppyok
Networking Support
Win4Lin supports two methods of TCP/IP networking:
- WinSock
This is the networking feature that was available in previous versions of
Win4Lin. It is "WinSock 1.1 compliant". With this type of networking, TCP/IP
based applications have their network data re-directed through the Linux network
interface. No configuration of Windows networking is necessary. You are required,
however, to have a functional Linux network configuration before Windows applications
can talk to the network. Winsock based applications such as ftp, telnet, Netscape,
Internet Explorer, etc. will function normally. Applications which do not
use WinSock for communications, such as MS Exchange, are not supported with
this type of networking.
- VNET
VNET stands for "Virtual Networking" and is new for Win4Lin 3.0.
With this type of neworking, the Windows session has a "virtual network interface
card" which must be assigned it's own IP address. If DHCP is used to allocate
IP addresses on your local network, then you can have DHCP assign this IP
address. With VNET, your Windows session has access to the "Network Neigborhood"
for file browsing and printing. Access to MS Echanges servers is also supported.
You choose which kind to use when you install Windows.
You can switch the type of networking from WinSock to VNET and from VNET to
WinSock using the new command win_network. To change to WinSock type
"win_network -w", and to change to VNET type "win_network -v".
NOTE: due to a limitation in the registry editor supplied with Windows 95 "classic"
, the "win_network -w" option is not supported with this release of
Windows.
Windows Application Support
Most Windows applications will simply install and function normally. Certain classes
of applications, however, may not be supported due to limitations in the Win4Lin
product.
Applications which require low level access to filesystem information may
not operate correctly. In some situation, this limitation can be overcome by
installing the application on a native Windows partition mapped to a Win4Lin
drive. Examples of programs that may not work correctly
are: disk defragmenters, disk scanners, and file repair programs.
Application that require direct access to hardware are not supported.
Applications that install VxDs (virtual device drivers)
may not operate properly.
Windows 95 Y2K update
Microsoft's Y2K fix for Windows 95 (w95y2k.exe) is supported although
some extra steps are required for Win4Lin to complete the update. For instructions
on these steps refer to the Win95
Y2K Update section in the Windows
installation problems topic of the Trouble shooting guide.
Removing Win4Lin
When you remove the Win4Lin package, it does not remove the Windows files that
you have loaded and installed, nor does it remove any application you have installed
or any data files you have created. All configuration settings are also retained.
This design allows you to remove an old version of Win4Lin and install a new
version without losing the Windows installation or configuration settings.
To remove the Win4Lin RPM package, perform the following
steps:
- Change to the root user:
su root
- Remove the product files:
rpm -e Win4Lin
If you wish to remove all the global Windows files and global configuration files,
run the script:
sh /var/win4lin/final_remove.sh
Then each user can remove their private Windows files and private configuration
files. These are located in subdirectories under the user's home directory:
.merge - Configuration file directory.
win - C: drive directory where Windows is installed.
- The commands winsetup, win and /bin/dos all requires
that the DISPLAY environment variable be set properly as is required
by all X client applications.
- Win4Lin can be executed within an X window on your desktop using the win
command or on a separate virtual console using the fwin command.
The preferred method is to create a separate virtual desktop for Win4Lin and
adjust the Windows Display Settings to make the Win4Lin window fill the entire
desktop. It's much faster switching between virtual desktops than virtual
consoles. It also uses less memory since you're only running one X server.
The advantage of running in full screen on a separate console is the special
accelerator keys (like ALT-TAB) can be passed into Windows rather than being
caught by the Linux window manager. This also makes it possible to configure
the window manager to use different accelerators, thereby allowing the normal
ones to be passed through to Windows.
- The default memory allocated to Windows 95 is 16MB. This is adequate
for running most Windows applications, including MS Office, and results in
good overall system performance. For Windows 98 first edition the default
memory allocation is 20MB, and Second Edition is 24MB. You don't want to give
Windows more memory than it needs because it will just suck it up. If
your system has more than 64MB of memory, or you want to run a particularly
memory intensive set of applications, try increasing the memory to 32MB.
You can increase this setting (to a maximum of 64MB) with the winsetup
utility.
-
Once your windows installation is complete, it is
a good idea to make a backup copy of your ~/win directory (your C:
drive under Win4Lin). For example, issue the following command under Linux:
cd
tar -czvf win-backup.tar.gz ./win
Also, it is strongly recommended that you use a separate drive mapping to
hold all your personal files, rather than storing them on the C: drive.
For example, use the D: drive that was automatically created when you
installed Windows. If you do both of these things, it will make it very easy
to reinstall Windows by simply restoring the archive of your ~/win
directory.
- It's important to remember that all the Linux filesystem permission are
enforced making it possible to take advantage of C: "readonly"
and "deny access to others" permissions. This makes it less likely
that important windows files will be accidentally overwritten or corrupted.
Use the Linux chmod commands to change the permissions for "group"
and "other".
- If you have cause to change the IP address of your Linux network interface,
and you have chosen to configure your Win4Lin session to use the VNET networking
feature, you need to notify the VNET environment of the change by issuing
the following command as root:
killall -HUP vnetd-2.2 - on a Linux 2.2.x system
killall -HUP vnetd-2.4 - on a Linux 2.4.x system
The focus of Win4Lin 3.0.0 is to provide Linux desktop users access to
the thousands of Windows desktop productivity applications that are not currently
available on Linux. This release is not suitable for multimedia
intensive applications or server configurations.
Note that the following features are not available in this version
of the product. These features are being considered for a future release.
Your feedback on the importance of these and other features is appreciated.
Please use the web site http://www.netraverse.com
for feedback
The top requested features not yet available are:
- Direct Device Access: Currently limited to serial and parallel port.
- Direct X (as used by most games): Not supported
- DirectDraw (as used by RealPlayer): Not supported
- Desktop Integration: No automatic placement of Win4Lin specific
icons on the Linux desktop.
- Cut and Paste between Windows and Linux: Not supported. As
an alternative, you can use file based cut and paste between Windows apps
and Linux apps.
Anomalies and Caveats
- CD-ROM Access: Some systems may not allow access to the CD-ROM device
by default. If you cannot access the CD-ROM device, check the permissions.
Typically, /dev/cdrom is a symbolic link to a real device, for example
/dev/hdc is the CD-ROM when you have an IDE CD-ROM as the secondary
master device. Be sure this device has the appropriate permissions (i.e.
readable by everyone). Also on some systems, the CD-ROM sometimes cannot be
ejected until you exit your Windows session.
On some systems, the use of the CD "automounter" might result in problems
accessing the CD.
If you are using the Gnome Desktop and have peripheral settings for the
CD-ROM turned on, you should turn those off at this time. To change these
settings:
- Click on the foot icon in the Gnome Panel.
- Select Programs->Settings->Peripherals->CD Properties.
- Deselect all options for Data and Audio CDs.
- Select OK. Then close the Control Center window.
If you are running the KDE desktop you will need to open a terminal window
and type:
killall autorun
This will stop the auto-mounter for the current KDE session only. Once
KDE is restarted, the CD-ROM auto-mounter will function as it normally does.
With some versions of KDE, you can edit the script /usr/bin/startkde
to permanently prevent KDE from automatically mounting CDs. To disable automounting,
remove or comment out the following lines and then restart the desktop:
# start autorun daemon if available and not already running
if [ -x /usr/bin/autorun ]; then
/sbin/pidof 2>/dev/null >/dev/null autorun || \
/usr/bin/autorun --interval=1000 \
--cdplayer=/usr/bin/kscd &
fi
NOTE: Make a copy of the original file before modifying the contents
so that you can restore your original configuration when required.
If you can't resolve the problems accessing the CD, try using winsetup
to define a drive letter for your Win4Lin session to obtain access to the
Linux directory where the CD is mounted.
- CD-ROM Recording: Writing to CD-R and CD-RW devices is not supported.
- Printing: When you install a printer and ask to print a test
page, the system will appear to hang for a short period, and then the print
request will fail. Just ignore this and click OK when asked if
the test page was printed correctly. Try printing again from an application.
Printing should proceed normally. This type of problem is not unique to Win4Lin
but may also be observed on native Windows systems when printing to some types
of network printers.
- $HOME/win directory on NFS mounted filesystem: This is not recommended.
Problems associated with file locking may cause Win4Lin to fail to start or
to execute incorrectly.
- NFS access to SGI system: There are problems using NFS mounted
filesystem from SGI systems. The problem is that some subdirectories are not
seen. NFS mounted filesystem from other types of NFS servers do not have this
problem.
- Floppy Disk Drive Access: There are several problems related to
floppy disk drive access:
- Inaccessible floppy disk drives
Some systems may not allow access to the floppy disk drives by default.
If you cannot access the floppy disk then check the permissions of the
devices /dev/fd0 (for the A: drive) and /dev/fd1
(for the B: drive). If these are not the floppy disk drive device
names for your system, you can specify other devices names with a setting
in the file /etc/default/merge. For example if the A: drive
is /dev/floppyA and the B: drive is /dev/floppyB,
then put these two lines into /etc/default/merge:
MERGE_ADRIVE_AUTOSENSING=/dev/floppyA
MERGE_BDRIVE_AUTOSENSING=/dev/floppyB
- No floppy disk drives.
Some Windows operations requires that there be an A: drive, and
can hang or cause long delays if it tries to access a nonexistent drive
(this is a problem most likely to occur with laptop machines). If this
is a problem then you can redirect A: drive access to an empty,
read-only virtual floppy disk device by putting the following line in
the file /etc/default/merge:
MERGE_ADRIVE_AUTOSENSING=/opt/win4lin/diskimages/f.dsk
- No second floppy disk drive
If you have the device file /dev/fd1 but no real matching physical
drive, it can cause delays when Windows tries to access the B:
drive. If you experience this problem, simply remove this device
file.
- DOS Emulation: If you have installed the DOS emulation support
that comes with Linux, you may run into a conflict with /usr/bin/dos
being in your path before /bin/dos which is the Win4Lin dos command.
If you're not going to run dos don't worry about this. Otherwise, check
your path or alias as you deem appropriate.
- Physical Memory Limitation: When building Linux kernels from source,
the 'Maximum Physical Memory' option in the 'Processor type and features'
section has to be set to 1GB. Support for Win4Lin and 2GB of Maximum Physical
Memory are mutually exclusive settings.
- Ctrl-Z: You cannot use Ctrl-Z to "background" the win
process. You must use win & to startup a Win4Lin session in the
background.
- Mysterious Windows Hangs: Occasionally, you may experience hang-ups
due to problems in Windows or your Windows applications. When a hang-up occurs,
Win4Lin offers an advantage over native Windows in enabling you to restart
your Windows session in just a few seconds. If the problem persists, please
try to verify that the failure does not occur on a native Windows installation
before reporting the problem to NeTraverse.
- Recycle Bin: With Windows 98, 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. To fix this you should log in as root
and then create the directory RECYCLED in the directory where the drive letter
is rooted.
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 Linux 'rm' command to remove the files.
Also, it is important to make all the RECYCLED directories readable and writeable
only by the users with permissions to write to the directory containing the
RECYCLED directory. You should set the RECYCLED directory owner and group
to be the same as its parent directory, and remove the read and execute permissions
where there users have no write permissions.
For example, if the directory /foo has owner and group set to "bin,sys",
and the permission reported by "ls -l" are "drwxrwxr-x", execute the following
commands as root:
mkdir /foo/RECYCLED
chown bin /foo/RECYCLED
chgrp sys /foo/RECYCLED
chmod ug+rwx /foo/RECYCLED
chmod o-rwx /foo/RECYCLED
- SOCKS and Proxy Servers: SOCKS, and similar proxy servers, will not
work with the current implementation of WinSock. In order to use application-specific
SOCKS proxy settings under Win4Lin, users should configure their system to
do networking via VNET.
- Norton SystemWorks: When Windows starts with Norton SystemWorks installed,
the following error messages is displayed: "Drive Read Error, drive X:". This
does not affect the operation of Win4Lin, but an annoying error message will
pop up every three seconds reporting: "An error occurred updating the image
data for drive C: This disk is either missing, full or damaged." as Norton
SystemWorks tries to create an image of the C: drive. The error message is
eliminated by cancelling the task that is attempting to create the image.
Norton SystemWorks contains serveral components that are meant to be used
with a real Windows disk drive. These components attempt to read information
from the disk Master Boot Record and the partition table. Since Win4Lin does
not permit Windows to have access to the physical Master Boot Record and the
partition table, these component will report errors until disabled by the
user.
- Session Hangs when using fwin: The fwin command invokes a
second X server and this has been found to cause problems on some system,
particularly laptop machines. Since this is usually found to be caused by
bugs in the X server software, it is recommended that you avoid using fwin
if this problem occurs.
- RealPlayer: If you install RealPlayer Basic, you will receive a "fatal
exception" error message on a blue screen during the installation. You can
press any key to continue with the installation. Everything will install correctly
and you can use RealPlayer but for audio only. If you attempt to play anything
that has graphics content, however, an error message will pop-up reporting
that your system does not support Microsoft DirectDraw. To avoid this problem,
it is recommended that, when downloading multi-media content from a Web site,
you select the Microsoft Media Player option if available.
- Win4Lin Installer Help: After clicking the Help button to obtain
additional help information during installation of your Personal Windows Session,
the help browser may appear only momentarily before exiting. This problem
has been observed only with the Helix-Gnome version of the Gnome help browser
in situations where the installer is invoked from a substitute user (su)
session. It is recommended that you do not invoke the Win4Lin installer from
an su session.
Providing Feedback
NeTraverse very much appreciates all feedback on the product. We are particularly
interested in hearing about applications that you have tried and have found
to work. Of course, we also welcome information regarding problems you have
encountered with the installation or operation of applications. Further, we
are interested in your ideas for new product features and enhancements. This
input will help guide our future development.
Please use our web site http://www.netraverse.com
to provide your much needed feedback.