Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!uwvax!umn-d-ub!nic.MR.NET!shamash!nis!com50!kksys!bird
From: bird@kksys.UUCP (Mike Bird)
Newsgroups: comp.binaries.ibm.pc.d
Subject: BEWARE of changing the command line switch (switchar)
Keywords: switchar COMMAND.COM
Message-ID: <824@kksys.UUCP>
Date: 16 Oct 88 20:27:55 GMT
Distribution: na
Organization: K and K Systems, Minneapolis, MN
Lines: 51


BEWARE: When you change the command line switch on COMMAND.COM, there are
quite a few products that no longer will work.  Let me (try) to explain what
I'm talking about:

A friend gave me the executable of switchar.  This will take any character
specified on the command line and change the command line switch to that
character.  Since MeSsy-DOS can handle paths specified with either a '/' or
an '\', and it is COMMAND.COM itself which specified that '/' is a command
line switch, I am now able to use paths with a '/' an stop getting confused
between UNIX and MS-DOS.  However, I discovered several problems.  This led
me to believe that something was being screwed up by the switchar program.
Another friend of mine used to work for a company (now defunct) who was a
licensed MicroSoft OEM.  He still had the OEM book from MS.  In it, there is
documented a MSDOS function x'37' subfunction 01.  I created a TP4.0 program
to use this function, and it worked identically to the switchar program.
Identically in every respect.  Same problems.  So, I conclude that the
problems are in the products I'm using, and not in the programs which
switch.  Here are some examples of the problems I'm having:

I have a LOGITECH 3-button serial mouse (great mouse!).  It came with
software to simulate keystrokes.  This allows me to use the mouse with
programs which do not communicate with the mouse directly.  You have to
"program" the mouse for each emulation.  It also included a program (called
CLICK) to automatically load the emulator with the proper program based upon
the command line or batch file entry.  This makes the re-programming of the
mouse transparent to the user and is a wonderful help.  However, CLICK
refuses to work when the command line character is switched off of '/'.
Switching it back lets it work again.  I called LogiTech's technical support
line, and was informed that function x'37' is a reserved function, so they
won't support their programs if I'm playing with reserved functions.
Apparently, the DOS technical reference manual doesn't document function
x'37' while the OEM manual does.

Another program I have problems with is one I got from PC magazine.  It's
called SWEEP, and it will duplicate a command on your current directory and
all sub-directories of your current directory.  It's a great way to get rid
of .BAK files just before doing a full-disk backup.  Anyway, when it tries
to do it's thing (I think it EXECs the command).  I get the DOS prompt and
I'm in an environment where NO environment variables were copied from the
parent.  The prompt is the default, no path exists, etc.  When I EXIT back,
I get this repeated for all sub-directories as well.  Changing the command
line switch character back to '/' clears the problem up.

So, as I say, be careful when you switch the command line switch character.
Some of your most cherished utilities may refuse to work. 
-- 
================================================================================
Mike Bird (These opinions are mine, dammit!) Mail paths: bird@kksys.kksys.mn.org
You can't call ME books!                 -or-   claudius@kksys.kksys.mn.org!bird
Void where prohibited by law.            -or-       ...rutgers!bungia!kksys!bird