I recently installed the Windows version of BOINC on Windows 7 64-bit machine which already had Oracle Virtualbox on it. I normally run boinc on my Linux machines, but am forced to keep this machine on Windows for a while. Whenever I add climateprediction project to this machine I have about a dozen or so error dialogs in the morning saying it cannot find msvcr100.dll. There are many copies of this in various locations on my machine.

C:\>dir /s msvcr100.dll
Volume in drive C has no label.
Volume Serial Number is 36B8-9396

Directory of C:\Program Files\BOINC

02/19/2011 12:52 AM 829,264 msvcr100.dll
1 File(s) 829,264 bytes

Directory of C:\Program Files\Oracle\VirtualBox

07/10/2015 01:21 PM 836,256 msvcr100.dll
1 File(s) 836,256 bytes

Directory of C:\Program Files\Oracle\VirtualBox\x86

07/10/2015 01:21 PM 836,256 msvcr100.dll
1 File(s) 836,256 bytes

Directory of C:\Program Files (x86)\Hewlett-Packard\HP Support Framework\Resour
ces\HPPSdr

01/30/2014 09:14 AM 770,384 msvcr100.dll
1 File(s) 770,384 bytes

Directory of C:\Program Files (x86)\Java\jre1.8.0_51\bin

07/17/2015 08:52 AM 773,968 msvcr100.dll
1 File(s) 773,968 bytes

Directory of C:\Program Files (x86)\Java\jre1.8.0_51\bin\plugin2

07/17/2015 08:52 AM 773,968 msvcr100.dll
1 File(s) 773,968 bytes

Directory of C:\Windows\System32

03/18/2010 09:36 AM 827,728 msvcr100.dll
1 File(s) 827,728 bytes

Total Files Listed:
7 File(s) 5,647,824 bytes
0 Dir(s) 460,096,380,928 bytes free

C:\>

Where does it need to be for climateprediction to find?

That is a Microsoft file.
Do a web search of the full name, and you'll get lots of responses, including how to fix it.

I _did_ do a Web search AND I pulled the file down from Microsoft AND installed yet another version in yet another place BEFORE I came here.

Apparently all Windows dll files are supposed to be in C:\Windows\System32.

And according to several web site pages, you need to run a Windows command after you install it.

This one is probably the simplest: Install a .DLL file in Windows

And this one is longer: How to install a .dll file with DLL-files Fixer

I _did_ do a Web search AND I pulled the file down from Microsoft AND installed yet another version in yet another place BEFORE I came here.

Still no viable answers. Was this ever tested with 64-bit Windows 7?

If you look at my directory listing which was also posted:

Directory of C:\Windows\System32

03/18/2010 09:36 AM 827,728 msvcr100.dll
1 File(s) 827,728 bytes

Apparently all Windows dll files are supposed to be in C:\Windows\System32.

And according to several web site pages, you need to run a Windows command after you install it.

This one is probably the simplest: Install a .DLL file in Windows

And this one is longer: How to install a .dll file with DLL-files Fixer

This forum seems to sort messages in an odd order. As the directory listing I posted in this thread indicates:

Directory of C:\Windows\System32

03/18/2010 09:36 AM 827,728 msvcr100.dll
1 File(s) 827,728 bytes


Still no love. This is Windows 7 64-bit.

I've been doing software development for 30+ years, but I work on real computers with real operating systems which rules Windows out. I have this machine right now because I have/had a client with the most incompetent networking department ever encountered during my career. If any machine which wasn't running Windows loaded a virtual machine on their network it was kicked off. It was fine to have the 8-lane wide security breach known as Windows doing it, but, no secured OS could be allowed to do that. Since I have to keep this machine around for remote support through the end of the year, I wanted to have it run BOINC projects. Now that I __finally__ have a usable off-peak data allowance from my satellite provider, I can once again let climate prediction run on my machines.

So far, ever time I enable/join climate prediction with this machine, the packets all fail looking for this DLL. As the directory listing posted in this thread shows, that file exists in 7 locations on the machine. This acts like climateprediction.net is linked with a physical path rather than relying on the OS default search path.

Oh, I wonder if this is it:

C:\>dir /s msvcr100.dll
Volume in drive C has no label.
Volume Serial Number is 36B8-9396

Directory of C:\Program Files\BOINC

02/19/2011 12:52 AM 829,264 msvcr100.dll
1 File(s) 829,264 bytes

Directory of C:\Program Files (x86)\Hewlett-Packard\HP Support Framework\Resour
ces\HPPSdr

01/30/2014 09:14 AM 770,384 msvcr100.dll
1 File(s) 770,384 bytes

Directory of C:\Program Files (x86)\Java\jre1.8.0_51\bin

07/17/2015 08:52 AM 773,968 msvcr100.dll
1 File(s) 773,968 bytes


Directory of C:\Windows\System32

03/18/2010 09:36 AM 827,728 msvcr100.dll
1 File(s) 827,728 bytes


Both the one in BOINC and the one in the System32 folder are viciously out of date. I will try copying the newest one from HP to all locations. Not certain I should use the one from Java.

Both BOINC and the cpdn programs have been running successfully on both Win 7 and Win 10 for a number of people.
There's apparently thousands of computers that are or have run all Windows versions from XP through to 10, accumulating large amounts of credits. The latter would indicate that at least some were running OK.
Although there's no break down between 32 and 64 bit systems.

I've been building my own computers for years, and if I did get that much of a problem back when I was using Windows, I'd probably clean the disk and start from scratch. Which may not be an option in your case.

Now that I'm running Linux, I've found that there's a very nice option in the installer, which goes something like: Delete everything from the hard disk and install Linux Mint by itself? And the Desktop and Menu look very similar to Windows XP.

As this entire forum is visited by whichever volunteers feel inclined to do so, and then mainly for cpdn matters, there may not be many who will know the technical details of fixing OS problems of any of the 3 types.

Roland:

The version of the run-time library you report is the same as on my 64-bit Windows 10 machine (which was a Windows 7 upgrade), so it isn't a version problem:

Directory of C:\Program Files\BOINC

19/02/2011 00:52 829,264 msvcr100.dll
1 File(s) 829,264 bytes

Moreover, the Sysinternals Process Explorer confirms that the BOINC executable on my machine is indeed loading the local copy of the library dynamically from "C:\Program Files\BOINC" as expected. So there's no question of a static link - and in any case your installation appears to be to the default location. It's also not obvious to me that, even if the problem only manifests itself when CPDN is running, the problem necessarily comes from CPDN.

The first thing to do is to re-install BOINC: suspend any running projects, uninstall BOINC and reinstall it; re-boot for good measure; resume the projects and see whether the problem persists. If so then make sure the folder is excluded from any virus checker and if that doesn't help then report back here ...

@Iain @Les,

Thank you both for your responses. The problem is indeed the viciously old version of the DLL. I copied the one from Oracle VirtualBox (which was much much newer), turned climateprediction back on in BOINC, and this morning I see tasks which have gotten roughly 5% complete before my logging in here made them suspend to wait for idle time.

There may well be many hundreds of computers running climateprediction on this very crummy OS as at least one of you has indicated. Yes, for my personal machines I run Mint 17 as well, usually KDE so I can have both KATE and KWrite, but this machine must remain as is at least until January.

One of the many many many many things I've always hated about Windows, which hasn't changed from Windows 3.1 (which was NOT an operating system, just a task switching GUI running on top of DOS) is this very DLL problem. It has gotten exponentially worse with Microsoft's creation of Visually Impaired Studio and "redistributable" portions of the tools.

I spoke too soon. While transporting the combine home from the repair shop, these jobs all errored out. Missing msvcr100.dll. Actually, that is not quite true. I had about 20 error windows to close, but BOINC manager says the jobs are still active.

Will write more in a bit.

The real problem here is that Windows error dialogs would have to improve by biblical proportions to achieve a level universally described as "useless". The dialog isn't showing the manifest values, just saying it cannot find the dll. It may well be finding the dll, but the manifest doesn't match (i.e. needs version 4.3.2 but found 1.2.3)

Most annoying one can get this error dialog and have the job continue. Definite improvement though! Previously when the dialog appeared the tasks all aborted. I am definitely on the correct track.

Will write more soon. Have to get heads switched on combines and such so we are ready for harvest as soon as it dries outside.

I copied msvcp100.dll from Oracle VirtualBox and did a search for rest of DLL files found in BOINC directory. Will know in a bit after rebooting if this fixes the problem.

Been burned by this soooo many times in the past. Acronis (sp?) used to be notorious for this back in the day. They would build with a very old version of the redistributable stuff and it would break any machine which had updates applied or something newer installed. MS regularly releases incompatible versions of the redistributable stuff due to bugs or security breaches they fix.

This machine is not a hand built white-box. It is an HP SlimLine/Low Profile desktop which used to be the corporate standard desktop. As such it has that HP Update Assistant and other things running which keep the system "current."

The problem with bundling the redistributable stuff with an executable package is so much of the underlying OS libraries cannot be bundled. When a non-backwardly compatible version of one of _those_ files gets installed in the "Windows says it must go here" directory, other things break.

Looking forward to getting back to working on OpenVMS where problems like these simply don't happen.

Roland, you might want to hold back on the rhetoric. As a Microsoft C++ developer of many decades, I'll make my own judgment about how well informed your comments are, so no offence taken on my part. However, as a moderator, I am obliged to object to your invocation of "visually impaired" as an insult - it isn't clever or funny. The world would indeed be a better place if people took offence less easily, but in the meantime we can at least stop those who would needlessly cause offence.

I was aiming for accuracy, not offense. It was _never_ a good IDE and calling the package "visual" was the pinnacle of audacity. There were much better IDEs at the time it was created (in truth the DOS based one it replaced stood full torso above the GUI one forced on developers) and there are many many much better IDEs out there now.

Perhaps you weren't there when we had to purchase Nu-Mega Bounds Checker because the debugger impaired a developers ability to debug? Code Warrior, Blinker, Periscope Debugger and a rash of other tools were dragged to market by developers weary of being completely impaired by the tools they currently had. Many of those tools moved off into the embedded systems world where quality mattered.

At any rate

Java 8 was in the search path ahead of Windows\System32. I no longer needed Java because we were no longer using jEdit in the project, so I removed and rebooted then let sit idle. Same problem with dialogs popping up.

At this point I punt. I removed ClimatePrediction from this machine. It can still run on the two Mint machines over in the corner, but I'm not investing any more into making it work on this machine. I quit using Windows years ago because it _always_ has problems like this. Some time in January the remote support part of the contract will be over and so will the life of Windows on this machine.

Roland

This project has a few children running models, possibly because their parents do. Occasionally one of them posts here.

So we have a strict policy of child friendly posts, and one of the main duties of moderators is to remove offensive posts.
For serious offenders, which we haven't had for years, there's a mechanism to ban posters for varying periods; I think it's one week, two weeks, and permanently.

If Linux is so superior to Windows then why can�t the Linux computers finish those 16,000+ hadam3prm3pm2t_eu tasks that have been sitting and waiting for about 5 months now. The Windows work gets snapped up and returned promptly.

---

Lots of Linux computers these days are 64 bit, and the owner hasn't installed a certain necessary 32 bit library. And also hasn't bothered to look at their Tasks page, which would show them that everything is failing.

I can understand Windows users not knowing how to sort out the more esoteric problems as most just want a computer to do what they bought it for and have the OS installed for them etc.

When as far as I can tell, the vast majority of Linux users have to at least be able to install the OS themselves, the run and forget mentality makes rather less sense.

Having been windows free since 2,000 I have to resort to google, nearly every time someone asks me for help with an M$ problem.

I am running CPDN on s 64-bit CPU and a 32-bit Linux OS.The last model I was running errored out after a long period (1,632,286.00 s). Now I am running another one and hope it goes well. I have also a Windows 10 PC running 4 CERN projects with Virtual Box, but it has the bad habit of rebooting for unknown reasons (it has a 20 GB RAM), not only when needed for OS updates. I asked Microsoft to notify before making a reboot so I can suspend the CERN tasks. It would not be a good CPDN cruncher. The Linux box never reboots except on electric blackouts.
Tullio

---

Vast majority of home Linux users appear to be "distro hoppers". They load a flavor of Linux, try it for a while, then move onto the next. Many don't think to let BOINC clear out before performing a fresh Linux install.

Ubuntu has new releases approximately every 6 months. 16.04 will come out the 4th month of 2016 and will be the new LTS (Long Term Support) version. Mint and the other YABU (Yet Another uBUntu) distros will follow with new releases shortly after each Ubuntu release. Don't remember what OpenSuSE and the other RPM based distro release cycles are.

On Windows platforms LibreOffice, FireFox, Thunderbird, and many other programs update independently from Windows. A Windows user with a machine which manages to stay up, can keep current on the latest application updates without installing a new OS.

When it comes to most Linux distros, you have to know how to hack a PPA into your source lists if you want to remain current on an application. Most Linux users either don't know how to do it or don't care to. Why should they? In less than 6 months a shiny new release will be out. They can boot the ISO, answer a few questions and have all of the latest stuff.

Most of my BOINC machines tend to be spares I put old hardware (like drives) into just to keep running so they don't end up with that mysterious sat-on-shelf-for-months-now-won't-boot syndrome. That is not the case with 2 of the machines right now, however. Ordinarily, I turn off all new work and let the machines clean out over the course of a few days before putting on a fresh distro...unless an old hard drive finally gives out.

Open SuSE send me regularly its updated both on 13.1 on this host, a SUN WS vintage 2008, and 13.2 on my HP laptop, vintage 2012. It is my choice whether to instyall them. Now I am waiting foe the next SuSE release, Leap 42.1, due in November. I shall put it as a Virtual Machine on my Windows 10 host with 20 GB RAM, where 4 CERN projects already run as Virtual Machines.
Tullio

---