Jan Alter wrote:
> "Desmond" <(E-Mail Removed)> wrote in message
> news:2048ce6f-984d-48ae-889b-(E-Mail Removed)...
> On Dec 12, 4:10 am, Desmond <otuat...@aol.com> wrote:
>> On Dec 11, 6:23 pm, Paul <nos...@needed.com> wrote:
>>
>>
>>
>>
>>
>>> Desmond wrote:
>>>> Hi I am having problems with using this mother board with Windows 7
>>>> 32 / 64. I have found in the past that motherboard manufacturers are
>>>> not end user frendly. Any downloads for this?
>>>> The CD states Vista inside. I thought that Windows 7 was just Vista
>>>> minus the deliberate bugs?
>>>> TIA
>>>> Desmond.
>>> http://support.asus.com.tw/download/...uage=en-us&mod...
>>> The motherboard is from 2007, so you wouldn't expect to see a heavy Win7
>>> presence.
>>> You can go to the various chip makers and get drivers there.
>>> But why not give Win7 a chance ? It probably has a ton of
>>> drivers built in. Let Win7 solve your driver problem first,
>>> before getting all bent out of shape.
>>> VIA drivers, for things like VT8237S storage features, or "Integrated
>>> Rhine"
>>> networking. For my VIA chipset motherboard, I got fresh stuff here. The
>>> Attansic chip could just be a PHY, and the driver you want instead is
>>> for the Rhine
>>> MAC in the Southbridge. Look in the networking section here, for
>>> Integrated
>>> Rhine and give that driver a try. The "MAC" layer is the brains, and the
>>> thing that gets the driver.
>>> http://www.via.com.tw/en/support/drivers.jsp
>>> RealTek HDaudio drivers.
>>> http://www.realtek.com.tw/downloads/...Langid=1&PNid=...
>>> If you've still got exclamation points in your Device Manager
>>> display, come back and give details. Or, using the first link
>>> above, go through the available drivers for WinXP, to understand
>>> what is needed to complete your Win7 install.
>>> Someone else may have tried Win7 on that motherboard, and
>>> this forum may have questions about drivers and the like.
>>> http://vip.asus.com/forum/topic.aspx...2V-MX+SE&SLang...
>>> "Most things seem to work"
>>> http://vip.asus.com/forum/view.aspx?...7&board_id=1&m...
>>> Paul
>> Asus take me to driver robot to download and run on my PC. Driver
>> robot has identified 17 drivers that require updating.
>> THE PUNCH LINE: I have to pay $29.95 to down load them. Cheeky
>> bastards.- Hide quoted text -
>>
>> - Show quoted text -
>
> Its the integrated vidio that is causing me a problem. If anyone knows
> the type that comes with the motherboard I could search for it.
>
> Desmond.
>
>
> It appears that this driver is being used for that mb
>
> VIA DeltaChrome
>
> but I'm not getting any conclusive results for drivers supporting Vista
> or Win 7 at the moment.
>
Desmond - my advice would be to never use "driver finder" links that advertisers
place on download sites. Be more careful where you click. I normally don't
find advertising on Asus.com web sites. Maybe you were actually using
a driver finder site instead ? Asus doesn't charge for drivers.
*******
So far, I have 17 browser windows open, and I'm not making much progress.
This link presumably has the "system of the week" listed, and right now, this
page is showing info for M2V-MX SE. First of all, their claim is the Northbridge
is K8M890CE, which is about a three year old chip. The VT8237S (I've got one on
my motherboard) may be slightly newer, but we don't care about that right now.
The Northbridge is the thing that needs a video driver.
http://www.fsf.org/resources/hw/systems
Asus M2V-MX SE
00:00.0 Host bridge: VIA Technologies, Inc. K8M890CE Host Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890 [Chrome9] Integrated Video (rev 11)
In the VIA marketing web pages, K8M890 and P4M900 "walk hand in hand", like
they were released at the same time.
http://www.via.com.tw/en/resources/p...VistaBasic.jsp
And yet, if I go to the VIA download page, I'm offered a driver for P4M900,
and K8M900 is not mentioned. it is like it "fell off the earth".
http://www.via.com.tw/en/support/drivers.jsp
Microsoft Windows
Windows 7 32 bit
Integrated Graphics
P4M900 Via Chrome9(TM)
The P900W7i.inf file from that p4m900(ce)-vn896(ce)-cn896(ce)_24-10-04p_bld2_win7_viawsetup_logod.zip
download, has this for an identity.
%S3GDeltaChromeIGP% = S3G700, PCI\VEN_1106&DEV_3371
If I go to the MSI web site, and look for drivers for K9VGM-V, they have drivers
for Vista, but no Windows 7. That motherboard uses K8M890CE.
http://www.msi.com/index.php?func=do...=1&prod_no=260
http://download2.msi.com/files/downl...K8M890_VGA.zip
The file K890LH64.inf in there has
%S3GDeltaChromeIGP% = S3G700, PCI\VEN_1106&DEV_3230
and a DEVice value of hexadecimal 3230 seems to be correct, from the info
I can find.
So on the one hand, VIA has a driver for Windows 7, with the wrong value
in the installer for it to install (they also don't include K8M890CE as
a candidate chip for that driver). If you use the VIA P4M900 driver,
it won't install, because the string in the INF is wrong.
On the other hand, an MSI driver for their K8M890CE board, has what
appears to be the right ID. The driver even unzips into a folder called
K8M890CE. But the thing is, they only offer a Vista driver, and no
Windows7.
If this was a new build, and there was no cost to me to start the install
all over again, I'd download the VIA driver, and change the one line to
match what I feel is the value actually contained in your chip. So the
P900W7i.inf would read
%S3GDeltaChromeIGP% = S3G700, PCI\VEN_1106&DEV_3230
You can either verify the VEN and DEV, by using Device Manager some how,
for the item which has the exclamation mark. Or, get a copy of Everest,
because it also lists VEN and DEV. This is the last version that Lavalys
gave away, and even if it doesn't name all hardware correctly, it may
still be able to allow you to verify the VEN and DEV on all hardware
devices sitting on system buses.
http://majorgeeks.com/download4181.html
So if you want to hack the VIA driver and give it a try,
go right ahead. I doubt I'm going to find a modern enough
K8M890 or K8M890ce based motherboard, to find a Windows 7
driver for it.
I understand it is possible to install Vista drivers on Windows 7,
but I'm not the right guy to ask about that. I don't have Windows 7,
and there are forums, USENET or private, that likely have more
info about across-OS driver hacks. I'd be less willing to try that,
than to hack the INF as proposed above.
There is someone in the same situation here.
http://www.viaarena.com/forums/archi...p?t-40141.html
Paul