HI I have read a ton of posts, trying every tip there is, and I still cant get HB to work. Every time I start HB, I get the same error "Could not load file or assembly 'fasmdll_managed.dll". Log attached. Running Windows 7 - 64bit Running Wow 32bit Wow set to Window mode Wow set to DirectX 9 Running HB as Administrator Tried some more : - Deleted HB and downloaded/re-installed it - Reinstalled Framework 4 - Reinstalled MS C++ 2010 - Tried Tony's "fix tool" (BuddyPrequisitesWizard.exe) - Checked for any windows OS update (all already installed) - Started HB in compatibility mode Windows Xp SP3 - Started WOW in compatibility mode Windows Xp SP3 I could be wrong, but it seems fasmdll_managed.dll try to load and fails or it calls a dependency (I don't know what file). Perhaps some could list perquisites of files that must exist on system? Any help would be much appreciated and thanks
Edit since its seems to be solved now. I did this : http://www.thebuddyforum.com/releases/68254-problems-new-install-buddy-product.html and run it as admin then it worked fine! Regards,
Same problem with new Honorbuddy v2.5.6384.495... Could not load file or assembly 'fasmdll_managed.dll New log attached Question : at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits) from the logfile, does this mean HB find WOW as 64bit???, if yes, then there is a problem, cause WOW is loaded as 32bit (taskmanager confirms that, wow.exe *32 running) So... what is going on?.. is there anyone who can actually run HB on a Windows 7 / 64bit system with a WOW 32bit client?
install this http://www.thebuddyforum.com/releases/68254-problems-new-install-buddy-product.html you must run it as admin
I will try it again. EDIT 08-10-2012 14:15 : I finlly got it to work. I used the tool Tony said (again) and have done so 3 times, and it did not work first! So I uninstalled the Microsoft Visual C++ 2010 x86 redist. and restarted. Then I installed Tonys tool again and it somehow could see the x86 part missing, and reinstalled this. Restarted again and the it worked. So to you guys with 64bit OS, try this if you get the same error.
