Dumpy Dooby
Content Type
Profiles
Forums
Events
Posts posted by Dumpy Dooby
-
-
Yes. It is being overwritten. That is made very clear in the link that he sent you. The source code for the custom setup.exe file is in that link as well. Have you considered checking out the link he sent you? You should really read the link he sent you if you're interested in knowing what's going on at the programming level. Have I mentioned that the link he sent you would have answered your question? I just want to make that clear. Allow me to emphasize that you should really check out that link.
You're welcome.
0 -
If TRID can detect MSIs created with Wix, then you should use dark.exe to decompile the MSI file. This should be preferred over MsiX.
0 -
i6comp does not use the copyrighted DLLs. The very first entry in the author's changelog is:
1) No more ZDxxx.DLL - compression/decompression (deflate) routines are
statically linked in.Here is the original zip file as the author distributed it: http://xpdnc.org/i6comp.zip
But if you're really worried about it, then just use unshield, which accomplishes the same thing without ZD*.DLL files. It's available on SourceForge, so you know it has a copyleft-friendly license.
edit--
You can find the i6comp author's e-mail address and the aforementioned changelog in the i6comp.txt file that's included in the archive. Maybe e-mail him to see if he knows about the licensing terms? It's a crap shot, but it could get you somewhere.
0 -
Subtle advertising.
0 -
-
Sorry, I assumed that would work.
I personally use an administrative program that's made by ESET specifically for creating those configuration files. I can't think of the name of it right now. I haven't used it in over a year. I created a config file and haven't had to use it since then. *shrug*
0 -
How to create the file of configuration Config.xml for versions 4?
Advanced Settings->Export
0 -
Dumpy Dooby
I see, OK, suppose all files to extract are zip, I'll check it to include the switch. Thx.
I suppose 35SP1_KB963707FIX_NOFFADDONPROPERTY.mst appears in .\TMP folder, is that right?
I have not defined any timeframe limitation for the script subprocesses. Waiting for your tests.
I ran it all the way through a couple times. Both times everything came out fine. I have no idea what caused that error message initially. If it ever shows up again, I'll go through everything and see what happened.
0 -
As of 7-zip 9.07, you must specify the type during extraction of executable files. Otherwise it will extract each individual resource and binary section. I already put in a suggestion to make that action switch-activated, but he says he'd rather have use the type switch if they don't like it.
I might have posted this earlier. Sorry if I'm repeating myself.
Did you missed the thread to post to?
Nah, that post was for you. All of your 7za.exe x entries leave out the -t switch. As of 9.07, that's a required switch for self-extracting archives, which would include hotfixes. It's not a big deal, really, because your instructions specifically call for the use of 4.x version of 7-zip, but I figured I'd point that out just in case you care to support the more current versions of 7-Zip.
About the other post with the error not finding FF addon file, I have to say I've seen this error ago but I though it was completely solved. In fact I cannot recreate the error, using exactly the same settings in .ini file. Can I have the file list? Any other useful info to recreate this condition?I didn't modify your code or anything. I just entered those settings and ran the CMD file. Here's the file list that was generated:
10/23/2009 09:32 PM 4,181 _20SP#_SLIMMING.7z
10/29/2009 02:49 PM 1,369 _20SP#LNGbr_KB829019FIX.7z
10/28/2009 09:46 AM 1,429 _20SP2_KB974417FIX.7z
09/27/2009 09:34 AM 1,109 _30SP#_REMFONTCACHEFIX.7z
09/27/2009 09:35 AM 1,626 _30SP#LNG_KB928416FIX.7z
10/19/2009 08:19 PM 16,941 _35SP#_SLIMMING.7z
10/29/2009 02:26 PM 1,009 _35SP1_KB963707FIX_NOFFADDONPROPERTY.7z
09/27/2009 09:33 AM 3,474 _KB951847FIX.7z
10/09/2009 07:54 PM 3,097 _REM_MSI_BLOCKING.7z
10/29/2009 04:32 PM 87,163 _SNMsynth.cmd
10/29/2009 11:20 PM 3,941 _SNMsynth.ini
08/29/2009 05:01 PM 578,048 7za.exe
09/14/2009 02:14 AM 108,032 7zSD.sfx
09/29/2009 12:54 AM 242,743,296 dotnetfx35.exe
10/29/2009 10:44 PM 952,840 msxml6-KB954459-enu-x86.exe
09/29/2009 12:01 AM 8,981,856 NDP20SP2-KB958481-x86.exe
10/13/2009 01:01 PM 11,459,928 NDP20SP2-KB974417-x86.exe
09/28/2009 11:59 PM 7,256,928 NDP30SP2-KB958483-x86.exe
09/28/2009 11:49 PM 1,424,736 NDP35SP1-KB958484-x86.exe
10/29/2009 10:40 PM 759,144 NDP35SP1-KB963707-x86.exe
10/29/2009 11:21 PM 26 PROCESSDATA.TXT
09/27/2009 05:04 PM 283,648 upx.exe
10/29/2009 10:44 PM 3,273,088 WindowsServer2003-KB971276-v2-x86-ENU.exe
10/29/2009 10:44 PM 3,278,200 WindowsXP-KB971276-v3-x86-ENU.exeI'm using an Athlon XP 2600+, so it's pretty old. It could just be an issue where it's not completing a task within a timeframe that your script is expecting. I'm not sure if you have anything in there like that, but just figured I'd mention this thing is incredibly slow in case that makes a difference to you.
Lemme know if you have any thoughts on this. I'll see if I can recreate the problem or if it was just a one-time thing.
0 -
Got this while running _SNMsynth.cmd.
Again, that's not during an installation. That's during the building process itself. Below are my settings:
; _SNMsynth.cmd 20091029 PROCESS SETTINGS. ---- Complete guide at: [url="http://www.msfn.org/board/index.php?showtopic=127790"]http://www.msfn.org/board/index.php?showtopic=127790[/url]
; Unless expressely stated, settings have 1, case insensitive, working value: "YES" meaning yes only if related packet is present.
; ------- PROCESS MAIN PACKAGES
; These settings request processing for .NET 1.1 (dotnetfx.exe), 2.0 SP1/SP2 (NetFx20SP1_x86.exe/NetFx20SP2_x86.exe, if both are
; present SP2 is processed) and each one of 2.0 SP1/SP2,; 3.0 SP1/SP2 and 3.5/3.5 SP1 inside any of the dotnetfx35.exe (3.5/3.5 SP1
; respectively). 2.0 SP# can only be processed from 1 of the possible sources, individual or full redistributable packet. Choose.
PROCESS_DNF11=YES
PROCESS_DNF20=
PROCESS_DNF35_DNF20=YES
PROCESS_DNF35_DNF30=YES
PROCESS_DNF35_DNF35=YES
; ------- SUBCOMPONENTS OF .NETFX 2.0 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove Visual C 8 Runtime Libraries and Office 2003 Crash Reporting Tools from installers/add-ons
; containing 2.0 SP# framework, useful for installing them from another updated source, see guide.
DNF20_VC8_RUNTIME=NO
DNF20_OFFICE2K3_DEBUGGER=NO
; ------- SUBCOMPONENTS OF .NETFX 3.0 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove those 3.0 framework pre-required components from your installer/add-on containing 3.0 SP# framework,
; useful if your OS have them installed, like WIC in XP SP3, or for installing them from another updated source. See guide.
DNF30_RGB_RASTERIZER=NO
DNF30_WIC=NO
DNF30_MSXML6=NO
DNF30_XPS=NO
; ------- SUBCOMPONENTS OF .NETFX 3.5 --->> DON'T TOUCH THIS UNLESS YOU KNOW WHAT YOU'RE DOING!
; These settings let you remove .NET Framework Assistant 1.0 add-on for Firefox from installers containing 3.5 SP1 framework and
; Visual C 9 Runtime Libraries from installers with .NET 3.5 SP#, useful for installing them from another updated source. See guide.
DNF35_FF_ADDON=YES
DNF35_VC9_RUNTIME=NO
; ------- PROCESS LANGUAGE PACKS
; "YES" here means yes only if both framework and langpack are present and set to be processed. These settings request langpacks
; processing for .NET 1.1 (langpack.exe), .NET 2.0 SP1/SP2 (from NetFx20SP1_x86*.exe/NetFx20SP2_x86*.exe), and each one of 2.0 SP1/SP2,
; 3.0 SP1/SP2 and 3.5 SP0/SP1 langpacks inside 3.5/3.5 SP1 redistributable langpack (dotnetfx35langpack_x86*.exe, same filename)
PROCESS_LNG_DNF11=YES
PROCESS_LNG_DNF20=YES
PROCESS_LNG_DNF35_DNF20=YES
PROCESS_LNG_DNF35_DNF30=YES
PROCESS_LNG_DNF35_DNF35=YES
; ------- SPECIAL
; -- Add WIN2K=YES / WINXP=YES / WIN2K3=YES define the target OS version for your ad-hoc installer(s)/add-on(s), instead of the your
; host OS version. Installer(s)/add-on(s) for each OS version are incompatible with another OS versions.
; -- T13ADDON=YES builds T-13 nLite/RVMI add-on(s) packing the .EXE installer(s) (HFSLIP compatible), so you can extract them later.
; -- MERGE_FRAMEWORKS=YES merge all frameworks that are being processed into a unique installer/add-on, instead of, otherwise
; single framework version installer(s). Merged installers/add-ons keep installing priorities, see guide.
; -- SILENT=YES makes quiet switchless installer(s)/add-on(s) instead of, otherwise, default passive one(s) (progress bars with
; no cancel button). The switchless default verbosity of installer(s)/add-on(s) can be modified at run with switches. See guide.
; -- UPX_SFX=YES Adds 50KB extra compression on .sfx module with UPX. False positives on eSafe and Comodo antivirus appear. See guide.
; -- COMPRESSION_RATIO=HIGHER / HIGH / NONE , reduce compression from, otherwise, HIGHEST setting. Useful for low RAM or slow machines.
; On the fly, you can restart compression subprocess with the next lower ratio in the previous scale.
WIN___=
T13ADDON=
MERGE_FRAMEWORKS=YES
SILENT=
UPX_SFX=NO
COMPRESSION_RATIO=NONE0 -
As of 7-zip 9.07, you must specify the type during extraction of executable files. Otherwise it will extract each individual resource and binary section. I already put in a suggestion to make that action switch-activated, but he says he'd rather have use the type switch if they don't like it.
I might have posted this earlier. Sorry if I'm repeating myself.
0 -
Oh, it happens with all MSI files, not just the .NET Frameworks. I was asking you because you seem to know your way around MSIEXEC. In any event, since I use a VBS file to run my installers, I just have it open the log file, and I do a string replace of Chr(0) with "" to get rid of all the NULLs. It works fantastically.
0 -
can you add an icon in context menu items?
like winrar:
They register DLL files as Shell Extensions in order to do that. Universal Extractor simply uses the registry to add its context menu options.
0 -
There's a setting in the options somewhere to disable "Self Defense." You need to do that before you can change any registry entries.
Alternatively, you can export your settings if you go into advanced mode, and those settings can be imported automatically during an installation.
0 -
It's not code. It's a command line. You can run it from a command prompt or the "Run" dialog.
To make it easier, just put what I have on the previous page into a file named setup.cmd and paste the command-line into it. Then run that file.
0 -
Great info. Thanks for posting YumeYao.
0 -
Why have multiple copies of it? When I last used WPI it had the ability to create various preset configurations. So on the left there was an option to install "all," or "administrative tools" or "utilities" or "design software" or "frameworks" so on and so forth. You could do the same thing except make the options "PC1" and "PC2" etc.
I don't know if that feature still exists, but I'd assume it does.
0 -
Dude thinks I'm a service provider or something.
0 -
There seems to be an issue with applying the hotfix.
Here's a program that utilizes one of the files. Just drag and drop an EXE onto this program (it's written by a fellow community member; the program reduces the privileges of an EXE) and it should work. Test it without the latest hotfix slipstreamed into .NET FW 2, and you'll see that it works. Then test it after the hotfix has been slipstreamed, and it will say it can't find that file.
http://xp.xpdnc.org/RunRestricted.exe
So something's not right.
0 -
wtf? Test it yourself.
0 -
I'm not sure what you think I've asked you to do, but clearly you've misread something.
I didn't ask you to code anything, "regress" your program, or otherwise make any changes at all. I asked for permission to modify it and do it myself. I also asked if it had been done in the past (which I've now confirmed it has).
There definitely was a "Lite" version. So that's cool. That would give me a starting point.
0 -
I can verify that the following files are actually getting copied over:
- dotNET20SP2\Win\Microsoft.NET\Framework\URTInstallPath\mscordacwks.dll
- dotNET20SP2\Win\Microsoft.NET\Framework\URTInstallPath\mscorlib.dll
- dotNET20SP2\Win\Microsoft.NET\Framework\URTInstallPath\mscorwks.dll
They are receiving the GDR update from the MSP.
So it's just a matter of manually telling WU that the hotfix is installed, right?
0 -
Try this:
IncrediMail.msi USERNAME="koby50" COMPANYNAME="MSFN.org" ISX_SERIALNUM=12345678987654321 DATABASEDIR="%COMMONPROGRAMFILES%\IncrediMail\" ChkBox_MyStart_Search=0 ChkBox_MyStart_HomePage=0
Change the values as needed.
Not all of those are public properties, but you can still test it.
I don't know if DATABASEDIR is necessary. I'm not sure what that's all about, and I have no interest in testing out this program.
0 -
I can confirm.
After applying the patch:
msiexec /p NDP20SP2-KB974417.msp /a Netfx20a_x86.msi
...and reinstalling Windows completely with integrated .NET Frameworks,
I get this:
Edit--
I don't install Microsoft .NET Framework 1.1. So there may or may not be updates that show up once that's installed.
0
Install XP from a RAM loaded ISO image
in Install Windows from USB
Posted
I wanted to make sure to be clear, per your request for clarity.
You're welcome.