Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to setup a RAM disk for various purposes and among them I would want to set the TEMP variable to point to a folder in the RAM disk. I haven't done this yet, but the RAM disk will be initialized before logging on and I have a certain problem:

If for some reason the RAM disk fails to start, what will the result be? The TEMP variable will still point to F:\Foo, yet the F: drive will not exist.

Additionally, what will happen if I don't set a TEMP variable in the environment variables?

share|improve this question
up vote 1 down vote accepted

Windows actually sets 4 "temp" variables:

TEMP and TMP for the current user, plus TEMP and TMP for the system. (Scroll through the list of system variables to see them.) So if you don't set them, nothing bad will happen because Windows does it for you.

As for setting it to a nonexistent drive or folder, that depends on the application. Well-written applications check if an object or setting exists before trying to use it, and abort gracefully if it does not exist. Bad applications just display a sometimes-useless error, or they just crash.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .