🚀 go-pugleaf

In article <72771@microsoft.UUCP>, steveha@microsoft.UUCP (Steve HASTINGS)
writes:

>                 IMHO, MKS is unusable because they insist on treating
> "c:foo" as identical to "c:/foo"; they claim this is more UNIX compatible
> and therefore desirable.  I say that if I had meant "c:/" I would have
> typed "c:/" instead of "c:" and it is a pain to use MKS when you work with
> networks and can have long paths on a half dozen drives or more.
> 
  I won't belabor the point about "c:" vs. "c:/".  It seems to have been
beaten around enough.

  I can comment on MKS's tech support; in one word: Super.  I had a few
problems with the first disks I received.  MKS promptly sent me a new
version within a week (must allow for UPS you know).  I had another
problem dealing with file management and disk organizers.  MKS quickly
explained the problem in a very knowledgable manner.  Unfortunately, it
was one of those problems where I was embarrased that I didn't think of
the solution myself.  All of this support was obtained through
CompuServe mail.  At the time, I didn't have net access and the phone
would have been outrageous.

  I am very pleased with the MKS tools.  I especially like the awk,
sed and vi tools.  They come in very handy.  It's unfortunate not many
MSDOS programs allow the '/' for path names.  <sigh>

  Shane();

--------------------------------------------------------------------------
From the keyboard of:			     email: sdawalt@cs.wright.edu
	Shane A. Dawalt
--------------------------------------------------------------------------