nowinscenario

Well, nuhi, what about it, man...?

Sorry, it would be more detailed and updated (because I have a couple more builds), but I'm overloaded in fixing computers right now). I only wish others would add to this list, so you would have it all in one place, to make it easier to troubleshoot, and to recognize collating patterns. (Hint. Hint, everybody. Thou shalt contribute to the cause of making Microsoft mine!) {:~]

Add this to the sif, too (it's just an example of one I used): [shell] DefaultThemesOff = "No" DefaultStartPanelOff = "Yes" CustomDefaultThemeFile = "%WinDir%\Resources\Themes\Crystal dlb 2.theme" And, yes, they are correct: 1) there are a gaggle of add-on CABs for themes, most of which I've used, too--get them as you see fit; and 2) using the OEM folders method, you can indeed add as many as your CD/DVD will allow (one time I've shoved in 300MB of themes there myself!)

Fernando: just a thought--wouldn't it be simpler just to make an add-on CAB (or add-on CABs) for nForce RAID that we could use with nLite to integrate into our installations? For instance. I've been using Rikgale_XPRAID5_addon_v1.cab without any problems for several builds now. Would such a thing work for your project here?

Tux, you mean nLite RC8 somehow mutates these values in a way that RC7 did not (of course NC7 simply refused to even properly execute some of these at all)?

[Preliminary Notes: If anyone has any specifics to add to this list, this is a place to do it, in order to collate the bugs into a single area, making it easier for Nuhi (as well as other VIPs) to peruse and analyze...] [This list is an ongoing edit, currently spanning six nLited OSes, tested in VMWare and, so far, on one completed laptop. Currently, I am readying two desktops for the next round. Everybody to their corners...!] NOT WORKING OR OTHERWISE STRANGE BEHAVIOR (An In-Progress Documentation): Visual Effects (My Computer Properties) - Persistent Behavior set to be disabled, but yet ended up enabled instead Slide TaskBar Buttons Show Translucent Selection Rectangle Use Common Tasks in Folders Use a Background Image for Each Folder Type Visual Styles on Buttons and Windows Enable Combo Box Animation Enable List Box Animation Enable Menu Animation Enable Tooltip Animation Enable Tooltip Fade Enable Window Animation Enable Smooth Scrolling Show window contents while dragging Visual Effects - Inconsistent Behavior one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores ClearType Effects (Display Properties/Appearance/Effects) - Persistent Behavior set to be disabled, but yet ended up enabled instead Scroll Effect Password Prompt (Display Properties/Screensaver/Power/Advanced): Inconsistent Behavior one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores Prompt for password when computer resumes from standby MRU (various settings) - Persistent Behavior set to be disabled, but yet ended up enabled instead Maintain document history Maintain network history Enable AutoComplete Remember Previously Used filenames Automatic Updates - Persistent Behavior set to be Turn Off Automatic Updates, but yet ended up no toggle at all Remote (Computer Properties/Remote) - Persistent Behavior set to be disabled, but yet ended up enabled instead (this despite the fact that other remote settings are disabled) Allow Users to Remotely Connect to this Computer Mouse Properties (Control Panel) – Persistent Behavior cursors set to install, but directory not created, though (unusable) themes still listed as installed Cursor themes seem install in name only (as an indication in properties), and themes of the multi-theme packs which contained them do install without a problem, but the cursors never finish installing. So to illuminate this even further: cursor schemes are visible in pointer box (including references to all the stand-alone add-on cursor theme CABs, but Windows has no Cursor directory, so the entire folder is not even created! So maybe those CABs would be able to deposit their cursors, but there's nowhere to put them. This is a strange first, in my experience: a common Windows directory that's simply not generated. [Another point: these themes and packs were all used on previous nLited OSes with no problem (these CABs are some of the usual stand-bys that usually operate without a glitch).] Another observation, which I've forgot to mention--but this one goes all the way back to when I first started using the theme add-ons that contain cursors: when I choose a specific theme, Windows always pops up an error message to the effect that "this theme is already in use ... blah, blah, blah"--and it happens every time I switch to a new theme (?!). This holds true even after correctly extracting the cursors and creating their directory. (It does, however, allow you to change themes.) Nuhi: Update and temporary workaround which may give you a clue: if I don't tick nLite to remove the Windows cursors (like I've always done without problems), then it installs the cursor themes fine—I just have to deal with all that crappy MS cursor schemata that I don't like. So somehow this little area becomes bugged. Folder Options - Persistent set to enabled, but never works (but this one is not original to RC8—it goes way back) Show Control Panel in My Computer Windows Settings (various) – Persistent set to be enabled, but yet ended up disabled instead Restore previous folder Windows at logon set to be enabled, but does not show Protected OS Files Show All Files and Folders Start Menu (various settings) – Persistent set to be disabled, but yet ended up enabled instead Use Classic Search in Explorer/IE Maintain network/document History Allow Recent Documents on Start Menu Enable AutoComplete one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores Start Menu Pop-up just added (I kept forgetting this one)--however, let it be known that this has been a longtime inconsistency, not peculiar necessarily to RC8 Time Synchronization – Persistent set to be disabled, but yet ended up enabled instead Desktop Cleanup and Desktop Cleanup Wizard - Inconsistent one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores NET Framework 1.1 (and updates to it) - Inconsistent one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores This is just as odd as the cursor install paradox above: the add-on CAB has both .NETs in the same CAB—they are not separate—yet, for some reason 1.1 has a 50/50 chance of installing (?!) … This is consistently inconsistent for five nLited OSes now, both Home and Professional, with slight variations in settings and additional CABs, in VMWare and as an actual install, on laptop and desktops. User and Logon Names – Inconsistent Behavior (?) one of those "flip a coin" settings: it sometimes obeys, it sometimes ignores, it sometimes does something else entirely This one is so weird I can't really comprehend it enough to explain, but I'll try: one time nLite did not change Administrator or User Name, as per my choices, thus auto login failed: had to login as simply Administrator by simply guessing default. You can also read another thread (for which not one person had a proposed solution or explanation) concerning particularly Home, where changing user name and company changes only the registration data, but not the name as it's displayed in Windows or the Control Panel—and even when you change it in the Control Panel, post-install, it only changes how it's displayed there [i will post a link to this later]. Best case scenario: I change the Administrator name when the choice first arrives, but do not change it in the second instance (I do, however, change the Guest name there, which seems to work fine)—this has the effect of logging me in as the Administrator, with no additional user created (which I've given up on for now); but, you guessed it, the Administrator name was not changed (?!). [More on this one later…] A sample of some session and winnt.sifs are attached, for your viewing pleasure... =;-}' Last_Session.ini WINNT.SIF Third_Last_Session.ini Third_WINNT.SIF

Look in TweakUI for simple tweaking to solve your problem--if it won't work, get Xteq (it will do/undo just about anything)...

You need NT Backup, too. For services, VSS and MVSC need to be Manual. Also, don't screw with anything that toasts MMC, or you're in a world of potential hurt here. Indexing is totally unneeded as an explicit service (I haven't used ot for over year in my installs)--but there are inter-component aspects extant (that's why you keep coming across references): we can remove it, but parts we keep that we need still imprint it on various interfaces--and it's one of these part you most likely made angry. Shadow Copy would certainly qualify...

RogueSpear: you think like me with regard to the unified Start Menu (I hate the default XP multimple Start Menus, and the fact that software installs in different locations until you redfine it, such as with TweakUI). What I would like to know is this (I'm sure the fix is an easy one for you--but this part of it is too new to me right now): After install, I have to redefine the Start Menu to only be All Users\Start Menu and then also the Programs to All Users\Start Menu\Programs (for instance with TweakUi or Xteq). I then delete all the shortcuts and default MS directories and replace them with a template of my own that has directories and subdirectories the way I prefer them. I do the same for Program Files (where it's really almost a basic mirror of the same naming conventions and directory structure). So what I'm wondering is do you have a scaled down script I can include in my custom install that will do all this automatically for me, so that it's like that on first boot? (Or is there an easy way to modify yours?) Also (perhaps this is not the place to ask--but I'm sure you have an easy answer), while I do really like the idea of the add-on CABs from the RyanVM forums for installing programs, I would like to know if there's a simple tool to internally alter their CAB path to match my install defaults in Program Files and the Start Menu. (The fact that their default paths are not mine is the only thing that prevents me from using them--and it would seem to be a simpler solution to just alter their work, than starting completely from scratch.) Thanks in advance for any assistance you can provide.

VSS needs NT Backup to work, if I remember correctly (from one of my 648.23 troubleshotting custom installs), and its twin service MS Software Shadow Copy Provider (SwPrv)--so did you include those?

rds_correia: Yeah, I now have great custom installs once again (I just leave out the 2 attribute changers and 1 audio context extensions, as well as the XPize--I miss this last, but, oh well, it's not essential: I just liked it because it was non-resource-hogging eye candy enhancements). The ethernet turned out to not be a problem--the problem was me: I forgot that I limited the amount of users on my router, so it wasn't letting the VMware install connect to the Internet. Strike that from the record. The .NET was what I thought: I simply forgot to toggle it--so now the install went fine there. Strike it from the record. VMware uses Creative PCI to power its audio output, so a previous component removal must have interfered with that--but I solved the problem in the current build. Strike that from the record. I will also attach my last INI session after one more build--I'm doing one more build because of very minor annoyances: one of the application installs, although working, is broken with respect to the CPL add-on, because the author hard-coded "Program Files" in the path, but I change the path to "Installations"); the CDImage GUI CPL add-on does not work (it comes up as unknown/unworking in the Control Panel--don't yet know why, but I suspect it's once again path naming convention discrepencies). I'll have to post to the respective forums to see if the author can fix any of these problems... Thanks for your helpful input... =;-}

1) I always do this after install, too, but it would be better during install since I have to reassociate the install paths (e.g., OS installed from D, I change it to Z, but rhe registry still says the install source is D): just to verify, though, will this solve this problem--or will I have to still change the registry? In other words, is the regsitry path written BEFORE the vbscript runs? 2) Is it possible to have a script that would change TWO optical drives to, for instance, Y and Z (master and slave)? (Since I almost always have two drives in the systems I build, this would be, of course, more ideal.) 3) What about changing logical partition letters/names? Thanks

Good News: Successful build, finally. 1. Started with an nLite'd build of Pro SP1a, SP2 slipstreamed. 2. Ran nLite again, integrated all possible drivers I need (plus a few extras for potential future: nVisa RAID, RAID 5). 3. Integrated all add-on CABs (that I currently use) EXCEPT: 4. I did NOT include (as per rds_correia's investigations) Kels_AudioShellExt_addon_v1.1.CAB OR Xable_ContextAttributes-v1.1_addon.cab (just to be safe, because it might share similar hypothesized problems as shxZacam_AttributeChanger-v5.23_addon.cab--which I confused in my mind earlier). 5. I did NOT include XPize (as per userus' tip) anywhere in the process (I just left this out, because I was so frustrated at this point by the whole process--I think I'm on or around my 15th build now!). 6. I did not really compromise on any of my tweaks or component removals or customizations or options (because I was so confident that eliminating those three items above would eliminate my problems), with a few perhaps notable exceptions. 7. Tested the custom install ISO in VMware, which went flawlessly--except that, for some reason .NET 1.1 add-on CAB did not install, but .NET 2.0 did (but I may have simply not selected it--I was getting very tired, after all). 8. Have been testing it, looking at all the components, peering under the hood--and it looks like everything is where it's supposed to be and everything is functioning like it should ... Whoopee! Just for the sake of completeness I'm going to take that install, run nLite yet again, finish off the rest of the customizations that I held back on, and try to get that missing .NET in the install, too--then test it out one final time... 10. Noticed one odd thing (has not happened before): no audio adapter. Hmmmm... might be a VMware problem because I pulled out all default/legacy audio (leaving only integrated nForce)--but it also looks like I left out one INF that looked redundant (maybe it isn't). I'll try to re-integrate, then instruct VMware to use nForce audio only. We'll see... 11. Made mistake and removed lagacy ethernet, which VMware apparently needs (also noticed on previous build that VMware is using virtual Intel system drivers--so I would say to NOT remove such things as Intel IDE Bus IF you're testing in VMware ... Interestingly, thoug, I removed all display adapters, but VMware seems to be able to get along without them, even though it's using a SiS adapter...?)

Problems in variation again, latest build. Did it in this order: integrated SP2 into SP1a XP Pro using nLite, no add-ons, no drivers, no update packs, then stopped; then manually integrated XPize by itself, then stopped; then re-ran nLite, integrating drivers and the add-on CABs, RyanVM Post-SP2 Update Pack, and made ISO. Tested in VMware: WMI service disappeared again; framedynn.dll & srclient.dll missing again; IE and Outlook Express icons missing from desktop, start menu and quick launch bar, again. The rest of MMC left intact this time (due to XPize first and post-SP2 updates second), so no hideous problems there. However, I believe rds_correia is on the right track: one or more of the add-on CABs is causing all of the above. Shame on them...

rds_correia: any more narrowing it down? Sorry, I had to take a little longer break than I originally planned--I was just going at it for far too long, getting burned out. I'm starting up again tonight and hope to have it ironed out by the end of the week at the latest (I really need to get started on my backlog of clients that have been waiting for me to solve this mystery)...

Hmmm, the only two add-on CABs that we share in this ordeal is shxZacam_AttributeChanger-v5.23_addon.cab and Kels_AudioShellExt_addon_v1.1.CAB ... So I would perhaps concentrate on those two, at least for your end of the problem(s). My problems may be either or both of these AND the MMC/XPize conflict combined together, which conspire to make my life hell. I'll also report back ASAP. Right now, I'm so sick of all this, I'm going to treat myself to a movie (V for Vendetta), and relax...

rds_correia: let's see who can get to the bottom of this very annoying annoyance first! (I've wasted over a week and half now on this nonsense--and have five computer jobs waiting on me.) I think we can do it tonight...

rds_correia throws a wrench in the machine by saying that he doesn't use XPize, so now I'm puzzled--but one thing seems to be for sure now: one or more add-ons, or (more likely, as it is appearing), combination of add-ons, is causing the problems we're all experiencing in variations. After further testing of my last supposedly working install, I discovered that some essential networking components missing; however, this, in fact, may be a VMware problem now because I removed legacy networking adapter components which VMware might require to make an internet connection. Other than this, though, all the other myriad problems I've been having seem to have disappeared by replacing those MMC files that XPize seems to mess up. The thing is, if you look at that pre-release MMC 3 on MS, they list several known issues with using it that may or may not play into some of these problems. I'm am now going to test an install without XPize and without removing legacy networking components to see if this fixes everything--then, for whatever all the specific reasons, I will have identified the source(s) of at least many of our problems. More on this later after my next test build ... I'm sooo close... Anybody no the easiest way to just remove the MMC 3 from the RyanVM Update pack...?--just remove the kb exe file and the two mmc 3 files...?--then try integrating it (or is more complicated than that? will it mess up RyanVM's install...?)....

We are getting closer to the issue: after my working custom installs, I added different things in, one by one--none of the component removal seems to break it so far (I did not really expect it to), but adding in a collection of the add-on CABs severely broke it again ... Now to find the culprit(s). userus suggests that XPize doesn't work well with one of the updates (KB907265), so that could in fact be all there is to it (I wonder if the XPize Beta release might fix this..?), since this is among the CAB add-ons that I integrate in the hotfixes section. XPize would make sense, because of how it works, and because I just don't see how a few CPL, context menu and Windows Update add-ons could be responsible for breaking the installation so severely. So what I'm trying now is (I did not see the userus post before I started this, unfortunately): take my working install (with SP2 and RyanVM updates already integrated), MANUALLY XPize it (not using nLite to integrate XPize), THEN take nLite and finish the job. I thought perhaps this would overcome the conflict pointed out by userus ... However, I'm not hopeful, because I'm sure it's that XPize screws around with MMC 3.0 files that it shouldn't be touching! So here's an idea: take out MMC 3.O Pre-Release (KB907265) from RyanVM's Post-SP2 Update Pack, integrate everything as normal, then integrate MMC 3.0 afterwords...? Only problem, I don't know how to make MMC integration occur after XPize in the process--except to manually install after Windows is installed...? Or just give up on using XPize, until and if when it is fixed (XPize is not exactly mission critical--it's just cool in that it makes Windows a little less boring without bogging it down in like a lot of eye candy). (Does anybody know if the XPize creator is aware of updated MMC conflict?) Another idea: nlite with XPize and RyanVM Update Pack, then redundantly apply the Post-SP2 Update Pack (to fix the XPize-corrupted MMC) by running nLite again...? Surprising Update Okay, I actually got it to work without errors, like this (I thought it was just to simple to work): I took my previous working customized OS (already slipstreamed with SP2 + all SP2 updates, with a bunch of tweaks added and components removed), then manually applied XPize, then re-ran nLite to integrate drivers and make a couple of other changes, but I waited to make the ISO--instead I extracted with RyanVM SP2 CAB, took all of the mmc files (exe and dll), copy them over to my newest custom install, then fired up nLite again and made the ISO, then ran it in VMware ... (drum roll) ... with no errors. Can it really be that simple? Well, so far, everything seems to be intact (no missing services, mmc snap-ins, dlls, etc.). BTW, it appeared that only two mmc files were different in size: the mmc.exe and the mmcshellext.dll--so it's poosible that merely replacing these two will solve the whole problem. (?) My premature conclusion is that screwing up those two pesky files causes a cascade failure, preventing inclusion of at least 7 basic Windows services and 2 important DLLs, and thus severely disembowels the whole install. (It gives a whole new meaning to an Achilles Heel...) One side note that makes Microsoft suck on this issue: you can't check Windows update with your install until you activate it (they should AT LEASET allow you to see if you need any, show them to you, but not let you download and install them)--which obviously is not going to fly when (in this case) I would be calling them up 15 times to activate this copy...! So in order to check the stupid thing, I would have to crack a legitimate copy of XP. My experience with this whole WGA and Activation thing is it just causes legitimate and legal users(and custom builders like ourselves) continual annoyances, without stopping even a newbie hacker from cracking XP--in other words, it's just an id*** way to protect your product (punish legal users, p*** of OEM builders, make illegal users laugh--sure, that's a real good formula for protection and security). If any of you happen to ever speak to an MS representative, I encourage you to complain--I do and I have, and they will listen (believe it or not). Okay, no more soapbox. Sorry. For now, I'm happy that a long week and half of pulling my hair out in frustration may be over. Oh, and thanks to userus for the tip (I appreciate someone struggling to explain something in a language not native to them--I certainly couldn't have done it the other way around). So I hope that userus can understand this thanks at least.

After two more ISOs, I have one that finally worked: little or no removed components, moderate customization, RyanVM Update Pack 2.04, nLite 1.0 RC7, no integrated drivers, no other integrated CAB add-ons, no other hotfixes. On the third ISO, it broke again: I integrated all the rest of the add-on CABs I've been using, but still no drivers--I removed just a few more components. My conclusion: one or more of the add-on CABS is breaking the installation. (The components I removed are still less than I usually remove, without problems--and I did not even go near any remotely questionable components.) So now I'm going to try an ISO with the same components removed, but no add-on CABs: if it works, it's definitely the add-on CABs (I then will need to try an ISO with all the drivers, just to make sure they don't break anything--though I cannot see how they would). From that point, I will have to painstakingly, one by one, integrate the add-on CABs o figure which one is the culprit... Anybody got any ideas which add-on CAB(s) might be causing my problems? (The framedyn.dll and srclient.dll disappeared again--and enough services were ripped out to cause MMC to come up as blank interfaces: basically the same as in my previous posts.) It is NOT RyanVM update pack, it is NOT my SP2 CD files, it is NOT my Windows installation CD files: at this point, it is most likely one or more of the add-on CABs--or, perhaps less likely, that one of the tweaks/customizations/removals I usually do in nLite is not working the way it usually does... Hmmmm... Here we go again (over a week later)... userus: Do you mean to say that if I answer NO in the final popup box, that THAT could cause the problems I'm having? In other words, if I answer NO, then go back, it somehow breaks the process and causes errors? That would point to a problem in nLite itself then (and may account for the randomness with which these errors in appear accross many different users with many different systems). Hmmm...

Well, now it appears that other stuff is not getting integrated properly either (such as the CAB inegrations for Windows Update, Microsoft Update, Genuine Advantage Tool, etc.) ... and who knows what else ... Very disappointing. So something very basic and essential is afftecting my custom installs all of the sudden (which did not ever affect them before--with the exception of a single framedyn.dll error a couple of years back)--even though I've verified my steps (as I always do anyway) through the whole process. Hmmm... (I'm actually surprised that, with such essential things missing, it's not riddled with errors right at the outset ... Oh, weell, if I gave it more time...!) Guess I'll just hammer away at it AGAIN, trying another custom install. (I am at least using VMWare for my testing).

Just did another of several installs using nLite v1.07 with RVM Update Pack v2.04 (and various add-ons for CPL and context menu, as well many of the common tweaks of done since their inclusion), with the same fundamental problems as before. Althoguh, I instructed nLite to keep the various DLLs coming up missing (which superficially corrected the framedyn.dll and srclient.dll missing errors)--and even took out far, far less than I did before (or ever have, for that matter)--certain services do not even appear anymore: WMI and WMI Performance Adapter, COM+ Event System and COM+ System Application, MS Software Shadow Copy Provider, Distributed Transaction Coordinator and Windows User Mode Driver Framework...! What the...?! I do not, nor have I ever, taken these out--nor do I want to. The result, of course, is that you cannot start several of the other services, the dependencies tab is entirely missing, and so on. I've left more in than ever before--I've been very conservative and viligant about the tweaks--I've not identified anything importantly different than the many, many systems that I've done virtually the same way since the first version of nLite--I've had no errors whatsoever for an entire year building systems for clients (notwithstanding one nasty attempt with MCE) ... So I cannot perceive what is so radically different that is causing these gross errors and obviously missing components. I now have five computers and clients waiting on me (I've been trying to track down the problems for over a week now), so it's very frustrating and will potentially cost me jobs and money. I am thus at my wits end and at a loss of what to try next. I wonder if it's possible that a seemingly innocuous tweak or component for removal that I've always done somehow does something radically different than it used to, but unbeknownst to me (like taking out some crucial component that links all these things together)...? I do not, nor have I ever, indisciminately marked entire sections: I always painstakingly review each change, one by one--and, for the life of me, cannot identify anything even remotely questionable in my processs (like I said, I've done this over and over for so long now, that these errors and problems come as a complete suprise to me). I am quite suprised that, after all the people that seem to have related problems on this issue, no one has yet identified the unifying factor(s) most likely responsible for this. Does anyone have any suggestions as to some next steps in a logical progression to assist in remedying these problems? Do an install with no customization, no removal, no non-default settings at all (and defeat half the purpose of deployment in the first place)?

Well, I'm sorry to say that I've reproduced these exact errors (missing framedyn and srclient dlls), too. I have experienced this before, but not for a couple of years--and I've set up countless systems between then and now, all without any such errors. It was so long ago, I don't remember the cause--but I do not understand why it is happening now. I'm using the newest nlite and ryanvm packs, as always. I've tried three times, reconfiguring differently each time, and even using a newly downloaded SP2. I'm thinking that it must have something to with the SP2 integration, because my long error-free period occurred while using XP with SP2 already installed (Home and Pro). Perhaps there's certain yet-to-be-specified changes within the nlite customization features that conspire with the SP2 integration with XP Pro (Pro is what is causing the errors--and Corporate, which is the same as Pro--is what caused it way back when--I haven't seen the problem yet with Home, but I think all the Home versions I've worked with already have had SP2). As far as the WMI is concerned, for some reason the service is completely missing...! Now I did not, nor would I, take this out--so some setting in nlite (which we think is safe) must be taking it out unbeknownst to us. Any ideas on this one anyone? (Interestingly, the WMI driver extension service is still there.) This explains also why I see that the firewall/ICS and a couple of other services--while they appear there--cannot be started. The only other oddity I've noticed is that there is some newer setting that causes the IE icon to not appear on the desktop (you have to create a shortcut to it), even though the desktop settings say it is visible (and even though I specify that it should appear in the setup tweaks). This oddity has plagued all my nlite installations for, I think, the last two or three builds. Could any of this be related to these other problems somehow? PLEASE: has anybody had luck in correcting this after install? has anybody figured out anything more specific about the cause?