FaD Beta 1.24d out!

[scoser]

Looks like the newest Find-a-Drug beta is out and has installed smoothly on my 3 main computers. It appears to do the CPU rating benchmark much more often and the steps between CPU rating points are smaller as well (ie: instead of 140/164, I'm getting 140/157/164/171/178 depending on proc. usage by other programs). THINK said he will be looking into seeing if this helps out the points variability between the same jobs run on different machines and will report back to us with his results.

1.24d changes

1.24d beta thread on the official FaD forum

 

[Ross Whitehead]

Thanx for the heads up.

 

[BCinSC]

Mine haven't updated yet - still 1.24c.

What do you think of this?
15-JUL-04 09:35 Completed : j287-1uou-q1.log Hits 13 from 9800 of m5369 in 61005.1s for 1uou-q1 2759 points to 4004561
15-JUL-04 09:35 Uploading to www.treweren.com
15-JUL-04 09:35 Failed on r287.smi with -3
15-JUL-04 09:35 Uploading to www.find-a-drug.net
15-JUL-04 09:35 1 jobs uploaded

 

[scoser]

It should update the next time you download a job, if you have the beta option set. I think treweren.com was having a little trouble this morning, according to a couple of people. I know I had to hit receive a couple of times before one of my machines triggered the beta download.

 

[Ross Whitehead]

5 of my machines upgraded fine... two automatically, three I had to hit receive once on each.

 

[mondobyte]

I'm not very impressed by what I see.

Seems Keith & company have decided to hide the CPU rating rather than actually fix it.

 

[sduguid]

I installed FaD on an Athlon 64 3000+ and the cpu rating seems to have settled at 167, whereas on an Athlon XP 2400+ it is at 187. Do these sound right?

 

[dringdahl]

Originally posted by: mondobyte
I'm not very impressed by what I see.

Seems Keith & company have decided to hide the CPU rating rather than actually fix it.

Yea I agree... Just sweep the problem under the rug instead of fixing it, and showing the userbase the solutions.

 

[Ross Whitehead]

Originally posted by: mondobyte
I'm not very impressed by what I see.

Seems Keith & company have decided to hide the CPU rating rather than actually fix it.

I am not sure I understand. If you look at Job Info it shows you the CPU Rating. Is/Was there another place which I did not know about where you could fin CPU Rating?

 

[dringdahl]

On a Linux box, with out graphics, you cant see the cpu rating anymore. It used to be in the tlg files for each of the nodes.

Obviously to me that is a big problem, most of my computing is on a linux cluster.

 

[Ross Whitehead]

I hope this is an oversight on their part and they will make it available again in the tlg

 

[Slapstick]

Well the beta got pushed out to the few networked PC I have trying FAD and really FUBAR'ed the works. I have an old Win98 PC controlling the queue that is located on a Novell server. With the latest beta the Win98 pc can't controll the queue or start the client. I may try uninstalling and reinstalling but I was hoping to find a project that didn't require a lot of admin. Oh well if I can't get this straightened out then off to the DC heaven for this one.

 

[Freewolf]

Originally posted by: Slapstick
Well the beta got pushed out to the few networked PC I have trying FAD and really FUBAR'ed the works. I have an old Win98 PC controlling the queue that is located on a Novell server. With the latest beta the Win98 pc can't controll the queue or start the client. I may try uninstalling and reinstalling but I was hoping to find a project that didn't require a lot of admin. Oh well if I can't get this straightened out then off to the DC heaven for this one.

That's not good news for me either.

 

[Slapstick]

Keeping my fingers crossed. It appears to be up and running again. I had to uninstall it from the Win98 PC, delete the directory off the server, run regedit to clear out the "find-A-drug" entries from the Win98 PC and then reinstall. Let the client update before restarting the other PC's. Luckily I have it running on only 4 networked PC at the moment or this had the potential to be a real pain. I hope this isn't a common occurance everytime the client updates itself.

 

[scoser]

Well, 1.24d is a beta client (1.23c is a release client), so you might want to turn off the beta option on your installations and then it will only download release clients. This should help out your stability as there are already a ton of people that have the time, effort, and willingness to test out the betas on their 40 PC w/ queue server setup so that it should work fine on yours when the new release client comes out.

I know I turn off the beta option on my remotes and they all seem to work well when the release candidates come out.

 

[Slapstick]

I have the beta option turned off now, the client accessed before I could change the setting, after it was done updating it then allowed me uncheck the beta option. Oh well it's working now.

 

[PlumUgly]

Hello ya'll !! thought I'd drop in and see what's up. I've updated all mine to the beta program. The only thiing I seen is it seems to have lowered the cpu scores on all of mine, Amd and P4's. that and not seeing the tlg scores makes it harder to keep track of things. Nothing has crashed yet(keeping my fingers crossed)