Use the FORMAT command at the C:\> prompt. See Chapter 7, “FORMAT”.

Use the New Drive… function on the Disk Drives… cascade menu on the Options menu; refer to Chapter 4, "Setting up hard disk files" in the SoftWindows for Unix Administrator's Guide.

Create a new hard disk file, and then copy the contents of the old file to the new file; referto Chapter 4, "Setting up hard disk files" in the SoftWindows for Unix Administrator's Guide.

Make the hard disk read-only; more than one user can then read data from it. To do this, enter the following command in a Unix terminal window:

chmod 444 filename.hdf 

where filename.hdf is the name of the hard disk file.

It may be useful to use the RO_DISK_PANEL_DISABLE configuration option; for more information refer to Chapter 7, "RO_DISK_PANEL_DISABLE" in the SoftWindows for Unix Administrator's Guide.

You can use the hard disk file from other versions of SoftWindows as D:, but do not use them as drive C: because the version of Windows and the configuration files are not compatible. For information on upgrading your old SoftWindows hard disks, refer to Chapter 5, "Upgrading a version 1 hard disk file" in the SoftWindows for Unix Administrator's Guide.

Refer to Chapter 4, "Setting up the CD-ROM" in the SoftWindows for Unix Administrator's Guide.

Refer to Chapter 4, “Using CD-ROMs”.

Use the Memory dialog box; refer to Chapter 4, "Setting up memory" in the SoftWindows for Unix Administrator's Guide.

Use the MS-DOS KEYB command; refer to Chapter 4, "Setting up keyboards" in the SoftWindows for Unix Administrator's Guide.

Use the Windows International control panel; refer to Chapter 4, "Setting up keyboards" in the SoftWindows for Unix Administrator's Guide.

Drag the sides or corners of the screen. See Chapter 4, “To resize the SoftWindows window”.

Refer to Chapter 5, “Printing, input, and output”.

Refer to Chapter 5, “Printing from MS-DOS applications”.

Use the Windows Printers control panel; refer to Chapter 5, “Printing from Windows applications”.

Refer to Chapter 5, “To use serial input and output”.

If the documents are on a SoftWindows hard disk file, you can use the MS–DOS utilities DOS2UNIX and UNIX2DOS; refer to Chapter 7, “DOS2UNIX”, or Chapter 7, “UNIX2DOS”.

If they are in the Unix file system, you can use the Unix utilities "dostounix" and "unixtodos" supplied in the $SWIN2HOME/bin directory. See Chapter 11, "Unix utilities in the SoftWindows for Unix Administrator's Guide.

Use the SoftWindows copy and paste facilities; refer to Chapter 4, “Copying and pasting between MS-DOS and Unix”.

File access permissions are used to tell a computer system who has access to files and directories. Files and directories have a set of permissions to determine which users can read, write, and execute the contents of a file. If a system is shared or is part of a network, other people may need access to its files and directories.

By setting file access permissions you control who is able to read, write, and use your files and directories.

There are four types of permissions for files and directories:

Any of the permissions can be assigned to three categories of users:

You can check file access permissions using the Unix ls -l command.

In a Unix terminal window, move to the directory containing the file by typing the command:

cd pathname 

Then type:

ls -l filename 

The output will be of the form:

-rwxrwxrwx 1 root 512 jun 9 09:35 filename

where the file access permissions are represented by the letters rwxrwxrwx; r is for read, w write, and x execute. The three sets are for the Owner, Group, and Others, respectively.

You can change file access permissions using the Unix "chmod" command.

To change the permissions you need to be logged in as the owner or root. If necessary, ask your system administrator to do this. Then issue the chmod command with an appropriate parameter.

The parameter consists of u (owner), g (group), or o (other), followed by + or - to add or remove permissions, respectively, followed by the type of access: r (read), w (write), or x (execute).

For example, to make a file so that the Owner can read it or write to it, and the Group can write to it, give the command:

chmod u+w+r g+w filename 

For more information on file access permissions consult your Unix reference manuals.

In the .swin2config file in your home directory; refer to Chapter 7, "SoftWindows configuration file" in the SoftWindows for Unix Administrator's Guide.

The MS-DOS files AUTOEXEC.BAT and CONFIG.SYS; refer to MS-DOS configuration, in the SoftWindows for Unix Administrator's Guide.

Refer to Chapter 7, “Installing MS-DOS applications”.

Type them at the C:\> prompt; refer to Chapter 7, “Using MS–DOS commands”.

Use the MS-DOS editor, EDIT; refer to Chapter 7, “Using the MS–DOS editor”. In Windows you can use the Windows Notepad text editor.

Refer to Chapter 6, “To add fonts”.

When you run Windows in a window you are not using one of the emulated display drivers (SVGA or Hercules), and the title bar changes to SoftWindows Desktop to indicate that you are using the SoftWindows Windows display and mouse drivers. These are called SoftWindows Display and SoftWindows Mouse.

While the mouse is attached for use by MS–DOS applications it is not available to Unix programs. To detach it refer to Chapter 4, “Using the mouse in MS-DOS”.

If you are using the print spooler, flush the port to ensure that all the data has been sent. Disable autoflush and flush the port manually. See Chapter 5, “To flush output manually”.

Redirect print output to a file, then print the file outside SoftWindows; refer to Chapter 5, “Redirecting to a file and piping to a process”.

Because MS-DOS was not designed to handle file ownership and permissions like the Unix system, MS-DOS uses an assortment of standard file error messages to indicate that you do not have permission to read, write to, or execute a given file or directory.

The following messages may indicate that you do not have access to a particular file or directory due to the file permissions:

File creation error
File not found
Invalid directory
Invalid path (or file not found)

If one of these messages appears in MS-DOS and you are certain that the file or directory exists, you should check the permissions and ownership using Unix.

Also note that an SUID bit with incorrect ownership will cause permission problems on FSA drives.

Alternatively, copy the files to the hard disk C: or D: and try again.

If the driver completely fails to load, it will display a message which says:

Could not find a host network card

This means that SoftNode has been unable to make contact with the networking facilities on the host machine. This is normally due to one of two things:

If you are not sure whether these packages are installed on your system, contact your system administrator.

If the driver loads but reports an error registering one or more of the protocols specified in the NET.CFG file, then SoftNode probably does not support the appropriate frame type or protocol on that version of SoftWindows.

If the ODI system loads successfully but the network software package you wish to use does not function properly, then it may be that either SoftNode or the package has been configured incorrectly. Please refer to Chapter 9, "Networking with SoftWindows" in the SoftWindows for Unix Administrator's Guide for additional troubleshooting information.

If the following message appears:

Bad command or file name

the batch file ETHER.BAT or TOKEN.BAT could not be found. These files are located in the C:\NOVELL directory, and you can amend the MS–DOS PATH variable to include this directory if required.

Edit CONFIG.SYS and check for an entry of the form:

LASTDRIVE=Z

The NetWare 3.11 client uses drives after the value of LASTDRIVE in the CONFIG.SYS file. By default, LASTDRIVE is set to K. The Netware 3.12 and NetWare 4 client, and LAN Manager, require LASTDRIVE to be set to Z.

An MS-DOS application may have been started with the wrong video mode. Change the display type; refer to Chapter 4, "Setting up the display" in the SoftWindows for Unix Administrator's Guide.

The application may be copy protected and installed on an FSA drive. Reinstall on the C: or D: drives.

Alternatively, the application may require additional memory; refer to Chapter 4, "Setting up memory" in the SoftWindows for Unix Administrator's Guide.

Windows needs a minimum of 2 Mbyte of memory to run, and 4 Mbyte is recommended. Check that this has been set correctly; refer to Chapter 4, "Setting up memory" in the SoftWindows for Unix Administrator's Guide.

Temporarily make it readable and writable. Then in your AUTOEXEC.BAT file change the line

SET TEMP=C:\DOS

to specify a writable disk. For example:

SET TEMP=H:

To load extra Windows drivers, set up an FSA drive (not drive G: as this is required for Windows to run) as $SWIN2HOME/winsetup. This must be done before Windows is started. When you are prompted for the disk or directory from which to load a driver, enter the appropriate drive letter and path, such as I:\.

Alternatively, assuming you have set drive I: to be $SWIN2HOME/winsetup, before running Windows type:

ASSIGN A=I 

If you get one of the following error messages when trying to run Windows:

cannot find files needed to run either standard or 386 enhanced mode; check to ensure the path is correct or reinstall Windows.
Invalid drive to search path

you have tried to connect to a network that maps a G: drive over the current SoftWindows G: drive, and the Windows system files cannot be found.

To solve this problem, map the Windows files to a different drive as follows: