rec.autos.simulators

> >    I use both adaware 6 and Spybot.  They both seem to pick up stuff
> missed
> > .
> > Although, Adaware seems to find a few more things after Spybot is done.
> > The runtime files was my reference to the .net stuff.  I just wanted to
> > make sure you had the files needed to run .net code.  So uninstall and
> then
> > re-install .net.  Did you get any installation errors?   Another option
> > would be to dload the non installer version of SCC and unrar it
manually.
> > You'd need to go to RaceSimCentral's SCC forum and get a premade driver.
> > The .net usage is by the SCC loader only.  If you can bypass that, then
> the
> > .net isn't needed.  Of course you can use the nifty featurers like the
> > headlight activation, carlocker, track stats etc.

> > I had the demo previously installed and there was a 2nd SCC  exe file.
IT
> > had a longer file name than the loader(which is scc.exe)  With the demo
> > exe, you can launch directly to SCC, again skipping the SCC loader.

> > good luck
> > dave henrie

> Ran Adware 6, everything clean.

> Uninstalled .NET Framework 1.1.  Manually erased Microsoft.NET folder in
> Windows that was still*** around.  Downloaded .NET Framework 1.1
again
> from Windows update.  Installed.  No instalation errors. Same problem.

> Sorry I've asked about this in a few places I'm not sure that I mentioned
it
> here but SCC works perfectly fine from the .exe.  It's only the Installer
> that there is an issue with, that's why I didn't push the issue before, in
> that I could use SCC perfectly although your right I missed out a few
> options in the Launcher.  But now Porsche Cup is out you can't really
start
> it without the Installer.  Also I suspect that in the future more and more
> Mods will use it too.

> I never installed the SCC demo so I didn't have anything*** around
from
> it.

> Schooner is probably right that there is some small error in the SCC
> Launcher code that's launching the JIT de*** but it must be pretty
> inocuous because everyone else runs it with no problem.
> I still think that the problem is some SDK stuff*** around in the
> Registry.  Does anyone know how to clean it out?

> Thanks.

> > Again you will only get the JIT windows IF an error has occurred.
Getting
> > rid of the SDK and related is not going to fix the problem causing this
> > IMHO.

> But how come no one else has this problem or a CTD for the error if there
is
> no De***?
> I've re-downloaded and reinstalled SCC a couple of times.

> > It could be something specific to your setup that is causing the error
and
> > perhaps others don't have the same configuration, I have no idea.
Without
> > seeing the actual error there isn't much I or anyone else can do really.

> Okeydokey, I know it of by heart by now:

> <<SCC.exe - Common Language Runtime Debugging Services

> Application has generated an exception that could not be handled.

> Process id=0x5dc(1500), Thread id=0x5e0(1504).

> Click OK to terminate the application.
> Click CANCEL to debug the application.>>

> Clicking OK terminates it, obviously, clicking cancel results in:

> <<SCC.exe - No De*** found.

> Registered JIT de*** is not available.  An attempt to launch a JIT
> de*** with the following comand resulted in an error code of 0x2(2).
> Please check computer settings.

> cordbg.exe !a 0x5dc

> Click Retry to have the process wait while attaching a de*** manually.
> Click Cancel to abort the JIT debug request.>>

> Clicking Cancel results in termination and clicking Retry results in
> nothing, except I think it leaves a runtime process going waiting for the
> de*** that never comes.

> Thanks
> Rudeboy