USING FLIGHT SIMULATOR 4.0b, A&SD WITH WINDOWS 3.0
USING FLIGHT SIMULATOR 4.0b, A&SD WITH WINDOWS 3.0
There seems to be considerable discussion regarding the use of Flight
Simulator 4.0b with the new Aircraft & Scenery Designer from Windows
3.0
Obviously with all the memory considerations involved the ideal
approach seem to be to boot Flight Simulator (including the new A&SD)
using as slimmed down AUTOEXEC.BAT and CONFIG.SYS files as possible to
leave maximum memory available. This is obviously somewhat
incompatible with the AUTOEXEC.BAT and CONFIG.SYS files used by most
people for running WINDOWS.
One answer, at least, and what I am currently using is to reconfigure
the system using batch files which include a utility program that will
do a warm boot into the batch files. This is not exactly like running
Flight Simulator from WINDOWS in that although Flight Simulator is
called from WINDOWS and you are automatically returned to WINDOWS, you
are not returned to the same place in WINDOWS which is actually
restarted after a warm boot on exiting Flight Simulator.
The following is submitted as some help for those WINDOWS users who
might want to avoid the aggravation of booting from a clean system
disk and simply start Flight Simulator from WINDOWS by clicking the
mouse on an icon. On exiting Flight Simulator you are automatically
returned to WINDOWS without a lot of hassle. Although the following
is what I'm using and seems to work for me, there are probably some
small changes that might improve the operation. If anyone has any
thoughts, I'd appreciate their comment.
From Windows 3.0 Flight Simulator (including the new A&SD) are loaded
by calling CFG-FS4.BAT from my root directory. This file is as
follows:
CFG-FS4.BAT:
ECHO OFF
CLS
RENAME AUTOEXEC.BAT AUTOEXEC.WIN
RENAME AUTOEXEC.FS4 AUTOEXEC.BAT
RENAME CONFIG.SYS CONFIG.WIN
RENAME CONFIG.FS4 CONFIG.SYS
BOOT WARM
You'll note that all this file does is rename the existing
AUTOEXEC.BAT and CONFIG.SYS files with a WIN extension, rename
AUTOEXEC.FS4 and CONFIG.FS4 as AUTOEXEC.BAT and CONFIG.SYS and then
cause a warm boot.
The new, slimmed down AUTOEXEC.FS4 and CONFIG.FS4 files are as
follows:
AUTOEXEC.FS4:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND.COM
PATH=C:\;\DOS;\FLTSIM4;\UTIL
ASTCLOCK /R
CD\
FLTSIM4
CONFIG.FS4:
STACKS=0,0
I have left my utility subdirectory in the path since I can then use
some of my utility files for editing purposes.
I have left the clock from my AST SixPak Plus in so that any files
created are correctly dated and timed. This enables me to check which
version of a file or similar file may be the latest version.
FLTSIM4 is actually FLTSIM4.BAT which is located in the root
directory. It loads Flight Simulator and on exiting calls
CFG-WIN.BAT located in the root directory which is as follows:
FLTSIM4.BAT:
CD\FLTSIM4
FS4
CD\
ECHO OFF
CLS
CFG-WIN
CFG-WIN.BAT saves the AUTOEXEC.BAT and CONFIG.SYS files used for
Flight Simulator with FS4 extensions brings back the AUTOEXEC.BAT and
CONFIG.SYS files used for WINDOWS 3.0 and then causes a warm boot,
which brings up WINDOWS again.
CFG-WIN.BAT:
ECHO OFF
CLS
RENAME AUTOEXEC.BAT AUTOEXEC.FS4
RENAME AUTOEXEC.WIN AUTOEXEC.BAT
RENAME CONFIG.SYS CONFIG.FS4
RENAME CONFIG.WIN CONFIG.SYS
BOOT WARM
The key to the whole thing is BOOT.COM a simple utility which allows
me to place a warm or cold boot command in a batch file. There are
many such utility programs available one of which is BOOTET.ARC
(3200 bytes) available in Lib.1 of the IBMSYS Forum on CompuServe.
I have included a file called FLTSIM.ICO which is the Windows icon
that I use for Flight Simulator in Windows 3 for those who would like
an appropriate icon.
Tom Carnegie
CompuServe 70267,2126
There seems to be considerable discussion regarding the use of Flight
Simulator 4.0b with the new Aircraft & Scenery Designer from Windows
3.0
Obviously with all the memory considerations involved the ideal
approach seem to be to boot Flight Simulator (including the new A&SD)
using as slimmed down AUTOEXEC.BAT and CONFIG.SYS files as possible to
leave maximum memory available. This is obviously somewhat
incompatible with the AUTOEXEC.BAT and CONFIG.SYS files used by most
people for running WINDOWS.
One answer, at least, and what I am currently using is to reconfigure
the system using batch files which include a utility program that will
do a warm boot into the batch files. This is not exactly like running
Flight Simulator from WINDOWS in that although Flight Simulator is
called from WINDOWS and you are automatically returned to WINDOWS, you
are not returned to the same place in WINDOWS which is actually
restarted after a warm boot on exiting Flight Simulator.
The following is submitted as some help for those WINDOWS users who
might want to avoid the aggravation of booting from a clean system
disk and simply start Flight Simulator from WINDOWS by clicking the
mouse on an icon. On exiting Flight Simulator you are automatically
returned to WINDOWS without a lot of hassle. Although the following
is what I'm using and seems to work for me, there are probably some
small changes that might improve the operation. If anyone has any
thoughts, I'd appreciate their comment.
From Windows 3.0 Flight Simulator (including the new A&SD) are loaded
by calling CFG-FS4.BAT from my root directory. This file is as
follows:
CFG-FS4.BAT:
ECHO OFF
CLS
RENAME AUTOEXEC.BAT AUTOEXEC.WIN
RENAME AUTOEXEC.FS4 AUTOEXEC.BAT
RENAME CONFIG.SYS CONFIG.WIN
RENAME CONFIG.FS4 CONFIG.SYS
BOOT WARM
You'll note that all this file does is rename the existing
AUTOEXEC.BAT and CONFIG.SYS files with a WIN extension, rename
AUTOEXEC.FS4 and CONFIG.FS4 as AUTOEXEC.BAT and CONFIG.SYS and then
cause a warm boot.
The new, slimmed down AUTOEXEC.FS4 and CONFIG.FS4 files are as
follows:
AUTOEXEC.FS4:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND.COM
PATH=C:\;\DOS;\FLTSIM4;\UTIL
ASTCLOCK /R
CD\
FLTSIM4
CONFIG.FS4:
STACKS=0,0
I have left my utility subdirectory in the path since I can then use
some of my utility files for editing purposes.
I have left the clock from my AST SixPak Plus in so that any files
created are correctly dated and timed. This enables me to check which
version of a file or similar file may be the latest version.
FLTSIM4 is actually FLTSIM4.BAT which is located in the root
directory. It loads Flight Simulator and on exiting calls
CFG-WIN.BAT located in the root directory which is as follows:
FLTSIM4.BAT:
CD\FLTSIM4
FS4
CD\
ECHO OFF
CLS
CFG-WIN
CFG-WIN.BAT saves the AUTOEXEC.BAT and CONFIG.SYS files used for
Flight Simulator with FS4 extensions brings back the AUTOEXEC.BAT and
CONFIG.SYS files used for WINDOWS 3.0 and then causes a warm boot,
which brings up WINDOWS again.
CFG-WIN.BAT:
ECHO OFF
CLS
RENAME AUTOEXEC.BAT AUTOEXEC.FS4
RENAME AUTOEXEC.WIN AUTOEXEC.BAT
RENAME CONFIG.SYS CONFIG.FS4
RENAME CONFIG.WIN CONFIG.SYS
BOOT WARM
The key to the whole thing is BOOT.COM a simple utility which allows
me to place a warm or cold boot command in a batch file. There are
many such utility programs available one of which is BOOTET.ARC
(3200 bytes) available in Lib.1 of the IBMSYS Forum on CompuServe.
I have included a file called FLTSIM.ICO which is the Windows icon
that I use for Flight Simulator in Windows 3 for those who would like
an appropriate icon.
Tom Carnegie
CompuServe 70267,2126
Comments
Post a Comment