TEMP & TMP Translation

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When we open a command promt and type "SET" we see this:

TEMP=C:\DOCUME~1\user\Local Settings\Temp
TMP=C:\DOCUME~1\user\Local Settings\Temp

This should be :

TEMP=C:\DOCUME~1\user\LOCALS~1\Temp
TMP=C:\DOCUME~1\user\LOCALS~1\Temp

So not the whole path is translated to 8.3 notation only the first part.
We have ben unable to find a way how to control this function.

Can anyone help.
 
From: "IVPCB" <[email protected]>

| When we open a command promt and type "SET" we see this:
|
| TEMP=C:\DOCUME~1\user\Local Settings\Temp
| TMP=C:\DOCUME~1\user\Local Settings\Temp
|
| This should be :
|
| TEMP=C:\DOCUME~1\user\LOCALS~1\Temp
| TMP=C:\DOCUME~1\user\LOCALS~1\Temp
|
| So not the whole path is translated to 8.3 notation only the first part.
| We have ben unable to find a way how to control this function.
|
| Can anyone help.

But does it work ? Do you have a problem where temporary file are not going to where the
Environmental variables point ?

If you do; point it to; %windir%\temp
 
If you paste
C:\DOCUME~1\user\Local Settings\Temp
into Start | Run , does the same folder open as when you type
%tmp%
or
%temp%
into Start | Run?

C:\DOCUME~1\WESLEY~1.VOG\LOCALS~1\Temp
C:\DOCUME~1\WESLEY~1.VOG\Local Settings\Temp
%tmp%
%temp%
and
%USERPROFILE%\Local Settings\Temp
all open the same folder here.

%windir%\temp is the System Environment Variable.
Start | Run | Type: temp | Click OK

%tmp% and %temp% are User Environment Variables.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
No unfortunatly it dos not work.
Problem is thet when we try to run a batch file from the temp folder we
receive a massage that C:\DOCUME~1\user\Local is not a valid command.
 
I fully agree with you all mentioned options point to the same user folder.
But thats OK

Fact is that bij entering them into Start > Run you us full 32 bit paths and
not 8.3 translation.

Open a command prompt an try a command like this
C:\DOCUME~1\WESLEY~1.VOG\Local Settings\Temp\batfile.bat

You will be informed that C:\DOCUME~1\WESLEY~1.VOG\Local is not a valid
command.
 
From: "IVPCB" <[email protected]>

| No unfortunatly it dos not work.
| Problem is thet when we try to run a batch file from the temp folder we
| receive a massage that C:\DOCUME~1\user\Local is not a valid command.

Then change the environmental variables to point to; %windir%\temp

If the user has limited rights to the folder, change the NTFS permissions to give full
Read-Write-Delete rights to this folder.
 
That will work we have tried that already.
So this can be a workaround.

Not all machines seem to have this behavior some work fine with the full
paths translated to 8.3.
So we would prefer to have all machines and users stick to using the
standard temp folders.
 
Put quotation marks around Local Settings like this:

C:\DOCUME~1\user\"Local Settings"\Temp\batfile.bat

Good luck

Nepatsfan
 
is it possible that you have disabled the generation of 8.3 filenames?
some tweaking utils have this ability (cacheman is one). it can speed up
ntfs operations, but is generally not recommended. But diehard tweakers
often don't listen, and tweaking utils often make things sound so rosey...

check it w/ this command (in a cmd window):

fsutil behavior query disable8dot3

if it returns a 0 then it is not disabled, and you're ok. if it returns a
1 then it is disabled; to turn 8dot3 back on give this command:

fsutil behavior set disable8dot3 0

reboot to make the change take effect, then retest your issue.
 
Back
Top