Demonbuddy can't attach to more than one diablo?

[nickchapelle]

[12:15:19.115 N] Demonbuddy v1.0.1106.281 started
[12:15:20.693 N] Logging in...
[12:15:23.695 N] Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The specified module could not be found.
File name: 'fasmdll_managed.dll'
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)

Looked everywhere couldn't find a solution.

 

[diabloiseasy]

YOur on US? guess thats why!

 

[fr3357]

has nothing to do with attaching.

fasmdll_managed.dll

search this, there is ALOT of post involving it some wow related etc. It has to do with .net and c++distro

 

[nickchapelle]

the thing is, they're both installed properly i had it working earlyer. This started happening after i copydd d3 into another folder and used -launch command. now i launch db and i choose which one to attach too and that happens.

 

[fr3357]

I guess I cant help no more, I dont use the copy folder tech, I find it really wastefull of space since I use SSD, I use Vm's atm because I have more then enough resources to fuel my # of accounts. clone is a matter of 3 seconds and I can set them up how I choose. ISO boxer I would recommend I guess.

 

[nickchapelle]

Thanks for the help then i had vm running my 4 bots. but it used too much resorces, it ran really glitchy. so i decided to run it this way.

 

[fr3357]

I know you have to do each patcher manually on each, but have never really toyed with it.

 

[Tony]

Are you ok now?

 

[nickchapelle]

yeah. i am. the trick was to open one diablo set db then open the next diablo.