Hi All, I've not made the jump to ME yet. (Nor am I in a hurry) but I do support some new ME installs that my customers bought. I have noticed very few problems with ME that I haven't worked around but this one has me stumped and I rarely have time to mess with it very long. If I add "DEVICE=C:\WINDOWS\COMMAND\ANSI.SYS" to C:\CONFIG.SYS and reboot, CONFIG.SYS is renamed to CONFIG.BAK and replaced with a generic CONFIG.SYS. Does anyone know what is responsible for this? Thanks in advance!

Windows ME don't use CONFIG.SYS and AUTOEXEC.BAT You don't need devices like ANSY.SYS because it is a DOS driver, and you "don't need to use DOS in windows ME" Some CONFIG.SYS configurations can be saved in the win.ini or system.ini like FILES=80 will be added in the system.ini [386Enh] in a entry Pervmfiles=80.

If you support DOS programs on ME machines... there may be some things you need to be aware of. These are all from the Microsoft KB located at support.microsoft.com: Overview of Real Mode Removal from Windows Millennium Edition: http://support.microsoft.com/support/kb/articles/Q269/5/24.ASP How to Increase Available File Handles for MS-DOS-Based Programs in Windows Millennium Edition: http://support.microsoft.com/support/kb/articles/Q269/0/30.ASP Ansi.sys Device Driver Cannot be Loaded in Windows Me: http://support.microsoft.com/support/kb/articles/Q273/7/80.ASP Cannot Configure Expanded Memory Support for an MS-DOS-Based Program: http://support.microsoft.com/support/kb/articles/Q275/4/23.ASP? 16-Bit Programs Cannot Open More Than 120 Files Simultaneously in Windows Me: http://support.microsoft.com/support/kb/articles/Q274/5/94.ASP

Duh. Thanks for the info! I wasn't even thinking in those terms! I just thought that some new program was renaming the files on me. I guess I'm used to having real-mode to rely on. Thanks again!