January 2003 - Wine-Devel - list.winehq.org

Re: [RFC] The Wine UI page

by Eric Pouech

> Whether such a matrix is usable (may be too big) is not clear to me. > But it's an interesting idea. However, the hard part is the content, > and that's difficult to get. Once I finish this page, maybe we can > create a unifing matrix, see how it looks. my idea was not necessary to use the matrix for display, but more for info gathering. afterwards, it would be easier to extract by rows and or columns. in any case, filling in the cells is the hardest task and the UI row is still empty... so, keep on filling it ;-) (or is it a column ? ;-) >>another piece, I forgot about some other control(s) (and here it's more >>than a simple control): >>- MCIWndClass in msvideo/msvfw32 the real official name seems to be MciWnd according to MS docs > Can you please help me complete the entry: > -- URL to MS docs http://msdn.microsoft.com/library/default.asp?url=/library/en-us/multimed/m… > -- status (% completion, what it's missing) I'd say 20 to 30% completion. Very limited core implementation. All bells & whistles are missing including extended styles, notification, MCIWNDM_ messages > -- maybe to an audit against the latest MS docs, see _exactly_ > what we're missing. A+ -- Eric Pouech

Jan. 31, 2003

Explorer

by Steven Edwards

I've been reading all of the traffic regarding getting explorer to work under WINE or writing a replacement for WINE and thought this would be a good time to chime in. ReactOS is about to release version 0.1.0 this weekend and is starting to include support for basic Windowing and CDrom installing. There has been much discussion on when/if we will reimplement explorer.exe also so maybe we can work together on this as ReactOS is using WINE for large parts of the shell support. If the WINE project is going to start a implementation of explorer.exe then we will work off of that. Thanks Steven __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Jan. 31, 2003

Re: Why is IOCTL_CDROM_READ_TOC so slow?

by Eric Pouech

Waldeck Schutzer wrote: > Here is something interesting. When I turn the drive back into a plain > ide (by removing the ide-scsi option from the kernel options), it speeds > up considerably. Now it rocks! This makes me wonder what the heck is > going on with the kernel. dunno maybe either some non caching being used in scsi, or request queueing with timers... should find some time reading the kernel source though A+ -- Eric Pouech

Jan. 31, 2003

Re: Winelib project

by Hans Christian Studt

Hans Christian Studt wrote: > Dimitrie O. Paun wrote: >> Yes, it's just a symbolic link: > Be sure someone fix that in the CVS. No fix needed - It is correct in /usr/local/bin - sorry -- Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk .dk og W3C standarder : http://w3c.studt.dk

Jan. 31, 2003

Re: Winelib project

by Hans Christian Studt

Dimitrie O. Paun wrote: > On Fri, 31 Jan 2003, Hans Christian Studt wrote: > >>I just build from the CVS and I now have >>/usr/local/wine/tools/winegcc >>but I canot find >>wineg++ >> >>Should there be a symbolic link to winegcc or what ??? > > Yes, it's just a symbolic link: > > [dimi(a)dimi dimi]$ ls -l /usr/local/bin/wine* > -rwxr-xr-x 1 root root 242956 Jan 15 21:09 /usr/local/bin/wine > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineboot > -rwxr-xr-x 1 root root 396533 Jan 30 13:08 /usr/local/bin/winebuild > -rwxr-xr-x 1 root root 66714 Jan 15 21:09 /usr/local/bin/wineclipsrv > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/wineconsole > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winedbg > -rwxr-xr-x 1 root root 287808 Jan 30 13:08 /usr/local/bin/winedump > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winefile > lrwxrwxrwx 1 root root 7 Jan 30 13:08 /usr/local/bin/wineg++ -> winegcc > -rwxr-xr-x 1 root root 51173 Jan 30 13:08 /usr/local/bin/winegcc > -rwxr-xr-x 1 root root 19864 Jan 15 21:09 /usr/local/bin/winelauncher > -rwxr-xr-x 1 root root 97085 Jan 30 13:08 /usr/local/bin/winemaker > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winemine > -rwxr-xr-x 13 root root 1594 Jan 15 21:09 /usr/local/bin/winepath > -rwxr-xr-x 1 root root 1372162 Jan 15 21:09 /usr/local/bin/wineserver > -rwxr-xr-x 1 root root 5726 Jan 15 21:09 /usr/local/bin/wineshelllink > -rwxr-xr-x 1 root root 62872 Jan 30 13:08 /usr/local/bin/winewrap > [dimi(a)dimi dimi]$ Thanks Be sure someone fix that in the CVS. -- Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk .dk og W3C standarder : http://w3c.studt.dk

Jan. 31, 2003

Re: Winelib project

by Jeff Smith

Yes. BTW, when 'make install'ed, wine should create the appropriate link in the same directory it installs winegcc. -- Jeff S >From: Hans Christian Studt <hcstudt(a)post10.tele.dk> > >I just build from the CVS and I now have >/usr/local/wine/tools/winegcc >but I canot find >wineg++ > >Should there be a symbolic link to winegcc or what ??? >-- >Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk >.dk og W3C standarder : http://w3c.studt.dk _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

Jan. 31, 2003

Re: PATCH - wineserver named_pipe.c porting fix

by Dimitrie O. Paun

On Fri, 31 Jan 2003, Steven Edwards wrote: > Working on building wineserver on mingw > > Changelog: check for sys/socket.h Dude, Just bundle all these patches together, under such a ChangeLog: Check for missing headers in mingw. I think it's simpler for everybody: you (to submit), us (to review), Alexandre (to apply), and it's in fact a logical change that shouldn't be split. -- Dimi.

Jan. 31, 2003

Re: Winelib and <io.h>

by Dimitrie O. Paun

On Fri, 31 Jan 2003, Hans Christian Studt wrote: > I can still try out Ming/Cygwin but how would that change the > <io.h> problem ??? It will not, but it will make it much more easy for us to fix. Basically, if it works under MinGW, it should work under Wine. Thing is, you don't want to have to fix _all_ the porting problems at once. MinGW provides an _ideal_ midstep in the process, and it comes almost for free, because it doesn't imply a detour to take it. Essentially you have to pass through the point where the app builds under MinGW, you might as well try and see that it does. This removes a _lot_ of the uncertainties in later stages, making them so much easier to debug and fix. That being said, try to compile using the MSVCRT headers. To do that, just pass -mno-cygwin to winegcc, see if that works. -- Dimi.

Jan. 31, 2003

Re: Winelib project

by Hans Christian Studt

Dimitrie O. Paun wrote: > On Wed, 29 Jan 2003, Hans Christian Studt wrote: >>Hi, >> >>I am trying to compile some sourceforge windows projects under >>winelib and need some guidance regarding how to fix these errors. >> >>bb4win >>=========================================== >>g++ -c -I. -I/usr/local/wine/include -g -O2 -fpermissive >>-fno-for-scope -D_REENTRANT -o BB >>Api.o BBApi.cpp > > Please use wineg++ instead of g++, and winegcc instead of gcc. > Do the apps you are trying to compile build under MinGW? If so, > all you have to do to the makefiles (in theory) is this: > > -CC=gcc > -CXX=g++ > -RC=windres > +CC=winegcc > +CXX=wineg++ > +RC=wrc > > If it does not work like this, please report back on the list. > > On the other hand if they don't build under MinGW currently, > your best bet is to get them to build & run under MinGW first, > and try to port them to winelib after that. > >>I you are busy I will try to look at it :-) > > If you are, let me know, I'll give you a braindump of > what I think needs to happen. I just build from the CVS and I now have /usr/local/wine/tools/winegcc but I canot find wineg++ Should there be a symbolic link to winegcc or what ??? -- Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk .dk og W3C standarder : http://w3c.studt.dk

Jan. 31, 2003

Re: RPC marshalling patch

by David Laight

> > > and here is some free-as-in-beer RPC 1.1 stuff: > > > > http://www.opengroup.org/products/publications/catalog/c706.htm > > And on there, they just want to borg the email addresses of every reader, > but not their souls or firstborns, as far as I can see. When they set up this 'free' access to the documents it was rather a change of direction for (what was then) X/Open. After all they had a business model that assumed they would be making money from selling the books, rather than just taking money from the contributing companies and giving away a 'free' copy of each book to each company. In any case they wanted a log of who was downloading stuff, but they said at the time that the email addresses wouldn't be used for other purposes. I've certainly never received junk mail from them. I suspect the log (like the ones from anon ftp passwords) is of little use to anyone. David -- David Laight: david(a)l8s.co.uk

Jan. 31, 2003