> I'm running 1.03/04 on WindowsNT 4.0 (Service Pack 3). At the moment I
>have to restart root each time I alter the macro file. Yuck. Any help would
>be great!
>Interesting. I've been using VC++ 5.0 to edit root macro files (nice syntax
>coloring, etc.) and it does refuse to save a file after it has been opened
>by root. However, if I use notepad it works just fine. Odd; it was as if
>some sort of lock was established by root that wasn't really a write
>lock... or the two systems are writing invisible/temp files (I couldn't
>fine anything) that collide?
>Well, I'm using notepad now, but I would really like to be able to go back
>to VC++... :-)
I guess some security feature of NT has something to do with your problem.
I'm not seeing problem with my Windows-NT4.0 Workstation. Maybe Valery can
give you better advice.
>BTW, I see large numbers of root temp files in my temp directory; they are
>all numbered. Besides the observation that this seems to be an inefficient
>way of handling commands (wouldn't it be better if it remained in memory,
>never written to the disk?), do they ever get deleted by ROOT when root is
>done? It dosen't look like it...
There is some historical reason why it uses file to handle commands. But
anyway, ROOT/CINT removes the temp files automatically. The only case they
remain is when ROOT/CINT crashes in the middle of processing macro. Or
possibly due to some problem , it can not remove the temp files. Anyway,
it is recommended to straight out above problem first.
Masaharu Goto