Is it possible to close Windows (98) and return to DOS?
I boot into DOS, I work in DOS.
I start Windows, I work in Windows and DOS.
I close Windows... but where is DOS?
I enter exit at the prompt and Windows starts!?
That is not DOS.
I have asked this question in other groups, but so far no
luck. Anyone?
--
Outsider
MS-DOS 6.22, Windows for Workgroups 3.11, Netscape Navigator 4.08
Your mouse has moved. Reboot machine for changes to take effect.
Sent via Deja.com
http://www.deja.com/
^ Is it possible to close Windows (98) and return to DOS?
Yes. Install a DOS operating system and configure Windows 98 with a
multiboot option. You can then either boot into Windows 98 with or without
the GUI, or you can boot into DOS.
Frank
This post was drawn to my attention. It is better dealt with in NGs
such as uk.comp.os.win95 (which deals with win98 and Me issues as
well), and which I have added to the group list of this reply. In my
experience, uk.comp.os.win95 is one of the most useful NGs for
Windows 9x issues. Traffic is fairly low, as is random noise, and
posts tend to be dealt with in depth, albeit not necessarily so
quickly as the high-traffic, high-noise, NGs.
The answer to your question is: Yes.
There are three principle ways of running MS-DOS applications in
Windows 9x (you seem to be using method 2, but want method 3):
1) In a DVM (DOS Virtual Machine) or DOS box
This takes advantage of the V86 mode of the higher x86 processors
(x>=3). Using this processor mode Windows can run a DOS session from
the GUI. Applications running in this environment are placed in a
virtual machine that resembles a real mode x86 processor. Extensive
GUI functionality is available in this mode (including 32 bit disk
cacheing, long file name handling, and additional functionality in
commands such as xcopy). This is generally the best way to run many
DOS applications. Multiple instances of DVMs can be run
simultaneously. Each DVM inherits the master environment state,
which can however be altered: so for example, each DVM instance can
be set to start automatically with its own specific path,
environment variable set, and operating state (for example processor
access priority).
2) MS-DOS mode
Win9x operates with a real-mode loader in IO.SYS and is switched to
protected mode to run the GUI. Once in the GUI, a fast route to a
single-task full screen DOS shell is provided. Only one instance of
this shell can be loaded, all the GUI applications are closed, and
the additional functionality available in a DVM is lost. This is
known as MS-DOS mode, or "Restart the computer in MS-DOS mode".
Windows can very quickly switch out of protected mode and load this
single-task DOS shell, which retains the settings as read from the
DOS startup files when your Windows session began. Since it is a
temporary command.com instance, typing EXIT at the DOS prompt exits
the shell. The MS-DOS mode shell is started by a temporary batch
script that returns to the Windows GUI once control is returned to
the temporary script. This appears to be what you have been doing.
This resembles, but isn't, plain vanilla DOS. It is provided for
quick startup of DOS applications that require a single task DOS
mode by users normally working in the GUI.
3) Plain vanilla DOS (7.1)
Boot the machine, (or reboot: plain "Restart the Computer" - NOT the
MS-DOS mode option). During the boot process, when the message
"Starting Windows 98..." is displayed a startup menu is available.
Press F8 when you see this message to bring up the menu. Select the
option "Command prompt only" (wording varies slightly with
sub-versions - it's around or about item 6). You will be booted into
a plain vanilla DOS session with a permanent COMMAND.COM instance.
Typing EXIT at the prompt has no effect. This is a normal real-mode
DOS session. This appears to be what you wish. This third method of
using DOS has been removed in current versions of WindowsMe.
Some further differences arise, mostly connected with how Windows
was installed and how the assorted startup files are configured, and
mostly concern device access (such as CD-ROM drive access). If you
have follow-up questions, I prefer to answer in uk.comp.os.win95
since I don't have time to read amb regularly at present.
--
William Allen
>
>
>Is it possible to close Windows (98) and return to DOS?
>
>I boot into DOS, I work in DOS.
>I start Windows, I work in Windows and DOS.
>I close Windows... but where is DOS?
>I enter exit at the prompt and Windows starts!?
>That is not DOS.
>
>I have asked this question in other groups, but so far no
>luck. Anyone?
Hmmm, just a guess to me, but I'd edit MSDOS.SYS so that under
[Options} the line that says BootGUI=1 now reads BootGUI=0. Then I'd
restart my machine. That should get you to boot to the command prompt
by default. Then at the command prompt, try typing WIN. That should
start Win98. Disable any power managment (shutdown at exit, that sort
of thing) features. Exit Windows. My guess is that when you shut
down Windows, you'll be at your command prompt... Let me know if it
works...
Regards...
Ray
You have to edit msdos.sys (mind the read-only attribute) to prevent booting
to GUI. Change "BootGUI=0" to 1 then rename LOGOS.SYS and LOGOW.SYS found in
the windows folder. These are just plain old bitmap files with a different
extension. You may even want to get rid of the splash on boot by placing a
"LOGO=0" in the same section.
Note, some hardware powers off when windows shuts down regardless of
removing these two exit screens. :(
Then you place WIN in your autoexec as you would in Win3.x machines. I'm
sure you know enough about using multi-config that I don't need to go there.
**************************
I would like to remind you however, if the boot partition of this machine is
FAT32, don't bother trying to install 6.22 to attempt to use the "Boot to
previous OS" option. The 6.22 setup will wipeout FAT 32 in a heartbeat.
**************************
--
Todd Vargo (body of message must contain my name to reply by email)
As in the Win1-3.x days?
Yes, you can:
1. Set BootGUI=0 in MSDOS.SYS. Without this, there is no
shell for Windoze to return to.
2. Run %windir%\system\msconfig.exe. Select Advanced...
Set Disable fast shutdown.
You should now be able to return to DOS using the
"Shut Down" command of the Start Menu.
Alas, if you have an ATX computer, you'll find that
Windows will power down the machine. To prevent this
you will need to beat win.com into shape:
debug %windir%\win.com
-s 100,f000 cd,15
Debug will list a number of addresses where INT 15
instructions were found:
0BE4:1367
0BE4:13A8
0BE4:13B2
[etc.]
Begin disassembly at the first address:
-u 1367
0BE4:1367 CD15 INT 15
0BE4:1369 7303 JNB 136E
0BE4:136B E99C00 JMP 140A
0BE4:136E 81FB4D50 CMP BX,504D
[etc.]
Win.com is looking for APM. Such behaviour is clearly
undesirable, so quell it:
-a 1369
0BE4:1369 nop
0BE4:136A nop
0BE4:136B
Now save your work and return to the command prompt:
-w
Writing 060D7 bytes
-q
Congratulations. You have eliminated a major annoyance
of Win98.
> I have asked this question in other groups, but so far no
> luck. Anyone?
I asked a similar question in a couple of Windoze groups,
but might as well have asked the cat. Eventually someone
on comp.os.msdos.programmer informed me about the "Fast
shutdown" thing. The win.com hacking is self explanatory
if you have the APM spec, which is available from the MS
FTP site.
The most likely reason why you don't get useful answers
from Windoze newsgroups is that they're populated with a
high percentage of Windoze-only users with little or no
background experience. Many (most?) of them would find
themselves lost at a command prompt.
What happens in my case is the computer warm boots when
I choose shutdown (!). Why is my computer now warm booting
when I elect to shutdown the computer? Perhaps, this dialog
box can be hacked out of the equation and just close the GUI
thereby returning to real DOS?
Ok, I tried it but was unsuccessful.
-u 1367
21F4:1367 CD15 INT 15
21F4:1369 7303 JNB 136E
21F4:136B E99C00 JMP 140A
21F4:136E 81FB4D50 CMP BX,504D
21F4:1372 7403 JZ 1377
21F4:1374 E99300 JMP 140A
21F4:1377 3D0101 CMP AX,0101
21F4:137A 7303 JNB 137F
21F4:137C E98B00 JMP 140A
21F4:137F 51 PUSH CX
21F4:1380 A3D30E MOV [0ED3],AX
21F4:1383 B80054 MOV AX,5400
21F4:1386 33DB XOR BX,BX
-a 1369
21F4:1369 nop
21F4:136A nop
21F4:136B
-w
Skriver 06177 byte
-q
Ok, my version of win.com (24,951 bytes) must be different?
The address above after the -a 1369 are different than what
you posted. Also the "writing bytes" message is different.
WINDOWS>fc /b win.com win.hak
00001269: 73 90 ;original
0000126A: 03 90 ;hacked
The hacked win.com makes no noticible difference.
All help appreciated.
BTW, my msdos.sys looks like this:
[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C
[Options]
BootMulti=1
BootGUI=0
DoubleBuffer=0
AutoScan=0
WinVer=4.10.2222
Network=1
Logo=0
LoadTop=0
BootDelay=0
BootMenu=1
SystemReg=0
--
<!-Outsider-//>
Your mouse has moved. Reboot computer for changes to take effect.
Oops, I had the zero and one reversed above, but you get the idea.
I have Win98SE and this "Disable fast shutdown" option is not there. What
gives?
>
> You should now be able to return to DOS using the
> "Shut Down" command of the Start Menu.
>
> Alas, if you have an ATX computer, you'll find that
> Windows will power down the machine. To prevent this
> you will need to beat win.com into shape:
> debug %windir%\win.com
[debug code snipped]
> Congratulations. You have eliminated a major annoyance
> of Win98.
Win95 has the same effect on ATX machines too.
(the 95 machine I use at work does it)
[snip]
> > You should now be able to return to DOS using the
> > "Shut Down" command of the Start Menu.
>
> What happens in my case is the computer warm boots when
> I choose shutdown (!). Why is my computer now warm booting
> when I elect to shutdown the computer? Perhaps, this dialog
> box can be hacked out of the equation and just close the GUI
> thereby returning to real DOS?
That's very strange. When shutdown is selected you should not be getting a
warm boot at all. I've never seen this happen before.
[snip]
> The hacked win.com makes no noticible difference.
> All help appreciated.
>
> BTW, my msdos.sys looks like this:
> [Paths]
> WinDir=C:\WINDOWS
> WinBootDir=C:\WINDOWS
> HostWinBootDrv=C
>
> [Options]
> BootMulti=1
> BootGUI=0
> DoubleBuffer=0
> AutoScan=0
> WinVer=4.10.2222
> Network=1
> Logo=0
> LoadTop=0
>
> BootDelay=0
> BootMenu=1
> SystemReg=0
This has nothing to do with the problem at large, but, I hope you left in
the padding lines.
;Msdos.sys must be > 1024 bytes, bla bla bla.
;a xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ect.
I left those in, but I wonder if it ever makes a difference?
I've worked on several systems where msdos.sys less the
prescribed size and I never noticed any problem due to it.
That usually means something is wrong. It happens to me
occasionally.
> Why is my computer now warm booting
> when I elect to shutdown the computer?
If it didn't use to happen before you disabled "Fast shutdown",
it probably crashes somewhere in WIN.COM.
> >
> > Win.com is looking for APM. Such behaviour is clearly
> > undesirable, so quell it:
> > -a 1369
> > 0BE4:1369 nop
> > 0BE4:136A nop
> > 0BE4:136B
> >
> > Now save your work and return to the command prompt:
> > -w
> > Writing 060D7 bytes
> > -q
> >
>
> Ok, I tried it but was unsuccessful.
>
> -u 1367
> 21F4:1367 CD15 INT 15
> 21F4:1369 7303 JNB 136E
> 21F4:136B E99C00 JMP 140A
> 21F4:136E 81FB4D50 CMP BX,504D
> 21F4:1372 7403 JZ 1377
> 21F4:1374 E99300 JMP 140A
> 21F4:1377 3D0101 CMP AX,0101
> 21F4:137A 7303 JNB 137F
> 21F4:137C E98B00 JMP 140A
> 21F4:137F 51 PUSH CX
> 21F4:1380 A3D30E MOV [0ED3],AX
> 21F4:1383 B80054 MOV AX,5400
> 21F4:1386 33DB XOR BX,BX
> -a 1369
> 21F4:1369 nop
> 21F4:136A nop
> 21F4:136B
> -w
> Skriver 06177 byte
> -q
>
>
> Ok, my version of win.com (24,951 bytes) must be different?
Mine is 24,791 bytes. The difference can probably be explained
by the fact that you have a Danish version of Windows.
> The address above after the -a 1369 are different than what
> you posted.
Are you referring to the segment address (21F4)? That just
means your WIN.COM was loaded at a higher address, and is
not a problem in itself.
> Also the "writing bytes" message is different.
Yes, because you're win.com is larger than mine
> WINDOWS>fc /b win.com win.hak
>
> 00001269: 73 90 ;original
> 0000126A: 03 90 ;hacked
>
>
> The hacked win.com makes no noticible difference.
That suggests the hack didn't cause any additional problems.
> All help appreciated.
>
> BTW, my msdos.sys looks like this:
> [Paths]
> WinDir=C:\WINDOWS
> WinBootDir=C:\WINDOWS
> HostWinBootDrv=C
>
> [Options]
> BootMulti=1
> BootGUI=0
> DoubleBuffer=0
> AutoScan=0
> WinVer=4.10.2222
> Network=1
> Logo=0
> LoadTop=0
>
> BootDelay=0
> BootMenu=1
> SystemReg=0
Your MSDOS.SYS settings are almost exactly identical to
mine. I have Network=0. What are LoadTop and SystemReg?
You could try removing some TSRs and device drivers and
see if it makes any difference.
That's odd. What is the version and file size of your msconfig.exe?
Mine is 4.10.1998 and it takes 69,632 bytes.
Anyway, this registry hack will probably work just as well:
[HKLM\System\CurrentControlSet\Control\Shutdown]
"FastReboot"="0"
> > You should now be able to return to DOS using the
> > "Shut Down" command of the Start Menu.
> >
> > Alas, if you have an ATX computer, you'll find that
> > Windows will power down the machine. To prevent this
> > you will need to beat win.com into shape:
>
> > debug %windir%\win.com
> [debug code snipped]
> > Congratulations. You have eliminated a major annoyance
> > of Win98.
>
> Win95 has the same effect on ATX machines too.
> (the 95 machine I use at work does it)
Yeah, I know. The Win95 win.com is in fact interchangeable
with the W98 win.com. I haven't tried the win.com from
a 3.xx version of Windows, but it would be an interesting
experiment.
See here:
http://members.aol.com/axcel216/msdos.htm#TAB
> You could try removing some TSRs and device drivers and
> see if it makes any difference.
>
I got a good respone in: microsoft.public.win98.setup (!).
I could not find the message on dejanews, so I included
it below.
------
Found at
http://members.aol.com/axcel216
Exit to Dos
To create the "Exit to DOS.pif" (Program Information File)
executable:
You will need to shut down Windows and restart in MS-DOS mode,
then go back into Win98/95 in order for the "Exit to DOS.pif"
file to be created in your Windows folder. According to this
MicroSoft Knowledge Base (MSKB) article:
http://support.microsoft.com/support/kb/articles/q138/9/96.asp
to define custom Config.sys and Autoexec.bat files to be
processed when you restart your computer using the "Restart
(the computer) in MS-DOS mode" Shut down... option, follow
these steps:
1. Click the Start button -> click Shut Down -> click "Restart
(the computer) in MS-DOS mode" -> click Yes/OK.
2. At the MS-DOS command prompt -> type "EXIT" (without
quotation marks) -> press Enter.
NOTE: Steps 1-2 are IMPORTANT if you have never used the
"Restart (the computer) in MS-DOS mode" option before. The
"Exit to DOS.pif" file is not created until you perform these
steps the first time.
3. Start Windows Explorer.
4. Highlight the "Exit to DOS" file in the Windows folder.
Right-click on it-> select Properties.
5. Click the Program tab -> click Advanced -> deselect the
"Warn before entering MS-DOS mode" box.
6. Check the "MS-DOS mode" box -> click the Advanced tab ->
check the "Specify A New MS-DOS Configuration" option.
7. Define the custom Config.sys file in the "Config.sys For
MS-DOS Mode" box. Define the custom Autoexec.bat file in the
"Autoexec.bat For MS-DOS Mode" box.
8. Click OK/Apply to close all dialog boxes.
From now on, each time when you'll restart your system using
the "Restart (the computer) in MS-DOS mode" option, your
custom Config.sys and Autoexec.bat files will be processed.
B. To shut down Windows 98/95 to the true/native/real MS-DOS
prompt from a Desktop icon, follow the same steps above, except
select the "Use current MS-DOS configuration" instead of
"Specify A New MS-DOS Configuration" at step #6. Name this new
batch file EXIT2DOS.BAT, place it a folder of your choice,
and then create a shortcut to it on the Desktop. Also, you can
skip steps 1-2 above when creating EXIT2DOS.BAT.
NOTES: - Read the "2 DOS OR NOT 2 DOS" topic in MYTIPS95.TXT
(included) for details on all Windows 98/95 "boot to DOS"
options.
Part 2
DOS NOW! [UPDATED 2|25|98] [+]
I found a fool-proof way to go to the real/true/native MS-DOS
mode when you click the Start button, then choose Shut Down,
and select the default: "Shut down the computer" in Windows
98/95. No more nagging "Waiting to shut down" or "It's safe to
turn off..." screens either.... And you can also boot directly
to the native MS-DOS mode if you like. :) To achieve this, you
need to perform these 5 easy steps:
1. Move the LOGOW.SYS and LOGOS.SYS files (just bitmaps with a
different extension) from your Windows folder (default is
C:\Windows) to a backup disk, eventually together with these
other files listed below.
2. Move to an empty, formatted 1.44 MB floppy diskette all the
following files (you may not have all of them depending on your
Win9x setup), located in the root folder of your boot drive
(C:\ is default):
Filename: Attributes:
---------------------------
BOOTLOG.PRV Hidden
BOOTLOG.OLD Hidden
BOOTLOG.TXT Hidden
DETLOG.OLD Hidden, System
DETLOG.PRV Hidden, System
DETLOG.TXT Hidden, System
MSDOS.--- Hidden
NETLOG.TXT Archive
OEMLOG.TXT Hidden
SCANDISK.LOG Archive
SETUPLOG.TXT Hidden
SUHDLOG.DAT Read-only, Hidden
SYSTEM.1ST Read-only, Hidden, System
W95UNDO.DAT Read-only, System
W95UNDO.INI Read-only, System
None of the files above are needed for Windows 98/95 proper
operation! They were created when you first installed Win98/95
and further updated when you have made certain changes to your
system configuration, or were created when your Win98/95
system loaded/shut down improperly. The only useful file (that
I know of) on this list is SYSTEM.1ST, good to restore your
original Registry, in case of a sudden disaster (system lockup,
file corruption etc), when you're caught offguard, with no
recent backups of your Win9x Registry files. Just keep that
floppy handy... The easiest way to move all these files is by
running File Manager (FM=Winfile.exe, found in C:\Windows). But
you can also do it in Explorer. If you use File Manager: make
sure you can view ALL files in File Manager (including Hidden,
Read-only AND System files): left-click View, By File Type...,
and then check the "Show Hidden/System Files" box. In File
Manager highlight all the above C:\ root files by holding down
Ctrl and then left-clicking on each one of them. Now drag all
highlighted files to the A: drive icon, while holding down Alt
(to move them instead of just copying). Release the left mouse
button and then answer Yes to all those confirmation screens.
[nag... nag... :)]
3. Add/modify the SHELL line in your Config.sys file (located
in C:\ root), to look similar to this one:
SHELL=C:\COMMAND.COM C:\ /E:1024 /L:128 /U:128 /P
Make sure you have a copy of COMMAND.COM in the root folder of
your C:\ boot drive, to make the line above work properly. You
can usually find COMMAND.COM in the C:\Windows\Command folder.
Now reboot, so the new Command environment can take "charge".
4. Edit your MSDOS.SYS file (found in C:\ root) by using
SYS95.BAT (included), and add/modify this [Options] section line
to read:
BootGUI=0
Save your work and exit the text editor. This setting prevents
the Windows GUI from loading, and you'll find yourself at the
plain DOS prompt after a (re)boot.
5. Now close all applications, click Start, click Shut Down, and
answer Yes/OK to the "Shut down the computer" selection. You'll
find yourself at the plain DOS prompt, to do whatever you want:
type those cryptic DOS commands, or play your coolest 3D SuperVGA
DOS game [:-)] that won't run under the Win98/95 GUI... sounds
familiar?!... instead of having to power off your PC, or reboot
again [what a pain... :(] into MS-DOS mode. When you're done
"playing" at [or with :)] DOS, just type WIN and press Enter to
reload the Windows GUI. No need for another reboot to get back to,
or out of Windows from now on.
------
I have not yet tried any of the above, but certainly will
do so at my earliest opportunity. If anyone has tried,
please speak up.
--
Outsider
BTW, I believe it is actually a cold boot.
> If it didn't use to happen before you disabled "Fast shutdown",
> it probably crashes somewhere in WIN.COM.
>
I wonder if this problem is connected with another,
namely that none of my shortcut keys work! They did
when I assigned them, but shortly after,they stopped.
You know, like, Ctrl+Alt+D to start DOS, Ctrl+Alt+N
to start Notepad, etc. Anyone know why this would
happen?
--
Outsider
As I said Win98SE(4.10.2222) which is where this problem is. It is a
different size too.
>
> Anyway, this registry hack will probably work just as well:
> [HKLM\System\CurrentControlSet\Control\Shutdown]
> "FastReboot"="0"
I already had this set.
>
> > > You should now be able to return to DOS using the
> > > "Shut Down" command of the Start Menu.
> > >
> > > Alas, if you have an ATX computer, you'll find that
> > > Windows will power down the machine. To prevent this
> > > you will need to beat win.com into shape:
> >
> > > debug %windir%\win.com
> > [debug code snipped]
> > > Congratulations. You have eliminated a major annoyance
> > > of Win98.
> >
> > Win95 has the same effect on ATX machines too.
> > (the 95 machine I use at work does it)
>
> Yeah, I know. The Win95 win.com is in fact interchangeable
> with the W98 win.com. I haven't tried the win.com from
> a 3.xx version of Windows, but it would be an interesting
> .
I don't have time to experiment with it right now. If you have some free
time, I would appreciate the result. Note, I have checked CMOS several times
in the past for a power feature to disable. Nothing there to change. I'm
thinking there may be a jumper to change on the mobo, but I'm not really
worried about it that much. It only takes a few more seconds to use the
"Restart" shutdown option, so it's no big deal.
[menu]
menuitem=WINDOZE (Windoze 98)
menuitem=DOS (Vanilla Dos 7.1)
menudefault=WINDOZE,5
menucolor=7,0
and in your autoexec.bat:
@echo off
IF "%config%"=="WINDOZE" GOTO WINDOZE
IF "%config%"=="DOS" GOTO DOS
:WINDOZE
(put windoze stuff here)
echo. Running Windoze...
c:
chdir \windoze
win
:DOS
(put dos stuff here)
edit your msdos.sys in your root directory (you will have to remove
read-only attributes before you can make changes to it change the line
that says BootGUI=1 to BootGUI=0
sorry if some of this is a little unclear, but I hope it helps.
--
john
ICQ# - 16141921
email - john-ca at redhotant dot net
web - http://www.the-void.co.uk/cv/
Procrastination - I'll deal with it sooner or later.
Yes, you said you had Win98SE (4.10.2222) but that doesn't necessarily
mean you have the same version of msconfig.exe (I have Win98SE OEM).
Anyway, since the size is different, your copy is obviously not
identical to mine.
> It is a different size too.
>
> >
> > Anyway, this registry hack will probably work just as well:
> > [HKLM\System\CurrentControlSet\Control\Shutdown]
> > "FastReboot"="0"
>
> I already had this set.
Then you have "Fast shutdown" disabled. Did you apply the hack
to your win.com? What happens when you shut down?
> > Yeah, I know. The Win95 win.com is in fact interchangeable
> > with the W98 win.com. I haven't tried the win.com from
> > a 3.xx version of Windows, but it would be an interesting
> > .
>
> I don't have time to experiment with it right now. If you have some free
> time, I would appreciate the result.
It didn't work - WIN386.EXE wasn't found. The Win3.x win.com is, by the
way, considerably larger than the '9x ones.
> Note, I have checked CMOS several times
> in the past for a power feature to disable. Nothing there to change. I'm
> thinking there may be a jumper to change on the mobo, but I'm not really
> worried about it that much.
I don't think there's a jumper for it, and I've never seen a BIOS where
you could disable the APM interface (yes, you can disable power managent,
but the INT 15 interface to APM is still functional).
Before I learnt how to hack win.com, I wrote a little TSR called KILLAPM:
http://195.148.172.4/~aw/sw/index.html
It hooks INT 15 and hides the APM interface. However, it's still possible
to shut down the computer using the chipset directly - I have a little
utility that does this too. It works on my Intel BX chipset, and I would
be interested in hearing whether it works on others:
C:\exec>debug bxoff.com
-u 100
0BE4:0100 BA0540 MOV DX,4005
0BE4:0103 B020 MOV AL,20
0BE4:0105 EE OUT DX,AL
0BE4:0106 CD20 INT 20
[snip]
> Did you apply the hack
> to your win.com? What happens when you shut down?
Bingo! I forgot to apply the debug hack. It works now.
I've been frustrated by the so called shutdown bug patch which I previously
installed from M$ that was suposed to fix the shutdown freeze bug in
Win98. Since I applied the so called patch, I have to shutdown windows
twice every time.
Note, although the hack works, it takes much longer to get back to the
command prompt than to it does to just use the "Restart" option with
FastReboot enabled. Too bad we can't just get windows to shutdown fast
without the reboot. This brings to mind a batch that could be used to
selectively set this registry key but IMO the FastReboot is faster so why
bother.
> > > Yeah, I know. The Win95 win.com is in fact interchangeable
> > > with the W98 win.com. I haven't tried the win.com from
> > > a 3.xx version of Windows, but it would be an interesting
> > > .
> >
> > I don't have time to experiment with it right now. If you have some free
> > time, I would appreciate the result.
>
> It didn't work - WIN386.EXE wasn't found. The Win3.x win.com is, by the
> way, considerably larger than the '9x ones.
>
> > Note, I have checked CMOS several times
> > in the past for a power feature to disable. Nothing there to change. I'm
> > thinking there may be a jumper to change on the mobo, but I'm not really
> > worried about it that much.
>
> I don't think there's a jumper for it, and I've never seen a BIOS where
> you could disable the APM interface (yes, you can disable power managent,
> but the INT 15 interface to APM is still functional).
This what I figured. Whenever I see anyone posting to change a setting in
CMOS I'll tell them to blow_it_out_their...oops, well I'll be a bit nicer.
>
> Before I learnt how to hack win.com, I wrote a little TSR called KILLAPM:
> http://195.148.172.4/~aw/sw/index.html
>
> It hooks INT 15 and hides the APM interface. However, it's still possible
> to shut down the computer using the chipset directly - I have a little
> utility that does this too. It works on my Intel BX chipset, and I would
> be interested in hearing whether it works on others:
> C:\exec>debug bxoff.com
> -u 100
> 0BE4:0100 BA0540 MOV DX,4005
> 0BE4:0103 B020 MOV AL,20
> 0BE4:0105 EE OUT DX,AL
> 0BE4:0106 CD20 INT 20
I downloaded the killapm tool and ran it prior to loading windows. It did
not work for me (Celeron). The computer still rebooted when I used the
restart option. No dice with BXOFF.COM either.
Just to be sure I got it right, here is the contents of bxoff.com which is 8
bytes.
-d100 107
1116:0100 BA 05 40 B0 20 EE CD 20
I tried using bxoff with and without loading killapm. Oh well, it sure would
have been nice to report it worked for me.
I looked into the patch, and it turned out that it replaces msconfig.exe,
which explains your missing "fast shutdown" option.
> Note, although the hack works, it takes much longer to get back to the
> command prompt than to it does to just use the "Restart" option with
> FastReboot enabled. Too bad we can't just get windows to shutdown fast
> without the reboot. This brings to mind a batch that could be used to
> selectively set this registry key but IMO the FastReboot is faster so why
> bother.
The reason why I bother is that I want to actually shut down windows - even
the "restart in MS-DOS mode" option seems to leave a piece of windows in
memory. I think this is what the original poster (Outsider) wanted to do.
> > Before I learnt how to hack win.com, I wrote a little TSR called KILLAPM:
> > http://195.148.172.4/~aw/sw/index.html
> >
> > It hooks INT 15 and hides the APM interface. However, it's still possible
> > to shut down the computer using the chipset directly - I have a little
> > utility that does this too. It works on my Intel BX chipset, and I would
> > be interested in hearing whether it works on others:
> > C:\exec>debug bxoff.com
> > -u 100
> > 0BE4:0100 BA0540 MOV DX,4005
> > 0BE4:0103 B020 MOV AL,20
> > 0BE4:0105 EE OUT DX,AL
> > 0BE4:0106 CD20 INT 20
>
> I downloaded the killapm tool and ran it prior to loading windows. It did
> not work for me (Celeron). The computer still rebooted when I used the
> restart option.
Well of course. But what happened when you used the "Shut down" option?
If "Fast shutdown" is disabled, you should get back to DOS, even without
a hacked win.com.
Win.com definitely uses the BIOS APM interface, but I'm pretty sure
the Windows kernel itself programs the hardware directly, so KILLAPM
won't stop it.
> No dice with BXOFF.COM either.
>
> Just to be sure I got it right, here is the contents of bxoff.com which is 8
> bytes.
It looks correct.
> -d100 107
> 1116:0100 BA 05 40 B0 20 EE CD 20
>
> I tried using bxoff with and without loading killapm. Oh well, it sure would
> have been nice to report it worked for me.
I'm not surprised it doesn't work. Do you know which chipset you have?
Do you know how I can reverse the patch? It's very annoying having to
shutdown twice to close windows every time.
>
> > Note, although the hack works, it takes much longer to get back to the
> > command prompt than to it does to just use the "Restart" option with
> > FastReboot enabled. Too bad we can't just get windows to shutdown fast
> > without the reboot. This brings to mind a batch that could be used to
> > selectively set this registry key but IMO the FastReboot is faster so
why
> > bother.
>
> The reason why I bother is that I want to actually shut down windows -
even
> the "restart in MS-DOS mode" option seems to leave a piece of windows in
> memory. I think this is what the original poster (Outsider) wanted to do.
I understand. I was just posting my own point of view (why bother). But I
was not refering to the "Restart in DOS mode" option. I was refering to the
"Restart" option that performs a warm reboot being faster.
Without the win.com hack, with FastReboot disabled, and with killapm
installed, shutdown still powers the machine off. Sorry I was not clear, but
that was my meaning by "did not work". As for the reboot part, I was just
checking to see if it (killapm) would block the warm reboot and commenting
on that. Sorry about the confusion.
BTW, you said "Fast Shutdown". I know about "FastReboot", but is there also
a "FastShutdown" option available too? I tried setting the key but it don't
work so I assume it was just a typo.
>
> > No dice with BXOFF.COM either.
> >
> > Just to be sure I got it right, here is the contents of bxoff.com which
is 8
> > bytes.
>
> It looks correct.
>
> > -d100 107
> > 1116:0100 BA 05 40 B0 20 EE CD 20
> >
> > I tried using bxoff with and without loading killapm. Oh well, it sure
would
> > have been nice to report it worked for me.
>
> I'm not surprised it doesn't work. Do you know which chipset you have?
No I don't know which chipset I'm using.
Sorry I couldn't be of more help.
Thank-you aw and everyone else who responded to my question!
I now have Windows 4.1 configured to run just like Windows 3.1.
I even got the short-cut keys to work (thanks William). It is
a wonderful feeling, really. I can even close Windows and return
to real DOS with a single click. Ha! In your face, Bill Gates.
I guess you could restore the files it modified from your Win98 CD.
You can find the list of files at:
http://support.microsoft.com/support/kb/articles/Q239/8/87.ASP
> > > I downloaded the killapm tool and ran it prior to loading windows. It
> did
> > > not work for me (Celeron). The computer still rebooted when I used the
> > > restart option.
> >
> > Well of course. But what happened when you used the "Shut down" option?
> > If "Fast shutdown" is disabled, you should get back to DOS, even without
> > a hacked win.com.
> >
> > Win.com definitely uses the BIOS APM interface, but I'm pretty sure
> > the Windows kernel itself programs the hardware directly, so KILLAPM
> > won't stop it.
>
> Without the win.com hack, with FastReboot disabled, and with killapm
> installed, shutdown still powers the machine off. Sorry I was not clear, but
> that was my meaning by "did not work".
Well, that's really odd. Win.com should not be able to find APM when KILLAPM
is resident.
> As for the reboot part, I was just
> checking to see if it (killapm) would block the warm reboot and commenting
> on that. Sorry about the confusion.
>
> BTW, you said "Fast Shutdown". I know about "FastReboot", but is there also
> a "FastShutdown" option available too? I tried setting the key but it don't
> work so I assume it was just a typo.
No, there's no such option. MSCONFIG.EXE modifies the FastReboot value
when you change the "Fast Shutdown" setting. You can confirm this by
dumping the registry to a text file (regedit /e reg.txt) before and after
using MSCONFIG to change the Fast Shutdown option and comparing the text
files. (Of course, you'd have to restore your original MSCONFIG first.)
> > > -d100 107
> > > 1116:0100 BA 05 40 B0 20 EE CD 20
> > >
> > > I tried using bxoff with and without loading killapm. Oh well, it sure
> would
> > > have been nice to report it worked for me.
> >
> > I'm not surprised it doesn't work. Do you know which chipset you have?
>
> No I don't know which chipset I'm using.
You should be able to find out by using System Properties->Device Manager and
expanding the "System Devices" item. I have a device called "Intel 82443BX
Pentium II processor to PCI bridge".