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

Re: Installing MS Office gives error in installer

by mdew

On Thu, 2002-04-18 at 11:39, Hetz Ben Hamo wrote: > As for others who tries to install Office 2000 with Wine CVS - nice try, but > you'll need to do tons of tricks in order to install it. running: wine > setup.exe won't do the trick. If you want to run Office 2000, then please > don't behave cheaply - go pay the $50 to Codeweavers for their excellent > product - they give all their modifications back and your money supports them > in order to continue developing Wine.. cheaply? Im sure this is an OOS Project, are we all leaches upon the linux community?...I feel a little cheap since I downloaded a couple of Debain ISO's without paying for them. We use Wine to test out Windows Apps in Wine...so its no great surprise Office 2000 has become an issue. > This is the same issue for Transgaming's WineX - want to run full game? then > subscribe and support them please.. > > And if you want to flame me - my email is right here - fire away. Scenerio: What *If* I (or someone else) had a few sane bug fixes, that allowed Office 2000 to work? What would happen?, "Umm sorry we cant commit this....because we feel you're too cheap to buy Codeweavers great product!" Fixing Issues such as getting Office 2000 to work should be in the same catagory as fixing support for any other App using wine. And it *shouldnt* be delyed just because it "Office 2000". Im Getting the feeling the codeweavers is failing to commit any code that would promote any *decent* workable progress of Office 2000 using Wine CVS. Those are my thoughts anyway.. -mdew -- ph33r! Linux mdew 2.4.18-xfs #1 Sun Mar 31 15:53:58 NZST 2002 i686 unknown

April 18, 2002

Re: Urgent need for advice: POLLHUP and sockets

by Martin Wilck

Ove, can you comment on this line in sock_reselect: /* previously unconnected socket, is this reselect supposed to connect it? */ if (!(sock->state & ~FD_WINE_NONBLOCKING)) return 0; Was this a short way of expressing if ( !(sock->state & (FD_READ|FD_WRITE|FD_OOB|FD_ACCEPT|FD_CONNECT|FD_CLOSE| FD_WINE_LISTENING|FD_WINE_CONNECTED|FD_WINE_RAW) )) ?? Rationale: I have been adding new flags (FD_WINE_SEND_SHUTDOWN, FD_WINE_RECV_SHUTDOWN) and my guess is they (being internal) should be treated like FD_WINE_NONBLOCKING here, but I'm uncertain. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

April 18, 2002

Re: PATCH: accept-deferred.diff (5 in series)

by Martin Wilck

On 17 Apr 2002, Alexandre Julliard wrote: > Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> writes: > > > PATCH: accept-deferred.diff > > > > If a connection request is deferred in a call to WSAAccept(), > > a subsequent accept()/WSAAccept() call must return the > > previously deferred connection rather than a new one. OK - I keep overlooking issues like that :( Thanks for spotting it. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

April 18, 2002

Duplication of definition of /.wine

by Vincent Béron

I was looking for the place in the source where the ~/.wine directory was defined, and it turns out it's defined twice: once in scheduler/client.c, the other one in server/request.c. There's also some duplicated code: the function get_config_dir is defined in both of these files, and none is static. And both implementation are identical. Is it normal? Do they go in the same executable or in different ones (which ones)? I thought we would rather try to avoid duplication of code, no? Vincent

April 18, 2002

Re: Duplication of definition of /.wine

by Marcus Meissner

On Thu, Apr 18, 2002 at 02:07:25AM -0400, Vincent Béron wrote: > I was looking for the place in the source where the ~/.wine directory > was defined, and it turns out it's defined twice: once in > scheduler/client.c, the other one in server/request.c. > There's also some duplicated code: the function get_config_dir is > defined in both of these files, and none is static. And both > implementation are identical. Is it normal? Do they go in the same > executable or in different ones (which ones)? I thought we would rather > try to avoid duplication of code, no? They go into different binaries, one into the wineserver, one into the wine executable. Ciao, Marcus

April 18, 2002

toolbar.c problem (ATTN: Duane)

by Dusan Vujosevic

Hi, I am having a problem with the way toolbar.c was modified between revisions 1.107 & 1.108. My application (Signlab) pops flyout toolbars that stay around until they lose focus. The parent toolbar receives a 'TBN_DROPDOWN' message when someone clicks on one of its flyout buttons (button style: TBSTYLE_DROPDOWN). It creates a flyout at that point. With revision 1.108 of toolbar.c in Wine the parent toolbar also receives an WN_COMMAND after TBN_DROPDOWN message which causes Wine (rightly so) to send an WM_SETFOCUS (and WM_ACTIVATE). That causes the parent to regain focus and kills the flyout. The line that sends the WN_COMMAND is in toolbar.c at line 4540 (TOOLBAR_LButtonUp() function): SendMessageA (infoPtr->hwndNotify, WM_COMMAND, MAKEWPARAM(infoPtr->buttons[nHit].idCommand, 0), (LPARAM)hwnd); In revision 1.107 it used to be: if (bSendMessage) SendMessageA (infoPtr->hwndNotify, WM_COMMAND, MAKEWPARAM(btnPtr->idCommand, 0), (LPARAM)hwnd); And that worked fine because it would never send WM_COMMAND for a flyout button. Note that WinXP (that's where I tested) doesn't send WM_COMMAND after TBN_DROPDOWN has been handled. I would like to suggest revert that line back to 1.106 because it is the correct way. If other apps are were having problems with 1.106 (Duane was mentioning Acrobat Reader - I will test that..) I suggest that the problem might be elsewhere. Should I supply a patch? Cheers, Dusan

April 18, 2002

Re: IOCTL_SCSI_GET_ADDRESS implementation

by Rizsanyi Zsolt

forgot to attach the files :(

April 18, 2002

Re: Installing MS Office gives error in installer

by Hetz Ben Hamo

Hi, I suggest that if you have problems with CrossOver Office - that you should report them (with a full output text) to the CodeWeavers support site - thats why they have their ticket system which works pretty well - http://support.codeweavers.com/ (after all - if you bought a product - you deserve full support).. As for others who tries to install Office 2000 with Wine CVS - nice try, but you'll need to do tons of tricks in order to install it. running: wine setup.exe won't do the trick. If you want to run Office 2000, then please don't behave cheaply - go pay the $50 to Codeweavers for their excellent product - they give all their modifications back and your money supports them in order to continue developing Wine.. This is the same issue for Transgaming's WineX - want to run full game? then subscribe and support them please.. And if you want to flame me - my email is right here - fire away. Hetz On Thursday 18 April 2002 01:46 am, Rizsanyi Zsolt wrote: > On Wednesday 17 April 2002 21:42, Speeddymon wrote: > > I just recently installed wine-20020411 (as you may > > have noticed from my patch) > > I haven't tried installing Office 2000 on previous > > versions, but heard that it worked, so I decided to > > try it. First I tried it in Crossover Office (since i > > just recently got that also) and the Office 2000 > > installer complained that it couldnt find a package to > > install on the installation media. So I tried it in > > wine and it did the same thing... There were no debug > > messages or anything (in the console). > > > > If anyone knows of a way around this, please let me > > know... If it has been mentioned before please point > > me to the right wine-devel archive so I can find it...

April 17, 2002

IOCTL_SCSI_GET_ADDRESS implementation

by Rizsanyi Zsolt

Hi! I have implemented IOCTL_SCSI_GET_ADDRESS for non scsi cdroms. On NT this ioctl is called on non scsi cdroms, and it should return a valid value. NT treats the two ide controllers as scsi (at least for this ioctl). The program which uses this ioctl, when the ioctl returns with success it tries to read further data from the registry, from the Machine\\HARDWARE\\DEVICEMAP\\Scsi I have looked at the registry of my w2k and I'm trying to set up according to it the registry of wine. But I have some implementation questions: - I'm setting up the registry in the CDROM_Open (in dlls/ntdll/cdrom.c). This is right, because before that no ioctl could be called, but maybe I should setup it when the devices are initialized (then of course only for the cdroms where the Device is specified in configuration), to ensure initialization only once, and not at every CDROM_Open - I'm having problems with the refreshing of the registry. If I delete the previously entered registry entries from system.reg, and run the (windows) regedit, then at start I dont have the Scsi registry key. But if I select ImportRegistry then the FileOpenDialog opens the cdrom, and from the debug messages I know that the data were entered to the registry, but regedit does not show it even if I press F5 (or select the Refresh menu) Why is this? I know that there are VOLATILE registry keys, but dont know if they apply here, and to how to use them... - I'm using some includes like linux/hdreg.h linux/major.h and sys/stat.h (fstat function) - where and how to add checks for them? Is it enough if I add those headers to the list in configure.ac? - and of course I want comments about anything - This is my first serious patch to wine The cdrom.diff is my patch, and the ntddscsi.h is a header file created by Laurent Pinchart who is working on IOCTL_SCSI_PASS_THROUGH_DIRECT, but has not sent his patch to the list yet... Thanks in advance for your help Zsolt Rizsanyi

April 17, 2002

Re: Installing MS Office gives error in installer

by Rizsanyi Zsolt

On Wednesday 17 April 2002 21:42, Speeddymon wrote: > I just recently installed wine-20020411 (as you may > have noticed from my patch) > I haven't tried installing Office 2000 on previous > versions, but heard that it worked, so I decided to > try it. First I tried it in Crossover Office (since i > just recently got that also) and the Office 2000 > installer complained that it couldnt find a package to > install on the installation media. So I tried it in > wine and it did the same thing... There were no debug > messages or anything (in the console). > > If anyone knows of a way around this, please let me > know... If it has been mentioned before please point > me to the right wine-devel archive so I can find it... I have also dared to try to install office2k, and had the same problem. But I have found a workaround... When the installation fails, the MSI installer is already copied to your windows directory (I think its name is installmsi.exe or something like that - I dont have it at hand). So I have tried to invoke it with the msi file in the root of the CD (the data1.msi or something like that - the other msi is something else). This way the installation started. The configuration of what programs to install worked perfectly, but when copying the files the installer broke, and said that it can't write a file. I dont know what was the problem. I had enough space, the persmissions were ok, and so on. I have tried again, and the installer broke again but now with a different file. So I give up, since I don't really need it to install, just I wanted to see what the people are talking about... But if you find a solution (or submit a patch :), then I will be interested... Best regards, Zsolt Rizsanyi

April 17, 2002