Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 2 post(s) |
xarjin
Gallente Center for Advanced Studies
|
Posted - 2011.01.23 00:28:00 -
[1]
Edited by: xarjin on 23/01/2011 00:28:24 I was just updating my sisi client I have stored on a 6TB intel raid 5 array on windows 7 x64 to discover the client autopatcher appears to believe my 6TB raid 5 array has insufficient free disk space which is naturally incorrect. I'm uncertain if this has something to do with the array having a GPT mft type which is recommended for arrays larger than 2TB in total size.
|
Jokiller Solarius
Lantean Industries
|
Posted - 2011.01.23 12:09:00 -
[2]
Edited by: Jokiller Solarius on 23/01/2011 12:09:45 autopatcher use's your systems primary drive to install its temp files to not where the game is installed |
Daneel Trevize
Black Viper Nomads
|
Posted - 2011.01.23 12:36:00 -
[3]
I believe I had a similar error on XP for the first time I tried to get the TQ 1.1.1 patch a few days back. Looked at my drives and none seemed to have less than a few gigs of free space. Closed and relaunched the client and it worked fine on the second go. |
|
CCP Atropos
|
Posted - 2011.01.23 13:18:00 -
[4]
Originally by: xarjin Edited by: xarjin on 23/01/2011 00:28:24 I was just updating my sisi client I have stored on a 6TB intel raid 5 array on windows 7 x64 to discover the client autopatcher appears to believe my 6TB raid 5 array has insufficient free disk space which is naturally incorrect. I'm uncertain if this has something to do with the array having a GPT mft type which is recommended for arrays larger than 2TB in total size.
http://img7.imageshack.us/img7/3108/evespace.png
This is an issue that we are aware of, but unfortunately we don't have a fix for it. I believe it's a 32bit issue where large drives cause an overflow with the size calcuations. |
|
|
CCP Atropos
|
Posted - 2011.01.23 13:21:00 -
[5]
Originally by: Jokiller Solarius Edited by: Jokiller Solarius on 23/01/2011 12:09:45 autopatcher use's your systems primary drive to install its temp files to not where the game is installed
This is a seperate issue and is really only something you can change. The installer asks the operating system for it's temporary storage location, which the OS usually returns as C:\temp, or similar. It's controlled, on Windows at least, by the %temp% environment variable. |
|
Xyfu
Minmatar Applied Mechanics
|
Posted - 2011.01.24 07:57:00 -
[6]
Originally by: CCP Atropos
Originally by: Jokiller Solarius Edited by: Jokiller Solarius on 23/01/2011 12:09:45 autopatcher use's your systems primary drive to install its temp files to not where the game is installed
This is a seperate issue and is really only something you can change. The installer asks the operating system for it's temporary storage location, which the OS usually returns as C:\temp, or similar. It's controlled, on Windows at least, by the %temp% environment variable.
Hahah, no it doesn't, it automagically always writes to c:\
Tell it to stop. I have to manually patch every time, with the help of a certain Chruker, 'cause I have about 13MiB free on c:\, and about 27GiB free on D:\. _____ ^ That is a sig line. It should be there without me having to put one in. |
Xyfu
Minmatar Applied Mechanics
|
Posted - 2011.01.26 03:16:00 -
[7]
Originally by: Xyfu
Originally by: CCP Atropos
Originally by: Jokiller Solarius Edited by: Jokiller Solarius on 23/01/2011 12:09:45 autopatcher use's your systems primary drive to install its temp files to not where the game is installed
This is a seperate issue and is really only something you can change. The installer asks the operating system for it's temporary storage location, which the OS usually returns as C:\temp, or similar. It's controlled, on Windows at least, by the %temp% environment variable.
Hahah, no it doesn't, it automagically always writes to c:\
Tell it to stop. I have to manually patch every time, with the help of a certain Chruker, 'cause I have about 13MiB free on c:\, and about 27GiB free on D:\.
I should mention my TEMP variable points to D:\temp\temp and my TMP points to D:\temp\temp\tmp, so there should be no writing to C:\ ever. _____ ^ That is a sig line. It should be there without me having to put one in. |
Blue Harrier
Gallente
|
Posted - 2011.01.26 14:17:00 -
[8]
Originally by: CCP Atropos
Originally by: Jokiller Solarius Edited by: Jokiller Solarius on 23/01/2011 12:09:45 autopatcher use's your systems primary drive to install its temp files to not where the game is installed
This is a seperate issue and is really only something you can change. The installer asks the operating system for it's temporary storage location, which the OS usually returns as C:\temp, or similar. It's controlled, on Windows at least, by the %temp% environment variable.
While I believe the above is inherently true, in Windows 7 it may not be actually true.
I believe, and I will test this with the next patch to confirm, that in Windows 7 while the autopatcher and the downloader exe file patcher do use the 'TEMPÆ or æTMPÆ variable, it does not use the one everyone thinks.
In Windows 7 (and maybe others I canÆt check) there are two TEMP and TMP variables. One is the system variable TEMP (or TMP) and points to (usually), C:\Windows\TEMP.
The other is the user variables TEMP and TMP and both point to (again usually) %USERPROFILE%\Appdata\Local\Temp
IÆm pretty sure it is the latter Temp the patchers use to store the unpacked and or downloaded files in before they are installed.
So users may change the location of the system variable TEMP or TMP but it may be the incorrect one. As a test before updating one of my computers I shall change the location of the user variable and leave the system variable as is before tomorrows update and see where the patcher drops all the junk. If IÆm correct IÆll get back to you.
|
Blue Harrier
Gallente
|
Posted - 2011.01.28 15:14:00 -
[9]
I can confirm at least for TQ, the eve update patch I downloaded and installed yesterday did use the modified user variable TEMP that normally points to %USERPROFILE%\Appdata\Local\Temp.
I changed this to E:\TEMP using the [Edit] button and the patcher dropped a bunch of files into this new location. It might be worth someone trying to modify both locations of TEMP and seeing if they can fool the patchers into unpacking files on to another partition.
|
Xyfu
Minmatar Applied Mechanics
|
Posted - 2011.01.28 17:37:00 -
[10]
Originally by: Blue Harrier I can confirm at least for TQ, the eve update patch I downloaded and installed yesterday did use the modified user variable TEMP that normally points to %USERPROFILE%\Appdata\Local\Temp.
I changed this to E:\TEMP using the [Edit] button and the patcher dropped a bunch of files into this new location. It might be worth someone trying to modify both locations of TEMP and seeing if they can fool the patchers into unpacking files on to another partition.
Which [Edit] button is this? _____ ^ That is a sig line. It should be there without me having to put one in. |
|
Blue Harrier
Gallente
|
Posted - 2011.01.28 22:38:00 -
[11]
Sorry should have been clearer in my post, the [Edit] button is found in Windows 7 (not the Eve client) by doing the following;
Click the Start button Right click the æComputerÆ selection on the right menu. Select and click the æPropertiesÆ selection On the System window that opens find and click æAdvanced system settingsÆ (left side bar) The System Properties window will open, near the bottom of this window is an [Environment Variablesà] button Click this button to open the Environment Variables screen, the user variables and system variables are here and so is the [Edit] button for each variable.
Note: make a new TEMP folder on the drive where you wish the files to be unpacked before you edit the variables, then point the User variables to this folder.
Results may vary
|
Xyfu
Minmatar Applied Mechanics
|
Posted - 2011.01.29 00:10:00 -
[12]
Windows 7 is for casuals. WinXP ftw. _____ ^ That is a sig line. It should be there without me having to put one in. |
Batolemaeus
Caldari Free-Space-Ranger Morsus Mihi
|
Posted - 2011.01.30 10:46:00 -
[13]
Originally by: Xyfu Windows 7 is for casuals. WinXP ftw.
WinXP works exactly the same if you have set it up properly. As in, you do not have admin rights and have to start processes that need elevated rights via runas.
Obviously, the environment variables for a process launched by a different user will be different from those used by the user who is logged in.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |