nuhi

But in that last preset you don't do anything...this must be that INTL.INF signature problem. I'm glad you found the solution.

Set your wallpaper, make sure it's where you know it is, for example %Systemroot%\Web\Wallpapers or just %Systemroot% Save your theme, integrate that exact theme you saved with nLite. After nlite is finished make folder on the ISO root directory before making ISO: $OEM$\$$\Web\Wallpapers and copy the wallpaper there. Or $OEM$\$$ if the wallpaper is in the %Systemroot%.

Thanks for confirming it. Component cache is needed for almost all hotfixes so better keep that one too.

Since this isn't vLite related I'm moving this topic.

Nothing out of the ordinary, and you don't remove much so it may not help but it's worth the try. Also if your virtual machine has internet access you can try will the windows update have listed those hotfixes in question if you integrate only them.

Problem is that those programs usually need some of the reg entries of the needed component so your best bet is: - remove all - learn which components are needed and start keeping them with every new reinstall (save your preset) I'm keeping only 5-6 components and all runs great, but for example you may be using analog Modem then you gotta keep 4-5 more components and so on...

Yup, all the same. Be sure to use 1.3 rc2 and test in virtual first. Also be prepared for issues which come from x64 natively...like more ram consumption, no speed advantage over 32bit, usually no driver support, majority of software is still 32bit so it actually runs it through the emulator...and so on. I gave up on it for my main OS until I need more than 4GB of RAM and software gets released first 64bit then 32bit, not the vice versa like it is today...but it is getting better.

No, I ment integrate them with nLite but don't do any removing or tweaking. (allowed pages during this test are Unattended, Bootable ISO, Slipstream service pack, Integrate Hotfixes, Drivers)

Tarun, wow Borec, I see so you're actually trying to say that Prefect compatibility isn't working for you, isn't hiding the protected components. I must say that it never happened to me before, can you explain to me how to see that? thx

Select Fully Automated for the Unattended Mode. Select if no password to no password of fill one. Select the Timezone and fill out the Workgroup.

Is that the sequence you did in that exact order?

It's definitely not nlite's fault. Check your BIOS settings, it's usually that, search the net about it.

It should never create a bad cd, if it does it's usually the addons, hotfixes (wrongly used in some way), third party modifications, custom remove files.

I'm having the same issue and I'm embarrassed to say that I'm not sure which service(s) are needed but there was talk about it on the forum, try searching and please let me know if you find it. It works with simple Refresh in the Connections window but that gets annoying eventually.

nLite may not be the cause. Check your other modifications. I always test it with all removed, it works on clean instalations you can try it yourself.

What is that...what ...trying to calm myself...attaching the first nlite release...slowly Now because of that blasphemy I'm locking the thread...actually because this is the forbidden topic, I hope you understand...and next version is final, then betas with many new features and so on...

Only Last Session preset which could had something in it that was problematic for you.

Talking about weird report. mystix, is that Windows 2000 and anyway attach your preset, maybe a screenshot of the problem too.

I would bet on the hotfixes. Not blaming them directly. For start you're integrating IE7 hotfix then IE7, that's bad but I don't think it is only that problem...anyway try first that IE7-KB929969-WindowsXP-x86-chs.exe IE7-WindowsXP-x86-chs.exe should be IE7-WindowsXP-x86-chs.exe IE7-KB929969-WindowsXP-x86-chs.exe Also if you still experience the same issue try removing hotfixes from the list until you find which it is...remove half then half of half...that way you'll find it fast. Then I'll check and fix, I don't have Chinese Windows nor all those hotfixes to help you other way.

Probably some of them is intended for IE6 and it overwrites reg entries or even some files of the IE7 if it was integrated before them. There is 2 ways to solve this: - integrate ie7 after all those hotfixes but make sure that if you do integrate some IE7 specific hotfixes to move them after IE7 - check which hotfixes are for ie6 and remove them, no need for them any more (recommended in combination with above, but if you don't have time and want to check this then you can start with number 1)

videonerd, thx but what is this about the "color scheme"? Can you wrap it up for me what did you keep for what to work so that I can make a new compatibility option? Thanks

nLite works just fine, you are one of the lucky ones. Do you integrate some camera drivers which get installed during install? Also please attach the preset so that I can try, thx.

What does "get run through nliteos" exactly means? Because if it's "as clean as a normal xp install" then it's not nlite's problem right?

Maybe you could test on full XP so that there is no false readings due to the missing files (removed with certain component). If you already have then I'll try too?

No SP1.cab in the original CD either, it's because x64 was shipped with sp1 in it and then it's already merged...they probably used nLite ... NOT Seriously until someone confirms and we see what is common with at least 2 reports in the situations like this when I try and it works there is nothing I can do.