www.nl-2000.com

Hello fellow simmers, I get an odd error message whenever and wherever I doubleclick the nl2000v3.exe.
(from folder NL2000 v3.0 part 1 of 5 (DVD1))
It says: (Titlebar)
NL2000V3.exe: Common Language Runtime Debugging Services
And underneath:
Application has generated an exeption that could not be handled.
...
Click OK to to terminate...
Click Cancel to debug...

So, I click the Cancel button and it tells me, no debugger is found.
I read through this forum for a while, I swear I also read the manual before but did not find a known bug like mine.
I found someone´s idea inspiring to run the executable from outside it´s directory and did the same - with the same results.
FS9.cfg Max_Vertex...set to 21 - saved;
.Net 1.1 installed and uninstalled - Language problem in mind - and got a german version for my teutonic XP. ...Nope...
HD has lots of space, defrag is okay, the whole Duo-Core-Machine is fine...
Any ideas appreciated ...as I feel a little stupid right now - and I would really like those holidays in Holland!

NL-Team, thank you all for what seems to be such a great work

Happy landings, Slide

Okay guys,
since nobody felt like giving any reply, hint or answer, I can say it is definitely a Windows problem.
Many people seem to have that i.e. with their Media Center or other applications.
.Net3.0 is installed, so now, to all of you WindowsWizzards, how to debug the debugger?

Cheers, Slide

I don't know the exact solution for this error but perhaps your DVD1 is incomplete or some files like the .toc or NL2000V3 are corrupted by the download process or burn on DVD process.
For more info on that you can read this thread
http://www.nl-2000.com/nuke/modules.php ... pic&t=1678

Did you allready try the installation directly from HD?
Best regards

Thanks for the heads-up, Wolf,
I went and checked the toc-files with Notepad, they seem to be okay - as everything else from your side.
I downloaded via torrent and tried installing from one single directory on HD anyway.
It´s that d... XP, I´m sure - but I cant grab it

Slide,

Check your DVD's at: http://www.nl-2000.com/nuke/modules.php ... c&start=15.
Maybe you can find a mistake at point.

Bert Kuyper

Slide wrote:Thanks for the heads-up, Wolf,
I went and checked the toc-files with Notepad, they seem to be okay - as everything else from your side.
I downloaded via torrent and tried installing from one single directory on HD anyway.
It´s that d... XP, I´m sure - but I cant grab it

The files should not be placed in one single directory. The files must stay in a directory per DVD. So 5 directories.

Oh, Thanks Mark, so back to the One-Folder-Solution...

Tried downloading DVD1 via http last nite, but it crashed for some reason when I was sleeping.

I´ll be back with ... well, whatever...

Thanks a lot so far, guys
Slide

Got DVD1 a second time via torrent - same results.
I have 2 machines to play with, both XP-equipped and "state-of-the-art", both may be six weeks old - and both do not like the installer...I can´t believe it but I think I have to give it up.
Thanks guys for reading and trying to help!

Slide - you aren't alone.

I've been going through the same experiences as you since my torrent downloads completed a few days after release.

I've re-downloaded the torrent for disk 1, that didn't help.

I've downloaded disk 1 as the .ico file via http and burned it onto a DVD. That didn't help.

Pop up box titled "NL2000V3.exe - Common Language Runtime Debugging Services"

Text reads...

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

Process id=0x1138 (4408), Thread id=0x1288 (4744).

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

Tried the download version a second time and got slightly different wording...

"Process id=0x1594 (5524), Thread id=0x818 (2072)."

Out of morbid interest, ran it a 3rd time and the numbers were different again.

Same story with the DVD version.

I'don't know if it's the answer to your problem but can you try to do an installation in "safe mode" if these seems a windows issue. (course this will take a longer installation time)

Go into "safe mode" by pressing the "F8" button at startup of your computer.

Hi fella's,

I did encounter the same error when trying to install the scenery first time, the runtime and lenguage error is a quirck related to the .Net runtime files from Microsoft, to cure it I re-installed .Net Framework 1.1, 2.0 and 3.0.

after that the thing installed straighton without a glitch.

I d/l'd the 5 iso files and burnt them to DVD's then I copied all the files from the DVD's to one folder on my external harddrive in reverse order counting backwards 5-1, hit the installer and as stated before it all installed without a beep.

Hope it helps to sort yer glitch there

cheers

Save Mode, I thought was a nice idea.
Also tried a hint via the command line, forgot the exact line as I am writing this from another machine.
Reinstalled DotNet 1.1 --- and, it´s all the same again.

Gosh...sometimes it´s hard.
I know this is not the place for Windows related problems, but could someone explain, what this DotNet stuff is all about?
And: Do I need to have 1.1 installed, when 3.0 is also on the machine?

Slide,

Alltough I had installed the .Net framework 1.1, 2.0 and 3.0, somewhere along the line they have seemed to lost a bit or so, after I re-installed all 3 of 'm the installer got straight ahead with no problems

Uhu, thanks for the response.

I did what you suggested.
Made a clean uninstall for all of them, 1.1 via Windows, 2.0 and 3.0 via the setup.exe (Repair/Uninstall), then put it all together again one by one and it´s still a bloody monday.

I wonder if someone will finally find out what kind of Win-Poker this is....

Sorry to hear that Slide, maybe the daft one out, but did you try and install it as Administrator ??

Sometimes when you are a single user you create your own login account for Windows, and the Administrator Account is there dorment, occasionally for god knows what odd reason certain programs don't let them install so when you switch to Admin then maybe you can have another wack at it.

Just thinking outloud here,

GL