similar to: Re: wine seti@home team

Microsoft probably has unix CPUs running seti, and I see no point in running it on wine, it would just be slower. The unix client is much better. The point is if M$ have a seti team we must have one too. The Linux team is way ahead of M$ so don't worry about being redundant. Ivan.

Hello, I would like to ask all users running seti@home to join wine's team http://setiathome.berkeley.edu/team_display.php?teamid=38091 if you haven't got a seti@home account you can create one and join our team automatically by using this link http://setiathome.berkeley.edu/create_account_form.php?teamid=38091 Our current target is to catch up with the Microsoft team that's here

http://setiathome.berkeley.edu/team_display.php?teamid=120195 If anyone here is participating in SETI at Home, consider switching teams to boost CentOS. :-) -Magnus -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20051026/545b1c11/attachment-0002.html>

For those of you who don't know yet, the Wine project has it's own seti@home team, at http://setiathome2.ssl.berkeley.edu/stats/team/team_172471.html The current objective is to overtake the Microsoft team http://setiathome.ssl.berkeley.edu/stats/team/team_28.html Help is needed, please if you already have seti@home installed. If you don't, it's only 300k to download, runs natively

This is a lil bit off topic, but I thought I would bring it up, since we have users that are trying to run windows BOINC under wine. The wine project has a SETI@Home team (has had for some time), so if you run the windows or linux BOINC/SETI@Home client, you can join our team and apply your credits towards the project's total. Just go to

All, The CentOS Folding at Home team has cracked the top 10% of all the folding teams. We could use some more members that have CPU Cycles to spare :) Folding at Home is a great distributed computing program that is used to process items for medical research teams. It is similar to SETI at Home (if you are familiar with that). Here is info on Folding AT Home: http://folding.stanford.edu/

Hi, I'm trying to run Seti Queue 1.0 under the latest debian wine package 0.0.20010326-3. However, when I try to run wine --winver win98 setiqueue I get the following log output: fixme:win32:GetUserObjectInformationA (0x1 1 0x40566c14 12 0x40566c20),stub! err:advapi:StartServiceCtrlDispatcherA Couldn't find wait semaphore err:advapi:StartServiceCtrlDispatcherA perhaps you need to start

This is the second attempt at sending this. Apologies for any duplicates. I've got Winbind up and running to authenticate our users against our AD and to save kerberos tickets. I have used the "winbind refresh tickets = yes" setting expecting this to renew these kerberos tickets before they expire. This does not appear to work. Gnome will pop up a dialog box saying that the

----- Message d'origine ---- > De : David Baron <d_baron at 012.net.il> > ? : wine-users at winehq.org > Envoy? le : Jeudi, 28 F?vrier 2008, 18h53mn 08s > Objet : Re: [Wine] How about this replacement of WINE. > > > However, it's a great, great project IMO. It was about time something > > > like that should've been made. Redirecting calls is simply

wine: Unhandled page fault on read access to 0x409ffd80 at address 0x4000ba7c (thread 0009), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 32") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger This happens on everything I try run. Note: Still a problem with latest upgrade. It may have more sideeffects than

The BOINC project has a screensaver that runs on Windows. I installed BOINC in a virtual machine running Windows XP (32 bit) and copied boinc.scr from the C:\Windows directory onto my 64 bit F13 system. When I run the screensaver I get an error. Any feedback is appreciated. I can run glxgears without any problem. $ wine boinc.scr Wine cannot find the ncurses library (libncurses.so.5).

On Fri, Dec 30, 2011 at 3:59 PM, Camale?n <noelamac at gmail.com> wrote: > On Fri, 30 Dec 2011 10:48:42 +0000, Bruno Martins wrote: > >> I am having this problem, and it gets logged every second: >> >> Dec 25 07:49:51 sputnik gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=joe

Around last weekend, the updated package, gnome-screensaver-2.16.1-8.el5_5.1, came in replacing gnome-screensaver-2.16.1-8.el5. Once our CentOS 5.5 machines are running the new gnome-screensaver, we start seeing problem in unlocking the Gnome screensaver with Kerberos authentication. Unlocking the screensaver with local password works fine. After we back out from the new version, Kerberos

Hi, Environment: I am using CentOS 5.3 operating system. I upgraded xorg of centos to 7.3. I am using intel 945 GM board. My xorg server version is 1.4.2 and inetl driver version 2.4.3. gnome-screensaver version is 2.16.1-8.el5. Problem: I connected another system of same hardware using VGA output. Now I can see clone of my system on secondary display. I enabled screensaver with 1 minute period

Hi, I tried some windows screensavers with Wine. Most screensavers start with the configuration screen without a possibility to start the main screensaver part. It's the same thing when I rename a screensaver file from 'somewhat.scr' to 'somewhat.exe' and try to run it with a doubleclick on my Windows 2000 PC. (*.scr: the screensaver starts, *.exe: the configuration screen

Hi Friends, I am trying to configure screensavers settings on Gnome and KDE running Centos 5.x 32-bit environment. I need to prepare a script which will be push by Puppet and this script should be able to change settings like idle_delay, set customized password-protected screen saver, enabling lock etc.. I have tried below commands for Gnome and somehow the settings are not taking place. The

Hello All, I'm trying to set defaults for gnome-screensaver on some Centos6.5 laptops and lock it down with these commands: # gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type boolean --set /apps/gnome-screensaver/lock_enabled true # gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type boolean --set

Hello All, these days one of my tasks is connecting some Centos7 laptops to Freeipa, also running on Centos7. After doing that, some users report nog being able to unlock their screens. Only after reboot are they able to login again. I see this em in /var/log/secure: Aug 10 13:34:37 **** mate-screensaver-dialog: pam_sss(mate-screensaver:auth): authentication failure; logname= uid=382900663

Hi all! I keep having problems with screensaver(s) on Centos-7. I have in the past liked Xscreensaver, so I've installed it and tried to suppress whatever other screensaver is on the system. Xscreensaver works fine for a day or 20 then quits working. After a lengthy battle I gave up and removed it. I'm now trying mate-screensaver, which does the same thing! when I say "quits

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When