VETUSWARE.COM

On Sunday April 13, 2014 wizman said:

PART3:
So now I have a file named "fox.bat" that looks like this:
===begin===
SET Path=C:\foxplus
SET NUMBER_OF_PROCESSORS=
SET OS=
SET PATHEXT=
SET PROCESSOR_ARCHITECTURE=
SET PROCESSOR_IDENTIFIER=
SET PROCESSOR_LEVEL=
SET PROCESSOR_REVISION=
SET ProgramData=
SET ProgramFiles=
SET PROMPT=
SET SESSIONNAME=
SET SystemDrive=C:
SET SystemRoot=C:\winxp
SET TEMP=
SET TMP=
SET USERDOMAIN=
SET USERNAME=
SET USERPROFILE=
SET windir=
SET XCHAT_WARNING_IGNORE=
SET ALLUSERSPROFILE=
SET APPDATA=
SET CLASSPATH=
SET CLIENTNAME=
SET CommonProgramFiles=
SET COMPUTERNAME=
SET ComSpec=
SET FP_NO_HOST_CHECK=
SET HOMEDRIVE=C:
SET HOMEPATH=
SET LOGONSERVER=
SET MOZ_PLUGIN_PATH=
foxplus.exe
===end===
You are so very welcome,
AppleSeed '96
TTFNMF

On Sunday April 13, 2014 wizman said:

PART2:
EXAMPLE:
CommonProgramFiles=C:\Program Files\Common Files
gets changed to
SET CommonProgramFiles=
So, only the below needed to have correct values:
SET Path=C:\foxplus
SET SystemDrive=C:
SET SystemRoot=C:\winxp
SET HOMEDRIVE=C:
..and then it starts just fine. No need to set special memory values by right-clicking
the FOXPLUS.EXE, no need for any other tricks or hacks.
NOTE1: Every computer is likely to have a different set of environment variables active
under XP - it really depends on the software and drivers a particular system has.
NOTE2: Doing this only works for the current Command Promt window. As soon as you
close it, the settings are lost/reset.
NOTE3: This does NOT change anything permanently in XP, just the current Command
Prompt session, so no need to worry that you'll screw your system up.

On Sunday April 13, 2014 wizman said:

Gonna attempt to post the fix for "error 2009: Not enough space for environment" The full text is in this archive.
PART1:
Run under XP
error 2009: Not enough space for environment
After much research using my assistant "Google", OK - got it to work!
It really IS environment variables being too long.
It really is NOT as Microsoft says, just right-clicking FOXPLUS.EXE in Windows
and setting memory requirements, or by just shortening the PATH= statement.
In DOS, the environment variables string can be a max of 128 bytes. Period. That's it.
I opened a Command Prompt, typed "set" AND piped it to a text file like so...
"set > env.txt"
... so I could review the entries. It was 1326 bytes! (The right pointing arrow
symbol is the "PIPE" command.)
In my installation of XP SP3, there is a sh*tload of entries. I changed them all to
[blank], still didn't work, but now, the error was that it couldn't find
C:\FOXPLUS\FOXPLUS.EXE. Houston, we have Progress!