RE: RunCommand and Win 95

Question

Actually, NT just renamed the mapping layer for WOW
type cmd /? to see the same (more) options on the NT interpreter
and command.com /? for the MSDos command interpreter
-----Original Message-----
From: Tim Sawyer [SMTP:[email protected]]
Sent: Wednesday, April 14, 1999 11:32 AM
To: '[email protected]'
Subject: Re: RunCommand and Win 95
On Wed, 14 Apr 1999, Daniel Nguyen wrote:
Hi,
You can not use Copy command on windows : it is a Dos command. So you
should make a
bat file and launch it with the runcommand for instance.Or use command.com with appropriate parameters. (sorry, I don't remember
exactly, and I have no DOS based machine here ... :)) )To run it using command.com, I think you need to run
command /ccopy <source> <dest>
(the /c specifies the command that you want to run)
but this will not work on NT, cos NT doesn't have a command.com. This
doesn't sound like the right way to go about doing the copy though...
Tim Sawyer
PanCredit
Leeds, UK.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Christina,
Since you are in a mixed environment, you should avoid using the operating
system commands for portability reasons. You can use the -fns option on
the ftexec command which allows you to override the environment/registry
variable FORTE_NS_ADDRESS.
Example: ftexec.exe -fns computername:portnumber
Hope this helps in your situation.
Doug Laures
Senior Technical Consultant
Claremont Technology Group
Columbus OH
To: forte-users @ Sagesoln.com
cc: (bcc: Douglas Laures/Central Region/Claremont)
From: BuPEDV @ compuserve.com @ INTERNET@INTERLIANT
Date: 10/15/97 07:11:20 AM AST
Subject: Re: RunCommand and ftexec
Hello Christina,
try the task.part.OperatingSystem.SetEnv() - method befor you make the
start with RunCommand. in SetEnv you set FORTE_NS_ADRESS to server2:6000.
Because the RunCommand executes a new shell, the calling Apllication A
works with it's old adress.
Hope it helps.
Joseph Mirwald
EMAIL: [email protected]
Christina Tomacelli wrote:
Dear forte-users,
I have the following problem.
I have an application A that uses a certain environment (say Aenv, with
FORTE_NS_ADDRESS=server1:5000). This application executes at a certain time
a RunCommand and calls a "ftexec" which runs another Forte' application
(B). Application B belongs to a different environment (say Benv, with
FORTE_NS_ADDRESS=server2:6000).
When I call application B from application A, application B reads the same
FORTE_NS_ADDRESS which was set before start executing application A (that
is, application B uses FORTE_NS_ADDRESS=server1:5000, which is incorrect).
I can have mixed platform UNIX and Windows 95, so FORTE_NS_ADDRESS can be
an environment variable or a line in forte.ini.
Can you think of a workaround to this problem ?
TIA
Cristina Tomacelli
(See attached file: firma.txt)