rcw@qetzal.UUCP (sysop) (10/13/87)
We are trying to use INFORMIX on a Wyse 286 PC. When we set eight or nine variables in the AUTOEXEC.BAT file, and boot the machine, it claims that it is out of environment space. After the machine comes up with the "C>" prompt, it will then accept the command "set INFORMIXDIR=C:\INFORMIX", but we don't want to inflict this on the user. Anyone have any thoughts? It is version 3.21 of what appears to be Wyse's implementation of DOS. -- Robert C. White, Jr *---- ----* MENTOR SOFTWARE, INC. 1-303-252-9090 ihnp4!upba!qetzal!rcw | |_| | 11534 Steele St. | _ o _ | Thornton, CO 80233 | | | | | | Custom Software Specialists.
guardian@laidbak.UUCP (Harry Skelton) (10/14/87)
In article <194@qetzal.UUCP> rcw@qetzal.UUCP (sysop) writes: >We are trying to use INFORMIX on a Wyse 286 PC. When we set >eight or nine variables in the AUTOEXEC.BAT file, and boot >the machine, it claims that it is out of environment >space. After the machine comes up with the "C>" prompt, it >will then accept the command "set INFORMIXDIR=C:\INFORMIX", >but we don't want to inflict this on the user. > >Anyone have any thoughts? It is version 3.21 of what appears >to be Wyse's implementation of DOS. If your version of DOS is anywere near 3.2 or has 3.3 features then there are two methods of correcting the environment problem. Under dos 3.1 (and some versions of 3.2) there is a 'E' switch to command.com that will help you expand your environment. I'm sure there are some programs that can do this for you but the following way is better and safer: Dos 3.1 and some 3.2: in the config.sys file - SHELL=C:\COMMAND.COM /E:[number-of-pages] /P this will load command.com (which by the way, controls the environment) and will allocate 'number-of-pages' of environment space. i.e. /E:20 (20*16bytes) Be carefull as some use 16byte pages and others use 128byte pages (wierd but true). Don't use a number beyond 50 as up to this point you risk overflow and you'll get stuck with 128 bytes of environment (as normal) or get some brain damaged error. Dos 3.3 and some 3.2: (3.3 is the version you should run with) The command in the config.sys file is the same BUT the 'E' option refers to the actual number of bytes to allocate (easy!). SHELL=C:\COMMAND.COM /E:2048 /P (what I have - 512 or 1024 will do the trick) Usually I would pop the environment in at 2k to allow for lots of room. Some programs will die with a large environment space but those tend to be programs compiled under 3.1 or something (2.1 etc....) . I would not worry about it since programs like Informix and Unify require tons of environment space in order to do anything. Specially if you are using a development environment. Give it a shot, It can't hurt. .---------. Harry Skelton : .-. : --- other mail drops --- guardian@laidbak.UUCP : `-'o : ihnp4!laidbak!ugh!bear ihnp4!laidbak!guardian : O : ihnp4!laidbak!laipc!bear `---------' As in the words of Socrates "I drank what*......."
garyq@hpfcdc.HP.COM (Gary Quakenbush) (10/14/87)
Re: Environment space in COMMAND.COM
In your CONFIG.SYS file, insert a line like:
shell=command.com c: /e:nn /p
The "c:" part tells the resident part of COMMAND.COM where to find the
transient part.
The "/e:nn" part controls how big an environment space is desired. The "nn"
is a number from 10 to 62 (defaulting to 10) indicating how many 16-byte
chunks of memory are to be reserved for the environment space.
The "/p" tells that this copy of COMMAND.COM is to be permanent; also
causes AUTOEXEC.BAT to be executed.
This works for DOS 2.x and DOS 3.1
For DOS 3.2 (and probably 3.3), the value "nn" must be in bytes (max 32000)
---------------------
The above response was originally posted by Steve Harrold in early July
of this year. I am reposting from my archives.
---------------------
Gary Quakenbush
Fort Collins, Colorado
---------------------mrk@gvgspd.UUCP (Michael R. Kesti) (10/17/87)
In article <5580004@hpfcdc.HP.COM> garyq@hpfcdc.HP.COM (Gary Quakenbush) writes: >In your CONFIG.SYS file, insert a line like: > > shell=command.com c: /e:nn /p > ... >This works for DOS 2.x and DOS 3.1 ^^^^^^^ It seems we've been through this, but this is *NOT* valid for anything before version 3.1!!!! > ... >--------------------- >The above response was originally posted by Steve Harrold in early July >of this year. I am reposting from my archives. >--------------------- Well, that explains why we've been through this before! -- =================================================================== Michael Kesti Grass Valley Group, Inc. P.O. Box 1114 Grass Valley, CA 95945 UUCP: ...!tektronix!gvgpsa!gvgspd!mrk