It was so vague because it was moved without the portion of the earlier thread that somewhat explained it. So, here goes again.
Windows XP Pro. One user is Admin. rights with password, second user is no password, restricted. All has been lovely and fine with program, Jetform Form Filler. Suddenly the "16 bit Windows Subsystem" window appears with the statement "C:\docume~1\Pat\Locals~1\Temp\. A temp file needed for initialization could not be created or could not be written to. Make sure that the directory path exists, and disk space is available. Choose close to terminate the application." Close and Ignore both result in Close.
If I change the account type the program runs fine so obviously there is disk space and the path does exist and is correct.
I created a new account with restrictions and same thing. Change the account type and happiness.
This may be a hint. Between the two users with restrictions, when the path appears in the 16 bit window, the path is Docume~1\USER THAT IS LOGGED ON\Locals~1\temp\.
Of course, with the Administrator that works fine I have not really good way of seeing what path it is attempting to address but I know that even though the only thing I change is the account type, the program runs fine if I do change the account type.
I am sure it is simple. I am.
I have seen many posts having to do with this that resulted right after the update to SP3. I have a repair shop. I know the headaches that come up with SP3 is not fully installed or correctly installed. I even generally know how to remove SP3 and do it correctly. I don't understand why this has been running fine for a few months and now decides not to. I am going to continue to remove updates and reinstall correctly but if you folks have a clue that would sure be helpful.
No hardware has been changed. AMD Athlon - but as I have stated, has run for a few months and then BAM!
Thanks for being patient.
Edited by louhardt, 29 January 2011 - 05:57 PM.