Thanks for the advice! Acutally I don't use many USB devices, except the IMON. I will try to unplug it, but I'm not sure it will help, since the cam can be moved without any problem by Logitech sw.
Yesterday I tried to uninstall the QC 11.50 and install QC 11.10 instead. It worked quite well after that, but this morning it got stuck again after the PC wake up from standby.
Other thing what I noticed is when the program says "...waiting", I can't close it, neither with Task Manager. If I reboot the machine, then after booting the cam looks like unplugged, neither program recognizes it.
Waiting for further suggestions...

Thanks,
DungT

Hopefully somebody else has some ideas because I don't have anything left except some wild guesses

1) I sort of recall that on one of my systems the 11.50 drivers caused trouble but the 11.10 drivers were okay. Sorry I can't remember the details anymore, at the time it was just one of those "oh, Logitech broke the drivers again, let's go back to the old ones" situations. And yet on my "main" XP box 11.50 is working okay.

2) Standby: I don't let any of my webcam boxes go into standby. Neither the cam drivers nor AbelCam have ever - in my experience - handled coming out of standby. I also disable the screen saver because some versions have had trouble with some screen savers. Not sure if current drivers or AbelCam have screen saver issues or not.

3) VideoCapX.ocx file: if you've been installing and removing experimental AbelCam releases (from the ISSUE TRACKER) for a while, there's a slight chance you have the wrong version - or several different versions - of VideoCapX on you system. There should be only one, and if you check the version (by way of right-click in Explorer) it should be ver. 6.1.0.4223. (strangely, if I check the OCX version from inside AbelCam it reports it as 6.1.0.4222 - not sure why)

DungT, thanks for reporting back. Lots of people don't bother, in which case nobody knows how (if) problems got solved.

That's interesting about how you changed the S3 wake-up settings. I will have to give that a try on one of my systems when I get a chance, since as I mentioned before I've always experienced cam/driver death when the system goes into standby.

Message has been edited, click here to see original content
I seem to have the same problem with 11.5 driver on XP. After some (!) problems with many errors while file capturing now I am not able to start the camera anymore although I didn´t change anything on my system except removing and adding the camera from the list a lot of times. (sphere AF) What I did the last time the cam was usable is: I switched videoserver on in 320x240. After this all worked I wanted to reactivate motion jpeg in 640x480 and after switching off video server I noticed that the resolution in motion jpeg also had changed to 320x240. Changing that back to 640x480 killed the installation kompletely. Removing the cam and adding it again didn't help anymore. (it did before ) After uninstalling everything I wonder which drivers will work at all...

___________________________________

Jörg

That's strange. I have serveral Orbit/Sphere cameras running with AbelCam 24/7 and they work fine. AbelCam 2.3.3 beta on XP, driver 11.7. I have seen the "too many errors" failure before but not for a very long time.

You already tried most of the things I would have suggested to try. You said you plugged the cam directly into the notebook - that is good, because many Orbit problems seem to be the caused by power drop across hubs or long cables.

You might want to try disabling the Quick Cam program that sits in the tray. I don't know why it would cause a conflict with AbelCam but not with WC-2000, but it's worth a try. On my systems I've always used the Drivers Only option when installing from a Logitech CD or download. Perhaps this makes a difference somehow?