I think this problem has been on and off lurking with only the TS 1.3 systems. The summary relevant to the topic is that, Bruker has released a 'revamped' makeau script and has rewritten several of the commonly employed au scripts such as : multizg, multicmd, multi_zgvd, multi_zgvt, simplex, to name a few.
The new 'makeau' should be in the following directory :
$XWINNMRHOME/exp/stan/nmr/au/
The new au scripts themselves should be here :
$XWINNMRHOME/exp/stan/nmr/au/src
In my peculiar case, I had an additional problem that has crept up for an inexplicable reason. This is that, the important include file called exptUtil has been copied over from a Topspin 3.0 distribution, onto the DRX499 system which runs the TOPSPIN 1.3. The two versions are different from each other.
exptUtil lives in the following location :
$XWINNMRHOME/prog/include/inc
In conclusion, with the correct exptUtil, makeau compilation script and the new au source files, compilation seems to run smoothly. I did a recompilation of all 'au' programs via 'expinstall' in DRX499 and that proceeded without a hitch. The same on DPX200 was mostly successful i.e. some scripts did produce an error, which I suspect are some of the user made 'au' scripts.
We will expand on those later, if it becomes important to investigate.
The new 'makeau' should be in the following directory :
$XWINNMRHOME/exp/stan/nmr/au/
The new au scripts themselves should be here :
$XWINNMRHOME/exp/stan/nmr/au/src
In my peculiar case, I had an additional problem that has crept up for an inexplicable reason. This is that, the important include file called exptUtil has been copied over from a Topspin 3.0 distribution, onto the DRX499 system which runs the TOPSPIN 1.3. The two versions are different from each other.
exptUtil lives in the following location :
$XWINNMRHOME/prog/include/inc
In conclusion, with the correct exptUtil, makeau compilation script and the new au source files, compilation seems to run smoothly. I did a recompilation of all 'au' programs via 'expinstall' in DRX499 and that proceeded without a hitch. The same on DPX200 was mostly successful i.e. some scripts did produce an error, which I suspect are some of the user made 'au' scripts.
We will expand on those later, if it becomes important to investigate.
