Winsock RSHD/95 (Remote Shell Daemon) is a service for Windows 95 and Windows 98 that accepts requests for command execution and file transfers from other hosts on the network via TCP/IP and executes them on the PC running Winsock RSHD/95. It runs under Microsoft Windows 95 and Windows 98 only.

Winsock RSHD/95 is similar to the Unix server of the same name, but provides some special functionality for the Windows environment, such as:

Command requests can come from hosts running other operating systems such as Unix or from other PC's running Windows 95/98, Windows NT, or Windows 3.1 using the standard rsh utility that comes with your TCP/IP package or Winsock RSH, also available from Denicomp Systems.

Files can be copied to the PC or from the PC running Winsock RSHD/95 using the standard TCP/IP rcp command. This includes the rcp command available with Unix or Windows NT or a PC-based rcp command such as Winsock RCP, also available from Denicomp Systems.

Winsock RSHD/95 requires a Intel x86-based PC running Windows 95 or Windows 98 and a network. The TCP/IP protocol must be installed and configured.

The purpose of a Remote Shell Daemon is to service the standard rsh and rcp commands. These commands were designed to be used on a network where users and systems were generally trusted and convenience was more desirable than security.

Since rsh and rcp do not require users to supply passwords before being granted access, there is the risk of unauthorized users being granted access to your system when running Winsock RSHD/95 (or any Remote Shell Daemon, for that matter). This risk is greatly increased if the system running Winsock RSHD/95 is connected to the Internet. Winsock RSHD/95 provides mechanisms for you to determine which hosts and users are granted access to your system. Firewalls can also help to reduce this risk. But the risk of unauthorized access still remains even when these are used because of the lack of password validation.

By installing Winsock RSHD/95, you are taking this risk of unauthorized access upon yourself. By installing Winsock RSHD/95, you are agreeing that you will not hold Denicomp Systems responsible for any damage caused by unauthorized access to your system through the standard rsh and rcp commands. Denicomp Systems did not design the rsh and rcp protocols; RSHD/95 simply implements the standard originally designed for Unix systems.

Please review the license agreement included with Winsock RSHD/95 and do not continue with the installation or with using it if you do not accept its terms.

To install Winsock RSHD/95, insert the Winsock RSHD/95 diskette into your diskette drive. Click on the Windows 95 Start button, then choose Run from the menu. Then type the name of your diskette drive followed by "SETUP". For example, if the diskette is in the A: drive, type "A:SETUP". Then press the Enter key. (This can also be done from an MS-DOS prompt from within Windows 95 if you prefer).

The Winsock RSHD/95 Installation window will then appear. Verify that the drive letter shown in the Install From field is correct. If it is not, specify the proper drive.

Specify the directory in which you would like Winsock RSHD/95 to be installed in the Destination field. This will default to the \WRSHD95 directory on the drive where Windows 95 is installed. You may change it if you wish.

By default, Winsock RSHD/95 installs as a Windows 95 service. A service is a program that starts automatically when Windows 95 starts. It is transparent and does not require anyone to be logged in to Windows 95. If you do not want Winsock RSHD/95 to be installed as a service, uncheck the Install as a Windows 95 Service option . Winsock RSHD/95 can then be run as a program from the Start menu.

Press the Install button to begin the installation. Press Cancel if you wish to exit. Files will be copied from the diskette onto your hard drive.

If you chose to install RSHD/95 as a service, Winsock RSHD/95 will be installed in Windows 95's list of services and it will be started for you. You do not need to reboot.

If you did not choose to install RSHD/95 as a service, a menu selection for RSHD/95 will be created on your Start menu. To run RSHD/95, find and select RSHD/95 from the menu.

See the section on Controlling Winsock RSHD/95 for instructions on how to manually start and stop the Winsock RSHD/95 service.

To remove Winsock RSHD/95, use the Add/Remove Programs applet in the Windows 95 Control Panel. Choose Winsock RSHD/95 from the list of programs by clicking on it, then click on the Add/Remove button. Verify that the RSHD/95 installation directory is correct and click on the Uninstall button. Winsock RSHD/95 will be completely removed from your system. However, if you have placed other files in the RSHD/95 installation directory, the directory will not be removed.

Under Windows 95, a service is a program that starts automatically when Windows 95 starts. It does not require you to log in to Windows 95 or select anything from the Start menu. It runs transparently. There is no RSHD/95 window. It does not appear in the Windows 95 Task List.

For those familiar with Windows NT services, Windows 95 services are much more rudimentary. There is no generic service controller as there is in Windows NT to allow you to start, stop, install, and uninstall services.

To give you some control over RSHD/95 when it is running as a service, a utility is included that provides some of the functions of NT's service controller. With it you can start, stop, and perform other functions that affect RSHD/95. This is explained later in the Controlling Winsock RSHD/95 section.

You can optionally run Winsock RSHD/95 as a Windows 95 program instead of a service. This requires that somone log in to Windows 95 and select RSHD/95 from the Start menu.

To start Winsock RSHD/95 as a program, execute the following command:

If you are executing this command from the Windows 95 MS-DOS, you should use the command:

If you do not use the start command, you will not have access to that MS-DOS Prompt window until RSHD/95 is stopped. Be sure that you do not already have Winsock RSHD/95 running as a service.

After you start RSHD/95, you will not see any window display. It runs transparently; it will not even appear in the Windows 95 Task List. If you need to stop RSHD/95, see the section on Controlling Winsock RSHD/95 for more details.

Winsock RSHD/95 will work properly using its default configuration. You only need to configure Winsock RSHD/95 if you wish to change any of the available options, enable security, or use the logging capabilities. By default, no security is enforced and no logging is done

You configure Winsock RSHD/95 by using the Windows 95 Control Panel. In the Control Panel, you should see an icon labeled RSHD. Double-click on that icon to configure Winsock RSHD/95.

Important Note: After changing a Winsock RSHD/95 Configuration option, you do not need to stop and restart Winsock RSHD/95. It will recognize the change, unless you disable the monitoring of the registry (see below).

NOTE: Each of the log files may refer to the same file name if you wish. They will not overwrite each other. Each message is appended to the end of the file. You should be sure to periodically delete the log file(s) because they can get large over time on an active system.

• The Minimized or Hidden options are useful when the system running RSHD/95 is actively used and is not a standalone server. With the Normal or Maximized options, the person using the system will see a window appear each time a command is executed through rsh.
• You cannot send keystrokes to commands that are minimized or hidden. Therefore,if you select the minimized or hidden option as the default, RSHD/95 will automatically run any program in a normal window when keystrokes are specified in the rsh command, overriding this setting.
• Using the Hidden option can cause administrative problems. When a program's window is hidden, it does not appear in the Task List, so there is not an easy way to stop a hidden program or to tell if any are running. There are utilities that allow you to see the hidden programs (such as the PView program that comes with Microsoft Visual C/C++).

• Never - Copy all files as binary

• Always - Convert all files

• Convert based on list of file extentions

• Convert based on contents of first block

With Unix, security is enforced on remote command execution using a combination of the password file (/etc/passwd), the hosts file (/etc/hosts),and the host equivalency files (/etc/hosts.equiv and $HOME/.rhosts).

Winsock RSHD/95 enforces security through the Security File. The name of this file is specified in the Winsock RSHD/95 Configuration in the Security File entry.

If you specify a Security File name and the file does not exist or the file is completely empty, all hosts and users are denied access.

Conversely, if you do not specify a Security File, all hosts and users are granted access. So if you do not wish to enforce any security, do not specify a Security File name in the configuration file.

Additionally, you can configure Winsock RSHD/95 to ensure that user names on remote hosts are valid on this system. You should only enable this security option if you use consistent user names across all of the systems on your network.

You create the Security File using a text editor. If you are using the Winsock RSHD/95 Control Panel applet, you can click on the Edit Security button to run the Windows Notepad editor to edit the security file specified in the Security File configuration option.

The Security File consists of lines that specify who may or may not access the PC using Winsock RSHD/95. The following are the options available in:

When specifying the host on the lines in the Security File, you may use either a host name or an IP address (in dotted-decimal format). If you use a host name, that name must be resolvable by TCP/IP, either through the hosts file or through DNS.

You may use wildcard characters when specifying the user and/or host name in the Security File. The wildcard characters that can be used are:

If the request is coming from a Unix system, the user name is the login name of the user. If the request is coming from another Windows PC, the method of specifying the user name is determined by the implementation of the rsh or rcp command you are using.

Note that the standard Unix rsh command (and the Winsock RSH command available from Denicomp Systems) allows a "-l" option to specify an alternate user name. The "-l" option has meaning on a Unix system, but is not especially useful with Winsock RSHD/95. However, if you do use the "-l" option to specify an alternate user, as with Unix, that user must be granted permission through the Security File in addition to the login name (Unix) or the name specified in your particular TCP/IP implementation (Windows/DOS).

To effectively use the Security File, you must first understand how it is viewed by Winsock RSHD/95.

When Winsock RSHD/95 receives a request, it sequentially processes the lines in the Security File to determine whether or not the host and user are granted or denied access. It looks at each line in the Security File until it determines that either the host or the user is specifically denied permission.

Winsock RSHD/95 begins by assuming that permission is denied for the request. It then examines the lines in the Security File to see if any of the lines pertain to this request.

Once Winsock RSHD/95 finds a line that denies access to either the user or the host, it stops looking and denies permission.

If it finds a line that grants permission to the user and/or host, permission is tentatively granted, but it continues to process the lines in the Security File.

If it processes the entire Security File and does not find a line that grants permission to the user and/or the host, permission is denied. If security was tentatively granted at some point and not denied subsequently, permission is granted.

For example, let's say that the following is the contents of the Security File:

In this example, if any user on the host "jetty" makes a request, permission will be granted, unless the user is "jackie", since "jackie" is denied access from all hosts (-jackie).

If "jackie@jetty" makes a request, Winsock RSHD/95 reads through the Security File and finds the host name "jetty", and tentatively grants permission. However, it continues and finds that the user "jackie" is denied from all hosts, so permission is denied.

Also, if any user on the host "booey" makes a request, they are granted permission unless the user is "gary", since "gary@booey" is specifically denied permission (-gary@booey). All other users on the host "booey" are granted permission except "jackie" (-jackie).

The user "fred" on the host "mars" is granted permission because of the line "+fred@mars". However, since the host "mars" does not appear on a line by itself, no other users on the host "mars" are granted permission except the user "robin", who is granted permission from any host (+robin).

Finally, all users making requests from systems whose host names end in ".netcom.com" are granted permission, unless the user is "jackie", since "jackie" is denied permission from all systems.

If you think you have properly set up the Security File, but you are being denied access when you think you should be granted access, the following provides some tips on determining the cause of the problem:

• Be sure that you have correctly specified the Security File name in the RSHD/95 Control Panel applet and that it actually exists.
• Be sure that you have saved the Security File as an ASCII text file. From DOSprompt, use the TYPE command to view the contents of the Security File.
• If the editor used automatically appends an extension to filenames (such as Notepad, which appends a .txt), be sure that you have specified this extension on the filename specified in the Security File field.
• Be sure that the Security File is stored on a local hard drive, not a network drive.
• If you have specified host names in the Security File, be sure that your system can resolve the names, either through DNS or through the HOSTS file. Try using the ping command to verify access to the host names specified in the Security File.

If these tips do not help, enter a filename in the Message File field and a 4 in the Message Level field in the RSHD/95 Control Panel applet. Then execute rsh or rcp from a system that should be given access, then examine the Message File. It will contain a trace of the steps RSHD/95 is using to validate the remote user and host.

With Unix, the rsh utility executes the specified command on a remote host and returns the standard output and the standard error output to the requesting host.

With Windows, there is no such thing as "standard output" and "standard error". Programs execute in graphical windows, so there is no way to return any output using rsh.

Therefore, when using rsh from Unix or another PC to initiate commands on a Windows PC, you will not see any output of the command on your screen. It will display on the PC that received the request.

For example, if you used the following command:

This would start Excel on the PC named "win95". You would see nothing on your screen as a result of starting Excel. Excel would be running on the screen of the PC named "win95".

The rsh command will NOT wait for the specified command to complete. The system issuing the request will regain control immediately after the command begins.

If you attempt to execute a command that does not exist or Windows returns an error trying to load the program, you will receive a descriptive error message on your screen from Winsock RSHD/95 to tell you that the command was not successfully executed.

You can optionally capture the standard output and standard error output of Windows Console or MS-DOS programs through Winsock RSHD/95 with the rsh command. This allows you to display the output of these programs that output to the standard output or standard error on another screen or capture it to a file on another system. It also allows you to send the standard input from rsh to the remote program. This is known as redirection.

By default, Winsock RSHD/95 automatically attempts redirection on every program executed using rsh, to capture the standard output and standard error and send it back to the rsh command, and receive standard input sent to it by the rsh command and provide it to the program executed.

If you mostly execute Console or MS-DOS programs through RSHD/95, this default behavior of automatic redirection is the most useful. However, it does have some downsides when you want to execute graphical programs through RSHD/95 (which do not have standard input/output/error) or you simply do not need redirection even for console or DOS programs.

The downsides to automatic redirection are:

• When executing graphical programs, there is some additional overhead in starting the programs because RSHD/95 tries to redirect the standard I/O, even though there is none.
• When executing graphical or console/DOS programs with automatic redirection, RSHD/95 does not return control to the rsh command until the program executed completes. The rsh command will not end until the remote program ends.

You can control this in two ways, if necessary:

Option 1. If you only occasionally need to use rsh to execute graphical programs or console/DOS programs where you do not want rsh to wait until they complete, you can add the special "<[WIN]>" option in the rsh command. This tells RSHD/95 that it should not attempt redirection on this program only. For example:

rsh win95 "<[WIN]%FP~%FX>" excel abc.xls

These will run the command "excel abc.xls" on win95 as a Windows program and send the specified keystrokes to it, disabling standard I/O redirection.

Option 2. If you mostly execute graphical programs or you usually do not want to do redirection on console/DOS programs because you do not care about the output, you should uncheck the option labeled Attempt Redirection on Every Command in the RSHD/95 Control Panel applet. If you uncheck this option, RSHD/95 will not automatically attempt redirection, unless you specify the special "<[CON]>" option in the rsh command. This tells RSHD/95 that it should attempt redirection on this program only. For example:

rsh win95 "<[CON]>" net view

This will run the "net view" command on "win95" and display the output on your screen. The "net view" command displays information on the standard output.

If you have unchecked the RSHD/95 Control Panel option labeled Attempt Redirection on Every Command, programs executed through rsh will return control back to rsh immediately after the program begins. It will not wait until it completes.

If you want the rsh command to wait until the program finishes executing, you can use the special "<[WAIT]>" option in the rsh command. For example, to execute the command "bkgprint" and wait for it to finish, use:

Winsock RSHD/95 provides the ability for you to send keystrokes to the Windows application you initiate using the rsh command. It also allows you to specify how the window is to be displayed (i.e., normal, minimized, maximized, or hidden). This provides you with some "remote control" over what the program you run does once it starts.

For those of you who program in Microsoft Visual Basic or the Visual Basic for Applications macro language, this is very similar to the SendKeys capability of those programming languages.

The standard syntax of the rsh command is:

rsh hostname command

This will execute "command" on the host "hostname". Winsock RSHD/95 allows a slight modification of the rsh syntax to send keystrokes. This is compatible with all rsh commands. The alternative syntax for sending keystrokes is:

rsh hostname "<keystrokes>" command

If the first parameter after the host name begins with a less-than sign (<), that parameter is interpreted as keystrokes to be sent to the command specified in the next parameter. The keystrokes must end with a greater-than sign (>). You must also enclose the entire parameter in quotes so special characters and spaces are not interpreted by the operating system.

For example, if you wanted to run the Windows Notepad on the PC named "win95" and type "This is a test" on the first line, the command would be:

If you looked at the win95's screen, you would see the Windows Notepad with "This is a test" on the first line.

You cannot send keystrokes to an application that is not designed to run in Microsoft Windows (i.e., MS-DOS programs).

Important Note: Due to a limitation in Windows 95, you cannot send keystrokes to an application started through Winsock RSHD/95 if there is no one logged in to Windows 95. The program will be executed, but it will not receive the keystrokes.

Winsock RSHD/95 also allows you to specify special keys in the keystrokes parameter that cannot normally be typed on a command line, such as embedded Enter keys, function keys, ALT keys, etc.

Keystrokes are sent sequentially as they appear between the "<" and ">". To send a single character, use the character itself. For example, to send the letter "X", use the letter "X". To send the word "hello", just specify those letters.

To specify keys combined with any combination of Shift, Ctrl, and Alt keys, prefix the regular key code to one or more of the following codes:

For example, to send the Alt-F keystroke, specify "%F". To send Ctrl-Alt-D, specify "^%D".

To send the Enter key, use the tilde (~).

To specify that the Shift, Ctrl, and/or Alt keys should be held down while several other keys are pressed, enclose the key codes in parentheses ( ). For example, to have the Alt key held down while X and D are pressed, use "%(XD)". You could also use "%X%D", but if the Shift, Ctrl, and/or Alt keys need to be held down for a number of keystrokes, the parentheses can make the string shorter. Also, you would want to use the parentheses if the application detects the release of the Shift, Ctrl, and/or Alt keys and that is not desired.

The following characters have special meaning in the keystroke parameter, so they must be enclosed inside braces ({ }). Some of these special characters have not been explained yet.

To send characters that are not normally displayed when you press a key (such as Enter or Tab) and keys that represent actions rather than characters, use the following special codes:

To send the function keys F1 through F16, use {F1} through {F16}.

You can also specify that a key is to repeat itself a certain number of times, without repeating the key itself in the string. To repeat a keystroke, use the format:

{keystroke number}

Where "keystroke" is the key to repeat, followed by a single space, then the number of times to repeat the key. For example, to press the down arrow key eight times, use "{DOWN 8}". To type thirty *'s, use "{* 30}".

Under some circumstances, it may be necessary to pause for a specific time before sending keystrokes to allow a program operation to complete. This is usually necessary when a program ignores keystrokes that have been queued while a long operation takes place.

Within the keystroke list, you can specify pauses by using the special {PAUSE #} keystroke.

This is not actually a keystroke, in that it does not press any key, but it can be included anywhere within the keystroke list. It will pause the specified number of seconds.

For example, the following keystroke list will press Alt-F, P, wait 10 seconds, then press Alt-F, X:

You can specify multiple pauses in the keystroke list if necessary.

The following example, will start Microsoft Word, load a file, print it, then exit.

The keystrokes are:

Note that if this example were being run from a Unix system, you would have to use two backslashes (\\) for every one desired backslash because the Unix shells interpret the backslashes as special characters. The command would then be:

If your keystroke strings get rather long or complex, you can store them in a keystroke macro file so you do not have to specify all of them each time you use the rsh command.

To create a keystroke macro file, you must use a text editor (or a word processor, but be sure to save as an ASCII file). Enter the keystrokes as you would on the rsh command line, with the following exceptions/reminders:

To use a keystroke macro file, enter the at-sign (@) followed by the filename in braces ({ }) where you would normally specify keystrokes on the rsh command line.

You will most likely need to specify a full pathname of the keystroke file on the PC running Winsock RSHD/95, unless you know the working directory of Winsock RSHD/95 on the system running it and the keystroke macro resides in that directory. You may use forward slashes (/) instead of backslashes if you wish; this makes life easier for Unix users because the shell interprets the backslash characters.

For example, if you had a macro in the directory \kbmac\printss.mac on the PC running Winsock RSHD/95, you could use it with this command:

This would run "excel" on win95 and send the keystrokes stored in the file \kbmac\printss.mac to it.

You can intermix command line keystrokes and macro file keystrokes. That is, you can specify some of the keystrokes on the command line and use some from a macro file. You can also use multiple macro files.

For example, let's say we want to print a file using rsh through a Windows application called "wintiff". We want to store the keystrokes in a macro file, but do not want to store the filename in the macro file because it can change.

To do this you can store the first set of keystrokes in one macro file, specify the filename on the rsh command line, then store the remaining keystrokes in a second file.

For example, let's say the file is "mypic.tif":

This example copies the file "mypic.tif" to the \tmp directory on win95. Then it runs "wintiff" and first sends the keystrokes from the file \kb\tif1.mac. That macro ends when "wintiff" requires a filename. The keystrokes to "type" the filename come from the rsh command line since the tif1.mac has ended. Then it continues by sending the keystrokes in the file \kb\tif2.mac. That is:

Winsock RSHD/95 also allows you to specify the window type of the application being run. Normally, the application is run using the default window type specified in the RSHD/95 Control Panel applet (the Default Window Type of Commands option)."normally", as if you ran it by double-clicking on its icon (assuming you did not set up the icon to run it minimized).

If you want to specify a different method of displaying the application's window, you can specify this inside the keystroke parameter by enclosing the method in square brackets ([ ]).

There are two methods of setting the window type. You can use one of the words shown below or you can use a number. The options are:

Other numeric values may be used - they correspond to the Windows' ShowWindow function (for all you programmers).

For example, if you want to run the Windows Notepad maximized, viewing the file "heyyou.txt", you would type:

rsh win95 "<[MAXIMIZE]>%FOheyyou.txt~" notepad

This runs the Notepad maximized, then "presses" Alt-F-O (File Open) and types the filename "heyyou.txt" and presses Enter to load it.

If you wanted to run some application that does some task and exits, you could run it minimized using:

Note that Windows does not allow you to send keystrokes to a minimized or hidden application. Therefore, "[MINIMIZE]", "[HIDE]", "[0]", or "[2]" should always appear alone between the "<" and ">". If you specify other keystrokes, the application will not receive them (Windows will beep at you for each keystroke).

RSHD/95 internally understands four special commands that allow you to remotely shutdown, powerdown, or reboot the Windows 95 system or to logoff any user on the system through the rsh command. These commands require the special <[INTERNAL]> or <[INT]> indicators. The commands have the following syntax:

rsh win95 "<[INT]>" shutdown [#]

rsh win95 "<[INT]>" poweroff [#]

rsh win95 "<[INT]>" reboot [#]

rsh win95 "<[INT]>" logoff [#]

The [#] are optional. You can specify a number of seconds to delay the action in this parameter. If you do not specify a number of seconds, it is immediate. For example:

The shutdown command shuts down Windows 95 and takes you back to the screen that says that you may turn off the power. After the shutdown, RSHD/95 will no longer respond to any requests.

The reboot command shuts down Windows 95, then restarts the PC and Windows 95. If RSHD/95 is running as a service or in the Startup group, it will restart with Windows 95.

The poweroff command will only have an effect if your system allows Windows 95 to turn off its power. If the system does not, it will have the same effect as the logoff command.

The logoff command will log off any user that is logged on to the Windows 95 system and then display the "log on" dialog box.

Winsock RSHD/95 also provides Remote Copy (RCP) Server capability. This allows you to copy files to and from a PC running Winsock RSHD/95 using the rcp command.

The rcp command is commonly found on Unix systems, Windows NT systems, and in some TCP/IP packages for Windows and DOS. If your TCP/IP package does not provide the rcp command, you can use Winsock RCP from Denicomp Systems (not included with RSHD/95).

The rcp command is described in more detail in your TCP/IP package manual or with the manual that comes with Winsock RCP. However, here are a few examples of its use.

Important Note: Unlike the standard Unix rcp command and Denicomp Systems' rcp command (found in the Winsock RCP/RSH package), the Windows NT rcp command copies all files with ASCII conversion by default. Binary files must be copied using the -b option of NT's rcp command. If you do not use the -b option on binary files, the contents of the file will be altered on the destination system.

To copy a file from the host named "srvpc" to your PC or Unix system, use:

The file "yourfile" is copied from the host named "srvpc" to the file on your PC named "myfile". The host "srvpc" could be running either Windows and Winsock RSHD/95 or Unix.

To copy a file from your PC or Unix system to the PC named "srvpc", use:

The file \lists\xmas.doc is copied from your system to the file xmas.doc in the directory \word\lists on the PC named "srvpc".

To send the entire directory tree from your PC or Unix system to "srvpc", use:

All of the files and subdirectories in the directory \share are copied to the PC named "srvpc". It will create a \share directory in the root directory (\) of srvpc.

If the \share directory contained any subdirectories, they would be created on the other PC and all the files in them would also be copied.

To copy all of the files ending with ".xls" from "srvpc" to your PC, use:

This copies all of the files ending with ".xls" in the directory \sheets on "srvpc" to the current directory (.) on your PC.

You can use drive letters if necessary. For example, to copy a file from the A: drive on the "srvpc" to your PC:

This will copy "file.txt" from the A: drive on "srvpc" to the file "file.txt" on your system.

NOTE: Winsock RSHD/95 allows you to use both slashes (/) and backslashes (\) for directory separators. It will adjust appropriately. This is especially important for Unix users, since backslashes are interpreted by the shell and must be escaped by using two backslashes for every one backslash. Use slashes instead.

The Winsock RSHD/95 service can be controlled from the RSHD/95 Control Panel applet using the Service Control button. This can be used whether you are running RSHD/95 as a service or as a program.

Support is available via e-mail through the Internet and Compuserve.

Internet: support@denicomp.com

WWW" http://www.denicomp.com

Compuserve: 71612,2333