Database Search
TechHome
- 32 Bit Environment Extender
- Add to PATH Environment Variable
- Assigning a System Variable to a Path
- Call Function and Environment Path
- Changing the Path in WinNT
- Detecting Search Drive Mappings
- DOS Environment Variables
- Edit of an Environment Variable
- Environment Issue from PopMenu
- Environment Settings
- Environment Variables Across DOS Sessions
- EnvironmentSet UDF
- Get More Environment Space
- Get Next Available Drive Letter
- Getting the Temp Directory
- Immediate User Environment Change in NT
- List All Environment Variables
- NT Environment variables
- PATH Information
- RunEnviron and File not Found or WinExec Error
- Set System Environment Variable
- Setting the Environment in Windows 95
- Unexpected Error - Quitting - Using RunEnviron
- Win95 and environment variables
- Win95 environment after Winset
- Win95 Environment and App Spawns
- Windows Environment Variables
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Environment Issue from PopMenu
Keywords: User System Envirnonment Variables Popmenu
Question:
For some reason the Environment function is unable to get the same information that I see in the registry for both User and System Envirnonment Variables. The documentation for the Environment function states that it can retrieve either a system environment variable or a user environment variable. These variables are defined in the { Advanced tab } [Environment Variables] using Sysdm.cpl.As I understand it the 'Environment' function is retrieving the value from the the environment block of the WinBatch process running the script. That block is inherited from the parent process that started the process running WinBatch. The parent process is usually either the Explorer.exe or cmd.exe but it could be something else. It all depends on how you start WinBatch (or your compiled script.)
So the question is how did the process starting my get the environment variables it is passing to WinBatch. Here are my tests and their results. The issue seems related to the popmenu somehow.
- Started WinBatch Navigator from Windows Start - Run a WBT - picked my WBT - Results are correct
- Started WinBatch Navigator from Windows Start - started Studio - opened my WBT - run/debugged it - Results are correct
- Started WinBatch Studio from Windows Start - opened my WBT - run/debugged it - Results are correct
- used WinBatch PopMenu - started Studio - opened my WBT - run/debugged it - Results are not right
- used WinBatch PopMenu - started Navigator - Run a WBT - picked my WBT - Results are not right
- run compiled script - Results are correct
Answer:
PopMenu is no different than any other executable in this regard. It receives the environment block of the process starting it - Explorer by default. However, PopMenu is started as part of the login session creation process, so the Explorer's environment block can be modified by other applications, drivers or services after PopMenu has started but before the session login is finished. This appears to be the case for you.If you plan on using PopMenu to start your sundry scripts that require your environment variable then you could modify PopMenu's environment block variables to match your needs. There are several ways to do this but the simplest may be to be editing the the PopMenu menu file PopMenu.mnw to add code to check and set the variable as needed. This could be done in either the top section of the menu file or in the section for each menu item that requires the variable to be correctly set. Another approach would be to kill and restart PopMenu after the login process has completed but this has some obvious drawbacks.
Article ID: W17860
Filename: Environment Issue from PopMenu.txt
File Created: 2013:07:16:08:15:26
Last Updated: 2013:07:16:08:15:26