[higina]

When starting Nlite i get the error messege shown in the Picture below, could anyone advice me what to do to overcomte this problem

OS XPSP2
CPU Intel E4500 2,2GHZ 2MB l2 cache
Graphic Card Nvidia Quadro 3400/4400 256MB
2GB Ram Corsair with heat sink
160 GB seagate hard disk
Sony DVD Rewriteable DL
Gigabyte P35 Motherboard
500 Watt Power supply


 nlite.jpg (45.98K)
Number of downloads: 10

[johnhc]

higina,
Hard to say since I can't read the error message. What version of nLite are you using? Do you at least get to the first screen from nLite? Do you have .NET Framework at least version 2.0 installed? Did you check the MD5 of the download? Have you tried it with your security software turned off (I unplug my modem when I do this to block Internet bad guys)? Any other information would be helpful.
Enjoy, John.

[higina]

Netframework 3.0 was installed i thought that it caused the problem i removed it but the same problem ( Version 2,0 is installed )and running . And this is the first screen i get after i double click on Nlite and i am running version 1.4.8

the error messege says ( maybe not exact translation )

A problem aoccured while trying running Nlite program was closed

and also explain problem to microsoft

A report is made which you can send to microsoft to help us make Nlite better

the report is
Event type : clr20r3 P1 :nlite.exe P2 : 1.4.8.0 P3 4883a93e
P4 : mscorlib P5 : 2.0.0.0 P6 : 471ebc5b P7 :1b08 P8: 10
P9 : system.typeloadexception

[johnhc]

higina,
You should go ahead and upgrade to nLite 1.4.9.1. I don't think this will help, but it will eliminate one factor. Information in the error message all point to .NET Framework. Do you have all the latest updates? I remember when I updated .NET 2.0 some time ago, it was compiling routines for several boots after the update. Perhaps it is not through with that. If all else fails you might try the latest .NET (MD5 D481CDA2625D9DD2731A00F482484D86) after removing your current one. Be sure to check the MD5 hashes for both nLite and .NET.
Hopefully someone will respond who has seen this error.
Good luck, John.