Re: M2N8-VMX motherboard



Venom wrote:
"Venom" <Venom@xxxxxxxxxxxxx> wrote in message
news:Ifs%i.13745$CN4.6644@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Fred" <bluser@xxxxxxxxx> wrote in message
news:5q6vt0Fud69bU1@xxxxxxxxxxxxxxxxxxxxx

"Venom" <Venom@xxxxxxxxxxxxx> wrote in message
news:JIn%i.13626$CN4.1928@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Rob" <robc@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:PdmdnQaQDvyNZ6DanZ2dnUVZ_jSdnZ2d@xxxxxxxxxxxxxxxx
Venom wrote:
"Rob" <robc@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:kMWdnYfwaej8OqDanZ2dnUVZ_umlnZ2d@xxxxxxxxxxxxxxxx

Venom wrote:

Is there anybody out there in Australia using this motherboard?
The motherboard drivers cd was not with the motherboard when I
got it

and I

have downloaded everything from the ASUS site but I still
can't find the driver for ACPI \ ATK0103 High Precision Event
Timer and I was wondering

if

anybody else is having this problem.




V,
Look on the Downloads Page under Utilities at the very bottom.
You should find it there.
Rob C.



There were two problems in device manager and that fixed the
ACPI \ ATK0110 problem but not the ATK 0103 problem.
I read a post in Google where one bloke said that this driver
automatically loads when you load the motherboard drivers from
the motherboard cd but was not of any more help. I just find it
odd that this is so but I guess he could be right as I have no
way of proving it. Getting another motherboard is out of the
question for me at this time.



V,
The drivers on the ASUS website aren't always the newest. You
might download therm direct from nVidia. If your using
WinXP(32bit) I believe you have a 405/6100 chipset on your board.
If so, try here:
http://www.nvidia.com/object/nforce_nf4_winxp32_8.26_11.09.html
If the error is related to the brains of the board that may cure
the issue. Might have something to do with AMD Cool N' Quiet as
well! Do you have it enabled in BIOS?
Rob C.


You are correct in your assumptions with the chipset and XP Pro
32bit. Cool
and Quiet is enabled. To my way of thinking, an error is an error
and should
be fixed. The grossly annoying part is that the hard drive led on
this case
is nice and bright and flashes like a strobe security light. Damned
annoying.
I tried that driver and nothing has changed except that now my
SATA hard drive and burner are now on the taskbar in the safe to
remove section. Obviously it is not that particular driver problem.

Re you using XP SP2? The high precision event component was
supplied with sp2.


It must be only with nVidia chipsets then. I have built one with SIS
and one with VIA chipsets with no drama just starting with SP1. I
don't have a slipstreamed XP Pro and as all my bits and pieces are
on external USB drives I only load SP1 to get the USB gear working.
My next thought this morning was SP2 but the damned thing crashed
before I tried it. Later on this afternoon I will format and start
again but try SP2 and see what happens.


SP2 sorted the little bugger out ok so that has to mean that the
driver is on the motherboard cd in the first place.

Actually what you had was a pci device that was unknown to your copy of XP.
IMHO all SP2 did was instal a null inf file to get rid of the yellow
exclamation in device manager.
I don't think XP can actually support the High Precision Event Timer but
Vista apparently can.
From http://www.microsoft.com/whdc/system/CEC/mm-timer.mspx
"This article provides information about the requirements for a new system
timer that is needed in chipsets to replace legacy timers and to meet the
needs of time-sensitive applications. System timers are the timers used by
the operating system to perform core tasks such as tracking the time of day
and triggering time-based events.

Chipset vendors should implement an HPET to comply with Intels "IA-PC HPET
(High Precision Event Timers) Specification". This spec will be available on
Intels web site in the second quarter of 2002 with royalty free licensing
terms.

Microsoft is in the process of adding the requirements for the HPET to the
Windows Logo Program for Hardware to check for the presence and quality of
the HPET in chipsets. Although no timeline has been set in regard to when
this hardware will be required for a logo, Windows Hardware Quality Lab
(WHQL) tests will begin testing the quality of the HPET, if it is
implemented, in the timeframe of the release of Windows Vista."

All I have to do is find someone who is using this motherboard and
get a copy of the motherboard cd from him and all will be well.

IMHO I think all the files you need are either in XP or available from the
web or at Asus ftp
ftp://ftp.asus.com.tw/pub/ASUS/mb/socketAM2/M2N8-VMX


.



Relevant Pages

  • Re: M2N8-VMX motherboard
    ... System timers are the timers used by ... Chipset vendors should implement an HPET to comply with Intels "IA-PC HPET ... get a copy of the motherboard cd from him and all will be well. ... Timer and one chap said that the driver loaded from the motherboard cd ...
    (alt.comp.periphs.mainboard.asus)
  • Re: P4P800 SE -- drivers for networking?
    ... Your manual should have a drawing of the motherboard, ... shows a Marvell driver ... Marvell, ... I checked in the BIOS and the on-board LAN is enabled but the onboard LAN ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Dead Mobo or PSU?
    ... cleared out a bunch of dust and decided to buy a new heatsink and PSU ... was searching for a new driver to the new 8600 GTS, ... download and install that driver while the system was still shutting ... motherboard wasn't even going through post anymore. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Epox EP-8RDA3+ motherboard
    ... Nvidia motherboard chipsets just aren't Linux-friendly -- because ... Linux can deal with basically any ol' CPU and any ol' RAM circuitry; ... but doesn't list the driver. ...
    (comp.os.linux.hardware)
  • Re: No audio device after latest Widows Update
    ... the driver you need will correspond to the audio codec on your motherboard. ... While the vast majority of onboard audio solutions are either AC’97 or HD ... determine what type of audio solution you have on your motherboard. ...
    (microsoft.public.windowsupdate)

Loading