| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | profile |
MB> > I have a much better suggestion. Have your EXE file determine which > directory it is running from, and use a default INI file > there. MB> As you say, this doesn't work on a network, or where there is a requirement for multiple users to use different INI files. Using an entry in OS2.INI to point to the private INI file solves both of these problems. In the case of the network, the private INI file is located on the local workstation's hard disc. In the case of multiple users (using something like Restricted Workplace Shell) each user's OS2.INI will point to a different location. The only complication is in the install program, where the option to place the private INI file in a location other than the main application installation directory should be provided. > JdeBP < ___ X MegaMail 2.10 #0:Dr Who is back on U.K. television! --- Maximus/2 3.01* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 @PATH: 440/4 141/209 270/101 712/515 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.