Replacing system files; manual updates; InUse.exe; new utility... SwapSysFile.exe

  • Thread starter Thread starter Scott Kelly
  • Start date Start date
S

Scott Kelly

I needed to be able to manual update certain system DLLs on my Win XPe load.
I tried InUse.exe, but b/c of WFP - it would not work.

I wrote a simple VB app that uses the MoveFileEx() functions to rename the
current DLL, then move over the new one. After doing this process, you
should reboot. On reboot, windows will then delete the old DLL. See the
source for more information.

I have posted SwapSysFile.exe and the source on xpefiles.com. See

http://www.xpefiles.com/a_file.cfm?custid=Updates&fileid=SwapSysFile.zip&gro
upName=Other

If you have any questions - let me know. I have tested it on my Win XPe
system and it works great. I can not garantee it will work perfect for you.

Don't forget - if you are using EWF to commit the changes before rebooting.
 
Scott,

I checked the zip and sources. It is a nice component!

This is not a complain but rather a suggestion...
Btw, why VB? I am not a big fan of VB, even though your code looks pretty clear and is good in use. As far as I understand your .exe
will require MS VB engine (6.0?) to be included into the image. This is a big chunk of space on HDD and in RAM if you don't plan to
use VB in your image. Do you plan to replace the app with C++ implementation? That should be a few lines of code.
 
Just thinking aloud.

Why not modifying registry directly with "reg.exe" and .bat file?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations ....

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

KM said:
Scott,

I checked the zip and sources. It is a nice component!

This is not a complain but rather a suggestion...
Btw, why VB? I am not a big fan of VB, even though your code looks pretty
Click to expand...
clear and is good in use. As far as I understand your .exe
will require MS VB engine (6.0?) to be included into the image. This is a
Click to expand...
big chunk of space on HDD and in RAM if you don't plan to
use VB in your image. Do you plan to replace the app with C++
Click to expand...
implementation? That should be a few lines of code.
 
Hi, Scott!
I needed to be able to manual update certain system DLLs on my Win XPe load.
I tried InUse.exe, but b/c of WFP - it would not work.
Click to expand...
strange - in my case inuse.exe works perfectly.
The only one note - the replaced files should be located on the same
partition. It's "move" not "copy" operation.
I made QFE828741 and QFE835732 with InUse and have no any problem.
 
Nikolai,

InUse.exe does import sfc.dll (WFP). I think you just happended to include
SFC feature ("Primitive: Sfc" component) into your XPe image.
In general, the feature may not be included in to a XPe image. I guess this
is what Scott meant.

KM
 
Hi, KM!
Nikolai,

InUse.exe does import sfc.dll (WFP). I think you just happended to include
SFC feature ("Primitive: Sfc" component) into your XPe image.
In general, the feature may not be included in to a XPe image. I guess this
is what Scott meant.
Click to expand...
Yep, you're 100% right.
 
KM (et al),

I wished I would have found the MoveEx from jsiinc.com - it would have saved
me some work. Oh well.

My implementation is a big VB app and requires all that goes with it. For
my purposes - that was ok.

The program is simple enough that someone versed in "C" could rewrite it. I
just did it in VB b/c that was what was handy.

Thanks,
Scott
 
Back
Top