#AREXX/WSHELL/CONMAN/A2.0
38 messages in this thread
Bill –
I have just recently upgraded from AmigaDOS 1.3 to 2.04. I would like
very much to continue to use your excellent programs AREXX, WSHELL, and
CONMAN. Some questions.
1) Is CONMAN/NEWCON still valid and useful under 2.04? 2) Which version of
AREXX should I use? I upgraded to v1.15 (?) and, of course,
have the version that comes with AmigaDOS 2.04. 3) How do I overcome the
problem with 2.04's internal (though documented external)
RUN command. I alias/aliased quite a few programs, WHAP! for example,
using the
RUN command under AmigaDOS v1.3. It seems that I am unable to get RUN
to work
under WSHELL under 2.04.
Things that make you go, "Hmmmmmm?"
– Nelson …
– via Whap!
Nelson,
I didn't think of this when I talked with you the other day, but have
you tried setting up an alias for 'run' to be 'runwsh'? Might be worth a
try.
Hope this helps….
…BobR
Aliasing run to runwsh would be my recommendation as well, or possibly just
changing the aliases to use runwsh directly.
-Bill
Bob –
Jeesh! Ya'd think I coulda thunkt that myself! Thanks for the idea…
I'll try it and let you know how it goes.
– Nelson …
– via Whap!
3) Bill has a newer verision of WSHELL for 2.0 that you will want to
inquire about. Given the amount of change that has gone on with 2.0, you
shouldn't be surprised by RUN problems. However, I would check to make
sure that there is a RUN command to begin with. It is my memory that RUN
is now internal and hence can not be accessed from an external program. If
your alias has C:run instead of RUN you might be able to make things work
with taking the C: out.
2) Use the version of AREXX that came with 2.0. 1) Conman is still valid
under 2.0, but until you get an updated version of WSHELL, I would
recommend using the C= supplied console handler.
John A. Toebes, VIII – via Whap!
Registered users of WShell will receive notices regarding the upgrade to
WShell 2.0 later this month, or early in December. Anyone who hasn't
registred their copy of WShell, or who has moved since they originally
registered, should send in the card or address update right away.
The new WShell software has lots of new features, including console-window
menus, a scrollable session history, drag-and-drop icons for shell windows,
and of course support for AmigaDOS 2.0 features.
Hey Bill, how much will you let me talk about what is in there? I'm not
sure I could live without the drag-n-drop stuff.
John A. Toebes, VIII – via Whap!
Since WShell 2.0 is just waiting for the manuals to come back from the
printer, discussion of the new features sounds like fair game. I'll be
sending out update notices in a couple of weeks …
For those of us who would be purchasing new rather than upgrading, what is
MSRPrice for WShell 2.0?
. . . . . JimDoc
Jim,
Suggested retail for WShell 2.0 is $89, and it will be available from
dealers and mail-order companies shortly after it ships.
In addition to an upgrade offer for current WShell customers, I'm also
planning a special offer for registered ARexx customers. Details on this
(and a flyer for WShell 2.0) will be mailed within a few weeks.
-Bill Hawes
yay! :^)
John –
Welcome John, as a SYSOP. You are quite correct in your assesment that
RUN has become an internal command… a la MS-DOS. It is, however,
documented as a C: command in the AmigaDOS 2.0 manual that came with the
2.0 Enhancer kit.
I have, at least temporarily, solved the problem by replacing all of the
WShell aliasing of RUN with RUNWSH. That seems to be working as well as
necessary for the moment.
So much time and so little to learn! … Wait! Strike that! Reverse it!
9-)
I have heard a lot about WShell and am planning on buying it. Will the new
version run under Wb 1.3? I would like to use it right away, but haven't
yet decided whether I am going to upgrade the hardware on my 1000 to use
2.04 or just go buy a 2000 or 3000. (and probably won't decide until after
Christmas 🙂
Yes, WShell 2.0 will run under AmigaDOS 1.3, but at a somewhat reduced
level of capabilities. No console-window menus or support for dropping
icons into shell windows, for example; these need the new AmigaDOS 2.0
software.
-Bill Hawes
Bill,
Is WShell 2.0 now out? If so I WANT IT!!!! BTW have you heard
about the new ARexx compiler which is due out shortly? Very nice product.
Steven,
WShell 2.0 is scheduled for release in a couple of weeks, and notices to
registered users will be mailed shortly. You'll like the new features
(grin).
I haven't seen the REXX compiler, though I may take a look at it once it's
released in a non-beta-test form. BTW, I would like to remind you (and
others) that “ARexx'' is a trademark for my company's product, so to avoid
confusion you should refer to a REXX-language compiler by its product name.
-Bill Hawes
Bill,
Sorry, Bill. It's called the Rexx Plus Compiler by Dineen Edwards
Group. It should be out shortly. I have been beta-testing it and the
final version should be out as soon as the final documentation is completed
and printed. It provides a good increase in execution speed for scripts
which are computational intensive or that use large stem variables. I
think it should prove an interesting product for those who are big users of
ARexx (TM). I'm anxious for the new shell. I don't know how I would live
with my Amiga without both ARexx and WShell. Both make the Amiga bigger
than life!
You've got that right. Bill's done more for the system software than any
other developer, single handed.
Ben
Yeah, Ben. Just imagine what he could do if he got serious!!
I want my 2.0 :^)
How about just nuking it off, C.O.D. to us, if posssible?
Ben
Ben,
Thanks, I appreciate your interest in WShell 2.0. We expect to start
shipments on December 4, but will keep the software open for potential bug
fixes until the last possible moment. Love to squeeze those bugs out!
(grin)
-Bil Hawes
What a mental image THAT conjures up. :^)
Can't do without my ConMan, even under 2.0. Whatever would I use for pipes?
-larry
The answer is simple… Get Bill's upgrade. I have been using it for quite
a while and you will be quite surprised at the new features. The
Scrollback console and the Icon Drop ins alone are worth the entire
upgrade.
John A. Toebes, VIII – via Whap!
Hmm.. are you saying the new ConMan is out already?
Don't care much about the dropi-in icon stuff. I only tolerate WorkBench
running because it's too much hassle to get rid of it, but the scrollback
console is worth a look.
The new WShell 2.0 software comes with a completely rewritten custom
console handler (called the DisplayHandler); it doesn't use ConMan anymore.
In addition to providing a session history with a scrollbar, the
DisplayHandler supports console-window menus, "jumping" from screen to
screen, and an assortment of new editing features.
The WShell 2.0 software hasn't been released yet, but will start shipping
in a few weeks.
-Bill
Like others, I eagerly await WShell2.0. I'd just like to take this
opportunity to thank you for the software you've done for the amiga. You're
definitely part of the amiga solution!
–jp–seattle–
Bill:
on my system (a 2000) back in the old days of 1.3.2 (I've been running 2.0
for a long time) I was able to fully replace the Ados shell with the
WShell. Will that still be possible with 2.0 Wshell? Is there any reason to
keep the ADos shell around once using the WShell?
-Mike Schiller
In sunny Fort Lauderdale
AmigaDOS 2.0 provides a facility called the `User Shell' whereby an
external (non-ROM) shell can be used by most system commands and
functions. With WShell 2.0 installed as the UserShell, the newshell
and run commands invoke a WShell, and Amiga-E from Workbench runs a
command in a WShell environment. It's still possible to use the ROM
shell with a UserShell installed, but most end-user-oriented
operations go for the user's choice of shells.
Bill:
Thanks for the info. Even though I'm a developer, I sometimes don't
understand all the technical stuff, and need it explained to me. This 'user
shell' facility sounds great. WShell 2.0 sounds great, and as soon (if not
sooner :>) as I get the upgrade notice, I'm gonna grab it (WShell 2.0 that
is) Now that Arexx is provided as part of WB 2.0 are you going to be doing
any further updates to it? I'm a registered user of both ARexx & WShell for
a while now (long before 2.0) and was wondering if reg users would be
getting any upgrades past the version distributed with WB. Thanks for the
info.
Mike,
Registered ARexx customers will continue to receive upgrade notices from my
company as future versions become available; they'll have a choice of
ordering directly or waiting for the next Commodore-supplied upgrade. I
don't foresee any major changes to ARexx in the near future, though I'd
like to work on updating and improving the documentation.
-Bill Hawes
Bill, what do you think of the book "Using Arexx on the Amiga" from Abacus?
I picked it up about a week ago and think they did a very good job, and the
best book from Abacus yet.
John – K7KB (via Whap!)
Bill,
Have you yet put in a method for finding out all of the elements in a
stem variable? It seems to me that a mechanism for 'looping' through an
entire stem variable list would be VERY useful. I know that 'standard'
REXX doesn't have this capability. If you feel constrained to only supply
features in the 'official' language, to whom can get in touch to suggest
this greatly needed feature.
Most importantly of all, Bill, does the new stuff still have PIP: and
fcomp?
-larry
Yes, the PIP: mode of operation is supported by the new console handler,
and filename-completion is provided by FComp as before. FComp also
implements the iconic drag-and-drop operations by receiving AppWindow
messages from Workbench and posting a string associated with the icon to
the shell window. Since the icon "string" can be any set of control
sequences, you can build icons to graphically edit a command line -add or
delete words, search for commands, etc.
You can also set up classes of icons (e.g. GIF, ILBM, TEXT) such that a
default tool will be run whenever an icon of that class is dropped into the
shell window. It's an interesting capability, so even a non-Workbench user
may find it worth trying.
-Bill
<big smile>
Thanks Bill! Looking forward to it.
Ahh… I knew there was something I wanted to ask (if you don't mind
preannouncing). Is there a 'backtick' provision in the new WShell?
-larry
Larry,
Yes, WShell 2.0 provides improved support for backticked-command
substitution. Any number of backticked commands can be placed on the
command line, and nesting is allowed using a “ (doubled-backtick)
sequence. Also, WShell detects errors in the commands being expanded and
aborts the command line after displaying the partial text (if you've got
the command-echo option enabled.)
-Bill