makecab & expand command lines
Hi,
I want to make a wise script which expand cab-files to my computer. I made the cab-files with the command line makecab.exe /f "mycab.ddf". Now I have the folders "disk 1" until "disk 10" with the included cab-files and under the root folder a setup.inf + setup.rpt file. How can I automatically expand this file now with a wise script to my machine?
I want to make a wise script which expand cab-files to my computer. I made the cab-files with the command line makecab.exe /f "mycab.ddf". Now I have the folders "disk 1" until "disk 10" with the included cab-files and under the root folder a setup.inf + setup.rpt file. How can I automatically expand this file now with a wise script to my machine?
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
IIRC, MakeCAB creates Windows-type CABs (as opposed to InstallShield-tyupe CABs) so the Windows XP SP2 Support Tool EXTRACT.EXE should be all you need.
Alternatively, use Explorer's built-in CAB handling by right-clicking on the CAB and selecting an appropriate menu item, e.g. Explore.
Lastly, you could use the normal DOS tool EXPAND.EXE.
Alternatively, use Explorer's built-in CAB handling by right-clicking on the CAB and selecting an appropriate menu item, e.g. Explore.
Lastly, you could use the normal DOS tool EXPAND.EXE.
Posted by:
mklaeser
14 years ago
Thanks, but I think I made something wrong in the ddf-file header. If I try to expand the cab-file I get a error message " Install.cab is not Disk 2 File Name 2". Expand command couldn't find the "Disk 2" folder to continue with extracting of the files.
Header
.Option Explicit
.Set Cabinet=On
.Set DiskDirectoryTemplate=CDROM
.Set CabinetNameTemplate=Install.cab
.Set Compressed=ON
.Set CompressionType=MSZIP
.Set CompressionLevel=7
.Set MaxDiskSize=CDROM
Header
.Option Explicit
.Set Cabinet=On
.Set DiskDirectoryTemplate=CDROM
.Set CabinetNameTemplate=Install.cab
.Set Compressed=ON
.Set CompressionType=MSZIP
.Set CompressionLevel=7
.Set MaxDiskSize=CDROM
Posted by:
mklaeser
14 years ago
Ok, I'll found the failure in the DDF-file. I have to comment out the ".Set CabinetNameTemplate=Install.cab" line and then makecab.exe generate 1.cab, 2.cab and so on but the expand command still end up with an error. If I extract the CAB-files with WinZip all works fine.
[:o]
Any Idea?
[:o]
Any Idea?
Posted by:
mklaeser
14 years ago
1. I have a legacy setup with source files over 6,5 GB and I want to compress them.
2. I made a script wich creates the DDF-file and executes makecab.exe. As result I get the 1-11.cab in different folder named Disk 1 until Disk 11 + a setup.inf file in the root folder.(That works now)
3. I want to expand them with a script to a local folder and afterwards I want to run the setup.
My question is: Why do I get still a error message with the expand command?
2. I made a script wich creates the DDF-file and executes makecab.exe. As result I get the 1-11.cab in different folder named Disk 1 until Disk 11 + a setup.inf file in the root folder.(That works now)
3. I want to expand them with a script to a local folder and afterwards I want to run the setup.
My question is: Why do I get still a error message with the expand command?
Posted by:
anonymous_9363
14 years ago
Wouldn't WinZip or 7Zip, both of which can create compressed archives, create an extracting EXE and then run a set-up stub, be a better solution?
Posted by:
mklaeser
14 years ago
I found the solution: Use the Extract tool from Microsoft "http://support.microsoft.com/kb/310618" with the command "extract <your first cab-file> /A /E *:* /L <Destination folder>
thanks
thanks
Posted by:
anonymous_9363
14 years ago
7Zip is 'freeware'. http://www.7-zip.org/license.txt
WinZip is USD18.70 per PC for 2-9 PCs. https://shopm.winzip.com/cgi-bin/wzct1.cgi?wzeu_wztmu1
Not what I'd call exhorbitant, either way, considering the time it's taken to get where you are now (no offence, BTW!) :)
WinZip is USD18.70 per PC for 2-9 PCs. https://shopm.winzip.com/cgi-bin/wzct1.cgi?wzeu_wztmu1
Not what I'd call exhorbitant, either way, considering the time it's taken to get where you are now (no offence, BTW!) :)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.