nuhi

My my you got me fired up for a second. Alienator, that is what happens when USB Mouse Rate Switcher doesn't support the version you're trying to modify. nLite does not edit the file if you don't instruct it to. Hotfixing or update pack is the most probably cause. And this is NOT a bug, report to the author of that program.

Uh half of you said it works out of the blue, now you see why I'm having trouble confirming it. Still haven't dig deep, collecting bugs. newer, you do realize that this topic is for Win2k and that ryanvm is for XP SP2 only?

You're welcome.

MJMatthew, thank you, I'll update the description of the VSS and gonna make the dependency checkup routines to warn on page exit. Mcfly000, thx for confirming. Let me know if it still fails with VSS kept.

I think we're missing the crucial information, the "message telling me that the partition is not good for a windows install", what was it exactly? Have you tried repartitioning the whole disk to a one partition or you have some saved data on it? Basically I don't think that the floppy would help because the integration worked? since you now see the partitions.

There was some dummy helpctr.exe (or whatever the file is), try searching for it. You basically copy it where it should be and it will silently do nothing You can integrate it into the installation by using addons or simply copy it to the appropriate $OEM$ folder.

Don't worry, you just asked and I see now that I came a bit hard even though I didn't feel anything except the rush to explain as fast as possible that it is not nLite's fault.

I know what it is and you're right while it integrates it doesn't expect the RIS and the uncompressed environment. It does for the removals but not for the integrations. If you can't integrate on the normal installation before preparing RIS then no luck. And who knows what would that do, too much complications with truncating the installation files like that. However I will put this into consideration but can't promise that it will be done since there is not much interest in that area. nLite is more of a personal tool for the enthusiasts.

Doesn't matter if it can be installed, this is an old issues. Open Driver.cab with Winrar and click Test in the toolbar, it should confirm that it is corrupted. Unless we're having some other issue at hand since you say it didn't say that it is corrupted in nLite. Let me know how it goes.

Because, if I recall correctly, WAB needs some OE DLLS and when you're already keeping the biggest files from the OE you can keep the whole thing.

This question is quite often lately, gonna add a new Compatibility option. Check here: http://www.msfn.org/board/index.php?s=&amp...st&p=675970

Nathan0490, don't spread misinformation. If one needs setup.exe then keep Manual Install component. And for Update keep Windows Easy Transfer as well.

Task Scheduler, read the description.

That's a different story. One is to say that it is non-existent or that it is broken. Keep me updated, if you give up let me know how to test for that, also attach your preset then.

dexter, vLite will break any Server Feature config so that is a bug. I know where to look but it's not a top priority right now.

Nothing except System Restore would remove it. Comes to mind to remind you that checked component means remove.

Antivirus. Disable it or set it to scan on execute only.

I hoped for a better Matrix sequels

Yeah. I have even better idea but I'm pulled by the new removals instead. It should warn you on leaving the component page if some removal is killing another left component...soon in cinema.

Woohoo my intention wasn't to raise a wall, just to give my opinion. My opinion is never final, that's the beauty of an open mind (advert detected). It comes down to this: - ISO creation was the only must...burning was given to me, all I did is made GUI for it. - does this activation works for all Vista once activated, not just OEM?

I can name million good features but if one is already made by someone else why waste time. Burning is more essential, not all of us have the OEM install. You can enable ISO page by browsing to your Vista folder and in Tasks enable the page and the checkbox to enable before Apply. If you meant to use it for any sorts of burning without browsing to the installation files then no.

Haven't looked at it yet but what is the problem with using his tool? Why must it be in vLite, just backup your activation with his tool and restore after install, if I got it right.

Did you maybe removed the WMP Codecs? If you didn't then attach your preset. There is no WMP for Vista, you can try these wmp11 codecs: http://ksphere.free.fr/site/codecspackage.php but that's a long shot.

Of course it doesn't touch the oembios files. If you want to keep your previous Winnt.sif then just don't enable nLite's unattended page. And above all first try your modifications without nLite before blaming it for the errors (not offended just saying) because it could be that that method is bogus. You can use nLite to make bootable ISO while testing that method, it won't influence the outcome like that (just select ISO page, nothing else).

When you started Computer browser did it start? Also reboot once if you didn't. And "Windows cannot find \\Dell_optiplex. Check the spelling...." can be only if you typed 1 backslash ( \ ) and not double ( \\ ) infront of the name.