<img src="http://cpdn.tuxie.org/uk_nick/CP-boinc/Fortran_error2.png">
Always shows up after 144 timesteps, ie. at the first checkpoint, &amp; execution halts.

CPDN dedicated machine 'Marion': AMD 'Barton' XP at 2.25GHz, 256MB, ATI Rage128, WinME.

I've tried restarting BOINC &amp; she resumes the same model at 0:00 CPU time. I also tried resetting the project but the same error always shows up at the first checkpoint.

I've reverted her to a v2.2.28 classic CPDN model for the moment - she runs those without any problem.

<img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=6&amp;team=off&amp;trans=off">

Hi Nick,

That looks like the same error that Carl posted this about:

<b>The "conout" error message from Fortran would seem to be something on the user's system that is "intercepting" normal "stdout" for fortran (which is actually redirected to stdout_um.txt). So I would think it's some sort of "over-zealous" virus-scanner or other low-level file driver (such as the HP one in their version of Win that someone mentioned).</b>

That would seem to figure with your crash at the first checkpoint, because a message gets written to stdout_um.txt for each scheduler request. Question is what's causing the stdout write to fail?

<a href="http://www.teampicard.net"><img src="http://www.teampicard.net/templates/fisubice/images/phpbb2_logo.jpg"></a><a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=3">Join us here</a>

Hi TL - I'm not running any firewall or anti-virus software on 'Marion' - she's behind my ADSL router with it's incorporated hardwired firewall. Also, apart from Windows updates, it is an almost vanilla WinME installation that has only been used for distributed computing, classic SETI &amp; classic CPDN. I also have an old DOS based R/C helicopter simulator on there that won't run under WinXP but that's about it...

BTW: I checked 'stdout_um.txt' on Alison - it was written when I restarted BOINC &amp; hasn't been written to since, over 12 hours later. 'stdout_um.txt' (and 'stderr_um.txt') <i>is</i> created on 'Marion' when I start BOINC <i>but</i> 'stdout_se.txt' (and 'stderr_se.txt') aren't present at all - I dunno if it's those files causing the problem instead..? Also, there shouldn't be a 'scheduler request' at each 144 timestep checkpoint, that is when the current model state gets written to hard disk - scheduler requests are transmitted at 10,802 timestep intervals AFAIK.

Hmmnnn: One other thing that's just now occurred to me - WinME, as supplied, has a load of device drivers in 'Device Manager' with another driver name in brackets after the originally listed version - I replace all these bracketed drivers with the correct listed version which can be found on the CD, ie.
<img src="http://cpdn.tuxie.org/uk_nick/CP-boinc/WinME_extra_files.png">
'cause they're somewhat faster than the original 'vanilla install' drivers - I wonder if they might affect this problem &amp; if HP did the same thing with their OEM WinME installation as a matter of course too..?

<a href="http://www.nmvs.dsl.pipex.com/"><img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=6&amp;team=off&amp;trans=off"></a>