DOS Environment not working


G

Guest

Hello, I have legacy system written in Clipper 5.2e/Blinker 7.0. I need to do
a bunch of SET' when I open up the command shell. To do that I run a batch
file once command.com is triggered, but variables are not been set as they
supposed to.

I can set these variables one-by-one and it works fine, but cannot run
batchfile.
Any ideas? is it possible to set variables using a SCRIPT?

Gus
(e-mail address removed)
 
Ad

Advertisements

P

Pegasus \(MVP\)

Gussie said:
Hello, I have legacy system written in Clipper 5.2e/Blinker 7.0. I need to
do
a bunch of SET' when I open up the command shell. To do that I run a batch
file once command.com is triggered, but variables are not been set as they
supposed to.

I can set these variables one-by-one and it works fine, but cannot run
batchfile.
Any ideas? is it possible to set variables using a SCRIPT?

Gus
(e-mail address removed)
Presumably you're talking about the Command Prompt, not DOS.
DOS is an operating system - it does not exist in WinXP.

The "set" command works exactly as designed but you need to
be aware that your changes are only effective within the process
in which they are applied. Child processes inherit their environmental
variables from their parents but the parents do not inherit anything
from their children. I suspect that you're trying to set your
variables by shelling out from within Clipper. You cannot do this -
you must set your variables when you start your Command Prompt.
This is usually done by placing a suitable batch file into your
Startup menu, e.g. like so:
@echo off
set path=%path%;c:\Clipper
clipper.exe

Note also that command.com is a legacy command processor.
It was superceded seven years ago by cmd.exe. Time to move on!
 
G

Guest

Your assumption is correct; I am using the Command Prompt.
The batch file is very simple:
@echo off

SET CLDON=0
SET INTLMAIL=1HPLSRJET
SET AUTO_COMP_ROOT=H:\DATA\SHARED\AUTO
SET BCO_APP_ROOT=H:\BIN\BCO

I run the batchfile at the command prompt, but when I check the variables:
SET, none of them are there!! but if I SET each one at the command prompt
then its fine.
 
P

Pegasus \(MVP\)

Try this:
1. Click Start / Run / cmd {OK}
2. Execute your batch file
3. Type this command:
set bco{Enter}

What do you see?
 
G

Guest

It just shows the variables set by windows on startup, the ones you can edit
when you go to MyComputer properties. The batch file does not fail because I
installed a errorlevel statement to echo a message.... mmmmm

Frustrating, and I agree with you: 'time to move on' but as a contractor I
need to do what my client needs, which is get this application going

Thank you for your time!
 
P

Pegasus \(MVP\)

My observation about "time to move on" referred to the
need to stop using a command processor that became
obsolete seven years ago. This has nothing to do with
the need to do what the client needs.

Let's nail this one down. Modify your batch file like so:
@echo off
SET CLDON=0
SET INTLMAIL=1HPLSRJET
SET AUTO_COMP_ROOT=H:\DATA\SHARED\AUTO
SET BCO_APP_ROOT=H:\BIN\BCO
echo INTLMAIL=xxx%INTLMAIL%xxx

Now invoke cmd.exe (not command.com!), then run this
batch file directly from the Command Prompt (without
shelling out to another command prompt!) and report what
you see.
 
Ad

Advertisements

G

Guest

It works that way.
Thank you very much!

I am eventually migrating their clipper applications into xHarbour using
Advantage Database Server. Client wants this part to be done first, so I have
ADS already installed working with Clipper.
 
P

Pegasus \(MVP\)

What did you do differently this time?


Gussie said:
It works that way.
Thank you very much!

I am eventually migrating their clipper applications into xHarbour using
Advantage Database Server. Client wants this part to be done first, so I
have
ADS already installed working with Clipper.
 
Ad

Advertisements

P

Plato

=?Utf-8?B?R3Vzc2ll?= said:
Hello, I have legacy system written in Clipper 5.2e/Blinker 7.0. I need to do
a bunch of SET' when I open up the command shell. To do that I run a batch
file once command.com is triggered, but variables are not been set as they
supposed to.
Honestly, if you want to continue to use dos apps, then its best to use
and OS on PC that has dos on it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top