Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Networks - Servers
 | |
| |
| |
| |
| |
| |
|
- !!Users, Workstations, Domains and Machine Domains Explained
- 1932 Winexec when Opening MultiUser Files on a Network
- 523 Error Enumerating Network Resources
- App not Launching from Mapped Root
- Backslashes with Servers - Volumes - Directories
- Changing Password in Windows 95
- Client IP Configuration script
- Connect to Servers via DOS batch files
- Detect Existence of Client32
- Determine if a Tree of Directory is Mappable
- Determine if a User has Admin Rights
- Disable NetBIOS over TCPIP
- Disconnect Mapped Drives Ex Dialog
- Display a Banner or Message Box on Remote PC
- Find out what Drive Letter is Mapped to Server
- Find Users Logged on Other Machines
- Finding and Listing Processes on Remote
- Getting Currently Connected Usernames to NT Share
- Global Net Map Setting
- Hiding Drive Mappings
- How do I see Im logged on
- Installing your Network via Windows Setup
- Is Network Alive
- Log Off User after an Amount of Time
- MSIE Proxy Server Control
- Net Use Command and Passing Passwords
- NT to Novell Translator
- RASSAPI.dll not Found
- Remote Launch of Winbatch
- Replication Manager - Replicate BDCs
- Sample Code Extracts Authenticating Server Name
- Segment Load Error
- Send Messages to Users
- SNMP in WinBatch
- Test Network Drive Mappings
- Unexpected Network Error
- Update All NT Existing-New User Registry Configs
- Use of Newer Network Extenders with Older Winbatch
- Using a BAT File to Launch Subsequent Operations
- Validate a Userid and Password
- Wake up Machine on LAN
- Who is Logging on to Remote NT Server
- Win32 Network Errors
- Workaround for Network Error 510
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Application not Launching from Mapped Root
Keywords: application not launching
Problem:
User is on a network, possibly Novell. W:\ is mapped to G:\winuser\userID (the path to Windows).If the user tries to launch Windows from the mapped W:\ drive, then Windows runs, but the application will not run. A message is displayed that the "INI file is not found". If the user runs from the actual G:\WinUser\UserID then the application will run fine.
Answer:
This a kinda common bug in a few applications. What happens is this:
The application asks for Windows directory name:
Case 1 It gets - W:\ Case 2 It gets - G:\WINUSER\userIDThen it adds a backslash and its INI file name to it:
Case 1 It gets - W:\\APP.INI Case 2 It gets - G:\WINUSER\userID\APP.INIWell, you can see that in case 1, because it was not expecting a root directory, it built an invalid file name with two slashes in it, whereas with the other name, everything came out rosy.
Article ID: W13472
Filename: App not Launching from Mapped Root.txt
File Created: 1999:04:15:16:54:16
Last Updated: 1999:04:15:16:54:16