16 bit windows subsystem error msg temp file missing???

[Guest]

While trying to install/upgrade some software/hardware the following error
message appears:

16 BIT WINDOWS SUBSYSTEM (on a blue background)

(the rest of the message is within the error message window)
C:\Documents and Settings\Me\Local Settings\Temp\
"A temp file needed for initialization could not be created or could not be
written to."

Anyone know what's missing?
Thanks
Stephen
(e-mail address removed)

 

[Guest]

Hey, Stephen,
It's Paul, great exchanging emails with you about this issue, just bought a
new printer today because my 16-bit based printer didn't work anymore. Tried
a few more things on our mutual C:\Documents and
Settings\Owner\LocalSetting\Temp problem, went into safe mode and tried
looking at the permission settings on a new user I created. No go, this is a
virulent problem we've got or should I say, you had. Don't want to reformat
my drives just yet. The new printer works real nice with the USB cable and
all. I'm posting to this forum because if anyone else runs into this
problem, my advice is.....FORGET YOUR 16-BIT PROGRAMS! They aren't worth the
hassle of trying to flesh out this problem. I should know, I've spent crazy
amounts of time on it. Work around it, buy new software/hardware whatever
and enjoy your life

Paul

 

[Malke]

Hey, Stephen,
It's Paul, great exchanging emails with you about this issue, just
bought a
new printer today because my 16-bit based printer didn't work anymore.
Tried a few more things on our mutual C:\Documents and
Settings\Owner\LocalSetting\Temp problem, went into safe mode and

(snip the rest of email)

Hey Paul, you posted to a Usenet newsgroup instead of sending your
friend a private email.

Malke

 

[Guest]

Hi, Malke,
If you read the last couple of lines of my post, you'll see my rationale.
By the way, I had a pretty good sized thread going on this bug and it has
vanished from the group. Wanted to give an update and poof, the entire
thread was gone. My post was fresh-dated compared to some others in there
and I wanted to give an update, but used Stephen's instead. I figure maybe
some newsgroup administrator didn't like it for some reason.
Paul

 

[Malke]

Hi, Malke,
If you read the last couple of lines of my post, you'll see my
rationale. By the way, I had a pretty good sized thread going on this
bug and it has
vanished from the group. Wanted to give an update and poof, the
entire
thread was gone. My post was fresh-dated compared to some others in
there
and I wanted to give an update, but used Stephen's instead. I figure
maybe some newsgroup administrator didn't like it for some reason.
Paul

Usenet doesn't work that way. Unless your original post was very old, it
would have still been here. Since you've posted using the web
interface, that is probably why you can't find it. Using a real
newsreader is a much better way to access these groups.

Now you've created a new thread which is orphaned from the original
problem. These newsgroups, while observed by MS, are not moderated.

Since I don't know anything about your original problem, I'm afraid I
can't help you. If you are still having difficulties with the 16-bit
error, here is some informatoin that may help:

Error message when you install or start an MS-DOS or 16-bit
Windows-based program:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767&Product=winxp

This can also be caused by malware.

Also, AVAST (antivirus software) can be the cause if you have WinXP SP2
installed:

http://groups.google.com/[email protected]

You can put back the standard version of autoexec.nt/config.nt by
copying a backup copy held in %windir%\repair\ to %windir%\system32\
(%windir% is typically C:\Windows) instead of using the procedure in
the KB article above.

If that doesn't address your problem and you still need help, please
post back to *this* thread with the details.

Cheers,

Malke