- Wine-Devel - list.winehq.org

I: Wine and SQl server.
by Carlo Pelini April 24, 2003

April 24, 2003

> -----Messaggio originale----- > Da: Carlo Pelini > Inviato: giovedì 24 aprile 2003 17.42 > A: 'wine-users(a)Winehq.com' > Oggetto: Wine and SQl server. > > Hy. I am a computer science student, and I am studing wine for my degree > thesis. > I have succeded to run VisualFoxPro on wine and by VisualFoxPro i have > succeded to utilize the unixODBC and the ODBC windows. With the unixODBC I > have succeded to open a connession with a database SQL server, to execute > a interrogation and to visualize the result. > For to can to do there, I dont'have utilized directly the driver SQL > server, but I have utilzed easysoft ODBC-ODBC bridge > (http://www.easysoft.com/products/oob/main.phtml) a ODBCF driver, which > do precisely from bridge between the ODBC client and the ODBC server, and > allow the connession with a database SQL server. > Thank at there proceeding, I have succeded to run AD HOC REVOLUTION, a > managerial software, even if is slow. > Bye.

1 0

Server Crash
by Jeremy Newman April 24, 2003

April 24, 2003

It's time for the annual server crash kids! Whee! Our server melted last night at about 3am or so after 2 days of solid high traffic (the load average was up over 100). I managed to get it up and running with some WD-40, Duct Tape, and some bubble gum. I can't guarantee uptime right now. I AM, however, scrambling to beef it up to handle the load. I apologize in advance for any further downtime. As you can imagine, with all this good press, I don't want the server do be down any longer than a few nanoseconds. If anyone has a quad processor Xeon they are not using, feel free to send it my way. :-D -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

1 0

Wintab32 dll devlopment
by Robert North April 23, 2003

April 23, 2003

I have just posted a status update on my wintab32 development to the following wine bug. http://bugs.winehq.com/show_bug.cgi?id=1160 And following on from that update there are a number of questions I need answered to guide my further development: 1. Cross over office and tablets. I heard somewhere that Crossover office had a tablet implementation. Does anyone know about this, and who to contact to find out more? If they've got an implementation of wintab, I wonder if it's worth continuing the development. 2. When to post patches I could start producing patches quite soon. For instance, I could post patches when the WTInfo function is working. Or, I could wait till the whole system is working fully with at least one app? 3. Size of the patches. Is it better to break patches into small (valid compile, but non-functioning) chunks, or to release large functioning patches? 4. Config files Wintab will need some config data. I assume the best place to put this is in the ~/.wine/config file, within a registry key named "wintab"? 5. Development notes. I have some notes on the design that other developers will probably find useful. Where in the wine project should they go? There seems to be no place for rough notes. 6. x11drv integration. Currently the code is implemented to connect to X11 in a similar way to directX. No additional code is placed in the x11drv dll. This X11 connection should be discarded. To this end I have a number of functions that I'd like to place in x11drv dll. The question is: Should I put them into x11drv before releasing any patches, or maintain the directX style connection in the initial wine patches? 7. Cross-platform abilities Is there any need to think about allowing alternatives to XInput to plug into the wintab dll? Yeah, I know that's a lot of questions, But I hope you guys can give me some guidance. Bye -Rob.

4 4

WineHQ's CVS server performance..
by Lionel Ulmer April 23, 2003

April 23, 2003

Hi all, Am I the only to find the current CVS performance abyssmal ? About 5 minutes for a CVS update and 10 for a CVS diff is not what I usually have on my connection... Let's hope it's Alexandre merging all the Crossover Office 2.0 patches <g>. Lionel -- Lionel Ulmer - http://www.bbrox.org/

3 2

CVS Character set (was: lostwages/templates/en documentation.template)
by Joerg Mayer April 23, 2003

April 23, 2003

I'm noticing that during the last few weeks several mails have been sent to the cvs list that use 8-bit characters but do not specifiy an encoding in the mail header. Would it be possible to either add one (depends on whether cvs does recognize the encoding type) or remove those extra characters? On Tue, Apr 22, 2003 at 01:28:01PM -0500, Jeremy Newman wrote: > Log message: > ChangeLog > Â Â Â Dimitrie O. Paun <dpaun(a)rogers.com> > Â Â Â Remove references to no longer existing document. > > Patch: http://cvs.winehq.com/patch.py?id=7945 Thanks Jörg -- Joerg Mayer <jmayer(a)loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.

1 0

RE: FoxPro & Wine :)
by Patrik Stridvall April 23, 2003

April 23, 2003

> On Wed, 23 Apr 2003, Patrik Stridvall wrote: > > > While, I suppose, you can have a license the regulates this to, even > > if the LGPL doesn't, the problem is the doctrine of first sale means > > anybody that it can be distributed to can resell (or give) that copy > > to anybody that can't be distributed directly to. > > And that is in no contradiction with the (L)GPL, as it does not > restrict to whom we can redistribute, but rather under what > conditions a derived work can be distributed. But that is exactly what I said above. Should I interpret it as you agree? But please note that the last step meantioned above is not distribution, it is sale (or gift) on an invidual copy allowed by first sale. And as I said earlier, it makes the conditions for redistribution is rather meaningless, since anybody regardless or willingless or abillity to follow the redistribution conditional can indirectly for all intent and purposed have distributed to anybody your work, while seperately distributing anything that uses, modififies, adapts etc your work for his purposes on the end users computer. The situation for the Microsoft Visual FoxPro (MVFP) runtime is almost identical since you analagous to above can for all intent and purpose have it distributed seperately. Summary: Microsoft released the MVFP runtime for all intent an purpose for free since they thought that charging for it would be bad for their purposes. Some people release some work under the LGPL because they thought charging for it would be bad for their purposes... Nobody can both have the cake and eat it. Microsoft can't, I can't, you can't... And futher more, again, Copyright law is designed that way on purpose, not by accident.

1 0

odd message
by Robert Lunnon April 23, 2003

April 23, 2003

I am debugging a shareware game my kids often play called little fighter 2 (It deadlocks after creating the third thread) But before I get to the deadloack I noticed I get the following two messages from wine, err:module:BUILTIN_LoadModule loaded .so but dll wineaudioio.drv still not found err:module:BUILTIN_LoadModule loaded .so but dll joystick.drv still not found from what I can see wine is loading the two shared libraries ok and __wine_dll_register gets properly called EG Breakpoint 2, __wine_dll_register (header=0xdcb82480, filename=0xdcb721f6 "wineaudioio.drv") at loader.c:327 Yet find_dll_descr( dllname ) in builtin.c fails to find the name ?? Any hints would be appreciated

1 1

Re: oleaut32 patch
by Alexandre Julliard April 23, 2003

April 23, 2003

Ove Kaaven <ovek(a)arcticnet.no> writes: > The oaidl_p.c is almost unmodified MIDL output generated from Wine's > oaidl.idl (I only had to add an #undef __WINE__ at the top to get all > the Winelib definitions, perhaps this isn't needed under Wine anymore), > so it shouldn't be hard to maintain, and Alexandre once said MIDL output > is acceptable as a stopgap solution. I don't know if proper > InstallShield repaint support calls for stopgaps, though. One problem is that this code causes hundreds of warnings, and I don't think that's acceptable (it also fails to link but that could be fixed by adding a few stubs). We could fix the warnings manually but that will cause obvious maintenance problems. How far are we from being able to generate that with widl? -- Alexandre Julliard julliard(a)winehq.com

3 3

Re: Winelib CoolPlayer port
by Dimitrie O. Paun April 23, 2003

April 23, 2003

On April 22, 2003 04:17 pm, Vincent Béron wrote: > Next is the actual Winelib stuff, which is very small. Just a few lines indeed! > The first part is an MFC header (thankfully, nothing else seems to be > needed from MFC). This is the: --- CoolPlayerCVS-20030421-2130-orig/afxres.h 1969-12-31 19:00:00.000000000 -0500 +++ CoolPlayerCVS-20030421-2130/afxres.h 2003-04-21 21:51:07.000000000 -0400 @@ -0,0 +1 @@ +#include "winres.h" right? > The second part is the only problematic thing. The current div > implementation works fine for binary compatibility on i386, but doesn't > work well for source level compatibility on the same platform. I would prefer if we fix this one in Wine, so we don't have to submit this part for inclusion in the CoolPlayer code. This would be _our_ benefit for the port, no? :) -- Dimi.

1 0

Re: Fix trackbar size
by Dimitrie O. Paun April 23, 2003

April 23, 2003

On April 22, 2003 05:55 pm, Maxime Bellengé wrote: > + * Copyright 2003 Maxime Belleng�<maxime.bellenge(a)laposte.net> > * > * This library is free software; you can redistribute it and/or > * modify it under the terms of the GNU Lesser General Public > @@ -231,13 +232,13 @@ > channel->top = lpRect.top + offsetedge; > channel->bottom = lpRect.bottom - offsetedge; > channel->left = lpRect.left + offsetthumb; > - if (dwStyle & (TBS_BOTH | TBS_LEFT)) channel->left += 8; > + if (dwStyle & (TBS_BOTH | TBS_LEFT)) channel->left += > (lpRect.right-lpRect.left-offsetthumb-cyChannel)/2; Unfortunately, the patch seems to be wrapped, and your name did not show up properly in the copyright notice. -- Dimi.

1 0