• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Can't connect for updates still?

E

EvilDrK

Member
OK so it looks like there's some troubles connecting with the updates site. And since I'm running HL under linux/wine I'm sure that's not helping matters. Is anyone else still having troubles? Any ideas how to get around them?
 
In the Tools menu, choose "Diagnostics", and then "Check Internet Connection"

Do you get the following message:

No problems could be found with your internet connection.

Retrieval from wolflair.com succeeded.
Retrieval from lonewolfdevel.com succeeded.
Click to expand...

(I just tested it at 5:39PM, PST, and it works for me)
 
Trying to check the internet connection just hangs up for a long time.
Linux Mint 17 Qiana/ Ubuntu Trusty, Wine 1.6.2 running under Win 7 mode.
About 2 weeks ago then after trying it when I got from vacation and hadn't run it in a while it wasn't working. Think it's the certificate stuff most likely but don't have a clue how to fix it.
 
So while I'm annoyed by this, I wasn't worried all that much since the systems I wanted to work worked. Until I tried to load a M&M3 character today. Which wants to load some MECHA file (Portal 'mchTable' - Auto thing 'Mecha' not found) that it can't find now. So any insights - looks like the support folks don't really have a good idea either since they basically know the updates issue is with the cert for us Linux folks, but don't know how to get around it.

This is the output from the wine.log when I run wine HeroLab.exe >wine.log 2>&1

Code: 
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:GetCurrentHwProfileA (0x33fba0) semi-stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:win:RegisterDeviceNotificationA (hwnd=0x1b0b60, filter=0xe2e934,flags=0x00000001) returns a fake device notification handle!
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4910,(nil)): stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x00000013
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae53c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:netapi32:NetGetJoinInformation Semi-stub (null) 0xcae5f4 0xcae5ec
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IPV6 optname 0x00000013
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   13 jjn3-322-mint.local. HINFO X86_64\00c2\00a6LINUX"
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd3c,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 jjn3-322-mint.local. Addr 10.78.211.65"
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadcac,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"Local Hostname jjn3-322-mint.local already in use; will try jjn3-322-mint-2.local instead"
fixme:service:EnumServicesStatusW resume handle not supported
fixme:service:EnumServicesStatusW resume handle not supported
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   21 65.211.78.10.in-addr.arpa. PTR jjn3-322-mint.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd40,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding   23 65.211.78.10.in-addr.arpa. PTR jjn3-322-mint-2.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd38,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 10.78.211.65:5353   21 7.4.f.1.1.4.e.f.f.f.5.e.7.6.2.d.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.
f.ip6.arpa. PTR jjn3-322-mint.local."
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcadd40,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding   23 7.4.F.1.1.4.E.F.F.F.5.E.7.6.2.D.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F
.ip6.arpa. PTR jjn3-322-mint-2.local."
fixme:ras:RasEnumConnectionsW (0x1b0508,0x32cce8,0x76c623e4),stub!
fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!
fixme:service:EnumServicesStatusW resume handle not supported
fixme:ras:RasEnumEntriesW ((nil),(null),0xbceada8,0x32d518,0xbceaa94),stub!
fixme:advapi:ReportEventA (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0xcae538,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000064,(nil),0x0001,0x00000000,0x1a4dc8,(nil)): stub
fixme:advapi:DeregisterEventSource (0xcafe4242) stub


If it helps I'm on Linux Mint Qiana / Ubuntu Trusty on one PC and Linux Mint Nadia / Ubuntu Precise on the other. Both are running Wine 1.62
 
I forget which package it is, but I believe Mecha are part of a MnM 2E supplement. Maybe the character was 2E originally?
 
I have the same problem

Was there any resolution to your problem, also running Herolab under Wine in Linux. It was working fine until recently...
 
Hey everyone! We're looking into this and we hope to have it resolved soon, but we're rushing to get Hero Lab for iPad ready for PaizoCon in a couple of weeks, and we likely won't have time to get to it until sometime after 4th of July weekend. :(

Once we're over our current crunch mode, we should hopefully be able to tackle this and get Linux users back up and running.
 
Solved!!

All!

I solved this issue on Linux Mint 17 using a fresh install of HeroLab and Wine 1.7.xx.

Ok here's what I did.

Uninstall EVERYTHING (Wine and HeroLab).

Restart

Install Wine 1.7.xx (sudo apt-get install wine1.7)

Download herolab and install with Wine.

In a terminal navigate to your ~/.wine/Progam Files (86)/Hero Lab.

Type in wine HeroLab.exe .... You'll get errors:

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000

You need to install some packages.

First: goto the Software manager and search for winbind ... install EVERY package that pops up (the i386 will say Not Available - don't worry just install what you can). This gets rid of the ntlm_auth error.

Second: Open a terminal and type: sudo apt-get install p11-kit:i386 ...
You'll be prompted for your password. Type it in and hit enter.

Third: in the terminal type: wget kegel.com/wine/winetricks
Then when that finishes type: sh winetricks wininet


DONE!! Now launch HeroLab and Enjoy! This works for Linux Mint 17 64-bit but should work for Ubuntu 14.04 and both 32/64 bit.

Hope this helps.
 
I forgot to mention - write down your license info BEFORE uninstalling herolab. Then when you reinstall and get it running, hit Activate on the first screen and type in your license #.
 
I am on Ubuntu 14.04 and have the same issue. Cannot install Wine 1.7, the latest version on my distro is 1.6.2 and I have to configure a PPA repository to use version 1.7. Since I'v juste upgraded from 12.04 to 14.04, I am not keen on taking the risk of adding an unsupported Ubuntu repository...
 
I have typed on a console "winetricks wininet" and after a download, the workaround was good and I could download Hero Lab updates.
 
User happywanderer has supplied a procedure that he says will fix the certificate issue for individual users:

happywanderers post

I would like to know if anybody else has had some success with this procedure.
 
You must log in or register to reply here.
Back
Top