Under Winnt the Diadem variable managament couldn't initialize

[Akos]

with administrator privilige,
using the UserVarCompile from autosequence, menu or button,
also with *.vas file containing only comments

[Super Fly]

What version of DIAdem are you running?

[Akos]

Sorry Super Fly, I should have mentioned before,

It is the 7.02.603 .

Thanks

[Tom F]

I've tried the uservarcompile command under WINNT without any problems. Somethings to check would be:

1. Is the VAS file in the the current directory that AUTODRVUSER is pointing at. For example if you use the following line of code, the path is implied as the same as AUTODRVUSER.

uservarcompile("demovars")

if you are not sure about the current state of the variable AUTODRVUSER modify uservarcompile to have the compleat path, for example

uservarcompile("c:\temp\demovars")


2. Is your VAS file formated properly? Refer to DIAdem's online help file under "User Variables".

Post any error message you might be getting,and let us know what version of DIAdem you are using.

[Akos]

Thanks for the answer, that was OK.

I mean that the path was correct, as well the file.
I have also made a new one containig only comments.
The strange is that for 2 days it was OK, then after a restart never worked again.
I couldn't find any help or comment related to this problem.
Is this a Win2000 problem or Diadem?
I uninstalled and installed Diadem again but it didn't helped so I guess it is more a Windows problem..?

If someone can help me further I would be glad.

Thank You Tom F

[Peasoup]

Hi,
I have experienced similar problems with Winnt running Diadem v8 (certainly the same error message and symptoms - correct operation for some time, then all of a sudden loss of user variables).

We have cured the problem (together with Ni) as follows:

When user variables are intialised (either from menu or an autosequence) 2 temporary files, in the default teporary directory, are created to manage them
av_indx.001 and av_info.001
these are swept when diadem closes.

The diadem variable tmpdrv holds the path - so it can be checked.

these files are not normally set to read only, however you may find that yours are. We summise that a machine/diadem crash causes the state to be changed.

deleting the files or changing file properties re
sults (for us at least) in a return to normal operation.

The error was probably generated as a consequence of diadem being unable to overwrite/delete the read-only temp files.


hope this helps

andy