You can probably use Revo Uninstaller to get rid of the crapware and then uninstall the drivers.
Then reinstall it by using the Add/Remove Hardware wizard and NOT the supplied installation utility and it should only install the drivers and not the crapware.
And what do Canned Worm have to do with all this?
Well, you basically described what I alreay tried...the problem is, when using the uninstall add/remove programs to get rid of that stuff, it also uninstalls and removes the drivers from my system. So when I am running the Add/Remove hardware wizard, there's no path to point at for the drivers.
I suppose I could try pointing to the SoftPaq.exe...I don't know :S
Thanks for your help!
If it removes both drivers and the "crapware" that's OK - you can just reinstall the drivers to the Add/Remove Hardware wizard.
Also with the SoftPaq.exe file, can you extract the files from inside it (try using 7-Zip or something) - pointing Add/Remove Hardware to SOFTPAQ.EXE will not work.
Yes. Extract the SOFTPAQ and then point it to the directory that you extracted the files to. There should be an OEMSETUP.INF (or something like that) there.
>Thanks again for the help and sticking with me!
I had a little trouble comprehending that particular post (part of my diagnosis for HFA is poor comprehension) but here are my responses to what I understand:
You guys have been insanely helpful. Since I am of course a bit noobish, I didn't realize at first that the hardware wizard would be looking for .infs, not .syss as I had installed. So I tried it my way, and of course it didn't work because I had only salvaged the .sys files. So I explored the HP provided softpaq .exe using IZArc (which I happen to like a bit more than 7-zip :P ) and found the relevant .infs fairly easily.
No worries mate! And don't feel too bad about being "noobish" over here! This is really a place for developers to ask questions etc. You are doing pretty well there mate! We all started from somewhere! I started off by opening up EXE files in Dev-C++ to try and find out how that worked. Needless to say, that never actually happened ;)
I am the extreme example of "noob" when it comes to communication, social skills, etc.
Now I am writing an operating system.
As a side note, early in this process, and I'm not sure if I mentioned this in my original post, but I checked the BIOS settings for the AMT functionality and they were all disabled (with the exception of one setting which had 2 options that aren't enable or disable at all). This didn't seem to have much effect at all on my system O.o
These settings won't have any effect unless the actual system software supports it either in the form of the OS supporting it alone or in the form of device drivers (which is the case here).
Also note that the software has to access the BIOS for the information. Mostly with operating systems the BIOS is only used for initialization purposes; software can, and often do, bypass the BIOS (usually because it is really slow)
Well, it was a learning process indeed...now time to make an optimized disk image and finally start using my new computer!
Remember above I mentioned how my first attempts at decompilation were opening the EXE files in Dev-C++ to find out how they worked (without success)? Well I learned that the hard way.
Also I notice you mention imaging. Do you create an image after the install, so as you don't have to do that whole thing of install and reconfigure everytime you need to reinstall the OS? Or do you use that image thing as a backup? If you create it after install and use that as a medium for reinstallation I would recommend you use IMAGEX from Microsoft (it can even image a Windows NT 4.0 [Servicepack 5+] machine assuming it has at least 512MB of RAM) - you can get it via the Windows Automated Installation Kit. In any case don't forget to defrag before taking the image!
As another aside, and this is a bit off-topic, but HP also included a set of security tools on this computer that are seemingly impossible to remove...that is to say, I had no trouble uninstalling them, however, there are tons of leftover registry entries and my homepage button in IE7 says HP Protecttools Security Manager still! Those finks!
Might I recommend you dump Internet Explorer completely for Opera instead? If you don't like Opera, try Firefox. If you don't like Firefox, try Google Chrome. If you don't like Google Chrome, try Apple Safari. If you don't like Apple Safari, then try Opera. Etcetera. Internet Explorer is hazardous and toxic. In fact it shouldn't even be considered being called a "Web browser" - the only advantage I see for IE is to download Windows Updates (for Windows 2000 and XP only) - otherwise there is absolutely no advantages!
Now to clear up the registry crap (or at least... try to clear it up) there is a tool called Piriform CCleaner which I find works very well (it's free - no ads etc)
Also if you think HP was bad, judging by the above descriptions, you definitely don't want a Dell...
Thanks again, guys, you have been awesome!
No worries mate!
Now for the bits I don't understand:
Everything was utter cake at that point.
So did you get a cake for fixing the family computer or something? Or was it some funny type of indigestion?
Hey Trevor, all I'm trying to do is get AMT's services and processes off my machine, since I don't need or want them. The reason I'm dealing with the drivers (or, was, that is to say) is because once I uninstalled all the applications and software and services AMT comes with, the Found New Hardware wizard would pop up on every startup. I figure, install the drivers so Windows/the devices are happy, leave off the software and services, and I am good to go, no more prompt. This line of reasoning follows the fact that I noticed AMT was already disabled in my BIOS and even disabling the devices in Device Manager wouldn't stop the prompt. This is all in my previous posts, I think ???
I understand trepidation re: OEM OS builds. But, it's all I've got and I'm not gonna shell out an arm and a leg for XP and Vista since HP just gave me both free...they work for me well enough IMO. I barely had enough to pay for the machine as it is :P
So I was unable to get into the MEBx environment but things seem to be going fine with the whole install-the-drivers-not-the-software workaround.