Dosstart, config.sys and autoexec.bat ???
Chris Young
>What exactly does dosstart.bat do? I have read where smartdrive and
>mouse are no longer needed under win95. these 2 commands have been
>moved to dosstart.bat. when does dosstart.bat execute? if the 2
>commands mentioned are not used by win95, why are they in the
>dosstart.bat file? also my mouse settings no longer contain the
>snap-to function i liked so much under 3.11. is there any way to get
>the old mouse settings back where i have snap-to again?
>
Hello,
The dosstart.bat is used when a shutdown to MsDos mode us done.
So if you want to set up special stuff for running in just Dos mode then
that is the place to do it.
I don't know about the snap-to function.
Chris
Ramesh Viswanathan
: What exactly does dosstart.bat do? I have read where smartdrive and
: mouse are no longer needed under win95. these 2 commands have been
: moved to dosstart.bat. when does dosstart.bat execute? if the 2
: commands mentioned are not used by win95, why are they in the
: dosstart.bat file?
The DOSSTART.BAT file is executed whenever Windows boots to DOS. This
way, you have all the necessary settings that are required under DOS.
Try including some echo statements in the file and do a shutdown to
DOS and you would see that these statements are executed. You can type
exit to re-load windows.
: Also my mouse settings no longer contain the
: snap-to function i liked so much under 3.11. is there any way to get
: the old mouse settings back where i have snap-to again?
The reason for this is due to the absense of the Mousemgr.dll file
in the search path.
To enable Mouse Manager, use either of the following methods:
- Add the folder containing the Mousemgr.dll file to the search path.
- Move the Mousemgr.dll file to a folder that is in the search path.
After you use either of these methods, restart your computer.
Ramesh
--
Ramesh Viswanathan *************** ClubWin Member ***************
Siemens Corporate Research, 755 College Road East, Princeton NJ 08540-6668
+++ The opinions expressed in this message are my own personal views ++
+++ and do not reflect the official views of Siemens Corporate Research ++
Phil Leonard
[comp.os.ms-windows.win95.misc] ankh9467...@campus.mci.net (Michael
Holloway) writes:
>What exactly does dosstart.bat do?
Nothing. I have completely erased mine (Since seeing everyone here rant
and rave about it) and when I exit to DOS, everything loads fine with out
it. I have no DOSSTART.BAT and I get 611K free memory in DOS 7.0.
Either Edit AUTOEXEC.DOS and AUTOEXEC.DOS or
Edit the EXIT TO DOS PIF in explorer.
>is there any way to get the old mouse settings back where i
>have snap-to again?
Call and get the update free from Microsoft.
phil leonard | pleo...@cybercom.net | http://cybercom.net/~pleonard
----------------------------------------------------------------------
32bit Files * 350 Web Tool URLs * Daily URLs * Powered by Win95 TCP/IP
Neil Polo
>In article <43pter$e...@ns.campus.mci.net> from
>[comp.os.ms-windows.win95.misc] ankh9467...@campus.mci.net (Michael
>Holloway) writes:
>>What exactly does dosstart.bat do?
>Nothing. I have completely erased mine (Since seeing everyone here rant
>and rave about it) and when I exit to DOS, everything loads fine with out
>it. I have no DOSSTART.BAT and I get 611K free memory in DOS 7.0.
>Either Edit AUTOEXEC.DOS and AUTOEXEC.DOS or
>Edit the EXIT TO DOS PIF in explorer.
Although _you_ might not need it, isn't it a bit misleading to say it
does "nothing"? Mouse and CD-ROM support must at times be provided to
DOS programs via the "standard" mouse driver, and MSCDEX. Unless other
arrangements are made, DOSSTART.BAT is used as a supplement to
AUTOEXEC.BAT when a DOS program is run in MS-DOS mode.
If you need those drivers, and place them in the AUTOEXEC.BAT instead,
everything will work fine - but then those drivers take up needless
space - and worse - while running in Win95 GUI mode.
Regards,
Neil
"Its not enough to do well . . .
. . . others must do poorly!."
Phil Leonard
[comp.os.ms-windows.win95.misc] np...@omni.voicenet.com (Neil Polo)
writes:
>If you need those drivers, and place them in the AUTOEXEC.BAT instead,
>everything will work fine - but then those drivers take up needless
>space - and worse - while running in Win95 GUI mode.
No, You just don't understand. You make your changes to Autoexec.DOS and
Config.DOS. It's always been that way since the first beta. I don't know
why all of a sudden everyone is looking at DOSSTART.BAT. It's not even in
the resource kit.
Autoexec.bat and config.sys do not have the same set of drivers as
autoexec.dos and config.dos. When you EXIT to DOS, these files are copied
over and temporarily replace autoexec.bat and config.sys.
Bottom line, I am typing this in Win95 No mouse, no CD, No sound:
SYSTEM 38,416 (38K) 9,664 (9K) 28,752 (28K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 4,320 (4K) 4,320 (4K) 0 (0K)
WIN 3,664 (4K) 3,664 (4K) 0 (0K)
vmm32 118,096 (115K) 1,696 (2K) 116,400 (114K)
COMMAND 9,168 (9K) 9,168 (9K) 0 (0K)
M1904 12,944 (13K) 0 (0K) 12,944 (13K)
IFSHLP 2,864 (3K) 0 (0K) 2,864 (3K)
SETVER 832 (1K) 0 (0K) 832 (1K)
DOSKEY 4,688 (5K) 0 (0K) 4,688 (5K)
Free 625,344 (611K) 625,344 (611K) 0 (0K)
When I exit to DOS 7.0, I get CD, Smartdrive, Sound, etc.
MSDOS 16653 (16K) 16653 (16K) 0 (0K)
HIMEM 1168 (1K) 1168 (1K) 0 (0K)
EMM386 3120 (3K) 3120 (3K) 0 (0K)
MOUSE 17088 (17K) 17088 (17K) 0 (0K)
ANSI 4208 (4K) 4208 (4K) 0 (0K)
COMMAND 3680 (4K) 3680 (4K) 0 (0K)
VSHIELD 3376 (3K) 3376 (3K) 0 (0K)
SETVER 736 (1K) 0 (0K) 736 (1K)
SGCDM 37216 (36K) 0 (0K) 37216 (36K)
SMARTDRV 28320 (28K) 0 (0K) 28320 (28K)
MSCDEX 16304 (16K) 0 (0K) 16304 (16K)
Free 616592 (602K) 605856 (592K) 10736 (10K)
Understand now?
Neil Polo
>In article <447518$5...@news.voicenet.com> from
>[comp.os.ms-windows.win95.misc] np...@omni.voicenet.com (Neil Polo)
>writes:
>>If you need those drivers, and place them in the AUTOEXEC.BAT instead,
>>everything will work fine - but then those drivers take up needless
>>space - and worse - while running in Win95 GUI mode.
>No, You just don't understand. You make your changes to Autoexec.DOS and
>Config.DOS. It's always been that way since the first beta. I don't know
>why all of a sudden everyone is looking at DOSSTART.BAT. It's not even in
>the resource kit.
I may not understand, but I can read the screen pretty well. On my
system, a switch to DOS invokes DOSSTART.BAT. Period. End of story.
If I restart under previous DOS, then autoexec.dos and config.dos are
used. So, as I said earlier, stop making universal statements when you
don't know the universe, OK?
>Autoexec.bat and config.sys do not have the same set of drivers as
>autoexec.dos and config.dos. When you EXIT to DOS, these files are copied
>over and temporarily replace autoexec.bat and config.sys.
As i said, on my system these are used only for DOSS 6.22. These files
look exactly like my autoexec and config files prior to installing
Win95.
>Understand now?
Understand Now?
Phil Leonard
[comp.os.ms-windows.win95.misc] np...@omni.voicenet.com (Neil Polo)
writes:
>>>If you need those drivers, and place them in the AUTOEXEC.BAT instead,
>>>everything will work fine - but then those drivers take up needless
>>>space - and worse - while running in Win95 GUI mode.
pleo...@cybercom.net (Phil Leonard) wrote:
>>No, You just don't understand. You make your changes to Autoexec.DOS and
>>Config.DOS. It's always been that way since the first beta. I don't know
>>why all of a sudden everyone is looking at DOSSTART.BAT. It's not even in
>>the resource kit.
In article <44n9je$c...@news.voicenet.com> from
[comp.os.ms-windows.win95.misc] np...@omni.voicenet.com (Neil Polo)
writes:
>I may not understand, but I can read the screen pretty well. On my
>system, a switch to DOS invokes DOSSTART.BAT. Period. End of story.
So, let's see it! What's your DOSSTART.BAT? Where is it documented? We
need some facts here.
Mine is blank. Nothing in it and it boots up in DOS 7.0 without Windows 95
with 595K free Conventional. It uses Autoexec.dos and config.dos period.
It renames autoexec.bat and config.sys as autoexec.wos and config.wos.
>stop making universal statements when you don't know the universe, OK?
Because you do not understand what's happening here? I admit it is
somewhat confusing. But why not try something for yourself.
Exit to DOS from Windows 95. Edit Config.sys and autoexec.bat with some
REM statement. Or load a driver. Type EXIT to return to Windows. Now
reboot your system, and exit from Windows 95 to DOS again. The driver will
load. And when you EXIT back to Windows 95, you'll find it in Autoexec.DOS
and Config.DOS.
Here is the bottom line. When Win 95 loads with Config.sys and
Autoexec.bat, no CD,sound, or mouse loads. When Windows 95 exits to DOS,
it uses Autoexec.DOS and Config.DOS. This then loads your mouse, CD, Sound
etc. So in answer to your ORIGINAL comment, "but then those drivers take
up needless space - and worse - while running in Win95 GUI mode.", not
only is this mis-leading, it is downright FALSE!
phil leonard | pleo...@cybercom.net | http://cybercom.net/~pleonard
----------------------------------------------------------------------
W95 TCP/IP Powered * IE 2.0 optimized * Daily URL * 350 Publish tools
trueba
>==========Phil Leonard, 10/5/95==========
>
>Here is the bottom line. When Win 95 loads with Config.sys and
>Autoexec.bat, no CD,sound, or mouse loads. When Windows 95 exits to DOS,
>it uses Autoexec.DOS and Config.DOS. This then loads your mouse,
Please explain why this doesn't now work, and why it NEVER
worked on my system past beta build 445? Here is my scenario.
When I first installed beta 445 on my system in May I booted DOS
6.22/WFWG 3.11 to the DOS prompt. I then renamed my CONFIG.SYS
and AUTOEXEC.BAT to CONFIG.DOS and AUTOEXEC.DOS, respectively. I
then brought up Windows and ran the Win95 setup from there.
After setup finished, I modified my new AUTOEXEC.BAT to setup my
new path (added directories to \WINDOWS and \WINDOWS\COMMAND in
the default Win95 path) and set up some other environment variables.
Now when I restart in MS-DOS mode, the only thing I see in
memory or in my environment is what I now have already loaded
from my AUTOEXEC.BAT. Does this CONFIG.DOS/AUTOEXEC.DOS useage
during "restart in MS-DOS mode" only work if you let Windows 95
create these files during installation time?
Bob Wasson
From what I have found out playing with win95 thru some of the
beta's, The dosstart file is only used when you select 'go to a
dos session at the start/shutdown/restart the computer in msdos
mode'. When you do this, the computer does not reboot, but runs
the dosstart.bat file. This is useful if you want to go directly
to dos without a reboot, and you need a mouse driver or cd-rom
driver etc.
The autoexec.dos files are used when you select at boot up time
to go to the old dos os like 6.2 etc.
On normal boot up, whatever is in config.sys and autoexec.bat will
be executed during boot up to windows are the command prompt.
Bob
Dave Cell
I don't know if anyone cares anymore, but here's what the different
files do:
If you boot straight into Win95 (GUI or command line), it uses
CONFIG.SYS and AUTOEXEC.BAT. If you use the boot-up menu to "start
your previous version of DOS", it renames CONFIG.DOS and AUTOEXEC.DOS
to CONFIG.SYS and AUTOEXEC.BAT and boots the previous version of DOS
with those.
HOWEVER....if you do a Shutdown with "Restart the computer in MS-DOS
mode, it shuts down the GUI and runs DOSSTART.BAT (located in your
Win95 directory). It doesn't "restart" the computer at all.
DOSSTART.BAT is created during the installation IF the install
routines think they have detected drivers which need to be present in
DOS mode but not in GUI mode. Hence, not all machines have a
DOSSTART.BAT.
Note that even when you do a "Restart the computer in MS-DOS mode",
CONFIG.SYS and AUTOEXEC.BAT have already run, and anything they load
is still present.
So, in general, you should be doing your start-up mods for Win95 in
CONFIG.SYS and AUTOEXEC.BAT, and your start up mods for DOS 6.22 (or
whatever) in CONFIG.DOS and AUTOEXEC.DOS. BUT, if you need something
special present when you drop out of the GUI to "MS-DOS" mode, load it
in DOSSTART.BAT. On most machines, this file is not needed and does
nothing useful.
Dave Cell
Access:Earth - Consulting and contract programming with
MS-Access, Visual Basic, and MS-Office. Specializing in
using OLE Automation to integrate the MS-Office suite.
Located in St. Petersburg, Florida, USA.
Contact: dc...@cftnet.com
Hans van Raaij
Newsgroups: comp.os.ms-windows.win95.misc
Subject: Re: Dosstart, config.sys and autoexec.bat ???
Date: Sun, 15 Oct 1995 16:41:06 -0400
Organization: EMI Communications
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-ID: <308171...@nb.net>
References: <43pter$e...@ns.campus.mci.net> <4452ui$o...@orion.cybercom.net> <447518$5...@news.voicenet.com> <44d6tk$g...@orion.cybercom=
net> <44n9je$c...@news.voicenet.com> <451ti3$h...@orion.cybercom.net> <45hd5a$3...@news.voicenet.com> <45q69p$b...@jaring.my>
Hans van Raaij
Reply-To: psm...@wengen.pc.my
Newsgroups: comp.os.ms-windows.win95.misc
Subject: Re: Dosstart, config.sys and autoexec.bat ???
Organization: Private user
Message-ID: <45q69p$b...@jaring.my>
References: <43pter$e...@ns.campus.mci.net> <4452ui$o...@orion.cybercom.net> <447518$5...@news.voicenet.com> <44d6tk$g...@orion.cybercom=
net> <44n9je$c...@news.voicenet.com> <451ti3$h...@orion.cybercom.net> <45hd5a$3...@news.voicenet.com>
I am getting confused.
I copied config.sys --> config.dos, and autoexec.bat -->
autoexec.dos.
I editted the .dos files to make them distinctive. eg set the prompt
to [FRED] !
When boot to DOS I still get my original setup? the .dos programs
don't seem to do anythink?
I do have a dosstart.bat in c:\windows. I didn't create it. It
contains loadhigh statements for mouse and CD-Rom.
Any definitive answer - to save me the repetitive slow '95 boot
sequence during tests!
Hans van Raaij
Hans van Raaij
Newsgroups: comp.os.ms-windows.win95.misc
Subject: Re: Dosstart, config.sys and autoexec.bat ???
Organization: Voicenet - Internet Access - (215)674-9290
Message-ID: <45hd5a$3...@news.voicenet.com>
References: <43pter$e...@ns.campus.mci.net> <4452ui$o...@orion.cybercom.net> <447518$5...@news.voicenet.com> <44d6tk$g...@orion.cybercom=
net> <44n9je$c...@news.voicenet.com> <451ti3$h...@orion.cybercom.net>
pleo...@cybercom.net (Phil Leonard) wrote:
>pleo...@cybercom.net (Phil Leonard) wrote:
>Here is the bottom line. When Win 95 loads with Config.sys and
>Autoexec.bat, no CD,sound, or mouse loads. When Windows 95 exits to DOS,
>it uses Autoexec.DOS and Config.DOS. This then loads your mouse, CD, Sound
>etc. So in answer to your ORIGINAL comment, "but then those drivers take
>up needless space - and worse - while running in Win95 GUI mode.", not
>only is this mis-leading, it is downright FALSE!
Like I said, I'm *sure* I don't understand, but I know I can read the
screen. Here's DOSSTART.BAT:
C:\QEMM\LOADHI /R:2 /LO C:\MSINPUT\MOUSE\MOUSE.EXE
rem C:\QEMM\LOADHI /R:2 C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSCD0001 /E
/V /M:0
Now, I didn't have such a file before I loaded Win95, and I have had
this file ever since, and I didn't put it there. Seems reasonable to
attribute this to Win95, eh? So - while there might well be other and
better ways to do this - the FACT is Win95 generated it and uses it.
Period.
Eventually, I rem'd out the MSCDEX line and found out Win95 didn't
need it. Since Win95 created DOSSTART.BAT, and since it was loading
MSCDEX, and since it clearly wasn't required, it is equally clear that
it was taking up unnecessary space.
So, what I said wasn't fales, it was 100% correct in my experience.
100% wrong in your experience. But, a fact!
Secondly, I've included my CONFIG.DOS file below. I don't expect you
to read it all, but it is very clear that it cannot work with Win95.
Further, I'd have to be f'n blind to miss the menu choice it should
give me every time I go to MS-DOS. So tell me - just the facts, now -
how the hell could this file on my system ever be used the way you say
it is?
Look, I'm not saying your way doesn't work, or that you are wrong
about what YOU see. Just accord the rest of us some slack - we ain't
lyin' to ya, OK?
CONFIG.DOS
[common]
SWITCHES= /F
[MENU]
rem =================================================
menuitem=WINDOWS, Windows via Norton Desktop
menuitem=WINDOWSMAX, Windows via Program Manager (Internet)
menuitem=WINDOWS2, Windows 3.11 Drive M No NDW
menuitem=DOS, DOS 6.22 via DOSSHELL (623K)
submenu=SEAGAMES, Sea War Games and Simulations
submenu=WARGAMES, Other War Games
submenu=GAMES, Other Games
menucolor=15,1
menudefault=WINDOWS
numlock=ON
rem =================================================
[MYMENU]
rem =================================================
menuitem=WINDOWS, Windows via Norton Desktop
menuitem=WINDOWSMAX, Windows via Program Manager (Internet)
menuitem=WINDOWS2, Windows 3.11 Drive M No NDW
menuitem=DOS, DOS 6.22 via DOSSHELL (580K)
submenu=SEAGAMES, Sea War Games and Simulations
submenu=WARGAMES, Other War Games
submenu=GAMES, Other Games
rem =================================================
[WARGAMES]
rem =================================================
menuitem=ARMFIST, Armored Fist Tank Simulator (CD Box #1, #12)
menuitem=COMAN, Comanche Helicopter Simulator (CD Box #1, #11)
menuitem=DARK, Dark Forces (CD)
menuitem=DOOM1, Doom (CD Box#1, #5)
menuitem=DOOM2, Doom 2 (CD Box#1, #6)
menuitem=PRIVATER, Privateer
menuitem=WC3, Wing Commander 3 (CD Box #1, #1-#4)
submenu=MYMENU, Return to Main Menu
rem =================================================
[SEAGAMES]
rem =================================================
menuitem=AODCD, Aces of the Deep (CD Box#1, #10)
menuitem=GNB3, Great Naval Battles Vol. 3 (CD Box #1, #14)
menuitem=JUTLAND, Jutland (CD Box #1, #13)
menuitem=SEAWOLF, SeaWolf (CD Box #1, #9)
submenu=MYMENU, Return to Main Menu
rem =================================================
[GAMES]
rem =================================================
menuitem=HOCKEY, NHL Hockey '95 (CD Box #1, #18)
menuitem=INDY, IndyCar Racing
menuitem=GUEST7, Seventh Guest (CD Box #1, #7-#8)
menuitem=UKM, Under a Killing Moon
submenu=MYMENU, Return to Main Menu
rem =================================================
[WINDOWS]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\ASPIFCAM.SYS /D /O
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\DESKSCAN\SJIIX.SYS
rem DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CSP.SYS /UNIT=0
/BLASTER=A:220
rem DEVICE=C:\QEMM\LOADHI.SYS /RF C:\WINDOWS\COMMAND\ANSI.SYS
FILES=50
LASTDRIVE=N
rem =================================================
[WINDOWSMAX]
rem =================================================
DEVICE=C:\WINDOWS\HIMEM.SYS
device=c:\windows\emm386.exe x=A000-FFFF
DOS=HIGH,UMB
DEVICE=G:\PWRSCSI!\ASPIFCAM.SYS /D /O
DEVICE=G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
DEVICE=C:\SB16\DRV\CSP.SYS /UNIT=0 /BLASTER=A:220
SHELL=C:\COMMAND.COM C:\ /E:832 /P
FILES=50
LASTDRIVE=N
rem
===================================================================
[WINDOWS2]
rem =================================================
SET LOADHIDATA=C:\QEMM\LOADHI.RF
DEVICE=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\ASPIFCAM.SYS /D /O
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\DESKSCAN\SJIIX.SYS
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CSP.SYS /UNIT=0
/BLASTER=A:220
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\WINDOWS\COMMAND\ANSI.SYS
FILES=50
LASTDRIVE=N
[DOS]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CTSB16.SYS /UNIT=0
/BLASTER=A:220 I:7 D:1 H:5
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CTMMSYS.SYS
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CSP.SYS /UNIT=0
/BLASTER=A:220
FILES=50
LASTDRIVE=N
rem
===================================================================
rem
===================================================================
rem ******************************************************************
rem Games requiring HIMEM.SYS without EMM386.SYS
rem ******************************************************************
rem
===================================================================
[COMAN]
rem =================================================
device=C:\WINDOWS\himem.sys /TESTMEM:OFF
dos=high,umb
DEVICE=G:\PWRSCSI!\fdcd.sys /D:MSCD0001
SHELL=C:\COMMAND.COM C:\ /E:832 /P
LASTDRIVE=N
rem
===================================================================
[ARMFIST]
rem =================================================
device=C:\WINDOWS\himem.sys /TESTMEM:OFF
dos=high,umb
DEVICE=G:\PWRSCSI!\fdcd.sys /D:MSCD0001
SHELL=C:\COMMAND.COM C:\ /E:832 /P
LASTDRIVE=N
rem ******************************************************************
rem Games requiring HIMEM.SYS and EMM386.SYS
rem ******************************************************************
rem
===================================================================
[PRIVATER]
rem =================================================
DOS=HIGH
DOS=UMB
LASTDRIVE=N
rem ******************************************************************
rem Games requiring QEMM, CDROM, Max Memory, No EMS
rem ******************************************************************
rem
===================================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=c:\qemm\QEMM386.SYS rf ram
[GNB3]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[HOCKEY]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[AODCD]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[JUTLAND]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[SEAWOLF]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CTSB16.SYS /UNIT=0
/BLASTER=A:220 I:7 D:1 H:5
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CTMMSYS.SYS
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CSP.SYS /UNIT=0
/BLASTER=A:220
LASTDRIVE=N
rem
===================================================================
[DARK]
rem =================================================
switches=/f
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[DOOM1]
rem =================================================
switches=/f
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[DOOM2]
rem =================================================
switches=/f
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
rem
===================================================================
[GUEST7]
rem
===================================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
LASTDRIVE=N
rem
===================================================================
[WC3]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
rem DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
LASTDRIVE=N
rem =================================================
[INDY]
rem =================================================
set loadhidata=C:\QEMM\LOADHI.RF
device=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\SB16\DRV\CSP.SYS /UNIT=0
/BLASTER=A:220
FILES=50
LASTDRIVE=N
rem
===================================================================
[UKM]
rem =================================================
SET LOADHIDATA=C:\QEMM\LOADHI.RF
DEVICE=C:\QEMM\QEMM386.SYS RAM ST:M X=DE00-DF7F rf
DEVICE=C:\QEMM\LOADHI.SYS /RF C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP
SWAPSIZE=1024
DOS=HIGH,UMB
DEVICE=C:\QEMM\LOADHI.SYS /RF G:\PWRSCSI!\FDCD.SYS /D:MSCD0001
FILES=50
LASTDRIVE=N
Regards,
Neil
"A little rudeness and disrespect can elevate a meaningless
interaction to a battle of wills and add drama to an otherwise
dull day."
Hans van Raaij
trueba
>==========Alex Tellez, 10/17/95==========
>
>So how could I set it up so that when I cold boot straight into DOS,
>the mouse and CD-ROM drivers are loaded, but not when I boot
>into the GUI?
>Is this even possible without having to always edit any files?
>
> Alex Tellez
>
Easy. Set up a boot menu in your config.sys and autoexec.bat
file just like in DOS 6.x. First, you need to edit the MSDOS.SYS
(attrib -r-h-s msdos.sys first) and change the BootGUI=1 line to
BootGUI=1. In the menu selection that loads the GUI don't load
the mouse, CD-ROM, sound board, etc. drivers. Remember to run
WIN as the last line in your autoexec.bat that gets run in your
GUI menu commands. In the menu selection that goes to straight
DOS load them. . Reboot and you should have a menu that will
allow you to do what you want.
Ted Katranas
> So how could I set it up so that when I cold boot straight into DOS,
>the mouse and CD-ROM drivers are loaded, but not when I boot into the GUI?
>Is this even possible without having to always edit any files?
>
> Alex Tellez
>
OK, here goes...
- First, locate the file "Exit To Dos" in the \WINDOWS directory. (It's a
.PIF file, extension not showing).
- Right-click on it and select properties.
- Select the "Program" tab, and click on "Advanced"
- Check the "MS-DOS mode" and "Specify a new MS-DOS configuration" options
- Type the commands you need for CONFIG.SYS and AUTOEXEC.BAT in the
appropriate listboxes (use commands and drivers that worked with your
pre-win95 configuration, but make sure you use the ones provided in the
\WINDOWS\COMMAND directory if new versions exist).
- Click OK
P.S. You can click the "Configuration" button and you get preset entries
for mouse, SmartDrive, etc. Then you edit them, and add your own.
Next time you select "Restart the computer in MS-DOS mode" from the
shut-down menu, your computer will reboot with the new configuration, (and
it will keep doing that, until you hit <Esc> when prompted, or type "Exit"
at the DOS prompt).
BTW, the settings for AUTOEXEC.BAT and CONFIG.SYS made above, are your
AUTOEXEC.DOS and CONFIG.DOS, plus a couple of lines added by windows
itself.
Hope this Helps
-----------------
Ted Katranas
kt...@hol.gr
Athens, Greece
-----------------
trueba
>==========Ted Katranas, 10/18/95==========
Unless I miss my guess here he's not talking about restarting in
MS-DOS mode from the Windows 95 GUI, but booting DIRECTLY into
DOS. To do what he wants here, he has to set up a boot menu.
Jim Trigg
> >>BTW, the settings for AUTOEXEC.BAT and CONFIG.SYS made above, are your
> >>AUTOEXEC.DOS and CONFIG.DOS, plus a couple of lines added by windows
> >>itself.
> I'm not sure this is true (the part about AUTOEXEC.DOS and
> CONFIG.DOS), because to test it, I put a few Echo lines in my
> AUTOEXEC.DOS file to echo a unique message to the screen so I'll know
> when it runs, and I don't see it when I shutdown Win 95 with "Restart
> the computer in MS-DOS mode", nor if I boot to the command prompt
> using F8. Anybody *really* know what AUTOEXEC.DOS and CONFIG.DOS are
> for?
Yes. They are the AUTOEXEC.BAT and CONFIG.SYS used when you boot with
USE PREVIOUS VERSION OF MS-DOS and are initially the backup copies of
your old AUTOEXEC.BAT and CONFIG.SYS from before installing W95.
(This was determined by examining CONFIG.DOS and finding my old boot
menu.)
Just a Thought,
Jim Trigg
John Mackowick
>I'm not sure this is true (the part about AUTOEXEC.DOS and
>CONFIG.DOS), because to test it, I put a few Echo lines in my
>AUTOEXEC.DOS file to echo a unique message to the screen so I'll know
>when it runs, and I don't see it when I shutdown Win 95 with "Restart
>the computer in MS-DOS mode", nor if I boot to the command prompt
>using F8. Anybody *really* know what AUTOEXEC.DOS and CONFIG.DOS are
>for?
>Bruce
>bri...@moa.com
Those *.dos files are only used if you boot to your 'Old DOS" (the last choice
on the <F8> menu - boot to a previous OS), not the same as booting to the
Command prompt from <F8>, that gives you Win95's 'DOS' (7.0)
In your root, you should have two sets of these [5] system files;
autoexec.bat
config.sys
command.com
io.sys
msdos.sys
Autoexec.bat and Config.sys are optional under Windows 95....
Whichever set is currently -not- in use gets renamed with the extension of the
other OS. i.e., if you are currently running in Win95, the 'old DOS' set gets
renamed to *.DOS (with the exception of IO.SYS, it gets renamed to WINBOOT.SYS).
If you're running under your old DOS, the Win95 set gets renamed to *.W40. If
you decide to nuke your old DOS, you can safely delete the *.DOS files....
============================
John Mackowick / WUGNET
Windows Users Group Network
Powered by W95 TCP/IP & IE 2.0
email:jo...@sgi.net
74242...@compuserve.com
============================
Ted Katranas
>>>Next time you select "Restart the computer in MS-DOS mode" from the
>>>shut-down menu, your computer will reboot with the new
>>>configuration, (and
>>>it will keep doing that, until you hit <Esc> when prompted, or
>>>type "Exit"
>>>at the DOS prompt).
>>>
>>>BTW, the settings for AUTOEXEC.BAT and CONFIG.SYS made above, are your
>>>AUTOEXEC.DOS and CONFIG.DOS, plus a couple of lines added by windows
>>>itself.
>
>I'm not sure this is true (the part about AUTOEXEC.DOS and
>CONFIG.DOS), because to test it, I put a few Echo lines in my
>AUTOEXEC.DOS file to echo a unique message to the screen so I'll know
>when it runs, and I don't see it when I shutdown Win 95 with "Restart
>the computer in MS-DOS mode", nor if I boot to the command prompt
>using F8. Anybody *really* know what AUTOEXEC.DOS and CONFIG.DOS are
>for?
>Bruce
>bri...@moa.com
>
>
Try deleting CONFIG.DOS and AUTOEXEC.DOS, and shut down to DOS mode again.
The settings in the PIF files, are now your AUTOEXEC.BAT and CONFIG.SYS
files, the original ones being renamed to *.WOS.
Make a small change in your AUTOEXEC.BAT (delete or add an ECHO line or
something). When you enter windows again, the changes you just made are
reflected in the PIF file.
When windows restarts, it usualy deletes the files, and renames the *.WOS
files back.
If for any reason the deletion fails (I haven't tested the reason for that
yet) the old files are renamed to *.DOS. hey are not used though, because
the next time you fall back to DOS mode, the PIF settings are used.
I'll test some more (when I have time) and re-post.
Ted Katranas
(open mouth, insert foot, echo internationally)
Err... well, correction follows.
I tested and looked around, and this is what I came up with:
Config.sys and Autoexec.bat, we all know about them.
Config.dos and Autoexec.dos (with command.dos) are used when you press F4
during bootup, to start in your old MS-DOS version (6.2). The files and
drivers you use in them, should come from your old \DOS directory to avoid
"incorrect DOS version" errors.
Config.wos and Autoexec.wos are the normal Config.sys and Autoexec.bat
files when the computer is in MS-DOS mode, or old MS-DOS mode. They are
renamed to *.bat and *.sys when win95 is restarted.
The settings in the PIF file I mentioned in my previous post, are converted
to Autoexec.bat and Config.sys when you enter MS-DOS mode (if you override
the current MS-DOS settings) and are deleted upon win95 restart.
Hope this clears it up, and sorry for the boo-boo.
Wayne S. Pelouch
copied to CONFIG.SYS and AUTOEXEC.BAT when you boot to
your OLD version of DOS. The only way to do this is by
pressing F8 and choosing Old DOS (or just pressing F4)
at boot time.
When you are in OLD DOS mode you will also see a
CONFIG.W40 and AUTOEXEC.W40 which are the Windows 95
and "New DOS" files.
When you boot into Windows 95 OR a ("new") DOS session
the CONFIG.W40 and AUTOEXEC.W40 get copied to CONFIG.SYS
and AUTOEXEC.BAT. Furthermore if you run a DOS session
from Windows 95 (not as a box) DOSSTART.BAT will be
executed instead of rebooting. If you specified a custom
DOS configuration, then it will reboot and use your
custom settings.
--
pelo...@plk.af.mil
##############################################################
# Wayne S. Pelouch, PhD # Ultrafast Laser Research #
# Phillips Lab (LIDD) # Femtosecond Lasers #
# 3550 Aberdeen Ave. SE, Bldg 243 # Semiconductor Physics #
# Kirtland AFB, NM 87117 # Nonlinear Optics #
##############################################################