Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HELP! - ERROR: SETUP UNABLE TO FIND A HARD DISK LOCATION-

1,202 views
Skip to first unread message

Frank J. Merenda

unread,
Dec 26, 1997, 3:00:00 AM12/26/97
to

HELP! I an running WIN95 OSR2 on a P-200 machine with 64 megs of ram. I have
1 gig of free space on my hard drive. I get the message "Setup is unable to
find a hard disk location to store temporary files. Make at least 877KB free
disk space available, and then try running setup again. Error 101" when I
try to install certain programs.
I've tried EVERYTHING I can think of. I went through the knowledge base on
Microsoft's web site, and couldn't resolve the problem. I don't know what
else to try out. It only happens with approx.. 5% of the setups that I run.
If anyone has any idea, PLEASE let me know, thanks! if you could email me
with a response, that would be great, because I don't know when I can head
back to this news group. thanks!!!!
-frank Merenda
fmer...@mindspring.com


Kestutis Sipavicius

unread,
Dec 27, 1997, 3:00:00 AM12/27/97
to

Type SET from a Dos prompt, do you see similar entries to the following? =
Is there a TEMP folder at the assigned location?
TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
COMSPEC=C:\WINDOWS\COMMAND.COM
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
windir=C:\WINDOWS
[TM Errol]

See a reply to Errol:
I figured out what the problem was and how to fix it later on the same day
as my posting. Errol Neilsen's posting from the night before gave me a
clue as to where to look.
Althought c:\windows\temp existed, the DOS environment variables TEMP and
TMP were pointing to c:\windows. Both Windows 95 and Windows/NT will not
put temporary files in their home directories.
I don't know where Windows 95 was managing pointers to the Windows TEMP
directory because I never had the SET= command in my autoexec.bat. There
was nothing evident in the registry relating to this either. I added the
SET= commands to my autoexec.bat and restarted. That fixed the problem.
DOS environment space was already set to 640, so environment space wasn't
an issue.

Frank J. Merenda escreveu ...

0 new messages