January 2004 - Wine-Devel - list.winehq.org

Re: File change notifications

by Duane Clark

Hans Leidekker wrote: > On Thursday 29 January 2004 01:01, Duane Clark wrote: > >>For some reason, a comment end is missing there. But otherwise, it seems >>to work fine with the one important app I use file notification on. > > > Which app is that? Xilinx ISE, a program for use when designing with Xilinx chips.

Jan. 29, 2004

Re: Wine totally broken on Fedora Core because of security patch in kernel

by Kevin DeKorte

I've found that setting my /etc/sysconfig/prelink file options to this PRELINK_OPTS="-m --no-exec-shield" And then prelink -au to undo the existing links and then prelink -a to do the prelinking with the new options Kevin On Thursday 29 January 2004 10:05 am, Ivan Leo Murray-Smith wrote: > FC has some security patch in the kernel, so wine fails with this error: > > err:virtual:map_image Standard load address for a Win32 program > (0x00400000) not available - security-patched kernel ? > wine: could not load L"C:\\Program Files\\Common > Files\\InstallShield\\Engine\\6\\Intel 32\\IKernel.exe" as Win32 binary > > as reported by Marek Lipovcan and some users on the newsgroup, I don't have > fc myself, but I guess something should be done about this. > > Ivan.

Jan. 29, 2004

Re: Wine totally broken on Fedora Core because of security patch in kernel

by Mike Hearn

On Thu, 29 Jan 2004 18:05:44 +0100, Ivan Leo Murray-Smith wrote: > FC has some security patch in the kernel, so wine fails with this error: > > err:virtual:map_image Standard load address for a Win32 program (0x00400000) > not available - security-patched kernel ? > wine: could not load L"C:\\Program Files\\Common > Files\\InstallShield\\Engine\\6\\Intel 32\\IKernel.exe" as Win32 binary > > as reported by Marek Lipovcan and some users on the newsgroup, I don't have fc > myself, but I guess something should be done about this. I'm working on this. I hope to have something to show at WineConf. For now the Fedora RPMs contain a hack to keep things rolling along, I suggest people who encounter this error use them.

Jan. 29, 2004

Wine totally broken on Fedora Core because of security patch in kernel

by Ivan Leo Murray-Smith

FC has some security patch in the kernel, so wine fails with this error: err:virtual:map_image Standard load address for a Win32 program (0x00400000) not available - security-patched kernel ? wine: could not load L"C:\\Program Files\\Common Files\\InstallShield\\Engine\\6\\Intel 32\\IKernel.exe" as Win32 binary as reported by Marek Lipovcan and some users on the newsgroup, I don't have fc myself, but I guess something should be done about this. Ivan.

Jan. 29, 2004

Re: OLEPictureImpl_Load CreateIcon failed

by Fabian Cenedese

>>I'm still on the VB SSTab problem as described here: >> >>http://www.winehq.org/hypermail/wine-devel/2003/12/0157.html > >I now know that it works if there are icons (property Picture) assigned >to the single tabs in the TabCtrl. But if the icons are missing, wine >goes woo. So either wine shouldn't try to create pictures if there >aren't any, or it should cope with failing CreateIcon calls. I guess >the first case would be better. May not be the right solution but makes an SSTab without icons come up. bye Fabi Index: dlls/oleaut32/olepicture.c =================================================================== RCS file: /home/wine/wine/dlls/oleaut32/olepicture.c,v retrieving revision 1.30 diff -u -r1.30 olepicture.c --- dlls/oleaut32/olepicture.c 5 Sep 2003 23:08:33 -0000 1.30 +++ dlls/oleaut32/olepicture.c 29 Jan 2004 16:19:25 -0000 @@ -873,6 +873,9 @@ hr=IStream_Read(pStm,header,8,&xread); if (hr || xread!=8) { FIXME("Failure while reading picture header (hr is %lx, nread is %ld).\n",hr,xread); + return hr; + } + if (header[1]==0) { return hr; } if (header[1] > statstg.cbSize.QuadPart) {/* Incorrect header, assume none. */

Jan. 29, 2004

Re: OLEPictureImpl_Load CreateIcon failed

by Fabian Cenedese

>I'm still on the VB SSTab problem as described here: > >http://www.winehq.org/hypermail/wine-devel/2003/12/0157.html > >I looked further into this to find out what happens with this picture >stuff. I found out that it fails in this function (from olepicture.c): > > * OLEPictureImpl_IPersistStream_Load (IUnknown) > * Loads the binary data from the IStream. Starts at current position. > * Currently implemented: BITMAP, ICON, JPEG. >static HRESULT WINAPI OLEPictureImpl_Load(IPersistStream* iface,IStream*pStm) { > >It first reads the picture size from the stream and reads the picture >properties and data. This works sometimes, I can see it creating >e.g. 32x32 pictures for icons. But in this error I have it always >fails due to the reported picture data size of zero. So it doesn't >read any picture properties from the stream and tries to create >a picture with 0x0 dimensions. Obviously this fails. >But now I can't find out where this comes from. What is this stream >where it wants to read data from? In what source file is this implemented? >The used IStream_Load is just a macro. What could have gone wrong >earlier that this picture size is now zero? Maybe the stream is ok but >wine wants to create more pictures than there are? Another one of my threads :) I now know that it works if there are icons (property Picture) assigned to the single tabs in the TabCtrl. But if the icons are missing, wine goes woo. So either wine shouldn't try to create pictures if there aren't any, or it should cope with failing CreateIcon calls. I guess the first case would be better. bye Fabi

Jan. 29, 2004

Re: NHL2004 (d3d, kernel32, lz32)

by Abdul Ahmad

Okay, so I copied version.dll from win98se, but now this is what I get: First chance exception: page fault on read access to 0x00000000 in 32-bit code (0x00426cbd). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:003b GS:0033 EIP:00426cbd ESP:0021fc34 EBP:00000000 EFLAGS:00210216( R- 00 I -A-P1 ) EAX:00000000 EBX:00000001 ECX:0021fc2c EDX:00000271 ESI:b61ae010 EDI:0084b36c Stack dump: 0x0021fc34 (_end+0x10daa8): 0084b36c b61ae010 0042790f 102f4e04 0x0021fc44 (_end+0x10dab8): 00000000 00000001 00409e3c 00000001 0x0021fc54 (_end+0x10dac8): b61726a0 0040714d 00000001 00000000 0x0021fc64 (_end+0x10dad8): 0021ff2c 1038ce28 0121fcef 005c3a5a 0x0021fc74 (_end+0x10dae8): 00000640 000004b0 40191a1c 4d5c3a43 0x0021fc84 (_end+0x10daf8): 6f442079 656d7563 5c73746e 204c484e 0x0021fc94 (_end+0x10db08): Backtrace: =>0 0x00426cbd (nhl2004.exe.EntryPoint+0x25c74 in nhl2004.exe) (ebp=00000000) 0x00426cbd (nhl2004.exe.EntryPoint+0x25c74 in nhl2004.exe): movl 0x0(%eax),%edi hmm... is there any way i can get something more detailed to figure out whats wrong? I AM using a blank kernel32.dll and a blank lz32.dll.. im figuring that those dll's might be critical... the only other thing i can think of is theres something wrong with my sound setup because i get that OSS error, or the implementation of D3D isn't complete enough to run it... does anyone know what the function of lz32.dll is by the way? Abdul-Haseeb Ahmad wrote: > I just tried the NHL 2003 demo right now, since it would be the most > relevant game to try since it also uses IE.. it has problems > initializing the WinMM components.. im not sure but i have a feeling > this might be because something isn't configure right.. i get this error > when i start wine everytime: > > err:wave:OSS_WaveOutInit /dev/mixer1: No such device > err:wave:OSS_WaveInInit /dev/mixer1: No such device > > anyone know how i could fix that? > > the exact error i get running nhl2003 is: > Backtrace: > =>0 0x005bb868 (nhl2003Demo.exe.EntryPoint+0xf301 in nhl2003Demo.exe) > (ebp=0065a4e4) > 1 0x6f724265 (MIDIMAP.DRV..data+0x29e70265) (ebp=6c746954) > *** Invalid address 0x6c746954 (MIDIMAP.DRV..data+0x26e92954) > > 0x005bb868 (nhl2003Demo.exe.EntryPoint+0xf301 in nhl2003Demo.exe): movl > 0x0(%eax),%ecx > > > also, NHL 2000 works in software mode from what i recall, NHL 2002 has a > problem selecting the video card that im using, it has something to do > with that program it uses, 3DSetup, like all of the older EA Games.. > > Backtrace: > =>0 0x600024ae (DX7Z.DLL._THRASH_selectdisplay(a)4+0x23e in DX7Z.DLL) > (ebp=00000000) > > 0x600024ae (DX7Z.DLL._THRASH_selectdisplay(a)4+0x23e in DX7Z.DLL): movl > 0x0(%eax),%ecx > > when I run 3DSetup to setup my videocard, it goes back to the > version.dll problem i was having with NHL2004: > Backtrace: > =>0 0x408c5d8b (VERSION.DLL.VerQueryValueA+0xa7 in VERSION.DLL) > (ebp=4083eae0) > 1 0x10003bcf (3DSETUP.DLL.TDSETUP_IsSupportedCard+0x1aa4 in > 3DSETUP.DLL) (ebp=4083eb18) > 2 0x1000249d (3DSETUP.DLL.TDSETUP_IsSupportedCard+0x372 in 3DSETUP.DLL) > (ebp=4083ebd4) > 3 0x10001160 (3DSETUP.DLL.TDSETUP_Init+0xcc in 3DSETUP.DLL) (ebp=4083efec) > 4 0x0040179b (3DSetup.exe..text+0x79b in 3DSetup.exe) (ebp=00000001) > > I copied over version.dll from winxp and it did run the 3DSetup but with > no videocards in the list; could be because i didn't install NHL 2002 > the way it should be installed (i installed nhl2003/2004 properly) > > like i stated earlier for NHL 2004, version.dll cannot be used from > WinXP as it gives an error... the only solution would be to fix the > version.dll implementation.. however im not familiar with windows api > and how everything works, so im not sure how i'd approach that problem > myself > > Tom wrote: > >> Abdul-Haseeb Ahmad wrote: >> >>> Jonathan Wilson wrote: >>> >>>> Abdul-Haseeb Ahmad wrote: >>>> >>>>> ive tinkered around some more, and i copied over winxp's >>>>> kernel32.dll, and i >>>> >>>> >>>> >>>> >>>> >>>> You cant use kernel32.dll from real windows on WINE. >>>> >>>> >>>> >>> if i do put it there, the program goes past the kernel32 error, as >>> i've explained.. i changed it to a dummy kernel32 and it worked as well >>> >>> >> >> Have you tried NHL 2003, 2002, 2001, 99 ? >> >> >> >> > > >

Jan. 29, 2004

Re: ListView painting (was Re: Mouse up vs Mouse click)

by Dimitrie O. Paun

On Thu, 29 Jan 2004, Fabian Cenedese wrote: > That was my weak try to explain what I see :) > Ok, again in short what happens: I can click on a cell in the first column, > it gets selected, I can release the mouse button, everything fine. > But when I press on a cell in another column it shortly gets selected > and immediately the selection again disappears, even while still > holding the mouse button. The logical selection seems to be ok > as I can move it to another cell with the cursor keys (and it strangely > stays there unlike if done so with the mouse). OK, so it seems that your app uses the listview in LVS_REPORT mode, and that it wants to make it bahave like a spreadsheet (that is, you want to be able to individually select any cell from the row/column matrix of the listview). Hence the OWNERDRAW, as by default a listview in REPORT more can either select the cell in the first column or the entire row. Now, I haven't used MFC before, so I don't know if this behaviour is done in your app or in MFC code. If it's in your app, it should be simple enough to add some print statements to figure out the paint order and to confirm/ruleout this theory. If it's done in MFC, I'm afraid you'll need to get creative, 'cause I can't help. But the problem seems to be in the order of events (or some missing notifications). Print statements are what you want: they'll help you figure out (1) if you get all required notifications, and (2) if they arrive in the right order. -- Dimi.

Jan. 29, 2004

Re: ListView painting (was Re: Mouse up vs Mouse click)

by Fabian Cenedese

At 08:27 29.01.2004 -0500, Dimitrie O. Paun wrote: >On January 29, 2004 08:08 am, Fabian Cenedese wrote: >> Understandable. Any hints how I could continue? Where to look at? > >I don't think I understand this bit. Care to explain it again? > > "So for me it looks like this: When I click in a cell it gets invalidated > and painted selected. But if the cell is not in the first row the first > column (or the whole line) gets invalidated and repainted too, therefore > erasing the already painted selection." Another idea: When a line changes it is completely invalidated and repainted without any selection. The the new cell is painted again with selection. So what if these two events are in wrong order? My cell gets selected and immediately loses it again. And that's maybe what happens as "it" (main thread?) doesn't wait in the OnLButtonDown as it does for the first column cells. Of course it's not just that simple as I made a test with a simple ownerdrawn listcontrol which of course worked. So it must be more in my app that interferes. Could it be that the listview is inside a ocx? Different event handling? bye Fabi

Jan. 29, 2004

Re: ListView painting (was Re: Mouse up vs Mouse click)

by Fabian Cenedese

At 08:27 29.01.2004 -0500, Dimitrie O. Paun wrote: >On January 29, 2004 08:08 am, Fabian Cenedese wrote: >> Understandable. Any hints how I could continue? Where to look at? > >I don't think I understand this bit. Care to explain it again? > > "So for me it looks like this: When I click in a cell it gets invalidated > and painted selected. But if the cell is not in the first row the first > column (or the whole line) gets invalidated and repainted too, therefore > erasing the already painted selection." That was my weak try to explain what I see :) Ok, again in short what happens: I can click on a cell in the first column, it gets selected, I can release the mouse button, everything fine. But when I press on a cell in another column it shortly gets selected and immediately the selection again disappears, even while still holding the mouse button. The logical selection seems to be ok as I can move it to another cell with the cursor keys (and it strangely stays there unlike if done so with the mouse). So if only the visual display is wrong I was looking for an explanation with the paint events. The cell is set selected and then the whole line invalidated (as it is ownerdrawn). Maybe in Windows only the Invalidate/Update cause the line to be repainted whereas in wine already the SetItem will cause a first Update and then the Invalidate a second one. But then again it should just flicker a bit but not completely disappear... Btw, the hanging in the CListCtrl::OnLButtonDown I mentioned is also in wine for the first column (maybe that's why this works). But for the other columns it just rushes through. bye Fabi

Jan. 29, 2004