Dolphin on Wine - starting to look good
- From: Steve Taylor <smt2@xxxxxxxxxxxxxx>
- Date: Wed, 02 May 2007 21:29:08 +1000
Though I use WindowsXP at home, it's been many years - and a few jobs - since I used anything other than Linux at work, and it's always annoyed me that I couldn't muck around with Dolphin there.
Add to that the fact that "because it only runs on Windows" is about 2028th on my list of "reasons I like Dolphin", and you can see why I check Dolphin out on Wine with each new update.
With the latest version of Wine, 0.9.36, Dolphin has become usable for the first time - most of the browsers can be opened without an error (the help system and the code mentor are still out, but the view composers and code browsers are fine). Idea spaces work, code can be executed, the image can be saved. I have had some crashes, but it feels workable - there may be obvious areas to avoid. Many of the sample applications run, though the graphics based ones are ruined by a hamhanded fix I made to get rid of a consistent walkback - perhaps someone here can offer a more sensible approach.
Here's a quick runthrough of what I did to make it work. Some of this may be incaccurate, as I did the actual Dolphin install quite a while ago:
Installing Wine - nothing special. As I'm using Fedora, I just did 'yum install wine'
Configuring Wine - using the winecfg utility, I set Wine to run as WindowsXP by default, to allow the window manager to control the desktop, and to run inside a virtual desktop.
Installing Dolphin - I installed Dolphin 6 professional from a .msi. I forget at this point whether I installed the Windows msi.dll or used the built in support in Wine. You might try looking at the advice on http://frankscorner.org/index.php?p=msi which says:
You can install .msi files with the msiexec.exe utility. This command is built into Wine, so you don't have to install Windows Installer from Microsoft.
If the .msi file is called msifile.msi you just have to type msiexec /i msifile.msi and the application will be installed.
The Dolphin installer had issues with window size - I seem to recall that it tried to draw its window a million pixels wide, and that setting Wine to run in a virtual desktop (rather than as multiple OS level windows) was the solution. You need Wine to run in a virtual desktop while installing Dolphin, but not afterwards when you're running it.
Running Dolphin - run as 'wine Dolphin.exe -nosplash myImage.img', as it can't handle displaying the splash screen. The system folder comes up only about 20 pixels high, and cannot be persuaded to expand. There is *just* enough room, if you're pixel perfect with the mouse, to open a new workspace, which is all you really need the system folder for.
When you open a browser, you'll get a walkback, with the failure on
I droppped into the debugger at this point and changed the line
ifTrue: [GDILibrary default systemError]
ifTrue: [Color black]
This is crude as hell, but it stops the system complaining. As I say above, if anyone has a more sensible approach, I'd love to hear it.
At this point I manually killed off the processes I didn't want (the 'panic button' under the Tools menu seems to panic a little too much :) ), opened one workspace for next time, and saved the image.
It's far from perfect, but it's workable, and I'm too pleased for words.
- Prev by Date: Re: Changing a menu in visual designer causes nasty deaf object image shutdown
- Next by Date: Re: Dolphin on Wine - starting to look good
- Previous by thread: Re: browseUnimplemented on ToGo app not working properly anymore?
- Next by thread: Re: Dolphin on Wine - starting to look good