From: Gerald Miller
Subject: parsing
Date: 1998/04/18
Message-ID: #1/1
References:
Distribution: fido
Organization: 4DOS for one and 4DOS for all!
Newsgroups: fido.4dos
Hello Jorj,
\|/ Subject: parsing
/|\ On Thursday April 16 1998 at 23:41,
you wrote to Gerald Miller saying:
GM>> I have a line in my AUTOEXEC.BAT that points to my ramdrive:
GM>> FOR %%a in (TMP TEMP) do set %%a=G:\QWOK
JS> Qwok? And might I ask why you do it this way? I can see it if
JS> there are lots of items to process. For instance, I do this:
JS> for /a:a %i in (cmie dosapp iexplore msacm opera...
JS> progman superfxp system) attrib/eq -a %i.ini
JS> when I exit Windows, to clear those annoying archive bits on
JS> files that change regularly but generally meaninglessly.
JS> But with just two items, it would be shorter to do
JS> set tmp=g:\qwok^set temp=g:\qwok
QWOK? What's in a name? I set it in my AUTOEXEC and provide a distinctive
name for the many programs that could possibly require any kind of "temp"
environment setting (DOS and/or 4DOS)... AUTOEXEC doesn't like the command
separator character, so that's out of the question. I am not about to start
investigating every program that may require a "temp" environment and modify
each batch file; it would be an arduous task and I've not had any failures with
programs NOT recognizing QWOK...
GM>> I will modify it to include TEMP4DOS... I was under the impression
GM>> that this could be set via 4DOS.INI. I'll remove it from the INI
GM>> file.
JS> It didn't produce an error message in 4DOS.INI? Odd. Temp4Dos
JS> overrides Temp, but Temp gets used if it doesn't exist, so you
JS> really shouldn't have had description-file changing from pipefile
JS> deletion before. Who knows why it happened.
Who knows, indeed! Every computer is unique. I ran a '286 system with 4DOS on
it for years... When I bought my '486 DX4 100, I transferred everything from
the '286 to the '486 and spent about eight months tracking down odd little
quirks and making repairs... ;^))
G'Day ... Gerald
|