SOLVED: Framedyn.dll & srclient.dll missing error

[glaurung]

ETA2: The problem was not with my winnt.sif - Evidently Nlite is not able to handle integrating XP SP3 under Win2k, and the only indication of a problem is that the updated source will throw these file missing errors after install completes. I created a slipstream inside a VPC running XP and it worked correctly.

Edited to add: Have now tried a virgin copy of XP SP2 with no updates and no alterations except for the winnt.sif file - still got the error. This makes no !@# sense. I've rolled back to virtualpc 2004 and am trying it again. If that doesn't fix this problem, my next recourse is to try it without an unattended file and see what happens then. @#$%^&*! Arrgh!

I've been getting the framedyn/srclient not found error. I've been paring back the things I've added/changed from the base install in an effort to figure out what is causing it, to no avail.

Latest attempt: I told nlite to integrate SP3 into a clean copy of XP Pro SP2, then dropped my winnt.sif into i386 and told nlite to make an ISO. I did NOT use any of the other options - no tweaks, no reducing, no switchless installers, nothing. Installing from ISO under virtualPC 2007 on a computer running windows 2000, I got the dreaded Framedyn/srclient error.

Google tells me that this error was cropping up a lot a few years ago, but mostly for people using RyanVM or doing other complicated stuff. I haven't done any of that - the only thing I can think of that's causing it is either a) trying to do the slipstream for XP on a computer running windows 2000, or B) using virtualpc 2007 instead of an older version (up until now VPC2007 has run fine for me, but you have to hack the installer to get it to run under win2k).

Was the source of this !@#$% annoying issue ever found? Is there a fix?

Attaching my session.ini file and my winnt.sif

Last Session.ini

winnt.sif

Edited June 8, 2010 by glaurung

[johnhc]

glaurung, what do you mean by "dropped my winnt.sif"? I see that it is not an nLite created winnt.sif, so I have no idea what that could cause. I am also not aware of anyone using W2000 to create an XP ISO. I have been around a couple of years and have not seen this problem before. Please try running nLite under XP, and let it use the winnt.sif that is created. You can do this under VirtualPC. I also do not think VPC is the source of your problems. If you want to see if it is a problem with slipping SP3 under W2000, then run again but do not integrate an SP and see if it works (use the nLite winnt.sif) Enjoy, John.

[glaurung]

glaurung, what do you mean by "dropped my winnt.sif"? I see that it is not an nLite created winnt.sif, so I have no idea what that could cause. I am also not aware of anyone using W2000 to create an XP ISO. I have been around a couple of years and have not seen this problem before. Please try running nLite under XP, and let it use the winnt.sif that is created. You can do this under VirtualPC. I also do not think VPC is the source of your problems. If you want to see if it is a problem with slipping SP3 under W2000, then run again but do not integrate an SP and see if it works (use the nLite winnt.sif) Enjoy, John.

It's a customized winnt.sif - nlite doesn't have the ability to set some allowed and documented settings in winnt.sif, so I put it together myself by hand. I was just drag/dropping it into the 1386 folder before hitting the "make ISO" button.

I'll try running Nlite under VPC later today or tomorrow, once I get a working XP installation (which may take a while).

[johnhc]

It's a customized winnt.sif - nlite doesn't have the ability to set some allowed and documented settings in winnt.sif, so I put it together myself by hand. I was just drag/dropping it into the 1386 folder before hitting the "make ISO" button.

I'll try running Nlite under VPC later today or tomorrow, once I get a working XP installation (which may take a while).

glaurung, I edit my winnt.sif after running nLite to set some NIC parameters that are not handled properly. I suggest you do the same or at least make sure the nLite produced winnt does not contain anything needed that yours does not have. Enjoy, John.

[fdv]

The fix is easy, but this says "solved." Is it?

The fix is editing TXTSETUP and LAYOUT so that

= 1,,,,,,,,3,3

is changed to

= 1,,,,,,,2,0,0

for framedyn and srclient

The byte counts of the files must stay the same. I will avoid 30 minutes of typing to explain how and why, etc and just say: replace

,_x,

with

,,

so that _x disappears from both (TXT... and LAY...) files.

Edited June 10, 2010 by fdv

[glaurung]

The fix is easy, but this says "solved." Is it?

The fix is editing TXTSETUP and LAYOUT so that

= 1,,,,,,,,3,3

is changed to

= 1,,,,,,,2,0,0

for framedyn and srclient

Yes, the problem appears to have finally been solved by doing the SP3 slipstream under XP instead of 2k. However, I very much appreciate your reply because now I know how to fix it manually -- thanks!

[Zorba the Geek]

I am one of three people that I know of who are still creating update packs and addons for Windows XP, and the framedyn.dll/srclient.dll not found error is a recurring problem during the development of my addons that I have never been able to get to the bottom of.  When I do make changes that fix the problem I cannot remember what I did to make it go away.

According to setuperr.log srclient.dll could not be registered because a specified module could not be found.  This means that there is a missing dependency, which in this case is framedyn.dll.  In fact framedyn.dll has not been copied to System32 for some reason   In txtsetup.sif framedyn has not been assigned a destination directory which means that it's destination is defined in an INF file, but I have searched all the XP INF files using Notepad++ and it is not there, so what controls it's copying to System32 is a real mystery.  Also msjava.dll is missing in the dependency tree, but it is not included in I386 or a standard XP installation.

The same issues apply to dgnet.dll not being registered.

eventcls.dll and swprv.dll were not registered and the only missing dependency is the non existent msjava.dll.

According to setuperr.log mofcomp.exe could not be registered and investigation shows that it is not present in the wbem folder.

I have received exactly the same setuperr.log entries multiple times during the development of various addons with the same missing shortcuts and missing wbem modules, which suggests that there is a single cause each time.

 

[Zorba the Geek]

After some experimentation I have concluded that this problem is caused by data corruption at one of the stages before Windows is installed in a virtual machine.  Repeating all these stages for my addon resolved the problem.  Here are the stages that need to be repeated:

• copy contents of INF and INI files in addon/update pack to Notepad and save them from there
• Build new 7z or CAB archive
• Copy Windows source from from ISO
• Use Poweriso or similar to build the ISO rather than the built in ISO maker in the integrator.