Glorb DOS version 2.0 is a MSDOS shell based on Maintenance by Brian Veditz, (source code for maintenance can be found on SSI).  All I did was change a few things so it could be used on any system, and not systems that have WC installed on D:\. I have also added a .cfg file so you can specify the dir you want this program to start in. I also added a few system utilities, ping, netstat, whois, finger, and traceroute. for a description on them see utilities.txt
 
Installation:
Copy all wcx files (or only glorb dos.wcx if you dont want the utilities) and all the .pif files (or only dosdir.pif if you dont want the utilities) into your WC dir, then copy glorbdos.cfg into your wc:\data dir, then copy all the .exe files into the c:\windows or the c:\winnt dir (or whichever directry you have ping.exe, netstat.exe, etc in) this will let teh utilities preform whois and finger functions under Windows NT DO NOT OVERRITE THE EXISTING FINGER.EXE!! then edit glorbdos.cfg. Some of the utilities may seem to lock up, but it may take a few miniutes for things like ping, whois to get the info back from the host servers.

Things you can do with Glorb DOS:

                                                                                 
  BEEP                    Make your computer beep
  CD <DIR>                Change Directory
  CHAT                    Chat between Nodes
  CLS                     Clear Screen
  COPY <FILE1> <FILE2>    Copy a file
  DEL <FILE>              Delete a File
  DIR <params>            Directory (optional Directory & params)
  DOWNLOAD <FILE>         Download a file from current directory
  EDIT <FILE>             Edit a text file
  EXIT                    Exit DOS Shell
  FINGER                  Display info on a user and/or a server
  HELP                    This Command List
  MD <DIR>                Create a Directory (also MKDIR)
  NETSTAT                 Shows all connections to your computer
  NODM                    Enter a node message (ex. I'm away)
  PING                    Sends data packets to a host computer
  RD <DIR>                Remove a Directory (also RMDIR)
  REN <FILE1> <FILE2>     Rename a file from <File1> to <File2>
  RUN <FILE>              Run a WCCode Program (ex. RUN DOS.WCX)
  TELNET                  Opens a telnet session to a remote host
  TRACERT                 Trace an address
  TYPE <FILE>             Display a Text File or Screen
  UNZIP <FILE> <PARAMS>   Zip a file
  UPLOAD <FILE>           Upload a file to currect directory
  USERED                  Sysop User Editor
  WHO                     Who is Online?
  WHOIS                   Get info on a Domain
  ZIP <FILE> <PARAMS>     Zip a file
  ZIPVIEW <FILE>          Display contents of a Zip file


Here are some more notes from the original version; most of this still applies to this version.
                        
  
   The Maintenance program is basically a WCCode version of a dos shell.
It has many limitations, not the least of which is that you cannot
actually run a dos program.  Of course, since you are using windows,
running a dos program is of little use.  The main use is to edit text
files from remote, view display files, run WC-Code programs and download
and upload files from any directory.  This is not only handy when you
are calling from remote, but has many useful local uses.  For instance,
viewing a .BBS file cannot be done in standard dos, you have to load up
your editor and view it there.  With the maintenance program all you
need to do is switch to the directory of your display file and 'Type'
It.  The second local use is for running WCCode programs locally.  Yes,
you can do this with WCRun, but its a tad easier to do from the
Maintenance software.  Perfect for those times when you need to run
the configuration program for some door.

   The limitations?  One, you'll notice the pif file with the archive.  The
Problem I had on my system is that dos windows do not close out.  You can
alter this somewhere in windows, but if for some reason you don't want to
make that a permanent change, I made a little pif file which it uses to
execute dos shells (for the dir, unzip and zip commands)...  Without this,
your system will seem to freeze up, since the real 'shell' may not return
back to the maintenance program.

   The next limitation is editing text files...  you can't edit anything
that has longer then 70 or so characters.  That is, anything that the
Editor will wordwrap around if you try to edit it.  I wouldnt bother.
If you have doorway, I would recommend using something like that to run
the edit command on the file the user specified.  I do not have any
Details on how to do this however :)  perhaps someone will make a good
wccode editor for editing things other then messages. Until then, this
is the best we've got.  The only real use for this is to edit 'skinny'
bulletins or to edit some batch files.  Don't bother trying to edit your
graphical menus, it will destroy them. :)

   The Zip, Unzip and Directory commands all run shells, as mentioned
above...  That makes it a limitation since any dos shell can cause havoc
with your system and windows.  The directory routine can be replaced with
a good findfile routine (findfirst, etc)...  the zip and unzip routines
I'm not really sure how you could replace.


Glorb Software BBS, bbs.glorb.com, telnet/http
released 8/15/1999 version 3.2f
