- Wine-Devel - list.winehq.org

Re: Borland C++ Buildeer under Wine
by Oliver Stieber March 13, 2005

March 13, 2005

--- Andrew Neil Ramage <nrsc16850(a)blueyonder.co.uk> wrote: > Below is the last three lines of error messages > printed when I tried to > run Borland C++ Builder under wine. (There were > pages and pages of > error messages after I hit Ctrl-C in the terminal I > had started BCB.EXE > from.) > > Is this a known bug in Wine ? > > err:syslevel:_EnterSysLevel (0x40797840, level 2): > Holding 0x4083ccc0, > level 3. Expect deadlock! > err:syslevel:_CheckNotSysLevel Holding lock > 0x4083ccc0 level 3 > err:seh:setup_exception stack overflow 176 bytes in > thread 0009 eip > 004078d5 esp 405b0f50 stack 0x405b0000-0x406b0000 > [andrew(a)zeus BIN]$ > The stack overflow looks like somethings got stuck in a loop, which is problably why there were pages and pages of messages. What version of CBuilder are you using, CBuilder <=5 used to work. http://www.borland.com/products/downloads/download_cbuilderx.html CBuilder X claims to run on linux OOTB. I've got standard on the shelf, > -- > > Andrew > > [hackcoughsniffle] > Internal Virus Database corrupt > > Send instant messages to your online friends http://uk.messenger.yahoo.com

2 1

Re: Wine Start Menu in the Desktop Applications Menu
by Mike Hearn March 13, 2005

March 13, 2005

On Sat, 12 Mar 2005 18:09:52 -0800, Scott Ritchie wrote: > We've talked about it on the Wine lists before, but there have been some > difficulties. The first is that we don't yet understand how to read > Windows shortcut files and interpret them: this can probably be overcome > with some work. Really? That's news to me. We can read .lnk files just fine and even produce .desktop files for them, that's where the icons on the desktop come from. > Here, I propose a short plan of action for getting Wine applications > into the Applications menu. Some of these need to be done at the > distribution level and some need to be done within Wine. When we have > it working nice and smoothly we can submit whatever changes we made to > freedesktop.org as well if they need to become a cross-distribution > standard. > > Here's how I see we can do this in Ubuntu: > > 1) Create a new Menu entry in the .menu file > at /usr/share/gnome-app-install/applications.menu This one will be > named "Windows Applications" and will need to point to two locations > for .desktop files: system-wide ones, and user-specific ones. > Instructions for how to do this are here: > http://standards.freedesktop.org/menu-spec/latest/index.html I don't think that's right, gnome-app-install is an Ubuntu thing. What you mean is we can drop a .menu file into ~/.config/xdg/menus/applications-merged and it'll be automatically linked in. We can do this in wineprefixcreate (or when the first menu entry is created). > 2) Create some Wine .desktop files that can go > in /usr/share/applications that will be readable by this menu entry. > These will be for system-wide Wine apps that are common to all users. > This will include Wine's own apps (like the configuration tool and the > uninstaller) as well as packages which depend on Wine (such as > Winetools). If we're going to create our own submenu to map the start menu we may as well put stuff like winecfg and the control panel there. No need to merge them into the main menu (where would they go, anyway?) > 3.) The menu specification can also point to a new location in the local > user's .wine directory, probably something like ~/.wine/menu. The winemenubuilder program is a winelib app so it'd be better to have it in, eg "~/.wine/drive_c/windows/start menu" > Here we'll have the user-specific .desktop files that link to the > Windows applications that user has installed. Once we figure out how to > make Wine build a start menu and translate the shortcuts into .desktop > files, they can be created there. It already does/can do, see winemenubuilder. We basically need to ensure it still works (probably hasn't actually worked properly for ages) and then merge the start menu directory in using the <LegacyMenuDirs> element. > These files can be kept up to date > (such as when a user installs a new windows application) by the > wineserver program. What will then tell Gnome to update the > applications menu (since new .desktop files will have been created) I'm > not sure yet. Not quite. The wineserver is a low level thing. Menu entries are created on the fly by the shell linker interface. GNOME monitors the menu directories/files so when they change it can reload the definitions (in theory, in practice this is broke on quite a few distros). > 4.) Once we get all that working, then we can start playing around with > icons. This should be fairly easy to translate across platforms. It > would be nice to have icons that Windows apps install available > centrally - this could perhaps be another dekstop integration task on > the Wine todo list. Already done. Again, observe that programs can place launchers onto the desktop (which you can then drag to the panel etc). thanks -mike

1 0

Borland C++ Buildeer under Wine
by Andrew Neil Ramage March 13, 2005

March 13, 2005

Below is the last three lines of error messages printed when I tried to run Borland C++ Builder under wine. (There were pages and pages of error messages after I hit Ctrl-C in the terminal I had started BCB.EXE from.) Is this a known bug in Wine ? err:syslevel:_EnterSysLevel (0x40797840, level 2): Holding 0x4083ccc0, level 3. Expect deadlock! err:syslevel:_CheckNotSysLevel Holding lock 0x4083ccc0 level 3 err:seh:setup_exception stack overflow 176 bytes in thread 0009 eip 004078d5 esp 405b0f50 stack 0x405b0000-0x406b0000 [andrew(a)zeus BIN]$ -- Andrew [hackcoughsniffle] Internal Virus Database corrupt

1 0

Re: [Wine]libwine-alsa, etc. still relevant?
by Scott Ritchie March 13, 2005

March 13, 2005

On Sun, 2005-03-13 at 11:01 +0200, David Baron wrote: > This came up before when debian upgrade wanted to remove these because of > their being the previous version. Now all the version numbers are consistant. > Deborphan lists them as orphans--no longer used! > > So ... are all these provided in the "main" wine library and these packages > actually orphans? If so, why are they still around? If not, what is going on? > > Packages are from the wine.sourceforge.net locations instucted on the winehq > site. > _______________________________________________ > wine-users mailing list > wine-users(a)winehq.org > http://www.winehq.org/mailman/listinfo/wine-users They're merged into the wine package in the winehq debs, since Wine is expecting them to be there anyway. Thanks, Scott Ritchie

1 0

Re: Warcraft 3 - "no program start menu found"
by Juan Lang March 13, 2005

March 13, 2005

--- Tony Lambregts <tony.lambregts(a)gmail.com> wrote: > I really appreciate you looking at this. Thanks for the patch. No worries, thanks for finding it. That'd been lurking for months, and it was my bug. Glad to flush it out. --Juan __________________________________ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs

1 0

dlls/dbghelp/elf_module.c, possible problem?
by Gerald Pfeifer March 13, 2005

March 13, 2005

Eric et al, the recent changes to dlls/dbghepl/elf_module.c have triggered the following compiler warning (using GCC 3.3) elf_module.c:1167: warning: passing arg 2 of pointer to function makes integer from pointer without a cast Would you mind having a look? Thanks, Gerald

1 0

Re: winetest, winrash and new volunteers
by Steven Edwards March 13, 2005

March 13, 2005

Hi, --- Chris Morgan <cmorgan(a)alum.wpi.edu> wrote: > I can give devel access to winrash cvs to anyone that wants it. I'm too busy > to work on this stuff myself these days. Is there some good documentation on how winrash and winetest work and communicate with the server? I am interested it in using it as part of the ReactOS build system. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

Wine Start Menu in the Desktop Applications Menu
by Scott Ritchie March 13, 2005

March 13, 2005

One of the most commonly requested features for Wine is for Wine to be aware of applications that put themselves into the Windows Start menu. We've talked about it on the Wine lists before, but there have been some difficulties. The first is that we don't yet understand how to read Windows shortcut files and interpret them: this can probably be overcome with some work. However, there are some other barriers to entry that are now turning around thanks to the Freedesktop.org specs. Here, I propose a short plan of action for getting Wine applications into the Applications menu. Some of these need to be done at the distribution level and some need to be done within Wine. When we have it working nice and smoothly we can submit whatever changes we made to freedesktop.org as well if they need to become a cross-distribution standard. Here's how I see we can do this in Ubuntu: 1) Create a new Menu entry in the .menu file at /usr/share/gnome-app-install/applications.menu This one will be named "Windows Applications" and will need to point to two locations for .desktop files: system-wide ones, and user-specific ones. Instructions for how to do this are here: http://standards.freedesktop.org/menu-spec/latest/index.html 2) Create some Wine .desktop files that can go in /usr/share/applications that will be readable by this menu entry. These will be for system-wide Wine apps that are common to all users. This will include Wine's own apps (like the configuration tool and the uninstaller) as well as packages which depend on Wine (such as Winetools). 1 and 2 will get us some nice launch icons for the important pieces of Wine that most users aren't yet aware of (such as the new uninstaller and winecfg tools). Combined with Wine's ability to make desktop launcher icons when a program says to install an icon on the desktop, this should be a fairly good start at making Wine console-free. 3.) The menu specification can also point to a new location in the local user's .wine directory, probably something like ~/.wine/menu. Here we'll have the user-specific .desktop files that link to the Windows applications that user has installed. Once we figure out how to make Wine build a start menu and translate the shortcuts into .desktop files, they can be created there. These files can be kept up to date (such as when a user installs a new windows application) by the wineserver program. What will then tell Gnome to update the applications menu (since new .desktop files will have been created) I'm not sure yet. 4.) Once we get all that working, then we can start playing around with icons. This should be fairly easy to translate across platforms. It would be nice to have icons that Windows apps install available centrally - this could perhaps be another dekstop integration task on the Wine todo list. 5.) Different architecture issues. One of these days a working amd64 version of the Wine packages will be available (perhaps whenever I manage to afford a new amd64 computer). It's entirely doable to make it work transparently, once the upstream quirks in compiling Wine on 64 bit get worked out. We can also install 32 bit libraries (so we can run 32 bit windows programs) in a way similar to what we do with Open Office. The PowerPC version of the packages, however, is another issue. Obviously, we can't make Wine work with i386-compiled apps on PPC, however we can make it work with Winelib ones. If I ever finish packaging up eMule after getting it to compile in Winelib, a PPC Wine package version could put the .desktop files into the same place as Winetools goes, and then put eMule right there alongside it on PPC. Alternatively, on PPC we could just not use the new Windows Applications submenu altogether, and instead put Winelib apps like eMule in a normal place like Applications->Internet. I still have no idea exactly who is going to do which part of this work, or when, but it all seems like the right way forward to me. Comment is very appreciated. Thanks, Scott Ritchie

2 1

Re: Warcraft 3 - "no program start menu found"
by Juan Lang March 13, 2005

March 13, 2005

> I am beginning to I suspect it should really go in > dlls/shell32/shellpath.c It is. I think I see where the bug is, and I'm working on it. I should have a patch sometime this weekend, maybe later tonight. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

winetest, winrash and new volunteers
by Paul Vriens March 13, 2005

March 13, 2005

Hi, as can be seen from the test.winehq.org site the number of test-runs dramatically dropped. Apart from the fact that there were problems with the automated download of new tests by winrash: http://www.winehq.org/hypermail/wine-devel/2005/03/0373.html winetest will not run but bail out because there is no visible desktop. 3 of the 5 (!) tests that are now there, where done by me. Where in a 'normal' case we should already have dozens. I don't want to go into a discussion about the fact that 'running as a service' and 'on a visible desktop' can/cannot live together properly. Or why we should have 'visible' tests or not. I just want to have as much tests run as possible. I mean that was the whole idea behind it right? An approach should be decided upon: - Have (again) volunteers who run the winetest manually/interactively - Use winrash and have every test decide whether it needs interactivity - 'Fix' winrash so tests run, maybe semi-automated, on a visible desktop - .... An approach for the last is to have winrash fill in one of the 'run' keys (as it does on win98 already during install). I will be/stay a volunteer for the first approach until we decide what to do. Cheers, Paul.

3 2