What's new
By:
  • 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 am currently having a problem where it almost instantly causes wow to crash once it starts up, i had the exact same problem with Arelog. I think it has something to do with "A 32 bit processes cannot access modules of a 64 bit process." any ideas?


HBRelog Version 1.0.4421.42046
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
DxDevice9 Offset found at 0xABDCCC
DxDevice9 Index is 0x2800
GameState Offset found at 0xAD5C76
FrameScriptExecute Offset found at 0x43B0A0
LastHardwareEvent Offset found at 0x9D2150
GlueStateOffset Offset found at 0xABA1D4
rogue level: GlueStatus: Disconnected
rogue level: WoW has disconnected or crashed.. So lets restart WoW
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
System.ComponentModel.Win32Exception (0x80004005): A 32 bit processes cannot access modules of a 64 bit process.
at System.Diagnostics.NtProcessManager.GetModuleInfos (Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModule Info(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at HighVoltz.WoW.Hook.get_BaseOffset()
at HighVoltz.WoW.WowManager.get_GlueStatus()
at HighVoltz.WoW.WowManager.LoginWoW()
at HighVoltz.WoW.WowManager.Pulse()
at HighVoltz.TaskManager.Pulse()
at HighVoltz.HBRelog.DoWork()
rogue level: WoW process was terminated. Restarting
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
rogue level: GlueStatus: Disconnected
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
rogue level: GlueStatus: Disconnected
rogue level: WoW process was terminated. Restarting
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
 
xenocides said:
I am currently having a problem where it almost instantly causes wow to crash once it starts up, i had the exact same problem with Arelog. I think it has something to do with "A 32 bit processes cannot access modules of a 64 bit process." any ideas?


HBRelog Version 1.0.4421.42046
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
DxDevice9 Offset found at 0xABDCCC
DxDevice9 Index is 0x2800
GameState Offset found at 0xAD5C76
FrameScriptExecute Offset found at 0x43B0A0
LastHardwareEvent Offset found at 0x9D2150
GlueStateOffset Offset found at 0xABA1D4
rogue level: GlueStatus: Disconnected
rogue level: WoW has disconnected or crashed.. So lets restart WoW
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
System.ComponentModel.Win32Exception (0x80004005): A 32 bit processes cannot access modules of a 64 bit process.
at System.Diagnostics.NtProcessManager.GetModuleInfos (Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModule Info(Int32 processId)
at System.Diagnostics.Process.get_MainModule()
at HighVoltz.WoW.Hook.get_BaseOffset()
at HighVoltz.WoW.WowManager.get_GlueStatus()
at HighVoltz.WoW.WowManager.LoginWoW()
at HighVoltz.WoW.WowManager.Pulse()
at HighVoltz.TaskManager.Pulse()
at HighVoltz.HBRelog.DoWork()
rogue level: WoW process was terminated. Restarting
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
rogue level: GlueStatus: Disconnected
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
rogue level: Installing Endscene hook
rogue level: GlueStatus: Disconnected
rogue level: WoW process was terminated. Restarting
rogue level: starting C:\Program Files\World of Warcraft\Wow.exe
Click to expand...
are you using a 32 bit windows?
 
If you're downloading the source you will need to search online for the 'BlackMagic.dll' source code and recompile it under .net4 (I'm planning to add it later to the repository)
Click to expand...
what it is?? where i can download this file?? I dont understand how to use this pluging/ Where i can get this blacj magic?
 
Last edited:
Hi guys can anyone tell me how can I set up the reloger to
farm for 2 hours then login to another character and
use professionbuddy for 10 min then
stop for 30 min and repeat thet so loop the task
im using it like
wait 120
logon the professionbuddy character
wait 10
idle 30
is that right or i have to change anything ?
 
gogogaga said:
Hi guys can anyone tell me how can I set up the reloger to
farm for 2 hours then login to another character and
use professionbuddy for 10 min then
stop for 30 min and repeat thet so loop the task
im using it like
wait 120
logon the professionbuddy character
wait 10
idle 30
is that right or i have to change anything ?
Click to expand...
Below the idle you'll want to add a logon for the farmer Farmer, other then that, it looks good.
 
I LOVE YOU!!! I just got started looking at wpf snoop's code and wrote the arelog dev a pm to ask whether i could have the source. :D

<3 <3 <3 highvoltz

edit: for anyone who has not noticed, there is a paypal donation link on the bottom of the first post in this thread. if anyone deserves our money, its this guy (and kickz ofc)!! :D
 
Last edited:
ciano1 said:
Getting the same:

HBRelog Version 1.0.4422.33728
ROFLWAFFLE: starting E:\Programs\World of Warcraft\Wow.exe
System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_dotnet4.dll' or one of its dependencies. The specified module could not be found.
File name: 'fasmdll_dotnet4.dll'
at Magic.BlackMagic..ctor()
at Magic.BlackMagic..ctor(Int32 ProcessId)
at HighVoltz.WoW.Hook..ctor(Process wowProc)
at HighVoltz.WoW.WowManager.Pulse()
at HighVoltz.TaskManager.Pulse()
at HighVoltz.HBRelog.DoWork()

I followed intructions but still getting this error
Click to expand...

Make sure your folder structure is proper i.e d:\HBRelog\Release ( all files should be in the release folder )
 
ciano1 said:
Getting the same:

HBRelog Version 1.0.4422.33728
ROFLWAFFLE: starting E:\Programs\World of Warcraft\Wow.exe
System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_dotnet4.dll' or one of its dependencies. The specified module could not be found.
File name: 'fasmdll_dotnet4.dll'
at Magic.BlackMagic..ctor()
at Magic.BlackMagic..ctor(Int32 ProcessId)
at HighVoltz.WoW.Hook..ctor(Process wowProc)
at HighVoltz.WoW.WowManager.Pulse()
at HighVoltz.TaskManager.Pulse()
at HighVoltz.HBRelog.DoWork()

I followed intructions but still getting this error
Click to expand...

I have had the same issue since release, kinda sad since I cant try it out :(
 
After almost two weeks of vacation, I suddenly found Tapatalk and BAM, this!

Thank god this works with Lowerping. That alone is worth the switch to me.

That said, would it be possible to add clock-based schedules?
If this works like arelog (I'm still on vacation so I can't try it), if the program crashed or comp restarted or whatever, the "schedule" would be restarted.

Having a clock-based schedule would make fix that, not to mention making it a hell of a lot easier to juggle different tasks and characters, specially for those with many accounts.

For example:
Monday 8-10 acc 1 toon 1 uldum
Monday 8-10 acc 2 toon 1 hyjal
Monday 8-10 acc 3 toon 1 vashj'ir
Monday 8-10 acc 4 toon 1 TH

Monday 10-12 acc 1 toon 2 hyjal
Monday 10-12 acc 2 toon 2 vashj'ir
Monday 10-12 acc 3 toon 2 TH
Monday 10-12 acc 4 toon 2 uldum

And so forth.
Not only it'd save users the confusion of setting up and calculating a billion wait tasks, but it'd help create a less erratic playtime for the accounts, if you know what I mean.

Any day, any time the logger started, the account would go on it's normal schedule and do what it's supposed to do at that specific time.

In any case, thanks for all your hard work man. You're an invaluable asset to the HB community
 
Last edited:
Toney001 said:
After almost two weeks of vacation, I suddenly found Tapatalk and BAM, this!

Thank god this works with Lowerping. That alone is worth the switch to me.

That said, would it be possible to add clock-based schedules?
If this works like arelog (I'm still on vacation so I can't try it), if the program crashed or comp restarted or whatever, the "schedule" would be restarted.

Having a clock-based schedule would make fix that, not to mention making it a hell of a lot easier to juggle different tasks and characters, specially for those with many accounts.

For example:
Monday 8-10 acc 1 toon 1 uldum
Monday 8-10 acc 2 toon 1 hyjal
Monday 8-10 acc 3 toon 1 vashj'ir
Monday 8-10 acc 4 toon 1 TH

Monday 10-12 acc 1 toon 2 hyjal
Monday 10-12 acc 2 toon 2 vashj'ir
Monday 10-12 acc 3 toon 2 TH
Monday 10-12 acc 4 toon 2 uldum

And so forth.
Not only it'd save users the confusion of setting up and calculating a billion wait tasks, but it'd help create a less erratic playtime for the accounts, if you know what I mean.

Any day, any time the logger started, the account would go on it's normal schedule and do what it's supposed to do at that specific time.

In any case, thanks for all your hard work man. You're an invaluable asset to the HB community
Click to expand...

'll see what I can do, this probably would require me to completely redo the task system.
 
Hey highvoltz, just wanna let you know that HBRelog is working great for me. Let it run over night and as i came back today i saw in the HBRelog-log that WoW crashed two times and the HB + WoW was still running well. ;) Also, great that it closes the WoW error popups. Thanks for your work!

SoTD
 
Ahhh here we go, using combat or assassination spec fixes the problem. How bizzare =D

Thanks for an awesome plugin, now got it working with no problems at all =)

Z.
 
Last edited:
You must log in or register to reply here.
Back
Top