Hi,

I am trying to use Pablo on wine, an independently developed Chinese language programme which looks very promising.

When I contacted the developer, he said it is written in Hotbasic, with some .NET functionality, specifically Windows.Storage.ApplicationData.

I have tried installing .NET 4.8, and using a clean 32 and 64-bit Wineprefix.

I don't know how to interpret the error message below, if anyone has any suggestions.

Searching for the error messages (RoGetActivationFactory Windows.Storage.ApplicationData, and RoGetActivationFactory Windows.ApplicationModel.Package) usually brings help, but it brings up absolutely nothing at all!

I am using wine 5.19-staging.







Thanks,

L

Wine usually throws a hissy fit before starting something up, as if it's permanently in debug mode, but then gets on with the job. I'd ignore the initial errors. This was the show stopper In the linux kernel, the low memory addresses (64k in my kernel, but you can set it higher) are off limits to all software, as a security measure. Hackers used to have the instruction 'goto 0x00000000' and they got root access to the system. So the crash was preserved, but you hardly need that either.

The software is clearly not going to work.

• What distro are you on?
• Why wine-5.19-staging?
• what compile?
• 32 or 64 bit?

Wine works by translating windows system calls to Posix ones. I have slackware64, which is a multilib system. 64bit libs are in /usr/lib64, 32bit libs are in /usr/lib. Most m$ programs are 32 bit. Try 'ls -l wine*' and run file on them. In Slackware64, Alien Bob does a special 32/64 compile which runs 32 or 64 bit programs. Is Pablo 32 or 64 bit? Find out that much and report back.

1 members found this post helpful.

Thank you for the explanation. I always wondered what that meant in crash logs and reports. I have heard of the use of memory overflows an exploit, but I wouldn't know much beyond that. Likewise, knowing the name of a few volcanoes wouldn't qualify me to be a geographer.

I'm using Ubuntu 20.04, which I should have mentioned. The wine release is from the official wine repository. I was using the staging release just to be a bit more up-to-date, but stable gave the same error when I installed it.

I have not heard back from the developer yet this time; I did ask if it was 32 or 64 bit. As the previous release was back in 2008, and that version gave the same error, I would guess it may be 32-bit.

I thought that perhaps I had installed .NET improperly, or perhaps it was a wine bug of some kind. If the programme is closed-source, would there be much else I can do? Hopefully the developer might still reply...

1. There's 2 debugging tools on most linux systems, gdb and strace. Familiarise yourself with them.
2. There's also the WINEDEBUG variable which allows you to log interaction in various areas. Now that you know the areas under suspicion, have a good look on winehq.org for $WINEDEBUG arguments and put a line together like "WINEDEBUG=arg1 arg2 arg3 wine /path/to/program.exe >wine.err 2>&1" that will trap all the stuff that rolls off the screen into a file called wine.err
3. As a last resort, or if you either haven't much installed or feel your ~/.wine dir is polluted, you can run 'rm -rf ~/.wine' which clears out your wine directory. the first time it starts, wine will curse you silently and repopulate it. Not half as necessary now as it used to be.
4. Lastly, there's the winetricks script which adds all sorts of extra packages (like .NET) to your wine install.

Over to you now.

1 members found this post helpful.