16 bit apps in XP

Windows XP >> 16 bit apps in XP I have two 16 bit applications that run just fine when an
XP administrator is logged in, but when an XP limited user
tries to run them, a box pops up:

16 Bit Windows Subsystem

C:\DOCUME~1\karen\LOCALS~1\Temp\. A temporary 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 Ignore

I checked access priviledges on that folder, and both
Windows Explorer and cacls.exe agree the limited user has
FULL (F) rights to the folder. I tried changing the
environment variables to other folders, such as C:\TEMP.
As far as I know, 16 bit apps don't even know about the
registry, so it's not something application specific.

Why will this run as an administrator, but not as a
limited user?

Windows XP1068

Windows XP >> 16 bit apps in XP If you are not afraid of somewaht technical software, get free File Monitor
from www.sysinternals.com. It monitors and logs all file access. I have used
it to find out why some programs wouldn' start (because of missing file or
file permissions).

"Larry 4000" <EMail@HideDomain.com> wrote in message
news:3f5101c37637$012ad910$EMail@HideDomain.com...
> I have two 16 bit applications that run just fine when an
> XP administrator is logged in, but when an XP limited user
> tries to run them, a box pops up:
>
> 16 Bit Windows Subsystem
>
> C:\DOCUME~1\karen\LOCALS~1\Temp\. A temporary 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 Ignore
>
> I checked access priviledges on that folder, and both
> Windows Explorer and cacls.exe agree the limited user has
> FULL (F) rights to the folder. I tried changing the
> environment variables to other folders, such as C:\TEMP.
> As far as I know, 16 bit apps don't even know about the
> registry, so it's not something application specific.
>
> Why will this run as an administrator, but not as a
> limited user?
>

Windows XP >> 16 bit apps in XP Thanks, that did it. I could see they weren't trying to
create files in the directory described in the popup. For
one of the programs I changed some settings in the app to
a directory with write permissions. For the other I
couldn't change the destination, so I had to give
permissions to another directory.

The popup was totally misleading.

>-----Original Message-----
>If you are not afraid of somewaht technical software, get
free File Monitor
>from www.sysinternals.com. It monitors and logs all file
access. I have used
>it to find out why some programs wouldn' start (because
of missing file or
>file permissions).
>
>
>
>"Larry 4000" <EMail@HideDomain.com> wrote in message
>news:3f5101c37637$012ad910$EMail@HideDomain.com...
>> I have two 16 bit applications that run just fine when
an
>> XP administrator is logged in, but when an XP limited
user
>> tries to run them, a box pops up:
>>
>> 16 Bit Windows Subsystem
>>
>> C:\DOCUME~1\karen\LOCALS~1\Temp\. A temporary 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 Ignore
>>
>> I checked access priviledges on that folder, and both
>> Windows Explorer and cacls.exe agree the limited user
has
>> FULL (F) rights to the folder. I tried changing the
>> environment variables to other folders, such as C:\TEMP.
>> As far as I know, 16 bit apps don't even know about the
>> registry, so it's not something application specific.
>>
>> Why will this run as an administrator, but not as a
>> limited user?
>>
>
>
>.
>