• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Via driver update screws up everything!!!

U

Uthiroid

Senior member
Helping a friend update the via drivers on his system. the driver program crashed the first time we installed, so we repeated and it went fine (or so we thought). On reboot, it enters the windows boot phase and says-
"setup is updating files" or some variation, which is typical,
but then it enters a loop that continues to give the error
cannot update file %1, %2
%1:%2.

this just keeps repeating and nothing else will happen.
I tried a floppy boot and reinstall of winME (i know, please no os cracks) without any change...

my question is this.
does anyone know where the driver update programs store the information for windows to change files on reboot? I know it has to be in the registry, like a runonce entry or something, but i'm not sure. i wanna fix this WITHOUT a full reinstall... he has plenty of apps already installed.

also, does anyone know the best procedure for registry editing from a dos-like (text) state? How do you do it?

system-
abit k7t
tbird 800
128 pc133
30gb quantum hd
diamond mx400
generic modem
radeon 32ddr
winme

thanks for any answers- help me help myself!!
 
Are you sure that you have the latest VIA drivers available? Check the mobo website to see what the latest version is and/or if they have addressed this issue before.
 
What OS? Try booting safe mode and pick last good configuration, or installing the 4in1's in safe mode. Which via version are you trying to install?
 
Thats what sucks... I can't even boot into safe mode, because the setup tries to update the configuration even before continuing a boot. i can't get to safe mode even!

 
It'a a long shot, but try to boot up and then turn it off and then back on(after 30 seconds) for 3 or 4 tries. I have had this work for me on a couple of ocassions and not work on many other ocassions.
 
I am happy to try that, but are you trying to get around one of those boot hang issues we've heard about in via chipsets, or are you doing something different? this seems more of a configuration problem. somebody else told me to reset the cmos. anybody vote for that?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top