[mindpirate]

BaggyG, on Mar 28 2004, 07:02 AM, said:

Hi All.

I've been trying to get wine and emule to work for a week with minor wins along the way but no real success.

I followed the how-to by the letter.  Wine work in so far as I can run regedit and install emule (that's all Ive done with windows apps so far).

How ever when I try to run emule I get:

[baggy@server01 eMule]# wine emule.exe
fixme:ole:CoRegisterMessageFilter stub
err:heap:HEAP_ValidateInUseArena Heap 401e0000: prev arena 40249110 is not prev for in-use 40249140
fixme:commctrl:InitCommonControlsEx Unknown class! dwICC=0x8000
err:win:CreateWindowExA bad class name "RichEdit20A"

And all the No debug messages and pointer info after that.  I have triple checked riched20.dll that it is in the right place and that the config file is correct, but I just don't know where to go from here.

You should double-check these things in particular:

• Make sure you haven't told Wine (during WineSetupTK) to use a real Windows installation; you should be using a "fake" one
  
• Install the required WinXP dll's (since WinXP is all we've been able to make Wine work with at the moment) into your "fake" /Windows/System directory (not /Windows/System32)
  
• Have the correct entries in your /.wine/config file, eg. "Windows" = "winxp" under the [Version]section, and the proper entries for eMule at the bottom before the last line that reads "# [/wineconf]":
  

  ;; eMule
  [AppDefaults\\emule.exe\\DllOverrides]
  "*" = "builtin, native"
  "comctl32" = "native"
  "riched20" = "native"

Let us know if you've verified all these and are still having problems, and we'll see what else we can dig up.

[mindpirate]

Painkiller Jane, on Mar 28 2004, 05:44 AM, said:

i'm outto ideas how it's possible to get wine working with comctl32 and commctrl from w98se... except for a desperate try to use even older w98(none SE) dlls.

My memory is probably failing me on the procedure I gave you. When I get my system back up and running I'll take a close look at CrossOver's configuration again to see what exact combination it's using and I guess I'll run a diff on CrossOver's default registry against Wine's default registry just in case. On the other hand, solving this problem could be something as simple as doing the updates in a different order.

Still not a peep from the Wine devs on the crypto problem. CrossOver support seems to be our last hope before we have to resort to Backup Plan A.

[BaggyG]

Thanks for the guidance. I tried again from the start.

Reconfigured wine using winesetuptk.
Made changes to the /.wine/config file
Checked registry entries
Recopied the DLLs from the XP Pro CD to windows\system (not 32) dir
Installed eMule .42d
ran emule with the following resault:

[baggy@server01 eMule]# wine emule.exe
fixme:ole:CoRegisterMessageFilter stub
err:heap:HEAP_ValidateInUseArena Heap 401e0000: prev arena 402494b8 is not prev for in-use 402494e8
fixme:commctrl:InitCommonControlsEx Unknown class! dwICC=0x8000
err:win:CreateWindowExA bad class name "RichEdit20A"
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e240
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e268
fixme:ole:CoCreateInstance no classfactory created for CLSID {00bb2763-6a77-11d0-a535-00c04fd7d062}, hres is 0x80040150
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e278
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e210
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e210
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e210
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e210
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e26c
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e26c
fixme:ole:CoCreateInstance no classfactory created for CLSID {00bb2763-6a77-11d0-a535-00c04fd7d062}, hres is 0x80040150
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e260
err:listview:LISTVIEW_WindowProc unknown msg 1044 wp=00000000 lp=4072e260
fixme:win:SetWindowTextA cannot set text "" of other process window (nil)
wine: Unhandled exception (thread 0009), starting debugger...
WineDbg starting on pid 8

Here is what I put in the config file:

;; eMule
[AppDefaults\\emule.exe\\DllOverrides]
"*" = "builtin, native"
"comctl32" = "native"
"riched20" = "native"
# [/wineconf]

I also changed "Windows" = "win98" to "winxp"

Don't know what to try next.

Cheers,

Baggy

[mindpirate]

BaggyG, on Mar 28 2004, 09:56 PM, said:

Don't know what to try next.

Those messages certainly seem to indicate that comctl32.dll and riched20.dll aren't being correctly identified or utilized.

A few more questions for you:

Did you install eMule after making all the changes you indicated, including the config line "Windows" = "winxp"? If not, do so, because eMule's installer attempts to detect its host environment and acts accordingly.

What version of Wine are you using, and is it a package from your Linux vendor? If you're using a version of Wine packaged by your Linux vendor, get rid of it (especially if you've got Mandrake). Try the latest official package from the Sourceforge page linked to in the howto doc.

Did you install a fresh version of Wine, or did you update or use an existing installation? Fresh is best.

Least importantly, but perhaps significant: what distribution, version, and kernel of Linux are you using?

[mindpirate]

I may have discovered a missing ingredient with our experimental DCOM installation procedure.

After DCOM98 installation, under the eMule section in your /.wine/config file, add:

"ole32" = "native,builtin"

then see how eMule acts.

I'm still without an X-enabled Linux box so I haven't been able to test this myself yet.

[Painkiller Jane]

that might get a little tricky since the DCOM98 doesn't install but quits with a messagebox saying (see my last post concerning that DCOM98 issue):

Quote

DCOM98 can only be installed on Windows98.
For Windows NT, please install latest service packs.

even though wine is set to w98 mode.
i can try the w98 comctl32, commctrl dlls with ole32 = native builtin, though.
right after the next crash. the patched emule doesn't crash very often. KAD seems to make a little trouble, making wine throw winsock errors every now and then but i'm positive that's no wine but a KAD issue.

-pkj

This post has been edited by Painkiller Jane: 30 March 2004 - 08:14 AM

[BaggyG]

Thanks for the help.

Here is the info you asked...

Quote

Did you install eMule after making all the changes you indicated, including the config line "Windows" = "winxp"?

Yes I did.

Quote

What version of Wine are you using

Wine version 20040309

Quote

is it a package from your Linux vendor?

No. RPM package from WineHQ (wine 20040309-1rh9winehq)

Quote

Try the latest official package from the Sourceforge page linked to in the howto doc.

I generaly try to use RPMs if I can. Saves headaches with sorting out dependencies. Any way. This is the latest for Red Hat.

Quote

Did you install a fresh version of Wine, or did you update or use an existing installation?

Installed fresh.

Quote

Least importantly, but perhaps significant: what distribution, version, and kernel of Linux are you using?

Redhat 9 (kernel verson 2.4.20-30.90)

Not sure if that will all help you. I also tried the trial version of the CodeWeavers CrossOver Office. Didn't work so well. I finally figured out that I was in 8bit coulour which killed it. Uninstalled and installed the Wine version above. Figured out it was the 8bit colour thing. So I got to the point where I could start using the windows apps (like regedit and the emule installer).

Cheers,
BaggyG

[mindpirate]

BaggyG, on Mar 30 2004, 06:30 AM, said:

Not sure if that will all help you.  I also tried the trial version of the CodeWeavers CrossOver Office.  Didn't work so well.  I finally figured out that I was in 8bit coulour which killed it.  Uninstalled and installed the Wine version above.  Figured out it was the 8bit colour thing.  So I got to the point where I could start using the windows apps (like regedit and the emule installer).

Color depth is definitely something that comctl32's behavior depends upon. So what was it that was set to 8-bit color, your X server, or CrossOver/Wine?

The rest of your setup sounds good.

BTW, using vendor-specific RPMs packaged by the Wine team should be alright, it's just the RPMs packaged by the vendors themselves that I'm discouraging -- at least for the time being -- because there are some well-known compatibility issues (Mandrake's Wine package being the worst, judging by the volume of cries for help in the Wine newsgroup ).

[Painkiller Jane]

after 30+ hours of running wine/emule (still the patched version on wine emulating winxp) froze so badly i couldn't even kill the wineserver nor the pthread-wine (emule) and had to reboot.
last thing wine said was:

Quote

...
fixme:winsock:NtStatusToWSAError Status code c000011f converted to DOS error code 4
fixme:winsock:NtStatusToWSAError Status code c000011f converted to DOS error code 4
wine client error:b: no fd received for handle 130240
wine client error:18: pipe: Too many open files

oh, wrt the dcom install problem. it seems to help if one sets
this:

Quote

[Version]
"Windows" = "win98"

and this

Quote

[Tweak.Layout]
;; supported styles are 'Win31'(default), 'Win95', 'Win98'
;; this has *nothing* to do with the windows version Wine returns:
;; set the "Windows" value in the [Version] section if you want that.
"WineLook" = "Win98"

the latter was set to Win95 (i can't remember touching this value so the Win31 (default) remark in the config is kinda puzzling).
anyways, dcom stopped complaining that i try to install it on a NT system but also told me there's already a newer DCOM95 or DCOM98 installed which i have to uninstall first.
well, there're no new files in the system dir so i guess some previous try to install dcom left some reg entries.
gonna try cleaning that up and see if i can get that bitch installed.

-pkj

edit: now i can install the COM update without getting

Quote

err:setupapi:SetupDefaultQueueCallbackA copy error 32 "E:\\IXP001.TMP\\comcnt.dll" -> "C:\\WINDOWS\\SYSTEM\\comctl32.dll"

but the DCOM98 still tells me there's already a newer version installed that i have to uninstall 1st. ook?
so if there's already a newer dcom98 version installed no need to install the old one, eh? hence i tried running emule and got:

Quote

jane@linux:~/wine/c/Program Files/eMule> wine emule
err:thunk:_loadthunk Unable to find thunk data 'Cctl1632_ThunkData16' in commctrl.dll, required by comctl32.dll (conflicting/incorrect DLL versions !?).
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\eMule\\emule.exe" failed, status c0000142

same as it was before updating the COM stuff. then i added that ole32 = native, builtin line to the config which looked like this:

Quote

...
;;eMule
[AppDefaults\\emule.exe\\DllOverrides]
"*" = "builtin, native, so"
"comctl32" = "native"
"commctrl" = "native"
"ole32" = "native, builtin"
...

and i got the very same error again.

This post has been edited by Painkiller Jane: 31 March 2004 - 09:29 AM

[mindpirate]

About changing "WineLook" to "Win98," good call. I didn't think to ever double-check that in the config file because I just assumed WineSetupTK was properly setting that attribute; apparently it wasn't. I'll put that tidbit into the howto when we can get this thing working under a Win98 environment.

FYI, looks like it'll be next Monday or Tuesday before my replacement motherboard arrives now. Until then I guess I'll just shut up about any new approaches to Win98 since I'm not helping much right now. In fact my shots in the dark seem to be contributing to some kind of burgeoning insanity over there. But I'm sure sifting through reams of debugging output is no small contributor either.

[mindpirate]

PKJ, if you're feeling adventurous, or just really, really bored, you might want to give this Wine setup utility bundle a try instead of the WineSetupTK method outlined in the howto:

http://franksworld.net/winetools.html

Hopefully it will yield a Win98 configuration that at least lets us install and launch eMule. I'll be giving it a try myself next week.

[Painkiller Jane]

neat tool.
too bad it only shows it's interface and regardless of what i select it just quits without a message or doing smth useful.
since frank not really states what is required to run his tool i have no idea what the problem might be.
so i'll wait for your report next week.

-jane

btw, some post on frank's forum says to install DCOM95/98 one has to use
ole32 and rcprt4 as native.
see:
http://www.frankscor...ighlight=dcom95
haven't tried, yet. will try after next crash. patched emule still semi-stable.
no crashes when completing files but after ~30hours winsock or out of file handles errors. wine and/or emule obviously leaks handles of sockets and files.
(i doubt that switching to a w98 emulation will fix that.)

This post has been edited by Painkiller Jane: 03 April 2004 - 06:30 PM

[Kry]

One thing about the HOWTO: you can only get cryptkey.dat from aMule because it's the ONLY *mule for linux that has sec ident. lmule and xmule are outdated.

[mindpirate]

@pkj:Ah, I knew about ole32 (that's why I mentioned including it in the config file) but hadn't read anything about rcprt4. I'll make note of that.

BTW FedEx reports my motherboard should be here by 4:30pm Wednesday at the latest, which means that it will probably arrive on Tuesday if my experience with them is any guide.

@Kry: Thanks, I'll put that in the next revision. What about lMule's successor ShareDaemon I wonder?

[mindpirate]

Phew...finally got my replacement mobo a few hours ago, and now my system is purring right along again. FedEx really sucks by the way.

Now I get to stress-test it with Wine/eMule. See if I can get the Win98 config working.

Any luck debugging that crash yet?

[Painkiller Jane]

no luck with the

Quote

...
fixme:winsock:NtStatusToWSAError Status code c000011f converted to DOS error code X
... repeat a few hundred times ....
wine client error:9: no fd received for handle 140096

X = 4, 6 or 9

errors yet.
it looks like a socket/handle leak. the more sources emule uses the sooner the errors.
i switched to 0.42e but it seems to be even worse with that version (hard to be certain, though).
at first i assumed this happens due to the use of kad but that wasn't the case.

-pkj

ps.: good luck with the w98 wine.

This post has been edited by Painkiller Jane: 09 April 2004 - 12:53 PM

[mindpirate]

For those interested, a good Wine tutorial was just published at IBM's developerWorks site yesterday:

http://www-106.ibm.c...-lnxw04FineWine

[mindpirate]

Alright, after a couple of days of trying every conceivable combination of "native,builtin" drivers and still not getting the toolbar to show up under a Win98 config, my brain is fried.

So I'm busting out the scalpel now... gonna dissect CrossOver mercilessly until I discover why eMule works with it in Win98 mode.

A thought occurs to me... I wonder if you would still experience those crashes if you ran eMule under CrossOver? They have a fully functional 30-day demo version on their site at http://www.codeweavers.com, so if you'd like to try... It's certainly much easier to setup and get going than Wine, no screwing around with config files and such (but you'll still have to add "riched20" = "native" for eMule).

Oops, the nurses are paging me... time for surgery. Get me 20cc's of morphine, and a Cuban cigar!

[Painkiller Jane]

Quote

I wonder if you would still experience those crashes if you ran eMule under CrossOver?

you show me yours i show you mine...

i wonder how stable does emule work for you in crossover?
gfx glitches gone? neat. but what about long time stability?

anyways, i've installed x-over and installed unsupported software 'emule'.
now i got an entry 'emule' in the x-over 'installed software' menu but how do i start emule under x-over? no icons on the dektop nor in the kde menu.
it's suposed to be obvious, right?

-pkj

This post has been edited by Painkiller Jane: 10 April 2004 - 05:14 PM

[mindpirate]

Painkiller Jane, on Apr 10 2004, 12:02 PM, said:

i wonder how stable does emule work for you in crossover?
gfx glitches gone? neat. but what about long time stability?

None of the problems we've found are present with eMule under CrossOver. That's the setup I originally used before starting this "eMule on Wine howto" project. I'm not sure if I ever ran it for more than 24 hours (my memory sucks), but I never noticed it crashing on me or locking up. That's why I've got to discover the "secret sauce".

Quote

anyways, i've installed x-over and installed unsupported software 'emule'.
now i got an entry 'emule' in the x-over 'installed software' menu but how do i start emule under x-over? no icons on the dektop nor in the kde menu.
it's suposed to be obvious, right?

That's the only odd thing about eMule with CrossOver. The start menu icons don't install properly like they do with other "unsupported" applications I've used with CrossOver.

You'll have to use the menu editor and create your own icon. Put this script in your eMule install directory (name it "emule") and point the icon to it:

#!/bin/sh
/opt/cxoffice/bin/wine emule.exe

Don't forget to "chmod u+x emule" on that before trying to use it.