galevsky
29th January 2008 23:07 UTC
CABSetup::BuildSetupFiles add=path bug ?
Hi all,
I spend lot of time to understand what was wrong with one of my script...
CABSetup::BuildSetupFiles /NOUNLOAD "/add=${SOURCE_FILES}" /S |
The script will try to create the cab but fail with return code 1. My ${SOURCE_FILES} was "C:\Documents and Settings\Admin\My Doc\Here_v1\sources\"
But no problem if I use the source files from "C:\Program Files\Test_v1\sources" instead.
Any idea ? I am admin, so I don't think it is a rights issue, both Program Files\ and Documents and Settings\ are on the same partition.... I cannot see.
Thks,
Gal'
Mr Inches
31st January 2008 14:45 UTC
Hi
A return code of 1 from BuildSetupFiles with the /MakeFiles option usually indicates there a problem with the syntax of the contents of the directive file created by the earlier switches.
The most likely reason I can think of for it having a problem is one or more of the paths added for your source files or folder are invalid. Note that the Add expects a path and file specification; if you only give it a path it does not assume '*.*'.
The error message in the DetailLog suggests running the command externally to observe MAKECAB's error message (I am looking at ways to capture it's output for redisplay from within CABSetup, but it does some strange things with it's console output...).
If you could post a copy of the {dataset}.DDF file that CABSetup creates and/or run the command given in the error from BuildSetupFiles and reproduce it's output, they may provide some more clues.
Duncan
galevsky
31st January 2008 14:55 UTC
I will do that in a while.
PS: I had set my SOURCE_FILES to "C:\some\path\*.*" so no problem with that.