RyanVM

Ouch

Congrats, I posted that one page back

Probably

Not your fault in the slightest. I looked back at my post and realized how badly worded it was.

OK, netfxsp1.exe is updated to work on any system with msiexec now. Thanks bitmonster for the help

I've never understood why not just open the fonts folder after installation to let Windows install them instead. Heck, you could probably even write a little VB Script to open and close the Windows font folder automatically.

I thought it's easier to delete or disable the whole feature of PrintMe. This should prevent everything related to it from installing, as you know. Who needs it all? I'm sorry, I wasn't nearly clear enough in my last post. I was referring to the Acrobat Reader shortcut, not PrintMe's. That was easy to kill

Having to either download a much bigger installer, from your hosting and therefore drain it, or download just a 50 KB MST file and use my already existing merged version. That's the difference. lol Gotcha Yeah, that's the easy part . There is one oddity with the merged installer, though. For some reason, I can't edit the actual shortcut because WinINSTALL LE bitches about a missing icon or something.

si3112.sys = nvraid.sys PCI DeviceIDs can be gotten out of txtsetup.oem in the folder of files you extracted. EDIT: For more info, read the Notes section at the bottom of GM's page.

That may not work (since there are likely registry entries within that key that actually control the Recycle Bin). What you're best off doing would be to export that entire key from another working computer and use it on yours. Heck, I'm feeling nice, so here's mine (on XP SP2). Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\{645FF040-5081-101B-9F08-00AA002F954E}] @="Recycle Bin""Recycle Bin" can be whatever you want it to be named.

That's true, I hadn't thought of that to be honest with you. But if I can make the changes to the MSI file prior to putting it on the web, what's the difference? Regardless, anyone can make their own slipstreamed administrative install point now with the directions above.

The full installer is a cheap hack job at best. All it is is the regular MSI file with an MST file included (and CAB file with the 6.0.2 files). Basically, it's about twice the size that it has to be since it has both 6.0.1 and 6.0.2 included in it. To create an admin point with 6.0.2 integrated into it, follow these directions. 1.) Download the full 6.0.2 redistributable (34.7MB) 2.) Extract it to a folder using WinRAR 3.) Rename the Adobe Reader 6.0.1.msi file to acrobatreader.msi 4.) Rename Rdr6020.mst to 602.mst 5.) Run the follow command from a command prompt: msiexec /a acrobatreader.msi TARGETDIR="C:\Documents and Settings\Administrator\Desktop\reader" TRANSFORMS=602.mstYou can obviously change the path you want the install point going to at your discretion. I've confirmed that the above works for creating a working 6.0.2 install point, which compresses down to 15MB using 7-zip and 16MB using WinRAR. A quick note, the MSI installer will still say 6.0.1 setup when launching, but the files are 6.0.2 (and the Adobe Reader splash screen confirms it when it launches). I'm working on playing with the MSI file right now to see if I can make the installer say the correct version along with doing some other stuff (like having it not create the PrintMe shortcuts).

Thanks much, I'll update the build on my end when I get home from work today.

1.) Download the latest nForce platform drivers (4.27 as of now) 2.) Open the exe in WinRAR 3.) Browse to the IDE\WinXP directory 4.) Extract those files 5.) Follow Greenmachine's guide

While I'm not questioning the usefulness of this program, I do wonder what exactly its purpose would be in an unattended environment. The best use I could see for something like this would be for driver installation. Imagine having this program pop up and you check the boxes for the hardware on the system and the appropriate installer launches. It would be really nice given that many drivers don't like to be installed straight from an INF.

I don't think it's on WindowsUpdate yet. If it ever does show up, it'll be a recommended update. However, I did check the file versions and the ones in this package are newer than the ones in SP2 (5.6.0.8820 vs. 5.6.0.8825).

care to share? I was thinking something along the line of a cmd file, but an exe would work as well.

XtremeMac pointed out the problem I see with that script. Yes, the files will likely be updated, but without at least a cat file, I don't think Windows will actually be aware of them being updated. As a result, WindowsUpdate will likely still prompt the user to install it (assuming that WS 5.6 eventually shows up on there). EDIT: Also, /D CompressionType=LZX /D CompressionMemory=21 should be added to the makecab command to maximize compression.

send me an IM and I can test the file for you

evilvoice, would you mind seeing if SP1's msiexec.exe can be used with SP2?

SP2 has build 8820, actually.

http://www.ryanvm.net/msfn/netfxsp1.exe (11.0MB) Enjoy.

The install point worked (I tested it successfully on one of my own computers). I'm going to pack it into an EXE and post a link in awhile.

OK, here's a link to a fully standalone, 7-zip based (Ultra compression), .NET 1.1 SP1 installer for XP SP2 (I've been told anecdotally that SP2's msiexec.exe isn't backwards compatible with SP1, but I haven't verified it). It requires no command switches to be operated. It extracts to a temporary directory and calls the MSI file, which is run with the /qb switch (sorry all you /qn nuts). Upon completion, all setup files are deleted and Windows setup continues on its merry way. Enjoy http://www.ryanvm.net/msfn/netfxsp1.exe (11.0MB) EDIT: Special thanks to bitmonster and evilvoice for the help in creating the 7-zip installer.

Well, the instructions part will be easy since it's going to be a switchless exe