Won't boot after using DOS startup

Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet

Post the contents of your autoexec.bat and config.sys here so we may have a look for
any offending lines. At this moment I suspect a real mode driver may be at fault.

--
Brian A.

Jack of all trades, Master of none.
One can never truly be a master as there is always more to learn.


"CGB" wrote in message
...
Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet

This may look like a long email but hopefully not. It's just got a couple
of file for your perusal you requested.

I'm wondering if there is an error in autoexec.bat or config.sys also and
have been exploring. Here's what I see for:

Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the problem
started

@ECHO OFF
@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

set path=c:\windows\command

LH c:\windows\command\mscdex /D:IDECD000 /L:M

LH c:\mouse\cloaking
c:\mouse\mouse ps2

SET PROMPT=$p$g
SET TEMP=C:\windows\TEMP
SET TMP=C:\windows\TEMP
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

c:\windows\smartdrv /q
REM
REM The following lines have been created by Windows. Do not modify them.
REM
C:
CD C:\WINDOWS
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

***************
Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no bak
files more recent)

@C:\PROGRA~1\NORTON~1\NORTON~2\NAVDX.EXE /Startup
REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\


@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\WINDOWS

************************************************** **************************
**************************************
************************************************** **************************
**************************************
Here is C:\Config.sys dated 6/10/04 about the time I began having trouble

DOS=SINGLE
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

REM Configure the PNP devices
device=c:\icu\dwcfgmg.sys

DOS=HIGH,UMB
buffershigh=10
fcbshigh=4
fileshigh=30
lastdrivehigh=Z
stackshigh=9,256
Device=C:\WINDOWS\Himem.Sys /testmemff

rem The following line will get you more ram, but no EMS
rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
Device=C:\WINDOWS\Emm386.exe RAM
DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000

***********
Here is C:\config.bak dated 6/3/98 (although there are a couple of
config files with several different extensions)

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE RAM

rem The below DOS CD ROM driver is not required to run Windows 95.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000

***********************************

Seems to have been some changes in the config.sys file and I'm wondering
about that. While I'm waiting for your reply I think I will save the
config.sys file to a floppy and rename the config.bak to config.sys and see
if it works. If it doesn't, I should be able to salvage this new, strange
looking config.sys from the floppy.

I notice you are suspicious of a real mode driver problem. I don't know
what that means but I see in the current config.sys it's trying to install
and OakCdRom.sys and in the config.bak file that device is "REM'd" out.
Also there are changes in the buffers and a couple of other lines.

Appreciate your interest and help.

Chet















"CGB" wrote in message
...
Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS
MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen
but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective
startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet

http://support.microsoft.com/default...b;EN-US;151717
Can't EXIT MS-DOS Mode
http://support.microsoft.com/?kbid=130448
Can't QUIT MS-DOS Mode
http://support.microsoft.com/default...;EN-US;q138996
Description of Restarting Computer in MS-DOS Mode

"Windows 98 Secrets" (Livingston/Straub), pgs 1068,1099, explains:

1. Direct Boot to DOS (Cold booted DOS)

a. Accessed through Boot Menu item, "Command Prompt Only".
b. Windows is not started.
c. Config.sys & Autoexec.bat are run, if present.
d. Ctrl-Alt-Del boots Windows. "WIN" loads Windows.

2. "Quit" to DOS (Re-started MS-DOS mode)

a. Accessed from "START, Shut Down, Re-start in MS-DOS mode", unless
"exit to DOS" pif was converted to "Warm Boot".
b. Accessed from any .pif that ISN'T a "Warm Boot" pif, as described
below.
c. Is NOT a warm boot; Config.sys & Autoexec.bat are NOT re-run, but are
honored to the extent Windows has not mussed the environment they set.
d. Dosstart.bat is run, if present.
e. "EXIT" reloads Windows (from 4K stub), also without a boot.
Ctrl-Alt-Del boots Windows.

3. Warm Booted MS-DOS mode ("Re-boot" to DOS)

a. Accessed from a "Warm Boot" .pif that IS BOTH checked "MS-DOS mode"
AND bolted "Specify a new MS-DOS configuration", in it's Properties,
Program tab, Advanced button.
b. Accessed from START button, if you've altered "exit to dos", as
described.
c. Does a warm boot, using Config.sys and Autoexec.bat as configured in
the pif. (The system files are renamed *.wos & the pif files are
extracted for the session.)
d. Dosstart.bat is NOT run.
e. "EXIT" restores the system Config.sys & Autoexec.bat & warm boots to
Windows. (Ctrl-Alt-Del & "WIN" should NOT be used.)

If you don't want to modify the "exit to dos" pif so that it does a warm
boot, then create a pif this way:

1. "START, Find, Command.com". (Probably in C:\ & C:\Windows).
2. "R-Clk either, Send to, Desktop (create shortcut)". It will be named
"MS-DOS Prompt".
3. R-Clk "MS-DOS Prompt" on the Desktop, & select Properties.
4. Click the Program tab & then the Advanced button.
5. Mark the MS-DOS Mode check box. Mark "Warn before entering..." as
desired.
6. For a "Warm Boot to DOS" pif, mark the "Specify a New MS-DOS
Configuration" button. If you do not do that, you will have a "Quit to
DOS" pif.
7. OK you're way out.

When you click that pif, you will either "warm boot" or "quit to DOS",
depending on what you did in step 6. If it's a warm boot, then the
Config.sys & Autoexec.bat inside the pif are the ones that will be in
effect in your DOS session. Alter them inside the pif as desired, before
clicking it.

Cquirke's WARNING: Because of system/.pif file switching, give a Warm
Boot .pif a chance to execute after clicking. If you click it a second
time before getting to DOS, you may lose your system Config.sys &
Autoexec.bat files.

http://cquirke.mvps.org/9x/doscompat.htm
There are even more DOS mentioned there.

"Select MS-DOS mode on this page", said Leboeuf.
http://www.colba.net/~hlebo49/winmode.htm


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"CGB" wrote in message
...
| This may look like a long email but hopefully not. It's just got a
couple
| of file for your perusal you requested.
|
| I'm wondering if there is an error in autoexec.bat or config.sys also
and
| have been exploring. Here's what I see for:
|
| Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the
problem
| started
|
| @ECHO OFF
| @ECHO OFF
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| set path=c:\windows\command
|
| LH c:\windows\command\mscdex /D:IDECD000 /L:M
|
| LH c:\mouse\cloaking
| c:\mouse\mouse ps2
|
| SET PROMPT=$p$g
| SET TEMP=C:\windows\TEMP
| SET TMP=C:\windows\TEMP
| SET BLASTER=A220 I7 D1 T2
| SET SNDSCAPE=C:\windows
|
| C:\EAPCI\APINIT.COM
|
| c:\windows\smartdrv /q
| REM
| REM The following lines have been created by Windows. Do not modify
them.
| REM
| C:
| CD C:\WINDOWS
| CALL C:\WINDOWS\COMMAND.COM
| C:\WINDOWS\WIN.COM /WX
|
| ***************
| Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no
bak
| files more recent)
|
| @C:\PROGRA~1\NORTON~1\NORTON~2\NAVDX.EXE /Startup
| REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\
|
|
| @ECHO OFF
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
| SET BLASTER=A220 I7 D1 T2
| SET SNDSCAPE=C:\WINDOWS
|
|
************************************************** **********************
****
| **************************************
|
************************************************** **********************
****
| **************************************
| Here is C:\Config.sys dated 6/10/04 about the time I began having
trouble
|
| DOS=SINGLE
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| REM Configure the PNP devices
| device=c:\icu\dwcfgmg.sys
|
| DOS=HIGH,UMB
| buffershigh=10
| fcbshigh=4
| fileshigh=30
| lastdrivehigh=Z
| stackshigh=9,256
| Device=C:\WINDOWS\Himem.Sys /testmemff
|
| rem The following line will get you more ram, but no EMS
| rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
| Device=C:\WINDOWS\Emm386.exe RAM
| DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000
|
| ***********
| Here is C:\config.bak dated 6/3/98 (although there are a couple of
| config files with several different extensions)
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| [common]
| dos=high,umb
| buffers=40
| device=c:\windows\himem.sys /testmemff
| DEVICE=C:\WINDOWS\EMM386.EXE RAM
|
| rem The below DOS CD ROM driver is not required to run Windows 95.
| rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000
|
| ***********************************
|
| Seems to have been some changes in the config.sys file and I'm
wondering
| about that. While I'm waiting for your reply I think I will save the
| config.sys file to a floppy and rename the config.bak to config.sys
and see
| if it works. If it doesn't, I should be able to salvage this new,
strange
| looking config.sys from the floppy.
|
| I notice you are suspicious of a real mode driver problem. I don't
know
| what that means but I see in the current config.sys it's trying to
install
| and OakCdRom.sys and in the config.bak file that device is "REM'd"
out.
| Also there are changes in the buffers and a couple of other lines.
|
| Appreciate your interest and help.
|
| Chet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| "CGB" wrote in message
| ...
| Things were running fine. I just wanted to see what happened if I
were to
| "restart in MS DOS mode." I clicked StartShut Down Restart in MS
DOS
| MODE
| and it shut down but when it restarted it hung up quickly when
something
| about PLUG and PLAY appeared on the screen. I waited about 30
minutes.
| Nothing would work except ctrl/alt/delete or powering off.
|
| I then tried rebooting with F8 pressed:
|
| "Command Prompt only" worked to get me to a command prompt, but
typing WIN
| or EXIT wouldn't get me into Windows
|
| Safe Mode got me into the safe mode of windows but then when I tried
| STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still
went
| into the DOS startup and hungup
|
| Starting in Safe Mode with Command prompt got me into a DOS-like
screen
| but
| it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
| HIMEM.SYS
| in Windows with file date of several years ago.
|
| I finally got it up enough to post this query by doing a "selective
| startup"
| and NOT loading anything that had anything to do with DOS.
|
| Scanned Windows with Norton Systemworks. It found no problem.
|
| I will now shut down and see what happens but posted this now
because at
| least now, I can get onto the newserver.
|
| Any thoughts, folks, assuming I can get back to read it !!!
|
| Thanks,
|
| Chet
|
|
|
|

Well, check whether you have a Config.wos & an Autoexec.wos. Look inside
the Config.wos. Does it begin... DOS=SINGLE. Then, your .wos are
useless. Delete them, & just do step (1) below. Post back for
instructions to fix the .bad files.

Otherwise...

(1) Rename your Config.sys & Autoexec.bat.
REN C:\Config.sys Config.bad
REN C:\Autoexec.bat Autoexec.bad

(2) Rename the two .wos...
REN C:\Config.wos Config.sys
REN C:\Autoexec.wos Autoexec.bat

That should do it. BUT, I think they look messy.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR

"CGB" wrote in message
...
| This may look like a long email but hopefully not. It's just got a
couple
| of file for your perusal you requested.
|
| I'm wondering if there is an error in autoexec.bat or config.sys also
and
| have been exploring. Here's what I see for:
|
| Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the
problem
| started
|
| @ECHO OFF
| @ECHO OFF
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| set path=c:\windows\command
|
| LH c:\windows\command\mscdex /D:IDECD000 /L:M
|
| LH c:\mouse\cloaking
| c:\mouse\mouse ps2
|
| SET PROMPT=$p$g
| SET TEMP=C:\windows\TEMP
| SET TMP=C:\windows\TEMP
| SET BLASTER=A220 I7 D1 T2
| SET SNDSCAPE=C:\windows
|
| C:\EAPCI\APINIT.COM
|
| c:\windows\smartdrv /q
| REM
| REM The following lines have been created by Windows. Do not modify
them.
| REM
| C:
| CD C:\WINDOWS
| CALL C:\WINDOWS\COMMAND.COM
| C:\WINDOWS\WIN.COM /WX
|
| ***************
| Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no
bak
| files more recent)
|
| @C:\PROGRA~1\NORTON~1\NORTON~2\NAVDX.EXE /Startup
| REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\
|
|
| @ECHO OFF
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| path C:\WINDOWS;C:\WINDOWS\COMMAND
| SET BLASTER=A220 I7 D1 T2
| SET SNDSCAPE=C:\WINDOWS
|
|
************************************************** **********************
****
| **************************************
|
************************************************** **********************
****
| **************************************
| Here is C:\Config.sys dated 6/10/04 about the time I began having
trouble
|
| DOS=SINGLE
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| REM Configure the PNP devices
| device=c:\icu\dwcfgmg.sys
|
| DOS=HIGH,UMB
| buffershigh=10
| fcbshigh=4
| fileshigh=30
| lastdrivehigh=Z
| stackshigh=9,256
| Device=C:\WINDOWS\Himem.Sys /testmemff
|
| rem The following line will get you more ram, but no EMS
| rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
| Device=C:\WINDOWS\Emm386.exe RAM
| DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000
|
| ***********
| Here is C:\config.bak dated 6/3/98 (although there are a couple of
| config files with several different extensions)
|
| REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT
|
| [common]
| dos=high,umb
| buffers=40
| device=c:\windows\himem.sys /testmemff
| DEVICE=C:\WINDOWS\EMM386.EXE RAM
|
| rem The below DOS CD ROM driver is not required to run Windows 95.
| rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000
|
| ***********************************
|
| Seems to have been some changes in the config.sys file and I'm
wondering
| about that. While I'm waiting for your reply I think I will save the
| config.sys file to a floppy and rename the config.bak to config.sys
and see
| if it works. If it doesn't, I should be able to salvage this new,
strange
| looking config.sys from the floppy.
|
| I notice you are suspicious of a real mode driver problem. I don't
know
| what that means but I see in the current config.sys it's trying to
install
| and OakCdRom.sys and in the config.bak file that device is "REM'd"
out.
| Also there are changes in the buffers and a couple of other lines.
|
| Appreciate your interest and help.
|
| Chet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| "CGB" wrote in message
| ...
| Things were running fine. I just wanted to see what happened if I
were to
| "restart in MS DOS mode." I clicked StartShut Down Restart in MS
DOS
| MODE
| and it shut down but when it restarted it hung up quickly when
something
| about PLUG and PLAY appeared on the screen. I waited about 30
minutes.
| Nothing would work except ctrl/alt/delete or powering off.
|
| I then tried rebooting with F8 pressed:
|
| "Command Prompt only" worked to get me to a command prompt, but
typing WIN
| or EXIT wouldn't get me into Windows
|
| Safe Mode got me into the safe mode of windows but then when I tried
| STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still
went
| into the DOS startup and hungup
|
| Starting in Safe Mode with Command prompt got me into a DOS-like
screen
| but
| it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
| HIMEM.SYS
| in Windows with file date of several years ago.
|
| I finally got it up enough to post this query by doing a "selective
| startup"
| and NOT loading anything that had anything to do with DOS.
|
| Scanned Windows with Norton Systemworks. It found no problem.
|
| I will now shut down and see what happens but posted this now
because at
| least now, I can get onto the newserver.
|
| Any thoughts, folks, assuming I can get back to read it !!!
|
| Thanks,
|
| Chet
|
|
|
|

Rename the autoexec.bat and config.sys files to autoexec.bad and config.bad

If you are working from a DOS boot, at the C: prompt, type the following and press
Enter after each line:
REN c:\autoexec.bat autoexec.bad
REN c:\config.sys config.bad

Then press Ctrl+Alt+Delete to reboot.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"CGB" wrote in message
...
This may look like a long email but hopefully not. It's just got a couple
of file for your perusal you requested.

I'm wondering if there is an error in autoexec.bat or config.sys also and
have been exploring. Here's what I see for:

Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the problem
started

@ECHO OFF
@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

set path=c:\windows\command

LH c:\windows\command\mscdex /D:IDECD000 /L:M

LH c:\mouse\cloaking
c:\mouse\mouse ps2

SET PROMPT=$p$g
SET TEMP=C:\windows\TEMP
SET TMP=C:\windows\TEMP
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

c:\windows\smartdrv /q
REM
REM The following lines have been created by Windows. Do not modify them.
REM
C:
CD C:\WINDOWS
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

***************
Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no bak
files more recent)

@C:\PROGRA~1\NORTON~1\NORTON~2\NAVDX.EXE /Startup
REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\


@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\WINDOWS

************************************************** **************************
**************************************
************************************************** **************************
**************************************
Here is C:\Config.sys dated 6/10/04 about the time I began having trouble

DOS=SINGLE
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

REM Configure the PNP devices
device=c:\icu\dwcfgmg.sys

DOS=HIGH,UMB
buffershigh=10
fcbshigh=4
fileshigh=30
lastdrivehigh=Z
stackshigh=9,256
Device=C:\WINDOWS\Himem.Sys /testmemff

rem The following line will get you more ram, but no EMS
rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
Device=C:\WINDOWS\Emm386.exe RAM
DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000

***********
Here is C:\config.bak dated 6/3/98 (although there are a couple of
config files with several different extensions)

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE RAM

rem The below DOS CD ROM driver is not required to run Windows 95.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000

***********************************

Seems to have been some changes in the config.sys file and I'm wondering
about that. While I'm waiting for your reply I think I will save the
config.sys file to a floppy and rename the config.bak to config.sys and see
if it works. If it doesn't, I should be able to salvage this new, strange
looking config.sys from the floppy.

I notice you are suspicious of a real mode driver problem. I don't know
what that means but I see in the current config.sys it's trying to install
and OakCdRom.sys and in the config.bak file that device is "REM'd" out.
Also there are changes in the buffers and a couple of other lines.

Appreciate your interest and help.

Chet















"CGB" wrote in message
...
Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS
MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen
but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective
startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet

In the config.sys I believe the problem is with the line:
device=c:\icu\dwcfgmg.sys

Remark this line out by typing REM and press the spacebar in front of it so it looks
like:
REM device=c:\icu\dwcfgmg.sys

I will leave this next choice up to you. In the autoexec.bat these 3 lines also have
to do with the SB DOS emulation. If you do not use sound in DOS you don't them
loading and can REM them as well.
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

Save and reboot.

That line has to do with the SoundBlaster and is an alternate PnP manager that is a
known problem.
From: http://www.daqarta.com/atn-sb16.htm

"quote"
The normal Creative installation process should have provided a DOS Configuration
Manager called CTCM.EXE, which will have been inserted into your CONFIG.SYS or
AUTOEXEC.BAT file. (DWCFGMG.SYS is an alternate PnP manager that may be used in
CONFIG.SYS, but it uses 1700 bytes of low DOS memory whereas CTCM does not, and
doesn't set the BLASTER string in the DOS environment.)

If you have a Windows 9x system, it should be in your C:\WINDOWS\DOSSTART.BAT file.
This is the file that is supposed to perform tasks similar to AUTOEXEC.BAT when you
select 'Start ... Shut Down ... Restart in MS-DOS Mode'.

Some newer Creative CD-ROMs don't install CTCM.EXE on a Windows 9x system. Instead,
each time Windows performs the 'Restart in MS-DOS Mode', it runs CTPNP.EXE. This will
refuse to configure your board, reporting that your PnP configuration has changed and
instructing you to run Windows again... endlessly.

"end quote"

If you still have problems, post back with any results on what you tried and any
error messages if any.


--
Brian A.

Jack of all trades, Master of none.
One can never truly be a master as there is always more to learn.


"CGB" wrote in message
...
This may look like a long email but hopefully not. It's just got a couple
of file for your perusal you requested.

I'm wondering if there is an error in autoexec.bat or config.sys also and
have been exploring. Here's what I see for:

Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the problem
started

@ECHO OFF
@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

set path=c:\windows\command

LH c:\windows\command\mscdex /D:IDECD000 /L:M

LH c:\mouse\cloaking
c:\mouse\mouse ps2

SET PROMPT=$p$g
SET TEMP=C:\windows\TEMP
SET TMP=C:\windows\TEMP
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

c:\windows\smartdrv /q
REM
REM The following lines have been created by Windows. Do not modify them.
REM
C:
CD C:\WINDOWS
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

***************
Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no bak
files more recent)

@C:\PROGRA~1\NORTON~1\NORTON~2\NAVDX.EXE /Startup
REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\


@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\WINDOWS

************************************************** **************************
**************************************
************************************************** **************************
**************************************
Here is C:\Config.sys dated 6/10/04 about the time I began having trouble

DOS=SINGLE
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

REM Configure the PNP devices
device=c:\icu\dwcfgmg.sys

DOS=HIGH,UMB
buffershigh=10
fcbshigh=4
fileshigh=30
lastdrivehigh=Z
stackshigh=9,256
Device=C:\WINDOWS\Himem.Sys /testmemff

rem The following line will get you more ram, but no EMS
rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
Device=C:\WINDOWS\Emm386.exe RAM
DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000

***********
Here is C:\config.bak dated 6/3/98 (although there are a couple of
config files with several different extensions)

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE RAM

rem The below DOS CD ROM driver is not required to run Windows 95.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000

***********************************

Seems to have been some changes in the config.sys file and I'm wondering
about that. While I'm waiting for your reply I think I will save the
config.sys file to a floppy and rename the config.bak to config.sys and see
if it works. If it doesn't, I should be able to salvage this new, strange
looking config.sys from the floppy.

I notice you are suspicious of a real mode driver problem. I don't know
what that means but I see in the current config.sys it's trying to install
and OakCdRom.sys and in the config.bak file that device is "REM'd" out.
Also there are changes in the buffers and a couple of other lines.

Appreciate your interest and help.

Chet















"CGB" wrote in message
...
Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS
MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen
but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective
startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet

On Thu, 10 Jun 2004 20:27:08 -0400, "CGB" wrote:

This may look like a long email but hopefully not. It's just got a couple
of file for your perusal you requested.

I'm wondering if there is an error in autoexec.bat or config.sys also and
have been exploring. Here's what I see for:

Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the problem
started

@ECHO OFF
@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

set path=c:\windows\command

LH c:\windows\command\mscdex /D:IDECD000 /L:M

LH c:\mouse\cloaking
c:\mouse\mouse ps2

SET PROMPT=$p$g
SET TEMP=C:\windows\TEMP
SET TMP=C:\windows\TEMP
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

c:\windows\smartdrv /q
REM
REM The following lines have been created by Windows. Do not modify them.
REM
C:
CD C:\WINDOWS ----Remove this line
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

***************
Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no bak
files more recent)

/Startup
REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\


@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\WINDOWS

************************************************* ***************************
**************************************
************************************************* ***************************
**************************************
Here is C:\Config.sys dated 6/10/04 about the time I began having trouble

DOS=SINGLE
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

REM Configure the PNP devices
device=c:\icu\dwcfgmg.sys

DOS=HIGH,UMB
buffershigh=10
fcbshigh=4
fileshigh=30
lastdrivehigh=Z
stackshigh=9,256
Device=C:\WINDOWS\Himem.Sys /testmemff

rem The following line will get you more ram, but no EMS
rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
Device=C:\WINDOWS\Emm386.exe RAM
DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000

***********
Here is C:\config.bak dated 6/3/98 (although there are a couple of
config files with several different extensions)

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE RAM

rem The below DOS CD ROM driver is not required to run Windows 95.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000

***********************************

Seems to have been some changes in the config.sys file and I'm wondering
about that. While I'm waiting for your reply I think I will save the
config.sys file to a floppy and rename the config.bak to config.sys and see
if it works. If it doesn't, I should be able to salvage this new, strange
looking config.sys from the floppy.

I notice you are suspicious of a real mode driver problem. I don't know
what that means but I see in the current config.sys it's trying to install
and OakCdRom.sys and in the config.bak file that device is "REM'd" out.
Also there are changes in the buffers and a couple of other lines.

Appreciate your interest and help.

Chet

Chet,

Renaming the config.sys and autoexec.bat files will probably get you
into windows but you have lines in those files that you need so try
this: The Restart to Dos Mode added lines to those two files.

REM these 4 lines from the Autoexec.bat file.
C:
CD C:\WINDOWS
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX (note: this line renames these two files and
restores your original ones, but it does not belong in here.. it
should be used only once and is probably too late to use it from the
command line. but worth a try)

REM this line from the Config.sys file:
DOS=SINGLE (note: this line prevents booting to Windows)

Reboot.

If no help boot to Dos Safe Mode and enter Win /wx.

Let us know.

Regards,

Bill Watt
Computer Help and Information http://home.epix.net/~bwatt/

Bill, I see no lines in either file that he needs to have, in Windows. The entries
are strictly for a DOS-mode boot.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"Bill Watt" wrote in message
...
On Thu, 10 Jun 2004 20:27:08 -0400, "CGB" wrote:

This may look like a long email but hopefully not. It's just got a couple
of file for your perusal you requested.

I'm wondering if there is an error in autoexec.bat or config.sys also and
have been exploring. Here's what I see for:

Autoexec.bat in C:\ dated 6/10/04 at 3:59, about the time the problem
started

@ECHO OFF
@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

set path=c:\windows\command

LH c:\windows\command\mscdex /D:IDECD000 /L:M

LH c:\mouse\cloaking
c:\mouse\mouse ps2

SET PROMPT=$p$g
SET TEMP=C:\windows\TEMP
SET TMP=C:\windows\TEMP
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\windows

C:\EAPCI\APINIT.COM

c:\windows\smartdrv /q
REM
REM The following lines have been created by Windows. Do not modify them.
REM
C:
CD C:\WINDOWS ----Remove this line
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX

***************
Here is C:\autoexec.bak dated 11/6/98 (when I bought the computer, no bak
files more recent)

/Startup
REM C:\PROGRA~1\NETWOR~1\MCAFEE~1\SCAN.EXE C:\


@ECHO OFF
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

path C:\WINDOWS;C:\WINDOWS\COMMAND
SET BLASTER=A220 I7 D1 T2
SET SNDSCAPE=C:\WINDOWS

************************************************* ***************************
**************************************
************************************************* ***************************
**************************************
Here is C:\Config.sys dated 6/10/04 about the time I began having trouble

DOS=SINGLE
REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

REM Configure the PNP devices
device=c:\icu\dwcfgmg.sys

DOS=HIGH,UMB
buffershigh=10
fcbshigh=4
fileshigh=30
lastdrivehigh=Z
stackshigh=9,256
Device=C:\WINDOWS\Himem.Sys /testmemff

rem The following line will get you more ram, but no EMS
rem Device=C:\WINDOWS\Emm386.exe RAM NOEMS
Device=C:\WINDOWS\Emm386.exe RAM
DEVICEHIGH=c:\cdrom\OakCDRom.SYS /D:IDECD000

***********
Here is C:\config.bak dated 6/3/98 (although there are a couple of
config files with several different extensions)

REM To make a DOS Boot Diskette; See the file C:\DOSBOOT\DOSBOOT.TXT

[common]
dos=high,umb
buffers=40
device=c:\windows\himem.sys /testmemff
DEVICE=C:\WINDOWS\EMM386.EXE RAM

rem The below DOS CD ROM driver is not required to run Windows 95.
rem DEVICE=c:\cdrom\OakCdRom.SYS /D:IDECD000

***********************************

Seems to have been some changes in the config.sys file and I'm wondering
about that. While I'm waiting for your reply I think I will save the
config.sys file to a floppy and rename the config.bak to config.sys and see
if it works. If it doesn't, I should be able to salvage this new, strange
looking config.sys from the floppy.

I notice you are suspicious of a real mode driver problem. I don't know
what that means but I see in the current config.sys it's trying to install
and OakCdRom.sys and in the config.bak file that device is "REM'd" out.
Also there are changes in the buffers and a couple of other lines.

Appreciate your interest and help.

Chet

Chet,

Renaming the config.sys and autoexec.bat files will probably get you
into windows but you have lines in those files that you need so try
this: The Restart to Dos Mode added lines to those two files.

REM these 4 lines from the Autoexec.bat file.
C:
CD C:\WINDOWS
CALL C:\WINDOWS\COMMAND.COM
C:\WINDOWS\WIN.COM /WX (note: this line renames these two files and
restores your original ones, but it does not belong in here.. it
should be used only once and is probably too late to use it from the
command line. but worth a try)

REM this line from the Config.sys file:
DOS=SINGLE (note: this line prevents booting to Windows)

Reboot.

If no help boot to Dos Safe Mode and enter Win /wx.

Let us know.

Regards,

Bill Watt
Computer Help and Information http://home.epix.net/~bwatt/

First, thank you all for quick, excellent responses.

With the help of the various suggestions I looked to the autoexec and config
files as the problem. After looking around a lot I opted to shut down and
reboot into a command prompt before replacing those two files with two I had
saved as backups. When I rebooted, I ended up in a DOS appearing screen
with C:\Windows. Different! I tried typing in "Win" and it said it would
have to reboot to Windows, I said OK and it booted fine. I checked and the
autoexec and config.sys files had been returned to the normal, pre-crash
ones!!! Can't figure that out, but I'll take it.

All's well that ends well. Now to try shutting down and "restart in MS DOS
mode" once again...........

Thanks to all.

Chet


"CGB" wrote in message
...
Things were running fine. I just wanted to see what happened if I were to
"restart in MS DOS mode." I clicked StartShut Down Restart in MS DOS
MODE
and it shut down but when it restarted it hung up quickly when something
about PLUG and PLAY appeared on the screen. I waited about 30 minutes.
Nothing would work except ctrl/alt/delete or powering off.

I then tried rebooting with F8 pressed:

"Command Prompt only" worked to get me to a command prompt, but typing WIN
or EXIT wouldn't get me into Windows

Safe Mode got me into the safe mode of windows but then when I tried
STARTSHUTDOWNSHUTDOWN, it shut down but on next restart, it still went
into the DOS startup and hungup

Starting in Safe Mode with Command prompt got me into a DOS-like screen
but
it said it couldn't find HIMEM.SYS when I typed WIN. A DIR showed
HIMEM.SYS
in Windows with file date of several years ago.

I finally got it up enough to post this query by doing a "selective
startup"
and NOT loading anything that had anything to do with DOS.

Scanned Windows with Norton Systemworks. It found no problem.

I will now shut down and see what happens but posted this now because at
least now, I can get onto the newserver.

Any thoughts, folks, assuming I can get back to read it !!!

Thanks,

Chet