Hi nuhi ,
I think I get the picture but I only open nLite when I have everything set to start building a new UACD.
And for the record, I think this has something to do with RVM addons or RVMIntegrator.
I am currently installing a new UACD on a VMWare that I built ONLY using nLite.
No RVMIntegrator used this time.
I'll let you know when I'm done.

@all,
For those having this problem: do you install RVM addons or use the RVMIntegrator?

Cheers

UPDATE: just finished installing that UACD and the problem is back.
Which means that RVMUpdate 2.0.4, RVM Integrator 1.2.2 and nLite 1.0rc7 don't have any problem.
The issue is add-on related.
I'll try to catch the little SOB and I'll let you know afterwards.

Cheers

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...?)....

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...

I have successfully narrowed it to the following addons from RyanVM site:

- Kels_AudioShellExt_addon_v1.1.CAB
- Kels_MemTest_addon_v1.cab
- Kels_myuninst_addon_v1.33.CAB
- MrsP_PowerOff_Addon_v3.0.1.3.cab
- MrsP_Rainlendar_Addon_v0.22.1.cab
- MrsP_uTorrent_Addon_v1.5.437-QL.cab
- shxZacam_AttributeChanger-v5.23_addon.cab
- Siginet_Codecs_OpenSourceMpeg_Decoder_Splitter1.0.0.1_Addons_Beta1.1.cab
- Xable_Foxit-v2.0_addon.cab

Please note that I chose NOT to install these on a random choice.
Some of these addons are quite young and some of these addons are quite old.
One thing's for sure: I have full confidence on their authors and for safety sake I have downloaded them again and will play with them tomorrow since it's already 2:30am.
Cheers

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: 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)...

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...

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...?)

@nowinscenario,
Hey there ,
Sorry for taking so long to reply but my life has been a mess lately.
Actually I haven't look any further into this mistery.
I have done all my XP installations with an nLite'd XP that is running perfectly.
I'm attaching my settings.ini so you can see what I included and what I removed .
Those other addons that I did not include...well...they're not essencial to my work.
So for now I'm happy with what I have.
Cheers

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... =;-}

FYI in the Audioshell Addon, the AudioShe.inf is MISSING a ; at the begining of the first line. If you place a " ; " there, framedyn.dll and srclient.dll errors should disappear on systems where you are installing Audioshell Addon.

I just did a test where I ran Integrator 1.2.2, RVM 2.03, 2.04 and 2.05 and ONLY added Audioshell. That was it, nothing else. I didn't even make it unattended to simplify things. Received framedyn.dll and srclient.dll errors. I then corrected the INF after discovering the issue and burned a new ISO with the corrected file, and obtained a perfect install.

I am having this issue now. I have posted on RyanVM:

http://www.ryanvm.net/forum/viewtopic.php?t=4800

Very frustrating to say the least...

So explain to me how did you manage that please?

Clean Windows installation files?
Then RVM integrator or what?
Then nlite with what preset, attach it...

You have to track down the addon that is causing it...

And sometimes it is not as simple as a single addon either!
I had this problem for over a month before finally working out which two addons were responsible - both worked perfectly on their own and each had worked fine in previous versions but I had one particular combination that just didn't want to play ball. Took hours and hours to track down.

Mandarin, how about some details, it's fixing time at the nLand?

@nuhi here is an example of 2 addons that work fine apart but MIGHT create a framedyn.dll error when integrated together, they have the same [sysoc] tittle http://www.ryanvm.net/forum/viewtopic.php?p=35060#35060

Visual Task Tips and Visual Tool Tips

Both addons have been updated several times since so I don't see the value in you spending time on those particular ones. But for info one addon was Foxys Nirsoft Collection large v1.5 which would never work for me with Kels Uber pack v9.9.5. Changing either would solve the problem and I don't get the issue with either of the updated addons.

I can understand Ricktendo's issue because both of those addons are variations of each other - you would never usually use both together on the same system.

Ok if they updated them so that they don't clash any more then I won't bother with it. Thx for the info.

Ran into some problems today.

First i did wmp11 with booogies tool.

Then i used nlite to integrate those.

RVMUpdatePack2.1.11.7z
RUPUpdates-2.1.11.8-Addon.7z
IE7-KB928090-WindowsXP-x86-enu.exe
IE7-KB929969-WindowsXP-x86-enu.exe
IE7-WindowsXP-KB933566-x86-ENU.exe
IE7-WindowsXP-x86-enu.exe

This was the first error i ran into, got it 4 times i think.





Then later when i came into windows, it came with Framedyn.dll and Srclient.dll, my internet explorer was greyed out aswell.

This is with the lastest release of wmp80 from boooogie and nlite beta 1.4


edit; forgot to mention this was on a clean xp pro x86.

wazer, move IE7 hotfixes below IE7 itself in the integration screen. Sort them all by the build date first.

Thanks nuhi for the tip, ill try:)=

i got this error today after using Nlite version 1.4 (which i presume is the latest) to only update a Windows XP sp2 CD (msdn original cd) with one hotfix, namely kb888111xpsp2.exe, i did not use any other tool like Ryan's ones mentioned earlier in this thread.

once I apply the hotfix i click on the make iso button and then i'm done, final step is to mount the completed iso in daemon tools and run rissetup to 'add new image' on my RIS server.

steps to reproduce:-

1. start nlite, point to c:\xp_source when asked.
2. click next and ignore any last session, then next
3. select 'hotfixes addons and update packs' and 'bootable isos' and click next
4. on the hotfix page click insert and point to path of hotfix exe file C:\hda hotfixes\hotfix2\KB888111_Supported_OS_All_Languages\us\x86fre
5. click next, click make ISO.
6. once done, close nlite, open daemon tools, select mount image, browse to winlite.iso
7. click start, at run type 'rissetup' click add new image and it'll complete adding your edited windows xpsp2 cd iso.
8. pxe client computer to test the above

so whats going on here ???

additional note, during RIS setup.exe complains that it cannot find/copy nlite.inf, and I resolved that by doing this

cheers
anyweb

i've just resolved the Framedyn.dll error described in the post above.

it seems the nlite.inf error mentioned above is giving a clue to the issue, as once i manually expand the file and copy it to my RIS source, the installation proceeds with no errors and the Framedyn.dll error is now gone.

can anyone explain why the nlite.in_ file remains compressed ???

i'll start searching the forums now to figure out why that is happening....

Im having the same problem, and its driving me nuts... ive attached my last .ini i can fix the framedyn.dll problem but not the srclient.dll


thank you