similar to: No subject

I installed the latest Codeweavers preview build (binary RPM, ugh!), and the DeskTopWindow error I was experiencing building from cvs is gone. All the font fixme warnings (which had, at one point, gone away) are back, and I'm back to the previous error I was getting before DeskTopWindow: babylon5:alaric:~:46 $ wine --debugmsg fixme-font d:\\install.exe Invoking /opt/wine/bin/wine.bin

A question for the WineLib guru's :) I am using the wine-20011108 build with Mandrake 8.0 and with this version of wine clean compiled and installed I can run several windows programs very successfully :). Then I use winemaker to create a WineLib 'so' file and the compile and link again runs clean. But when I run the resulting 'so' file using this command line: $

The Wine development release 1.2-rc7 is now available. Barring any last minute problems, this should be the last release candidate before the final 1.2. Please give it a good testing. What's new in this release (see below for details): - Translation updates. - Various bug fixes. The source is available from the following locations:

This is release 1.0-rc3 of Wine, a free implementation of Windows on Unix. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. Because of lags created by using mirrors, this message may reach you before the release is available at the public sites. The sources will be available from the following locations:

maximi89@maximi89-desktop:~$ wine '/home/maximi89/.wine/drive_c/Sierra/Empire Earth/Empire Earth.exe' wine: Unhandled page fault on read access to 0x00000000 at address 0x866f8e (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00866f8e). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:00866f8e

I compiled and installed wine using the ./tools/wineinstall script without any modifications. It built and installed without indicating problems. When I attempt to run any program wine drops into the debugger immediately. When I run with --debugmsg warn+all I get the following trace which I have copied in part. I gather that wine is searching for the following dll's: ntdll.dll,

Hi all, i have run starcraft from the debugger, and it's fast. (Well, about as fast as win98 on a P-60) I have run it from wine, and it's slow (about a 468-33) The real machine i runt it from is a celeron 416, 160 MB ram, geforce 2 mx400 PCI I *finaly* discovered i could get a trace from it by using winedbg -debugmsg i.e. ONE dash. I run a diff on both files, and i was surprized to

Hello again, I've now running wine20010326 according to Gerards Tips and Hints and I make several debugmsg events. First I was very surprised of the size of the debug-message (50 MB) and so I run every event singular (instead of --debugmsg +relay +text +string +file +dosfs) Hope someone could help me now with my problem when he reads the debug messages. Again I cannot position any Text

Hi! I started using wine (wine-20020122 compiled from source tarball) a couple of weeks ago to run a store-point-of-sale application. The idea is to port this windows application to linux. Before porting, we decided to check if the app could be emulated on linux with wine or recompiled with winelib. This is also necessary to run proprietary windows DLLs from third parties such as credit card

crossposted to wine-dev, and wine-users Hi, I've done some more tests, and i found that when i run winedbg starcraft and wine starcraft and then again winedbg starcraft etc. It works, but always following this pattern: <boot my box> winedbg starcraft :all runs perfectly wine starcraft: all video choppy winedbg starcraft :all runs perfectly winedbg starcraft: all video choppy wine

Hello, We just started using WineLib, and have very basic question: which -g??? option do you use to do source level debugging with winedbg? I searched the documentation and mailing list for any step-by-step about this, but found nothing. So either the answer is so obvious that I just can't see it - or it doesn't work? By default, winemaker seems configure things for no debug - so

Thanks Lawson. I am trying to run a program now, but it doesn't start. I have got the next output after I did: wine --debugmsg +loaddll logic.exe: trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\Program Files\Logic Audio Platinum 5.01\msacm32.dll' : builtin trace:loaddll:MODULE_LoadLibraryExA Loaded module 'C:\WINDOWS\SYSTEM\msacm.drv' : builtin

Hello, I run Mandrakelinux 10.1 with wine-20040813-2mdk. I have BricsCAD version 5.1.0012-1 installed. Upon start, I get this wine error message: can't open file icad.log error=5 (Access to icad.log was denied) [pablo@localhost bricscad]$ /opt/bricscad/bcad.sh fixme:ole:CoRegisterMessageFilter stub fixme:ole:RegisterTypeLib Registering non-oleautomation interface!

please find enclosed the latest WWN issue A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle -------------- next part -------------- Wine Weekly News All the News that Fits, we print. Events, progress, and happenings in the

please find enclosed the latest WWN issue A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle -------------- next part -------------- Wine Weekly News All the News that Fits, we print. Events, progress, and happenings in the

I recently upgraded from Fedora 8 to Fedora 9. Wine-0.9.58 was included. When I tried to run an already installed app, nothing happened. Wine configuration didn't run either. I examined the shell scripts in /usr/bin and found that winecfg, wineconsole, winedbg, winefile, and winemine all contained the same scripts, starting with "Wrapper script to start a Winelib application once it

Hello, Has anyone ever gotten Dungeon Keeper to successfully run under wine? I'm a newbie to wine, but I managed to get it installed and configured to the point of where it would install the game off the cd-rom. I'm using: Wine release 20010629 And I've added the usual WinMM section to the config file. Here is what wine told me when I installed the game: Linux black > wine

Sorry, I'm new to this group, therefore I couldn't answer until now. I think I may have some answers, all related to Wine source distrib, but they should be adaptable to CodeWeavers Wine: 1) Don't know... 2) for uninstalling win32 apps, you have to use "uninstaller". This program is in ./program/uninstaller from the wine source tree. It is very easy to install actually:

Full_Name: Venkatesh Mysore Version: R-1.7.0 OS: WindowsXP Submission from: (NULL) (216.165.110.10) While accessing Rproxy.dll repeatedly (using the code from the (D)COM example in the R website) causes a failure in the 24th iteration. R-1.6.2 does NOT give this error. This seems to be a memory management error, that might be linked to the huge leakage difference between R-1.7.0 and R-1.6.2

nomailthankyoug.patel@wanadoo.fr (gerard patel) writes: > The font mapper is something really weird under Wine; most of > its weirdness comes from that it's emulating Windows behaviour. How reassuring :) > I use stars to test Wine, and definitely the app does not > use this strange font on my system > It only displays 'the production queue on Backwele is empty' and