Re: DOS Environment not working
- From: "Pegasus \(MVP\)" <I.can@xxxxxxx>
- Date: Tue, 31 Jul 2007 21:17:46 +0200
Try this:
1. Click Start / Run / cmd {OK}
2. Execute your batch file
3. Type this command:
set bco{Enter}
What do you see?
"Gussie" <Gussie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DD9501AE-BACF-4A61-BFCE-E728802A8DAC@xxxxxxxxxxxxxxxx
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.
"Pegasus (MVP)" wrote:
"Gussie" <Gussie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1E10AC2B-D646-4731-A50F-5D8FED33E070@xxxxxxxxxxxxxxxx
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
sdl-gus@xxxxxxxxxx
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!
.
- Follow-Ups:
- Re: DOS Environment not working
- From: Gussie
- Re: DOS Environment not working
- References:
- Re: DOS Environment not working
- From: Pegasus \(MVP\)
- Re: DOS Environment not working
- Prev by Date: Re: power managements clashing
- Next by Date: Re: Deleted Partition on Accident, Can I Get My Files?
- Previous by thread: Re: DOS Environment not working
- Next by thread: Re: DOS Environment not working
- Index(es):
Relevant Pages
|
|