April 2005 - Wine-Devel - list.winehq.org

Installing Mozilla
by Alex Woods April 22, 2005

April 22, 2005

Hello, I'm encountering a crash when trying to install Mozilla 1.7.7 under wine. I am using a fresh CVS checkout, but I've tried older revisions with the same result. Here is a backtrace. It's falling over trying to write to 0x99806858. Backtrace: =>1 0x557581df wine_cp_wcstombs(table=0x5584855c, flags=0x0, src=0x55c08a38, srclen=0x12, dst=0x99806858, dstlen=0x20, defchar=0x0, used=0x0) [/var/tmp/portage/wine-cvs-1.1/work/wine/libs/unicode/wctomb.c:161] in libwine_unicode.so.1 (0x55c08934) 2 0x55a3a4f1 WideCharToMultiByte+0xe1(page=0x0, flags=0x0, src=0x55c08a38, srclen=0xffffffff, dst=0x99806858, dstlen=0x20, defchar=0x0, used=0x0) [/var/tmp/portage/wine-cvs-1.1/work/wine/dlls/kernel/locale.c:1651] in kernel32 (0x55c08970) 3 0x60f61cfd PR_AttachThread+0x56a in nspr4 (0x55c08ae0) 4 0x60f62956 in nspr4 (+0x12956) (0x55c08b08) 5 0x61d42e13 NS_GetMemoryManager+0x1b in xpcom (0x55c08b30) 6 0x61d7680a public: virtual int __thiscall nsCaseInsensitiveCStringComparator::operator()(char,char)const +0x716 in xpcom (0x55c08b5c) 7 0x61d548ff in xpcom (+0x148ff) (0x55c08b88) 8 0x61d566ed NS_NewNativeLocalFile+0x53 in xpcom (0x55c08ce4) 9 0x00416296 in setup (+0x16296) (0x55c0cd44) 10 0x00405958 in setup (+0x5958) (0x55c0ee5c) 11 0x00415e2f in setup (+0x15e2f) (0x55c0fe94) 12 0x00424375 EntryPoint+0xce in setup (0x55c0ff20) 13 0x55a4e645 start_process+0xf5(arg=0x0) [/var/tmp/portage/wine-cvs-1.1/work/wine/dlls/kernel/process.c:1044] in kernel32 (0x55c0fff4) 14 0x55585c71 wine_switch_to_stack+0x11 in libwine.so.1 (0x00000000) I've created a +relay trace, which shows the following stuff happening just before things go pear shaped: 0011:Ret ntdll.RtlAllocateHeap() retval=559752b0 ret=572beb67 0011:Ret msvcrt.calloc() retval=559752b0 ret=60f53690 0011:Call msvcrt._strdup(60f68130 "shma") ret=60f536a2 0011:Call ntdll.RtlAllocateHeap(558c0000,00000000,00000005) ret=572bebe7 0011:Ret ntdll.RtlAllocateHeap() retval=559752d0 ret=572bebe7 0011:Ret msvcrt._strdup() retval=559752d0 ret=60f536a2 0011:Call msvcrt.getenv(60f664f4 "NSPR_LOG_MODULES") ret=60f58ed1 0011:Ret msvcrt.getenv() retval=00000000 ret=60f58ed1 0011:Call kernel32.GetVersionExA(55c089a0) ret=60f61cbc 0011:Call ntdll.RtlGetVersion(55c0877c) ret=55a71f38 0011:Ret ntdll.RtlGetVersion() retval=00000000 ret=55a71f38 0011:Ret kernel32.GetVersionExA() retval=00000001 ret=60f61cbc 0011:Call kernel32.GetTimeZoneInformation(55c08a34) ret=60f61cd6 0011:Call ntdll.RtlQueryTimeZoneInformation(55c08a34) ret=55a6fae5 0011:Ret ntdll.RtlQueryTimeZoneInformation() retval=00000000 ret=55a6fae5 0011:Call ntdll.NtQuerySystemTime(55c08874) ret=55a6ebc5 0011:Ret ntdll.NtQuerySystemTime() retval=00000000 ret=55a6ebc5 0011:Ret kernel32.GetTimeZoneInformation() retval=00000000 ret=60f61cd6 0011:Call kernel32.WideCharToMultiByte(00000000,00000000,55c08a38 L"GMT Standard Time",ffffffff,99806858,00000020,00000000,00000000) ret=60f61cfd So, it's probably worth saying that I'm on UK time. Possibly also worth noting that I am using an x86_64, with wine -m32 compiled. Any ideas? Cheers. -- Alex

1 1

version change broke InstMsiA.exe
by James Hawkins April 22, 2005

April 22, 2005

Hi, The following patch broke InstMsiA.exe: Modified files: dlls/ntdll : version.c Log message: Ivan Leo Puoti <puoti(a)inwind.it> Better EXE version check in VERSION_GetLinkedDllVersion. Patch: http://cvs.winehq.org/patch.py?id=14894 Here is +ver: trace:ver:VERSION_Init getting version from L"AppDefaults\\InstMsiA.exe\\Version" trace:ver:VERSION_Init getting default version trace:ver:VERSION_GetLinkedDllVersion L"InstMsiA.exe": 07.00/05.01/05.01/04.00 trace:ver:VERSION_GetLinkedDllVersion 07.00/05.01/05.01/04.00 trace:ver:RtlGetVersion <-- Windows XP (L"Service Pack 2") .... trace:ver:RtlGetVersion <-- Windows XP (L"Service Pack 2") trace:ver:VERSION_Init getting version from L"AppDefaults\\msiinst.exe\\Version" trace:ver:VERSION_Init getting default version trace:ver:VERSION_GetLinkedDllVersion L"msiinst.exe": 07.00/05.01/05.01/04.00 trace:ver:VERSION_GetLinkedDllVersion 07.00/05.01/05.01/04.00 trace:ver:RtlGetVersion <-- Windows XP (L"Service Pack 2") ... Before the change GetLinkedDllVersion recognized InstMsiA.exe as win98, but now it's XP SP2. I'm not sure how to change this test to make it work because both InstMsiA.exe (win9x version) and InstMsiW.exe (nt/xp version) return 07.00/05.01/05.01/04.00 for GetLinkedDllVersion. One solution is to just use the config file and specify win98, but since we are moving away from the config file I think it would be worth figuring out why this isn't working yet. -- James Hawkins

1 0

wine and gcc 4.0
by Florian Goth April 22, 2005

April 22, 2005

Hi! I've just installed gcc 4.0 and now wine(CVS) stops compiling in ./wine/dlls/msvcrt/tests : gcc -c -I. -I. -I../../../include -I../../../include -I../../../include/msvcrt -I./.. -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -O2 -o headers.o headers.c In file included from headers.c:33: ../../../include/msvcrt/wchar.h:201: warning: conflicting types for built-in function 'iswalnum' ../../../include/msvcrt/wchar.h:202: warning: conflicting types for built-in function 'iswalpha' ../../../include/msvcrt/wchar.h:204: warning: conflicting types for built-in function 'iswcntrl' ../../../include/msvcrt/wchar.h:206: warning: conflicting types for built-in function 'iswdigit' ../../../include/msvcrt/wchar.h:207: warning: conflicting types for built-in function 'iswgraph' ../../../include/msvcrt/wchar.h:208: warning: conflicting types for built-in function 'iswlower' ../../../include/msvcrt/wchar.h:209: warning: conflicting types for built-in function 'iswprint' ../../../include/msvcrt/wchar.h:210: warning: conflicting types for built-in function 'iswpunct' ../../../include/msvcrt/wchar.h:211: warning: conflicting types for built-in function 'iswspace' ../../../include/msvcrt/wchar.h:212: warning: conflicting types for built-in function 'iswupper' ../../../include/msvcrt/wchar.h:213: warning: conflicting types for built-in function 'iswxdigit' ../../../include/msvcrt/wchar.h:214: warning: conflicting types for built-in function 'towlower' ../../../include/msvcrt/wchar.h:215: warning: conflicting types for built-in function 'towupper' ../../../include/msvcrt/io.h:179: error: 'open' aliased to undefined symbol '_open' ../../../include/msvcrt/io.h:180: error: 'sopen' aliased to undefined symbol '_sopen' ../../../include/msvcrt/conio.h:57: error: 'cprintf' aliased to undefined symbol '_cprintf' ../../../include/msvcrt/conio.h:58: error: 'cscanf' aliased to undefined symbol '_cscanf' ../../../include/msvcrt/process.h:129: error: 'execl' aliased to undefined symbol '_execl' ../../../include/msvcrt/process.h:130: error: 'execle' aliased to undefined symbol '_execle' ../../../include/msvcrt/process.h:131: error: 'execlp' aliased to undefined symbol '_execlp' ../../../include/msvcrt/process.h:132: error: 'execlpe' aliased to undefined symbol '_execlpe' ../../../include/msvcrt/process.h:133: error: 'spawnl' aliased to undefined symbol '_spawnl' ../../../include/msvcrt/process.h:134: error: 'spawnle' aliased to undefined symbol '_spawnle' ../../../include/msvcrt/process.h:135: error: 'spawnlp' aliased to undefined symbol '_spawnlp' ../../../include/msvcrt/process.h:136: error: 'spawnlpe' aliased to undefined symbol '_spawnlpe' make: *** [headers.o] Error 1 make died with exit status 2

2 1

/tmp using
by Vitaly Lipatov April 22, 2005

April 22, 2005

I suppose to make patch for using TMPDIR environment variable as temp directory if it is not empty. There is hardcoded path to /tmp for wine server directory, and I would like to use ~/tmp dir... Will it change accepted and or it is not wrong intention? -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

2 1

Last call for PGP key signing party
by Shachar Shemesh April 22, 2005

April 22, 2005

Hi all, This is your last chance to get your very own PGP key signed by your community. So far, we have 6.5 participants (hoping to get it to 7 by tomorrow). This means 7 brand new signatures on your PGP key. Read the previous announcement (http://www.winehq.org/hypermail/wine-devel/2005/04/0057.html and http://www.winehq.org/hypermail/wine-devel/2005/04/0084.html) for details on what you need to do. New submissions should be possible to get right up to the party itself, assuming I can get our hosts to lend me the use of a printer (Will you?). Thanks, Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. Have you backed up today's work? http://www.lingnu.com/backup.html

2 1

shell32/shflder_unixfs: Use shell kind ITEMIDLISTs
by Michael Jung April 22, 2005

April 22, 2005

This silences some ERROR messages when browsing in the namespace extension and allows to apply shell32's helper functions. Changelog: Use the shell32 typical binary format for ITEMIDLISTs. Bye, -- Michael Jung mjung(a)iss.tu-darmstadt.de

1 0

Win16 programs and Wine internal messages
by Richard Cohen April 22, 2005

April 22, 2005

Closing Win16 programs using the Window manager doesn't work any more, because 16 bit programs don't recognize the WINE internal messages, so they don't get processed. This patch moves the internal messages to just below 0xffff, but perhaps there is a better way? Richard.

2 2

Re: USB status ...Who maintains wineserver?
by Damjan Jovanovic April 22, 2005

April 22, 2005

--- Hiji <hijinio(a)yahoo.com> wrote: > > > --- Lars Segerlund <lars.segerlund(a)comsys.se> > > wrote: > > > > > > > > What is the status of wines USB support ? > > > > Is there anything done yet or am I on my own > ? > > > > Can someone also giva a hint on the > > feasibiliyt, > > > > complexity of managing a USB > > > > implementation for wine ? I am rather good at > > > linux > > > > device drivers and such. > > > > / regards, Lars Segerlund. > > > > There's not much I can say in the way of > > > development, > > > but as a user, getting USB support (beyond > what's > > > supported in the kernel) would be a HUGE leap of > > > improvement for Wine. I think others have said > > > before > > > that there are a lot of apps out there that will > > run > > > on Wine, but are useless because they depend on > > > their > > > hardware counterpart. (In the music world, > > > Guitarport > > > comes to mind.) > > > > > > Hiji > > > I have proposed several possible solutions for > using > > USB under Linux. In fact, I have given 4 possible > > ways > > of doing it, one of which I have hacked up (and > > gotten > > to work, at least partially). > > > > If you're interested in the details, let me know, > > and > > I'll email you (or look at the "Wine device > drivers > > proposal" email in the Wine archives in the past > > month > > or so). > > Phew, I thought I'd type a short reply! Interested > > in > > working on this? I can't do it all alone. > > Damjan > > There's not much I can do other then try to > encourage > you and Lars to work together (as I'm not a C > developer). Damjan, it sounds like you have already > covered a lot of the groundwork through your > research > and understanding of the USB infrastructure (from > both > the Windows, Linux and Wine worlds). Lars, I see > you > have both the motivation and experience with Linux > device drivers to work on Wine USB. > > To me, it sounds like a perfect match for you two to > pair up and work on implementing additional USB > functionality. > > I suppose the last piece missing is to consult the > expert on the wineserver (as far as USB is > concerned) > to see if any changes would truely need to be made > there. Who would that be? I think it might be Alexander, and I think the general suggestion was "avoid changes to the wineserver". Anyone else know? > Hiji > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > __________________________________ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide

2 1

Re: WineHQ: Janitorial update
by Michael Jung April 22, 2005

April 22, 2005

Hi Dimitrie, On Friday 22 April 2005 05:47, Dimitrie O. Paun wrote: > ChangeLog > ... > Some W->A warnings are invalid. While you're at it, I think the CryptAcquireContextW W->A call in advapi32/crypt.c should also be considered an invalid warning. CryptAcquireContext calls the CSP dll's CPAcquireContext function, which is only present as an ASCII version. Thus, if we would get rid of this W->A call, we would get an A->W->A conversion chain in case of CryptAcquireContextA. Bye, -- Michael Jung mjung(a)iss.tu-darmstadt.de

1 0

Re: Program cannot be run in DOS mode
by Dustin Navea April 21, 2005

April 21, 2005

I dont think (although I could be wrong) that programs compiled in vs6 would have dependencies on .net, even if they were compiled on xp.. You said that you are able to get other programs to run, such as winzip and solitaire? If that is the case, then what I said above more than likely _is_ wrong :-/ in which case not much can be done. You could always try your hand at implementing the missing .net functions, but this may be a bigger task than it is worth. The other option if you must get it going on linux is to port it to linux using winelib, although if it is dependent on .net that may not be possible either.. Anyone else have any comments on this? Dustin Brendan Clark Ribera wrote: > Yeah, I know enough of Linux to do that. It just strikes me as weird > that all of the executables I've downloaded (WinZip, etc) have produced > no errors. Someone suggested this might be due to .NET dependencies in > the Windows XP binaries, but I might as well try a newer version of Wine. > > Brendan > > On Tue, 19 Apr 2005, Dustin Navea wrote: > >> Hi, that does seem a little strange. It could be that there is >> something wrong with the package. How familiar are you with Linux? >> Familiar enough to know what CVS is and how to use it to get the >> bleeding edge version of wine, and enough to know how to compile it >> from scratch, if I pointed you to the guide that tells you how? >> >> Dustin >> >> Brendan Clark Ribera wrote: >> >>> >>> The version I'm running is from an RPM on winehq.com (I'm running >>> Fedora Core 2). Also, I considered the .NET problem, so I compiled a >>> little "Hello World" program in Visual Studio 6, which also produced >>> this error. I don't know if perhaps VS 6 has been made to >>> encorporate .NET libraries, but I was really surprised to see that >>> program not work. >>> >>> Someone else suggested trying an NT-based winver, which I found not >>> to help. >>> >>> Brendan [-info not relevant to the nature of this specific email snipped-]

1 0