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.

    RMClock problem

    Discussion in 'Gateway and eMachines' started by gamadaya, Feb 20, 2009.

  1. gamadaya

    gamadaya Notebook Evangelist

    Reputations:
    121
    Messages:
    491
    Likes Received:
    0
    Trophy Points:
    30
    I get this error message when I try to start RMClock up:

    Cannot install or load RTCore64 driver.

    It then tells me to make sure I'm not loading from a read only medium/network drive (All files are in a folder on my desktop) and that I'm logged on with Administrator rights (I am). So what's the deal hear?
     
  2. PopRoxMimo3

    PopRoxMimo3 Notebook Deity

    Reputations:
    82
    Messages:
    1,090
    Likes Received:
    1
    Trophy Points:
    56
    hear? i dont know whats wrong hear? jk just yanking ur chain. try to reinstall it.
     
  3. nfsnyc

    nfsnyc Notebook Consultant

    Reputations:
    72
    Messages:
    236
    Likes Received:
    0
    Trophy Points:
    30
    You need a signed driver.

    http://forum.rightmark.org/topic.cgi?id=6:1557

    (Replace the RTCore64.sys in ur program folder with this one, keep the old one elsewhere to be safe).

    Might wanna run a virus scan or two, but I think this is the one im using, or you can google yourself and find a more official download source.
     
  4. gamadaya

    gamadaya Notebook Evangelist

    Reputations:
    121
    Messages:
    491
    Likes Received:
    0
    Trophy Points:
    30
    *yawn* Sorry I fell asleep like right after posting this. And right hear on the floor too. I figured it might have been an unsigned driver, but the usual warning didn't pop up. Thanks for the link.