Arie

Ehm, this thread is over 6 years (!) old...

$OEM$-folders. See the Unattended Guide.

First of all you're kicking up a topic which has been dead for almost three (3) years! "cmdow" is a small tool which lets you hide command windows. You can download it by looking for it on Google. I would advice you however to use "cWnd" instead as it's not detected as a virus by mistake such as cmdow is.

Plenty of scripts and such are posted on this forum, simply have a look at all the other topics.

Reinstalling MSXML 6 most likely will solve your problem.

Yes, you can integrate Internet Explorer 7 into your source. You can use default Microsoft tooling for this, or use tools such as HFSLIP, nLite, et cetera.

No one will be able to properly answer your question, as the durability and stability will also depends on the combination of your hardware and software. The only way to really find out is to simply test your project. As for the security, without looking at your attached file, there are plenty of guides around on how to properly configure your machine. I suggest you look for those.

I don't use nLite myself, but you can install most, if not all applications you listed at T13 via SVCPACK.INF. No need to make CAB-files, you could simply make self-extracting, silent installers yourself.

Yep, you'll need to start with a clean, newly copied, original source.

Upload your LastSession.ini.

I prefer neither. I would simply go for integrating the hotfixes. As for tools such as nLite, they take too much of my control over my project away in my humble opinion, hence I prefer to use HFSLIP, my own scripts and packages.

You could have found the answer easily yourself by simply reading the Unattended Guide. Click here for your answer.

You should have posted your questions at the nLite section of this forum. Please ask a moderator to move your topic.

Upload your LastSession.ini instead.

I don't quite understand your problem, but perhaps this is simply because I don't use nLite. You can change your WINNT.SIF file in such a way that you can enter a serial number during setup, but so that the user account creation screens are skipped. See the Unattended Guide and Ref.chm.

Click.

You mean Windows Messenger. You can simply not make it install via your WINNT.SIF for example. What nLite does for a lot of things is not just simply not having something install, it sometimes removes a component completely from your source and this can create future problems, like what you're experiencing now. Tools such as nLite are in short meant to strip your source. If you don't want to strip your source, but instead simply have certain components not installed, other applications such as Internet Explorer 7 added, you don't need nLite to achieve this.

VMware doesn't count on users to remove default functionality, that's why it doesn't work after you ruined... ehm, editted your installation source using nLite. Your problem is nLite, not VMware. Ask at the nLite section of this forum, perhaps someone there can be of service. Adding drivers to your installation source doesn't matter for VMware, as VMware doesn't use your physical hardware, but virtual hardware for which VMware provides it's own drivers and such. I never understood why people would want to strip default functionality from their installation source using applications such as nLite. If you're concerned with disk space on your installation medium, simply use a DVD. Enough ranting from my side

Search your hard drive for DBX-files. Your e-mails might still be in there. You can open these with Notepad for example.

Recording the TV output or the output during the game via the phono cables, you will get the following:

There are several ways. You could use $OEM$ folders for example to have the DLL copied over to your system32 folder, or create a self-extracting, silent installer package which extracts the DLL to your system32 folder. Next you could run regsvr32.exe /s filename.dll from a batch file, via RunOnce or RunOnceEx, automatically after the extraction of your self-extracting, silent installer package, et cetera.

Never heard of it. Looks good. Will give it a try soon. Curious. Cheers for the heads up

Rule number one: no warez!

No, it won't be smaller really. By using this method you don't cut down the installation source files, you cut down the size of the final installed files on your hard disk. The unofficial Lite and Micro builds have a reduced size of installation source files as well as a reduced size of the final installed files on your hard disk. The above described method gives you more configuration options, it gives you more control, that's it's power.

I honestly have no clue what you're on about. If you've created the MST-file, then you can simply type the correct command in a batch script for example or whatever...