hi folks,
since i updated my motherboard (msi kt4-l; ms-6712) bios i can not install gw anymore because my pc freezes as soon as i click ok after i choose the gw install path during the setup.
i also got the freeze problem when i try to access the windows sp2 security center and the internet explorer (iexplorer only locks up when the little cookie denied message appears, you know the one with the eye, and while windows update) :/
several os reinstallations didn't help either, maybe one of you can help me?
opera runs fine, upgrading other software through the internet (adaware, spybot search+destroy etc. ) works also.
i upgraded my bios with a bootable cd that creates a ramdrive and the bios update went fine, too. i also reconfigured the bios and tried to put my network card (i have dsl) into another pci slot, didn't help either.
maybe of you can help me? im so frustrated
thanks in advance
p.s. sry for my english, it isn't my native language
can not install gw anymore :/
maxpower
maxpower
problem solved
if one of you ever has problems with installing via4in1 drivers on a winxp sp2 installation, try right-clicking the driver installation file and choose windows 2000 compability mode, it will let you install the ide+agp drivers then and not only the inf ones
if one of you ever has problems with installing via4in1 drivers on a winxp sp2 installation, try right-clicking the driver installation file and choose windows 2000 compability mode, it will let you install the ide+agp drivers then and not only the inf ones
aeroclown
I don't know if this is still the case, but depending on the age of the via based board, I can remember having to pull out all cards during a reinstall except the video card. Then install the via drivers for the agp and pci bridges before replacing all the cards. Otherwise the system would not recognize any new devicen or install it properly on other slots.
maxpower
ah thanks for the tip i will try that, because now windows runs fine but gw locks up everytime
edit: problem finally solved, it turned out to be the bios update. my motherboard is revision 1.0 and i used the 1.1 one
edit: problem finally solved, it turned out to be the bios update. my motherboard is revision 1.0 and i used the 1.1 one