Am 16.12.2021 um 12:46 schrieb atecon:
Am 16.12.2021 12:33 schrieb Olasehinde Timmy:
> Thanks for the swift response, sir. Below is an example of what I am
> facing:
>
> Couldn't open C:Users immeAppDataRoaminggretlirf239.gp [2] for writing
> C:Users immeAppDataRoaminggretlirf239.gp [2]: Invalid argument
> *** error in function IRFgrph, line 34
>> outfile "C:Users immeAppDataRoaminggretlirf239.gp [2]"
that looks like a corrupted path to nowhere.
The problem seems to stem from
backslash-t (\t) being interpreted as the
tabstop code. This might affect all Windows users with a user name
starting with "t" (both uppercase and lowercase, I think). Perhaps the
combination \n might also cause the same problem, so user names starting
with "n".
Did this work before?
Good question. Timmy, did you perhaps set up a new machine / new system
with a new user name recently? Or did your user name on Windows always
start with a "t", and SVAR worked? I'm not sure right now whether we
have changed those code lines recently, but it's possible in principle.
thanks
sven