When I start up in DOS it has two messages: 1. Device
driver not found: 'IDECDOO1' no valid cdrom device drivers
selected. 2. Mouse driver, version 9.11 Already
installed Logitech mouse driver. Another mouse driver is
present in memory this driver cannot be loaded. Please
remove the existing mouse driver then load this mouse
driver.

As for the first I have a dvdrom drive that came with the
computer on drive E that is working fine. And I have an
external cdrw drive on drive F that is also working. Here
is a copy of my C:\CONFIG.SYS:
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,AUTO,UMB
rem - By Windows Setup -
DEVICEHIGH=C:\WINDOWS\SYSTEM\CPQIDECD.SYS /D:IDECD001
FILESHIGH=40
BUFFERSHIGH=20,4
Is there a problem with the destination /D:IDECD001, since
the drive should be E?

As for the mouse, I am using a cordless Logitech mouse.
There is only one device listed in the device manager
(TrackMan13 PS/2). I removed this and restarted the
computer and it reinstalled itself. I went back to dos
and the prompt was still there. When it says "Another
mouse driver is present in memory this driver cannot be
loaded" is it referring to something in the sytem.ini? In
the system.ini under [boot] there is mouse.drv=Imouse.drv
under [boot description] mouse.drv=Logitech and under
[386Enh] mouse=*vmouse.
Thanks for the help.

Rename your Config.sys file to Config.bak, then rename the Autoexec.bat file
to Autoexec.bak (you'll find these by using Explorer and viewing the C:
drive, but you may need to turn on the option to view hidden or system
files) then restart the computer. If all works well then leave the files
renamed.

--
Richard G. Harper [MVP Win9x] rgharper@email.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"ollyollyoxenfree" <anonymous@discussions.microsoft.com> wrote in message
news:138e701c3f8a4$7ea7d880$a101280a@phx.gbl...

I renamed the two files. But before I did I copied and pasted them to a different folder. Then I restarted in MS-DOS and got the same errors. Then I started up in Windows and ran sysedit and got these messages: C:\CONFIG.SYS can not open this file. C:\AUTOEXE.BAT can not open this file. Why did you you have me rename these and what was that supposed to do?

"ollyollyoxenfree" <anonymous@discussions.microsoft.com> wrote in message
news:138e701c3f8a4$7ea7d880$a101280a@phx.gbl...

Yes. Edit AUTOEXEC.BAT so the
CD system file points to the correct drive.

Windows drivers for the mouse are
irrelevant to a DOS boot. You can use
only DOS drivers (if they exist for your mouse.)

--
Don Phillipson
Carlsbad Springs (Ottawa, Canada)

Renaming the files was supposed to get them out of the way so that their
unneeded real-mode drivers would not be loaded. However, looking at your
later comments, I'm not sure I understand when and where this problem is
happening and what exactly the problem is. Are you getting these errors
when you start up in MS-DOS Mode, or when you Restart in MS-DOS Mode?

--
Richard G. Harper [MVP Win9x] rgharper@email.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"ollyollyoxenfree" <anonymous@discussions.microsoft.com> wrote in message
news:C5B22D93-D00B-4B20-B8AF-8A74AC547023@microsoft.com...
I started up in Windows and ran sysedit and got these messages:
C:\CONFIG.SYS can not open this file. C:\AUTOEXE.BAT can not open this
file. Why did you you have me rename these and what was that supposed to
do?

On Sat, 21 Feb 2004 09:59:47 -0800, "ollyollyoxenfree"
<anonymous@discussions.microsoft.com> wrote:

The problem seems to be that Windows has remmed out your driver in
the Config.sys file. This line:
rem - By Windows Setup - DEVICEHIGH=C:\WINDOWS\SYSTEM\CPQIDECD.SYS
/D:IDECD001
Change it to: (remove rem - By Windows Setup -)
DEVICEHIGH=C:\WINDOWS\SYSTEM\CPQIDECD.SYS /D:IDECD001

Your Config.sys and autoexec.bat CDrom entries must end with the
same thing.
Here's mine and my 2 CDroms are F: and G:
Autoexec.bat:
LH C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSCD001
Config.sys:
DEVICEHIGH=C:\windows\command\Oakcdrom.sys /D:MSCD001

Make sure both lines in both files end with the same thing with
/D:IDECD001 or visa-versa. Include the /D:

Those two lines I show above setup both my Cdroms and one is a
burner. I can access both in Dos also. If you still have the problem
try remming your lines With REM and a space and add the two lines
above. Both the MSCDEX.EXE and Oakcdrom.sys drivers are included
with Windows and work on most CDroms, but not all.

Regards,

Bill Watt
Computer Help and Information http://home.epix.net/~bwatt/
E-mail address is fake to minimize spam.

On Sat, 21 Feb 2004 09:59:47 -0800, "ollyollyoxenfree"
<anonymous@discussions.microsoft.com> wrote:


The /D operand specifies the driver name that also must appear
in the autoexec.bat "mscdex" line.

To specify a specific drive, use the /L operand.

Jack

Richard,

Just a thought...
Perhaps he's using a DOS shortcut and has modified the pif under Properties/Advance tab?

All the best,
--
George Aker aka SG
NOTE: Please post to the group...email is invalid.





"Richard G. Harper" <rgharper@email.com> wrote in message news:e5XCGqM#DHA.3900@tk2msftngp13.phx.gbl...

I'm beginning to wonder also.

--
Richard G. Harper [MVP Win9x] rgharper@email.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"SG" <48249333@naxs.com> wrote in message
news:u7MFl1g%23DHA.3232@TK2MSFTNGP10.phx.gbl...
Richard,

Just a thought...
Perhaps he's using a DOS shortcut and has modified the pif under
Properties/Advance tab?

All the best,
--
George Aker aka SG
NOTE: Please post to the group...email is invalid.





"Richard G. Harper" <rgharper@email.com> wrote in message
news:e5XCGqM#DHA.3900@tk2msftngp13.phx.gbl...

To answer Richard G. Harper’s question, it was when I was restarting in MS-DOS Mode. And to answer SG’s question, no I wasn’t making any changes in the pif. Well this is what I finally did. I took out the rem - By Windows Setup - in front of
DEVICEHIGH=C:\WINDOWS\SYSTEM\CPQIDECD.SYS /D:IDECD001 in th
C:\CONFIG.SYS

Then I added this line to the C:\AUTOEXEC.BA
LH C:\WINDOWS\COMMAND\MSCDEX /D:IDECD001 /L:
The E, at the end, being the drive letter. Now if I have a need I can use the CD-ROM in MS-DOS. I referenced these websites
http://www.computerhope.com/ac.ht
http://www.dosgamesarchive.com/newsltr/news12.ph
http://www.pcnineoneone.com/howto/cdboot1.htm

The only question I now have is could someone better explain the third to last paragraph of the last site I listed. It mentions that MSCDEX.EXE should not load with Windows 9x. Why is that? The above configuration is how my computer is now and I haven’t had any problems booting into Windows with the line not remmed out

As far as the mouse goes I referenced this site
http://www.computerhope.com/issues/ch000007.ht

but mainly this site

http://www.logitech.com/index.cfm/su...l ldocuments=

I went into the C:\WINDOWS\dosstart.bat and found this

set mouse=c:\compaq\imous
lh c:\compaq\imouse\imouse.co

So I changed it to this

C:\WINDOWS\dosstart.ba
rem set mouse=c:\compaq\imous
rem lh c:\compaq\imouse\imouse.co
lh C:\cpqdrv\Logitech\Mouse.ex

And now I have access to the mouse in MS-DOS. If anyone can shed the light on
“MSCDEX.EXE� for me that would be great
Thanks for the input

You may be interested in reading this article.

Command-Line Switches for MSCDEX.EXE
http://support.microsoft.com/?kbid=87165
--

You system configuration may required the file, in your case it's working
with it so let it be.

Others may give you other reasons more appropriate to your situation.

Henri Leboeuf
Web page: http://www.generation.net/~hleboeuf/index.htm


"ollyollyoxenfree" <anonymous@discussions.microsoft.com> wrote in message
news:6BD6C8EA-B675-4DFD-8905-D30B17F9779D@microsoft.com...
the pif. Well this is what I finally did. I took out the rem - By Windows
Setup - in front of
should not load with Windows 9x. Why is that? The above configuration is
how my computer is now and I haven’t had any problems booting into Windows
with the line not remmed out.

The file MSCDEX.EXE I added in the C:\AUTOEXEC.BAT is really located on my C drive (C:\WINDOWS\COMMAND\MSCDEX). I already read that article and it doesn't explain why MSCDEX.EXE shouldn't load with Windows. And that is really the only question I have left. Everything seems to be working fine and I'm not messing with it anymore. I'm just curious about that one site I referred to in my previous message that said MSCDEX.EXE should not load with Windows 9x
Thanks for the input anywa

On Sat, 28 Feb 2004 15:01:06 -0800, "ollyollyoxenfree"

Win95 and Win98 can run CD-ROM drives in one of two ways:

1) Natively, using inbuilt 32-bit drivers
2) In DOS Compatibility Mode, using add-on real-mode drivers

Method (1) is always preferable for performance and other reasons.

The real-mode drivers referred to in (2) are a device-orientated .SYS
driver typically loaded via C:\Config.sys, and a OS-level MSCDEX
driver typically loaded via C:\Autoexec.bat

When these real-mode drivers are present, the CD drive can be accessed
whether the OS is running "properly" or in DOS Compatability Mode.

Where these real-mode drivers are not present. the CD drive will
vanish from the system unless in DOS Compatibility Mode (DCM).

On the face of it, it may seem a good idea to have these drivers under
Windows, in case the system should fall into DCM. In practice, not:
- if in DCM, you want to know about that and *fix* it
- the drivers may themselves cause DCM if not ignored by Windows
- Auto-Insert Notification doesn't work in DCM
- drive letter mis-mappings and duplicates (MSCDEx /L: parameter)

Better practice is to set up "Exit to DOS.pif" to "Specify a new..."
and then load trhe real mode drivers *there*. That means DOS mode
gets CD-ROM support, while Windows stays clean.

See http://users.iafrica.com/c/cq/cquirke/doscompat.htm on DOS
Compatibility Mode. Not all causes are innocuous!

How do I set up the "Exit to DOS.pif"? What should be there? And how should my config.sys, autoexec.bat, and dosstart.bat read? This is how they are now
Under properties, program tab, advanced tab (of exit to dos), MS-DOS mode is checked and Use current MS-DOS configuration is checked

config.sys
DEVICE=C:\WINDOWS\HIMEM.SY
DOS=HIGH,AUTO,UM
DEVICE=C:\WINDOWS\EMM386.EXE NOEM
DEVICEHIGH=C:\WINDOWS\SYSTEM\CPQIDECD.SYS /D:IDECD00
FILESHIGH=4
BUFFERSHIGH=20,

autoexec.bat
@ECHO OF
SET BLASTER=A220 I5 D
LH C:\WINDOWS\COMMAND\DOSKE
LH C:\WINDOWS\COMMAND\MSCDEX /D:IDECD001 /L:

dosstart.bat
@echo of
lh c:\windows\command\mscdex.exe /d:idecd001 /m:1
rem set mouse=c:\compaq\imous
rem lh c:\compaq\imouse\imouse.co

C:\Program Files\Logitech\MouseWare\mouse.ex

Specifically what changes do you suggest I make
Thanks

On Tue, 2 Mar 2004 16:11:08 -0800, "ollyollyoxenfree"

Settings that allow DOS mode to function effectively for what you need
to there. That answer is less fatuous than it sounds.

Chances are, your reasons for being in DOS mode will be so varied that
one setup can't fit all needs.

For example, you may want to run DOS applications in an optimal
environment that has to be outside Windows for some reason. At the
other extreme, you may need the cleanest possible boot for the
greatest safety when evacuating a sick HD or doing diagnostics. In
between, you may have troublesome apps that need EMS, can't abide by
Emm386.exe or disk caching, etc. etc. etc.

Fortunately, the Config.sys [Menu] system addresses this, linking via
%Config% to Autoexec.bat and beyond. The Include statement allows
system-specific items to be localised for re-use.

Rather than throw links to the syntax involved, I'll hope these things
will explain themselves in the exaples that follow.

Examples to follow, which I'll build from yours.



was set up during the Windows boot process. That's likely to be less
than ideal; something that can only be partially addressed through
the DOSStart.bat that will run on the way to DOS mode.

I'd change that to "Specify a new..." so that the private Config.sys
and Autoexec.bat within the .pif light up and go into effect. Under
these circumstances, DOSStart.bat is ignored completely.

Here's how a good private CONFIG.SYS might look:


[Menu]
MenuItem=Def,DOS Mode; default startup
MenuItem=EMS,DOS Mode; with EMS support
MenuItem=Max,DOS Mode; maximum DPMS memory
MenuItem=Lean,DOS Mode; lean, no Emm386 or SmartDrv
MenuItem=Debug,DOS Mode; debug, no extra file loads or writes
MenuDefault=Def,10
; A ;comment to say the "10" in line above is timeout in seconds

[NoEMS]
Device=C:\Windows\HiMem.sys
DeviceHigh=C:\Windows\Emm386.exe NoEMS
DOS=High,UMB

[YesEMS]
Device=C:\Windows\HiMem.sys
DeviceHigh=C:\Windows\Emm386.exe RAM
DOS=High,UMB

[HiMem]
Device=C:\Windows\HiMem.sys
DOS=High

[CDROM]
DeviceHigh=C:\Windows\System\CpqIDECD.sys /D:IDECDROM
; > Generic systems can un-;comment this instead of above
; DeviceHigh=C:\Windows\Command\EBD\OakCDROM.sys /D:IDECDROM
; <

[Regional]
; Enter any regional settings here if required

[Def]
Include NoEMS
Include CDROM
Include Regional

[EMS]
Include YesEMS
Include CDROM
Include Regional

[Max]
Include NoEMS
Include CDROM
Include Regional

[Lean]
Include HiMem
Include CDROM
Include Regional

[Debug]
DOS=NoAuto


A good matching private autoexec.bat may look like:


@Echo Off
Set Blaster=A220 I5 D1 T4
:: This ::comment says other Set statements go here
Echo Booting DOS mode configuration "%Config%"...

GoTo %Config%

ef
LH MSCDEx /D:IDECDROM
LH SmartDrv A- B- /X
:: Your regional stuff goes here
LH Mouse
LH DOSKey /Insert
: Your choice of front-end menu, if any
GoTo End

:EMS
Prompt [EMS] $p$g
LH MSCDEx /D:IDECDROM
LH SmartDrv A- B- /X
:: Your regional stuff goes here
LH Mouse
LH DOSKey /Insert
:: Your choice of front-end menu, if any
GoTo End

:Max
Prompt [Max] $p$g
LH MSCDEx /D:IDECDROM
LH SmartDrv A- B- /X 128
:: Your regional stuff goes here
LH Mouse
:: Your choice of front-end menu, if any
GoTo End

:Lean
Prompt [Lean] $p$g
LH MSCDEx /D:IDECDROM
:: Your regional stuff goes here
LH Mouse
:: Your choice of front-end menu, if any
GoTo End

ebug
Prompt [debug] $p$g
Echo.
Echo Tip: Lock before you hack the HD!
GoTo End

:End
Echo.
Echo This is DOS Mode. The system will stay here even after reset.
Echo To restart Windows, enter EXIT command (don't use "Win")
Echo.


Because you are using "Specify...", DOSStart.bat doesn't matter

That wouldn't work, because in DOS Mode, you can't see LFNs even if
you did enclose them in spaces. To make the above generic files work,
copy that MOUSE.EXE to C:\Windows\Command



a match to see if what you are standing in is water or petrol.

What do you mean by regional settings? I think we are on the same track and I don’t think it applies to me.

You used “IDECDROM� instead of “IDECD001� any reason? I know the value has to be 8 characters and has to be the same in config.sys and autoexebat.

You used “Set Blaster=A220 I5 D1 T4� instead of “Set Blaster=A220 I5 D1�. What is the reason for the “T4�?

I am not aware of any front-end menu on my pc. These are programs that gamers and programmers ues, right?

What do you mean by “Lock before you hack the HD�?

I copied the MOUSE.EXE to C:\Windows\Command. There is nothing further I have to do with it, right?

When I click on the Configuration button in the Advanced Program Settings, the only box that is checked is Expanded Memory (EMS). Do any of the other three boxes need to be checked?

Also should I rem out or remove the lines that I added to CONFIG.SYS, AUTOEXEC.BAT, and DOSSTART.BAT? I know that mentioned whenyou are using "Specify...", DOSStart.bat doesn't matter. So I might as well remove that one

Well this is what I edited your example down to, would appreciate your opinion. Notice I changed your IDECDROM to my original IDECD001, but I will change if needed. I will wait until I get your input before making these changes

[Menu
MenuItem=Def,DOS Mode; default startu
MenuItem=EMS,DOS Mode; with EMS suppor
MenuItem=Max,DOS Mode; maximum DPMS memor
MenuItem=Lean,DOS Mode; lean, no Emm386 or SmartDr
MenuItem=Debug,DOS Mode; debug, no extra file loads or write
MenuDefault=Def,1

[NoEMS
Device=C:\Windows\HiMem.sy
DeviceHigh=C:\Windows\Emm386.exe NoEM
DOS=High,UM

[YesEMS
Device=C:\Windows\HiMem.sy
DeviceHigh=C:\Windows\Emm386.exe RA
DOS=High,UM

[HiMem
Device=C:\Windows\HiMem.sy
DOS=Hig

[CDROM
DeviceHigh=C:\Windows\System\CpqIDECD.sys /D: IDECD00

[Def
Include NoEM
Include CDRO

[EMS
Include YesEM
Include CDRO

[Max
Include NoEM
Include CDRO

[Lean
Include HiMe
Include CDRO

[Debug
DOS=NoAut

A good matching private autoexec.bat may look like

@Echo Of
Set Blaster=A220 I5 D1 T
Echo Booting DOS mode configuration "%Config%"..

GoTo %Config

e
LH MSCDEx /D: IDECD00
LH SmartDrv A- B- /
LH Mous
LH DOSKey
GoTo En

:EM
Prompt [EMS] $p$
LH MSCDEx /D: IDECD00
LH SmartDrv A- B- /
LH Mous
LH DOSKey
GoTo En

:Ma
Prompt [Max] $p$
LH MSCDEx /D: IDECD00
LH SmartDrv A- B- /X 12
LH Mous
GoTo En

:Lea
Prompt [Lean] $p$
LH MSCDEx /D: IDECD00
LH Mous
GoTo En

ebu
Prompt [debug] $p$
Echo
Echo Tip: Lock before you hack the HD
GoTo En

:En
Echo
Echo This is DOS Mode. The system will stay here even after reset
Echo To restart Windows, enter EXIT command (don't use "Win"
Echo

This is what was already there when I clicked on “specify a new MS-DOS configuration�

CONFIG.SYS for MS-DOS mode
DOS=HIGH,UM
Device=C:\WINDOWS\Himem.Sy

AUTOEXEC.BAT for MS-DOS mode
SET TMP=c:\windows\TEM
SET TEMP=C:\windows\TEM
SET PROMPT=$p$
SET winbootdir=C:\WINDOW
SET PATH=C:\WINDOWS;c:\windows;c:\windows\COMMAN
SET BLASTER=A220 I5 D

Thanks for the help

On Sat, 6 Mar 2004 09:56:06 -0800, "ollyollyoxenfree"
<anonymous@discussions.microsoft.com> wrote:

There are generally two kinds; those that change the DOS character
set, and those that change the keyboard layout. For example, a German
keyboard swaps Z and Y keys, a UK keyboard has " rather than @ when
you shift the 2 key, and so forth.

These things are set via statements such as "country" in Config.sys
and other stuff there and in Autoexec.bat - folks from affected
regions can tell you more, but here we use US keyboards, so we don't
have to fiddle to get them working correctly so I'm out of practice!

Partly to illustrate the arbitrariness of the value - it can be just
about anything you like. It doesn't have to be 8 characters either
(that's the max length) but whatever you use will become a reserved
device name throughout the system - that's why you don't want a name
like "README" else you'd never be able to save a README file :-)

The name you use in Config.sys must match that in Autoexec.bat, as
this is what links the .SYS driver to MSCDEx.

Syntax of the conventional Blaster value:

Axxx = base port address
Ix = IRQ
Dx = (low) DMA channel
Hx = High DMA channel (not applicable to SB Pro or older)
Tx = Type; I think 4 = SB Pro 2, 6 = SB 16, 7 = AWE32

Most generics emulate SB Pro 2 but not SB16, even if they are 16-bit
sound cards. Forcing T4 may stop some over-ambitious games from going
off the rails by assuming the card's SB16-compatible.

Yes - I use DOS Shell (it's a great menu, with user-writable F1 Help
that you can use to offer game keyboard tips etc.) but others may use
PC Tools, Norton Commander, or anything else that's easier than the
C:> prompt. Even something tacky like this:

@Echo Off
CLS
Type Menu.txt
Echo.
Echo Enter the number of the program you want to run
Echo.

1.bat

2.bat

3.bat

etc.

If you're in Debug mode, chances are you're there to do some low-level
hairy stuff (e.g. UnErase) that Win9x's DOS mode may object to.
Rather than allowing access that could break Long File Names, Win9x
DOS mode will hard-lock the system to protect them. You can disable
that protection by entering the internal LOCK command, e.g. LOCK C:,
then you can run UnErase etc.(for sensible values of "etc.")

Nope; it's in the Path now, so entering the MOUSE command from
anywhere will find it, as it wouldn't have done where it was.

Stay out of there; as the dialog says, any changes made in there will
NUKE the private files you so carefully created! That's dummy wizard
stuff; you're working beyond that level now.

You can do, or integrate them. Note that the files I posted were for
use within "Exit to DOS.pif", not the system's files!

I usually set that to be functional, but alerting the user, e.g.

@Echo Off
Call CD-ROM.bat
LH SmartDrv A- B- /X
LH Mouse
Mem /C/P
Echo.
Echo The above is why "Use current..." sucks :-(
Echo DOSStart.bat now ends.
Echo.

CDROM.BAT looks like this...

@Echo Off
CTLoad C:\Windows\Command\EBD\OakCDROM.sys /D:CD1
LH MSCDEx /D:CD1

....requiring Creative's CTLoad utility to load the .SYS driver from
the .BAT (other free utils do the same).

; No space between /D: and the name!

That looks fine!

Doesn't give you the same control, without the [Menu] etc. and without
Emm386, you'd have less DOS memory. No mouse of CD-ROM support. Not
as clean as Debug but doesn't give much better functionality.



a match to see if what you are standing in is water or petrol.