Thanks TayTay! I appreciate that. Do you have a list of parameters that are specific to DR? As an example, I use -renderthread 1 for CoX in order to take advantage of multi-core processors for that game.

I'm sorry you don't like the Launcher or the .NET framework jerry. Can you be more specific as to what it is you don't like about it?

What do you mean when you say "Apply a patch manually?" Do you mean you wish that each patch knew how to apply itself without the aide of a program installed on your machine?

Yeah, the lawyers make the programmers display a EULA more than people want. If there was a way to turn it off, I wouldn't be allowed to post about it I'm afraid...

Sorry Ripper - There's no public list of them.

Thanks anyway, TayTay!

Thanks for the feedback and link Taytay. I think I'll just stick with waiting for MONO to use the installer in wine. I've experimented with true .NET in wine and I didn't find very good results.

Thanks also for explanation of how to apply switches to a program. I used the -perf switch a lot to monitor framerate and the network connection.

I dont' like the Launcher because it uses .NET ;-)
The reason i don't like .NET is, that i like my system be be small and fast with small memory footprint, and a huge framework which allows interpreted languages to run doesn't fit that bill.
I want the launcher to be optional, because then i can choose if i install .NET or not.
By "Apply a patch manually" i think of an exe file, which patches the game to a new Version, without the need of any additional program (the Launcher). That way I'm able to download the patch with a fast connection where i don't have to pay for extra traffic, or i can patch different systems, for example my Desktop and my Laptop, without having to download the patch via the launcher twice.

Another problem with .NET, that was already mentioned is that it doesn't work on Linux (shouldn't "compile once, run anywhere" be an advantage of an interpreted Language?).
You mentioned Mono, but the problem with Mono is, that it is, correct me if I'm wrong, still only partially compatible with .NET 1.1 whereas your Launcher uses .NET 2.0.
The next problem with Mono/Linux which hasn't been addressed is that Mono is a native Linux framework, which isn't aware of wine, which is needed to run native Windows apps like DungeonRunners itself.
So when you are able to get the launcher to work with mono, you need a way to tell the launcher to start wine and execute the DungeonRunners app. The only way to achieve that I can think of, is to have a DungeonRunners.exe which is a native Win32 app, but that would mean the launcher is optional. :-)

So the EULA-Dialog is working a intended...
I guess I'm not allowed to post a "fix" either.. :-)

Thanks for the explanation Jerry. If it makes you feel any better, .NET takes up some harddrive space, but it won't be running unless a .NET app is running. Since the Launcher can be set to shut down immediately upon launching DR, it shouldn't slow your system down at all. And although I agree that one of the benefits of interpreted languages is often the ability to run on multiple platforms, that was not why we chose it. We chose it because it's a dream to develop in, and it saves us an immense amount of development and debugging time. Prettier programs with more features in less time with less developers is hard to argue against, although I realize it makes things a bit harder for people who want to run our games on Linux.