compstuff
-
Posts
564 -
Joined
-
Last visited
-
Days Won
6
Content Type
Profiles
Forums
Events
Posts posted by compstuff
-
-
I followed this thread but never had a chance to test anything until now so I thought I would provide some minor feedback. I am always curious as to the best way to optimize my integration time without compromising any reliability etc.
I have an I5 E5410 laptop with 4 GIG, an older Intel X-25 SSD and a Momentus XT HDD. I usually have my Temp and WinToolKit folders run from my SSD and my McRip update files and my WIM source on my HDD. Integrating about 400/425 updates consistently completes in 2 to 2 1/4 hrs. Their are always some variations in time and hotfixes so this is an approximation but it is always consistent and I always plan my integration's and time accordingly. I decided to try the integration with the McRip updates on the SSD instead of the HDD and see what the timing would be. Well there was no difference at all, it finished in the same amount of time.
I am setting up a new I7 laptop with 8 gig and a new SSD and out of curiosity I think I will try 1 more test which will be using the SSD for the WinToolKit and a Ram Drive for the McRip Updates and the WIM source. I actually doubt this will make any significant difference at all but I will report back.It will take me a little while and I will need a new baseline for an integration so I will try my best to be accurate and make a fair comparison.
-
Komm & McRip both have a directory for these and I am wondering does anyone/everyone create new media with these included?
These updates are meant for the installation media only.
The updates in question (that give DISM errors) are:- Windows6.1-KB2023591-x64, Windows6.1-KB2521168-x64, Windows6.1-KB2525084-v2-x64, Windows6.1-KB2673007-x64 and Windows6.1-KB2757588-x64
-
I have run into path length issue many times on my Win7x64 laptop so I definitely agree
Spaces aren't the only issue. Sometimes it's the resulting path length. If you end up with a path length >256 characters it can create problems for you. Even if Win Toolkit is able to finish everything without error, if you then try to copy or move that folder elsewhere on your system, Windows itself might complain. I have run into this even with Win7 x64. Not if it's just the ISO, but rather if you expand it. It's always safer to keep the path length a short as possible.
Cheers and Regards
-
I agree 1000% and if I can add: I know the toolkit handles spaces but I really think its good practice to NOT put spaces in the directories and names, even if they are short. c:\win kit\ versus c:\winkit\
We've got to get the word out better that one of the first things to try, besides double checking the file MD5, if Win Toolkit doesn't work correctly is to temporarily disable ALL anti-virus and sandbox type programs. Then make sure you are running Win Toolkit as an Admin and all work folders are as close to the root of the drive as possible with as short a path name as possible. Don't use paths like - C:\The most ridiculous path name\I can possibly\come up with\Just for me\Just to make life difficult\I'll put Win Toolkit here\ - Instead use something like - C:\WTK\.
Cheers and Regards
-
This is really great news...major appreciation to Reaper and Rick... and of course Liam and TH-Tech ...shame on MediaFire
-
FYI: I have never had to align any SSD on my WIN 7 systems and I have had many many... in fact I do ALL my physical image testing using SSD's due to the significant time savings it gives me.
Here are some great guides: http://thessdreview.com/ssd-guides/optimization-guides/
Here is another good guide: http://www.ocztechnologyforum.com/forum/showthread.php?79848-THE-BASIC-GUIDE-amp-FAQ-ABC-for-OCZ-SSD
Here is info about alignment: http://www.ocztechnologyforum.com/forum/showthread.php?79848-THE-BASIC-GUIDE-amp-FAQ-ABC-for-OCZ-SSD&p=567558&viewfull=1#post567558
-
Happy New Year to Everyone Everywhere!!!!
-
Merry Christmas to Everyone!!!
-
Sorry for the late response... end of year stuff is killing me at work... YES YES YES it seems to be working perfectly :beerchug: THANKS this really meant a lot to me due to the way I managed things... again THANKS
That issue is now fixed, compstuff, no?Lego, so the latest version is now on the 1.4 numbering scheme? It's confusing... 1.5 just got final, but named 1.4?
-
Thanks to all of you!!!!!!
-
I don't really care about the ads but if you need donations I am glad to help... do I do it through the kit link?
-
I haven't been able to test lately so are you stating that this reported issue is resolved?
http://www.wincert.net/forum/topic/10628-update-catalog-confusion-v15/?p=92650
Already discussed in some thread, there is an option named Update Catalog Filter in v39, that when unchecked, loads all the files on the server, not only .msu, .cab and .msp. I think the current implementation is just great, it's satisfying everyone.
-
Because as stated earlier in this thread many of us still want to be able to easily download the file and then manage the installation process ourselves... I for one find not downloading files very problematic.
That is correct. It was requested to leave only the .msu files in the update folder so all other files will be moved to old. Anyway some files aren't updates or not directly integratable as are the .msu files so why bother with them. -
Sounds great to me
-
Hope university is going well... nice to see you back
-
I always use a driver if the monitor has one especially if the native resolution is non-standard
-
Thanks guys... I didn't use this as an "addon" but I did extract it and test it in a VM... I won't actually use it as is but I did like the idea of adding the Download folder to the library but not the public Download folder.... I also did not like removing the Downloads link from Windows Explorer Favorites so I tweaked it a little just for my own use
-
Can anyone post this somewhere else... I hate "signing up" but would like to try this
No, you have to sign up/in to 4shared to download
-
Can't seem to download without signing up... am I missing something in the link?
-
Took me awhile to test this and get back with you but thanks it worked like a charm
I usualy use the component remover in 1.4.0.77 locate the unwanted update package by it's KB number and remove. I've done this about a dozen times without any adverse effects. In fact i'm about to remove about 6 updates that are not on McRip's server. Hope this is of some help. Best regards.
EDIT :: With respect to the SFX entry. You could always delete the folder from the apps folder on the mounted image and remove the RunOnce entry in the registry of the Offline WIM.
-
Performance Report:
I used 5.01 v38 and integrated 407 updates to Win7x64ENT, Temp and Mount on my SSD C:\ and Updates on my WD Black E:\, it took 2hrs and 38 min, which is just about the exact same as 4 v77. Using both versions my last 6 or 7 updates only integration's have all been around 2 1/2 hrs which is up from 2 hrs previously (maybe 60 or more integration's). I believe the increase is due to the updates and not WinToolKit.
-
I never reuse an already integrated image so this is a first for me but I wanted to try something quickly and I realized I don't know how to do it. Using 5.01 v38 I integrated all my updates and realized that I made a minor mistake and wanted to remove the RDP 8 updates, which actually add an update as a pre-req and then creates an SFX entry. I have already tried a few different things with no luck now I am wondering if there is an easy way to actually do this.
-
More odd deletion behavior; before running WinToolKit v38 I had removed the files under my local under "Integrate to installation media\KB2757588\" folder and when I ran the ToolKit it actually deleted the KB2757588 folder that was already there and showed that I needed to download the file
-
I just did an x64 integration test yesterday but I used 5.01v38 and it seemed to integrate fine
''Error'' with updates from komm's DVD folder
in Win Toolkit
Posted
I really don't think so but I actually don't know since I never include them