• fsfikke
  • DriverPacks newbie
  • Offline
  • From: The Hague, Netherlands
  • Registered: 2006-10-24
  • Posts: 4

Topic: Framydyn.dll & srclient.dll

After integrating the newest driverpacks on my Dutch XP Home DVD I get two errors after the install at bootup.
Two popups informing me that framedyn.dll as well as srclient.dll cannot be found. This happened on my English DVD too.

The post-sp2-update pack from RyanVM also had problems with this. It had something to do with unicode text formatting I think.

On my latest DVD I tried only integrating Graphicks PackB and the Mass storage drivers. This still creates the error.

I hope there is a solution for this, because my latest DVD with driverpacks gives me the 0x0000007b errors...

Thnx in advance!

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Framydyn.dll & srclient.dll

Name: SRFirstRun
Filename: srclient.dll
Command: rundll32 srclient.dll, CreateFirstRunRp
Description: Created by execution of the Windows XP sr.inf file, which installs the Windows XP System Restore feature, needed for example when installing System Restore into Windows Server 2003. This file should only be found on initial installs/re-installs. It is required for Windows to function on first boot.
File Location: %System%
Startup Type: This startup entry is started automatically from a Run, RunOnce, RunServices, or RunServicesOnce entry in the registry

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: Framydyn.dll & srclient.dll

hi fsfikke

do you know what chipset this motherboard has?
Some mass storage controllers are giving trouble in ne incarnation, and not in other, and some will refuse you access when another mode is chosen in BIOS.. so we'd like to know at least something more about your rig.

The file framedyn.dll, is required for the Windows Management Instrumentation (WMI) processes within windows to operate correctly.

http://support.microsoft.com/kb/319114

I'll be running a couple live setups today, using latest packs, will see wether i have that issue too.
(did not have it four days ago, suspect it won't happen now.)

what operating system do you run on machine you do the slipstraming on?
could you post a base-log?

The answer was 42?
Kind regards, Jaak.
  • fsfikke
  • DriverPacks newbie
  • Offline
  • From: The Hague, Netherlands
  • Registered: 2006-10-24
  • Posts: 4

Re: Framydyn.dll & srclient.dll

Hi Jaak,
Thanks for your reply. I think I fixed the srclient.dll problem thanks to you. It tries to run after booting but he cant find it. The srclient.dll is located in the system32 dir. If i execute the rundll32 srclient.dll, CreateFirstRunRp command it does run. After that I removed in from HKLM\softw\micr\wind\curver\run.

The framedyn problem is still there unfortunatly. It happens on every computer i install it to. I created the DVD with a XP Pro (english) and also tried in on a Dutch XP Home, same problem.

Btw, Did you see these topics on Ryan's site?  http://www.ryanvm.net/forum/viewtopic.php?t=2872 http://www.ryanvm.net/forum/viewtopic.php?t=1033
Maybe they can help to understand what causes the problem.

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: Framydyn.dll & srclient.dll

srclient.dll & framedyn.dll errors are not DriverPacks-related. They're caused by an UpdatePack or by removing to many things with nLite.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • muiz
  • Vista / 7/8 Driverpacks Team
  • Offline
  • From: Netherlands
  • Registered: 2006-07-01
  • Posts: 1,555

Re: Framydyn.dll & srclient.dll

Bâshrat the Sneaky wrote:

srclient.dll & framedyn.dll errors are not DriverPacks-related. They're caused by an UpdatePack or by removing to many things with nLite.

Yep nlite does this  sometimes with updatepacks (hotfix)

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/VVyo3dzRp1allVk-OCdyukcaj701mcdrrsdDOyX2wK8/perpetual:forever/userbar/admin-1.png
DONATE!
HWID's Tool     Read BEFORE you post
  • fsfikke
  • DriverPacks newbie
  • Offline
  • From: The Hague, Netherlands
  • Registered: 2006-10-24
  • Posts: 4

Re: Framydyn.dll & srclient.dll

That's strange...

With applying RyanVM's updatepack to a Dutch XP CD you have to enable the 'convert unicode to ansi' option, if you don't you get these errors. So when I had my perfectly working CD and updated it with the latest updatepack and driverpacks all of a sudden I got this error on my Dutch and my English CD. So I immediately thought the updatepack was causing this problem. I couldn't help this so I took the original CD and only updated the driverpacks. Guess what? I got the same errors. And I only used nLite to create the image file.

  • muiz
  • Vista / 7/8 Driverpacks Team
  • Offline
  • From: Netherlands
  • Registered: 2006-07-01
  • Posts: 1,555

Re: Framydyn.dll & srclient.dll

try not to use nlite, problem solved smile

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/VVyo3dzRp1allVk-OCdyukcaj701mcdrrsdDOyX2wK8/perpetual:forever/userbar/admin-1.png
DONATE!
HWID's Tool     Read BEFORE you post
  • Registered: 2007-02-20
  • Posts: 7

Re: Framydyn.dll & srclient.dll

I am seeing this exact same problem with the latest RVM update pack and its Integrator. There is something in the driverpack integration which causes these errors. On top of the missing files, IE doesn't work anymore.

Last edited by Pistolero (2007-02-20 06:51:58)

  • muiz
  • Vista / 7/8 Driverpacks Team
  • Offline
  • From: Netherlands
  • Registered: 2006-07-01
  • Posts: 1,555

Re: Framydyn.dll & srclient.dll

Works like a charm here.....and on many pcs's we install here every day.

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/VVyo3dzRp1allVk-OCdyukcaj701mcdrrsdDOyX2wK8/perpetual:forever/userbar/admin-1.png
DONATE!
HWID's Tool     Read BEFORE you post
  • Registered: 2007-02-20
  • Posts: 7

Re: Framydyn.dll & srclient.dll

muiz3 wrote:

Works like a charm here.....and on many pcs's we install here every day.

I don't doubt that, however I think the issues I was seeing were due to unicode against ANSI handling by the BASE app. Let me explain:

My usual build process is as follows,

1- Copy source i386 folder from XP-SP2 VLK CD
2- Using the RyanVM integrator, merge update pack and addons
3- Using nLite, apply unattended options and hacks
4- Apply latest DriverPacks with the latest base
5- Create bootable ISO
6- Test on VMWare

The above procedure has *always* worked like a charm, until the latest RVM update pack came out. I started getting a bunch of files not copied and apps not functioning, such AS IE not even starting. These problems *only* occurred if I slipstreamed any DriverPacks into my DVD.

Here is what I did to finally get the DVD to work as advertised:

1- Copy source i386 folder from XP-SP2 VLK CD
2- Apply latest DriverPacks with the latest base
3- Using nLite, apply unattended options and hacks
4- Using the RyanVM integrator, merge update pack and addons
5- Create bootable ISO
6- Test on VMWare

This tells me that maybe the BASE app is handling the INF files differently than the RVMI or nLite.

Worth looking into, IMHO, as the DriverPacks are one of the most kick-ass things ever invented, and they should be kept datacenter grade.

  • Registered: 2007-02-20
  • Posts: 7

Re: Framydyn.dll & srclient.dll

Hi all,

Unfortunately, this issue was not addressed in the latest release. How come applying the DriverPacks last in the build process always worked hunky-dory until ver 7.x came along? While i do understand that you have not experienced this particular problem, it is still a very real issue for more than one user out there, and ignoring it did not make it go away. Don't get me wrong, I think you guys are doing a bang-up job of keeping this project alive and kicking, and I have nothing but the utmost respect for your abilities, which far surpass  my own, this is why I humbly ask for your assistance in this matter.

Thanks!

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: Framydyn.dll & srclient.dll

I can assure you that this problem cannot be caused by the DriverPacks BASE, nor by the DriverPacks. It has always been a problem caused by either nLite or UpdatePacks.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website