Re: Questions about using native vs implementing our own

2007-04-12 Thread Tom Spear
Well the patch definitely works, so if it hasn't been submitted, please do so. There are still crashes in random spots, but that is documented on Paul's wiki page. Tom On 4/11/07, Tom Spear <[EMAIL PROTECTED]> wrote: I just tried the patch is it fails, but I copied and pasted the code into the

Re: Questions about using native vs implementing our own

2007-04-11 Thread Tom Spear
I just tried the patch is it fails, but I copied and pasted the code into the correct files and am recompiling wine now. We will see just how far we can get with the stubs.. Tom P.S. did this get submitted to wine-patches today as well? On 4/11/07, Eric Pouech <[EMAIL PROTECTED]> wrote: Tom S

re: Questions about using native vs implementing our own

2007-04-11 Thread Dan Kegel
Alexander Sørnes wrote: > No, if native dlls are required then it's very helpful for users to know > which ones, and it's even better if you provide download links to these > dlls, by using sites such as www.dll-files.com or www.dll-downloads.com, > or uploading your own somewhere. Helpful and b

Re: Questions about using native vs implementing our own

2007-04-11 Thread Detlef Riekenberg
On Mi, 2007-04-11 at 10:18 -0500, Tom Spear wrote: > Is there a fully stubbed dll in the current tree that I could use as a > reference to start a stub for acledit? I'd like to at least see how > far I can get with a stubbed dll, Eric send already a sub, but ... Is something missing here? http

Re: Questions about using native vs implementing our own

2007-04-11 Thread Stefan Dösinger
Am Mittwoch 11 April 2007 20:26 schrieb Tom Spear: > Legal? From Microsoft's standpoint, no, but as long as you have a > valid windows license, then I dont see why there should be any > problem. Thus the reason I didn't actually provide any links. > Besides, a quick google search for the dll brin

Re: Questions about using native vs implementing our own

2007-04-11 Thread Alexander Nicolaysen Sørnes
Onsdag 11 april 2007 20:09, skrev du : > > No, if native dlls are required then it's very helpful for users to know > > which ones, and it's even better if you provide download links to these > > dlls, by using sites such as www.dll-files.com or www.dll-downloads.com, > > or uploading your own some

Re: Questions about using native vs implementing our own

2007-04-11 Thread Tom Spear
Legal? From Microsoft's standpoint, no, but as long as you have a valid windows license, then I dont see why there should be any problem. Thus the reason I didn't actually provide any links. Besides, a quick google search for the dll brings up the dll-files site for the dll.. Tom On 4/11/07, S

Re: Questions about using native vs implementing our own

2007-04-11 Thread Stefan Dösinger
> No, if native dlls are required then it's very helpful for users to know > which ones, and it's even better if you provide download links to these > dlls, by using sites such as www.dll-files.com or www.dll-downloads.com, or > uploading your own somewhere. Helpful and better yes, but legal? pgp

Re: Questions about using native vs implementing our own

2007-04-11 Thread Eric Pouech
Tom Spear a écrit : Hi again all, before I go and file another needless bug, I thought I would ask for opinions. I decided to try to run Process Explorer today with wine. When I first ran it, I got a dialog about missing a function. So I looked back thru the traces and it was because we were m

Re: Questions about using native vs implementing our own

2007-04-11 Thread Paul Vriens
Tom Spear wrote: GAR! I just checked Paul's site after sending the last email. He already has a stubbed version of acledit. Paul, do you mind sending me what you have? I'd like to take a look, but cant guarantee I can get anything done, but still, I'd at least like to try. Tom Hi Tom, I d

Re: Questions about using native vs implementing our own

2007-04-11 Thread Alexander Nicolaysen Sørnes
Onsdag 11 april 2007 16:48, skrev Tom Spear: > Hi again all, before I go and file another needless bug, I thought I > would ask for opinions. > > I decided to try to run Process Explorer today with wine. When I > first ran it, I got a dialog about missing a function. So I looked > back thru the t

Re: Questions about using native vs implementing our own

2007-04-11 Thread Tom Spear
GAR! I just checked Paul's site after sending the last email. He already has a stubbed version of acledit. Paul, do you mind sending me what you have? I'd like to take a look, but cant guarantee I can get anything done, but still, I'd at least like to try. Tom On 4/11/07, Tom Spear <[EMAIL P

Re: Questions about using native vs implementing our own

2007-04-11 Thread Tom Spear
On 4/11/07, Robert Shearman <[EMAIL PROTECTED]> wrote: They are only required because they are imported by acledit.dll, as is also samlib.dll. You might want to do a little debugging next time to see what modules are importing the DLLs. The only DLL that is required directly and that needs to be

Re: Questions about using native vs implementing our own

2007-04-11 Thread Robert Shearman
Tom Spear wrote: I decided to try to run Process Explorer today with wine. When I first ran it, I got a dialog about missing a function. So I looked back thru the traces and it was because we were missing acledit.dll.. So I imported that from my windows xp install, and got the dialog again. Tu

Re: Questions about using native vs implementing our own

2007-04-11 Thread Paul Vriens
Tom Spear wrote: Hi again all, before I go and file another needless bug, I thought I would ask for opinions. I decided to try to run Process Explorer today with wine. When I first ran it, I got a dialog about missing a function. So I looked back thru the traces and it was because we were miss

Questions about using native vs implementing our own

2007-04-11 Thread Tom Spear
Hi again all, before I go and file another needless bug, I thought I would ask for opinions. I decided to try to run Process Explorer today with wine. When I first ran it, I got a dialog about missing a function. So I looked back thru the traces and it was because we were missing acledit.dll..