The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Acer 5610 Orbi Cam Problems

    Discussion in 'Acer' started by skyegurl05, Sep 21, 2007.

  1. skyegurl05

    skyegurl05 Newbie

    Reputations:
    0
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    5
    Hi, I've had my 5610 for about a month and a half now, and my Orbi Cam has worked perfectly fine up til now. I can use the webcam with MSN, or Yahoo, and it works fine, except if I try to adjust the settings (from the chat engines themselves OR just my Orbi Cam application) it crashes. That gets in the way, but I'm not so much worried about that, as now, for some reason anytime I want to open Orbi Cam by itself, to take a picture... Just trying to open it makes it crash. I have Vista, so it comes up with the option of letting windows find the problem, or closing the program. I've tried both, but Windows does absolutely nothing when I try that option. Does anyone know what I can do to fix the application crashing?? :(
     
  2. hoggie

    hoggie old boy

    Reputations:
    316
    Messages:
    1,627
    Likes Received:
    1
    Trophy Points:
    56
    when i got my aspire the orbicam was a pain until i noticed the driver date.
    acer sent my laptop out with old drivers for XP Pro.
    i found that my orbicam was the low res and used the bison bar software & drivers.
    i got the update,deleted the old drivers and software. then renewd it all with the new drivers and (touch wood ) all has been well.but it will crash if you try and use it with msn switched on.
    if you have MSN on and try to open the cam to take a pic it will crash.

    just check in running processes that the bison bar software isn't running all the time