Announcement

Collapse
No announcement yet.

Road Runner Shell Issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Road Runner Shell Issue

    Hey guys,

    Don't know if anyone else has encountered this but I've been running Road Runner as shell for awhile now and wanted to do some configuration this afternoon which meant it was easiest if I just changed my shell back to run as "explorer.exe". I made these changes and noticed that Road Runner was still starting up so I located another Registry Entry (under "CurrentVersion/Run") and disabled that also.

    I then started noticing that as soon as the computer booted up I was getting the "Your computer has recovered from a serious error" message which just didn't go away (if I clicked the "Close" button it kept coming back up). The odd thing is that as soon as I change the Shell value back to start up Road Runner it all works fine again. It seems as if a Device Driver is dependent upon starting up Road Runner (the only thing I can think of is the CD Rip component but I can't really see how this would be causing any problems).

    I did some further investigation in the Registry but couldn't see anything that would be causing this issue.

    Has anyone ever encountered this problem before?

    Your help would be greatly appreciated cause I'm super lost here!

  • #2
    Anyone at all?

    If someone out there is running RR as shell and using Windows XP SP 2 try changing the Registry Entry back to "explorer.exe" and see what happens.

    Comment


    • #3
      Originally posted by B|ade View Post
      If someone out there is running RR as shell and using Windows XP SP 2 try changing the Registry Entry back to "explorer.exe" and see what happens.
      I've gone back and forth many times without a problem. (yet! )

      Comment


      • #4
        Yeah it's incredibly weird dude.

        Just wanted to see if anyone else had seen it ... Might have to do a rebuilt *sigh*

        Comment


        • #5
          Updated Road Runner and the problems gone away

          Must have been some corruption in the executable or somethin!

          Comment

          Working...
          X