[ANSWERED] Can't Start DB Exe

[Fisher67]

We have blocked the usage of old Demonbuddy and Hearthbuddy builds and will be pushing new builds that
will be as safe as before soon.

You might notice that our bots will be renaming themselves after they have launched. This is done for security
measures and shouldn't affect your daily usage. Bots will be leaving an auto updating shortcut (symlink) in the
folder which you can use as there was no renaming like before. We tried our best for this security measure to
not affect any reloggers or provide a bad experience in any form. Manually renaming the symlink or the exe
will not provide any extra protection and should be avoided.

Thank you all for your support and happy botting.

I had to rename the directory of the DB install, and the shortcut on my desktop was no longer valid. So I deleted it and attempted to make a shortcut again. I can't seem to start DB now, even when clicking on the application itself directly in the installation folder:

Any ideas? How do I initialize the program?

 

[Fisher67]

Well shoot. So I renamed the directory to the original "Demonbuddy" and it works again. So how do I make multiple DB installations now? I want a demonbuddy directory for bounties, rifts, and greater rifts. Thanks!

/e This is so strange - if you copy the directory you can run DB from the copied directory symlink. But if you rename the directory folder manually, the symlink produces that error.

 

[MaiN]

Well shoot. So I renamed the directory to the original "Demonbuddy" and it works again. So how do I make multiple DB installations now? I want a demonbuddy directory for bounties, rifts, and greater rifts. Thanks!

/e This is so strange - if you copy the directory you can run DB from the copied directory symlink. But if you rename the directory folder manually, the symlink produces that error.

Thanks for the steps! I can reproduce it with this. We will look at getting this fixed for the next release.

 

[Fisher67]

Thanks for the steps! I can reproduce it with this. We will look at getting this fixed for the next release.

Thanks!

 

[misosozi]

This is how I work around it:

1. I make a base folder with DB: DB Beta + Trinity (SVN) + Adventurer (SVN)
2. Copy base DB folder to the new location
3, Rename the new DB folder in accordance with its role
4. Copy "demonbuddy.exe" file from the base DB to the new DB
5. Run db from the new location
6. Profit

You can still copy DB folders in whatever way making multiple copies but each time you need to copy demonbuddy.exe from the base DB to the new DB folder.

I bealive that symlink makes a hard link with exact folder name and additionally takes some file checksum so you cant do it twice. Just my assumption.

 

[MaiN]

This is how I work around it:

1. I make a base folder with DB: DB Beta + Trinity (SVN) + Adventurer (SVN)
2. Copy base DB folder to the new location
3, Rename the new DB folder in accordance with its role
4. Copy "demonbuddy.exe" file from the base DB to the new DB
5. Run db from the new location
6. Profit

You can still copy DB folders in whatever way making multiple copies but each time you need to copy demonbuddy.exe from the base DB to the new DB folder.

I bealive that symlink makes a hard link with exact folder name and additionally takes some file checksum so you cant do it twice. Just my assumption.

The sym link is relative, not absolute. If you want the technical reasoning for the bug it is this Windows bug: https://support.microsoft.com/en-us/kb/2987926
The current DB beta (605 and up) should not have the problem, so you can use that with as many renames as you'd like.