I think I'm on the right track to figuring out why I can't get GTA to install. I thought ole was at fault, but now I suspect user32. It seems that the installer pops up various message boxes (or at least, it supposed to...but it doesn't). Then it waits for a reply, and it never receives one, because I don't see any message boxes. That's why it "freezes", imho. One box it's supposed to show is "out-of-space", if I don't have enough hard drive space for the components (which apparently I don't..when the audio is installed). Another one has empty contents at msgbox.OnInit (not sure what that means - is the text set later? - I see ignored event 0006 (setText)). I can't see the boxes in question, but I see calls to msgbox to create them. The WM_SHOWWINDOW event is propagated down to DefWindowProc, where it is blocked.
In "custom install" mode, the out-of-space box shows up, but the second "mystery box" doesn't. In "complete install" mode I see neither box. If I free up enough hard drive space, it still fails, because of this second box that I can't see.
More detail here: http://bugs.winehq.org/show_bug.cgi?id=3108
Well, whats the behavior in desktop mode? Is this in desktop mode or normal mode?
On 10/8/05, Ivan Gyurdiev [email protected] wrote:
I think I'm on the right track to figuring out why I can't get GTA to install. I thought ole was at fault, but now I suspect user32. It seems that the installer pops up various message boxes (or at least, it supposed to...but it doesn't). Then it waits for a reply, and it never receives one, because I don't see any message boxes. That's why it "freezes", imho. One box it's supposed to show is "out-of-space", if I don't have enough hard drive space for the components (which apparently I don't..when the audio is installed). Another one has empty contents at msgbox.OnInit (not sure what that means - is the text set later? - I see ignored event 0006 (setText)). I can't see the boxes in question, but I see calls to msgbox to create them. The WM_SHOWWINDOW event is propagated down to DefWindowProc, where it is blocked.
In "custom install" mode, the out-of-space box shows up, but the second "mystery box" doesn't. In "complete install" mode I see neither box. If I free up enough hard drive space, it still fails, because of this second box that I can't see.
More detail here: http://bugs.winehq.org/show_bug.cgi?id=3108
Vijay Kiran Kamuju wrote:
Well, whats the behavior in desktop mode? Is this in desktop mode or normal mode? It's normal mode... Yes! I see both boxes in desktop mode (now that I've tried this). The second one contains nothing (???) (set text event being ignored maybe - I see not all of the events are relayed down to Window?). It says: "Question" with no text. I chose YES twice, and then I get another installer screen with a text field - "Current Settings", which is completely empty. Then I click Next, and it begins install! I don't have enough space to let the install proceed right now, but this is great - hopefully it can be made to work.
well some times, things that ont work in normal mode, do work in desktop mode ;) There is an old bug, the dialog boxes getiing behind the main window
On 10/8/05, Ivan Gyurdiev [email protected] wrote:
Vijay Kiran Kamuju wrote:
Well, whats the behavior in desktop mode? Is this in desktop mode or normal mode? It's normal mode... Yes! I see both boxes in desktop mode (now that I've tried this). The second one contains nothing (???) (set text event being ignored maybe - I see not all of the events are relayed down to Window?). It says: "Question" with no text. I chose YES twice, and then I get another installer screen with a text field - "Current Settings", which is completely empty. Then I click Next, and it begins install! I don't have enough space to let the install proceed right now, but this is great - hopefully it can be made to work.
On Sat, 08 Oct 2005 08:47:09 +0200, Vijay Kiran Kamuju [email protected] wrote:
well some times, things that ont work in normal mode, do work in desktop mode
There is an old bug, the dialog boxes getiing behind the main window
I get similar behaviour on an InstallShield based installer.
It appears that there is a bug in showmodal dialog boxes not coming to the top of the z-order. They are typically left behind a window of the same app within wine.
They are generally still accessible via the keyboard (Esc, Enter, etc.) if you can guess the correct responce, or sometimes Alt-Tab can bring them up. None of which actually fixes anything but it can help as a work-around.
This bug is very old , I can recall this going back at least a year, it seems odd that such an important bug has not been adressed.
;)
[email protected] wrote:
On Sat, 08 Oct 2005 08:47:09 +0200, Vijay Kiran Kamuju [email protected] wrote:
well some times, things that ont work in normal mode, do work in desktop mode
There is an old bug, the dialog boxes getiing behind the main window
I get similar behaviour on an InstallShield based installer.
Maybe you can add comments to the bugzilla, or open a new one, describing the issue better: http://bugs.winehq.org/show_bug.cgi?id=3108
It appears that there is a bug in showmodal dialog boxes not coming to the top of the z-order. They are typically left behind a window of the same app within wine.
They are generally still accessible via the keyboard (Esc, Enter, etc.) if you can guess the correct responce, or sometimes Alt-Tab can bring them up. None of which actually fixes anything but it can help as a work-around.
This bug is very old , I can recall this going back at least a year, it seems odd that such an important bug has not been adressed.
-
Ivan Gyurdiev -
Vijay Kiran Kamuju -
wino＠piments.com