HWHAP - T3000 does not back-up

Houston we have a problem…I am unable to make a program back-up.
I have just now updated T3000 software (when I look in T3000/Database/Update the file “T3000 Version” refers to version 20260316)

I am doing what I have always done:

  • File / Save As /
  • pick a location - usually C: Programs x86 / T3000 / Database /Buildings / Default Building. File structure is fully visible/navigable.
  • enter a file name - usually similar to prev. with new date
  • check file type .prog
  • click “save”

The bottom bar of T3000 screen narrates through various steps, green bar extends until “Save config file success”
BUT
There is no file with the name in the location. I have tried various other names/locations no result. Seems that the .prog file is created correctly but just doesn’t write anywhere. I even tried over-writing an older file name - but that failed.

This started 2 weeks ago but I didnt notice until recently (ie both earlier version and latest update.. I have tried this many times now with no success. My last successful save was in February.

I am now extremely vulnerable with no recent back-up accessible.
How do I fix this???

No response to earlier post. Now an Update:

I have another copy of T3000 on a different PC that I use off-line. This had not been updated for some time.

(I still dont know how to check the current version - there is no “About…” feature. I did find a file called MINI-Revision which showed rev67.8.)

I successfully “Save” to a location/file name .

I then successfully performed a T3000 update.

I then tried to “save” again to the same location as before but with a new file name. Again, the Status line responded - stating “config file success”.
However, the file was NOT saved to the location - nor to anywhere in the Programsx86 / T3000 folder.

Poking around in the programs x86 / T3000 folders I found T3000/database/temp and here I found the last-saved [panel serial no].prog file as well as the folder prg_txt_file which has a complete history of program txt files. This seems to allow an alternate recovery method.

What I conclude from these tests is that the inability to save a .prog file was caused by updating T3000. This seems a serious bug- are any other users affected??