What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Honorbuddy v2.5.8562.705

B

Bitofabotter

New Member
Joined
Nov 15, 2013
Messages
25
Reaction score
0
First time here, so hi all.

OK been using HB for awhile, with the usual collection of issues and eventual solutions - thanks to the team and posters.

A new error appeared with the last update:

"A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread."

Soon after this the usual report to Microsoft crap appears then HB closes.

This occurs during Initializing Routines and seems to be more likely when I have my Monk open. Initialization will complete before the Microsoft error window pops up.

Only shutting down and restarting the machine will allow me to logon and run HB again sometimes.

The machine is up-to-date re XP-SP3, AVG is disabled and I have tried with and without plugins - no difference. I have clean installed HB both with installer and zip several times - no change.

I have attached a log file in case its of use.

I await input for those more knowledgeable than me.

This has now been posted here after I apparently posted in the wrong area - as I said above first timer - thread closed - no thread move - just closed - so helpful Tony. I guess you must be getting frustrated with the problems that this app obviously has.

I hope this meets with the moderators approval and is in the correct area.
 

Attachments

well its not that hard to open your thread under the proper section as the other users are doing i guess,right?

so instead of bashing me you could check that there is a support issues section and no we are not moving threads,we are closing them :)

as for the problems that this app may have,like you said,i am afraid you are not able to know them since you are a member of this forum less than a day

so if you are done with the drama we can check your issue now


are you on a VMware environment?
 
what about Parallels then? it seems ODD that theres an OSX metadata folder in your zip folder, on top of the fact its acting like its running in a VM.
 
Nope. It running on a Windows machine, no VM, no parallels. Windows XP SP3. Oh I zipped it on a friends machine, that was a Mac. I had the full txt file from my machine on a thumb drive and then realised I needed to zip it to post. So I borrowed a friends machine to zip the txt file so I could post it, I guess it must have added a metadata file. Sorry for the confusion.

No I use Windows XP SP3. It has 2 drives both running XP, but I only ever boot and use 1. Everything was fine until the most recent HB update.
 
remove:
- microsoft .net framework 4 client profile
- microsoft .net framework 4 extended
- microsoft visual c++ 2010 x86 redistributable
- microsoft visual c++ 2012 x86 redistributable


restart your pc,
download the installationwizard from here
run it as administrator.
after the wizard is done, run windows update. And install all updates for .net & c++
restart


also install this

NET Framework
 
Thanks I'll try in 2 days when back in town and let you know. Any idea why it was all fine prior to this update, then this problem appears?
 
idk if something got corrupted somehow,any major software changes/updates?
 
Well sorry to report the above plan did not help. Start machine, login WoW, start HB gather for awhile. Close HB, close WoW. Repeat login routine, above error.

Ideas??
 
Thanks Tony, but I think Ill try a clean install of XP, on a dedicated drive just WoW/HB, with an all new Wow and HB install on a different machine ie totally different machine and software, and then if it doesnt work Ill take you up on your offer. Thanks very much for your help thus far. Ill post next week once Ive done clean install. One weird thing is if machine has been off for awhile I can load and run WOW/HB. IF I repeat the process as above the error occurs and persists with restart/shutdown if for a short time, but will work if left turned off for an extended while, I am suspicious of a ram issue or some other hardware problem, so the issue may be coincident with the HB latest update, but I also note another poster with the same issue
 
OK fresh install Win 7-64 install, yanked 2 ram modules, new HB - Runs! Error gone. Whilst .Net and other MS components may have been the issue, I suspect the ram. The long standing 'We are stuck!' problem however is still omnipresent. This is started around the same time noted by others, maybe 3 or 4 versions ago - it makes questing almost impossible and detection highly likely. Anyhow, thanks for you help, ultimately not sure of root cause but as I said I suspect ram, and the update problem timing may simply have been a coincidence.
 
post a full log as an attachment so we can see whats going on.
 
OK heres 1 example

As requested a log showing We are stuck. Seems much worse when questing, doesn't seem to be affected by plugins or not. Still fine since clean install etc re earlier error.

Thanks
 

Attachments

click Settings and Tools and try turning off "Use Framelock"
 
Yup tried that before, makes some difference to speed, mainly with farming, no effect on the getting stuck. Ive watched the bot, it happens around npc's and low level scenery like tree roots. I also noted it was happening when the bot was in water trying to cast a net - a quest item usage, the stuck was almost continuous as was a weird problem where the bot was constantly mounting and unmounting. It is also much more prevalent when questing than farming, although it does still happen. I know you're going to think I'm crazy and I'm preparing for the lol responses, but its almost as though the HB positioning of the bot is slightly off. I know nothing about the technicalities of how it works but I assume it uses x,y,z co-ords to match toon placement within the game environment, is it possible that blizz deliberately made a very small change to its 3d 'map' just enough to cause the bot to have a mismatch resulting in this I am stuck issue? That in my mind makes some sense because mines for example are usually in the open and landing near by is good enough to interact, but questing is different. I also have noticed that when farming nodes the bot often misses the mark and has several attempts to get to the node, often overflying a smidge. Just a thought. I had not seen the error at all until about 3 or 4 updates ago if memory serves.
 
we're only working on the stuck issue, if turning off framelocking does not do it for you. then try turning up the priority of your wow process in your task manager.
 
You must log in or register to reply here.
Back
Top