11/23/2023 0 Comments Blizzard battle.net app 32 bitYou need the same bottle because you need the right version of Agent.exe to already be running (so that you don't get in the update loop that causes it to fail). SELECT THE SAME BOTTLE YOU USED IN STEP ONE!!!!! This will again launch the software installer.īefore you click "Install". Use the up arrow to re-populate the command you used in the first step. Let that run to it's heart's content in the terminal. Note that there is a possibility that your version number may be different (2581 in my case). ~/cxoffice/bin/cxrun -bottle "_Desktop_App" ~/.cxoffice/_Desktop_App/drive_c/users/Public/Application\ Data//Agent/Agent.beta.2581/Agent.exe In the other terminal, you will be starting the proper Agent.exe process.Don't close this terminal! Make your life easy! Exit out of it and out of the software installer and get back to the command prompt. ~/cxoffice/bin/cxinstaller -tiefile="/path/to/ Desktop App.tie"ĬrossOver's software installer will launch and begin the installation of the Desktop App. Start the CrossOver installer with the tie file:.The instructions assume the ".bin" installer was used (as in CrossOver's home is ~/cxoffice/bin/crossover) so if you used the debian or rpm installer, please make the necessary adjustments (as in, ~/cxoffice/bin/crossover becomes /opt/cxoffice/bin/crossover). Also, CrossOver will need to be installed prior to starting these instructions. You will need Silvu Cojocaru's tie file, two terminals and a little patience (not much, I promise). The workaround is "easier" than deleting things from your folders though that will be as effective. I'm sure I don't recall the exact issue but if I remember correctly, "Agent.exe" got an update and there's either a version mismatch or an extra "Agent.exe" process hanging around (I believe it's the former). I remember it happening with Diablo III, World of Warcraft and Starcraft II. You might also want to take a look on WineHQ In one log file there was a lot of this:Įrr:wininet:open_http_connection create_netconn failed: 12029 It will prompt you to choose where to save the log. Click the Run Command button and navigate to where it's installed. $HOME/cxoffice/bin/cxrun -bottle "$BOTTLE" "$HOME/.cxoffice/$BOTTLE/drive_c/Program Files//"Īdjust the bottle name and path for cxrun accordingly (it may be /opt/cxoffice/bin/cxrun).Ģ) Open the bottle manager. create a little script called bnet.sh and put this code into it:.Unfortunately all I can give you at this time is two workarounds:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |