wine-devel

wine-devel@winehq.org

84463 discussions

Assertion in dlls/ntdll/loader.c
by Jon Griffiths 03 Jul '04

03 Jul '04

Hi, I'm experimenting with native vs builtin comctl32 for an app and whenever I set this dll to native I hit this assert in init_system_dir(): assert( mod->Flags & LDR_WINE_INTERNAL ); This happens on a 2.6 and a 2.4 system. I suspect its not related to comctl32 per-se, but merely loading a native dll at all (since this is the only native dll I'm using). Using all builtins does not hit this assert. I don't really grok what this function is doing, but commenting it out allows the app … [View More]

1 0

Re: Pango for BiDi
by Shachar Shemesh 03 Jul '04

03 Jul '04

Jonathan Wilson wrote: >> Maybe we can get our supplied packages to be BiDi enabled, but so >> long as we use ICU, and ICU has this horrible linking policy, we >> can't really > > What linking policy? > > I checked the IBM ICU website (http://oss.software.ibm.com/icu/ and > specifically > http://oss.software.ibm.com/cvs/icu/~checkout~/icu/license.html and it > appears to be under the X11 licence which is GPL compatible. > > IANAL but unless … [View More]

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Peter Dennis Bartok 03 Jul '04

03 Jul '04

May I remind you that this thread was started by you, asking why we are abandoning Wine, not by me complaining about Wine. All I did was give you the reasons why we are no longer using Wine. You may not like them, you may disagree with them, but the decision has been made. And there is really nothing to be gained in nitpicking or pointing fingers. I don't understand the comment about managed Quake, but we don't have to create managed Wine. We simply have to create the SWF controls in managed … [View More]code and the underlying SWF framework. Wine doesn't have anything to do with the framework, anyway, so it's down to the controls. And even by using the Wine controls we still would have to either modify Wine to support the additional functionality required by SWF, or subclass them, basically recreating the drawing code for those controls and just using the WndProc messages from Wine. So, you can see it's really just a small step to then drop Wine and handle the management of Windows ourselves instead of using Wine for it. Not trying to be rude either. You asked, I answered. Peter -----Original Message----- From: "Steven Edwards" <steven_ed4153(a)yahoo.com> To: "Peter Dennis Bartok" <peter(a)novonyx.com>; <mono-winforms-list(a)ximian.com> Cc: <wine-devel(a)winehq.com> Date: Thursday, 01 July, 2004 21:03 Subject: Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans. >Hello Peter, > >I am not trying to be rude but... > >--- Peter Dennis Bartok <peter(a)novonyx.com> wrote: >> >Rather than spending a whole lot of time rewritting things wouldnt >> it >> >be better to help the Wine project get stable and move to the 1.0 >> goal? >> >There is a roadmap and TODO on Winehq of things that are needed for >> >1.0. >> No, it wouldn't. Even if Wine already was 1.0 we still would not have >> the >> portability we're trying to get (ie. run on Solaris Sparc, Mac OS, >> etc) and > >Well Winelib does run on PPC and the port to Sparc is mostly done. 99% >of Wine even compiles on Alpha here for me. See > >http://www.winehq.com/site/status_porting > >> debugging would still be almost impossible (Wine does funky stuff >> with >> register for thread storage, special stuff would be required to setup >> Mono-created threads before they'd be able to call Wine functions, >> etc). >> Also, there doesn't seem to be much interest from the Wine community >> to do >> anything that helps using Wine with SWF/Mono. We've had to resort to >> some >> quite complicated mechanisms to even be able to use Wine as a shared, >> runtime attached library, after Alexandre rejected a patch that only >> touched >> six lines of existing Wine code and added a new library to Wine, to >> allow >> straightforward use of Wine as a library. Having to take instead the >> complicated route it now means that many people are having problems >> getting >> SWF to run at all, with due to strict path dependencies. > >I was there when Miguel came online to ask why the patch was not merged >and I also seem to recall Alexandre proposed a fix the would work and >seemed to make Miguel happy. > >See: >http://www.winehq.org/hypermail/wine-devel/2004/03/0150.html > >> Another problem was that we had to spend way too much time tracking >> what >> changed from one Wine version to the next. For example from April to >> May, >> the wine_get_unix_file_name() function arguments were changed (I'm >> not even >> asking why it was changed instead of introducing a new function with >> different arguments and leaving the old one for those people who >> might use >> it). Since I can't require always the latest Wine version, I have to >> come up >> with code figuring out what Wine version might be running, and write >> code to >> make version dependent Wine calls. I'd rather spend that time >> improving SWF. > >Once again how can you fuss about unstable interfaces on a project that >does not have a stable release? You could work with Winehq to create >those stable interfaces. > >Besides how can you blame the Wine project for tracking changes when >the first patch Mono submitted was this? > >http://primates.ximian.com/~duncan/mono-wine/sources/mono-wine.patch > >A whole bunch of #ifdefs and other kludges that violates Winehq coding >standards. > >> Notice how people complain on this mailing that they're having >> problems >> getting even basic stuff going? The SWF code works, it's the >> interaction >> with Wine that's mostly causing the problems. Again, as I said, it >> will >> become much easier for the regular user once the Wine dependency is >> removed >> and the controls are all in managed code. > >Alright well I am not claiming to know very much about the project. >Like I said I only lurk here because I care about how its going to run >on ReactOS. I guess my final though on the matter is that if Vertigo >Software could make a mananged Quake2, how hard can it be for you to >make a managed Wine? > >Thanks >Steven > > > > >__________________________________ >Do you Yahoo!? >Yahoo! Mail - 50x more storage than other providers! >http://promotions.yahoo.com/new_mail >_______________________________________________ >Mono-winforms-list maillist - Mono-winforms-list(a)lists.ximian.com >http://lists.ximian.com/mailman/listinfo/mono-winforms-list > > [View Less]

8 9

IE6 installation error. would you please give me a suggession
by Shiva Ram Krishna 03 Jul '04

03 Jul '04

Dear Sir/Madam, I downloaded the latest cvs of wine and compiled it. All went well but it seems that the regsvr32.exe.so file wasn't created properly. If check the dependency o f expand.exe.so, winver.exe.so, winepath.exe.so, I can see all the proper files that it needs but if I do it on regsvr32.exe.so, it says "regsvr32.exe.so: Not a dynamic executable". I have that his problem for the last 3-4 months. I used a text editor and it seems that the header is the regsvr 32.exe.so looks like an … [View More]

4 3

Re: collation tables
by Dmitry Timoshkov 03 Jul '04

03 Jul '04

"Vitaly Lipatov" <lav(a)altlinux.ru> wrote: > > What app is it? In which way it depends on the collation table > > being MS compatible? > It is 1C, an accounting system, widely used in Russia. > It keep a copy "right" collation table in exe file and compare it > with gotten from system. > > > Crossover Office has a patched version > > libs/unicode/collation.c, could you try it with your > > aplication? > If I have not Crossover Office, how I … [View More]

2 4

taskmgs hangs on edit debug channels
by Andrei Barbu 02 Jul '04

02 Jul '04

The taskmanager dies when trying to edit the debug channels of any programs with the newest CVS (checked out 2 days ago) It just sits there with this: 002e:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=409cd43c 002e:Call kernel32._ConfirmSysLevel(40a08ac0) ret=409a3f15 002e:Ret kernel32._ConfirmSysLevel() retval=00000000 ret=409a3f15 002e:Call kernel32.GlobalLock16(0000116f) ret=40999b70 002e:Ret kernel32.GlobalLock16() retval=404326d0 ret=40999b70 002e:Call kernel32.… [View More]ReleaseThunkLock(41625f7c) ret=409cd30f 002e:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409cd30f 002e:trace:msg:GetMessageW (116f) mask=0000007f, bits=00000000, changed=00000000, waiting 002e:Call kernel32.ReleaseThunkLock(41625fe4) ret=409cd684 002e:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409cd684 002e:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,404326d4,ffffffff,00000000,00000000) ret=409cd6c6 002e:Call ntdll.RtlEnterCriticalSection(40d76680) ret=40d54902 002e:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40d54902 002e:Call ntdll.RtlLeaveCriticalSection(40d76680) ret=40d54932 002e:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40d54932 002e:Call ntdll.RtlEnterCriticalSection(40d76680) ret=40d54902 002e:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40d54902 002e:Call ntdll.RtlLeaveCriticalSection(40d76680) ret=40d54932 002e:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40d54932 002e:Call kernel32.WaitForMultipleObjectsEx(00000002,41625dac,00000000,ffffffff,00000000) ret=40d383db 002e:Call ntdll.NtWaitForMultipleObjects(00000002,41625ba0,00000000,00000000,00000000) ret=40591c85 If I move the mouse it spits out the correct mouse messages which indicate that wine itself is running just fine. The taskmanager window doesn't get redrawn (the black backround around it does). The backtrace from that point is: =>1 0x400636a9 (0x41b2be48) 2 0x402335c2 NTDLL_wait_for_multiple_objects+0x122(count=0x1, handles=0x41b2bf38, flags=0x4, timeout=0x0) [sync.c:587] in ntdll (0x41b2beec) 3 0x40233636 NtWaitForMultipleObjects+0x66(count=0x1, handles=0x41b2bf38, wait_all=0x0, alertable=0x0, timeout=0x0) [sync.c:605] in ntdll (0x41b2bf14) 4 0x40591c85 WaitForMultipleObjectsEx+0xb5(count=0x1, handles=0x41b2c06c, wait_all=0x0, timeout=0xffffffff, alertable=0x0) [sync.c:171] in kernel32 (0x41b2c044) 5 0x40591b1a WaitForSingleObject+0x3a(handle=0x6c, timeout=0xffffffff) [sync.c:99] in kernel32 (0x41b2c064) 6 0x40656867 ProcessPageRefreshThread+0x87(lpParameter=0x0) [procpage.c:511] in taskmgr (0x41b2c1a4) 7 0x40598fba THREAD_Start+0x11a(ptr=0x40450220) [thread.c:107] in kernel32 (0x41b2c27c) 8 0x40234fe9 start_thread+0x199(info=0x40450240) [thread.c:198] in ntdll (0x41b2cacc) 9 0x4005df70 (0x41b2cbcc) 10 0x4017e40a (0x00000000) Any ideas? I'm not quite versed enough in wine to know what's happening too well. I realise it's a thread waiting for another that apparently never finishes.. or I think it is, and I'm kind of lost from there. Thanks, Andrei [View Less]

2 1

Delayed breakpoints in winedbg
by Adrian Rees 02 Jul '04

02 Jul '04

Hi all, Apologies in advance for what is probably a dumb question... I'm trying to debug a windows application by breaking on a call to a DLL function - in fact it's the NtCreateKey function within the ntdll library. I must be missing something fundamental because the debugger indicates that it has set a delayed breakpoint, but the breakpoint is never reached, although turning on debugging messages clearly indicates that the function is being called. Here's a typical attempt: $ WINDEBUG=… [View More]

2 3

Re: collation tables
by Dmitry Timoshkov 02 Jul '04

02 Jul '04

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > Given that simply calling whatever the locale functions are on windows and > using their results is considered too legally risky (because the results > are almost certainly covered under a MS copyright), the best solution is to > simply take the best possible implementation we have now then build a > testcase. Build a testcase that calls the locale functions and checks that > the output matches. From there, you can … [View More]

1 0

Re: winedbg crashes
by Jon Griffiths 02 Jul '04

02 Jul '04

Hi Eric, <cc'd to wine-devel so anyone with a similar problem can google for the fix> > no, it's normal you get this. In fact, we should simply abort the > loading. > Does this work better ? I can't test it unfortunately, but it looks like the right thing to do. I asked on bugs@binutils and was told to upgrade to binutils 2.15 to fix the bad stab generation. Sure enough, this fixes the issue (which means I can't duplicate this behaviour any more). It also fixed a bunch of … [View More]

1 0

IE6 installation error. would you please give me a suggession
by Shiva Ram Krishna 02 Jul '04

02 Jul '04

Dear Sir/Madam, I downloaded the latest cvs of wine and compiled it. All went well but it seems that the regsvr32.exe.so file wasn't created properly. If check the dependency of expand.exe.so, winver.exe.so, winepath.exe.so, I can see all the proper files that it needs but if I do it on regsvr32.exe.so, it says "regsvr32.exe.so: Not a dynamic executable"… [View More]

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Peter Dennis Bartok 02 Jul '04

02 Jul '04

>You are asking for stable interfaces and those can only come once there >is a Wine 1.0. Its not here and dont get me wrong I think the Wine TODO >list is way to long and things should be close to frozen by now but >thats not the case. All you are doing is pointing out that its not >stable which is well known. I wish it was stable now but its not and >until the TODO is done its not going to be. Paul's message was very specific, asking about a versioning interface (which I … [View More]

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Steven Edwards 02 Jul '04

02 Jul '04

Hello Peter, I am not trying to be rude but... --- Peter Dennis Bartok <peter(a)novonyx.com> wrote: > >Rather than spending a whole lot of time rewritting things wouldnt > it > >be better to help the Wine project get stable and move to the 1.0 > goal? > >There is a roadmap and TODO on Winehq of things that are needed for > >1.0. > No, it wouldn't. Even if Wine already was 1.0 we still would not have > the > portability we're trying to get (ie. run … [View More]on Solaris Sparc, Mac OS, > etc) and Well Winelib does run on PPC and the port to Sparc is mostly done. 99% of Wine even compiles on Alpha here for me. See http://www.winehq.com/site/status_porting > debugging would still be almost impossible (Wine does funky stuff > with > register for thread storage, special stuff would be required to setup > Mono-created threads before they'd be able to call Wine functions, > etc). > Also, there doesn't seem to be much interest from the Wine community > to do > anything that helps using Wine with SWF/Mono. We've had to resort to > some > quite complicated mechanisms to even be able to use Wine as a shared, > runtime attached library, after Alexandre rejected a patch that only > touched > six lines of existing Wine code and added a new library to Wine, to > allow > straightforward use of Wine as a library. Having to take instead the > complicated route it now means that many people are having problems > getting > SWF to run at all, with due to strict path dependencies. I was there when Miguel came online to ask why the patch was not merged and I also seem to recall Alexandre proposed a fix the would work and seemed to make Miguel happy. See: http://www.winehq.org/hypermail/wine-devel/2004/03/0150.html > Another problem was that we had to spend way too much time tracking > what > changed from one Wine version to the next. For example from April to > May, > the wine_get_unix_file_name() function arguments were changed (I'm > not even > asking why it was changed instead of introducing a new function with > different arguments and leaving the old one for those people who > might use > it). Since I can't require always the latest Wine version, I have to > come up > with code figuring out what Wine version might be running, and write > code to > make version dependent Wine calls. I'd rather spend that time > improving SWF. Once again how can you fuss about unstable interfaces on a project that does not have a stable release? You could work with Winehq to create those stable interfaces. Besides how can you blame the Wine project for tracking changes when the first patch Mono submitted was this? http://primates.ximian.com/~duncan/mono-wine/sources/mono-wine.patch A whole bunch of #ifdefs and other kludges that violates Winehq coding standards. > Notice how people complain on this mailing that they're having > problems > getting even basic stuff going? The SWF code works, it's the > interaction > with Wine that's mostly causing the problems. Again, as I said, it > will > become much easier for the regular user once the Wine dependency is > removed > and the controls are all in managed code. Alright well I am not claiming to know very much about the project. Like I said I only lurk here because I care about how its going to run on ReactOS. I guess my final though on the matter is that if Vertigo Software could make a mananged Quake2, how hard can it be for you to make a managed Wine? Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail [View Less]

1 0

collation tables
by Vitaly Lipatov 01 Jul '04

01 Jul '04

In test dlls/kernel/tests/locale.c I see comment /* this requires collation table patch to make it MS compatible */ I get trouble with one program it needed collation table to be identical to MS table. Does anyone knows what is the better way to fix this tables, in which place? Can I fix libs/unicode/cpmap.pl for it? Any suggestions? -- Lav Vitaly Lipatov Saint-Petersburg GNU! ALT Linux Team! LaTeX! LyX!

2 1

Re: fix bug in GetCPInfo
by Uwe Bonnes 01 Jul '04

01 Jul '04

>>>>> "Vitaly" == Vitaly Lipatov <lav(a)altlinux.ru> writes: Vitaly> Bug: When call GetCPInfo with CP_ACP for example, in returned Vitaly> structure field CodePage filled with CP_ACP constant, not real Vitaly> codepage of current ACP. The attached patch fix this bug. I Vitaly> have compared behavior of this functions with Win2003. This implies, that you have written a test. Please provide the test for our test suite. Bye -- Uwe Bonnes … [View More]

2 1

psapi.dll tests
by Ferenc Wagner 01 Jul '04

01 Jul '04

Hi, please somebody enlighten me! How does this test work once psapi_test.exe is linked with -lpsapi? How can a program start at all without one of its hard dependencies? START_TEST(module) { dll = LoadLibrary("psapi.dll"); if (!dll) { trace("LoadLibraryA(psapi.dll) failed: skipping tests with target module\n"); return; } The above seems to be a common idiom which I don't understand as opposed to using GetProcAddress and invoking functions through pointers. … [View More]

2 2

Bad Icon display with native comctl32
by Uwe Bonnes 01 Jul '04

01 Jul '04

Hallo, running with native comctl32, some programs show a bad icon display in treeviews. E.g. Xilinx ISE shows this behaviour. A JPG of the treeview with Icons is appended. A debug log with +relay,+bitmap,+x11drv is about 400 MByte. Any hints how to tackle that problem? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Cleaning up W->A calls
by James Hawkins 01 Jul '04

01 Jul '04

I recently decided to help with the development of Wine, and seeing as how I am new to the process, I have chosen menial tasks to take on. This way I can learn more about Wine while contributing. I am currently working on the janitorial task of getting rid of W->A calls and I have a few questions about how I should implement these changes. I'll start the question with an example: dlls/advapi32/crypt.c line 255, 482 BOOL WINAPI CryptAcquireContextA (HCRYPTPROV *phProv, LPCSTR … [View More]pszContainer, LPCSTR pszProvider, DWORD dwProvType, DWORD dwFlags) { ... complete implementation } BOOL WINAPI CryptAcquireContextW (HCRYPTPROV *phProv, LPCWSTR pszContainer, LPCWSTR pszProvider, DWORD dwProvType, DWORD dwFlags) { PSTR pProvider = NULL, pContainer = NULL; BOOL ret = FALSE; TRACE("(%p, %s, %s, %ld, %08lx)\n", phProv, debugstr_w(pszContainer), debugstr_w(pszProvider), dwProvType, dwFlags); if ( !CRYPT_UnicodeToANSI(pszContainer, &pContainer, -1) ) CRYPT_ReturnLastError(ERROR_NOT_ENOUGH_MEMORY); if ( !CRYPT_UnicodeToANSI(pszProvider, &pProvider, -1) ) { CRYPT_Free(pContainer); CRYPT_ReturnLastError(ERROR_NOT_ENOUGH_MEMORY); } ret = CryptAcquireContextA(phProv, pContainer, pProvider, dwProvType, dwFlags); if (pContainer) CRYPT_Free(pContainer); if (pProvider) CRYPT_Free(pProvider); return ret; } Initially CryptAcquireContextW converts all of its arguments to ansi then calls CryptAcquireContextA (which is intuitively not what we're wanting and thus the cleanup.) The question is, what exactly is the best way to clean this up? It seems to me that there are two main options as to what can be done: A) convert the W->A calls in the wide-char functions to A->W calls in the asci functions and implement the wide-char functions instead, or B) implement both asci and wide-char functions separately ie asci functions only call asci functions etc. If we are to choose plan A, I have seen several different methods of converting asci to wide-char, and I am wondering which method is best. for example: dlls/advapi32/crypt.c lines 133-141 wcount = MultiByteToWideChar(CP_ACP, 0, str, -1, NULL, 0); wcount = wcount < wstrsize/sizeof(WCHAR) ? wcount : wstrsize/sizeof(WCHAR); if (wstrsize == -1) *wstr = CRYPT_Alloc(wcount * sizeof(WCHAR)); if (*wstr) { MultiByteToWideChar(CP_ACP, 0, str, -1, *wstr, wcount); return TRUE; } and, dlls/advapi32/registry.c lines 1626-1636 LONG WINAPI RegSaveKeyA( HKEY hkey, LPCSTR file, LPSECURITY_ATTRIBUTES sa ) { UNICODE_STRING *fileW = &NtCurrentTeb()->StaticUnicodeString; NTSTATUS status; STRING fileA; RtlInitAnsiString(&fileA, file); if ((status = RtlAnsiStringToUnicodeString(fileW, &fileA, FALSE))) return RtlNtStatusToDosError( status ); return RegSaveKeyW(hkey, fileW->Buffer, sa); } Which method is better/more efficient? I would have to argue that implementing both the asci functions and wide-char functions separately would be the most efficient way to solve the W->A problem. Throughout all the wine libs, many conversion calls are being made from W->A and A->W, when most of these calls could be left out. I think performance would improve without all of the conversion calls. Granted the size of the code would increase, but speed would also increase. There are a couple snags when it comes to implementing asci and wide-char functions independently, but that can be discussed later. If I'm totally off the mark, let me know, and if there are other jobs I could be doing, let me know as well because I would like to contribute, but I'm not exactly sure what to do yet. Thankyou for your time. James Hawkins truiken(a)comcast.net [View Less]

4 4

Re: dlls/shell32 W->A cleanup of systray.c
by Marcelo Duarte 30 Jun '04

30 Jun '04

Danny Hawkins wrote: >Hi, > >Converted all wide-char->ansi calls to ansi->wide-char in systray.c > > > The TTM_UPDATETIPTEXTA should be converted to TTM_UPDATETIPTEXTW and TTM_ADDTOOLA -> TTM_ADDTOOLW >@@ -272,13 +272,13 @@ > ti.rect.bottom = ICON_SIZE+2*ICON_BORDER; > > if(modify) >- SendMessageA(ptrayItem->hWndToolTip, TTM_UPDATETIPTEXTA, 0, (LPARAM)&ti); >+ SendMessageW(ptrayItem->hWndToolTip, TTM_UPDATETIPTEXTA, 0, (… [View More]

1 0

Scrollbars, an application bug or a wine regression ? (#2314)
by Gabriele Giorgetti 30 Jun '04

30 Jun '04

Hello, I've noticed a problem with scrollbars in the latest Wine's release (20040615). With wine version 20040505 everything was just fine. I've attacched a zip file with two screenshots (pls. see wine BUG #2314 @ bugs.winehq.org ) the first one is the correct behavior of the app using wine 20040505 the second one is wine 20040615 and the app in its wrong behavior. Trying to describe the problem: The application show up with a bottom scrollbar and a right scrollbar even if they are not needed.… [View More]

5 9

err:opengl:X11DRV_ChoosePixelFormat Flag not supported
by Tobias Burnus 30 Jun '04

30 Jun '04

Hello, I have the following problems with WINE, CVS version as of yesterday and Crystal Impact's Diamond http://www.crystalimpact.com/diamond/ http://www.crystalimpact.com/download/diamond/demo/dm2demo.exe, which installs flawlessly. a) I get a err:opengl:X11DRV_ChoosePixelFormat Flag not supported when I open e.g. ./Samples/Minerals/Copper.dsf and a dialogbox with the following text is shown: ChoosePixelFormat() returns 0 (last error = 0) SetPixelFormat() returns 1 (last … [View More]

1 0

Re: Typo in winedbg
by Mike Hearn 30 Jun '04

30 Jun '04

On Mon, 28 Jun 2004 20:45:35 -0400, Andrei Barbu wrote: > This fixes debuggee to debugger. I think debuggee is the right word, it means "the one that is being debugged". Ctrl-C doesn't interrupt winedbg, it interrupts the process you are currently attached to.

2 1

Failed to compile on Sparc/Solaris 9
by John O'Donnell 30 Jun '04

30 Jun '04

make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/export/home/root/wine/wine/dlls/newdev' make[2]: Entering directory `/export/home/root/wine/wine/dlls/ntdll' ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ntdll.spec cdrom.o critsection.o debugbuffer.o debugtools.o directory.o env.o error.o exception.o file.o heap.o large_int.o loader.o loadorder.o misc.o nt.o om.o path.o process.o reg.o relay.o resource.o rtl.o rtlbitmap.o rtlstr.o sec.o server.o signal_i386.… [View More]

1 0

[RFC] Wine upgrade procedure (spec)
by Dimitrie O. Paun 30 Jun '04

30 Jun '04

Hi folks, It seems that we are getting ever so closer to 0.9. Slow, but steady. Looking at the TODO, it looks like upgrading is one of the big showstoppers, in that it will affect (1) the end-user experience, and (2) how we deal with the configuration. So this seems like a good time to start discussing this topic, as we need to eventually reach the elusive 0.9. This seems to be a difficult topic, so we need to approach the problem well prepared. That is, we need to first define (and agree) … [View More]on what we need to solve here. So after a tumultuous discussion on IRC, I decided to get the ball rolling. Intuitively, upgrading wine is simple to understand: once a new version is installed, we need to get users in a state where they can use it. While simple to state, this problem is complicated by the various corner cases that can appear in Real Life (TM): -- native vs. builtin DLLs handling -- multiple Wine installations on a box -- updating only some DLLs -- integrating into the Unix environment -- dealing with Windows software We can also look at some important use-cases that we need to support, but before we do, the following must hold true in all cases: -- administrators should be able to install a new Wine on the system easily with "rpm -U" (or equivalent). -- the upgrade should not erase registry settings that are managed by the user Let's look at the use-cases: A. Global Install In this case, both Wine code, as well as applications are installed globally, for all users to access. This is the most Unix-like setup, but unfortunately the most difficult to support, due to the fact that Win32 apps simply expect a different environment. Since we can't control application's code, this setup may present some limitations, but it may be sufficient for sites that need a limited set of applications. For this to work, it is acceptable that we ship special scripts that know about the applications that are supported, so that they can work around inherent limitations in the applications themselves. Users should transparently be able to use the new version of wine, the next time they start wine. B. Mixed Install Here, Wine code is installed globally, but applications are installed in the user's account. In a way is like (A) but with some additional applications installed directly into the user's account. Same requirements apply to this case as well. C. Local Install Both Wine code, as well as applications are installed locally, into the user's account. The Wine code is still installed globally by the administrator (as in A & B), but it is copied locally before it's being used. An upgrade in this case may require an explicit action by the user, so the upgrade can happen at a controlled time, when the user desires it. In all of the above, there is always state in the user directory. Thus, it is imperative that the upgrade process makes sure that after the upgrade, the user-private state is consistent with the new code base. Also, any solution must take into account that the registry must be created on the fly, as it is created when registering the DLLs. Before we go any further, I'd like to ask everybody to contribute their thoughts/requirements/desires so that we get a conprehensive view of the problem we are trying to solve. Thanks for reading this far! -- Dimi. [View Less]

3 3

A wine magic trace key
by Andrei Barbu 29 Jun '04

29 Jun '04

I'm about to implement a set of keys that lets me enable disable traces any time. Seems to me like it's a good idea, like that I can get traces for exactly what I need. Especially when I'm faced with weird debugger output that's 10 minutes into the game and I can't turn traces on to begin with. Is there another way, possibly existing, to do this? Is this a really bad idea? If people are interested I can post a patch later on today or tomorrow with it. It'll be implemented in the x11 driver … [View More]

3 4

Temporary moderator needed
by Duane Clark 29 Jun '04

29 Jun '04

Howdy, Someone is needed for the period June 30-July 5 to handle moderation of the Wine lists. If you are willing to do it, please email me off list. Thanks.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel