Posts by Masse

1) Questions and Answers : Getting started : "No hosts are eligible for merging with this one ..." (Message 77333) Posted 27 Jan 2025 by Masse Post: Relating to Microsoft was due to how you responded and you have definitely not provided an answer. At best, guesses. That's weird, if anything ... This is not BOINC related, as this only occur with Milkyway@home. Not at the other projects I'm involved in ... (Astroids@home, PrimeGrid, Einstein@home)
2) Questions and Answers : Getting started : "No hosts are eligible for merging with this one ..." (Message 77331) Posted 26 Jan 2025 by Masse Post: If so, then this issue wouldn't exist, but it does ... Are you working at Microsoft? That would explain your answer ... Incompatible means that it doesn't work. Changing the meaning of words is a bad strategy. When changing the OS and/or the CPU (memory, disks ...), technically it is still the same computer. Valid when I professionally started with computer hardware back in 1986 and still is today. Changing to a completely different motherboard, but keeping the rest, then it is a different computer. I have been saving the BOINC data directory almost since I started with it back in Jan 2004, when I have done any changes to the hardware, like disks or major OS upgrades. Works with Windows 7, Lubuntu 18.04/20.04/22.04, but not with 24.04. In the latest version, all the data is wiped clean, regardless if it is put there before installing BOINC or after. In most of my computers since 10-11 years ago, I keep BOINC data on a separate disk and in Lubuntu, I map the disk into the regular location (/var/lib/boinc-client/). When I was still using Windows, I changed the path in the configuration file of concern. (Learned this the hard way due to all regular Windows crashes ...) If a crash occur, most often due to bad updates, it is a quick procedure with Lubuntu to reinstall everything from scratch and be up and running within 5-10 minutes, depending on the hardware.
3) Questions and Answers : Getting started : "No hosts are eligible for merging with this one ..." (Message 77329) Posted 25 Jan 2025 by Masse Post: Now something happened, as when trying to merge, both mentioned computers are considered as one. Wrong.
4) Questions and Answers : Getting started : "No hosts are eligible for merging with this one ..." (Message 77328) Posted 25 Jan 2025 by Masse Post: I have upgraded CPU's in two of my computers and these are now identified with new computer ID's, obviously. The computer with ID 990896 is a HP ProDesk 400 G4 and the computer with ID 1040565 is a Dell OptiPlex 7060 micro. Replaced i5-8500T with i7-8700T in both. Tried to merge and no problem with the HP, but was refused with the Dell. Got this explanation: "Host 1040565 has an incompatible CPU: (GenuineIntel Intel(R) Core(TM) i7-8700T CPU @ 2.40GHz [Family 6 Model 158 Stepping 10], GenuineIntel Intel(R) Core(TM) i5-8500T CPU @ 2.10GHz [Family 6 Model 158 Stepping 10])" Still, it is the very same computer though and the CPU's of concern are indeed compatible ... (Compare the Family, Model and Stepping codes.) An incompatible CPU would be any one from the 6th and 7th generation or any from 8th and 9th generation with a TDP higher than 35W. (Gen. 6 and 7 CPU's are using the 1151/H4r1 socket, while gen. 8 and 9 are using the 1151-1/H4r2. Both socket versions have the same mechanical spec's, but different electrical spec's. Mixing will fry the CPU and/or the motherboard. If unlucky, there might be problems with the memory modules too.) This is the very same classic issue the Microsoft included in Windows long time ago, when upgrading the CPU. Why? Because they calculated the serial number based on what CPU and motherboard that was used, together with the product key. Eventually, after a number of computer owners complained about suddenly having a invalid license, Microsoft was forced to exclude the CPU in the calculation. Checked the rest of my computers and found that the same issue apply to computer ID's: 994786 & 951917, 896361 & 990997 and 1038906 & 990631. Technically, changing/upgrading OS should not matter either, so there are more examples ...
5) Message boards : Number crunching : Not receiving enough with WUs (Message 70879) Posted 16 Jun 2021 by Masse Post: Have tested it. It only produce a number of GPU calculation errors.
6) Message boards : Number crunching : Not receiving enough with WUs (Message 70878) Posted 15 Jun 2021 by Masse Post: Nice one! A 'quick-and-dirty', like that and are going to try it. Thank you!
7) Message boards : Number crunching : Not receiving enough with WUs (Message 70875) Posted 15 Jun 2021 by Masse Post: The K80(s) will then be waiting a lot, as I normally keep the network shut down at times when I'm not at home or asleep. Sad ... Edit: The K80 is a double GPU card, so it would be 900. The K80 will finish the majority of those in 'no time', as each GPU on the K80 finish every WU (de_modfit_8x_bundle4_4s_south4s_gapfix) in less then one minute.
8) Message boards : Number crunching : Not receiving enough with WUs (Message 70873) Posted 15 Jun 2021 by Masse Post: Got two nVidia K80 (but only one installed yet) about a week ago and have realized that if I shut down the network, I will run out of GPU WUs within 2-3 hours. Have tried to change the values, both in the account settings and in BOINC Manager, but ... It seems that the requested amount is related to the CPU, but not the GPU's. Is this problem related to MW@H or BOINC Manager.? Anyhow, it's sort of a 'nice' problem ...