CrossOver Support - Community Forums

Can someone tell what is happening from the below log?

I have tried to install and reinstall in every bottle from 98-Vista as well as every MSXML Parser from 3-6 without any luck.

Sorry to be such a Noob!

Unhandled exception: unimplemented function msxml.dll.??0cUniModelLookup@@QAE@XZ called in 32-bit code (0x7bc3f248).
Register dump:
CS:001b SS:0023 DS:0023 ES:0023 FS:1007 GS:000f
EIP:7bc3f248 ESP:0033f5f4 EBP:0033f658 EFLAGS:00000206( - -- I - -P- )
EAX:0128214e EBX:0033f600 ECX:0033f67c EDX:010de064
ESI:00000000 EDI:00000000
Stack dump:
0x0033f5f4: 00000000 0033f654 78134c39 80000100
0x0033f604: 00000001 00000000 7bc3f248 00000002
0x0033f614: 0128216a 0128214e abaa250f 00000000
0x0033f624: 00000000 004177f4 00000000 781f2e01
0x0033f634: 010edbc8 0033f65c 0033f61c 7b85d550
0x0033f644: 0033f688 78138ced d3829f3b fffffffe
0200: sel=1007 base=7ffc0000 limit=00000fff 32-bit rw-
Backtrace:
=>0 0x7bc3f248 in <wine-loader> (+0x7bc3f248) (0x0033f658)
1 0x00380627 in <wine-loader> (+0x380626) (0x003c26d0)
0x7bc3f248: subl $4,%esp
Modules:
Module Address Debug info Name (48 modules)
ELF 0-82001000 Stabs <wine-loader>
PE 340000- 377000 Deferred mbtcp
PE 390000- 3b6000 Deferred cserver32fm3
PE 3c0000- 3cb000 Deferred emcsplitter
PE 3d0000- 3f0000 Deferred flashfile
PE 400000- 6cf000 Deferred ptpro
PE 6d0000- 935000 Deferred registry
PE 980000- 99c000 Deferred a32
PE 9e0000- 9f4000 Deferred emcntl32
PE a20000- a79000 Deferred emutilfm3
PE a80000- ad4000 Deferred fmproutil
PE ae0000- ae7000 Deferred emcopy32
PE af0000- b4c000 Deferred a3uapp
PE b50000- b92000 Deferred flash32
PE c00000- c0e000 Deferred ematom
PE c10000- d47000 Deferred softctrl
PE d50000- ea3000 Deferred pegrp32a
PE eb0000- 10de000 Deferred fmprouapp
PE 1200000- 12c0000 Deferred fmpro
PE 10000000-1000c000 Deferred trace
PE 401b0000-401b4000 Deferred version
PE 401c0000-401cd000 Deferred msxml
PE 401e0000-401e4000 Deferred iphlpapi
PE 40490000-40494000 Deferred advapi32
PE 40710000-40781000 Deferred winmm
PE 407c0000-407c4000 Deferred ws2_32
PE 42610000-4264a000 Deferred user32
PE 42740000-42746000 Deferred gdi32
PE 43fb0000-43fb8000 Deferred shlwapi
PE 44010000-44014000 Deferred msvcrt
PE 440a0000-441f7000 Deferred shell32
PE 442b0000-442de000 Deferred comctl32
PE 443b0000-443b8000 Deferred ole32
PE 444c0000-444c4000 Deferred rpcrt4
PE 44530000-44538000 Deferred oleaut32
PE 44630000-446c3000 Deferred comdlg32
PE 44710000-44718000 Deferred winspool
PE 447c0000-447c4000 Deferred winex11
PE 44930000-44934000 Deferred imm32
PE 44b20000-44b27000 Deferred wineps
PE 44bc0000-44bc5000 Deferred localspl
PE 44be0000-44be3000 Deferred spoolss
PE 5d360000-5d36e000 Deferred mfc80enu
PE 78130000-781cb000 Deferred msvcr80
PE 781d0000-782e0000 Deferred mfc80
PE 7b810000-7b987000 Deferred kernel32
PE 7bc10000-7bc14000 Deferred ntdll
PE 7c420000-7c4a7000 Deferred msvcp80
Threads:
process tid prio (all id:s are in hex)
00000008 winewrapper.exe
00000009 0
0000000c services.exe
0000001e 0
0000001d 0
00000017 0
00000016 0
00000015 0
00000013 0
0000000e 0
0000000d 0
00000010 winedevice.exe
0000001b 0
00000018 0
00000012 0
00000011 0
00000019 plugplay.exe
0000001f 0
0000001c 0
0000001a 0
00000020 (D) C:\Program Files\Control Techniques\PowerTools Pro - v5.2\PtPro.exe
00000021 0 <==
00000022 explorer.exe
00000023 0
System information:
Wine build: wine-1.4-6770-g99b913e
Platform: i386
Host system: Darwin
Host version: 11.3.0

... something about that trace looks whacky ; have you tried
installing Microsoft Visual C++ 2005 Redistributable into the
same bottle? Also, it's best you mention exactly which app you
are referring to, and, how said servo motors connect to your
computer itself...ie; USB?..

.

Thanks for the response!

I have not installed Visual C++ any version but I will... 😉

The App I am installing is called "PowerTools Pro" by Control Techniques - Emerson.

I am not actually going to connect to the motor with the software (although I could via USB). I need to just run it to demonstrate it to Engineers.

I am running a 2012 Airbook-11 inch with Lion.

Thanks for feedback and I will d-load C++ and post back.

Thanks again.

Scott Campbell wrote:

I am not actually going to connect to the motor with the software
(although I could via USB). I need to just run it to demonstrate it
to Engineers.

..not necessarily the case -- a lot of win32 apps that are frontends
or controllers to USB devices use activex controls, many of which do
not work in wine ; do not assume this hardware functionality is there,
especially with USB connected devices...

Scott Campbell wrote:

Thanks for feedback and I will d-load C++ and post back.

..that package is available in the 'runtime support components' area
of the crossover installer UI...

Thank you very very much for your comments and insight!

...so much easier when I know the name of the app, and,
it's creators provide same for free...

• c++ redist 2005 is bundled with the app ; it may be optional to install it separately..

• it's actually the base msxml win32 library calling foul (why it looked whacky) ; the
  app bundles it's own (custom?) msxml.dll in the program dir, but wine doesn't know to use
  that in preference to the wine builtin version --- to fix this, all you need to do is add
  msxml.dll in the wine configuration/libraries tab area (adding it will set the load order
  to native,builtin) then click apply->ok, restart the app (should now work fine)....

• that said, I'm none to sure how functional it is at that point, even for demonstration
  purposes -- this powertools suite looks like it works very much like TI's software IDE (CCS)
  for msp430xxxx devices, in that it must communicate with the USB controller to get anywhere.
  For -that- to work, necessitates (typically) device driver supports on the host side to
  begin with, so that one can 'map' the device nodes into the wine/win32-like environment..ie;
  being able to symlink /dev/ttyUSB0 -> COM1 or similar ; if there's no device to map to (that's
  providing the pipe thru your OS' kernel), you're boned... =)

... nowadays however, like with the msp430 'launchpad' eval_kit, these device nodes manifest
themselves as network interfaces hoisted in the 'localhost' segment (127.0.0.1 ~ .254), and
the device data as such is passed over network sockets. When that is the case, you end up with
some kooky mapping akin to /dev/usb/hidraw0 -> 127.0.0.5 or such, which is extremely difficult
to deal with because of device/user permissions and so related, plus one would have to map this
into the wine windows registry for the app to hook to the device, and afaik it's right about
here that thw win32 activex controls hook in. Then it becomes a case of which, if any, of these
controls the app itself actually uses, and whether or not wine supports same...

... a lot of the time, the answer is 'no' ; I'm talking USB dongles, rf->joystick dongles, ipods,
modilephones, blablabla... the actual software suite, whatever it may be, may actually be made
to work fine in wine ... but cannot communicate with the USB connected devices = moot point...

..... there are, as I infer, exceptions here ... but that has to be viewed from a 'hardware up'
stance, rather than a 'software app down' one - your might like to read the following ;

http://wiki.winehq.org/USB?highlight=%28usb%29

...that's about the current state of play afaik ; hopefully it clarifies the what you are looking
at wrt to this area of wine usage...

.

I am very sorry I am not sure what to address you as (your image is awesome!) but none the less thank you again for your very very precise and educational answer.

It is way more than I deserved and it is humbly humbly appreciated!!

Thank you again.

😀