bphlpt

I see no need for that. This is a marvelous example of the give and take between the author of an app and a user asking questions and offering changes, in this case for ease of installation. Just because it hasn't borne fruit, yet, I see no reason to delete the thread. Sometimes we learn as much from our failures as from our success. There is useful information here. Cheers and Regards

I believe you have to manually add it yourself.. Cheers and Regards

No worries at all. No accusations were made, just a general warning. We have had a rash of folks, here and at other sites we belong, who seem to not understand the concept of copyright, EULA's, etc. Since some of the sites, including this one, have then had to deal with anything from takedown notices to loss of advertising revenue as a result, I'm afraid we have gotten a little gun shy and sometimes err on the side of caution. Please just consider it merely a reminder of some of the board policies in general, and not something directly directed at you, if it does not apply. Thanks for joining and participating at WinCert. I'm looking forward to seeing what other Switchless Installers you are able to share. Thanks for posting the ones you already have. Cheers and Regards

However, if you plan to write a blog or tutorial how folks can automate their own installs, using sources that they legitimately own and have obtained through authorized sources, and using free tools such as Win Toolkit or WPI or tools or scripts that you write and provide, then that is perfectly alright. Welcome to WinCert! Cheers and Regards

One of the features of Win Toolkit is that it should automatically install any needed drivers that it finds in the folder it finds in the root called "drivers", so if you don;t want it to do that, then yes, you should rename the folder. But I don't think it should be trying to do that at the same time that it is installing programs. If it is, then you have another problem, likely caused by one or more of the updates you are trying to integrate that is failing, I believe. Cheers and Regards

Maybe Win Toolkit is using an older version? I did think we were supposed to be all using the same list, but I could be wrong. Cheers and Regards

Glad to see you're OK (at least OK-ish ).You do so much for us, please let us know if there is anything we can do for you. Cheers and Regards my friend

As ianymaty said, the field where you see "Lurker" in your posts is a tag called "Member Title" whose default behavior is to automatically change as you make more posts on the forum, just as ianymaty's Member Title is "WinCert Friend", and mine, bphlpt, is "WinCert Addict". It has nothing at all to do with your name, Most people just leave it alone and let it do it's thing. If for whatever reason it really offends you, you can change it yourself along with other of your profile settings. Go to your profile page, click the "Edit my Profile" button near the top right of the page, then look for the "Profile Information / Member Title" field. It should be empty. Put whatever you want in the field then click "Save Changes" at the bottom of the page. If you want the field to go back to it's default behavior, just go back, delete whatever is in the field and "Save Changes". Cheers and Regards

It does seem strange though that apparently 4.5.1 is used if the updates are done via MU/WU. And it would seem to make more sense that 4.5.1 would be used. Of course this wouldn't be the first time that MS was not consistent. Cheers and Regards

But again, it shouldn't matter the size of the ISO. It sounds like a smaller install size is what you should be focused on, not the size of the ISO. They are NOT directly related. Cheers and Regards

I'm not one to give you advice for removing things since I choose to remove nothing, but I'm curious. Why are you focused on the size of the .ISO image, when I would have thought that the size of the installed image would be what is more important? Win Toolkit, which uses the "official" DISM method to remove things, does not remove much at all from the .ISO, but rather just prevents things from being installed. AFAIK, this still won't reduce the installed image as much as some other methods, but it should be more stable. Cheers and Regards

Not to worry about any virus. Other respected update pack makers including OnePiece, user_hidden, ricktendo, 5eraph, tomasz86, Kel, and others are all keeping an eye on this project. And I also wouldn't be that concerned about using XP, if that is the OS you like, beyond the "expiration date". The number of threats that are attributed to the OS iteslf vs other apps or user actions is relatively minor, less than 10% according to some studies, and with the use of a good router and up to date software firewall and AV and other anti-malware software, the risk becomes essentially miniscule. After all, there are some folks that still use Win2K and Win9x on a daily basis. Cheers and Regards

Rick, I'm confused. For almost 2 1/2 years all of your .NET packs have always been named something like: dotNetFx45_Full_x86_x64_xxxxxxxxxxx.exe but now the downloaded files from the first post are named: NDP451-KB2925430-x86-x64-AllOS-ENU_REPACK.exe NDP451-KB2925430-x86-x64-AllOS-INTL_REPACK.exe The last file of yours I downloaded with a similar naming format was in Dec. 2011 - NDP40-KB2599651-x86-IA64.exe. Are you changing naming scheme? If so, why and can you please explain how your various packs will be named? TIA EDIT: It seems that the "guilty" party is MS. They have changed their naming scheme and Rick is merely following it to be consistent with them. He just adds "_REPACK". Cheers and Regards

Welcome to WinCert! Cheers and Regards

And a little "higher up" link - http://heidoc.net/joomla/ - highlights that you can find other legal Digital River downloads there of Windows 7, Office 2010, Vista, and more. Cheers and Regards

I don't know if this will work or not, but you could try this - http://www.bluestacks.com/ Cheers and Regards

There are two ways. One, the "standard" way, is to separately integrate updates into each of the versions you plan to use. As you mentioned, this will indeed take awhile. The other way is to integrate all the updates into the "lowest" version you plan to use, ie home or standard or whatever, then you can "promote" that into all the other versions all the way up to ultimate. This would have to be done separately for x86 and x64 versions. I'm not sure of the exact procedure how that works, and I can't find the links to the info at the moment, but ricktendo knows and hopefully he'll see this post and respond with more explicit instructions if you want to try that route. Lego has verified that the method works, and there has been talk of Win Toolkit eventually incorporating the method, but that hasn't happened yet. Cheers and Regards

While user_hidden has not had a chance to update his installers as often as some would like, jaynbe has done a good job keeping yumeyao's installers updated. The OP in the threads is not updated, since it was started by yumeyao, so you have to look for jaynbe's posts, such as here and here, both updated this month. Note: I think you might have to be a member at Ryan's to get to those posts, but if you are not already, you really should be. Cheers and Regards

Sorry, I saw your OS listed as Win7 x64 and made an assumption, apparently an incorrect one. So which exact version of XP, x86 or x64, were you looking to use the 3.5 and 1.1 installer on, and if it is for XP why not just use a .NET AIO, for which there are already a couple available? Cheers and Regards

No such thing exists for use in Win7, AFAIK. .NET 3.5 and 1.1 are now part of the OS itself instead of separate installs like they were in XP. Why were you requesting this? Cheers and Regards

Welcome! Cheers and Regards

An even better explanation would be: This XP post-SP3 All-in-One Update Pack is similar to Ryan's and user_hidden's, but can be customized more to your needs, and includes more stuff like IE8, ... etc. Cheers and Regards

Have you tried to make a build without deleting anything or disabling any services? If that works, then it would seem that your problem is with something that you are deleting or disabling that is necessary to install .NET 3.5. Cheers and Regards

This is not the RT7L forum. Why are you here? Cheers and Regards

Yes. AFAIK, SP1 is required to be installed first. Cheers and Regards