If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Path statement
Know I can put a windows paths statement in msdos.sys file. Can I put such
a path statement in the msdos.sys file where a windows application that opens at startup requires it? I understand the folder names require 8 character msdos names in that location. Where can I put a path statement in windows for windows applications that need same that do not open at startup? My end purpose is to move all such statements from the autoexec.bat file to such locations, and make the autoexec.bat file empty (0 bytes). All it contains now are path statements. |
#2
|
|||
|
|||
Path statement
Why?
The autoexec.bat file is where the environmeental variables are *supposed* to go....not the msdos.sys file. For what reason do you need an empty autoexec.bat? -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm "Lil' Dave" wrote in message ... Know I can put a windows paths statement in msdos.sys file. Can I put such a path statement in the msdos.sys file where a windows application that opens at startup requires it? I understand the folder names require 8 character msdos names in that location. Where can I put a path statement in windows for windows applications that need same that do not open at startup? My end purpose is to move all such statements from the autoexec.bat file to such locations, and make the autoexec.bat file empty (0 bytes). All it contains now are path statements. |
#3
|
|||
|
|||
Path statement
Guess that means no. Remembered someplace that WinME puts this somewhere
after an app install makes a path statement in autoexec.bat, and never uses an autoexec.bat file. Just wondered if it were possible. "glee" wrote in message ... Why? The autoexec.bat file is where the environmeental variables are *supposed* to go....not the msdos.sys file. For what reason do you need an empty autoexec.bat? -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm "Lil' Dave" wrote in message ... Know I can put a windows paths statement in msdos.sys file. Can I put such a path statement in the msdos.sys file where a windows application that opens at startup requires it? I understand the folder names require 8 character msdos names in that location. Where can I put a path statement in windows for windows applications that need same that do not open at startup? My end purpose is to move all such statements from the autoexec.bat file to such locations, and make the autoexec.bat file empty (0 bytes). All it contains now are path statements. |
#4
|
|||
|
|||
Path statement
Windows ME and higher do not have real-mode support, so the environmental variables
formerly configured in autoexec.bat and config.sys are moved to a Registry key. Windows 95/98/98SE do have real-mode support.....they will not even look for a Registry key. Overview of Real Mode Removal from Windows Millennium Edition: http://support.microsoft.com/?kbid=269524 -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm "Lil' Dave" wrote in message ... Guess that means no. Remembered someplace that WinME puts this somewhere after an app install makes a path statement in autoexec.bat, and never uses an autoexec.bat file. Just wondered if it were possible. "glee" wrote in message ... Why? The autoexec.bat file is where the environmeental variables are *supposed* to go....not the msdos.sys file. For what reason do you need an empty autoexec.bat? -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm "Lil' Dave" wrote in message ... Know I can put a windows paths statement in msdos.sys file. Can I put such a path statement in the msdos.sys file where a windows application that opens at startup requires it? I understand the folder names require 8 character msdos names in that location. Where can I put a path statement in windows for windows applications that need same that do not open at startup? My end purpose is to move all such statements from the autoexec.bat file to such locations, and make the autoexec.bat file empty (0 bytes). All it contains now are path statements. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
'Windows cannot access the specified device or Path Name" | Kate | General | 2 | July 7th 04 05:44 AM |
UNC path as Fully Qualified Domain Name | Forrest | Networking | 0 | July 1st 04 10:00 PM |
project 1 path not found | elaine | Monitors & Displays | 1 | June 29th 04 04:43 PM |
UNC Path bug ? | Skybuck Flying | Networking | 2 | June 23rd 04 10:42 AM |
Where to set PATH for DOS enviornment | John John | General | 9 | June 7th 04 08:29 AM |