Core_b4.fah will not v3Decompress

[19Grumpah42]

One of my Fah tasks on this PC will not restart (after an unfortunate kill), the other 3 are fine.
It is a virtual Win98SE, same as another v98SE (Folding@home Client Version 4.00, using FahCore_78.exe). It downloads this core (Core_b4.fah, 5,049 KB) and then....

[03:46:14] Verifying core Core_b4.fah...
[03:46:14] Signature is VALID
[03:46:14]
[03:46:14] Trying to unzip core FahCore_b4.exe
[03:47:03] UnzipCore: Couldn't v3Decompress
[03:47:03] + Error: Could not extract core
[03:47:03] + Core download error (#5), waiting before retry...

It has retried 7 times now.

Any ideas on how I could fix this. Thanks
--Grahame

[bruce]

It has been a while since I've done anything with V4 and Win98SE, but I do know that there were several problems which seem to have been related to its inability to allocate enough memory to properly unzip some cores. I'm not sure if anybody has tested FahCore_b4 on the V4 client or WIn98 but I'll ask around.

[Ravage7779]

Why virtual? Native would seem much simpler to deal with?

[bruce]

If you're using the -advmethods flag, remove it. I'm not sure if that will help, but it might. I'm working on getting a more permanent solution.

You'll need to delete the WORK directory and queue.dat until the server stops reassigning that project.

[19Grumpah42]

Thanks for the prompt replies, everyone.
I cleared out ../work and re-ran Fah, but it just starts up with the same Core_b4.fah and encounters the same failure. According to MemTurbo, my free RAM assignment does not drop below 57 MB during the failed unpacking.
I have been using two v98SE machines on this WinXPpro host for over 6 months and they have been rock solid, as is the other v98SE machine right now, running FahCore_78.exe
I do not use any startup flags, the shortcut is simply to "..\Folding@Home\winFAH.exe"
Is there any way I could tell this instance to <not> use a V4 core project?
--Grahame

[bruce]

The server can be configured to not send B4 projects to V4 clients, but the project owner has to do that. That's what I meant when I said I was working on a more permanent solution.

[19Grumpah42]

Thanks Bruce, that's magic. Best of luck.
--Grahame

[19Grumpah42]

Just in case it's of any help, the currently active but unfortunate job is ...

"Folding@Home" (b4) 129.74.85.48:8080

--Grahame

[bruce]

Just in case it's of any help, the currently active but unfortunate job is ...

"Folding@Home" (b4) 129.74.85.48:8080

--Grahame

No, 129.74.85.48 is the server that's issuing the WU. You won't see the Project/Run/Clone/Gen numbers in FAHlog unless FahCore_b4 actually runs. You may be able to find out that information if you start the client with the -queueinfo flag, but we really don't need to know the active WU.

[19Grumpah42]

Thanks Bruce, I remain your faithful servant in all domestic folding matters.
I have [Exited] the instance which was trying to run the b4.
--Grahame