16 bit windows subsystem error in XP
Neiman
When I login to WindowsXP/SP2 as a normal user I get the following message:
16 bit windows subsystem
C:\DOCUME~1\Bob\LOCALS~1\Temp\. A temporary file needed for the
initialization could not be created or could not be written to. Make sure
that the directory path exists, (it does) and disk space is available (it
is). Choose 'Close' to terminate the application.
Close Ignore
Regardless of the choice I make, everything is fine after that. Can anyone
tell me how to resolve this? It doesn't happen with admin accounts.
Thanks.
Don Phillipson
news:M4CdnakDudu2d53V...@comcast.com...
> When I login to WindowsXP/SP2 as a normal user I get the following
message:
>
> 16 bit windows subsystem
>
> C:\DOCUME~1\Bob\LOCALS~1\Temp\. A temporary file needed for the
> initialization could not be created or could not be written to.
Any file call at boot to any file in a /Temp directory
is likely to be due to bad coding of some instal routine.
Good code may write files to /Temp folders (because
needed by an instal routine but not a functioning part of
the app, thus not to be written permanently to /Program
Files or /Windows) but also deletes these these as it
completes and exits.
Follow your normal security routine (which may include
adding a System Restore point) then delete all contents
of C:\DOCUME~1\Bob\LOCALS~1\Temp\
and reboot. You will probably never see this messaga
again. In case of trouble repost to (only) the likeliest MS NG.
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)
philo
have a look in windows\system32 to see if you have autoexec.nt
if not, there should be a spare copy in the windows\repair folder that you
can copy over to the system32 folder
Touch Base
on the system. Have you done any scans to eliminate this possibility?
Michael
programs on startup or else it may be a failure of an old virus.
Please check that you get suitable permissions in
shannon saylors
>> On Saturday, April 12, 2008 1:20 PM Don Phillipson wrote:
>> "Neiman" <crk...@comcast.net> wrote in message
>> news:M4CdnakDudu2d53V...@comcast.com...
>>
>> message:
>>
>> Any file call at boot to any file in a /Temp directory
>> is likely to be due to bad coding of some instal routine.
>> Good code may write files to /Temp folders (because
>> needed by an instal routine but not a functioning part of
>> the app, thus not to be written permanently to /Program
>> Files or /Windows) but also deletes these these as it
>> completes and exits.
>>
>> Follow your normal security routine (which may include
>> adding a System Restore point) then delete all contents
>> of C:\DOCUME~1\Bob\LOCALS~1\Temp\
>> and reboot. You will probably never see this messaga
>> again. In case of trouble repost to (only) the likeliest MS NG.
>>
>> --
>> Don Phillipson
>> Carlsbad Springs
>> (Ottawa, Canada)
>>> On Sunday, April 13, 2008 4:58 AM philo wrote:
>>> have a look in windows\system32 to see if you have autoexec.nt
>>>
>>> if not, there should be a spare copy in the windows\repair folder that you
>>> can copy over to the system32 folder
>>>> On Monday, April 14, 2008 9:23 AM Touch Base wrote:
>>>> Could also indicate that some badly written spyware/trojan failed to install
>>>> on the system. Have you done any scans to eliminate this possibility?
>>>>> On Tuesday, June 10, 2008 4:33 AM Michael wrote:
>>>>> Neiman wrote:
>>>>> If you get this error on logon, you have probably added some 16-bit
>>>>> programs on startup or else it may be a failure of an old virus.
>>>>> Please check that you get suitable permissions in