Hi. I have a compute with the following configuration (MY MESSAGE WILL FOLLOW THE CONFIGURATION INFORMATION FILE TEXT): THIS FILE CONTAINS THE PRESENT CONFIGURATION FOR MY MAIN (DESKTOP) COMPUTER as of: 5-4-08-SUN-@140325h.

I built the present computer from one I received as a gift from a friend. I recently purchased 2-Gig DDR1 (PC3200) rated DDR-400/333/266MHz in 2 1-Gig DDR RAMs (Now a total of 2-Gig) for my ECS (Hsing Tech Enterprise Co., Ltd.) PC400 motherboard M930L (FSB rated @400Mhz) with a 1.5 Gigahertz Intel Pentium 4 processor, and a brand new Coolmax 450-Watt CX-450B system power supply, I have 2 relatively new hard disks: 1)80-Gig 1)120-GIg both fast Maxtor drives, a ATI9550 AGP graphics card with 256Mb DDR RAM on it's card, and a Sound Blaster PCI-512 Sound card. Internet Browsers: MSIExplorer 6.1 and Apple' Safari. Both up to date.

Hi. Now my problem. Your "BOINC 6.2.18_windows_intelx86" caused my computer to crash and I lost access to one of my hard disk partitions. I recovered the disk partition using a drive boot information repair program from the Fix-It Recovery disk created by the VCOM CD containing System Suite, and then running Norton System Works's Norton Disk Doctor. I'm glad I chose not to remove my Windows98SE from my computer, and kept my disks formated as FAT32, and it has saved me from the complete loss that might have been. I think it was the screen saver in the BONC GUI. I don't know for sure, but when the screen saver started I could no longer access my computer, and after REBOOT I could no longer access one of my drive spaces. As noted before I used a BOOT Fixer utility. Then Norton's Norton Disk Doctor. Then all was back to normal. I restarted "BOINC 6.2.18_windows_intelx86" to see if the problem could be repeated. YEP! It happened again. I repeated the repair steps I noted earlier, and then I removed "BOINC 6.2.18_windows_intelx86" to return to "boinc_5.10.28_windows_intelx86.exe". No more problems as yet. Please fix BOINC.

---

Hi. Very nice, very nice indeed, but if the screensaver problem was supposedly caused by an older screensaver file. Then you have a problem. I installed the new BOINC on my computer after I had to replace the operating system due to system failure within Windows XP_SP3. I then completely removed the older BOINC 5.10.30 from my computer before installing the BOINC 6.2.18 after having problems with it. So I should not have had any problems at all if this is what you are saying. Thank You. P.S. In another thread in this site the same type of problem is noted by BOINC. I don't know about the screensaver they are talking about at the end of the message, but I was using the BOINC screensaver I believe for the SETI@home project after the new install of BOINC. The project had to be reset after it failed on first start within the old BOINC. Still the computer crash: Screen Freeze with no access to the system after the screen saver started.
From the other thread (BOINC 6.2.18 release to public for all platforms):
Message 19479 - Posted 14 Aug 2008 7:32:04 UTC
Last modified: 14 Aug 2008 11:33:09 UTC
Before any of you wonder again.... 6.2.16 is showing back as development version and 5.10.45 as recommended version, due to a bug in the graphics application which can cause BOINC/the computer to hang when running Seti - Astropulse as a screen saver. This is both with 6.2 and 6.3

It affects all versions of Windows.

Please fix BOINC.

BOINC version 6.x implements the screensaver differently than BOINC 5.x. The BOINC screensaver is produced by the BOINC project and, as far as I know, it has been updated to 6.x requirements. However, the projects you attach to also send screensavers. Some projects have not updated their screensaver to the 6.x standard. If you tried to run a 5.x screensaver on 6.x then that is most likely your problem. Please check with the projects you are running on that computer and ask them to update their screensaver. Or just turn the screensaver off, it's more trouble than it's worth.

---

I installed the new BOINC on my computer after I had to replace the operating system due to system failure within Windows XP_SP3.

Sounds more like you have a hardware problem. Something with the hard drive controller or the file allocation tables of the hard drive.

Make sure your BIOS is up-to-date. You can find the last one here
This BIOS update supports all M930L PCBs: v1.5 \ v5.1\ v5.1a
Make sure your chipset drivers are up to date.
Make sure your DirectX 9.0c is up to date.

Now the funny thing about your purchase of the memory is... it's overrated. The memory on that motherboard will at maximum run at 333MHz. Yes, PC3200 RAM will clock back, but you could just as well have bought PC2700 RAM.

---