darks0ul

glad to hear that.

What I said is that I used WiUseXfm.vbs to apply transforms via command line! (You can only do it one by one, though). It is included in the platform SDK, or download it here. I think you don't have a choice: each language will need its own transform file. And, depending on how you plan to do things, a res file for each language.

That is exactly what I'm trying to do. Anyway, I'm trying to automate the whole process. For the time being I've created a batch file to extract all MSIs from the compressed EXEs, create subfolders and move the files into those subfolders. Now I need to apply the transform via cmd to all of the MSIs, and then manually remove/change any language specific stuff. After that I have already made a batch file to create the SFXs, but I need some help to find how to change the Version Info with Resource Hacker using a script. Open the original file with reshacker. Modify the versioninfo and compile it. Click action, save resource as *.res file and do it. Then, provided that the original file is test.exe, the modified file is test_out.exe, and the resource file with the version info is test.res, run the following command: ResHacker.exe -modify test.exe, test_out.exe, test.res, VERSIONINFO, 1 Keep in mind that you cannot modify a value providing it via command line. The resource in the exe file is a compiled script. So, you can't do something like reshacker.exe -modify test.exe, test_out.exe, VERSIONINFO, 1, FILEVERSIONINFO, 3232343 By the way, I have an automated method of creating my lite version, using autoit, that uses WiUseXfm.vbs to save the msis transformed. How do you do this?

Or use windows update catalog or MBSA

What do you mean? What kind of language stuff? You could have a base transform, and then an extra transform for each language.

By the way, do you people realize that the full version of Adobe Reader is about 25MB, and you can pass msi commands to the installer, such as a transform? That is much simpler.

Free advice: don't bother in saving 5 mbs of disk space. Profile what is taking most time to load adobe reader, and if its something that can be noticed, go for it. But Lite, as it is now, is perfectly fine and probably solves most user's needs (Almost complete PDF reader that loads fast and is not bloatware).

IMO form filling is a priorty, it should stay. EDIT1: in todays world of terabyte drives etc etc, size does not matter so much. The Lite'ening of this product has more to do with RogerDB's sentiments posted HERE. There are few people with actual concerns of hdd space. MANY people are concerned about background processes running without any way of stopping them. Please keep this in mind when trying to make the product as small (in bytes) as possible. EDIT2: I have read the comments on the internet by small minds comparing 20 MB to 25 MB etc etc Ignore these people. This Lite product isnt for them. They have no idea whats running in the background, and never will. Those with real knowledge seek this product for the reasons posted above in EDIT1 shark Seconded, I think it's a must.

Tronborg: I already tried the CustomWizard and that does not work. Acrobat.com buttons are a new feature in 9.1, it seems.

XhmikosR: I'd greatly thank you for the updated tutorial (and the create pdf using acrobat.com registry key). rt3d.dll I tried opening a 3d PDF with JUST this file, and it doesn't work. You also need the .x3d files. Hands up those who say rt3d.dll is the only file needed for 3d pdf viewing.

Hehe, I wonder what kind of people would need a button just to launch www.acrobat.com ... Anyway, I disabled it manually, but could not find a registry key for that. I guess it will be just binary information stored in a preference file.

The fix didn't work. In order to have 3D, the Atmosphere_3D component must not be removed from the MSI. For the toolbar button, I mean silently (reg tweak?). Shark's version does not show it, and the version I created displays the button too (even though I disabled all online fetures using the customization wizard).

Shark: I did create mine, too. And didn't remove the Atmosphere_3D feature that installs rt3d.dll. I have the mst file I use (Spanish version, though, but it should work with the english one). XhmikosR: did not. The same data parse error. Uhm I'll have a look at something, got an idea. By the way, I'm not really interested in 3d, but I tried it because some people requested 3d support in the past. Edit: As I suspected, preserving rt3d.dll is not enough, the .x3d files are needed too. That solved the issue. Edit2: By the way, with this release, the Create PDF using Acrobat.com shows up in the toolbar. Any idea on how to disable that?

3D is not working with this release. You can check it out with any of these files

I tried Windows Server 2008. Even using vlite and stopping all the services I could, it was a resource hog. I prefer XP x64.

>echo %processor_architecture% AMD64 Note that this will not work for a script like RunOnceEx.cmd or similar that are called from cmdlines.txt I mean, this variable is set when the computer makes the first boot after the installation. Otherwise, try checking if %WinDir%\SysWOW64 exists... Or you can use AutoIt (@OSArch constant)

The new version is not available in MSI, yet

it's getting a bit confusing for me... I tried yesterday's script (20090111?) and windows update wants me to install .NET 3.5 SP1 with hotfixes. I had to manually apply the patches for 2.0-3.5 in order to get rid from that entry in windows update. Do you plan to do this?

Windows Server 2003 Standard x64 Edition As long as microsoft releases updates for 2003 SP2 x64, any XP x64 user will be able to apply them...

just do "set" and you'll get all the environment variables. Anyone knows the equivalent of $Progs for 32 bit programs under the $OEM$ folder structure? ($OEM$\$Progs will be copied to %ProgramFiles%)

Reread post #1. You can't install 1.1 and 3.# without rebooting after installing 1.1. To install both without rebooting you have to install 1.1 last. You can do that with merged installer, but you have to build it to include all the frameworks, including 1.1. You got me I read about that some time ago and forgot about it hehe. It seems to be working, thank you!

I didn't use the loud flavour. I use VMWare instead of VPC. The Windows image is completely up to date (including Windows Installer 4.5) and I just change ProgramFilesDir to another location. THe very first thing I install is .net 1.1 and then I proceed to install the merged 2.0,3.0,3.5 package. (all using runonceex). The funny thing is that I have a similar XP x64 image using my own .net installers and they do work in x64 (my installers have the same problem than this .net maker in WP Pro x86). however... strel, look what I've found... It could be ok until now, but s***, this could be the problem (when going to install 3.0)

TranceEnergy, I don't read those boards, however the guide is top notch. Have you tried your procedures with a second partition (ie: D:\PF_64)? You took the time to search for all the wrong registry entries, which is amazing johnhc: I use Auslogics DiskDefrag. It is free, and much better than Diskeeper (I used DK for years). It can defragment opened files that Diskeeper cannot. And works in windows x64.

Yes, I do (strel's cmd). Version 2.0 is installed on the machine that makes the installer. I'm trying to install from 2.0SP2 to 3.5SP1 on a clean XP installation. Are you saying that I do must install .net 2.0 (plain) and then, 2.0SP2 and the rest of the files? I did not get any error message using that package, I will pass /lv %SystemDrive%\dotnet.log to the installer and check the log.

Merge them all together using strel's modified script and this wil solve this problem. Did not work here, even using the merged installer My INI file: ; SNM.CMD default configuration settings. "YES" means "if it exists". ; PROCESS MAIN PACKAGES PROCESS_DNF1=YES PROCESS_DNF2=YES PROCESS_DNF3=YES PROCESS_DNF35=YES ; HANDLING OF INDIVIDUAL FRAMEWORKS IN .NET 3.5 PROCESS_DNF35_DNF2=SEPARATE PROCESS_DNF35_DNF3=SEPARATE PROCESS_DNF35_DNF35=YES ; PROCESS SUBCOMPONENTS OF .NET 3.0 SP1 PROCESS_DNF3_RGBRAST=YES PROCESS_DNF3_WINIMAGING=YES PROCESS_DNF3_MSXML6=YES PROCESS_DNF3_XMLPSSC=YES ; PROCESS LANGUAGE PACKS LANGPACK1_NAME=langpack.exe PROCESS_DNF1_LNG=YES PROCESS_DNF2_LNG=YES PROCESS_DNF3_LNG=YES PROCESS_DNF35_LNG=YES ; SPECIAL ; Set MERGE_FRAMEWORKS to 12 to merge .NET 1.1 with .NET 2.0 SP1. ; Set MERGE_FRAMEWORKS to FULL to make a single complete package. ; If the temporary file appears to not go up in size anymore after several minutes, ; decrease the compression ratio. Accepted values: MED and LOW. Try MED first. MERGE_FRAMEWORKS=FULL COMPRESSION_RATIO=