g-force

After overtaking the last domain by stupid and some headaches we found a new "german" home; http://windows-unattended.org We are known as german-nlite.de, win-lite.de and we hope, you will follow us to our new forum. THX to nuhi for nlite and NTLite! Greetz, g-force

Using "mkisofs" instead of standard ISO-engine - the choice isn`t stored and has to set everytime manually. Edit: Made another run - everything is fine, choice is stored. nLite.ini: [General]Language = DeutschCPriority = 2AdvTweaksNoCompatPopPath1 = W:\! XP-BEARBEITUNG_x32\XPCD-Test_1.4.9.3[ISO]ISO_engine = 1

As XP will arrive at a "final" state in 2014, it would be a good idea to take nLite to a final version, too. THX nuhi for refreshing nLite again! Nuhi is back, and so am I.

Welcome back, nuhi !!! BTW, here`s the link to the german nLite forum - still active! http://www.win-lite.de/wbb/board202-windows-xp/board8-xp-tools-zur-image-bearbeitung/

Welcome to MSFN-Forums! Please read the red advice in the forums header. Please attach your "winnt.sif" too, but delete your CD-Key in it.

Maybe "DriverPacks.net" is your solution: http://driverpacks.net/driverpacks/windows/xp/x86/lan/10.05.1

I always work like that. I mount my XPCD-ISO with UltraISO, then point nLite to that (virtual) CD-ROM.

The cause for failed integration of your themes is your folder-structure. Every xxx.msstyles needs its own folder (mostly named like the style). It would be better and easier for you to install XP first as a working OS and then use nLite to get things work. You`ll be able to get the correct structure of the folders in XP, e.g. "%systemroot%\Resources\Themes". I always prefer to use the same Host-OS as the one to modify.

THX @ johnhc for the link - here`s the topic @ "Win-Lite.de": http://www.win-lite.de/wbb/index.php?page=Thread&threadID=4252

Is there any reason to do so? With nLite you integrate your drivers, they are available during XP-Setup. If you want to install them, you need to treat them like an "Unattended-Software-Installation". Edit: Double-Post here:

Having your Hotfixes integrated will prevent you of spending lots of time AFTER XP-Install. And you don`t need to be online and do the same thinga again, again, ...again... , ag....... One-time-in-5-years-XP-Installers: Don`t mind about us, who install 5 times a day....

You didn`t SEARCH for yourself? Don`t Mind, I did: An ADDON can be be included using "nLite", quite simple.

Fernando missed to point you to the thread where you`ll find the right files: He`doing an awesome kind of work, promise you. If you`re unsure about your hardware, give this a try: SIW

Kel, if you need help please contact me, we sure find a solution: g-force@web.de (Admin of "German-WinLite")

WPI can do that.

Agree - I use "setup.cmd" in some of my Silent-WinRAR-SFX (I usually install with this method). Some Setups won`t install (or stuck) without that "start /wait" because of false or "too fast" execution. I´m sure it makes a difference in a .cmd.

It seems to make a diiference if you start "explorer.exe" from "system32" of using your program. Maybe your program "Run" adds some parameters, I don`t know. Search for "explorer.exe" on your system (there are different "shortcuts") and execute them by using your "Run".

I think you bought a key (maybe few years ago), but you got to know what key you paid for. If you know there is no problem to lean a genuine XPCD that matches your key. A useful keyword for your search is PID.

I´M not sure about that, cause this is a HKCU-Setting: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders] "Personal"="YourDrive\YourFolder" I replaced my current setting with "YourDrive\YourFolder". I´m on a german system, don`t know if I´m right about "My Documents = Eigene Dateien".

You`ve got to modify the "sysprep.inf" manually and delete the asterik "Computername = * ". It´s explained here: http://capitalhead.com/articles/force-sysprep-to-prompt-for-a-computer-name-during-mini-setup-in-windows-xp.aspx

Maybe I miss the point due to my poor english. That`s what I understand (written in a .cmd): 1.) start /wait MySetup.exe ---> executes and waits until end of "MySetup.exe", then executes the next line 2.) start MySetup.exe ---> executes "MySetup.exe", doesn`t wait and executes immediatly next line of the .cmd 3.) no switch at all ---> same as 1.), because "wait" is set by default Please correct me if I`m wrong.

A little "Push". I`m still looking for a backup of the german translation.

Glad to hear your good news. I`ve done this procedure by Try & Error a few years ago - without rabbit`s help... Enjoy, g-force

If I don`t use Start /wait im my CMD, all lines are executed without waiting. So it makes a difference for me. There is no waiting enabled by default in a CMD.

I usually use "start /wait" in a .cmd - and it works.