We'll get there..:up:
Printable View
We'll get there..:up:
I'll try tweaking a little bit more out of my Q9450 today. I might be able to get it to do a little above 3.8 for slightly more points. I can use a 9850 in the third system once I get the wireless card, onboard wifi is not something I like.
Right now I only have my one quad going. Trying to sort out why this new mobo i recieved wont boot for me. Had to take my other p5b down to help with parts to trouble shoot. By the end of this weekend I should have 4 rigs back up. I feel so guilty that i have rigs down:shakes:
Don't feel guilty because some of your machines are down...
just get it fixed asap :up:
Speaking of machines down and guilt :rofl:
I blew up not one, but two mobos. Then there was a doa 790i I'm dealing with too. Long story short I'm in rma hell and down to two rigs :shakes: Bright side, at least I have plenty of extra vid cards, cpus, and ram to play with for the time being :ROTF:
I have the QX6700 quad back to consistant daily output...:yepp:
The QX9650 is due back from RMA by the end of next week...:clap:
Then I'll be back to my normal 30K points a day.....:up:
Well my opty 1356 is on its way to being replaced. I really have a feeling its going to clock like a monster, at least an amd monster.
XtremeSystems 5,574,978
YAY! $30 MIMO wireless card. And that's from microcenter no less. Too bad the 9850 only does blend up to 2.9ghz stable.
2.9 or 2.5, whatever it does stable is a plus the way I look at it.
There are people here that can get more out of a machine than I can but we all do what we can and are comfortable with..
To me I'll give up a little on the top end for increased stability.
Tortoise and hare sort of thinking.
A machine that goes down once a week for even 2-3 hours makes less than a slower one that never goes down.
And congrats on the card!:up:
Well, the 9850 will only be in till Tuesday or Wednesday depending on how fast the new 1356 gets here. Just checked newegg and they're shipping me a brand new one. The one I had died on me within 30 minutes because of two bios flashes. 1-3-3-3-11-1T timings are disgusting, and even at 470mhz they get the same bandwidth as 800mhz at like 4-4-4-12, but there's no room to overclock then. I have the issue sorted out now though so it should all be good when it comes in. I flashed to an earlier bios because of the timings, but the cpu didn't even have beta support even though its really just a 9600 with an extra nb multi, but I used the 9500 I had to flash back to the bios it worked on, and then it wouldn't work at all. $400 almost down the tubes in. 30 min.
I just got my q6600 up and crunching ...
Third quad up and running at 2.9ghz. Will have results from it today. I don't have room/enough monitors/AB switches to run more yet. I'd run it on my lappy but it would die being a lowly 1.73ghz pentium-m on a bogged down install of vista ultimate.
I'd love it if someone could do up a guide on how to implement this for us network challenged guys. I have 3 machines (soon to be four) in close proximity and would love to run them headless but I lack the knowledge to set them up on a network and monitor them that way.
I would love a guide also, mainly with Linux Ubuntu. I had everything working except when I would try to log in it said something about the setting where not right so I could not see anything. I had it crunching though with out a video card I just could not see it when try to log into the machine on the local network...
Here are the steps I'm going through right now as I don't think this install of Ubuntu has VNC running:
1. Set the soon-to-be-headless machine's IP to static.
....Click on the 2 computers icon at the top of the screen and then "manual configuration".
....Starting with 8.04, I believe, you have to Unlock the settings screen with the button on the bottom of the window that pops up, enter your admin password.
....Click Wired Connection, then Properties. On Configuration, select "Static IP address", then type an IP in the box, then your subnet mask 255.255.255.0 and type in your gateway's address. Then tell it OK. You now have a fixed IP address you can use to talk to the machine. I, for instance, have the DHCP in my router set up to issue addresses from 192.168.2.2 through 192.168.2.100; I call this machine "q1" so I numbered it 192.168.2.101 so it won't ever have an IP conflict with something that used DHCP to get an address.
2. Config VNC
...Under System, Preferences, click on Remote Desktop
....Click "Allow other users to view your desktop", it looks like it's automatically set to select "allow other users to control your desktop"
....I'm unchecking "When a user tries to view or control your desktop" "Ask you for confirmation" but I'm not checking the box to require a password. I don't think anything from the advanced page is necessary.
3. On your client (we've just set up the server) which will have the monitor when we're through:
....Click on Applications, Internet, Remote Desktop Viewer
....Click Connect, then type the IP address you configured in step 1. You'll note that you have other options for browsing for VNC servers on the network and how you can actually address the machine by name, removing the need to assign an IP address. This is just the way I've always done it. You should now see your other desktop appear. You're free to experiment with screen scaling, etc and you can drive and monitor the other computer as you need.
You can use VNC to reboot; but VNC doesn't start yet if you have to type your username to logon; I have all of my crunchers set to bypass the logon screen so they'll start again after a power outage. Here's how to do that:
....Click on System, Administration, Logon Window. Enter the password
....On the Security tab, click "Enable Automatic Login" and select your username. Close and you don't need to deal with that stuff anymore !
I'm sure there are more elegant solutions, but this is the way I've done it !
I've noticed that this probably isn't the best remote viewer, in the past I'd used UltraVNC (google it) as this doesn't seem to be changing my remote cursor to make it easier to drag window edges, etc. It also doesn't seem to support remote viewing scaled, so you can see the whole screen of the other computer in a window. I don't see ultravnc in the ubuntu repositories, but if you're planning on using a lot of VNC you may want to research other clients.
If you're looking to VNC with Windows, check out ultravnc for your server/client software. You can use it with your mixed Windows/linux network. I don't know what RDP is that's available in some of these things, maybe that's Windows Remote Desktop, I've never really moved on once I got into VNC.
You can always turn the monitor off too. I'm setting up 4 machines in my basement and I'm going to use an old CRT. They'll also be hooked into my network so I can run boincview. That is pretty easy to set up, the only trick is not use more than one router. You can do it, but the routers screw up the addressing - something to do with DHCP I think. I had one router downstream from the main router once and had no problem accessing the internet but couldn't see other machines on the network. If you use one router and then daisy chain switches, that seems to work fine.
Here's a good guide that I used and it work for the couple machines I tried it out on - http://www.broadbandreports.com/forum/remark,15201703
Edit - Or use don's - I must remember to refresh before replying.
Refresh, then reply
Refresh, then reply
Refresh, then reply
you have to turn dhcp off on all the routers but one, to make it work properly.