• 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.

Update - New VIA 4-in-1 Drivers Available

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
UPDATE from VIA Arena!!!!!


The problem was replicated on a P4 chipset system with 1MB of RAM. They have now been removed from VIA Arena.
VIA Arena Team
Web Media Liaison
VIA Technologies, Inc.
Click to expand...


HEHE looks like we`re right, these drivers have been pulled from their site,now the 4.49s are back up 🙂.
 
Jeff, that was the 2.41s that wreaked much havoc on us. The 2.42s weren't as bad but they too got pulled in lieu of the 2.03s.
 
I had the same problem, reformated and reinstalled everything Tuesday into Wednsday 🙁... A few things to point out:

1-"For all VIA chipsets using Microsoft? Windows Operating Systems"
2-What I had was some kind of overflow error. I tried going back to the last known good config, and that worked to an extent, but every single program I ran came up with a file corruption error, and sound didn't work. Tried uninstalling drivers, no. Tried reinstalling last release, no. Tried repare, nothing. I had to reformat. While I suppose it could be my fault for not backing up, I don't see how so many people (especially @ the VIA boards) can defend the company without being willing to admit that VIA made a mistake here. All I'm getting there is "backup twice a day" and "you obviously didn't try all the fixes listed" etc.
 
At least VIA pulled them which is a good thing,I also find it funny they were WHQL certified by Microsoft ,shows you how important that is.

🙂
 
Talk about early adaptors.
rolleye.gif
 
So far I don't think Iv had any problems with them. Not sure if its related but IV had to lower my FSB back to 133 due to some radom lock ups. Since I cant remember when the locks upstarted vers when I installed the 4.50's, does anyone know if they could be causing my OC problems at higher FSB speeds?
 
Originally posted by: Megatomic
I'm glad to hear you've managed to repair your system temporarily Quixfire. :beer: I'd take this opportunity to backup all your data, format c:, and do a clean install.
Click to expand...
That's what I did for Thanksgiving, besides eating turkey 😀, and I have a fully functional PC again.

 
UPDATE:
We would like to sincerely apologize for any problems that people have experienced with the Hyperion 4in1 4.50 drivers.

These drivers were removed from the download page on VIA Arena and from the VIA Arena ftp, once we started receiving reports of the drivers causing problems. These drivers were officially tested and certified by Microsoft and VIA to work correctly and efficiently with Windows Operating systems that have Microsoft certified drivers installed.

After detailed investigation of the issues that have been reported, we have found that they only occur with systems configured with 1GB or more of memory and an ATI graphics card where the AGP aperture has been set above 32MB.

We are currently working on a new revision of the driver that changes the default size of the AGP aperture to 32MB.
Click to expand...



Link.
 
I am happy with their apology except for one thing... It happened to me and I only have 512MB RAM. Seriously, I don't think they've gotten it right yet...
 
And these stupid VIA fanchildren over at the VIA help forums aren't any help. The little *-suckers don't stop telling me that I should have backed up and it wasn't VIA's fault and that VIA can't possibly test every single setup. How in god's name do you not test with a video card from a company that, from a gaming standpoint, is ahead of anyone else as far as the entusiasts go? If I had my password with me (I'm at school), I'd be posting this over there, but as it is I don't and I need to get this out. I am going to go off (explode) on that message board when I get home if those little moronic brainwashed mother f'ers don't stop being such assholes.
 
I am happy with their apology except for one thing... It happened to me and I only have 512MB RAM. Seriously, I don't think they've gotten it right yet...
Click to expand...

Same here as well,however I do have my aperture size set to 128mb so wonder if that was the cause?
 
UPDATE: I`ve installed the 4.51 drivers via safe mode since I had write failure with 4.50 drivers so did not want to take any chances,just rebooted after to normal desktop and everything is working fine 🙂.


So looks like these are fine so far .Make a system restore point if you`re worried.
 
That's a has to be a joke ... right ...?

Telling users to use safe mode AFTER thier system corrupts >...?

They should just say ... "INSTALL USING SAFE MODE" ... BEFORE thier system corrupts ...

... wtf is with that ...?

The 'word' from Via
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top