crashfly

Education is good. It just means you do not always have the time for stuff on the side. We understand. Best of "luck" (or knowledge) on those tests.

It is not often that I am able to help out. I donated $25 for this great site. I hope it helps out.

My reasoning behind the question was purely academic. In my opinion, I think it is a better program that can be written to support most any .net you have installed instead of specifically requiring a certain version. I have not gotten to the point where I removed the "lesser" version of .net, but I consider it if that would help contribute to the programs development.

Not that I am complaining or anything, would it be possible to make it compatible with .net 3.5 or even 4.0? (If possible, just remove the .net 2.0 restriction?)

Answer:

His package *IS* compatible with Windows 7 in both x86 and x64 as I have used it on my systems. It works well too.

Although you already have the option to include your own registry file, I think you could just scrap the whole section all together and just leave it for the user to find their own tweaks. (Also tends to be less for you to debug.) As an alternative, you could split that whole tab off into a "helper" program that would "build" a registry file for the user. Then that would allow the user to add additional tweaks if they wanted. Just a couple of ides for you.

The installer is only .net 4. Win 7 already has .net 3.5.1. Those are two separate entities. If you want .net 3.5.1, then do not remove it from the Win7 install source.

Statistics are good! And to think, you are a popular programmer right now! :dancing: You do good work. I am seriously glad you are not charging for this service.

It is probably the "SSL 3.0" option. Back several revisions ago, I performed an install after using W7T. With most of the IE options left alone, appearantly the default is to have 'SSL 3.0' off. With that, the game "Hellgate London" will not properly operate. It took a while to find it, but turning the option back on solved my problem with the game.

Luckily, there is a way to fix your problems. In doing a little research I came across the following. Assuming you are in a Windows 7 PE, you can use the program "sfc" to scan your directory. Likely you will need your original installation media. Here is the command line help for the file: Even if you are not using a Win7 PE, you can do something similar from the "install" command line. Boot from your CD as if you were going to install it. Press <Shift>+<F10>. That should bring up a command prompt for you to work with.

While I cannot give good answers for the rest of your listed problems, I see the only way to make sure and remove your virus problem is to add that hdd to an already working system and scan the drive for viruses. First, this prevents the viruses from auto loading in the OS. Second, it stops any root kits from hiding themselves. Only when you have the virus(es) removed would I then say try to work with the hdd to get it working again. Of course, the above is only applicable if you have access to another system that you can perfom said actions on. Otherwise, you are going to be fighting a losing battle to those virii you want to remove from the system.

It is sad that you guys have to do that. Jeeze, will spammers please just grow up? Keep up the great work on holding back the spam.

Is your virtual machine set as a 64 bit OS? If set to 32 bit, you will likely get the error.

I do not doubt that you will fix it. I was just adding to Kel's assessment of the current state of Windows 7. If you remove too much, something breaks. Microsoft never intended for all of those options to be removable, so unless someone comes along (like you Legolash2o) to make it happen, best to leave it alone.

I could be wrong about this, however I think the extractor works on '.msu' files and not '.exe' files.

This is your problem. Editing x64 binary files on a x32 machine will cause issues. Although W7T supports both x64 and x32, the underlying OS is what is used to build the ISO.

As I have not read the discussion on this, why can the animation not be changed in a pre-install environment? Is there some check that the setup does to prevent that?

I use Defraggler. It works quite fast for me actually. No problems at all.

Something else you missed Kel: if you remove IIS, you break .net support.

What exactly is a "Corsair Voyager Mini"? If it is a USB stick, have you tried it in another computer (to verify it is not working)? If so, it is likely that some of the contacts have come lose on the solder joints. Depending on how "rough" you have been with the drive, it *might* be possible to fix it if your soldering skills are good, otherwise you should just replace it.

No! This is not the site that RT7 comes out of. In addition, most of us do not deal with RT7. W7T is superior in that it is being actively developed. Since RT7 is not, you will not get any help here.

Seems to be translated. More than likely he meant "size".

You can easily combine your batch files down to two. I am not sure why you are setting an environment variable to the architecture, but those can easily be combined. SPTDinst.cmd (Combined) @echo off if exist "%SystemDrive%\Windows\SysWOW64" goto :Cpu64 set Arch0=x86 cmd /c %SystemDrive%\Install\Apps\Daemon\86\SPTDinst-x86.exe add /q goto :exit :Cpu64 set Arch9=AMD64 cmd /c %SystemDrive%\Install\Apps\Daemon\64\SPTDinst-x64.exe add /q :exit FirstLog.cmd (Combined) @echo off if exist "%SystemDrive%\Windows\SysWOW64" goto :Cpu64 set Arch0=x86 REM ## Put more x86 type setups here goto :exit :Cpu64 set Arch9=AMD64 REM ## Put more x64 type setups here :exit cmd /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\wpi\wpi.exe start %%i:\wpi\wpi.exe It just seems kind of redundant to have two similar batch files for each OS. Combining allows to use one to cover both types.

Yes, I still have a few left to do. This should complete it nicely.