The reason upg.tps errors first is because it's the first file in the
system that gets created or gets written to. Nothing to do with FM3. If
I put a upg.tps file in the folder manually, then next file errors.

This is the kind of thing I would expect when running a program on a
network shared drive/folder that hasn't been given read/write
permissions. It's not our source code or the program itself. I install 4
or 5 a week. It just happened in the last week on 2 different brand new
computers (windows 10). When I right click on the folder and give access
to 'everyone' and make 'everyone' read/write... it worked.

And yes I know c:\wrench is old school, like c:\clarion11 is. One of
these days I'll move things under program files and program data.. but
right now this works 99% of the time... plus it's much easier If I have
to grab the folder to put it somewhere.

We'll see if we get more of this. Maybe it's one of those Windows S
computers I've heard about.

Ray Rippey
VMT Software

On 04/03/20 3:06 AM, Friedrich Linder wrote:
> If I were you I
> would check (in your own Clarion source code) what might be the problem with
> UPG.tps file creation. C:\wrench is not a Windows protected folder
> resource.