32 réponses à ce sujet

[Unicrone]

So I've done some experimentation, and I'm able to both reproduce how to get the error code when patching, and how to stop it happening. It's a bit of a pain, but if you can't get the patch to work, this should fix it. I've tested this multiple times on three separate machines (an XP-SP3 box, a Vista x32 box and my gaming Win7 x64 rig), and it's worked each time.

First of all, you must uninstall EVERYTHING related to dragon age: origins. Move your save games to a flash drive or different hard drive, if you want to keep them. Don't leave them on your install drive. Also get rid of the M$ C++ redistributable and Nvidia PhysX, if it was installed or updated by DA:O.

Download and install Crap Cleaner: http://www.ccleaner.com 
It's a freeware app, and works on all forms and flavours of windows. It's best on Vista / win7 machines though.
XP users should stick to RegSeeker, available from http://www.hoverdesk.net/freeware.htm

After doing that, reboot.

Before continuing, disable Vista / Windows 7's UAC. It will cause problems when running the patcher. The instructions on how to do so are easy enough to find with a quick google search. Turn it back on when you're finished installing everything.

Pop your disc in the drive (or start the install process, however it works for online purchasers) and run the setup directly from the disc, not from the autorun. Do a custom install, even if you don't change the target folder or anything else, and then let the install run. When it's finished, run CCleaner or RegSeeker again, then reboot.

[Edit] I've been in contact with a few people who were still getting the error when patching. If all this fails, try booting in to the windows safe mode before running the patch. It's easy to forget about it., but it did finally cure the damned [36] error for some. [/Edit]

Turn off any Anti-Virus Software, then block anything related to DA:O in the windows firewall from accessing the net (even if you use a 3rd party one or none at all). Run the patch exe from wherever you downloaded it to (I've always gotten the [36] error if I copy the patch to another folder and run it from there), and everything should go through.

Reinstall your DLC / Mods, unblock DA:O from the firewall, restore your AV and windows UAC, and you should be off and running.

------------

I caught a message at the end of the external installer that made mention of "old files" every time I got the [36] error, so my assumption is that previous patches / installs are leaving files in a temp folder somewhere that the patcher can't overwrite.

If this fails (which it shouldn't), pm me and I'll see if there's any other help I can give.

Modifié par Unicrone, 01 janvier 2010 - 06:49 .

[Unicrone]

One more thing, I've mentioned it before, but DO NOT install patches prior to the 1.02a patch when you do a fresh install of DA:O. If you do, you'll get the error 36 every time. Same if you have DLC or mods installed before you try to patch. Something screws up. I don't know what, but considering all of the other technical faults with the engine, I'm not surprised. Bioware should have used the version of the Aurora Engine that the mob who made The Witcher modified.

[5anctuary]

It worked! Thank you very much for sharing this knowledge with us )))) Now that we have 1.02 we don't need patch 1.01 right?

[Unicrone]

No. If you install any of the patches prior to 1.02a you'll get the error [36] when trying to install. 1.02a has all the fixes from the previous patches in it, anyway.

[5anctuary]

Is there a way to verify if the patch is installed correctly or not ?

[Unicrone]

Yes. In the launcher, click the "configure" button, then click on the "game" tab. If you're all patched up, the versions should read as



1.02

1.01

1.03

1.03

[Karatanthala]

That's all very well, but how do you get patch 1.02? The patch page tells me I'm downloading 1.02 but only gives me 1.01

[Karatanthala]

Google is my friend! Downloaded the patch from IGN.



Slightly off-topic... is anybody else getting concerned for Star Wars The O;d Republic? If Bioware/EA can't handle the minimal online requirements for Dragon Age, how can they hope to run an MMO?

[5anctuary]

Huh?! It says

1.00

1.01

1.03

1.03

I didn't receive error [36] the last time and the patch installed completely I hope they'll release a fix or something...

[Jimtp]

i rly hope they fix it because i rly cant uninstal and block all those files(im afraid that ill mess up things)

[Michael Suede]

You don't have to uninstall the whole game to make it work.

In this post I detailed how I resolved my black screen lock up problem.  Part of that resolution involved overcoming an "error 36" when attempting to apply the patch to a re-install of the game.

I've noticed others in here experiencing the same problem so I thought I would detail a post on how to resolve it so others can find it easier.

The relevant part:

I also recommend deleting everything you can in the "C:/Users/'your username'/AppData/Local/Temp" folder...  Also delete any log files that may be in your "documents" folder related to the game. - this is above the Bioware directory.  If you have patched before, these logs may interfere with reapplying the patch to a fresh install of the game.  Deleting the temp data and logs will prevent the "error 36" from occurring when applying the patch again. (obviously I ran into this problem, one of many I encountered during this ordeal.)

So to sum up, delete everything in your temp directory, delete any dragon age logs in your documents directory, and reboot.  

I believe the temp folder is hidden by default so you'll have to type in the full path.  Remember to put your windows username where it says "your username".

This should resolve the patching issue.

Modifié par Michael Suede, 30 décembre 2009 - 05:35 .

[Unicrone]

I also recommend deleting everything you can in the "C:/Users/'your username'/AppData/Local/Temp" folder...  Also delete any log files that may be in your "documents" folder related to the game. - this is above the Bioware directory.  

Those log files are also placed in the users/documents folder on some windows 7 x64 machines. They also have to go.

I recommended using CrapCleaner because it automatically finds and deletes files in the temp and hidden folders. I know some people do not like delving into their systems, and this app does it safely and securely.

[Wizard-69]

Installing the Patch in the safe mode worked fine. Thanks for this tip

[Doodeyfoodle]

Unicrone, thank you so much for your excellent, well-written help. It worked for me. Since I was following your instructions to the letter, I did notice one small omission: in your third paragraph you instruct users to download and install Crap Cleaner, but never actually say to run it, yet you mention to "run CCleaner . . . again" later on. Obviously you meant for me to run it after downloading.



I'm not nitpicking here: your instructions are so detailed (and users like me so appreciative) that I thought I would just point-out a way to make your instructions even more accurate. Thanks again. If Bioware/EA have any brains, they should send you a small cheque for having done some of the work they should be doing themselves to support their own product.

[Jimtp]

ok this might sound noobish but how i run safe mode on vista

[Nycterida]

hold down F8 when booting up.

[Silent Rogue]

Do I have to worry about CCleaner deleting the game itself at all when using it?

[Silent Rogue]

Nevermind... Error 36 still comes up though after I've just used CCleaner.

[AgentOfAtlas]

Well, I've tried a LOT of things. UAC off, cleaning all temporary files, CCleaner, Safe Mode, reinstalling the game from scratch... nothing works, and I still get the error 36.

I'm the type to usually roll my eyes and scoff quietly at people doing absurdly excessive rages on forums over minor issues, but I have to say I'm incredibly frustrated by all of this, and I've wasted almost the entire day trying to solve this issue. That's a lot when I only have time to play on weekends as it is.

Does anyone know when the next patch is due, as I'm hoping it will use a less problematic scheme than the current piece of crap?

Edit: Or is there anyway to "manually" install the patch contents? I'm more than willing to do it that way.

Modifié par AgentOfAtlas, 31 janvier 2010 - 10:26 .

[spkeyhdgehog]

have you tried applying the patch in safe mode? i tried everything with no luck and finally had success in safe mode.

[BellyBen]

the point is why should we have to delete stuff off or change stuff?? some of us dont want to in case we mess things up! The point is EA/Bioware/Adminstrators here should be addressing this problem, its not like only 1 person has the problem or they dont know about the problem! I mean an acknowledgment they are aware of the problem would be a start and especially as in order to play "Return to Ostagar" you need patch 1.02 (funny how it doesnt mention that when you buy it though eh??). Its just really rubbish customer service....you would have thought a company with so much "expertise" could have sent all its customers an email (seeing as we get loads about buying new stuff anyway!!) saying that some people may be experiencing problems etc etc but hey why fix something after u have our money........... cant wait for the expansion pack patch it will probably blow my computer up

[BrnBeDestine]

Im getting it as well some items from the dlc pack go missing just vanishes but It has to do with the patch because Im getting the same error. By the time the expansion comes out I don't want to see things like that happen.

Modifié par BrnBeDestine, 12 février 2010 - 06:49 .

[rarebreed4320]

same. its bs that the people have to find away around to fix a problem that bioware should have found a solution for. i still havnt been able to download the patch and i already bought return to ostagar. im not to computer savy so i dont really want to try the way everyone else got their patches to work since i most likely will cause my computer to self destruct.

[Navy557]

ok i think i fu**ed up my dragon age... i installed the patch i got an error but it wasn't error 36. so i re-downloaded the patch and it worked fine. Then i ran the game and on the DLC RTO the game version required thing had 1.02a in red so i figured that it didnt install so i tried to reinstall it i got the error 36. then i tried to get the older patch to like Refresh it or something then i ran the exe for 1.02a then i got error 36 again... did i fu** up my dragon age by trying to run the older patch?? and when i try to install the 1.02a it goes real fast and says already installed and stuff then 1/3 of the DL the error pops out i dont think i installed all the 1.02a content its like fragmented.

[Miriel Amarinth]

I'd say just reinstall from scratch Navy557, especially if you have the disc version as it will take less time than trying to figure out how to fix a botched install. Make sure to back up your savegames just incase and after reinstalling the basic game from the discs, apply the 1.02a patch directly (and dont use any of the previous patches at all), just like suggested in the OP.