.NET error when opening the kitchen
 

I had been using the kitchen for a while now, and I love it, and I seriously thank the guys who made it. Your work has made the Titan a "useable" device.

The problem now:
For many reasons, I had to rebuild my PC, format-C, the whole thing. Anyway, I now get a .NET error when OPENING the kitchen. It's when the kitchen trys to paint the selection screen.

I have installed .NET 2, 3 and 3.5 and all the SP's. I uninstlled them, did a reg clean, re-installed 2.0, uninstalled everything, re-installed everything, rebooted a zillion times, manually installed the kitchen, uninstalled them again, installed the kitchen first then .NET, uninstalled it. Installed .NET first then the kitchen. Nothing seems to work. I tried 2.0 3.0 3.5 all verions of .NET that are out there. I tried all the SP's with no joy. I used the new version of installer, and the older version. No luck.

I understand that a new version as of 8/25/2008 is now the current version. I tried that - didnt' work.

I am including a screen shot of the error popup.

This is error occurs when the kitchen trys to come up - way before cooking.
It does not matter what project I select, they all generate the same error when they try to paint the selection screen.

I have used the kitchen before, and it all worked fantastic. I always saved the file after making one that I liked, so I DO have a working .NBH file, but I'd like to get the kitchen working again.

What am I missing??

Thanks.

Re: .NET error when opening the kitchen
 

bump ...

Re: .NET error when opening the kitchen
 

UPDATE:
After a day of experimenting, I have discovered that the culprit was IE8. It makes the kitchen not run!

After removing it, all runs fine now. So, be warned, IE8 beta 2 crashes the kitchen.

Re: .NET error when opening the kitchen
 

Thanks. You can work around this by removing (or commenting out) the backgroundimage= line in the kitchen_config.txt file in Titan_Core.rar. A permanent fix is in the works.

Re: .NET error when opening the kitchen
 

u need to repair your .net that should fix it