>>>>With NT Workstations v4.0, Service Pack 1 that are configured
>>>>to have read-only rights to the root of C, even though the config.fpw
>>>>files are configured to write temporary files to C:\TEMP, an
>>>>error
>>>>"Cannot initialize environment"
>>>>pops up when trying to start our application.
>>>>When the rights for the root of C are changed to not just be read
>>>>only, the application starts fine.
>>>>We need to have these NT stations with read-only rights to the
>>>>root of C.
>>>>Any thoughts?
>>>
>>>RESOURCE=OFF in CONFIG.FPW, or pointed elsewhere where they do have rights, or put a FOXUSER.DBF and FPT there, flagged as read-only.
>>
>>This will not solve the problem. The temp files could be pointed to a network drive, but it will slow down the application.
>
>I've assumed that rights to C:\TEMP were explicitly granted, and not inherited downwards; if this isn't the case, then explicit granting of rights in the C:\TEMP directory is necessary, if that's where the problem lies. Unfortunately, what we are missing is the startup directory; if it's the root of C:, FOXUSER is the probable error.

A couple of other thoughts this morning (I'm not so sleepy now). Try the WinNT temp directory (which is not C:\TEMP) or the user's profile directory.