Temporary files
Plastic PPRuNer
Thread Starter
Temporary files
OK, found a nice little Seagate 1Gb HDD in the spares box & stuffed it into the main machine as D
Thought I'd keep all temporary files on there to make things tidier and easier to maintain.
Explorer/Internet Options/Temporary Internet Files/Settings/Move Folder seems to have done it for IE 5.5s tempfiles. All tickety boo. Can I now delete what's left in the old CWindows\Temporary Internet files folder????
Now for the other tempfiles. To get some temporary files to shift ya put Set TMP=D:/TEMP in autoexec.bat. So far so good. What about apps that look for the value of the TEMP pointer rather than TMP?
For some reason you're not allowed to ALSO put Set TEMP=DTEMP in autoexec.bat - - If you do Set<enter> it shows it xxxxxed out. WHY NOT? (I also saw this mentioned on some website but they gave no reason just said it wasn't allowed)
Okay, so I tell autoexec to call win.bat, put Set TEMP=Dtemp in win.bat and then got THAT to call win.com. Success. Set<enter> now shows both environmental variables point to DTEMP
Had to tell a few apps where to park their temporary stuff, but everything (so far) seems to work OK and the machine seems perhaps fractionally faster.
Any comments? Good idea? Or have I set myself up for later trouble?
[the D: drive is on a different IDE channel from the main C: drive]
Thought I'd keep all temporary files on there to make things tidier and easier to maintain.
Explorer/Internet Options/Temporary Internet Files/Settings/Move Folder seems to have done it for IE 5.5s tempfiles. All tickety boo. Can I now delete what's left in the old C
Windows\Temporary Internet files folder????Now for the other tempfiles. To get some temporary files to shift ya put Set TMP=D:/TEMP in autoexec.bat. So far so good. What about apps that look for the value of the TEMP pointer rather than TMP?
For some reason you're not allowed to ALSO put Set TEMP=D
TEMP in autoexec.bat - - If you do Set<enter> it shows it xxxxxed out. WHY NOT? (I also saw this mentioned on some website but they gave no reason just said it wasn't allowed)Okay, so I tell autoexec to call win.bat, put Set TEMP=D
temp in win.bat and then got THAT to call win.com. Success. Set<enter> now shows both environmental variables point to DTEMPHad to tell a few apps where to park their temporary stuff, but everything (so far) seems to work OK and the machine seems perhaps fractionally faster.
Any comments? Good idea? Or have I set myself up for later trouble?
[the D: drive is on a different IDE channel from the main C: drive]
Join Date: Feb 2000
Location: New Zealand
Age: 73
Posts: 120
Likes: 0
Received 0 Likes
on
0 Posts
No Mac you have done good work. No nasties awaiting you at all.
Now, if the drive is fast enough (and only time will tell !!), put your windows swap file in there too. Absolutely no problems doing this onto a gash drive. If it goes down - nothing important will be lost.
Clean out all the temp files before you make the switch in PERFORMANCE and then the WIN386.SWP file will be contiguous (all it's ducks in a row and connected) or use Norton Defrag afterwards.
I have run this way for years and it seems to be the way to go.
MG
Now, if the drive is fast enough (and only time will tell !!), put your windows swap file in there too. Absolutely no problems doing this onto a gash drive. If it goes down - nothing important will be lost.
Clean out all the temp files before you make the switch in PERFORMANCE and then the WIN386.SWP file will be contiguous (all it's ducks in a row and connected) or use Norton Defrag afterwards.
I have run this way for years and it seems to be the way to go.
MG
Plastic PPRuNer
Thread Starter
Thanks MasterGreen for your reply & reassurance, though I'm still puzzled as to why one can't set both TMP and TEMP environmental variables in AUTOEXEC - there MUST be a reason for this and I'm still a little uneasy at having tricked the system so. Any ideas anyone?
On another note, I DID bump into a unexpected problem and it may be of interest how to get round it.
I have a removable HDD bay that I use for backups of important files onto a couple of smaller removable HDDs. Stuffed one in tonight and lo and behold, my D drive had become E and the removable HDD was now E: ! Not what I wanted at all and very liable to confuse Windoze! I'd noticed it before, but it hadn't been important. I knew what was happening - DOS/Windows starts by allocating sequential drive letters to all the primary partitions it finds on all the HDDs there are - when THAT is done, then (and only then) will it start allocating the remaining drive letters to any extended partitions that it finds. "There is one relatively simple way to avoid having this letter-shifting happen: don't create a primary partition on any hard disks in the system other than the first one."
"It is perfectly legal to only create an extended partition on a hard disk, and put all of the partitions in it. The only place that a primary partition is absolutely needed is on the first hard disk, because it is required to boot the operating system. You cannot normally boot from an extended partition volume anyway (although some motherboards may let you)." The solution (easy because they were backup volumes) was to delete the primary partition on the removable drives with FDISK and then create an extended partition and a logical DOS drive within that extended partition. Format the new logical DOS drive and away you go. No more shifting drive letters.
I think NT4 and Win2000 allow you to designate drive letters within the OS itself and apparently Partition Magic can also do the job for you without having to reformat and rewrite all your data.
Finally, putting the swap file on a dedicated drive is something that I've read about and considered, but the little Seagate isn't really fast enough. A fast SCSI drive on a fast FSB would be another matter. I was just idly curious and wanted to find a use for the little feller. Fascinating the things you learn... And several apps that write big tempfiles DO seem noticeably quicker.
On another note, I DID bump into a unexpected problem and it may be of interest how to get round it.
I have a removable HDD bay that I use for backups of important files onto a couple of smaller removable HDDs. Stuffed one in tonight and lo and behold, my D
drive had become E and the removable HDD was now E: ! Not what I wanted at all and very liable to confuse Windoze! I'd noticed it before, but it hadn't been important. I knew what was happening - DOS/Windows starts by allocating sequential drive letters to all the primary partitions it finds on all the HDDs there are - when THAT is done, then (and only then) will it start allocating the remaining drive letters to any extended partitions that it finds. "There is one relatively simple way to avoid having this letter-shifting happen: don't create a primary partition on any hard disks in the system other than the first one.""It is perfectly legal to only create an extended partition on a hard disk, and put all of the partitions in it. The only place that a primary partition is absolutely needed is on the first hard disk, because it is required to boot the operating system. You cannot normally boot from an extended partition volume anyway (although some motherboards may let you)." The solution (easy because they were backup volumes) was to delete the primary partition on the removable drives with FDISK and then create an extended partition and a logical DOS drive within that extended partition. Format the new logical DOS drive and away you go. No more shifting drive letters.
I think NT4 and Win2000 allow you to designate drive letters within the OS itself and apparently Partition Magic can also do the job for you without having to reformat and rewrite all your data.
Finally, putting the swap file on a dedicated drive is something that I've read about and considered, but the little Seagate isn't really fast enough. A fast SCSI drive on a fast FSB would be another matter. I was just idly curious and wanted to find a use for the little feller. Fascinating the things you learn... And several apps that write big tempfiles DO seem noticeably quicker.
