> > 2. Could you find the lines:
> >
> > # Show where item is found in the specified path
> > Root.ShowPath: false
> >
> > within your ".rootrc" and replace "false" with "true".
>
> I changed this to "true", but it didn't change root's behaviour (i.e. it
> didn't cause root to output the debugging information that you asked
> for) . This suggests to me that, on Win98 anyway, root does not read
> the .rootrc file in the tutorials subdirectory (the only one on my Win98
> system), or any directory for that matter (except for the "Current
> Working Directory" - see below).
>
> However, when I ran root from the tutorlals subdirectory, then root
> appeared to run OK (I was able to ".L rootalias.C" and ".x
> benchmarks.C", and everything appearded to run OK). Here is the output
> that you asked for:
>
> So, it would appear that ROOT v. 2.23.11 requires a .rootrc file to
> exist with an entry for "WinNT.*.Root.DynamicPath" in order to properly
> function on a Win98 machine. Can you confirm this?
Under Windows NT it works properly either way (with .rootrc and with
no ".rootrc"). If ROOT finds no ".rootrc" it uses the default parameters.
My wonder Win98 screw those defaults.
> If this is the
> case, then where should .rootrc be placed on a Win98 system so that root
> finds it at startup?
If I udnerstand things right the way ROOT uses ".rootrc" is explained on
http://root.cern.ch/root/html/TEnv.html#TEnv:description
In fact this means one should provide ".rootrc" file under %ROOTSYS% directory
at least and one may provide a custom version under his/her home directory and / or
under the current working directory.
> I have attached the file myroot.bat to this e-mail
> which now starts up root properly on my Win98 system, thanks to your
> help. Please let me know if this is the "wrong" way to do this, or if
> you think that there is a better way.
I can not understand this "remotely".
This sounds something wrong with some of the global variables TSystem class defines:
R__EXTERN const char *gRootDir;
R__EXTERN const char *gProgName;
R__EXTERN const char *gProgPath;
The problem there is no API to get these values so one can need either debugger
or "print statements" to see what is going on for Win98.
Valery
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:17 MET