Twitter
Powered By
Powered by Squarespace
Navigation
« DC++ "Could Not Open Target File" Error | Main | New S92A Proposal Up »
Sunday
Dec202009

My Borderlands Troubles

Being a Good Consumer

Last week I purchased the Borderlands DLC, Zombie Island of Dr Ned, for my PC Retail version of Borderlands. After purchasing it I was informed I would also have to install the 1.1 update so that was downloaded as well.

We've Got a Problem

My first attempt to update Borderlands resulted in a catch-all error dialog informing me that the update had failed. After looking on the Gearbox forums I got pointed at running the update from the command prompt using the "msiexec" program. http://gbxforums.gearboxsoftware.com/showthread.php?t=87233 - (FIX) Fatal Error:Installation ended prematurely because of an error. This resulted in the patch doing the same "Gathering information about your computer" routine as the original patch attempt and silently exiting without doing anything. A quick check on the "msiexec" program's help dialog showed a logging flag which I set and posted the output of that and the dxdiag output on the Gearbox forums. http://gbxforums.gearboxsoftware.com/showthread.php?p=1721935 - Unable to Install Patch or Zombie DLC - Windows 7 - Error 1603

You Didn't. Did You?

This is when things got interesting. Soon after I read a new post of someone having a similar problem as me and posted a suggestion to run the "msiexec" program with the logging flag set. A reply post by another member to mine said that would be pointless as "we know where the patch is try to write to" This gave me an idea which prompted me to look through the "msiexec" log to try and answer. A quick search for the drive that I installed Borderlands to (E:) found nothing. A search for the 32 and 64 bit Program Files directories on the C drive found both. Now my question was a pretty simple one, did the patch and DLC require that the game be installed in the Program Files directory on the C drive? A question in the FIX thread brought no answer after several days so I decided to give it a go and reinstalled Borderlands to my "C:\Program Files(x86)\" folder.

You Did

And guess what, the patch and DLC installed without a hitch.

For a game developer to not allow the patch to be installed to wherever the program has been installed is just unacceptable when every other game I have patched has never required it.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (4)

This is indeed kind of stupid, might have just been something simple that's been overlooked by em. Make sure you tell the developers though so they can fix it.

January 14, 2010 | Unregistered CommenterXeross

Woah, I didn't even know people commented on my blog.

Xeross,

I did make a post on their forum in both the threads I commented in so hopefully it does make it to a developer or two.

February 22, 2010 | Registered CommenterJames

It's important you tell the developers. Errors can be very annoying. Or perhaps there are other similar programs that will work well with your PC.

Steve Kerr
www.ohealthlounge.co.nz

December 9, 2010 | Unregistered CommenterSteve Kerr

broski, im hoping you see this. i have a similar problem with my goty borderlands. also, in terms of computing, i am a push button, recieve content kind of guy. can you explain all that in english please? i had to install borderlands the msiexec way. im guessing that has something to do with it. i push the button that should download, and lo and behold, internal error 2738. dont know what the hell that means. my email is thatguy0808@hotmail.com

June 9, 2013 | Unregistered CommenterTim the Enchanter

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>