A description of procomm
john...@my-dejanews.com
The Discussion Forum: dejanews.comm.procomm has been created.
The description that was given for this forum is:
Since Symantec has acquired
Quarterdeck, there is no Peer Support
area where Procomm Plus users can ask
Questions about the product and the
Aspect scripting language.
This forum is developed to solve this
problem.
If you have a question about Procomm
Plus and/or the Aspect Script Language,
post it here!
Here is some important information about this Forum:
Forum Name: dejanews.comm.procomm
Forum Web address:
http://www.dejanews.com/~procomm/group/dejanews.comm.procomm
We encourage you to leave your mark. Post a message to this forum
to really get things started.
------------------------------------------------------------------
Deja News - The Discussion Network
http://www.dejanews.com/
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
jsch...@mail.coin.missouri.edu
john...@my-dejanews.com wrote:
> The Discussion Forum: dejanews.comm.procomm has been created.
> The description that was given for this forum is:
>
> Since Symantec has acquired
> Quarterdeck, there is no Peer Support
> area where Procomm Plus users can ask
> Questions about the product and the
> Aspect scripting language.
>
> This forum is developed to solve this
> problem.
Some people may have seen my messages on the various Symantec boards, but
I'll introduce myself a bit more. I worked with Datastorm, then Quarterdeck,
for approximately 4.5 years. I started off in tech support, then moved into
QA after about a year. I've got a fairly broad knowledge of the various
flavors of Procomm, but I know more about the various Internet modes,
terminal emulation, and ASPECT. However, I had some exposure to just about
all areas of the product, so feel free to ask me any questions. I may even
know the answer!
---- Posted via Deja News ----
-- Visit the Procomm Plus / Aspect Script community
-- http://www.dejanews.com/~procomm
john...@my-dejanews.com
becoming a moderator for some of the forums?
John
zh...@fisci.com
our DOS application use procomm plus 2.0, we are now trying to
migrate to version 4.0 for it's Y2K compliance, but not the
application, which will stay DOS for a while.
The old script can not be recognized under version 4.0's ASPECT, and
gets a lot of errors if I try to compile it.
A post in the knowledge base suggests to use the ASPECT Conversion Utility for
the migration from V2.11 to V4. But I could not find it.
Can any expert here give me some hints on this problem?
Thanks a million, million times !
Ben
zh...@fisci.com
jsch...@mail.coin.missouri.edu
zh...@fisci.com wrote:
> A post in the knowledge base suggests to use the ASPECT Conversion Utility for
> the migration from V2.11 to V4. But I could not find it.
You should find the conversion utility in the Procomm Plus Utilities
subfolder, located in the main Procomm Plus folder off of your Start Menu.
Run the conversion utility, select the script you want to convert, and that's
about it.
zh...@fisci.com
thank you for the answer. I found the utility, but the conversion fails with
the msg: Load Library Failed 126 c:\procomm\0_3.dll
I reinstalled procomm plus 4.7 with FULL-Install option, with the same result.
Ben
Can you shed more light into this problem? thank you so much!
following is our small script file:
;Script for entering trades to the VAX
proc main
CLEAR
LOCATE 0, 0
BOX 0 0 4 50 12
ATSAY 2, 3, 32 "ENTER ROYAL BANK USERNAME"
MATGET 2, 34, 32, 12, S0
CLEAR
LOCATE 0, 0
BOX 0 0 4 50 12
ATSAY 2, 3, 32 "ENTER ROYAL BANK PASSWORD"
MATGET 2, 34, 32, 12, S1
CLEAR
DIAL "1"
WAITFOR "Connect"
PAUSE 2
TRANSMIT "^M"
PAUSE 2
TRANSMIT "^M"
PAUSE 2
TRANSMIT "^M"
WAITFOR "name:"
TRANSMIT S0
TRANSMIT "^M"
WAITFOR "word:"
TRANSMIT S1
TRANSMIT "^M"
WAITFOR "$$"
TRANSMIT "instruct^M"
WAITFOR "..."
SENDFILE XMODEM "dti.trn"
EXECUTE "issue1"
endproc
zh...@fisci.com
I need to write a script for our DOS appl. We used a v2 script as shown below.
now we need to rewrite a script on v4.7 procomm, but still be called by a DOS
application - i.e. interactive portion must appear in a DOS window.
Under v2 for DOS, we use CLEAR, LOCATE, BOX, ATSAY, and MATGET commands to
manipulate the screen, construct dialog box, get user input etc. Since it must
run under DOS-window, uwincreate, iconbutton, uwinpaint etc can not be used.
Can any expert here shed some light on these? I am totally in dark.
thank you sooooooooooooo much for any hints!
Benjamin
---- Posted via Deja News ----
jsch...@mail.coin.missouri.edu
zh...@fisci.com wrote:
> Hi John,
>
> thank you for the answer. I found the utility, but the conversion fails with
> the msg: Load Library Failed 126 c:\procomm\0_3.dll
Interesting, I get the same error message as well. The referenced file does
not exist anywhere on my system. I've got version 3 of Procomm on my Win3.1
partition still. I'll boot to that later, convert the script to version 3
format, then use the version 4.7 convert utility to convert it once more. I
have a feeling the end result will be a large script, so it may be best for
you to rewrite the script.
jsch...@mail.coin.missouri.edu
zh...@fisci.com wrote:
> I need to write a script for our DOS appl. We used a v2 script as shown below.
> now we need to rewrite a script on v4.7 procomm, but still be called by a DOS
> application - i.e. interactive portion must appear in a DOS window.
>
> Under v2 for DOS, we use CLEAR, LOCATE, BOX, ATSAY, and MATGET commands to
> manipulate the screen, construct dialog box, get user input etc. Since it must
> run under DOS-window, uwincreate, iconbutton, uwinpaint etc can not be used.
Unfortunately, there is no way to do this with the Windows versions of
Procomm. All input and output is done via a window. While you can run DOS
applications from Procomm or open a DOS window, there is no command to get
input and output from a DOS window. Is there any reason the script must run
in a DOS window?
zh...@fisci.com
exactly, there is no such a file at all. I followed your recommendation to
rewrite the script. Fortunately, it is not so much difficult to do it. I now
also use sdlginput() to grap user input. It works find now.
thanks for your generous help!
Benjamin
In article <7cpu4q$ofb$1...@nnrp1.dejanews.com>,
jsch...@mail.coin.missouri.edu wrote:
> In article <7cola6$lku$1...@nnrp1.dejanews.com>,
> zh...@fisci.com wrote:
> > Hi John,
> >
> > thank you for the answer. I found the utility, but the conversion fails with
> > the msg: Load Library Failed 126 c:\procomm\0_3.dll
>
> Interesting, I get the same error message as well. The referenced file does
> not exist anywhere on my system. I've got version 3 of Procomm on my Win3.1
> partition still. I'll boot to that later, convert the script to version 3
> format, then use the version 4.7 convert utility to convert it once more. I
> have a feeling the end result will be a large script, so it may be best for
> you to rewrite the script.
>