Lionel Ulmer wrote:
I would say sponsoring Wineconf 2005 would be a better idea (so we could go
somewhere exotic (not that St Paul in winter was not exotic in a kinda
perverted way for most of us :-) )).
I have volunteered to organize it in Cyprus. I've already started
lobbying for that locatio
In the same yard sale where I bought Lotus SmartSuite '96
(whose Lotus 1-2-3 works under wine-20040615), I also
bought the '97 version. I had numerous problems with
the '97 version. Its installer failed while installing
Word Pro (though it seemed to install Lotus 1-2-3). Lotus 1-2-3
fails with n
> Why is that?
Adam Schreiber may know as slackware he build 2 binaries for slack users using
xfree86 and x.org, you can reach him at shipssadam -at - clemson.edu
Ivan.
> Why is that?
I have no idea, but X11drv doesn't initialize properly. This has been reported
by users, I don't have x.org myself.
Ivan.
> Maybe, but for example Mandrake users won't get wine listed in the "remove
> software" utility, and that will be confusing
> Solving that problem is a desktop issue, I've done a bit of work on it but
nothing has got into mainstream yet.
OK, but in the mean time I still don't see how one binary c
Does anyone knows why we have not in registry
Software\\Wine\\Wine\\Config\\Wine\IconsDir entry?
winemenubuilder can't extract any icons without this dir.
--
Lav
Vitaly Lipatov
Russia, Saint-Petersburg
GNU! ALT Linux Team! LaTeX! LyX!
On June 19, 2004 03:24 pm, Mike Hearn wrote:
> On Sat, 19 Jun 2004 15:01:31 -0400, Geoff Thorpe wrote:
> > Excellent, I'm glad this was said. One only has to look at the swing
> > away from binary-distributions as a case in point - people *want* to
> > eliminate unknown layers of patches, packaging
Dan Kegel <[EMAIL PROTECTED]> writes:
> OK, if wineinstall is no longer needed, how does one
> get drive letters set up? The doc on winehq seems to
> still tell people to edit the config file. If one does
> that, wine will then create the symlinks, but there's
> no doc on how to do it yourself..
I went to a yard sale today, and that's always dangerous.
Today I ended up buying a copy of Lotus SmartSuite '96.
I then installed Wine-20040615.tar.gz and tried installing my new disc with
$ wine d:\\install.exe
It got all confused, started iterating through every file underneath my
home directo
On Sun, 20 Jun 2004 00:35:06 +0200, Ivan wrote:
> About building one binary of wine for all distros, it's interesting to notice
> that one the same distro you need different binaries depending on if you're
> using xfree86 or x.org.
Why is that?
On Sun, 2004-06-20 at 01:02 +0200, Ivan wrote:
> And why shouldn't we have the wine programs in the menu?
We should but that's not a packaging problem, that's a matter of waiting
for XDG menus to become prevalent then teaching wineshelllink how to use
libxslt and apply transforms to the menu defin
> Anyway, Wine doesn't have any menu
> integration.
And why shouldn't we have the wine programs in the menu?
> Compiling it as i586 or i686 should be fine, very few people use
> processors old enough to barf on it
Sure.
> That's what apbuild solves. It lets you compile for glibc 2.2 on a 2.3
> sy
> The trouble with this idea is that the few times
> I've tried to offer software to Lionel and others
> they tell me that they have all they need.
Well, it's mostly that this is a bit of a slippery slope to start sending
stuff to some people and not others. And then, this would mak
On Sun, 2004-06-20 at 00:12 +0200, Ivan wrote:
> This isn't easy to do, and it means you have to A) Leave out some features (mime
> types, menus, that most distros handle in a different way) or B) package
> menu/mime stuff for all distros, meaning the user downloads a big binary but
> will only nee
About building one binary of wine for all distros, it's interesting to notice
that one the same distro you need different binaries depending on if you're
using xfree86 or x.org.
Ivan.
> (a) and (b) can be solved by WineHQ providing its own distro-neutral, run
> anywhere binary packages.
This isn't easy to do, and it means you have to A) Leave out some features (mime
types, menus, that most distros handle in a different way) or B) package
menu/mime stuff for all distros, meaning
Hi all,
I'm trying to create a winelib DLL project from scratch. You can
reproduce using the following steps:
create a file called "name.c", put the following content in it:
int func( int a )
{
return a+1;
}
Create a file called "name.spec". Put the following content in it:
@ cdecl func( long
OK, if wineinstall is no longer needed, how does one
get drive letters set up? The doc on winehq seems to
still tell people to edit the config file. If one does
that, wine will then create the symlinks, but there's
no doc on how to do it yourself...
--
My technical stuff: http://kegel.com
My poli
On Sat, 19 Jun 2004 13:16:56 -0600, Leonardo Quijano Vincenzi wrote:
> I can't help but notice that there's no Yum repository for Wine. Or at
> least I haven't found it yet ;).
http://newrpms.sunsite.dk/ has one with Wine in.
thanks -mike
On Sat, 19 Jun 2004 15:01:31 -0400, Geoff Thorpe wrote:
> Excellent, I'm glad this was said. One only has to look at the swing away
> from binary-distributions as a case in point - people *want* to eliminate
> unknown layers of patches, packaging, and divergence from the "real"
> thing.
The on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I can't help but notice that there's no Yum repository for Wine. Or at
least I haven't found it yet ;).
So, would it be too hard to setup one?
In case anyone needs instructions, there is a tutorial here:
http://fedoranews.org/alex/tutorial/yum/
Leon
On Friday 18 June 2004 11:10, Nicolai Kuntze wrote:
> Hi,
>
> I have here an application (bmed) but I can't see any scrollbars. Is
> there something I can do?
>
try [EMAIL PROTECTED]
--
Hatky,
Worshiper of wine (http://www.winehq.org/),
Impossible is only an opinion.
On June 19, 2004 01:37 pm, Alexandre Julliard wrote:
> > way towards cutting the number of non-developers building from source
> > down to zero.
>
> I don't see why that should be a goal at all. You guys need to get rid
> of the mindset that building from source is some 1337 thing that mere
> morta
Mike Hearn <[EMAIL PROTECTED]> writes:
> Is there a reason that can't be dlopened too? relaytool makes it much less
> hassle to write dlopened code.
libicu can't be dlopened thanks to their idiotic versioning scheme.
>> f) They want to try a patch that someone sent them.
>
> How often does that
On Sat, Jun 19, 2004 at 10:37:54AM -0700, Alexandre Julliard wrote:
> users build without having to fight the autoconf tools. It's for the
> same reason that we have wineinstall. Of course I'm all for improving
> the binary packages, but it doesn't avoid the need to also support
> source builds.
S
On Sat, 19 Jun 2004 10:37:54 -0700, Alexandre Julliard wrote:
> d) They need something that isn't part of the standard packages (for
>instance BiDi support).
Is there a reason that can't be dlopened too? relaytool makes it much less
hassle to write dlopened code.
> e) They want to report a c
Hello Filip,
Monday, June 14, 2004, 12:26:18 AM, you wrote:
FN> Now with the correct patch...
Thanks Filip, it works fine here. Any chance that it will be committed
to CVS?
--
Best regards,
Philmailto:[EMAIL PROTECTED]
Mike Hearn <[EMAIL PROTECTED]> writes:
> a) There is no binary package for their distribution. How common is this?
> I don't know but I've encountered a startling number of newbies that use
> off-the-wall distros like Ark/College Linux etc.
>
> b) There is but it's out of date or broken. This is w
--- Eric Pouech <[EMAIL PROTECTED]> wrote:
> Damjan Jovanovic a écrit :
> > Hi
> >
> > Basically, I have a Windows user-space device
> driver,
> > and I need to get it working under Linux.
> >
> > I note Wine has some "device" functions
> > (FILE_CreateDevice(), and DOSFS_OpenDevice()). How
> do
Jeremy White wrote:
The trouble with this idea is that the few times
I've tried to offer software to Lionel and others
they tell me that they have all they need.
Didn't Lionel say in his interview that a new GPU videocard would have
helped him get into newer areas?
* Sponsor Winecon
On Sat, 2004-06-19 at 09:54 -0400, Dimitrie O. Paun wrote:
> I don't think we're doing too badly with the current packages -- over
> 85% of people go for them. Having a distro-neutral binary packages
> would be good, and it may shave off another 5% or so of the people
> who do go for source downloa
On Sat, 19 Jun 2004 14:42:27 +0100
James Courtier-Dutton <[EMAIL PROTECTED]> wrote:
> The Windows api method uses the function call IDvdInfo2::GetDiscID
> http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/directx9_c/directx/htm/idvdinfo2getdiscid.asp
>
> This returns a unique 64bit
> (a) and (b) can be solved by WineHQ providing its own distro-neutral, run
> anywhere binary packages. This isn't hard as Wine is generally excellent
> at running on different peoples machines from the same binaries - after
> all, CodeWeavers need it. I think a nice installer for correctly built
>
The Windows api method uses the function call IDvdInfo2::GetDiscID
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/directx9_c/directx/htm/idvdinfo2getdiscid.asp
This returns a unique 64bit ID for a DVD.
Has anyone found out what exactly it does to create this 64bit ID.
It would be
On Fri, 18 Jun 2004 17:05:49 -0700, Alexandre Julliard wrote:
> Maybe Linux users in general know how to run configure (though I doubt
> that), but that's definitely not true for Wine users IMO; most of them
> come straight from Windows, and Wine is often the first time ever they
> build something
On Mon, Jun 14, 2004 at 04:30:28PM -0700, Alexandre Julliard wrote:
> It may be that when the module handle is NULL Win95 falls back to a
> thread-local hook, or does some other strange magic; NT refuses to set
> a system-wide hook with a NULL module, so I'd expect your app to fail
> on NT (except
36 matches
Mail list logo
