I just made a nlite cd and ran into some problems. When windows started after the intro {What i mean by "after intro" is after windows ask you for your username and other stuff} I got an error. "This application has failed to start because framedyn.dll was not found. Re-installing the application may fix this problem.” So i hit ok. Then i get another error. "Srclient.dll was not found". So i came here and search the forums for both dll files. I didn't find anything. So i ran a search in google and it brought me to this microsoft page. Here. So i did what is said and no luck. I know i can pop in the sp1 cd in and copy over the files but i was wondering if there is more to this than what is on the surface. There is more things that are wrong with it but it would be a long post. I will include the settings.ini to see if someone can tell me what i did wrong.

My first guess is that you have used Manual install and not cd boot to install Windows ?

There are some serious issues regarding manual install while using nlite, i didn't know this before but now that explains a lot of bugs reported which no one can reproduce.

Working on it.

However if you did boot from cd and got these errors tell me so that i can check it.

Thanks for your reply nuhi. I did do a cd install. No manual install. I personally don't like manual installs. There were also some strange things that i found out and will explain. In the start menu at the top where ie and outlook reside, usually it says Internet Explorer and Outlook Express. But it doesn't say that. It says Internet and Mail but next to internet the ie icon isn't there. But when you click on it brings up ie options and not ie. The only way i was able to acess ie was clicking on Windows update and then ie launched. When I go into device manager my video card wasn't recognized, but i inserted my own drivers. Got the 71.20's from guru3d but they didn't get installed. I uncheck videocard drives and old videocard drivers from the drop down list. I will let you know if there are more problems.

Those icons are "normal" if you remove IE and OE...
maybe you figured out wrong that rare issue when people think that Unselecting means removing ?

Also it may be your hotfixes if you integrate them...try without it.
And you may use VMWare or Virtual PC to save nerves.

Also, my 71.80 integrates just fine...be sure to REMOVE Windows Display drivers.

i remember i had exact the same problem on a very old version
it was caused the hive*.inf files r not stored as ANSI

@nuhi, he didnt remove IE and OE
look he attached the settings.ini file

Ah, I always forget to look at first post.

Looks to me that this is something unique and untraceable...but be sure to report if you keep getting this error with next version, then we'll talk more.

nuhi i forgot to add that with this whole setup i had intergrated ryan's hotfixes but for some reason they didn't work. after windows started up i went to windows update and all of the post sp2 fixes needed to be applied. i went to his site and checked out his faq and came across a faq question about framedyn.dll but it only applies to manual installs. It says to edit some files but i intergrated them through nlite. I emailed him and asked him how to probperly intergrate them and i did what he said was the proper procedure. Maybe this can shed some more light onto this problem.

Today i ran into this problem while integrating Ryan's pack and not editing properly txtsetup and dosnet.inf.

Recheck what you do or try without his pack to find your bug...this isn't caused by nLite...I'm 98% sure and that's pretty high.

do you mean maunally integrating or integrating with nlite?

Manually...or you overwritten it after nlite somehow.

But be sure to use newest nlite only with Ryan's 1.2

i had this problem too, its not nlites fault, u deleted the folder wbem , reinstall windows but leave this folder

I am using nlite 0.99.8 beta 3 and have been getting the same problem with the framedyn.dll after using nlite to integrate Ryan's 1.2, remove some things, and add some tweaks.

I found that I do not get the error if you add framedyn.dll and srclient.dll to the [Keep Box] section.


@MCT: my wbem folder still appears in the %system%/system32 folder.....so it's not getting deleted. But I am also getting another problem of the IE icon not on the desktop or in the start menu....along with the outlook express icon. Are these related to the wbem folder?

no, thats a known bug, the ie icon disappeared

i was going threw windir & removing folders i didnt think i needed, but i had made a batch file to remove wbem, which i didnt think i needed, but i did, everything is ok now that i deleted that line in my batch file, i thought maybe u done the same thing

Salvo2002, wait a second, this shouldn't be happening with latest nlite.
If you may at least virtually try it without Ryan's pack or any drivers to see if it's internal nLite mistake or integration.

what shouldn't be happening...the dll errors or the ie and oe icons or both??

Anything bad.

ok i will try using nlite and remove/tweak on a clean xpSP2 source....




I tested it on the xpSP2 source without Ryan's packs, and like you said I get no errors.....

should i try manually adding the packs to a clean source, and then use nlite? (before i was using nlite to integrate) or does it make a difference?

it *shouldnt* but try it anyways

Salvo2002, yeah, probably that full version of Ryan's have some other critical file updated and it causes an error...I tried only Lite one.
Integrate Ryan's only without using nlite at all and see if it causes problem.

Interesting. I ran in to the same thing, but I didn't integrate Ryan's VM pack thorugh nlite, I did it manually afterwards (full version). Files were edited correctly, but I'm getting the same problem with these two files missing.

Very curious. I'll try to post back here after I'm able to play with it more.

I manged to get rid of the errors by adding the 2 .dll files mentioned aove. However, I can access ad/remove [B]windows[\B] components in control panel so mabe they are not install correctly. Can someone else who has added the files please check this.....


Thanks

Rich

Wait, so how do I reproduce this problem ?
Are you using latest RVMPack...Home Edition XP or ?
Latest nLite 0.99.8b5 ?

Just to help you out guys...
I just checked mine which had the same problem, and here is my setup :

WinXP SP2 + RyanVM UpdPack 1.2.1
Both files (framedyn & srclient) are on the source disk
but seems not to be copied during setup process

but framedyn.dll is in txtsetup.sif
supposed to be copied but isn't

I bet it's due to the 6 trailing spaces on that line :
"framedyn.dll = 100,,,,,,,,3,3 "

Trying to simply remove those and coming back here to tell you what's up...

No framedyn.dll problem for me.

on 0.9.99 or something
just got this error too with latest beta and dutch update pack 2-5 (hp38user)
see lastsession

Me too. I've got the dll problems and the missing IE and Outlook express icons in the startmenu. So the solution should be to manualy insert the framedyn.dll and Srclient.dll? Or go to nlite advanced option and select the two dll to keep?

Is this also the solution to get rid of the missing IE and Oulook icons?

edit: I inserted the two dll's in the advanced tab and now i don't get the dll waring/error anymore. But The IE and OUtlook icons are still missing in start menu. It now says (allready did) internet and mail. When i press internet i get the configuration screen for internet explorer. The only way to get on the internet is by going to windows update

and we never heard of him again

isit hp38users pack or his guess now?

I have this same prob. Shortly after rebooting to desktop, win gives me an error, that "framedyn.dll" and "srclient.dll" is missing, or not working properly.

I've downloaded framedyn.dll and installed it into systemroot/system32 -folder. Now win doesen't give me that error at startup, but i cannot turn on - or view win firewall -panel at all.

It says WMI -service must be running or something like that. Also, i cannot install nForce4 firewall (program), because installer gives me an error, that WMI -service must be running in order to finish this install.

When i start WMI (Windows Management Instrumentation) nothing happens. When restarting, service has stopped once again.

I'm using nLite 0.99.9b and i've configured the following: Intergrate Ryans hotfixes (1.2), unattended setup, few os setting. SP2 was already intergrated on this media.

So, any tips to get this WMI service fully working?

I had exactely the same problem, Also no firewall and emule was not able to work proparly because of teh firewall. I could acces the firewall but it did block some ports! I dont know what is did to solve the problem. I think i just started all over again with a fresh win xp and sp2 and so on.

Yeah, i got my win-version working again (that missing framedyn -thing). I made a new one with nLite 0.99.9 with 1.22 ryan's pack. One thing more i did differently: i changed WMI -service from 'Manual' to 'Automatic'. Everything else was quite same.

Where do yu change the WMI-settings? After install of windows xp?

No, from nLite setup when creating new media. I can't remember where it locates, but try to find "services" tab somewhere.

I only see this error when my pack is integrated improperly (generally missing txtsetup.sif entries, which in turn angers sysoc.inf when it's executed). You guys should check your txtsetup.sif and see if the entries for my update pack are in it (you can see what entries should be there from the manual integration directions on my website). If they aren't there, then you can be certain that's what's causing the problem. And it means that there's a bug with how nLite adds those entries which causes them to not always be added. If they are there, then something else is causing your problems

I just recently started to experience this issue. Using the latest nLite with the latest full RVM Pack. I always integrate RVM manually prior to running nLite. I know it's more work but sometimes I just like to get in there do things myself.

All of the file entries (txtsetup, dosnet, etc.) seem to be in order before and after nLite does it's thing. I am wondering if the removal of any certain component with nLite is the cause. I think at this point, after four days of troubleshooting, I'm going to try nLite without removing anything at all. Just going to enable higher compression and merge cabs, which I realize is a little redundant with the RVM Pack process, but what the hell.

Dont know if this helps but I have the newest version of nlite and rvm pack (3-17-06) and i'm still having the same problem. I notcied that all the files are in the system32 folder but the applications are looking for the files in the system folder. Have not tried this yet but maybe someone can figure out how to modify the installation settings to extract it to both directories.

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?

If i do
1. Copy clean i386
2. Run Nlite RC7
3. Load my conf to Nlite, press next, next... "Apply changes?" i dont do anythig !!
4. Run manually UpdatePack-XPSP2-Rus(update pack for rus windows(ryan))
5. UpdatePack-XPSP2-Rus is integrated OK
6. "Apply changes?" press yes
7. Nlite do his jobs OK
I have this problem

But if i do
Run UpdatePack-XPSP2-Rus(update pack for rus windows(ryan)) first (do not run Nlite)
after Run Nlite -> all OK !

userus, and you find that weird?
You see update packs have some files which nlite updates but if you overwrite with update pack after nlite done it job once there will be a problem.

Update dont overwrite any files after nlite do his job, updatepack always run before nlite START HIS JOB i dont press button YES in window "apply changes".
How is work nlite - scan windistr -> configuring - > show window "Apply changes?" -> if YES strat job
I dont press YES in window "Apply changes?", nlite do not any changes, i press YES only after update integrated

ps. may be i'm stupid, or dont understand english?

So basically you keep nlite open in the background while upgrading?
I don't understand

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

Ok
1. copy clean distr
2. run nlite, configuring
3. press next next... while not see attached window
4. NOT PRESS YES(KEEP IN BACKGROUND)
5. run updatepack manually
6. when updatepack is finish
7. PRESS YES in attached window
8. have this problem

ps. My english is too bad and i can not explain in detail

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

I more detailed tested nLite and i found this problem
1. If i try apply only Tweaks, nLite do not change txtsetup and dosnet -> error missing nLite.inf and Srclient.dll

2. Call nLiteRF=ocgen.dll,OcEntry,nLite.inf,HIDE,7 from sysoc not work(he cnt work)
3. reason of my problem with UpdatePack-XPSP2-Rus, at moment of presence window "Apply changes?" nLite lock files txtsetup sysoc... , and UpdatePack-XPSP2-Rus can't change them, i don't know continues nLite lock this file when he itgrated Ryn automatic if yes -> error
4. HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlreg",0x00020000,"rundll32 advpack.dll,LaunchINFSection %SystemRoot%\inf\nlite.inf,T" I thought that this section from hivest will be added to registry, BUT on T34 windows RUN immediately this "rundll32 advpack.dll,LaunchINFSection %SystemRoot%\inf\nlite.inf,T"(try install calc.inf)
from sysoc nLite section work correct, i think not it is necessary to start form hivesft, all strings from RunOnce run on T13, some tweaks will be overwriten later(crashcontrol tweaks not work).

After nLite i have this strings in nLite.inf
[nLiteRF]
OptionDesc = "nLite"
Tip = "Windows component removal adjustments and tweaks."
Modes = 0,1,2,3
AddReg = S
[S]
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlreg",0x00020000,"rundll32 advpack.dll,LaunchINFSection %10%\inf\nlite.inf,nLiteReg"
what is %10% may be %systemroot%

i think ->
need add HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlreg",0x00020000,"rundll32 advpack.dll,LaunchINFSection %systemroot%\inf\nlite.inf,nLiteRF" to T or H C section in nlite.inf
[nLiteRF]
OptionDesc = "nLite"
Tip = "Windows component removal adjustments and tweaks."
Modes = 0,1,2,3
AddReg = S
[S]
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlreg",0x00020000,"rundll32 advpack.dll,LaunchINFSection %systemroot%\inf\nliteFinal.inf" nliteFinal.inf this is copy of nlite.inf without calling nLiteRF(nLite section rename to DefaultInstall )

Result -> form sysoc apply nlite.inf,nlite -> on t13(work runonce) apply nlite.inf,nliteRF -> from nliteRF add to runonce nliteFinal.inf call ->= all tweaks enabled

try to setup calc.inf(Rbutton -> setup)
from attached nlite.inf i have all tweaks are enabled

to nowinscenario:
MMC to come up as blank interfaces
if I correct has understood your problem then answer here -> u apply Ryn(or other update) he contains in itself KB907265 which does not be friends with Xpize ! do not apply Xpize!

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.

@nuhi,
As always, thank you very much for giving us nLite.
Great piece of software .
Too bad it needs DotNet...
But there's already so many tools out there nowadays that need DotNet that anyway it's starting to become "a must have" in every PC.

@userus
I'm sorry buddy but I'm affraid I didn't understand a word of what you were saying .
Maybe you could write it in your native language and we could use babelfish to translate it.
How about that?
I'm saying this because I get the feeling that you are closer to giving a good tip to nuhi than anybody else here.
And I would really like to get rid of this annoiance.
Anyway thanks for all your efforts so far.

@nowinscenario & @nuhi
I myself have been facing this problem lately on a lot of VMWare trials.
I even thought it could be related with VMWare so, silly me, I decided to try this on a real PC just to find out that it's a real...how shall I call it...a bug?
Anyway, just to let you know that:
- I always use XP-SP1a as a source.
- I sleapstream SP2 on it and close nLite.
- I download latest RyanVM pack and latest RVMIntegrator.
- I also download some RVM add-ons such as:

- I integrate RVMUpdatepack 2.0.4 and the RVM Add-ons with the integrator.
Now, if I don't remove stuff, such as for instance Internet Explorer, and I only integrate some hardware drivers and ask nLite to create and ISO everything works perfectly.
Which means, and correct me if I'm wrong, that this rules out RVMUpdate pack and the add-ons.
Now, if I remove some stuff from WinXP then I get a "rundll32.exe - Unable to locate component - This application failed to start because framedyn.dll was not found. Re-installing the application may fix this problem.".
And then I get a "RUNDLL - Error loading srclient.dll - The specified module could not be found.".
Everytime I right-click My Computer icon I get the srclient.dll message.
Hope I have sometime today to run some tests without RVM's update packs and add-ons.
Maybe I can try to narrow the possibilities to a point that nuhi can actually catch the s**ker .
BTW, I don't use XPize one my unattended XP CDs .
Cheers

I'm having the same problem. I've followed this step :

- nLite1.0RC7
- RyanVM Integrator (for french pack which isnt compatible with nLite)

At the final reoot, when my batch try to use taskkill.exe, it doesnt work because Framedyn.dll is missing. I'm gonna try in this order :
- RyanVM Integrator
- nLite1.0RC7

Hold on a minute!
I just did another trial with the same settings as before but this time I didn't apply RVMUpdate 2.0.4 or any of the add-ons AND I didn't add my SIS SATA drivers.
This time around the nLite'ed XP does not show any signs of framedyn.dll/srclient.dll being missing at all.
Everything is working as it should!
Now, I'm going to use the same settings.ini and I'm going to add my SATA drivers and I'll test it with VMWare.
If it works, I'll make another nLite'ed XP based on the same settings.ini and this time I'll add RVMUpdate 2.0.4 with nLite and not with RVMIntegrator -> For now, no add-ons will be added.
If everything works fine, I'll give it another shot using the same procedure and this time adding the SATA drivers, adding RVMUpdate 2.0.4 AND I'll only add add-ons that I have always worked fine, meaning, no new add-ons that I downloaded lately.
I'll catch the little SOB that has been giving me sleepless nights .
Cheers

EDIT: I have just finished an nLite'ed UACD with RVMUpdate 2.0.4 integrated from nLite's options and using the already mentioned Settings.ini file.
This means that it's either RVM_Integrator or one of the add-ons.

I don't have time to read carefully but here goes something important:

Never keep nlite running in background while upgrading your source because nlite keeps some important files in memory for fast access and on apply it overwrites them with modified versions...meaning if you kept it at apply and did something you'll make hell.

Just turn it off until you think on using it in one go.