System Configuration Utility

When I run MSCONFIG, I get a message in a box entitled System Configuration
Utility. The message is Unable to sychronize the environment variables in
the Windows Registry with the environment variables in the legacy files
AUTOEXEC.BAT and/or CONFIG.SYS

After I click on, the regular msconfig box opens.

What do I need to do?

What do I need to do?

Most probably nothing.

Next time, before you open MSConfig, have a look at autoexec.bat and note
down its contents, especially any SET= commands. What is happening, or
rather not happening in your case, is that on opening MSConfig Win Me
detects that autoexec.bat may have been altered and checks it for possible
changes to any environment variables (the SET= commands) so as to transfer
these changes to the registry. Unlike earlier Win 9x operating systems
Win Me does not process autoexec.bat on boot up and handles the setting of
environment variables differently than previously. Autoexec.bat is
retained simply for legacy support of certain applications which use
autoexec.bat to set environment variables with the most common users being
various sound card drivers.

Win Me actually processes autoexec.bat on shutdown and transfers any
changes made to environment variables contained in autoexec.bat to the
registry so as to be available to the operating system when the PC is next
booted.
--
Mike Maltby MS-MVP



debba wrote:

When I run MSCONFIG, I get a message in a box entitled System
Configuration Utility. The message is Unable to sychronize the
environment variables in the Windows Registry with the environment
variables in the legacy files AUTOEXEC.BAT and/or CONFIG.SYS

After I click on, the regular msconfig box opens.

What do I need to do?

My autoexec.bat:

If MSCDEX doesn't find a drive...
IF ERRORLEVEL 2 SET CDPROB=1
::
GOTO QUIT

:HELP
lh %ramd%:\MSCDEX EXE ID:msc001 /l:%CDROM%
::If MSCDEX doesn't find a drive...
IF ERRORLEVEL 1 SET CDROM=1
cls
call HELPBAT
::
GOTO QUIT

call FIXIT.BAT
rem cleanup enviroment varibles
DE CDPROB=
SET CDROM=
SET LGLDRV=

GOTO QUICK
:QUICK

Does anything need changed?


"Mike M" wrote:

What do I need to do?

Most probably nothing.

Next time, before you open MSConfig, have a look at autoexec.bat and note
down its contents, especially any SET= commands. What is happening, or
rather not happening in your case, is that on opening MSConfig Win Me
detects that autoexec.bat may have been altered and checks it for possible
changes to any environment variables (the SET= commands) so as to transfer
these changes to the registry. Unlike earlier Win 9x operating systems
Win Me does not process autoexec.bat on boot up and handles the setting of
environment variables differently than previously. Autoexec.bat is
retained simply for legacy support of certain applications which use
autoexec.bat to set environment variables with the most common users being
various sound card drivers.

Win Me actually processes autoexec.bat on shutdown and transfers any
changes made to environment variables contained in autoexec.bat to the
registry so as to be available to the operating system when the PC is next
booted.
--
Mike Maltby MS-MVP



debba wrote:

When I run MSCONFIG, I get a message in a box entitled System
Configuration Utility. The message is Unable to sychronize the
environment variables in the Windows Registry with the environment
variables in the legacy files AUTOEXEC.BAT and/or CONFIG.SYS

After I click on, the regular msconfig box opens.

What do I need to do?

Does anything need changed?

Only if you have problems however most if not all of that autoexec.bat
file does precisely nothing, since, as I mentioned in my previous post,
Win Me doesn't process the autoexec.bat file other than to transfer any
environment variable settings it might find there to the registry when the
system shuts down.

In other words your entire autoexec.bat file could be safely junked.
--
Mike Maltby



debba wrote:

My autoexec.bat:

If MSCDEX doesn't find a drive...
IF ERRORLEVEL 2 SET CDPROB=1

GOTO QUIT

HELP
lh %ramd%:\MSCDEX EXE ID:msc001 /l:%CDROM%
If MSCDEX doesn't find a drive...
IF ERRORLEVEL 1 SET CDROM=1
cls
call HELPBAT

GOTO QUIT

call FIXIT.BAT
rem cleanup enviroment varibles
DE CDPROB=
SET CDROM=
SET LGLDRV=

GOTO QUICK
QUICK

Does anything need changed?

Mike,

Why is debba quoting the EBD autoexec.bat from msconfig?

Shane

"Mike M" wrote in message
...
Does anything need changed?

Only if you have problems however most if not all of that autoexec.bat
file does precisely nothing, since, as I mentioned in my previous post,
Win Me doesn't process the autoexec.bat file other than to transfer any
environment variable settings it might find there to the registry when the
system shuts down.

In other words your entire autoexec.bat file could be safely junked.
--
Mike Maltby



debba wrote:

My autoexec.bat:

If MSCDEX doesn't find a drive...
IF ERRORLEVEL 2 SET CDPROB=1

GOTO QUIT

HELP
lh %ramd%:\MSCDEX EXE ID:msc001 /l:%CDROM%
If MSCDEX doesn't find a drive...
IF ERRORLEVEL 1 SET CDROM=1
cls
call HELPBAT

GOTO QUIT

call FIXIT.BAT
rem cleanup enviroment varibles
DE CDPROB=
SET CDROM=
SET LGLDRV=

GOTO QUICK
QUICK

Does anything need changed?

Shane,

I haven't a clue which is why I've given up. I've decided to try like you
and withdraw from these newsgroups before I do too much harm to my blood
pressure which is already far too high.
--
Mike


Shane wrote:

Mike,

Why is debba quoting the EBD autoexec.bat from msconfig?

In that case you should definitely step back Mike, your health is more
important than anything going on in here.
Joan

Mike M wrote:
Shane,

I haven't a clue which is why I've given up. I've decided to try
like you and withdraw from these newsgroups before I do too much harm
to my blood pressure which is already far too high.

Joan Archer wrote:

In that case you should definitely step back Mike, your health is more
important than anything going on in here.

Thanks Joan,

Its been too high for a long time now but it tends to be other things
rather than these newsgroups that usually cause me problems.
--
Mike

Well, Mike, naturally I support you in that effort.

As for the 'unable to synchronize environment variables' message, I recall
such happening to me once or twice, but can't for the life of me remember
what caused it! It seems so long ago.


Shane



"Mike M" wrote in message
...
Shane,

I haven't a clue which is why I've given up. I've decided to try like you
and withdraw from these newsgroups before I do too much harm to my blood
pressure which is already far too high.
--
Mike


Shane wrote:

Mike,

Why is debba quoting the EBD autoexec.bat from msconfig?

Usual culprit, IIRC was SB/Creative sound cards.

--
Noel Paton (MS-MVP 2002-2006, Windows)

Nil Carborundum Illegitemi
http://www.crashfixpc.com

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's
"Shane" wrote in message
...
Well, Mike, naturally I support you in that effort.

As for the 'unable to synchronize environment variables' message, I recall
such happening to me once or twice, but can't for the life of me remember
what caused it! It seems so long ago.


Shane



"Mike M" wrote in message
...
Shane,

I haven't a clue which is why I've given up. I've decided to try like
you
and withdraw from these newsgroups before I do too much harm to my blood
pressure which is already far too high.
--
Mike


Shane wrote:

Mike,

Why is debba quoting the EBD autoexec.bat from msconfig?