Alanoll

that would assume he used nLite... did you change anything BESIDES adding the servic pack? what does your batch file do? did you add some modified files...

@prathapml Well, link to the discussion, or tell me the question and answer or something along those lines...

Technically, it's harder.

Neutral poll option added

the /integrate switch, all it does, is add the hotfix file to the SVCPACK dir inside I386, and add an entry to SVCPACK.INF. If there are files within the pack that are newer then the ones that were present on the RTM of the OS, they are then replaced with the newer versions. The SP1 guide still is relevant when you want to do it manually, however the SP2 section would have only delt with calling the hotfix with /integrate and that's it. Also, I should mention, that section of the write is finished. Just not uploaded

oh, you're waiting for that? It's a slight problem in the INI file created during install. Typed in the wrong number or something, I'll fix that right away. Workaround is to go into the plugins, select the WAV one, and then select the file types.

I'm gonna be putting a FAQ on site (there already is one, but larger) Start linking to topics that should be included? I means things like the repair thing above...

i don't believe the XP CDIMAGE_HOME from the unattended website has the -o switch to optomize the image...

just for fun... Go to the run box (Start>>Run or <WindowsKey><R>) Type : services.msc Look for the Themes service, and if it's running. If it isn't, somewhere somehow it's getting disabled. If it's NOT there, you may have used nLite or somehow the source got corrupted.

This has NOT been my experience. Of course, I conduct my test via cmdlines. What this is at runtime, it translates %systemdrive% to it's value before executing the command. However, if you were to use the INI method for the MSI, try using a Windows Installer Property, [ProgramFiles] for example or something along those lines. I'm not sure if it work, but the way I have the MSI setup is that reads in the entire line as a string, and then processes it in it's internal processes. I wouldn't call them (WIHU,XPLODE and the likes) that run at "First Startup" to be extensions of RunOnceEX. WPI compiles as RunOnceEX script at runtime then imports, then executes. For teh most part, I use RunOnceEX to call WIHU/XPLODE simply because I have all my applications running from CD and as such, [GUIRunOnce] is useless to me, as NOTHING is copied over besides the Windows Install files, so RunOnceEX is a good way to accomplish this,especially using INFs (I like INFs more then BATCH). Novices find RunOnceEX easier then others, since they don't need to learn the new syntax of INI files or Javascript or the like.... Speaking of which... I'm planning on after the next update to the MSI, to upload the InstallShield file that make it, so all anyone has to do, is find the correct files, and recompile then upload somewhere to share. Sure, it won't be controlled, but it will reduce the time, as with the last MSI I got kinda busy and had to keep putting it off (and I tend to get off topic of things I'm doing).

If you're executing the winnt32.exe command, I think there is an upgrade switch, if not.... look at either winnt.sif reference on site, or ref.chm in the deploy tools, and look up Upgrade, and there should be an upgrade thing to add to your answer file.

now seriously.... did you not read what I sead or search for CDBOOT errors? I'VE REPEATEDLY TOLD PEOPLE TO USE CAPITAL LETTERS Also, just a side note to others, it is NOT advised to replace I386 with something OTHER then ANOTHER 4 LETTER directory. It's the basis of hex editing, you can't add bytes as you don't know how it will affect the internals of the file. It's an assembled file, and as such when you're reading it in HEX, most of which you see are the VARIABLES, and the code underlying is invisible and so adding bytes could alter the code. I'm not saying it doesn't work, HOWEVER it's NOT ADVISED. EDIT:: After looking at the guide, did you even notice that when it's telling you to replace I386 with PRO1, and it doesn't say replace I386 with pro1?

you could also use WIHU, which allows for the similar type of functionality, but also deselecting and such via boolean expression (if newer version is installed, if a file is already there, etc.)

not to rude or anything..... But seeing as there are SO FEW people who have this problem who have followed that guide, it is MOST LIKELY USER ERROR. What the guide tells you to do WORKS. As bobby100 said, are they from the same version of windows? When making the CD, did you first make it, then add SP2 to the install? If so, did you remake the boot folders? Did you use CAPITAL LETTERS when hexing?

@a06lp you do know it's been released right? The only thing missing is the XREGAUD to allow you to say "NO DON'T REGISTER ASSOCAITIONS"

I really need to put a disclaimer somewhere.... @bmn I believe Astalavista is correct, however I can't confirm as I don't use WPI.

creating the two different types of kernels is the same no matter which you're using. You're problem is SELECTING which one to use at runtime. FOR /F "tokens=3 delims= " %%A IN ('REG QUERY "HKLM\SYSTEM\ControlSet001\Control\Session Manager\Environment" /v NUMBER_OF_PROCESSORS') DO SET NUMBER_OF_PROCESSORS=%%A bootcfg /copy /D "Windows XP Professional" /ID 1 if %NUMBER_OF_PROCESSORS%==2 goto DUAL REM ----For Single proc bootcfg /RAW "/Kernel=OEMKrnl.exe" /A /ID 2 goto End :DUAL REM ----For Multiprocess/Hyperthread proc bootcfg /RAW "/Kernel=dualKrnl.exe" /A /ID 2 :End bootcfg /Timeout 2 bootcfg /Default /ID 2 The singkrnl.exe is the normal ntoskrnl.exe file, while dualkrnl is ntkrnlmp.exe. Both need to be in system32. Just create a batch file, and run it during yoru install.

are you trying to install from Within Windows? if so, svgusta is on the right track. You have to use a switch when calling setup to tell it to use the answer file. The answer file is ONLY automatically used if you boot into the CD.

Well, I don't even think the screenshot resembles the current build anyways

I know of a way to remove ACCESS to outlook express, but I don't see an INF for outlook express installation

speaking of the next revision... yeah yeah... since only one bug was noticed, gotta remember how I fixed that. But expect it tomorrow.... I got alittle tied up doing research on PHP and MySQL for the Unattended Website

ummm.... I personally like the idea of, if you don't know when a program does it's thing, then ask the author.... No offense. nLite, if it still uses the INF file, i believe runs at about T-13 or so, as for the DriverPacks, depending on how they're constructed maybe around the sametime as RyanVM's pack or entries are jsut added and they're present at time of Driver installation (perhaps DetachedProgram).

maybe a long shot, or a short one, but can't you just copy the Steam folder over, and change the "InstallDir" key in the registry?

anyone know some good PHP/MySQL sites to quickly learn? ay?

Ah come on guys, don't hide from me. Most of what I say is meant in jest... @saitoh183 to be quite honest, the ONLY way this will work is if you get the help from the mods to keep it clean. I mean, prime examples of failures....the application switches THREADS (there are two), the autoit thread was cluttered like non other till I gleaned 7 pages from it, there was a similar post to yours to create such a thread, and it's now more oriented more toward WPI. Instead of creating this thread, unless it's about Apps, post in the "Unattended Additions" thread and they'll be added to the website, and as such there will be NO people giving their say or asking questions. I say besides Apps, primarily because I just spend all day today working with xoops (it's an open source program) to see about creating a database to keep everything in and clean. Which is basically what you really want..... As for other types of solutions, if you find them for me, i'll be more then happy to add them to the site (which I'm currently rewriting and reorganizing).