I'd like to once again thank Notfred for all of his hard work on creating the Diskless folding client. However the corestatus = ff (255) is just killing me. I lost a day's worth of folding...It was at 90% or something. I have now changed the VMware so that it suspends instead of powering off every time I press close. I have included the FahLog as well. I have no idea what's going on with the client. I can tell you that the computer was turned off last night because my sister shuts it down every time she goes to sleep.

Warning: By using the -forceasm flag, you are overriding safeguards in the program. If you did not intend to do this, please restart the program without -forceasm. If work units are not completing fully (and particularly if your machine is overclocked), then please discontinue use of the flag.

Hmm that's not a code at the FahWiki http://fahwiki.net/index.php/CoreStatus_codes so I'm not sure if it's something my code is doing or whether you just got unlucky with a bad WU from Stanford. Did this just happen the once or does it happen repeatedly?

notfred wrote:Hmm that's not a code at the FahWiki http://fahwiki.net/index.php/CoreStatus_codes so I'm not sure if it's something my code is doing or whether you just got unlucky with a bad WU from Stanford. Did this just happen the once or does it happen repeatedly?

Happens a lot of times. We turn our computers off at night because of personal reasons such as sleep and stuff, and half the time we power it back up, I get some sort of error, like the Corestatus = ff (255). I've had this error a couple times and have lost a lot of WU already. As of now, I changed the VMware client so that it suspends instead of shuts down, but I'm still worried bout the client because now I have no idea what's going on in the FahLog.

I've posted like in a couple places, and I think might've reposted somewhere but I don't remember where. No one's replying to my latest thread that I made at Hardware Canucks and EVGA either.

I've got some sites here that might be of help...There might be more...

Your error is not with notfred's software, it's almost certainly with your VMware setup.

When you're asking for help, it's a good idea to include as much useful information as possible, including your system's components (including CPU, RAM, & motherboard), their particular configuration including overclocking if applicable, and the operating system.

I've never had a problem with VMware in XP Pro, but others have had problems in other Windows operating systems, at least until they learned how to do certain things. Though I've never set my system to automatically suspend, I do manually suspend the Linux Virtual Machine I run before shutting down Windows.

Since we don't know anything about you, we do not know your level of knowledge, and can't respond as effectively without it. Further, your terminology, using the words, "I have now changed the VMware so that it suspends instead of powering off every time I press close." raises some flags with me. What do you mean by "press[ing] close" ? VMware has the option of automatically suspending as mentioned, but you have to wait a while for it to complete that suspension, and if you force it to kill VMware with "End task" or something, you're likely to have problems. But I'm just speculating. More information from you is required to get anywhere.

Ragnar Dan wrote:Your error is not with notfred's software, it's almost certainly with your VMware setup.

When you're asking for help, it's a good idea to include as much useful information as possible, including your system's components (including CPU, RAM, & motherboard), their particular configuration including overclocking if applicable, and the operating system.

I've never had a problem with VMware in XP Pro, but others have had problems in other Windows operating systems, at least until they learned how to do certain things. Though I've never set my system to automatically suspend, I do manually suspend the Linux Virtual Machine I run before shutting down Windows.

Since we don't know anything about you, we do not know your level of knowledge, and can't respond as effectively without it. Further, your terminology, using the words, "I have now changed the VMware so that it suspends instead of powering off every time I press close." raises some flags with me. What do you mean by "press[ing] close" ? VMware has the option of automatically suspending as mentioned, but you have to wait a while for it to complete that suspension, and if you force it to kill VMware with "End task" or something, you're likely to have problems. But I'm just speculating. More information from you is required to get anywhere.

System is a AMD Athlon 64 X2 @ 2.65Ghz with 2GB RAM on an ASUS M2N-E. The overclock is stable. We're using Windows XP Pro 32 bit SP3 and the latest version of VMware Player that can be obtained at the VMware site.

In the VMware client, there's an option under "Preferences" (not sure if it's Preferences since I have no access to computer atm) that you can choose where you close the VMware client, you can either suspend the virtual machine, or you can close the virtual machine completely. I have it set to close the virtual machine completely right now since I removed the old Notfred client and replaced it with the latest one available.

When we turn off the computer, we close the VMware client first because if you don't close the VMware client, then you're not allowed to turn off the computer. The client is not closed via Task Manager, but it is closed by pressing the "X" button at the top.

Well, I haven't read EVGA's guide, and since notfred's home is here, I doubt they have anything that isn't more or less a commonplace on this forum for users of his setup.

I have begun using VMware Player lately, though, and have had a couple of system shutdowns and crashes for various reasons. I'm using a USB-based flash drive on that system, though, and it has no problem restoring its previous state and starting again fine. I'm not using the Virtual Appliance, so that may be enough of a difference to make it inapplicable, but the setup I generated from the EasyVMX.com site worked well for me, and that's enough to keep me happy.