Who is running winxp with a 2600k cpu ?

[Markfw]

So I have tried 2 different motherboards, and 2 sets of memory running bigadv units, at stock and overclocked to 4.6 and everywhere in between. I have only completed ONE unit sucessfully. All the rest get "could not allocate memory for arcfile". I have 3 other 950's all with the same OS, and they all work perfectly.

Any advice ?

 

[Rudy Toody]

You stated that:

I just noticed that the GPU unit on that box are on the old ide drive (on a pci card) and the smp was on the sata, so I just moved it to the IDE drive. I will know in 2 hours if that was it (sata bug ??)

fixed an other box. Why not try it for this one?

 

[Markfw]

I have tried IDE and sata both for the smp unit, no difference.

 

[somethingsketchy]

How much memory are you running and what version of XP are you running? 32-bit?

 

[Markfw]

How much memory are you running and what version of XP are you running? 32-bit?

The same version of XP that my 950 boxes are running, 32 bit pro. and 4-6 gig in all cases, but I know 32 bit sees 3.25-3.5 of it.

 

[Rudy Toody]

This is an off-the-wall idea!

Maybe there is an arcfile in the folder that failed to be deleted or renamed at upload time.

The open for output command may be reporting the memory error instead of "I'm not authorized to overwrite an existing file."

 

[GLeeM]

Could it be a file permissions thing?

Or was it first run as a different user or as an Administrator?

Were any folders moved, so that the exe is looking for or looking to write somewhere that isn't there anymore?

 

[Lightflash]

I wish I could help you out Mark, but it sounds like there is a problem with a file still around from a previous install.

Have you tried something besides the main client like F@H v2 Tracker? If not, I would suggest giving it a try just to see if it makes a difference.

Just weird that it would not work considering you have XP on the i7s and they work just fine.

 

[Markfw]

All the boxes run as user administrator, they are all configured the same. The only difference that I can tell, is that the 2600k is SB, and the rest are nehalem. In fact, the install was on a Q6600 , and when I upgrade the box to SB, I installed the motherboard drivers. And t FIRST unit or 2 WORKED. And the box is dedicated as a folder, no other uses, and the 3rd unit or so started getting this error, and ever since.

Damn F@H software.

 

[biodoc]

All the boxes run as user administrator, they are all configured the same. The only difference that I can tell, is that the 2600k is SB, and the rest are nehalem. In fact, the install was on a Q6600 , and when I upgrade the box to SB, I installed the motherboard drivers. And t FIRST unit or 2 WORKED. And the box is dedicated as a folder, no other uses, and the 3rd unit or so started getting this error, and ever since.

Damn F@H software.

Since you've tried swapping drives, MB and RAM, you've narrowed it down to the CPU or OS. You could sell the CPU and get another 950 or if you wanted to keep the 2600K, try linux. If linux doesn't work then you've got a CPU that developed a problem after your 1st or 2nd WU on XP.

 

[rabrittain]

When you said 2600k cpu, I (being ignorant) thought that you were talking about a cpu running at 2.6 GHz. I thought about my 2 FX-60 boxes which have been running for years without a problem, and I was confused. Then I read the post and thought that I should google 2600k cpu - a new i7!! -- sounds like fun.

From reading the post, it sounds like you swapped out the cpu and left the OS intact. I would probably re-install the os. The linux 64 is a good idea!

 

[rabrittain]

From reading the post, it sounds like you swapped out the cpu and left the OS intact. I would probably re-install the os. The linux 64 is a good idea!

I know -- I've quoted myself here. You see . . . , I have to take that statement back. This evening I dropped an AMD Athlon 64 4000+ into a spot that was occupied by an AMD Athlon 64 FX-60 Dual Core a few days ago.

It's running just fine, albeit a little slower and less powerful. It's crunching Edges@Home right now.

All I did was start the computer up. Boot up was a little slower. I have to change the memory clock. Right now it's DDR 320 instead of DDR 400. I made no changes to any configuration, bios -- not anything.

Everything appears to be fine. Go figure. Now I feel a little ashamed for what I said earlier.

Still -- I'm one of those people that reloads the os if there's something going on that just can't be explained in any other way.

What if it does take an hour? . . . , and then sp2 and sp3 -- and all those updates! and reloading all the essential programs that you must have.

Man -- I know it can all be done in a day or two. . . . , and then you would know. I'm not sure what you would know, but YOU WOULD KNOW!!!

you know what I mean man?