> An aside. On another thread, I noticed you are running Linux with Wine. Have
> you had any problems using Windows software under Wine?
> The reason I ask, is that I am, seriously, thinking of switching over to SuSE
> -H. Richard Utzig
I've had issues running setiathome on wine.
The fonts get messed up (classic gui)depending on how you set up your Wine config. I've also seen what I think are access violations when running the classic gui under wine.
The setiathome.exe command line runs ok under wine. It runs a smidge faster than the linux command line. If yo're a 'cruncher' then go for that route. The linux command line for seticlassic works ok as well, just 5% slower.
The 'cruncher' thing to do is run "seti.exe CLI 3.03"* for maximum performance.
On my xp machine, desktop, windows XP is on a NTFS partition, so, running knoppix as a test means that I have to mount that drive using captive NTFS, manually set it to read/write mode from a commmand line.
Then, I start up wine. Wine is good at grabbing the win98 fonts. It runs differently when on a XP machine and has to create a fake windows file.
pentium 2 266 laptop which had a win98SE on a drive. This machine is a knoppix machine now that the hard drive crashed yesterday.
2.2ghz Celeron with XP home. I tend to run this under windows only.
Boinc - I tried out boinc 3.20 on wine.
Had trouble getting the '-allow_remote_gui_rpc' to work.
ie.. had trouble calling it as
wine boinc -allow_remote_gui_rpc
wine 'boinc -allow_remote_gui_rpc'
wine boinc doesnt work on my xp machine.
I had 'wine boinc' running on my laptop, but it couldn't really handle the graphics (poor pentium 2).
Summary: I don't bother running boinc under wine. You need to have had a win98 previous install (basically the files for wine to access to grab drivers) to run nicely. So, on my XP machine, I don't have access to the win98 setup. On my laptop, it doesn't have the horsepower to run wine, gui, and do the OpenGL rendering of graphics, so I mostly stick with the linux boinc client.
Boincview - runs on wine. I recommend it if you cant get boincgui to run.
The older versions of boincview used a lot of memory.
Newer boincviews are compatible with boinc 4.x
Was able to run boincview under wine to connect to boinc_linux running on my laptop
Boinctop runs under knoppix. Cause it's a stand alone linux app.
Setispy 'runs' under wine. I had issues with the fonts and having stuff show up in the menu list. This is a Wine-Win98 versus Wine-FakeWindows thing.
some linux addons don't run under knoppix. They require QT to run. So, that rules out boincgui and I think boincstat.
I like the linux client.
Newbie linux users may run into issues with unpacking the various clients and putting them on the hard drive (in my case, flash drive on laptop). If something doesn't run, check the permissions. Sometimes, linux will know know what to do with a recently unpacked 'boinc'.
Konqueror is good at using Ark to unpack the boinc client. it's easy to make mistakes using tar.
* I like to rename my clients from setiathome.lotsofdigits.etc.etc.etc to setiathome and boinc
Things that work.
wine boinc -works, running gui on old machines is clunky.
wine boincview -works. allows you to easily add projects, reset, etc without having to get into typing stuff in the cli.
Things that suck.
wine boinc -allow_remote_gui_rpc silly wine, silly brackets. I give up.
wine without access to a win98 install.
wine running classic.gui (had some exception errors when client tried to contact server)
wine boinc .. and trying to run opengl graphics on a clunker.