Jump to content

Temp Directory Other Than C:

Issue Bug Report

2 replies to this topic

#1 Gnume

    Member

  • PipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 279 posts
  • Facebook: Link
  • LocationPrattville, AL

Posted 06 May 2015 - 04:01 AM

The MWO Patcher seems to be stuck on using the C: Drive for the Temp Directory no matter what. I click the Gear Icon at the login Screen and Change the location of the Temp Directory to another Drive, yet the patcher STILL wants to use C:. When I click the Gear to change, it first shows up as using the C: and when I click to change, bam, the location I HAD set appears. So no matter WHAT I do, it ALWAYS tries C: location first.

This is a problem for me because my C: is a small SSD for my OS.

My workaround has been to keep clicking OK to the Insufficient Space pop-up and allow the patch to "Complete", then run the Repair Tool because that doesn't seem to use the Temp Directory at all, rather it scans the actual location for the files and replaces them at their actual location. It is an annoying extra step.

Edited by CaptRosha, 06 May 2015 - 04:03 AM.


#2 Krist Smith

    Senior Engineer

  • Developer
  • Developer
  • 629 posts

Posted 06 May 2015 - 09:24 AM

View PostCaptRosha, on 06 May 2015 - 04:01 AM, said:

The MWO Patcher seems to be stuck on using the C: Drive for the Temp Directory no matter what. I click the Gear Icon at the login Screen and Change the location of the Temp Directory to another Drive, yet the patcher STILL wants to use C:. When I click the Gear to change, it first shows up as using the C: and when I click to change, bam, the location I HAD set appears. So no matter WHAT I do, it ALWAYS tries C: location first.

This is a problem for me because my C: is a small SSD for my OS.

My workaround has been to keep clicking OK to the Insufficient Space pop-up and allow the patch to "Complete", then run the Repair Tool because that doesn't seem to use the Temp Directory at all, rather it scans the actual location for the files and replaces them at their actual location. It is an annoying extra step.


I will have a fix for this soon, but in the meantime, when choosing your temp directory, don't select MWOUpdate, choose its parent directory. The patcher is set up to automatically create MWOUpdate within the path that you choose. So, for example, if you want to use D:\Temp\MWOUpdate, then just select D:\Temp as your path, and the patcher will make and use the MWOUpdate directory in that path.

Sorry about all the confusion here, the fix should be out soon.

#3 Gnume

    Member

  • PipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 279 posts
  • Facebook: Link
  • LocationPrattville, AL

Posted 06 May 2015 - 10:13 AM

View PostKrist Smith, on 06 May 2015 - 09:24 AM, said:


I will have a fix for this soon, but in the meantime, when choosing your temp directory, don't select MWOUpdate, choose its parent directory. The patcher is set up to automatically create MWOUpdate within the path that you choose. So, for example, if you want to use D:\Temp\MWOUpdate, then just select D:\Temp as your path, and the patcher will make and use the MWOUpdate directory in that path.

Sorry about all the confusion here, the fix should be out soon.

Ah! Well, then that may resolve it because I think you are correct, I was telling it to use /MWOUpdate but on a different drive. Thanks, I will give that a shot.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users