wine-devel

wine-devel@winehq.org

84463 discussions

Re: AVI resources in shell32.dll
by Sylvain Petreolle 05 Oct '02

05 Oct '02

--- Stefan Leichter <Stefan.Leichter(a)camLine.com> a écrit : > I did not extract the original. The tool resgrab ( > http://www.Inner-Smile.com/dl_resg.htm#downl) told me the size. > > Using the original is hopefuly a joke!?! No, if it's only for testing purpose. You can extract it using ResHacker, as Greg said. But you didn't answer to my second question : does the size really matter? After all it's only 50k... ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

2 2

Re: [patch] Fix listview scrolling
by Dimitrie O. Paun 05 Oct '02

05 Oct '02

> instead of the very bottom. Lastly, I'm pretty sure there should be > separate nPartialAdjust variables for horz and vert scrolling. You are right, we do need separate nPartialAdjust. My bad. THe other bug was (half of it) in the old code, when I changed it I noticed the inconsistency, is just that I picked the wrong half :). Thanks for the fix. This looks good, it should go in. -- Dimi.

1 0

Need help interpreting debug log for Wine hard loop
by Sean Millichamp 04 Oct '02

04 Oct '02

I hope this isn't too off-topic for the wine-devel list but I asked for debugging help on wine-users a couple of days ago and got no reply so maybe that isn't the right place to ask about debugging help? I bought and use Codeweaver's Crossover product to drive Office and have fiddled with Wine briefly on and off over the years but other then that I am mostly a Wine newbie. I am trying to make an old Windows 3.1 application work and it appears to be causing Wine to go into a hard loop while loading. For what it's worth, this application is called "Travex" and is used in the health care industry. I think it uses the Win 3.1 era Borland GUI toolkit in case it matters. I followed the directions on the website for debugging and have a --debugmsg warn+all +loaddll output that I only can vaguely interpret. Wine enters the hard loop somewhere following the debug log. I tried debug logs at various other levels including a relay log/trace (though I have no idea what it is) and +all and under those levels the same output keeps getting outputted to the log as Wine loops. I am not a Windows developer although I have done a little with C under Linux. Is there anyone who could help me figure out what is going wrong? I'd be happy to make the logs available for http or send them in email. Unfortunately, I can't provide the application itself due to licensing issues (it's a commercial package). I have tested it with Wine from RH 7.3, Wine from 10/01 CVS, and Codeweavers Crossover Office 1.0 (just for kicks). All three exhibit the same behavior. I tried the Wine from 10/01 in both Win98 and Win31 behavior mode. No change. The application runs just fine in Windows 98. I installed it in my fake_windows in Wine and have tried running it from there as well as my real Windows partition. No change. Any help would be greatly appreciated. Thanks in advance. Sean

3 7

Re: Major tidy up of Scroll.c to add foundations for flatscroll bars
by György 'Nog' Jeney 04 Oct '02

04 Oct '02

> I have used this code to implement flat scroll bars in two ways however > I run into problems and I am looking for advice. Hi, I was thinking about implementing flatscrollbars but never got round to implement the Flatscrollbars itself. I thought about doig it like this: Subclass the window with flatscrollbars, with the Subclassing functions that I have implemented recently. Implement GetScrollBarInfo and use it to get all of the scrollbar properties like thump position and size, arrow sizes etc. Store an internal list of the System metricies (just like native) and then draw the control. All of the functions that pertain to flat scroll bars will just call their user counterparts and the same goes for messages. nog.

3 2

VB errors (treeview, debugger)
by Fabian Cenedese 04 Oct '02

04 Oct '02

Hi again Problem 1: I have found something strange in a VB app. If I run it with "wine vberror" it works quite ok. But if I call it with "winedbg vberror" it freaks out on pressing the button. Maybe it's a timing problem that an exception couldn't be caught as wine could do it being faster. Problem 2: Quite simple to test: If I click in the treeview it disappears :) Both problems can be tested with this little sample proggy: http://www.indel.ch/ftp/VBError.zip I had to use the native oleaut32.dll as the builtin worked even worse on the treeview. The rest is out of the (cvs-)box 20021004, SuSE 8.0 Thanks bye Fabi

1 0

Listview K6
by Dimitrie O. Paun 04 Oct '02

04 Oct '02

This one fixes a nasty little bug in OWNERDATA listviews. Xnews should now refresh properly. Selection is still borken, but that's the subject of a different patch. Bug reports are always welcomed. ;) ChangeLog Fix condition so we actually store the state in virtual listviews. Assorted code cleanups. --- dlls/comctl32/listview.c.K5 Fri Oct 4 02:39:12 2002 +++ dlls/comctl32/listview.c Fri Oct 4 11:38:11 2002 @@ -1236,7 +1236,7 @@ LONG lStyle = infoPtr->dwStyle; UINT uView = lStyle & LVS_TYPEMASK; POINT Origin, Position, TopLeft; - RECT Icon, Boundary, Label; + RECT Icon, Boundary, Label, FullText; INT nIndent = 0; if (!LISTVIEW_GetOrigin(infoPtr, &Origin)) return FALSE; @@ -1380,7 +1380,6 @@ if (infoPtr->himlNormal != NULL) { INT nLabelWidth; - RECT FullText; Label.left = TopLeft.x + Origin.x; Label.top = TopLeft.y + Origin.y + ICON_TOP_PADDING_HITABLE + @@ -1404,10 +1403,6 @@ InflateRect(&FullText, 2, 0); if (lprcLabel) *lprcLabel = Label; if (lprcText) *lprcText = FullText; - TRACE("hwnd=%x, item=%d, label=(%d,%d)-(%d,%d), fulltext=(%d,%d)-(%d,%d)\n", - infoPtr->hwndSelf, nItem, - Label.left, Label.top, Label.right, Label.bottom, - FullText.left, FullText.top, FullText.right, FullText.bottom); } else return FALSE; } @@ -1433,9 +1428,6 @@ Label.right = nLeftPos + infoPtr->nItemWidth; if (lprcLabel) *lprcLabel = Label; if (lprcText) *lprcText = Label; - TRACE("hwnd=%x, item=%d, label=(%d,%d)-(%d,%d)\n", - infoPtr->hwndSelf, nItem, - Label.left, Label.top, Label.right, Label.bottom); } else /* LVS_LIST or LVS_REPORT */ { @@ -1461,7 +1453,8 @@ if (lprcText) *lprcText = Label; } - TRACE("hwnd=%x, item=%d, label=%s\n", infoPtr->hwndSelf, nItem, debugrect(&Label)); + TRACE("hwnd=%x, item=%d, label=%s, fulltext=%s\n", + infoPtr->hwndSelf, nItem, debugrect(&Label), debugrect(lprcText)); /***********************************************************/ /* compute boundary box for the item (ala LVM_GETITEMRECT) */ @@ -2296,6 +2289,8 @@ { LVITEMW lvItem; + TRACE("nItem=%d\n", nItem); + LISTVIEW_RemoveAllSelections(infoPtr); lvItem.state = LVIS_FOCUSED | LVIS_SELECTED; @@ -2485,14 +2480,16 @@ NMLISTVIEW nmlv; INT oldState; - /* a virtual livst view stores only state for the main item */ + /* a virtual listview stores only the state for the main item */ if (lpLVItem->iSubItem || !(lpLVItem->mask & LVIF_STATE)) return FALSE; oldState = LISTVIEW_GetItemState(infoPtr, lpLVItem->iItem, LVIS_FOCUSED | LVIS_SELECTED); + TRACE("oldState=%x, newState=%x, uCallbackMask=%x\n", + oldState, lpLVItem->state, infoPtr->uCallbackMask); /* we're done if we don't need to change anything we handle */ - if ( (oldState ^ lpLVItem->state) & lpLVItem->stateMask & - ~infoPtr->uCallbackMask & (LVIS_FOCUSED | LVIS_SELECTED)) return FALSE; + if ( !((oldState ^ lpLVItem->state) & lpLVItem->stateMask & + ~infoPtr->uCallbackMask & (LVIS_FOCUSED | LVIS_SELECTED))) return TRUE; /* * As per MSDN LVN_ITEMCHANGING notifications are _NOT_ sent for @@ -2517,7 +2514,7 @@ add_selection_range(infoPtr, lpLVItem->iItem, lpLVItem->iItem, TRUE); } else - remove_selection_range(infoPtr, lpLVItem->iItem, lpLVItem->iItem, TRUE); + remove_selection_range(infoPtr, lpLVItem->iItem, lpLVItem->iItem, TRUE); } /* notify the parent now that things have changed */ @@ -3267,7 +3264,7 @@ } /* Get scroll info once before loop */ - LISTVIEW_GetOrigin(infoPtr, &ptOrig); + if (!LISTVIEW_GetOrigin(infoPtr, &ptOrig)) return; /* we now narrow the columns as well */ nLastCol = nColumnCount - 1; @@ -3315,7 +3312,8 @@ item.mask = LVIF_PARAM | LVIF_STATE; item.stateMask = LVIS_SELECTED | LVIS_FOCUSED; if (!LISTVIEW_GetItemW(infoPtr, &item, TRUE)) continue; - + + ZeroMemory(&dis, sizeof(dis)); dis.hwndItem = infoPtr->hwndSelf; dis.hDC = hdc; dis.CtlType = ODT_LISTVIEW; @@ -3323,7 +3321,6 @@ dis.itemID = nItem; dis.itemAction = ODA_DRAWENTIRE; dis.itemData = item.lParam; - dis.itemState = 0; if (item.state & LVIS_SELECTED) dis.itemState |= ODS_SELECTED; if (item.state & LVIS_FOCUSED) dis.itemState |= ODS_FOCUS; dis.rcItem.left = lpCols[0].rc.left; @@ -3333,7 +3330,7 @@ OffsetRect(&dis.rcItem, ptOrig.x, 0); TRACE("item=%s, rcItem=%s\n", debuglvitem_t(&item, TRUE), debugrect(&dis.rcItem)); - if (SendMessageW(GetParent(infoPtr->hwndSelf), WM_DRAWITEM, uID, (LPARAM)&dis)) + if (SendMessageW(GetParent(infoPtr->hwndSelf), WM_DRAWITEM, dis.CtlID, (LPARAM)&dis)) continue; } @@ -3481,7 +3478,7 @@ if(GETITEMCOUNT(infoPtr) == 0) return; - LISTVIEW_GetOrigin(infoPtr, &ptOrigin); + if (!LISTVIEW_GetOrigin(infoPtr, &ptOrigin)) return; GetClipBox(hdc, &rcClip); @@ -4746,7 +4743,7 @@ } /* we store only a little state, so if we're not asked, we're done */ - if (!(lpLVItem->mask & LVIF_STATE) || lpLVItem->iSubItem) return FALSE; + if (!(lpLVItem->mask & LVIF_STATE) || lpLVItem->iSubItem) return TRUE; /* if focus is handled by us, report it */ if ( !(infoPtr->uCallbackMask & LVIS_FOCUSED) ) @@ -6790,28 +6787,26 @@ */ static LRESULT LISTVIEW_SetItemState(LISTVIEW_INFO *infoPtr, INT nItem, LPLVITEMW lpLVItem) { - BOOL bResult = TRUE; - LVITEMW lvItem; - - TRACE("(nItem=%d, state=%x, stateMask=%x)\n", nItem, lpLVItem->state, - lpLVItem->stateMask); + BOOL bResult = TRUE; + LVITEMW lvItem; - lvItem.iItem = nItem; - lvItem.iSubItem = 0; - lvItem.mask = LVIF_STATE; - lvItem.state = lpLVItem->state; - lvItem.stateMask = lpLVItem->stateMask; - - if (nItem == -1) - { - /* apply to all items */ - for (lvItem.iItem = 0; lvItem.iItem < GETITEMCOUNT(infoPtr); lvItem.iItem++) - if (!LISTVIEW_SetItemT(infoPtr, &lvItem, TRUE)) bResult = FALSE; - } - else - bResult = LISTVIEW_SetItemT(infoPtr, &lvItem, TRUE); + lvItem.iItem = nItem; + lvItem.iSubItem = 0; + lvItem.mask = LVIF_STATE; + lvItem.state = lpLVItem->state; + lvItem.stateMask = lpLVItem->stateMask; + TRACE("lvItem=%s\n", debuglvitem_t(&lvItem, TRUE)); + + if (nItem == -1) + { + /* apply to all items */ + for (lvItem.iItem = 0; lvItem.iItem < GETITEMCOUNT(infoPtr); lvItem.iItem++) + if (!LISTVIEW_SetItemT(infoPtr, &lvItem, TRUE)) bResult = FALSE; + } + else + bResult = LISTVIEW_SetItemT(infoPtr, &lvItem, TRUE); - return bResult; + return bResult; } /***

1 0

Window flags problem
by Fabian Cenedese 04 Oct '02

04 Oct '02

Hi I have a problem with my VC6 MFC MDI app. Every child window that is docked inside isn't painted anymore and doesn't receive any messages. Together with a friend (THX ic) I found out that the wrapper window that does the docking doesn't have the visible flag set. Even if I create the window with the flag set it gets deleted somewhere in CreateWindowEx or ShowWindow. In Windows the flag can even get set even if it wasn't set before but I just couldn't find out why. I scrutinized the MoveWindow call. It sends the messages WM_WINDOWPOSCHANGING, WM_NCCALCSIZE, WM_WINDOWPOSCHANGED, WM_MOVE and WM_SIZE (in this order) to the window. After these there is an additional WM_SHOWWINDOW. In every handler the visible flag isn't changed yet. After leaving the MoveWindow call the flag can be set or deleted. So this must happen between WM_SHOWWINDOW and the end of MoveWindow. But I couldn't find out what reason Windows uses to change it so I can't say where in wine the error is. I'd be very thankful if somebody with knowledge about windows and their style flags could shed some light upon this. Here is a small sample app (only exe, source is quite complicated, but I can deliver that too if anybody is interested). There is a toolbar docked below the menu but in wine there is just a dead area. http://www.indel.ch/ftp/TestIMD.zip BTW winedbg doesn't show the class information for walk wnd. The same problem has MS-Spy++ but besides that it runs quite well in wine :) Thanks for any hint/help/patch... bye Fabi

1 0

Regression Test - kernel atom test
by Steven Edwards 04 Oct '02

04 Oct '02

Here is another one on my win2k sp3 box. All tests compiled with cygwin atom.c:81: Test failed: succeeded adding ff74 atom.c:84: Test failed: succeeded adding ff74 atom.c:81: Test failed: succeeded adding ff75 atom.c:84: Test failed: succeeded adding ff75 atom.c:81: Test failed: succeeded adding ff76 atom.c:84: Test failed: succeeded adding ff76 atom.c:81: Test failed: succeeded adding ff77 atom.c:84: Test failed: succeeded adding ff77 atom.c:81: Test failed: succeeded adding ff78 atom.c:84: Test failed: succeeded adding ff78 atom.c:81: Test failed: succeeded adding ff79 atom.c:84: Test failed: succeeded adding ff79 atom.c:81: Test failed: succeeded adding ff7a atom.c:84: Test failed: succeeded adding ff7a atom.c:81: Test failed: succeeded adding ff7b atom.c:84: Test failed: succeeded adding ff7b atom.c:81: Test failed: succeeded adding ff7c atom.c:84: Test failed: succeeded adding ff7c atom.c:81: Test failed: succeeded adding ff7d atom.c:84: Test failed: succeeded adding ff7d atom.c:81: Test failed: succeeded adding ff7e atom.c:84: Test failed: succeeded adding ff7e atom.c:81: Test failed: succeeded adding ff7f atom.c:84: Test failed: succeeded adding ff7f atom.c:81: Test failed: succeeded adding ff80 atom.c:84: Test failed: succeeded adding ff80 atom.c:81: Test failed: succeeded adding ff81 atom.c:84: Test failed: succeeded adding ff81 atom.c:81: Test failed: succeeded adding ff82 atom.c:84: Test failed: succeeded adding ff82 atom.c:81: Test failed: succeeded adding ff83 atom.c:84: Test failed: succeeded adding ff83 atom.c:81: Test failed: succeeded adding ff84 atom.c:84: Test failed: succeeded adding ff84 atom.c:81: Test failed: succeeded adding ff85 atom.c:84: Test failed: succeeded adding ff85 atom.c:81: Test failed: succeeded adding ff86 atom.c:84: Test failed: succeeded adding ff86 atom.c:81: Test failed: succeeded adding ff87 atom.c:84: Test failed: succeeded adding ff87 atom.c:81: Test failed: succeeded adding ff88 atom.c:84: Test failed: succeeded adding ff88 atom.c:81: Test failed: succeeded adding ff89 atom.c:84: Test failed: succeeded adding ff89 atom.c:81: Test failed: succeeded adding ff8a atom.c:84: Test failed: succeeded adding ff8a atom.c:81: Test failed: succeeded adding ff8b atom.c:84: Test failed: succeeded adding ff8b atom.c:81: Test failed: succeeded adding ff8c atom.c:84: Test failed: succeeded adding ff8c atom.c:81: Test failed: succeeded adding ff8d atom.c:84: Test failed: succeeded adding ff8d atom.c:81: Test failed: succeeded adding ff8e atom.c:84: Test failed: succeeded adding ff8e atom.c:81: Test failed: succeeded adding ff8f atom.c:84: Test failed: succeeded adding ff8f atom.c:81: Test failed: succeeded adding ff90 atom.c:84: Test failed: succeeded adding ff90 atom.c:81: Test failed: succeeded adding ff91 atom.c:84: Test failed: succeeded adding ff91 atom.c:81: Test failed: succeeded adding ff92 atom.c:84: Test failed: succeeded adding ff92 atom.c:81: Test failed: succeeded adding ff93 atom.c:84: Test failed: succeeded adding ff93 atom.c:81: Test failed: succeeded adding ff94 atom.c:84: Test failed: succeeded adding ff94 atom.c:81: Test failed: succeeded adding ff95 atom.c:84: Test failed: succeeded adding ff95 atom.c:81: Test failed: succeeded adding ff96 atom.c:84: Test failed: succeeded adding ff96 atom.c:81: Test failed: succeeded adding ff97 atom.c:84: Test failed: succeeded adding ff97 atom.c:81: Test failed: succeeded adding ff98 atom.c:84: Test failed: succeeded adding ff98 atom.c:81: Test failed: succeeded adding ff99 atom.c:84: Test failed: succeeded adding ff99 atom.c:81: Test failed: succeeded adding ff9a atom.c:84: Test failed: succeeded adding ff9a atom.c:81: Test failed: succeeded adding ff9b atom.c:84: Test failed: succeeded adding ff9b atom.c:81: Test failed: succeeded adding ff9c atom.c:84: Test failed: succeeded adding ff9c atom.c:81: Test failed: succeeded adding ff9d atom.c:84: Test failed: succeeded adding ff9d atom.c:81: Test failed: succeeded adding ff9e atom.c:84: Test failed: succeeded adding ff9e atom.c:81: Test failed: succeeded adding ff9f atom.c:84: Test failed: succeeded adding ff9f atom.c:81: Test failed: succeeded adding ffa0 atom.c:84: Test failed: succeeded adding ffa0 atom.c:81: Test failed: succeeded adding ffa1 atom.c:84: Test failed: succeeded adding ffa1 atom.c:81: Test failed: succeeded adding ffa2 atom.c:84: Test failed: succeeded adding ffa2 atom.c:81: Test failed: succeeded adding ffa3 atom.c:84: Test failed: succeeded adding ffa3 atom.c:81: Test failed: succeeded adding ffa4 atom.c:84: Test failed: succeeded adding ffa4 atom.c:81: Test failed: succeeded adding ffa5 atom.c:84: Test failed: succeeded adding ffa5 atom.c:81: Test failed: succeeded adding ffa6 atom.c:84: Test failed: succeeded adding ffa6 atom.c:81: Test failed: succeeded adding ffa7 atom.c:84: Test failed: succeeded adding ffa7 atom.c:81: Test failed: succeeded adding ffa8 atom.c:84: Test failed: succeeded adding ffa8 atom.c:81: Test failed: succeeded adding ffa9 atom.c:84: Test failed: succeeded adding ffa9 atom.c:81: Test failed: succeeded adding ffaa atom.c:84: Test failed: succeeded adding ffaa atom.c:81: Test failed: succeeded adding ffab atom.c:84: Test failed: succeeded adding ffab atom.c:81: Test failed: succeeded adding ffac atom.c:84: Test failed: succeeded adding ffac atom.c:81: Test failed: succeeded adding ffad atom.c:84: Test failed: succeeded adding ffad atom.c:81: Test failed: succeeded adding ffae atom.c:84: Test failed: succeeded adding ffae atom.c:81: Test failed: succeeded adding ffaf atom.c:84: Test failed: succeeded adding ffaf atom.c:81: Test failed: succeeded adding ffb0 atom.c:84: Test failed: succeeded adding ffb0 atom.c:81: Test failed: succeeded adding ffb1 atom.c:84: Test failed: succeeded adding ffb1 atom.c:81: Test failed: succeeded adding ffb2 atom.c:84: Test failed: succeeded adding ffb2 atom.c:81: Test failed: succeeded adding ffb3 atom.c:84: Test failed: succeeded adding ffb3 atom.c:81: Test failed: succeeded adding ffb4 atom.c:84: Test failed: succeeded adding ffb4 atom.c:81: Test failed: succeeded adding ffb5 atom.c:84: Test failed: succeeded adding ffb5 atom.c:81: Test failed: succeeded adding ffb6 atom.c:84: Test failed: succeeded adding ffb6 atom.c:81: Test failed: succeeded adding ffb7 atom.c:84: Test failed: succeeded adding ffb7 atom.c:81: Test failed: succeeded adding ffb8 atom.c:84: Test failed: succeeded adding ffb8 atom.c:81: Test failed: succeeded adding ffb9 atom.c:84: Test failed: succeeded adding ffb9 atom.c:81: Test failed: succeeded adding ffba atom.c:84: Test failed: succeeded adding ffba atom.c:81: Test failed: succeeded adding ffbb atom.c:84: Test failed: succeeded adding ffbb atom.c:81: Test failed: succeeded adding ffbc atom.c:84: Test failed: succeeded adding ffbc atom.c:81: Test failed: succeeded adding ffbd atom.c:84: Test failed: succeeded adding ffbd atom.c:81: Test failed: succeeded adding ffbe atom.c:84: Test failed: succeeded adding ffbe atom.c:81: Test failed: succeeded adding ffbf atom.c:84: Test failed: succeeded adding ffbf atom.c:81: Test failed: succeeded adding ffc0 atom.c:84: Test failed: succeeded adding ffc0 atom.c:81: Test failed: succeeded adding ffc1 atom.c:84: Test failed: succeeded adding ffc1 atom.c:81: Test failed: succeeded adding ffc2 atom.c:84: Test failed: succeeded adding ffc2 atom.c:81: Test failed: succeeded adding ffc3 atom.c:84: Test failed: succeeded adding ffc3 atom.c:81: Test failed: succeeded adding ffc4 atom.c:84: Test failed: succeeded adding ffc4 atom.c:81: Test failed: succeeded adding ffc5 atom.c:84: Test failed: succeeded adding ffc5 atom.c:81: Test failed: succeeded adding ffc6 atom.c:84: Test failed: succeeded adding ffc6 atom.c:81: Test failed: succeeded adding ffc7 atom.c:84: Test failed: succeeded adding ffc7 atom.c:81: Test failed: succeeded adding ffc8 atom.c:84: Test failed: succeeded adding ffc8 atom.c:81: Test failed: succeeded adding ffc9 atom.c:84: Test failed: succeeded adding ffc9 atom.c:81: Test failed: succeeded adding ffca atom.c:84: Test failed: succeeded adding ffca atom.c:81: Test failed: succeeded adding ffcb atom.c:84: Test failed: succeeded adding ffcb atom.c:81: Test failed: succeeded adding ffcc atom.c:84: Test failed: succeeded adding ffcc atom.c:81: Test failed: succeeded adding ffcd atom.c:84: Test failed: succeeded adding ffcd atom.c:81: Test failed: succeeded adding ffce atom.c:84: Test failed: succeeded adding ffce atom.c:81: Test failed: succeeded adding ffcf atom.c:84: Test failed: succeeded adding ffcf atom.c:81: Test failed: succeeded adding ffd0 atom.c:84: Test failed: succeeded adding ffd0 atom.c:81: Test failed: succeeded adding ffd1 atom.c:84: Test failed: succeeded adding ffd1 atom.c:81: Test failed: succeeded adding ffd2 atom.c:84: Test failed: succeeded adding ffd2 atom.c:81: Test failed: succeeded adding ffd3 atom.c:84: Test failed: succeeded adding ffd3 atom.c:81: Test failed: succeeded adding ffd4 atom.c:84: Test failed: succeeded adding ffd4 atom.c:81: Test failed: succeeded adding ffd5 atom.c:84: Test failed: succeeded adding ffd5 atom.c:81: Test failed: succeeded adding ffd6 atom.c:84: Test failed: succeeded adding ffd6 atom.c:81: Test failed: succeeded adding ffd7 atom.c:84: Test failed: succeeded adding ffd7 atom.c:81: Test failed: succeeded adding ffd8 atom.c:84: Test failed: succeeded adding ffd8 atom.c:81: Test failed: succeeded adding ffd9 atom.c:84: Test failed: succeeded adding ffd9 atom.c:81: Test failed: succeeded adding ffda atom.c:84: Test failed: succeeded adding ffda atom.c:81: Test failed: succeeded adding ffdb atom.c:84: Test failed: succeeded adding ffdb atom.c:81: Test failed: succeeded adding ffdc atom.c:84: Test failed: succeeded adding ffdc atom.c:81: Test failed: succeeded adding ffdd atom.c:84: Test failed: succeeded adding ffdd atom.c:81: Test failed: succeeded adding ffde atom.c:84: Test failed: succeeded adding ffde atom.c:81: Test failed: succeeded adding ffdf atom.c:84: Test failed: succeeded adding ffdf atom.c:81: Test failed: succeeded adding ffe0 atom.c:84: Test failed: succeeded adding ffe0 atom.c:81: Test failed: succeeded adding ffe1 atom.c:84: Test failed: succeeded adding ffe1 atom.c:81: Test failed: succeeded adding ffe2 atom.c:84: Test failed: succeeded adding ffe2 atom.c:81: Test failed: succeeded adding ffe3 atom.c:84: Test failed: succeeded adding ffe3 atom.c:81: Test failed: succeeded adding ffe4 atom.c:84: Test failed: succeeded adding ffe4 atom.c:81: Test failed: succeeded adding ffe5 atom.c:84: Test failed: succeeded adding ffe5 atom.c:81: Test failed: succeeded adding ffe6 atom.c:84: Test failed: succeeded adding ffe6 atom.c:81: Test failed: succeeded adding ffe7 atom.c:84: Test failed: succeeded adding ffe7 atom.c:81: Test failed: succeeded adding ffe8 atom.c:84: Test failed: succeeded adding ffe8 atom.c:81: Test failed: succeeded adding ffe9 atom.c:84: Test failed: succeeded adding ffe9 atom.c:81: Test failed: succeeded adding ffea atom.c:84: Test failed: succeeded adding ffea atom.c:81: Test failed: succeeded adding ffeb atom.c:84: Test failed: succeeded adding ffeb atom.c:81: Test failed: succeeded adding ffec atom.c:84: Test failed: succeeded adding ffec atom.c:81: Test failed: succeeded adding ffed atom.c:84: Test failed: succeeded adding ffed atom.c:81: Test failed: succeeded adding ffee atom.c:84: Test failed: succeeded adding ffee atom.c:81: Test failed: succeeded adding ffef atom.c:84: Test failed: succeeded adding ffef atom.c:81: Test failed: succeeded adding fff0 atom.c:84: Test failed: succeeded adding fff0 atom.c:81: Test failed: succeeded adding fff1 atom.c:84: Test failed: succeeded adding fff1 atom.c:81: Test failed: succeeded adding fff2 atom.c:84: Test failed: succeeded adding fff2 atom.c:81: Test failed: succeeded adding fff3 atom.c:84: Test failed: succeeded adding fff3 atom.c:81: Test failed: succeeded adding fff4 atom.c:84: Test failed: succeeded adding fff4 atom.c:81: Test failed: succeeded adding fff5 atom.c:84: Test failed: succeeded adding fff5 atom.c:81: Test failed: succeeded adding fff6 atom.c:84: Test failed: succeeded adding fff6 atom.c:81: Test failed: succeeded adding fff7 atom.c:84: Test failed: succeeded adding fff7 atom.c:81: Test failed: succeeded adding fff8 atom.c:84: Test failed: succeeded adding fff8 atom.c:81: Test failed: succeeded adding fff9 atom.c:84: Test failed: succeeded adding fff9 atom.c:81: Test failed: succeeded adding fffa atom.c:84: Test failed: succeeded adding fffa atom.c:81: Test failed: succeeded adding fffb atom.c:84: Test failed: succeeded adding fffb atom.c:81: Test failed: succeeded adding fffc atom.c:84: Test failed: succeeded adding fffc atom.c:81: Test failed: succeeded adding fffd atom.c:84: Test failed: succeeded adding fffd atom.c:81: Test failed: succeeded adding fffe atom.c:84: Test failed: succeeded adding fffe atom.c:81: Test failed: succeeded adding ffff atom.c:84: Test failed: succeeded adding ffff atom.c:110: Test failed: bad buffer contents atom.c:112: Test failed: GlobalGetAtomNameW succeeded on short buffer atom.c:116: Test failed: succeded atom.c:118: Test failed: succeded atom.c:120: Test failed: succeded atom.c:122: Test failed: succeded atom.c:140: Test failed: bad length 0 atom.c:143: Test failed: bad buffer contents aaaaaaaaaaha?xA

4 13

AVI resources in shell32.dll
by Stefan Leichter 03 Oct '02

03 Oct '02

Hello, i have an installer that fails because of a missing AVI resource (the magnifier in front of the computer) in the buildin shell32.dll. To get the installer running i tried to build the resource. i used Paintshop Pro 6 to create the single pictures of the AVI and built the AVI with the animation builder of Paintshop Pro. The created AVI work (at least in the Media Player), but my new AVI is 53k big instead of the 7k of the native shell32.dll. Reducing the color deep of the single picturs does not have any effect to the size of the AVI. What do i need to change to get the resource as small as the native on? Are other tools needed to build the resource? Using compression ? Is there a tool to analyse the native resource in deep ? Any ideas? Thanks Stefan

3 4

Re: Need help interpreting debug log for Wine hard loop
by Miguel Feitosa 03 Oct '02

03 Oct '02

On Thu, 2002-10-03 at 18:35, Sean Millichamp wrote: > On Thu, 2002-10-03 at 17:03, Miguel Feitosa wrote: > > I forgot to ask. > > What are the DLLs that your app links? > > It seems that your code is failing before mine. > > Mine actually got to start drawing a window...and yours hasnt. > > I was able to track done my erros to Borlands BWCC or something > > like that .DLL > > Well... I'm not sure how to see what DLL the app links but I suspect it > does need BWCC. I looked and it was installed in C:\Windows\System on > my fake_windows area. I use +file and +dll [I think] I've never done +loaddll Do a simple grep in the wine src and you can see the channels that exist. > > When I do a --debugmsg +loaddll I don't see any mention of bwcc.dll or > any non-builtin DLL. Is there a way I can force-load bwcc? Is there > some reason Wine wouldn't be loading it automatically? No, wine loades DLLs very well. I have never had any problems with that. > > Here are the DLLs that it's installer installed in Windows\System: > bwcc.dll dewcc.dll dewsc.dll dewtc.dll winsys.dll The only one I know is bwcc.dll > > I presume it needs all of them at some point but I see none of them in > use with loaddll before the loop. Do I need to configure this special > in .wine/config? I thought that it was supposed to know to auto-load > them but.... No need to put them in config, they will be loaded, your app is failing before bwcc get's loaded... > > I'm sorry if these are simple questions. I really appreciate you taking > the time to try to help me. If I don't get this working I will have to > install Windows where the application is needed (currently it's all > Linux) and I want to avoid that if possible. No problem, I had to sort through all this too a couple months ago. At the time I was trying to do this, I seach alot and didnt find a whole lot about wine + Borland C... I finally gave it up... I believe that expert wine programmers with the relay can pinpoint the issue that is bugging your app...8-) > > Thanks, > Sean > > See ya! Miguel

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