Re: 16 bit subsystem problems

From: Alan Illeman (illemann_at_surfbest.net)
Date: 07/16/04 

Date: Fri, 16 Jul 2004 18:28:55 -0400

"Doctor Arcane" <docarcane@altavista.net> wrote in message
news:1ceb9ea2.0407160629.2fe30a44@posting.google.com...
> "Alan Illeman" <illemann@surfbest.net> wrote in message
news:<10fdlbp9i63vu5d@news.supernews.com>...
> > "Doctor Arcane" <docarcane@altavista.net> wrote in message
> > news:1ceb9ea2.0407150627.d0ce75c@posting.google.com...
> > > I am attempting to run some older applications on a Windows 2000
> > > machine, under a non administrator acccount. I keep getting the
> > > following error:
> > >
> > > 16 BIT WINDOWS SUBSYSTEM C:\TMP A temporary file needed for
> > > nitialization could not be created or could not be written to. ...
> > >
> > > To answer the obvious: yes, there is enough space, yes the account
> > > does have necessary permissions on the directory and all children
> > > present in the directory. I tried setting the TEMP/TMP environment
> > > variables to C:\TMP thinking the path might be giving it issues. I
> > > tried making the user a power-user, I also tried enabling windows 95
> > > compability mode. I looked at the config.nt and autoexec.nt and found
> > > nothing out of the ordinary. Every 16-bit app like command.com
> > > generates this error. These are public access machines, so I do not
> > > want the account to be an admin.
> > >
> > > I would love any ideas, I'm all out.
> >
> > . . .but did you actually go ahead and create "C:\TMP"? (I had a
> > similiar problem)
>
>
> Yes, I created C:\TMP and set the permissions to allow Everyone to write.

Just creating it, solved it for me, but I did give Everyone full control of
it.