SFXCAB.EXE
#1
Posted 23 April 2005 - 01:47 PM
#2
Posted 24 April 2005 - 03:11 AM
SFXCAB's are created only by Microsoft, and there are no tools, no documentation or anything else available to help others create SFXCAB's.
The /integrate option btw is passed to UPDATE.EXE, which then examines the UPDATE.INF and does the slipstream - SFXCAB.EXE doesn't do much itself really. /integrate will FAIL if UPDATE.INF is not "signed" - that is, if it does not contain a reference to a Microsoft signed .CAT file with a checksum of the .INF itself. You'll need to "help" UPDATE.EXE overcome this and similar other "shortcomings" just to make it do anything at all btw.
Is /integrate the only reason that you want to create SFXCAB's in the first place?
Best regards,
Gurgelmeyer
#3
Posted 27 June 2006 - 11:43 AM
Quote
Thanks.
#4
Posted 30 June 2006 - 04:08 PM
scratch that. i take that back. maybe the only to overcome the update.exe problem is to have MS digitally sign your package so that they can create a CAT file for it. that might be next to impossible.
This post has been edited by erpdude8: 30 June 2006 - 04:33 PM
#5
Posted 12 November 2007 - 01:21 PM
1. Hex edit one update file. Delete after MSCF part. So u have sfx module. lets name it cab.sfx
2. Compress all folder or files with make cab. lets name it files.cab
3. copy /b cab.sfx+files.cab files.exe
4. Hex edit to run files after extract. For example. u want to run setup.exe
Search setup.exe in files.exe.
There is 20 00 in front of setup.exe
Chance it to 60 00.
Done.
Run your sfx cab file.
#6
Posted 26 February 2008 - 06:04 PM
eryen, on Nov 12 2007, 01:21 PM, said:
you mean "create", eryen. you've gotta use some spellcheck in your post.
Quote
2. Compress all folder or files with make cab. lets name it files.cab
you mean makecab.exe
Quote
4. Hex edit to run files after extract. For example. u want to run setup.exe
Search setup.exe in files.exe.
There is 20 00 in front of setup.exe
Chance it to 60 00.
Done.
Run your sfx cab file.
okay. since I may want to create SFXCAB like NT4 packages, can I use hotfix.exe instead of setup.exe listed in step 4?
#7
Posted 26 February 2008 - 06:32 PM
just edit HEX:20 00 to HEX:60 00 in front of your program.
#8
Posted 27 February 2008 - 09:55 AM
Quote
What MSCF part? There is more than one instance of MSCF. Look in any NT-based update file in Notepad or Wordpad (or even in a hex editor like XVI32) and you will find that there are three instances of "MSCF". So which MSCF part do I delete? Look very carefully.
This post has been edited by erpdude8: 27 February 2008 - 10:01 AM
#9
Posted 27 February 2008 - 02:31 PM
Quote
what about using CABARC.EXE to make CAB files? Seems to be easier than using MAKECAB.EXE.
Also, have you tested your own methods of making SFXCAB files on an NT-based Windows computer and did it work or not?
This post has been edited by erpdude8: 27 February 2008 - 02:33 PM
#10
Posted 27 February 2008 - 02:55 PM
erpdude8, on Feb 27 2008, 02:31 PM, said:
Ok. I finally got my SFXCAB file to work now, eryen. I had problems creating CAB files with MAKECAB.EXE, so I used CABARC.EXE instead. The CAB file I created needed to be created using LZX:21 compression with CABARC.EXE. Then I copied your SFX file with the CAB file (compressed with LZX:21 compression) and then hexed "20 00" to "60 00" before the hotfix.exe file and now running the SFXCAB file works.
thanks for the MSCF.SFX file. It's version 6.1.22.4. Other versions of SFXCAB.EXE don't seem to work for me while the one you posted worked well.
This post has been edited by erpdude8: 27 February 2008 - 03:05 PM
#11
Posted 27 February 2008 - 05:54 PM
There is at least three type of fsx for cab file.
The one i send here working good.
One from IE7 updates can extract file but not running setup. And another one give me allways error.
Lucky me. Found good one at first run.
This post has been edited by eryen: 04 March 2008 - 02:08 AM
#12
Posted 12 March 2008 - 03:57 PM
eryen, on Feb 27 2008, 06:54 PM, said:
There is at least three type of fsx for cab file.
The one i send here working good.
One from IE7 updates can extract file but not running setup. And another one give me allways error.
Lucky me. Found good one at first run.
Did you know that someone in the "hotstream" project on this board actually got their grubby paws on the actual sfxcab.exe utility? It's really irritating, because he says he won't share it.
#13
Posted 04 February 2010 - 11:51 AM
dragon695, on Mar 12 2008, 01:57 PM, said:
and who exactly what that person be, dragon695? [name please]
maybe because that person is not authorized by M$ to share the tool.
oh well
This post has been edited by erpdude8: 04 February 2010 - 11:51 AM
#14
Posted 27 August 2010 - 06:18 PM
I'm trying the hex editing trick with a program called HxD. But I always get "C:\...\.exe is not a valid Win32 application".
I even took the sfx from this thread (the rapidshare link) and i did "copy /b mscf.sfx+...." and made an EXE. Then I hex edit that with HxD and make it identical to mscf.sfx that I downloaded from here and it works perfectly.
So why won't it work when I try to get the MSCF.SFX from Windows xp sp2 update file or internet explorer 8? both those use SFXCAB but I can't make it work.
Any help please?
#15
Posted 11 June 2011 - 11:38 AM
#17
Posted 14 June 2011 - 10:39 PM
WildBill said:
12. Compress your files:
cabarc -m LZX:21 -p -r N ..\outfile.cab *.*
13. Patch the created .cab file so that it knows to execute update.exe. You'll need a hex editor for this (e.g. xvi32). Look for the update\update.exe entry toward the beginning of the file. Before it there should be a 20h byte. Change that to 60h which will flag it as an auto-execute file.
14. Prepend the MSCF.sfx file before the .cab file to make an installer:
copy /b MSCF.sfx + outfile.cab outfile.exe
15. Rename outfile.exe to something appropriate to the patch and language:
ren outfile.exe Windows2000-KB######-x86-XXX.exe
#18
Posted 24 June 2011 - 12:52 AM
regards...
#19
Posted 24 June 2011 - 12:57 AM
thanx...
#20
Posted 24 June 2011 - 01:43 AM
Update.ver doesn't seem to matter AT ALL. It can be empty and the update still installs/slipstreams fine. The one that matters is update.inf.
- ← setupapi.dll and WinXP SP1.0a
- Windows NT4 / 2000 / 2003
- How to get around the 2047 characters CMD string limitation →



Help


Back to top









