|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (3 bit)
Join Date: Oct 2004
Posts: 6
|
Custom path ignored in ME
I have just reinstalled Windows ME and set my PATH in autoexec.bat to:
SETPATH=C:\WINME;C:\WINME\COMMAND;c:\progra~1\common~1\gtk\2.0\bin;C:\!BATCH;C:\bench but th ME prompt does not take it into account. When I type the PATH command, all I get is: PATH=C:\WINME;C:\WINME\COMMAND So my path applications do not work, and my batch files are messed up. any help would be appreciated. |
|
|
|
|
|
#2 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 36,460
|
Run msconfig.
Click the environment tab, select PATH and press the edit button. |
|
|
|
|
|
#3 |
|
Member (3 bit)
Join Date: Oct 2004
Posts: 6
|
Thanks, but MsConfig is only a uttility to modify configuration files(such as autoexec.bat or system.ini) without needing to know their location, the syntax, etc. I directly modified Autoexec.bat, the file MSConfig toys with in the first place, but to no result. I HAVE tried to use MSconfig, but it makes no difference. If I am wrong and the uttility can alter files unreachable by other means, then I was unaware of it. But my problem stands; Autoexec.bat is the system file that determines the path(wether you modify it throught MsConfig or with notepad), but Win ME fails to take it into account. Even Third party programs cannot change my path(I suspect they function the same way as MSConfig). This is a mystery to me. If anyone knows the source of this problem, please let me know.
|
|
|
|
|
|
#4 |
|
Member (9 bit)
Join Date: Jun 2000
Posts: 499
|
Me doesn't use the autoexec and config.sys files.
Did you not go into the Environment tab as recommended?? In Microsoft Windows 98, the Autoexec.bat and Config.sys files were used to set global environment variables. When real-mode MS-DOS was removed, another method was required to set global environment variables (PATH, SET =, etc). Windows Me solved this issue by migrating current environment variables during setup and placing them in the registry under the following sub key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\Environment. |
|
|
|
|
|
#5 |
|
Member (3 bit)
Join Date: Oct 2004
Posts: 6
|
Thank you for this precision; I did not know this information about ME(I only started using ME 3 days ago... I was using 98 before). But I did try MSconfig, to no avail. I will check the registry to ensure it has been properly modified.
|
|
|
|
|
|
#6 |
|
Member (3 bit)
Join Date: Oct 2004
Posts: 6
|
That fixed it! I manualy changed the Path in the registry, and it is now correctly recognized by ME. Thanks for the help. It is strange that MSconfig could not adjust this setting however(I DID fiddle with the system files a lot to fing my way around winME; perhaps I accidentaly messed with something I shouldn't have, and caused this error. Strange.).
|
|
|
|
|
|
#7 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 36,460
|
Can I ask why you "upgraded" from 98 to ME?
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|