|
From: Leif M. <le...@ta...> - 2002-11-27 16:54:04
|
I just put a debug build of Wrapper.exe up on the server at http://wrapper.sourceforge.net/Wrapper.exe Can you BACKUP your current wrapper.exe and try it with this one? It will dump out a bunch of debug info as it reads in the properties from the file. Could you post what you get? Thanks, Leif Todd Enright wrote: > Hi Leif, > The variable is set to c:\windows in the control panel, and this is > verified by going to a command prompt and typing SET. I also have > windir=c:\windows in the system variables but no setting in the user > section. > > I have get the same results by running wrapper as either a console > app, or a service. > > I'll keep digging on my end. > > Thanks, > Todd > > ----- Original Message ----- > From: Leif Mortenson <mailto:le...@ta...> > To: wra...@li... > <mailto:wra...@li...> > Sent: Wednesday, November 27, 2002 10:22 AM > Subject: Re: [Wrapper-user] environment variables > > Todd, > Strange, All the wrapper does is call the standard Windows API > to get the > system environment variable's value. > > I just tested this on a Windows XP machine and on my machine I > got the correct > value: C:\WINDOWS > > What do you get if you open a command prompt and type SET at > the prompt? > > Do you see this problem when run as both a service and as a > console app? Or > just one or the other? > > You might want to go in and look at the environment variable > setting in the > system control panel. There are two sections. User variables and > system > variables. I have windir=c:\windows in the system variables but > no setting in the > user section. If the variable is set in both places, then you may > be getting > different values depending on context. > > Let me know whether or not any of this helps. > > Cheers, > Leif > > > Todd Enright wrote: > >> I am using ver 2.2.9 on XP. >> The environment variable for WINDIR returning c:\winnt, but the >> actuall WINDIR variable on my machine is c:\windows, and further >> i don't have any c:\winnt directory on my machine. >> >> Do you know why this is happening? > > |