ms-dos compatibility mode?

if I go to controlpannel then system then performance, I see ms-dos compatibility mode...that is what virtual memory, c: is in...

I have been told this is why my teac cdrw will not burn any cds.

any ideas?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Kyle SchroederConnect With a Mentor Endpoint EngineerCommented:
See these pages at Microsoft for help in resolution.  Try the suggestions, if they don't work, let us know and we can try some other ideas.

Most likelt you are loading CDROM.SYS (or another CDROM driver by another name) in your CONFIG.SYS file as well as MSCDEX in your AUTOEXEC.BAT file.  There is NO NEED for either of these in WIN32 and that includes Win95, Win98, and WinME.  

Edit your CONFIG.SYS and AUTOEXEC.BAT to remove these.  If you have a line like:


comment it out with a REM at the beginning of the line:


Similarly, if you have:


put a REM at the beginning:

REM LH C:\....

This will take care of your MSDOS compat problem.
bebonhamAuthor Commented:
I had already whacked all that stuff before asking...

ended up deleting autoexec.* and config.* as I was getting frustrated...

anyways.... I am going home for today, and I just moved, so no internet at home...I'll get back to y'all tomorow.


NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

What have you installed/removed PRIOR of receiving this situation?

Even when both CDROM.SYS or simular cd-driver AND MSCDEX.EXE are loaded, windows will stil not put you in compatibilty mode.

AUTOEXEC.BAT and CONFIG.SYS are not the only files that can point to a driver/program that will put you in compatibility mode, some entrys in WIN.INI, and I believe SYSTEM.INI can also force compatibility mode

Even some devices in your computer can cause this.  For example and old harddisk that does not support 32-bit functions...

Best is to remember what programs/devices you have installed PRIOR to receiving this error.

This can help you out:

Solution 1: determine software cause
Restart your pc and when you see "Starting Windows" or something like it, press the F8 keys multiple times until you see the "Windows Startup Menu"

Select the mode "Safe Mode without networking" or something resembling that option.

Windows will then boot without loading AUTOEXEC.BAT, CONFIG.SYS, and will only load drivers essential to running windows, like display, keyboard, mouse,...

Open system propertys and see if it says compatibility mode.  If it doesn't, you know it's a software cos, and you'll have to determine what caused it.  To do that, restart the pc and open the "Windows Startup Menu", as described above and choos Logged to file C:\...

Let windows load completaly, open the file with wordpad (it will be too large for Notepad) and perform a search for the (sub) word FAIL

If you recognize any of the drivers you have added, put a remark (usually ; before it, in autoexec.bat, just add :: before it), restart windows, and check if it solved

Solution 2: Determine Hardware cause
Start windows, open the control pannel, then system propertys or just press WIN+BREAK, then click on the Device Manager Tab, and look for an entry with an exclamation mark or an 'X' next to it.

Click on the entry, then click on the button Properties.  You will then get a window with a "Device Status" text displayed.  Read it.  If that helps, perform the requested steps.  If that don't, check the "Disable in this hardware profile" checkbox.  Press OK, OK, restart windows, and try again to see if the problem is solved.  If not, open the Device Manager again, and remove the item in question.  Restart windows, and windows will automatically reinstall that device (if it still exists in your pc).

If all that doesn't answer your problems, maybe it's time to get some free fysical help from a computer guru in your neighbourhood.  Most of us enjoy working on/with pc's soo much we'll be happy to help.  And all it will cost you is a pizza, some coke (coca-cola), and maybe a pack of smokes... :-)

Ramses says RooOOOOar!

This issue pops up on occasion in my shop.  If you have already cleared all the DOS drivers from loading, then you can do this to clear it up usually.  Run regedit and search for the key PCIDualIDE and change its value from 0 to 1 or vice versa.  In other words, swap the value.  Close regedit and restart.  That should clear it up.
I think dogztar probably answered your question.  Look at the second URL and use REGEDIT to look for an entry called NOIDE.  Once this is set on in the registry, your stuck in DCM even if you pull out the offending hardware.

His URLs also mention device drivers, etc., but I'd bet that the problem was caused by the CDR having a conflict with the drive.  You might try putting the CDR on the secondary controller and then delete the NOIDE.

bebonhamAuthor Commented:
there is no NoIDE entry in my registry...

I checked win.ini, system.ini, I made bootlog.txt and there were no fail

there are no warnings or disabled devices in device manager.

any other ideas?
it is w98 second edition, so it is not the large ide problem...
What piece of hardware did you install prior to having this error?
bebonhamAuthor Commented:
the cdrw,,,was the last thing is resolved...I came across a post on some board that said "start in safe mode, then remove all cd,hd, fd controlers,drives, etc."

so I did, then I rebooted, then it reinstalled some stuff, and without any other fussing at all, the msdos compat went away, and the cdrw started working.
bebonhamAuthor Commented:
thanks to everyone
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.