What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: HBRelog--DO NOT DELETE

I always found this error when I run HBRelog in VMWare (Windows 7 x64) and HBRelog cannot login World of Warcraft (every session).

PHP:
[11/08/2014 09:10:41] System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The device is not ready. (Exception from HRESULT: 0x80070015)
File name: 'fasmdll_managed.dll'
   at GreyMagic.ExternalProcessReader..ctor(Process proc)
   at HighVoltz.HBRelog.WoW.WowLockToken.StartWoW()
   at HighVoltz.HBRelog.WoW.States.StartWowState.Run()
   at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   at HighVoltz.HBRelog.WoW.WowManager.Pulse()
   at HighVoltz.HBRelog.TaskManager.Pulse()
   at HighVoltz.HBRelog.HbRelogManager.DoWork()
View attachment Log[2014-11-08_09-10-31].txt
 
Hey all,

Just built a new computer: When I run HBRelog it opens WoW but doesn't enter a password etc

Any thoughts on what's wrong? (I have .net and C++)


Thanks in advance!



I have exactly this same problem and i alreadly have tried Tanatoo sugestion ("Set "WoW Start Delay" to 20 Set "Login Delay" to 20")
and still the exact same thing happens, wow window opens, but HBRelog does nothing, it keeps "waiting wow to start".

Here is my log:
​[02:19:05] HBRelog Version 1.0.0.216[02:19:05] ******* Settings ********
[02:19:06] Auto AcceptTosEula: False
[02:19:06] Auto Start: False
[02:19:06] Auto Update HB: True
[02:19:06] Check Hb's Responsiveness: True
[02:19:06] Check Realm Status: False
[02:19:06] HB Delay: 3
[02:19:06] Login Delay: 20
[02:19:06] Minimize Hb On Startup: False
[02:19:06] Set GameWindow Title: False
[02:19:06] Wow Start Delay: 20
[02:19:07] HerbMinHunter: ********* Tasks ***********
[02:19:07] HerbMinHunter: ********* End of Task list ***********
[02:19:08] HerbMinHunter: Starting E:\World of Warcraft\Wow.exe
[02:19:09] HerbMinHunter: Waiting for Wow to start
[02:19:16] System.IO.FileNotFoundException: Não foi possível carregar arquivo ou assembly 'fasmdll_managed.dll' ou uma de suas dependências. Não foi possível encontrar o módulo especificado.
Nome do arquivo: 'fasmdll_managed.dll'
em GreyMagic.ExternalProcessReader..ctor(Process proc)
em HighVoltz.HBRelog.WoW.WowLockToken.StartWoW()
em HighVoltz.HBRelog.WoW.States.StartWowState.Run()
em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
em HighVoltz.HBRelog.WoW.WowManager.Pulse()
em HighVoltz.HBRelog.TaskManager.Pulse()
em HighVoltz.HBRelog.HbRelogManager.DoWork()




[02:19:25] System.ArgumentException: wowManager.Globals is null
Nome do parâmetro: wowManager.Globals
em HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
em HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
em HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
em HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
em HighVoltz.HBRelog.WoW.WowManager.Pulse()
em HighVoltz.HBRelog.TaskManager.Pulse()
em HighVoltz.HBRelog.HbRelogManager.DoWork()
 
any way to schedule different wow accounts to start one after another?

http://i.imgur.com/slwJr6m.jpg

I just want Profile "Number1" to run for an hour, stop, then Profile "Number2" to start and run for an hour, then back to Number1. two different wow accounts, one honorbuddy account, they don't run at same time.

what can i put into the tasks list?
 
You must start the next task before you cancel the first on.

Number 1 = wait task (1h) - start Number 2- stop number 1

Number 2= wait (1h) - start Number 1 - stop number 2.

Delete the second 'wait task'. Why do you need it?
 
I always found this error when I run HBRelog in VMWare (Windows 7 x64) and HBRelog cannot login World of Warcraft (every session).

PHP:
[11/08/2014 09:10:41] System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The device is not ready. (Exception from HRESULT: 0x80070015)
File name: 'fasmdll_managed.dll'
   at GreyMagic.ExternalProcessReader..ctor(Process proc)
   at HighVoltz.HBRelog.WoW.WowLockToken.StartWoW()
   at HighVoltz.HBRelog.WoW.States.StartWowState.Run()
   at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
   at HighVoltz.HBRelog.WoW.WowManager.Pulse()
   at HighVoltz.HBRelog.TaskManager.Pulse()
   at HighVoltz.HBRelog.HbRelogManager.DoWork()
View attachment 150255

OK. It was solved after I re-install.
 
Last edited:
how to remove "wow not responding" "wow has crached" message from windows 7 that stops wow from restarting?
 
I have exactly this same problem and i alreadly have tried Tanatoo sugestion ("Set "WoW Start Delay" to 20 Set "Login Delay" to 20")
and still the exact same thing happens, wow window opens, but HBRelog does nothing, it keeps "waiting wow to start".

Here is my log:
​[02:19:05] HBRelog Version 1.0.0.216[02:19:05] ******* Settings ********
[02:19:06] Auto AcceptTosEula: False
[02:19:06] Auto Start: False
[02:19:06] Auto Update HB: True
[02:19:06] Check Hb's Responsiveness: True
[02:19:06] Check Realm Status: False
[02:19:06] HB Delay: 3
[02:19:06] Login Delay: 20
[02:19:06] Minimize Hb On Startup: False
[02:19:06] Set GameWindow Title: False
[02:19:06] Wow Start Delay: 20
[02:19:07] HerbMinHunter: ********* Tasks ***********
[02:19:07] HerbMinHunter: ********* End of Task list ***********
[02:19:08] HerbMinHunter: Starting E:\World of Warcraft\Wow.exe
[02:19:09] HerbMinHunter: Waiting for Wow to start
[02:19:16] System.IO.FileNotFoundException: Não foi possível carregar arquivo ou assembly 'fasmdll_managed.dll' ou uma de suas dependências. Não foi possível encontrar o módulo especificado.
Nome do arquivo: 'fasmdll_managed.dll'
em GreyMagic.ExternalProcessReader..ctor(Process proc)
em HighVoltz.HBRelog.WoW.WowLockToken.StartWoW()
em HighVoltz.HBRelog.WoW.States.StartWowState.Run()
em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
em HighVoltz.HBRelog.WoW.WowManager.Pulse()
em HighVoltz.HBRelog.TaskManager.Pulse()
em HighVoltz.HBRelog.HbRelogManager.DoWork()




[02:19:25] System.ArgumentException: wowManager.Globals is null
Nome do parâmetro: wowManager.Globals
em HighVoltz.HBRelog.WoW.FrameXml.UIObject.GetUIObjectByName[T](WowManager wowManager, String name)
em HighVoltz.HBRelog.WoW.States.LoginWowState.get_GlueDialogTitle()
em HighVoltz.HBRelog.WoW.States.LoginWowState.get_IsBanned()
em HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
em HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
em HighVoltz.HBRelog.WoW.WowManager.Pulse()
em HighVoltz.HBRelog.TaskManager.Pulse()
em HighVoltz.HBRelog.HbRelogManager.DoWork()


I still have this problem guys, can any1 help me?
 
Getting this error. How could I fix this? It just starts WoW and then does nothing

[18:14:49] System.AccessViolationException: Could not read bytes from 555500FF [299]!
at GreyMagic.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at GreyMagic.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at HighVoltz.HBRelog.WoW.Lua.LuaTable..ctor(ExternalProcessReader memory, IntPtr address)
at HighVoltz.HBRelog.WoW.Lua.LuaTValue.get_Table()
at HighVoltz.HBRelog.WoW.FrameXml.UIObject.<GetUIObjects>b__3(LuaNode n)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.<OfTypeIterator>d__aa`1.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at HighVoltz.HBRelog.WoW.States.LoginWowState.HandleAccountSelectionDialog()
at HighVoltz.HBRelog.WoW.States.LoginWowState.Run()
at HighVoltz.HBRelog.FiniteStateMachine.FiniteStateMachine.Engine.Pulse()
at HighVoltz.HBRelog.WoW.WowManager.Pulse()
at HighVoltz.HBRelog.TaskManager.Pulse()
at HighVoltz.HBRelog.HbRelogManager.DoWork()
 
Has anybody found a solution to this error?

Honorbuddy process has exited with code 12, signaling that it should not be restarted

Wasn't happening before the last big wow patch,

Help !

Your honorbuddy itself is shutting down because the inactivity timer has been activated.

On another note, since the latest build HBrelog has trouble shutting down HB when I make it switch botbases through a task. Happens about 20-30% all the time. Very annoying.
 
I've used this relogger 2-3 years ago, no issues. having lots of issues now.

Just a suggestion, edit the first post to make it real clear in big bold letters about this addon. I wasted a lot of time dicking around with the tasks and testing etc, until I finally noticed there is an hbreloghelper addon that must be manually enabled on every character i used. maybe i'm extra dumb but it really wasn't obvious.

however there are still major league issues. simple project, i want it to log on three different accounts one after the other. WOW1 (Profile 1) and WOW2 (Profile 2) on the same battlenet, and a WOW 1 (Profile 3) on a different battlenet. fine, make 3 profiles and set up tasks for each one, eg for Profile 1 it's WAIT 1 hours, START (Profile 2), and STOP the running (Profile 1). similarly for next two.


when (trying) to go from Profile 1 to Profile 2, it just logs directly back into WoW1 instead of WoW2. gives a message "Character name not found check spelling" and stops on the char selection screen. If I manually close that wow window, it immediately restarts it and this time successfully chooses WOW2 and keeps going.

Then, many other times... it will not close the running profile. so it will start the next one, but the STOP task for the running profile doesn't work. here it gets stuck with two open wow windows and two HBs, the second one can't start since the key is already being used.

hopefully this shit will get sorted out, Arelog is even worse. weird that such an advanced bot doesn't have a functioning relog function. I won't even get into the fact that combining relogger with the new buddystore is like pulling nails.

enclosing a log illustrating both errors.
 

Attachments

Please add PROCESS KILLER more powerful for kill the wow and honorbuddy, sometimes not close correctly dude
 
I've used this relogger 2-3 years ago, no issues. having lots of issues now.

Just a suggestion, edit the first post to make it real clear in big bold letters about this addon. I wasted a lot of time dicking around with the tasks and testing etc, until I finally noticed there is an hbreloghelper addon that must be manually enabled on every character i used. maybe i'm extra dumb but it really wasn't obvious.

however there are still major league issues. simple project, i want it to log on three different accounts one after the other. WOW1 (Profile 1) and WOW2 (Profile 2) on the same battlenet, and a WOW 1 (Profile 3) on a different battlenet. fine, make 3 profiles and set up tasks for each one, eg for Profile 1 it's WAIT 1 hours, START (Profile 2), and STOP the running (Profile 1). similarly for next two.


when (trying) to go from Profile 1 to Profile 2, it just logs directly back into WoW1 instead of WoW2. gives a message "Character name not found check spelling" and stops on the char selection screen. If I manually close that wow window, it immediately restarts it and this time successfully chooses WOW2 and keeps going.

Then, many other times... it will not close the running profile. so it will start the next one, but the STOP task for the running profile doesn't work. here it gets stuck with two open wow windows and two HBs, the second one can't start since the key is already being used.

hopefully this shit will get sorted out, Arelog is even worse. weird that such an advanced bot doesn't have a functioning relog function. I won't even get into the fact that combining relogger with the new buddystore is like pulling nails.

enclosing a log illustrating both errors.

Looks like HBRelog is having issues reading the GreyMagic file in your honorbuddy directory, make sure that folder is in a read/write allowed location and/or run HBRelog as Admin.

It really isn't overly obvious about the plugin but something I stumbled upon pretty early, guess I was just lucky to have noticed it in my plugins menu.
 
When honorbuddy stop for fail quest, the hbrelog dont reload honorbuddy, why?

Maybe the inactivity trigger built into HB itself triggers, which makes HBrelog stop the HBrelog profile with the error code 12.

Next time post a log and someone can say for sure.
 
Back
Top