wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

default config file creation
by Chris Morgan 17 Dec '03

17 Dec '03

I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the things that he was doing for the rpm package. One of the patches he applies to wine prior to packaging it is a patch that creates local user config files if they don't exist. This helps end users as they don't have to worry about the package maintainer providing valid config files. I thought this sounded like a pretty neat idea to improve usability. The patch currently copies files from /etc/* which means they would need to be installed there during the process. I was wondering if it would make more sense during the compile process to take the default configuration files, config, system.reg, user.reg and userdef.reg and convert these to binary form and compile them into the wine binary itself. We could detect the lack of these files at startup and install them for the user. Another feature could be a command line switch that would rebuild a users config, like: 'wine --rebuild-config' that would reset the users config back to the defaults. Sound like something reasonable? Should we instead be putting the default files somewhere on the users machine and copying them over like the patch does? Chris

2 3

Re: default config file creation
by Ivan Leo Murray-Smith 17 Dec '03

17 Dec '03

> Trading off configurability with usability seems fine to > me. We aren't as one can tweak things with winecfg if he wants/needs to > The goal is to solve both > the lack of config files for binary installs, fixed by the > patches that Che has in his rpm package and Marcus has for > Suse, and for users that run 'make install' but never > create config files. All this can be solved by shipping a config file with with wine, get wine to adapt it to the users system, install it, install the registry and create the fake windows partition. This would work for all binaries on all distros, even on freebsd, and would work when installing from source. Only that someone has to implement it. And volunteers?

1 0

Re: default config file creation
by Ivan Leo Murray-Smith 17 Dec '03

17 Dec '03

>The less modification to the install process the better. >If there was a single location the files could be >installed to that would work for all distros I think this >is the route to head in. You can install the files anywhere, as long as the location isn't already used for something else, /etc/wine could do. Also, compiling the files means nobody could change the default config without recompiling wine, that sound short of weird. Ivan.

2 1

Re: default config file creation
by Ivan Leo Murray-Smith 17 Dec '03

17 Dec '03

> Read documentation/PACKAGING, I had it added to CVS with most ideas already > inside on Jun 27, 1999. I've read this. I also had a look at the recording of your speech about wine packaging at wineconf 2002. I've followed the indications of documentation/PACKAGING at lines 385-404, mainly for usability. > Feel free to copy the attached SuSE default make_fakewindows setup script I > use and the included minimalistic wine patch to loader/main.c. It all seems quite SuSE specific, anyway I haven't yet seen a script that works as well as winesetuptk, and there are complaints from time to time about helper scripts shiped with RPMs. Also a script doesn't give a user the freedom of choosing if he wants to use a real or a fake windows partition, and doesn't allow the user to chose where to have the fake windows partition, simply because it can't interact with the user. Nobody seems to be currently shipping winelauncher,and having a scipt to start wine isn't a great idea for a beta/stable build and ideally we want a long term solution. Bill Medland wrote: >I don't like the idea; I much prefer the idea of copying them from somewhere >in /etc, as redhat does. The default config file in /etc can then be >modified so that it matches the distribution (redhat have their cd at >/mnt/cdrom) and it can be modified by the sysadmin There is no need to add text files to the wine binary, but the default config should be modified on the fly. Some computers don't have a cd or a floppy, some have 2 cd drives, some don't use distro-standard paths, so drives should be detected on the fly, already we have enough logs from users full of /mnt/floppy not found and /mnt/cdrom not found, and it's not a great feature for 0.9 or 1.0. Winesetuptk does thit very very very well, I'm no engineer but I suppose that something written in tcltk can be easily ported to C. A binary package (But also a normal make install) should install configb and registry in /etc/wine or /usr/share/doc/wine-version/samples or something like that. The user should then start wine, that would look for $HOME/.wine, create it if necesarry, figure out the removable media paths, create a config file on the fly, write it to $HOME/.wine, run 'wine regedit path/to/winedefault.reg' and start normally.This does not require a script, will create a properly working config file, and the default configuration can be tweaked/restored with winecfg, once it's finished. Ivan.

1 0

Mouse usage when Wine not in focus
by Mark Knecht 17 Dec '03

17 Dec '03

Hi, Please excuse me for bringing this question here. I'm not a developer. I have asked this in a couple of different forums but to date have received no answers. I will copy a message sent earlier this week to Wine-Users and hope for some insights on how to handle it. I have done some Googling around and run across numerous emails about mouse focus, but there doesn't seem to be anything in the Wine-HQ FAQ or Online Docs that tells me how to handle this. The basic issue in a nutshell - How do I configure Wine to not pay attention to the mouse when the Wine window is not in focus? Just in case it matters, I'm using fluxbox on all my systems, but I checked xfce4 and had the same problem. Thanks, Mark <SNIP> Hi, Is there a way to have mouse movements & positions not be sent to a Wine app when the Wine desktop is not the active window? I have looked through the online docs and the FAQ but I see nothing about this problem I'm having. I hope it's just a configuration issue, but I cannot find much info in the docs about mouse configuration at all. Also, I have seen this issue under Crossover Office and WineX, but have not had a chance to check Wine CVS yet, so if it's fixed or a non-issue just let me know. Thanks in advance. Under Windows I have played a game called Caesar 3 for years. Finally with some help from another wine user, I got it working perfectly (as far as I can tell) on Saturday using an ebuild of WineX on a Gentoo 2.4.20 kernel. The game plays well. I do have one problem when the game resolution and the Wine desktop are not the same size, but we can save that for another email if it's of interest to anyone. Anyway, the way the game works is that it has a play area for building your city. To move around this play area you drag your mouse to the edge of the board and the area scrolls inside the window. When playing the game under Wine, using the first config files I had with WineX and cxoffice that had "DXGrab" = "Y", the mouse stayed inside the Wine desktop and the game always worked fine, but I couldn't use the system for anything else unless I tricked Wine into letting my mouse escape from the desktop trap by using another window in the background. I then found the "DXGrab" option and changed it to "N" and I was able to get my mouse out of my Wine desktop and get email, etc. However, even when the Wine desktop and game are not in focus the mouse position is being fed to the game, so the game scrolls around underneath while I use items and applications on my desktop. How can I configure Wine to not send any mouse position information to the game when the game is not in focus? Right now I cannot take a meaningful screenshot since the game area is drifting around all the time. Thanks in advance, Mark <SNIP>

1 0

Re: Wine Status Page Pre-1
by Brian Vincent (C) 17 Dec '03

17 Dec '03

> 3) Send to Brian V for WWN coverage :) (Brian if you want you can get a > early start) Hm. 1.7 meters of snow this week at Steamboat and I have the next three days off. I'm guessing I won't have much done until Monday. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Input Focus problems with IE
by Aric Stewart 17 Dec '03

17 Dec '03

Hello, I am working on a problem with IE where if you start the application in full screen mode: (start IE, change to full screen using view->full screen, shutdown IE, restart IE) the keyboard focus never gets given to the application so you cannot enter any information into forms. Looking into this i found that we where never being given any ClientMessage events to take focus nor any FocusIn events. So the keyboard focus remains on whatever app last had it, such as the terminal used to start IE. A very simple, shotgun, way to solve this is this attached patch. Thinking about windows architecture i was trying to think of a time where a window would receive a button click and would not be given input focus (yes the app may modify focus but it would do that anyway) However this change is HUGE and will affect alot and wanted to bounce it off people before continuing to investigate it. This look ok to people? Other ideas on proper ways to deal with this issue? thanks -aric Index: dlls/x11drv/event.c =================================================================== RCS file: /home/wine/wine/dlls/x11drv/event.c,v retrieving revision 1.30 diff -u -w -r1.30 event.c --- dlls/x11drv/event.c 5 Dec 2003 04:45:50 -0000 1.30 +++ dlls/x11drv/event.c 16 Dec 2003 19:02:57 -0000 @@ -287,6 +287,14 @@ break; case ButtonPress: + /* + * I am sort of unsure about this however + * there should not be a case where the button is clicked somewhere + * and windows does not assume focus is sent there. + * + * it also fixes a bunch of input problems for forms in IE + */ + set_focus(hWnd,CurrentTime); X11DRV_ButtonPress( hWnd, (XButtonEvent*)event ); break;

3 4

Re: default config file creation
by Ivan Leo Murray-Smith 17 Dec '03

17 Dec '03

> If wine-c is stored uncompressed, it's easier for a site admin to modify > it for all its users. True, but this shouldn't be necessary. Also any global configuration should be done via winecfg. > Also, there are a couple places in Wine which are dependant on how the > underlying distribution is setup, things like menu entries and such. Not > every distro ship a vanilla Gnome or KDE (and then there are many > versions of each). Sure, after all I ship mime types files and menu entries for the mandrake menu system in mdk rpms, but I'm reluctant to change the actual application source code, because the same source should work for all (After all that's why we use autoconf), so if any changes are needed, they should go in the CVS, and consequentially end up in all packages Ivan.

1 0

Re: default config file creation
by Ivan Leo Murray-Smith 17 Dec '03

17 Dec '03

>I was chatting with Rudolf Kastl(che on #winehq) and he was mentioning the >things that he was doing for the rpm package. One of the patches he applies >to wine prior to packaging it is a patch that creates local user config files >if they don't exist. His patches modify wine/libs/wine/config.c and wine/misc/registry.c, I don't see the need to change things, they could do if Alexandre accepts them in the CVS. They would uniform wine packaging, and make things easier, also wine-c could be a comprssed dir as it's only usility would be to be copied to $HOME, it doesn't really need to be uncompressed in /usr/share. Of course, all packagers could just apply these patches to binaries, but official packages should just ship vanilla wine (Otherwise why call them "official"?), so this depends on Alexandre. Ivan.

2 1

Re: Fix for Japanese Font Names
by Michael Stefaniuc 17 Dec '03

17 Dec '03

Hi, could you please resubmit your diff using the unified output format? See http://www.winehq.org/site/sending_patches for details. bye michael On Wed, Dec 17, 2003 at 12:00:56PM +0900, Vik wrote: > May last patch had some wrong font names for Japanese resource files. > The correct name for MS UI Gothic is 'Gothic' in English, and not 'Gothic' in > Japanese. > > Changelog > + fixed MS UI Gothic Font names in: > dlls/commdlg/cdlg_Ja.rc > dlls/user/resources/user32_Ja.rc -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

1 0

Re: Always add a \ to temp file path
by Steven Edwards 16 Dec '03

16 Dec '03

There is a prepackaged binary that works great for me on slackware if you want it. Builing one from scratch is to much of a pain in the ass. http://www.libsdl.org/extras/win32/cross/README.txt Thanks Steven --- Mike Hearn <mike(a)theoretic.com> wrote: > The NullSoft installer assumes this will be present, so it most > likely > always is on Windows. When I get a cross compiler setup (soon, > promise!) > I'll try writing a test case for this behaviour. > > Mike Hearn <mike(a)theoretic.com> > Always add a \ to temp file path. Add a warning to DeleteFile. > > Index: files/file.c > =================================================================== > RCS file: /home/wine/wine/files/file.c,v > retrieving revision 1.196 > diff -u -r1.196 file.c > --- files/file.c 12 Dec 2003 04:10:52 -0000 1.196 > +++ files/file.c 16 Dec 2003 19:47:04 -0000 > @@ -921,10 +921,8 @@ > strcpyW( buffer, path ); > p = buffer + strlenW(buffer); > > - /* add a \, if there isn't one and path is more than just the > drive letter ... */ > - if ( !((strlenW(buffer) == 2) && (buffer[1] == ':')) > - && ((p == buffer) || (p[-1] != '\\'))) *p++ = '\\'; > - > + *p++ = '\\'; > + > for (i = 3; (i > 0) && (*prefix); i--) *p++ = *prefix++; > > unique &= 0xffff; > @@ -1556,7 +1554,11 @@ > return FALSE; > } > > - if (!DOSFS_GetFullName( path, TRUE, &full_name )) return FALSE; > + if (!DOSFS_GetFullName( path, TRUE, &full_name )) > + { > + WARN("Unable to get full name from %s\n", debugstr_w(path)); > + return FALSE; > + } > > /* check if we are allowed to delete the source */ > hFile = FILE_CreateFile( full_name.long_name, > GENERIC_READ|GENERIC_WRITE, 0, > > > __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/

1 0

Re: Fix kernel heap test
by Dimitrie O. Paun 16 Dec '03

16 Dec '03

On December 15, 2003 10:35 am, Hans Leidekker wrote: > The test succeeds on Wine. This is wrong of course, tests should > always succeed on Windows and either succeed on Wine or fail on > Wine and be marked todo_wine. Great, thanks for catching this. Our current implementation seems to be freeing memory on size=0, how can we check what Windows does? If it doesn't, we can just simpligy the code to this: Index: dlls/kernel/heap.c =================================================================== RCS file: /var/cvs/wine/dlls/kernel/heap.c,v retrieving revision 1.4 diff -u -r1.4 heap.c --- dlls/kernel/heap.c 27 Nov 2003 00:59:36 -0000 1.4 +++ dlls/kernel/heap.c 15 Dec 2003 16:19:04 -0000 @@ -615,37 +614,15 @@ SetLastError(ERROR_INVALID_HANDLE); } else #endif - if(size!=0) - { - hnew=hmem; - if(pintern->Pointer) - { - if((palloc = HeapReAlloc(GetProcessHeap(), heap_flags, - (char *) pintern->Pointer-HGLOBAL_STORAGE, - size+HGLOBAL_STORAGE)) == NULL) - hnew = 0; /* Block still valid */ - else - pintern->Pointer = (char *)palloc+HGLOBAL_STORAGE; - } - else - { - if((palloc=HeapAlloc(GetProcessHeap(), heap_flags, size+HGLOBAL_STORAGE)) - == NULL) - hnew = 0; - else - { - *(HGLOBAL *)palloc = hmem; - pintern->Pointer = (char *)palloc + HGLOBAL_STORAGE; - } - } - } + if(size == 0) size = 16; + hnew=hmem; + if(pintern->Pointer) palloc = HeapAlloc(GetProcessHeap(), heap_flags, size+HGLOBAL_STORAGE); + else palloc = HeapReAlloc(GetProcessHeap(), heap_flags, (char *) pintern->Pointer-HGLOBAL_STORAGE, size+HGLOBAL_STORAGE); + if (!palloc) hnew = 0; else { - if(pintern->Pointer) - { - HeapFree(GetProcessHeap(), 0, (char *) pintern->Pointer-HGLOBAL_STORAGE); - pintern->Pointer=NULL; - } + pintern->Pointer = (char *)palloc + HGLOBAL_STORAGE; + if (!pintern->Pointer) *(HGLOBAL *)palloc = hmem; } } } -- Dimi.

2 1

Re: Implement support for many MCIWndClass MCI_ and MCIWNDM_ messages
by Dimitrie O. Paun 16 Dec '03

16 Dec '03

On December 15, 2003 03:12 am, Dmitry Timoshkov wrote: > What remains to be done is a proper support for MCI_WINDOW > command in mciavi.drv. Cool stuff Dmitry! Now that this stuff is in the tree, would it be fair to mark this on the status page as 75% complete? What's still left to do? Eric was saying that we needed (before your patch): - missing extended styles, notification, MCIWNDM_* I guess you did the MCIWNDM_* stuff, but the notification is still a TODO. Is the TODO list still too big to be listed in its entirety? -- Dimi.

2 1

Re: Internally maintained end-to-end API documentation
by Brian Vincent (C) 16 Dec '03

16 Dec '03

> After reading Wine Weekly News Issue #200, (Congrats > by the way), I stumbled across the Wine Status Pages. Thanks. > In my humble opinion, this is a very dangerous and > volatile place to have it. It is volatile and there have definitely been instances of people wondering where documentation has disappeared to. > This is quite tragic as my knowledge of XML is really > weak. As far as I know, it's that HTML superset, isn't > it? SGML is the one document format To Rule Them All. XML is a subset of that. HTML is a subset of XML (and therefore SGML). Realistically, Wine could probably use XML for all its documents. But we use SGML since that was around first. We convert the SGML into various nice document formats depending on how it's used. If you know HTML then you won't have much of a problem marking up SGML. > Stepping back a bit, I started thinking of tossing an > SQL database on one of my machines and writing some > kind of dynamic HTML front end for it. I wouldn't. Wine has lots of tools in use for building and searching documentation, not the least of which is "grep". > The second hurtle is what to put as the actual > fields. I'm really only used to seeing function > rendered an a "Unix man style" format. Name, synopsis, > description, return value, errors, bugs. I actually really like this idea. The standard C library is nicely documented in man pages, why shouldn't Win32 be the same way? I don't think we need another document format or repository (Side note, is it just me, or is the GNU texinfo format the stupidest form of documentation ever invented..) The important thing is, keep the documentation in a format that is easily modifiable by developers. Since most have a copy of CVS laying around that probably means keeping docs in a text format somewhere in the documentation/ directory. The scope of this project is huge. In some ways you're trying to recreate MSDN, and as Greg pointed out that documentation lives on real media in the hands of thousands of people. Yes, it might be nice to replicate that but copyright issues are something you'll need to be aware of. If you rewrite all of it by hand you definitely won't infringe on copyrights, but is there an easier way put it together? Something tells me there's already some resources out there that could be used as a foundation. Also, be sure to read the "Terms of Use" link at the bottom of msdn.microsoft.com. It may as well just say "You can only read our web pages." A quick search on Google alludes to people writing man pages for Win32. This was on a NetBSD mailing list: http://mail-index.netbsd.org/netbsd-bugs/2001/05/17/0008.html >Number: 12974 >Category: pkg >Synopsis: w32doc-borland - man pages for the win32 api >Confidential: no >Severity: non-critical >Priority: low >Responsible: pkg-manager >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Thu May 17 13:16:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Ben Collver >Release: 1.5 >Organization: >Environment: >Description: >A set of Unix-like man pages for the Windows 32 API. This package creates >a new manual section (wb) containing man pages derived from a Windows >help file distributed by Borland for Delphi2. Once installed, you could for >example read the WinMain man page by typing "man wb WinMain". >This documentation is not as up-to-date as that in devel/w32doc. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

2 1

Re: TDI + NetBIOS = Network Neighborhood
by Luke Kenneth Casson Leighton 16 Dec '03

16 Dec '03

hi, wrote to the wine-devel mailing list about this one describing a few words about what's needed to be done to "support" your efforts. documentation. rfc1001.txt and rfc1002.txt - these describe NBT (netbios over tcp) and how to get: - datagrams (port 138) equivalent to UDP - sessions (port 139) equivalent to TCP - names (port 137) LISTEN UP! THIS IS EQUIVALENT TO DYNAMIC-DNS + DHCP! the last one of these needs careful explanation. in light of the recent attempts by the wireless IETF crowd to create a dynamic routing protocol is is _totally_ ironic that netbios got there first _by over twenty years_ - and that there is a FREE implementation for the taking, in nmbd. it's also pretty ironic because they've had to play catch-up with concepts like node status queries in additional extension draft rfcs, and they STILL haven't added the "name conflict" concept which is there to tell anyone that will listen that a name which is attempting to be claimed is being taken by someone else who won't give it back. port 137 _is_ actually dns, so if you happen to know of any wine-licensing compatible DNS client code then you can use that as the basis for your efforts. it's dns but it's extended: the names of the types of packets mean slightly different things; there is additional packet types to represent NAME_REGISTER and NAME_STATUS; there is also a different CNAME type to cope with netbios names; the "dns zone" is there it's called a "scope"; the "dns name" is "compressed" it's a brain-dead misnomer given that the name is actually expanded in some sort of stupid base-4 (no, not base-64, yes, that's right, base-4) encoding scheme that turns a 16-byte space-padded thing into an overbloated 64-byte monster. cifsbrow.txt. eek, it's been a while. have a look at www.cb1.com/~lkcl/ntdom. no, try this: http://www.monyo.com/technical/samba/rfc/ actually, first try this: http://ubiqx.org/cifs/References.html which will give you a better idea of what the other one contains: the ftp://ftp.microsoft.com/developr/drg/CIFS directory appears to be inaccessible, now, which is just typical. basically you should read cifsbrow.txt in conjunction with rfc1001.txt and rfc1002.txt. SKIM THEM! YOU ONLY NEED A MINIMAL SUBSET OF THOSE DOCUMENTS FOR A CLIENT IMPLEMENTATION!!!! the only reason that you need to read those docs - skimmed - is because you need to know what you are going to be communicating with (not implementing, server-side, just connecting to, client-side). all you _really_ need is to be able to do a NetBIOS name query and also to be able to do a couple of SMB queries to obtain lists of servers. THAT IS ALL THAT A CLIENT-SIDE NETWORK NEIGHBOURHOOD BROWSER IS. REALLY! if you're implementing this from scratch, however, expect to allocate about ... mmm ... anywhere between four and eight weeks. i _thoroughly_ recommend that you investigate finding some dns client code to adapt and save yourself some time with decoding port 137. also, while you're at it, you might want to next focus on the contents of the ntnp.doc file which was last available with the ms-dev that contained visual studio 4.3. ntnp.doc stands for nt network provider and it had a companion "client-side" document to describe the other bit that went with it. basically there is a "redirector" protocol on both client _and_ server-side that covers browsing. these two protocols "merge" the network neighbourhoods into one big happy family, such that netware's network neighbourhood can be installed and cooperate happily with the smb network neighbourhood can be installed and cooperate happily with the kerberos-domain-based network neighbourhood and it was all one big happy family yippee. so, whilst you may believe that it is best to implement the network neighbourhood browsing functions as "direct" as possible, if you ever install the "client for netware" under wine and then wonder why it doesn't appear in the network neighbourhood, remember what i said in the paragraph above!! l.

1 0

Vacation
by Alexandre Julliard 15 Dec '03

15 Dec '03

Folks, There won't be any commits for a while, since I'm leaving now for a vacation in Switzerland, where I won't have net access. Assuming I survive the deprivation, I'll be back in two weeks. I hope you all have nice holidays, and I look forward to finding a few hundred patches in my mailbox when I get back... -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Fix ntdll test
by Alexandre Julliard 15 Dec '03

15 Dec '03

Hans Leidekker <hans(a)it.vu.nl> writes: > Uncomment some tests in rtlstr.c and wrap them in todo_wine{} instead. You can't do that, many of these tests succeed, which is not allowed inside todo_wine. And please try a 'make test' when you change a test, as already explained there's no point in submitting a patch that causes make test to fail. -- Alexandre Julliard julliard(a)winehq.com

2 1

netapi32 and NetBIOS
by Luke Kenneth Casson Leighton 15 Dec '03

15 Dec '03

[sent also to samba-technical mailing list] hi, i've just been alerted to the netbios work in wine (hooray!) as part of an effort to get the network neighbourhood going (yippee!). there is a problem, which i can help overcome. the problem is this: imagine that there is no TCP/IP stack in linux. imagine that TCP/IP runs in two separate user-space services, both of which are GPL'd: the TCP service is a fork-on-demand one that binds to all interfaces, and the UDP service is even worse, it's a single-process running a state machine. let's pretend that neither of the processes understand anything but Web services, and now you want to add SMTP, or worse, HTTPS. you have to consider hard-coding and linking into a paired monolith of programs, and you have a licensing and logistical nightmare that is totally unacceptable for practical purposes. this is the situation that is faced by wine, because samba, which consists of two programs, smbd and nmbd, "controls" the NetBIOS transport, from both a server _and_ (due to some bugs in Windows) also a client perspective. a flawed attempt to make it possible to cut-in to the NetBIOS equivalent of Dynamic-DNS-plus-DHCP (the NBNS system on port 137) was added in 2000 into nmbd, however from the Wine perspective this is totally useless because the code to access the bypass mechanism is GPL'd (tdb - trivial database). happily there is a convenient way round the mess, because it is possible to create the equivalent of a "Network Address Translation" service, and working code along these lines, which maintained a state machine of NetBIOS connections, was created over three years ago. nmbd needs to talk via this NAT service, so does nmblookup and, once the code is all there, so does Wine's Network Neighbourhood browsing code. at present, all you have to do to get the Wine "Network Neighbourhood" code to work is to disable samba, which is going to be totally impractical for most people. it is not _yet_ necessary for such a service to be created, but by the time the NetBIOS code in wine is released, it will _become_ necessary. if anyone wants to sponsor me [pay money] to revive the experiments i made in late 1999 / early 2000 in order to implement a NetBIOS "NAT" service, please contact me. l. -- -- expecting email to be received and understood is a bit like picking up the telephone and immediately dialing without checking for a dial-tone; speaking immediately without listening for either an answer or ring-tone; hanging up immediately and then expecting someone to call you (and to be able to call you). -- every day, people send out email expecting it to be received without being tampered with, read by other people, delayed or simply - without prejudice but lots of incompetence - destroyed. -- please therefore treat email more like you would a CB radio to communicate across the world (via relaying stations): ask and expect people to confirm receipt; send nothing that you don't mind everyone in the world knowing about...

1 0

uxtheme clips to much
by hatky 15 Dec '03

15 Dec '03

I know these are stubs but since they were added more of the splash screen and the top of the main application of Trillian has been cut off freeware at: http://download.com.com/3000-2150-10047473.html?part=trillian&subj=dlpagtag… home page at: http://www.ceruleanstudios.com/downloads/ Hatky. __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/

2 2

Extended window flag
by Fabian Cenedese 15 Dec '03

15 Dec '03

Hi I have an application where I get the styles from a window with GetWindowLong(m_hWnd, GWL_EXSTYLE); In Windows I get 0x00000110 but in wine I get 0x40000110. From the wine headers (mine seem to old) I get this means 'managed by the system'. Is this something wine specific? Do I need to pay attention to this? If it's a valid Windows flag why isn't it set in Windows? If it's just wine specific can I just mask it out? Thanks bye Fabi

3 6

Re: Running Wine under MS SFU under Wine ... ?
by ea＠iol.it 15 Dec '03

15 Dec '03

> My real point is - SFU is yet another set of windows > programs we can use to test wine, may as well grab a > copy while they're 'free'. SFU3 contains also the POSIX personality for NT/2k. Does Wine run native NT apps yet?

1 0

Wine Segmentation fault
by Fabian Cenedese 15 Dec '03

15 Dec '03

Hi I have a problem with starting wine itself. After trying the CodeWeavers wine I wanted to get clean again and removed everything I could find only slightly wine related (/usr/bin, /usr/local... etc). I even removed my cvs of wine of a few days ago. Then I made a fresh checkout and did the complete install with wineinstall. But still after this whole procedure I cannot start wine. Any ideas? Knoppix (Kernel 2.4.22) fabi@lx_fabi:/usr/local/bin$ gdb wine GNU gdb 5.3-debian Copyright 2002 Free Software Foundation, Inc. .. snip .. This GDB was configured as "i386-linux"... (gdb) run Starting program: /usr/local/bin/wine Program received signal SIG32, Real-time event 32. 0x40046fc4 in pthread_getconcurrency () from /lib/libpthread.so.0 (gdb) bt #0 0x40046fc4 in pthread_getconcurrency () from /lib/libpthread.so.0 #1 0x40046e08 in pthread_getconcurrency () from /lib/libpthread.so.0 #2 0x400463f2 in pthread_create () from /lib/libpthread.so.0 #3 0x00110de6 in get_threading () at glibc.c:61 #4 0x00110e2e in main (argc=1, argv=0xbffffc74) at glibc.c:73 Thanks bye Fabi

3 4

Re: PATCH: old freetype patch / FT_Get_First_Char
by Pouech Eric DMI AEI CAEN 15 Dec '03

15 Dec '03

> + if(!!pFT_Get_First_Char || (pFT_Get_First_Char( ft_face, &dummy ) < 0x100)) me thinks two bangs are one too much A+

2 1

Re: Running Wine under MS SFU under Wine ... ?
by Dan Kegel 15 Dec '03

15 Dec '03

Greg wrote: > On Sunday 14 December 2003 09:02 pm, Dan Kegel wrote: > >>I recently posted with problems running Microsoft's >>Services for Unix under Wine. I only tried it out >>of morbid curiosity, actually, and because MS was >>offering it for free. The free offer expired, but >>it's back again for a little while; slashdot.org >>seems to be running banner ads for it. I'd encourage >>any of you who even *might* be tempted to try this >>out to go order the CD-ROM. It would be way bitchin' >>cool if we could nest Wine and MS SFU (I seem to recall >>we can't nest Wine in Cygwin for some technical reason, >>but who knows, maybe SFU won't have the same problem). > > Don't get your hopes up; they are nothing to write home about. OK, I have to confess, I was drunk when I wrote that :-) My real point is - SFU is yet another set of windows programs we can use to test wine, may as well grab a copy while they're 'free'. - Dan

1 0

Re: Resend: Another fix for kernel file test
by Alexandre Julliard 14 Dec '03

14 Dec '03

Hans Leidekker <hans(a)it.vu.nl> writes: > Tested on Win2k and Win98. MoveFile returns ERROR_ALREADY_EXISTS > when the destination exists. > > -Hans > > Changelog > MoveFile returns ERROR_ALREADY_EXISTS, not ERROR_FILE_EXISTS You need to fix the code too, or add a todo_wine; I can't commit tests that fail. -- Alexandre Julliard julliard(a)winehq.com

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel