bphlpt

@tomasz86, I'm confused. It looks like you've said: The problem is here, "A" (setupusp.exe), specifically this line, "B" (spsetup.exe), it should be "A" (setupusp.exe). While I expected you to say: The problem is here, "A", specifically this line, "A", it should be "B". or The problem is here, "B", specifically this line, "B", it should be "A". Or did I misunderstand something? (That happens all the time. ) Please clarify. Cheers and Regards

I believe that he is asking you to set the Superfetch Service Startup type to "Manual" instead of "Disabled". You can do this manually by going to Computer Management -> Services and Applications -> Services -> Superfetch. In the Pulldown box for Startup type select Manual then click Apply and OK. Then reboot the system, maybe a couple of times, then redo your tests and see if that makes any difference. You can then go back into Services and see if indeed the Superfetch service was started, or if just allowing for the possibility that it could be started allows the system to perform correctly. I understand your concern about having the service running effecting the life of the SSD, but doing this test just to see if indeed it is the problem will not effect it's life enough to notice. You can always disable the service again after completing the test. Once we can find what is causing your problem, then we can try and figure out how to prevent it. Cheers and Regards

You can't really make a general statement that will always be true. It will depend on everything from the actual CPU that has the integrated GPU, the external GPU, the motherboard, the BIOS, the OS, etc, etc. I know some combination of integrated GPU + certain external GPU + plus certain motherboards can actually be as you described and have the integrated GPU used for certain tasks and the external GPU take over from, or work together with the internal GPU. For other combinations, if the external card is plugged in the internal one is disabled. For others, you can pick which one you want to use in the BIOS, but you can only use one or the other, not both and it cannot be changed except through the BIOS. You'll just have to read the specs in detail, mainly the motherboard specs, and go from there. Cheers and Regards

You should also look around more here on the board. http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/ That is the reason that Andre only recommends the use of MS's own defragging tools. As you found, defragging just to eliminate fragmented files is only part of the solution. File placement is also a factor. Cheers and Regards

Our condolences, Ponch. It's never easy no matter what their age. Cheers and Regards

I don't think I can help you with your question, but I would be fascinated to see your other cmd scripts such as "create_boot_folder.cmd" and get a better understanding of how this all works. Cheers and Regards

Seems to me that if you go down that road, and I would like to see that, that KernelEx and ALL the files that are "For KernelEx Systems only" should be ONE single option. That way the folks that want a more "pure" solution can have that, and the folks that want a more expanded solution could have that with a group of files that have been tested to all work together correctly with the basic 98 SE SP 3.x files. Any more fine tuning of which files to include and which to leave out puts too much of a burden and workload on PROBLEMCHYLD. A single all or nothing kind of option only. For anything else the user can choose not to select the option and then add in the individual files that they want. Cheers and Regards

Not that I see the harm with the "advertising", but I can understand Kullenen_Ask's point. Especially if this was going to be used in any setting other than occasionally at home by an individual. It would probably be nicer it the volume names were left "stock". Cheers and Regards

It seems that the OP needs to be told exactly which things to install and in what order including what prerequisites. And when you tell him to install all the drivers, apparently you need to say "YES, I MEAN INSTALL EVERY FREAKING DRIVER IN XXX FOLDER WHETHER YOU THINK YOU NEED IT OR NOT!", if that is the case. LOL Also, sometimes it's best to go to the PC manufacturer's web site (IBM/Lenovo) for drivers, and sometimes it's better to go to the chip manufacturer's web site (ATI). Unfortunately, it depends. YMMV Cheers and Regards

I know you are a "purist" and only want to use MS written code, even if you have to port it in from an alternate MS OS, (a third party approach if you think about it), but once the underlying code that supports that code has also been removed, then you're just going to have to accept that you are not going to be able to accomplish what you want. Besides, I would think that using a third party approach like ClassicShell, which is designed and intended to be installed in Win7 and Win8, will be more robust, reliable and flexible than trying to shoehorn older MS code in to a place where it was not designed to be, in fact was purposefully removed from and efforts were made to not allow it to be put back. ClassicShell is both Free and Open Source. Even if were closed, anyone can pick up the source and continue their efforts. ClassicShell even lists their "competitors", with links, if you would prefer to check them out. A member of their staff also participates on this board. The only thing that can really "stop" ClassicShell, temporarily, is MS removing more code or putting up more roadblocks, which would also effect code ported in from other MS OS even if it did work now, such as what happened without advance notice prior to Win7 RTM and what happened again between the early releases of Win8. I wouldn't worry about ClassicShell being removed as much as I worry about MS changing their minds about what features they're going to revamp next week. And I guess as a purist, you also don't use any third party code like Java or Flash since they are not part of the OS? Not to mention not being able to play DVD's if you decide to try Win8? Cheers and Regards

Of course the OP has no information at all on his profile page anyway, not gender, age, country, OS, interests, etc, so ... Cheers and Regards

And people wonder why we often suggest the simple things first, such as checking cables, when there are obscure or intermittent problems. They don't take long to check and they are inexpensive to replace. Cheers and Regards

WPI.cmd calls itself? autorun calls WPI.exe? Create an iso with what? Just those two files? What is the purpose of your entire post? Just to confuse? Were you trying to play a joke having an endless loop that was so lame you muffed it up? Were you trying to get banned? If you have any idea what you are doing you sure didn't show it. I'm confused. Cheers and Regards

What worked? What fixed the issue? Cheers and Regards

Can you provide a link so that we can see what you're talking about? Cheers and Regards

As an example of how much better that PNG can be Multibooter, I downloaded the screenshot from your last post, which as a GIF was 38.7KB, loaded into IrfanView and saved it as a PNG with the highest compression level and it became 19.1KB, less than half the size. That should free up some space for you. Cheers and Regards

Well now that there have been three different versions identified, with slightly different tools and docs available, here is what I would be interested in. First off, note that forensic accuracy is not important to me at all. Functional accuracy is. I would like to understand the list of all the tools available in the different versions, what each tool does, and for tools that were in early versions of the Resource Kit but were removed in later versions I would like to know why they were removed and if they would still be of any use even if they are no longer supported. Essentially I would like to see a merger of the three versions with everything that is still worth having. If everything that is worth having is in the last version, ie the one still on the server, then except for forensic accuracy I see no reason for continued discussion of the other versions. Cheer and Regards

The comments from mdc have not been deleted ... yet. There was just the fear that they might be. Cheers and Regards

Yes, OS install and customization using nLite or vLite is not for everyone. Maybe some other time. Cheers and Regards

The implication is that mdc is no longer with MS since he says: so I don't think the post will be deleted. It was an interesting point of view. If the mods don't object, and I don't see why they would, it might interest others to read mdc's posts here. However, they don't change my opinion of Metro, or Win8 in general. Cheers and Regards

Actually, I don't know if I understood your explanation any better. I also thought that your original statement was correct: That you can install either an x86 install.wim or an x64 install.wim with an x86 boot.wim. Isn't that correct? Yes, I know that you probably can't install 64bit drivers with the x86 boot.wim, but I thought the you can install the x64 install.wim and install the 64bit drivers once you have booted into the x64 OS. Isn't that the way it works? Cheers and Regards

Of course not. WinPE (boot.wim) doesn't support WoW, so you need to match archs for either build. I use x64 boot.wim to do everything nowadays tho. Tripredacus, if RickRollNW is anything like me, I'm sure he's just as confused. Could you please clarify the apparent contradiction? Cheers and Regards

I use the DigitalRiver source and I also always have to hide all the optional language updates from showing up in WU. It's no big deal but a pain I wish I didn't have to do every time. To modify the OP's question a little bit and generalize it, isn't there some way to set up the unattended install so that you can "inoculate" the install so that you can "pre-hide" any updates that you know in advance that you want to hide so that you will not be bothered by them? There might not be a way, but I sure wish there was. Cheers and Regards

1) You have changed everything in your repair configuration except the broken drive itself leaving no common elements from your initial times you "fixed" the drive. 2) The drive has been broken two or three times before, so I wouldn't say it has ever been "fixed" just made temporarily operable. I have been fortunate that I have never had to deal with this issue, but from what I understand I thought that the purpose of doing the "fix" on the drive was merely to hopefully be able to get the data transferred off the drive. Any further use of the drive was to be considered totally a temporary gift and the drive was very likely to fail again, as your experience has proven two or three times. If what I have said is correct, then you have been fortunate to have gotten as much use out of the drive as you have and it is now time to put the poor drive out of it's misery and give it a decent burial at your nearest recycling center. May it rest in pieces. Cheers and Regards P.S. If I am wrong I'm sure someone else will post accordingly.

winrar seems to work. I don't know why 7-Zip has problems. Cheers and Regards