Hello!
What do you mean but why?
Do you mean about the consequnences? All I am trying to say, is that I do not have a lot of information about the driver. I have Window 7 and 64 bit. Dont really know if that will make a difference.
Seven is Vista under the skin, I think that drivers are the same, but the important word is THINK.
No, the drivers will not be the same. Vista and 7 are more different than some people realise. At the very least, that file will fail signature verification, if not worse.
Even if they are mostly similar, the major-minor version has changed from 6.0 to 6.1.
7 files will never work on Vista. Especially not driver files.
Also, 64bit drivers will never work on a 32bit system. Never. And, before anyone has a brain wave, SysWOW64 files will NOT, EVER work on a 32bit system. If anybody wants me to explain how WOW works, and how the kernal performs this native 32bit support, ask me
You will learn a lot I am sure! All about processor contexts, and user mode vs kernal land, which each of the WOW64 .dlls do in relation to each other, the exception to the rule, printer drivers, SysNative etc. etc.
I've got a copy of Vista Home Premium 32 bit as I stated earlier in this thread (I got ignored
). I can upload the file if you guys need me to?
Tom
Thanks Tom. I can also do it if people want!
*
Please remember, all of you, that drivers are not like other files. You cannot just get a similar file, and certainly not a similar file from a similar OS. You are lucky that this is 32bit. If you tried this on a 64bit OS, you would come up with the wrath of Kernal Patch Protection and Driver Signature and Checksum Enforcement.
Just remember that Installing drivers is not a cimple Copy and paste
With other drivers like graphics etc you will need one of 3 types of Drivers
.ini , .cab and can't remember the last one sorry
and then you would use DRVLOAD command in cmd to "Inject" the driver
I have not tried this for core drivers so this maybe hit and miss
Not in this case. The file is only missing. The driver is still in the registry under HKLM, LEGACY, CurrentControlSet, and ControlSetxxx times by several etc. etc. It is still loaded, and does not need re-loading.
Here are the steps to fix this computer:
DO NOT accept any files until somebody tells you that they aren't just grabbing any old copy of the file, but are being clever, and grabbing a file matched to your computer, and your Service Pack and update level -
your active driver.
- We need to make a bootable CD. Either from Neosmart, or any CD you already have.
- We will then run SFC, specifiying off bootdir and install disk.
- We then take a portion of your CBS.log after SFC has run.
- We then analyse the log file.
- I will then source the correct file, of the correct version, specifically chosen for your computer.
- We create a Packs.zip, and we use Robocopy to perform an offline fix which doesn't ruin permissions, otherwise we will fix the driver, and still have to reinstall.
Does anybody feel confident enough now, or do you want me to have a go? Too many cooks spoil the broth, and I don't want to do anything without permission.
Thanks a lot!
Richard
