Alanoll

have you tried installing .NET when the computer is done installing? When are you trying to install .NET? That's only to get the link in the autorun to work.

I'll look into it....but I don't promise anything till Monday :/ I'm busy today, and tomorrow I'm moving...

Not entirely accurate. You can modify txtsetup.sif to have Windows Setup copy it over like any other XP file, but then you'd have to edit files....and could get complicated. Atleast your got it working the way you want

it won't appear on WU. You have to know the problem (possible search on the software support forums, links to the Microsoft KB) and then look.

what processor do you have? you may need to modify ntkrnlmp.exe

the sys doesn't behave differently, the user that uses it does. Basically, there are problems when programs try to run a loop to an IP address other then 127.0.0.1, say for Remote Desktop or something. Only people that use those certain programs will have the problem with it not working properly (microsoft blocked the other IPs)As for linking and not showing up.... You have to contact Microsoft for it (i've had to contact to correct a problem with my TV card with the HT processor)

That is a VERY bad understanding of hotfixes. Microsoft may test them, but the ones taht AREN"T released for everyone (ie, you have to have teh specific problem, or contact Microsoft) haven't been tested in as many circumstances as others. It is actually WORSE to install this, if you don't have the problem as described in the article, because it may interfere with something else, or just go hay wire with your config. That's one reason AutoPatcher is not such a good idea. Sure it's easy, but blindly installing patches is not always best. Infact, it might create more problems then it solves.

he doesn't want multiple winnt.sif, but just not to use cmdlines.txt in one of his installs. What you could do, is have CMDLINES.TXT call a batch file that then runs the other batch files. The batch file CMDLINES.TXT runs just checks to see if a file is present (ie $OEM$\$1\oem.txt was copied over, it would check for that file). If present, it runs the other batches, if not, it exits and setup continues.

you could include my VBS if you wanted, replace the SLEEP that way there is a visual prompt that they have to click when they're done. True it will disable the unattend, but for the people that don't have two CDROMS that will disable the unattend as well, as they'd have to be present to install Office. you could also use ping, and ping the localhost to cause the sleep as well.

the syntax above, but change -m \ROOT\(OSDIRECTORY you may need to add the drive letter to that, but this is assuming you started from your root directory.

it's the same syntax you would to make the AIO-DVD CD or almost any other CD, just a different path to the folder you want to make the CD out of (XP source or something) That's truly the only difference. cdimage.exe -lAIODVD -b\AIO-DVD\BOOT\loader.bin -h -n -o -m \AIO-DVD C:\AIODVD.iso Just change -lAIODVD to whatever you want the label to be. .b\AIO-DVD\Boot\loader.bin to the original boot secter for the OS. -m \AIO-DVD to the path that contains the original OS. and C:\AIODVD.iso to where you want the ISO created.

when you reburn it, you have to tell it to be a bootable CD. Look around the web for a slipstream guide. http://www.msfn.org/articles.php?action=show&showarticle=49 The F6 RAID drivers won't work with a WINNT.SIF file. It's something with the setup mechanism. You have to integrate the drivers somehow if you need them.

do you have %Systemdrive%\Windows\Web\Wallpaper\NewBliss2.jpg? Is it in C:\Windows\Web\Wallpaper\NewBliss2.jpg? I have the royale theme and I don't have that file. If windows can't find that file when it first tries to load the theme (through the WInnt.sif file) then it won't load the theme. Same thing for the other entries. If it can't find them, the theme won't load automatically

why did you post the same exact thing twice? double post? EDIT :: Nevermind ProductID is still supported, it's a legacy thing. Make sure you're typing the key properly

If you are talking about the box that comes up saying "Configuration" or something, and it's a normal small box, then you can't hide that. /qb- get's ignored in that instance.

correct. For simplicity, you may want to enclose anything strings (non numbers) with quotes. It shouldn't matter, but you never know. You will also get a desktop shortcut and a startmenu shortcut, unless you specify otherwise. @adiel this MSI will NOT download anything from the internet. All that switch does, is allow you to specify an already present skin, and it just gets inputted into winamp.ini. If the skin is present, and that's the name, then it should work. Otherwise, it will revert to the classic skin

do you have problems with the install.ini or getting the thing started? The page I gave you is pretty straight forward on how to use install.ini. As for getting it started, do waht my2001 said, and type wihu.exe /? to get the commandline arguments, read it, and then call the program from GUIRunOnce from within winnt.sif

I don't suggest you continue..... But it has been observed that with SP1 slipstreamed, i won't fit on a disc, atleast that I know of.

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\NewStartPanel] ;1=hide, 0=show ;internet explorer "{871C5380-42A0-1069-A2EA-08002B30309D}"=dword:00000001 ;computer "{208D2C60-3AEA-1069-A2D7-08002B30309D}"=dword:00000001 ;my docs "{450D8FBA-AD25-11D0-98A8-0800361B1103}"=dword:00000000 ;neighbour network "{20D04FE0-3AEA-1069-A2D8-08002B30309D}"=dword:00000000 2 second search prompt those up.

try renaming your files. since you're using the /kernel switch in boot.ini, you can name the kernel anything, and WFP won't have a problem. the logon screen, you can change with a registry tweak. you can name the logonui.exe anything. but the key is [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] UIHost="C:\Windows\Resourcs\LogonUI\logon.exe

DEP last I saw is controlled ENTIRELY by the kernel, which is Boot.ini territory.

mmkay, do you not read pages? http://www.kalytta.com/wihu.manual.php

try removing this line and try again Wallpaper=%Systemdrive%\Windows\Web\Wallpaper\NewBliss2.jpg or just blank the line to be Wallpaper= You may also want to change, Path=C:\Windows\Resources\Themes\Royale\Royale.msstyles to Path=%windir%\Resources\Themes\Royale\Royale.msstyles in case your letters change later on down the road. I'm not entirely sure what this does Wallpaper.MUI=@themeui.dll,-2036 so you could leave it if it works after doing the above, or blank it/remove it like above.

you really shouldn't technically install applications from CMDLINES.TXT especially ones that are heavy registry entry buggers like Office. The reason, the registry is VERY transitive during setup, and isn't finalized untill the VERY end of it, so ALOT of changes made aren't saved. however, you could just call that CMD file in your normal RunOnceEX routine instead of calling setup directly, just an idea.

did you slipstream SP1 into Office?