I use WinXP-pro SP3 and the new Whatpulse version 1.6 is working fine on my PC.
My husband uses XP-Home-SP3. The installation of Whatpulse went without any problems but when he tries to pulse there is only a green dot in his systray. The pulse is not send.
He removed Whatpulse 1.6 and installed it again but that did not help. A reboot did not correct the problem either.
We are on the same router and using the same settings for our internetconnection. We use a wired network (UTP to router).
He now reinstalled version 1.5 again and everything workes fine again.
True, but I go on the assumption that if their connecting to the internet (being able to post here) port 80 cant be blocked. But then again your same argument applies, who knows how these crazy network things work with their mad protocals, TCP handshakes and such
My port 80 is not blocked in router or PC’s. That can’t be the problem because whatpulse works fine op my XP-Pro-sp3 PC and I’m typing this message on this connection on my Vista laptop.
I can log off and log again So there is connection to the whatpulse server but when I pulse I still see that persistant green dot and I have to shut Whatpulse down using the taskmanager because nothing works anymore. When I start whatpulse again the generated keys are gone and not added to my account. Still the same problem op XP-Home-sp3 and Vista Premium.
We have a firewall in our router and use the windows firewall for extra on our PC’s.
Even with the windows firewall off I can’t pulse using version 1.6. Using version 1.5 gives no problem at all.
I have the same problem I tried the following things (Vista x64 SP1):
deactivating the windows firewall => doesnt help
starting without skype, because skype may use port 80
Disable Skype from Using, Opening and Listening on Port 80 and 443 on Local Computer (mydigitallife.info/2008/12/03/disable-skype-from-using-opening-and-listening-on-port-80-and-443-on-local-computer/) => without success…
In version 1.5 was a failure message if pulsing didn’t work. After confirming the message, it was possible to chance the settings. But now, when the green dot shows up whatpulse doesn’t react on clicking. So you only can stop it by killing the process or restarting the computer. Maybe you can also fix this issue, to have control if pulsing doesn’t work…
Three more bugs left: Milage (most important), pulse timers and invalid tokens on failed pulse (green dot hanging).
Really want to get them all fixed before anything is released, don’t know how long that will be though. Every time I the bug count down to 1, I get 5 more thrown at me