• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Something wrong with notfred...

M

Mr. Pedantic

[H]ard|Gawd
Joined
Sep 19, 2009
Messages
1,707
My specs:

Core i7 920 @ 3.6GHz
6GB G.Skill DDR3-1333
MSI Eclipse mobo
XFX HD4870 512MB

I set up 4 instances of VMWare player with notfred to fold about a week ago. Apart from the fact that I used to run out of memory, it was all good (I run 32-bit XP...). And then, for some reason it started playing up. Task manager showed each VM was still eating up 2 cores' worth of CPU resource, and I got the same slowdowns and jerky performance as I used to because of the memory usage, but I could no longer monitor the clients. I have both Fahmon and Fahspy on my computer (both have their advantages, and I like to have both on hand), but neither could monitor the clients; FAHSpy said "no access" and Fahmon "something is wrong with this client". Nor could I see the VM in my internet browser, whereas a day before all 3 methods worked perfectly fine. And all in spite of the fact that VMWare player keeps saying the IP addresses are the same as they always were.

I reinstalled VMWare, set up notfreds again, no luck. I saw that there was a new version of VMWare that supported 4 CPUs, so I downloaded, installed, and ran that, no luck either.

Could anyone give me some help about this?

Thanks
 
I would say uninstall everything. Since youve got 8 cores to work with, setting up 2 "4 core" VM's will help you considerbly with the RAM issue. Give each one 1 Gig and your set. Start fresh with the new Player, follow the guide to the T (well, except everywhere that says 2 core, think 4 core)

Since you were kinda short on RAM being XP and all, I'm guessing that the VM's were unstable and hit a never ending loop of .. well, shit, its been awhile but there is an error that happens alot if you dont give them enough RAM. Also, usualy when you have a notfreds error, its not the Player thats screwed up, its the notfreds file

I'd also suggest you delete your version of notfreds and start fresh. I've had a similar issue on a VM, although 1, not 4. I deleted everything and started anew

Also, about monitoring, not sure about FahSpy, but for FAHMon, check the box that says client is a VM when you add it (its at the bottom) and also in the preferences check the ignore async clocks to make sure you can view them. If not, FAHMon will report the thing as not running because the times dont match up
 
Still nothing. Uninstalled VMware, deleted the VMs, reinstalled VMware, unzipped notfreds, set it all up again, still nothing. I checked the files I downloaded with md5 against a new set I just downloaded, and they're exactly the same, no corruption or anything. Same problem. Full processor usage, but I can't access the VM with IP, or with Fahmon/Fahspy, even with the ignore async clocks option.

Maybe there's something wrong with the .vmx file?
 
Can you see the clients when you type the VM's IP address into a web browser?
 
No. The little circle in the tab just keeps going round and round, as if (shock horror) the IP address didn't exist or wasn't assigned.
 
long shot, but are you at work? firewall problems?
 
No, I'm at home. No uni today.

I haven't changed anything in the firewall, so...but I'm no good with the firewall, so what am I supposed to see?

EDIT: No, even if I turn the firewall off I still can't see the client, either in IP or in FAHmon/FAHspy.
 
if your at home it wont be an issue, just maybe at work

like I said, longshot. VM's arent my area, but I'll look around see if I can find anything like what your experienceing

ack, spelling lol
 
you need to mess with the network settings for the VM's.. because you reinstalled VMware it went back to the default settings.. try messing with the different ones.. try with the network bridged.. unbridged.. crap like that.. took me for ever to get mine working ages ago.. but i havent run the notfred client in probably 5 months so i cant remember all the various settings..
 
Ah. Ok. I got it. I had to change the "bridged" thing to "nat", and then it all works fine. I get a slightly random IP address, but I actually have a proper hostname now, and it all works. Thanks for the help, guys.
 
I'll have to take a look at my system as I'm pretty close to your specs: running an i7-920 w/6 gigs of RAM. My setup is VMWare workstation 6.something with 2 instances of notFred, 4 cores each.
 
Mr. Pedantic said:
Ah. Ok. I got it. I had to change the "bridged" thing to "nat", and then it all works fine. I get a slightly random IP address, but I actually have a proper hostname now, and it all works. Thanks for the help, guys.
Click to expand...

That's weird as I have mine set to bridged. I guess it's whatever works.
 
tjmagneto said:
That's weird as I have mine set to bridged. I guess it's whatever works.
Click to expand...

It probably depends on your physical network setup. I need to set mind to NAT, otherwise it doesn't work.

Bridged shares the current physical card, iirc.
 
Sometimes Bridged works, and sometimes NAT works. It's luck of the draw. As far as I've seen, there's no pattern to determine which option will work on which PC. I've even had Bridged stop working on a PC and NAT started working instead.
 
Zero82z said:
Sometimes Bridged works, and sometimes NAT works. It's luck of the draw. As far as I've seen, there's no pattern to determine which option will work on which PC. I've even had Bridged stop working on a PC and NAT started working instead.
Click to expand...

you had one stop working!?

I really don't get most of this networking setup business. Why cannot it just work?
 
Sorry I am late to the show. My work schedule doesn't allow me to visit as much as I used to.

I tried to read the entire thread, but it is late and I have to get up in 5 hours :(

If you are on wireless, NAT may be the only way to go as VMWare doesn't always work with Bridged. The only issue with NAT is that it is a little difficult (not impossible) to see the VMs from other machines. Basically you can monitor locally, but it isn't as easy to monitor from a different box.

Given that you have 6GB of RAM, you really need to consider moving to an x64 OS. In essence half the money spent on RAM is wasted as you can't use it.

I've not played with the latest version of Player, but will definitely be taking a look at it next weekend when I am home for more than 48 hours. I am currently running workstation, but frankly there is a lot of overhead with that and these are dedicated boxen and the reduced RAM overhead would be good.

 
Zero82z said:
Sometimes Bridged works, and sometimes NAT works. It's luck of the draw. As far as I've seen, there's no pattern to determine which option will work on which PC. I've even had Bridged stop working on a PC and NAT started working instead.
Click to expand...


yeah i had the same problem as well.. first setup vmware i had to set it to bridged.. restarted the VM and then it forced me to set it to NAT.. vm crashed a few days later because of other reasons im to lazy to say.. and then i had to go back to bridged.. completely random.. while at the same time vmware ran flawlessly on my x2 6400+ system with it set on bridged and never had a single issue with it even after restarting the vm 3-4 times..
 
You must log in or register to reply here.
Back
Top