Question:
installing adobe reader on vista - problem
I tried to install adobe reader 8.0 onto my notebook but i keep getting this error:
The Temp folder is on a drive that is full or is inaccessible. Free up space on that drive or verify that you have write permission on the Temp folder.
does anyone know what does that mean and what I'm supposed to do in order to solve the problem? thanks a lot i appreciate any help.
Answer:
Re: installing adobe reader on vista - problem
have enough free disk space? call set up via vista xplorer?
alternative is that foxit reader works better under vista then adobe reader
cheers ...
Answer:
Re: installing adobe reader on vista - problem
i have plenty of free disk space seeing how i only have one partition and it's got 65G's free...
what is call set up via vista explorer? I use firefox.
I'll look into foxit. Thanks ghn!
Answer:
Re: installing adobe reader on vista - problem
just installed foxit, nice program, good recommendation. thanks
Answer:
Re: installing adobe reader on vista - problem
many installations must be called inside vista (windows) explorer - this is a security thing within vista - to set up correctly.
i hope that this is a temp bleep within vista.
glad to hear u enjoy foxitreader (under help, there is a check for update - recommend running it)
cheers ...
Answer:
Re: installing adobe reader on vista - problem
thanks!
I'll see if it happens with any other programs I install in the future.
toodles,
Answer:
Re: installing adobe reader on vista - problem
I see you got a solution to your problem. I encountered the same issue, and solved it by using this guide. Maybe somebody else will find it useful.
Answer:
Re: installing adobe reader on vista - problem
Right clisk and run as administrator or disable UAC in CP ;)
ps. Acrobat reader 8.0 is working fine here
Answer:
Re: installing adobe reader on vista - problem
I had a similar problem (disk space errors) when trying to download some apps on my roommate's new Vista PC. I changed the download directory and it fixed it. The REALLY weird part is that I changed the download path back for the next file and it was fine. :confused: Whatever... it works fine now.