Keeperos

Hi, sorry for the 1year + post but I am having the same problem and couldn't find a pack to ONLY install TweakUI (v 2.10.0.0) or a way to make it install silently (I also have the 2.0.1 version which simply uses the /quiet switch but that's another deal). From what I can gather I actually don't need to install it but rather simply copy it into the system32 folder? If so, is there also a way to copy the shortcut? (In short all I need is the relative path (like %WinDir% for C:\Windows) for "C:\Documents and Settings\All Users\Start Menu\Programs" so that I may add it in a self-extracting file and put it in a pack. I find this to be easier and more clean cut that the $OEM$/$$ method...) I don't know where or how to add the code you provided above... do I make a .reg file, I add it somewhere in a sif file... I'm somewhat lost. any help will be greatly appreciated!

Hey thanks, worked like a charm! Actually, I don't know if the package would work or even if it's for the RVM Integrator or nLite (or both), all I did was take the LUNA.MS_ from your package and put it in the I386 folder, replacing the windows original. Now one last thing, apparently your package must work as an integration, and although the method I used worked perfectly I'd still like to know how you did it so that I could make my own alterations (which is why I didn't simply used one of your packs) so that to integrate other styles and themes as well... Thank you!

Right, first of all, it is not a RyanVM problem since it works without nLite so RyanVM would either ignore me or simply tell me off. As for the later part, I think I mentioned that the whole point would be to keep a "clean" install that I'd later use as a starting point for making various alternate versions to suit different needs. If I used the nLite integration then I'd have to integrate the pack in all these cases. If the "original" I'd use on the other hand, had it integrated already that would save me a lot of time... Right now the only option I have is to only integrate the pack using nLite (disabling the "re-package the cab files") and then use this as a starting point. Either way, it isn't that I didn't have any alternatives, this was just a heads up.

Hi, I used the RVM Integrator 1.4 to integrate RVM's Update Pack 2.1.0 in my windows installation as a first step which I'd backup and use for my nLite installation variations. However after nLitening the setup files (with v. 1.0.1, enabling the re-compressing of the driver cabinets under "Options", I suspect here is where the problem lies) about 90 MB are removed with no good reason and I end up with a broken installation disk missing SEVERAL critical files. I know what you'll say, I should also integrate the RVM Update Pack 2.1.0 using nLite, however this only is a workaround, the whole point was so that I would avoid doing this every time. Anyway, just a heads up

Busted... No, I wanted to retain the repair/recovery console functions and AFAIK the only way to do that is to skip the "[unattended]" portion of the winnt.sif file. But this changes little. Even like that the problem I'll be solving will be the files not being copied. As soon as windows detect the altered "luna.msstyles" they'll still try to restore the original one. What I want is for windows to install the Royale "luna.msstyles" instead of the original. Please do note that the new "luna.msstyles" has 4 styles, the 3 original PLUS the Royale one so it is a complete replacement for the original and it did come directly from Microsoft unaltered... Update: After A LOT of searching I found the original "WindowsXP-TabletPC-EnergyBlueTheme-x86-ENU.exe". I thought I would try the manual integrate switch. Surprise surprise, it wanted the tablet PC version files for it to be integrated. Next one was the nLite integration. Here's sth. The nLite integration said that it couldn't find the "energybliss.jpg" in the ISO for it to update... Hmm, apparently the only thing stoping the nLite integration is that the ISO doens't have some non-critical files. Is there a way to make nLite ignore this and integrate the files nevertheless??? This could solve everything I think...

Guys, really need help here: I put these folders in the root folder of the setup CD: $OEM$\$$\Resources\Themes and $OEM$\$$\Web\Wallpaper Then, per THIS guide's instructions I put the following to the end of my WINNT.SIF file (located in the I386 folder) [shell] CustomDefaultThemeFile = "%ResourceDir%\Themes\Energy Blue.theme". Now, there basically were two problems, though I guess the one has to do with the other. The afore mentioned theme as you may or may not know uses the infamous Royale style which, in order to function correctly, must replace the original "luna.msstyles" file and add the "Royale\shellstyle.dll" in the "Luna\Shell" folder. For my PC it works correctly. For the new CD however which I tested with a virtual PC setup tried to use the .theme but failed miserably because: a) NONE of the files in the $OEM$\$$\Resources\Themes and $OEM$\$$\Web\Wallpaper folders were copied in the windows folder and b) Because although the new "luna.msstyles" came straight from Microsoft nevertheless as soon as I try to manually copy it in the right place it gets replaced by the original "luna.msstyles" (after my 2nd attempt I tried to delete the old "luna.msstyles" without the setup image loaded. Soon enough windows complained that critical file was replaced by a file that could not be validated (or sth) and that the original should be copied back again in order not to lose system stability blah blah blah...). So, for me the afore mentioned method won't work (I suspect that the files were not copied because setup hiccupped at the "luna.msstyles" copy process). Is there a way for me to DIRECTLY slipstream the afore mentioned file into the windows installation? EDIT:Clarification: I did have the patched dll for themes installed. All other unofficial styles that I tried after manually copying them worked fine.

One reason COULD be (although somewhat unlikely) that there is some sort of incompatibility between the ini files of versions 1.0 and 1.0.1. If it isn't too much trouble I guess you could recreate the settings (or the things you kept out) without loading the last settings. That way you can be sure that it isn't sth that nLite does because of reading the ini files wrongly or sth. It could even be that 1.0.1 has found that removing a certain component would break windows (a new one) and it somewhat misbehaves if you take it out or sth. Tell us how it goes. Cu

Worked ok for me. Guys, in the end if you still have troubles integrating SP2 or the hotfixes there always is the manual way (quite masochistic for the countless HOTFIXES to go one at a time but for these you can use the Ryans' integrator instead), meaning Run / CMD: WindowsXP-KB835935-SP2-ENU.exe /integrate:X:\(WinXPSetupFiles) (Where "X" the drive and "(WinXPSetupFiles)" the directory where you keep the setup files). The example above is for SP2, however ALL hotfixes that have the WindowsXP-KBxxxxxx.exe name format can be integrated in the same way, actually all nLite does (I would guess!) is automatically run these commands (or the extract switch and update.exe). Personally I keep an SP2-integrated backup and make my builds from there. (Yes, I am too lazy (at least at the moment) to actually manually integrate all hotfixes one at a time!!!) The way I see it, the more up-to-date (as regards to the defaults) the original files are, the less work for me to further personalize them to my tastes/needs. - Delete the setup files completely (but keep the Last Session.ini and Last Session_u.ini !!!), copy them again from the CD, FIRST integrate SP2 (preferably manually as I described above) and then use nLite to integrate the pack BEFORE any other add-on. CheerS!

Really guys, I tried several things but no go. Since I only got to using nLite yesterday I'm still very conservative with what I take out (meaning I only got rid of the Messenger (=less spam pop ups) and Windows Messenger (if you have internet then you'll want to DL MSN Messenger, btw, I'm gonna look for an add-on for the latest non-beta later...)) I most certainly kept that manual install thingy (I even checked), no go. I opened the winnt.sif and removed the Unattended section and voila! It worked!!! Since even in unattended you still need to choose the partition I REALLY don't see the problem in pressing a few more keys (like an F8 and a couple of ENTERs). By removing the [unattended] section in the winnt.sif you lose the TEXT-MODE unattended part, the GUI part is controlled by the [GuiUnattended] section, so, if you don't remove it, it defaults to DefaultHide mode which basically means, if you have pre-answered all questions the setup makes then it will still be an unattended setup. (If you have some then setup will still ask you to answer the non-pre-answered ones only). The ONLY thing is that when the GUI part of the setup begins setup will AGAIN ask you to accept the EULA agreement. However since this only happens at the beginning of the setup it's not that big a deal. After all, if you want to make a FULLY unattended setup to install in many machines at once then you won't mind keeping an extra CD just for that reason and keep this one as an enhanced generic. Y'know? THANK YOU sIn_maxo !!! CheerS!

(Sorry since this is a rather old post but since this question is the whole reason for me signing up here it goes:) You mean the ONLY way for me to use the recovery console or the repair windows installation option is to keep two seperate windows CDs, one with and one without the winnt.sif ??? BTW, how can I create a multi-boot DVD with those two versions both in? (Ok, MAYBE I'll also put in a W98 installation as well, especially if I can also slipstream in it all the remaining fixes and drivers...) Might be somewhat of a better deal...