#Help
Mr. Hawes
On April 10, this year, I wrote you about some problems I was and
am having with WShell V2. As I have not heard from you in reply, I have
come to the conclusion that either you do not support your product or you
did not get my letter. I prefer to believe the latter and, indeed, this
could be the case as the New Zealand postal service sometimes assumes the
character of a third world country and letters to and from the U.S.
sometimes go astray. At any rate, I will try again here. A copy of my
original letter follows.
J.D. (Don) Finlay
105 Norwood Rd.
Bayswater, Auckland 9
New Zealand
April 10, 1992 Wishful
Thinking Development Corp P.O. Box 308 Maynard, MA 01754 U.S.A. Dear Sir,
As a new owner of WShell 2.0, (Serial #1107) I write in search of
aid and comfort. I assure you I have read the manual before writing to
you. It may well be that I have been taken unexpectedly stupid as this has
been known to happen, but I can not find answers in your printed pages and
I can find no one else in New Zealand who knows anything about your
product.
First about my system. I run a 2000 with 5MEG memory. One meg
chip and the expansion is run off of a Commodore 2058 card. I have two
floppys and two hard drives controlled by a Commodore 2090A card. The
system has a rom switcher with both 1.3 and 2. roms. I work mostly with
the newer rom and WB2.04. I installed WShell with the supplied program and
am reasonably sure that all required programs are located where they should
be. I will enclose a copy of my startupsequence in case that should be
causing the problems.
The largest worry so far is that I can not get SetExecute to work
at all. It seems that about every fifth thing I attempt to use requires
Execute and it has become so frustrating that I am not using WShell at this
time. I have tried running SetExecute from the startup-sequence and as a
direct command from a shell and in neither instance am I able to use
anything which requires Execute. Help!
"Assign dismount CON:" doesy