*** RServer *** (c) MJ Micro Systems 1994 Allows a DOS PC to execute NT commands remotely over named pipes. *************** FEATURES: Multi-user Automatic startup as a service Security Protocol independant (uses Named-Pipes) Routable if underlying protocol is TCP/IP --- This is a SHAREWARE program which means I only want a measly $9.95 for each NT server you use it on or $49.95 for your entire network. The DOS client is free. Please make checks payable to: MJ Micro Systems 6007-C Curtier Dr. Alexandria, Va. 22310 Other NT utilities are coming and people who register will recieve notifications and updates automatically. --- INSTALLATION INSTRUCTIONS: -------------------------- By now you've already unzipped the file to be able to read this. What you probably didn't do was unzip this file using the -d option which unzips the RSERVER sub-directory. So let's start at the begining. 1) Unzip RSERVER.ZIP using the -d option onto a floppy (any type of floppy). You can alternately unzip it to your hard disk then XCOPY it to a floppy. 2) Make the floppy your current drive and type in SETUP. 3) Copy the file RADMIN.EXE from the root of the floppy to all the DOS PCs that you want to access your NT PC(s). Example usage: RADMIN \\myserver That's it... TECHNICAL OVERVIEW: ------------------- This section is for people who want to know how this thing works so they can be more self supporting (or they are just curious). As an overview, the host program RSERVER and SERVER wait for a DOS client (RADMIN.EXE) to connect. It then spawns an NT command processor and hooks stdin and stdout back to the DOS client allowing the DOS client to execute NT commands as if you were actually on the NT PC. The only drawback is you cannot remotely run programs that don't use stdin or stdout, such as graphics or edit.com. If and when NT supports an API that allows the console to be completely redirected I'll update this program. To test a program you are unsure about try starting it when you are on the NT PC and redirect it to a file using the > redirection. If it writes its output to the file instead of the screen you should be OK. Or you could just run it from the DOS PC and if it doesn't work then, oh well press Ctrl-C. RSERVER.EXE is just a program that talks to the Service Manager and fires off the process SERVER.EXE. This allows the program to automatically start when no one is logged on. The way services in NT work is there is a process that is registed with the Service Manager that can send and recieve info about service states. It then fires off the parent thread or threads that actually do the work. By controlling this master thread, the service can start, pause or stop all the child threads. In this program I create a child process so I have to specifically suspend or terminate the process (no big deal). SERVER.EXE is the real program that can be used with or without RSERVER.EXE. If you just use SERVER.EXE then you must be logged on and start the program either in your STARTUP group or by manually starting it. RADMIN.EXE is the DOS software. Not much to say here except I'm using async i/o. This means if you type in a command such as NET START that doesn't return instantly you can still type in your next command to execute without it returning from the first. The only catch is the characters get a little scrambled. I've marked this as a future enhancement. INSTSRV.EXE is something I compiled out of the Visual C for NT samples. I use it to install RSERVER as a service. You can use it to de-install RServer by typing in "INSTSRV RServer remove" and deleting RSERVER.EXE and SERVER.EXE from your WINDOWS or WINNT sub-directory (whatever you may have called it). SETUP.EXE automatically figures out where NT is installed and copies the files to the right places and installs it as a service. If you would like to put it in your own sub-directory you can by first removing it (if you installed it already), then manually copy the files RSERVER.EXE and SERVER.EXE to where ever you want, then run the INSTSRV RServer c:\your\location\RServer.exe SUPPORT and PATCHES: -------- If you have tried everything and still cannot get this program to work you can contact me through Compuserv at 76170,2475. A better suggestion is to try the LANMAN-L listservice. I monitor this frequently and although it's read only for me I can atleast here your suggestions and problems more quickly. Also there are quite a few very helpful people who participate on that list who could provide assistance. Patches will be posted on Compuserv and the Internet. SPECIAL THANKS: Mike Partain who helped me through some 'tuff spots in code. Chris Ohlandt and Al Graeff for their suggestions and testing efforts.