Hi All,
I've completed the merge of the work Aric and I have done to date on
MSI. Some programs that use and do not package the MSI installer may
start to work. We still have no implementation of msiexec.exe, so there
is still no method to install .msi files directly, however not all MSI
base
On Fri, 2004-07-09 at 21:18, Duane Clark wrote:
> Mike Hearn wrote:
> > ...
> > So you need to figure out why {402b4180-fa0c-40ee-ebf8-ee40f0ce5360} isn't
> > being registered, which may involve figuring out what it actually is :)
>
> Okay, I'll see if I can make some sense out of that.
>
> >
>
Le sam 10/07/2004 à 11:37, Vincent Béron a écrit :
> Changelog:
> Create a WINEGRAPHICSDRIVER env var to override either the config value
> or the default value (in user and gdi).
Please disregard, there's a problem with the patch (changed the default
value in gdi to ttydrv).
I'll send an updated
On Sat, 19 Jun 2004, Saulius Krasuckas wrote:
> With thepatch [1] I am getting some this line from Wine:
>
> err:wave:OSS_RawOpenDevice ioctl(/dev/dsp, SNDCTL_DSP_SETDUPLEX) failed
> (Input/output error)
>
> Yes, my soundcard doesn't support full duplex, I believe (I have OPTi
> 82c931 chip with
Le sam 10/07/2004 à 08:54, Mike Hearn a écrit :
> On Sat, 10 Jul 2004 09:55:20 +0300, Shachar Shemesh wrote:
> > That's ugly. I cannot touch a file that doesn't belong to me.
>
> Just submit a patch that lets you override the video driver in use via an
> environment variable.
I'll do it.
Vincent
On Sat, Jul 10, 2004 at 01:54:30PM +0100, Mike Hearn wrote:
> On Sat, 10 Jul 2004 09:55:20 +0300, Shachar Shemesh wrote:
> > That's ugly. I cannot touch a file that doesn't belong to me.
>
> Just submit a patch that lets you override the video driver in use via an
> environment variable.
Can't we
On Sat, 10 Jul 2004 09:55:20 +0300, Shachar Shemesh wrote:
> That's ugly. I cannot touch a file that doesn't belong to me.
Just submit a patch that lets you override the video driver in use via an
environment variable.
thanks -mike
Hi,
On Fri, Jul 09, 2004 at 04:14:31PM -0400, Andrei Barbu wrote:
> Point is.. it works, it's compliant letter for letter with the MSDN
> docs, and it doesn't break anything.
That's EXACTLY the problem - if it's compliant to MSDN letter for letter, then
you can bet your whole household that it is
Vincent Béron wrote:
Running wineprefixcreate manually should fix your problem.
Try this:
mkdir ~/.wine
sed -e "s/\\\"x11drv\\\"/\\\"ttydrv\\\"/g" /etc/wine/wine.conf
That's ugly. I cannot touch a file that doesn't belong to me.
~/.wine/config
wineprefixcreate
You should then have a populat
