Date: Fri, 19 Dec 1997 08:44:12 +0100 From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> To: Stefan Esser <se@freebsd.org> Cc: "Christoph P. Kukulies" <kuku@gilberto>, ports@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Wine success story Message-ID: <19971219084412.46153@gil.physik.rwth-aachen.de> In-Reply-To: <19971217235738.48757@mi.uni-koeln.de>; from Stefan Esser on Wed, Dec 17, 1997 at 11:57:38PM %2B0100 References: <199712170841.JAA20651@isdn-kukulies.dialup.rwth-aachen.de> <19971217235738.48757@mi.uni-koeln.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 17, 1997 at 11:57:38PM +0100, Stefan Esser wrote: > On 1997-12-17 09:41 +0100, "Christoph P. Kukulies" <kuku@gilberto.physik.RWTH-Aachen.DE> wrote: > > > > Just FYI: > > > > I installed the most recent version of Wine (Wine-971130 from sunsite). > > And despite one quirk in memory/virtual.c where I had to get > > acoross the fact that FreeBSD doesn't do synchronuous memory > > syncs (Linux: <asm/mman.h>) I was able to throw it at my > > C:\WIN95 directory. > > Hi Christoph! > > Hmmm, didn't you build Wine from within the ports tree ? > If you did, then the second chunk in patch-an should have > taken care of defining MS_SYNC: Actually the story went this way: I compiled wine from the ports tree and it gave a bad system call in the first place. Hmm, thought I, should the port be broken? Maybe. Anywat, let's try the latest version (971130) and while doing this it came to mind that SYSVSHM might be the cause for the bad system call. Then it worked and while being at the newer version anyway I didn't care to fall back to previous (ports) release). Strange though that the patch didn't apply. > > *** memory/virtual.c~ Mon Dec 1 23:13:06 1997 > --- memory/virtual.c Mon Dec 1 23:24:57 1997 > *************** > *** 1098,1101 **** > --- 1098,1104 ---- > } > if (!cbFlush) cbFlush = view->size; > + #ifndef MS_SYNC > + #define MS_SYNC 0 > + #endif MS_SYNC > if (!msync( addr, cbFlush, MS_SYNC )) return TRUE; > SetLastError( ERROR_INVALID_PARAMETER ); > > I had added that patch before John Dyson added MS_SYNC > to sys/mman.h. AFAIK, we didn't need it, because it is > the default behaviour of msync() (that's where the name > comes from :), and a flag value of 0 could have been > used in WINE. > > > wine progman > > > > and voila, my Win95 desktop appeared neatly sorted in progman program groups. > > The fonts and the colors/hatching/dithering a bit strange though. > > You may need to edit your $(PREFIX)/etc/wine.conf file, > if it contains font alias lines as required by earlier > releases of WINE. See the sample wine.ini file found in > the work directory. > > > Now, the big success: Freecell works! > > > > So, no more need to boot a Win95/NT System :-) > > Quite some more stuff is working under WINE! I've been > using it to look at MS-Word .doc files. Both Winword and > the free Word viewer work reasonably well under WINE for > more than one year, already! > [...] > > You can always choose to execute the real Windows DLLs, > instead of the emulation code that comes with WINE. Ah, that's interesting. Didn' t know that. Actually, the reason why I tried wine againe was that I was in seek of running some applications , a 8051 cross compiler, under DOS (emu or whatever). pcemu though running fine turned out to be insufficient since it doesn't support DPMI resp. 386 architecture. So my hopes concentrated on running a DOS Command Prompt box under Wine. It doesn't seem to work with me here. > > > What I'm concerned about though is the fact of this unimplemented > > MS_SYNC feature. That's why I'm cross posting this to -hackers also. > > Well, it always was kind of implemented ... > You only had to use its other name: "0" :) > > Regards, STefan Thanks. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971219084412.46153>