Biostar

Please notice there's a Jumper JP8 stick together with the JPANEL 1. You might treat the JP8 as part of JPANEL 1.

The function just able worked under windows 98/98Se/ME, but it unable to work under windows XP/2000/NT and DOS environemnt.
This is because both of windows 98 and windows ME are using polling way to check the CPU's Temperature per 6 seconds. But, these perating system as windows 2000 & NT & XP are using a Event action to check it.

Yes. M7VKH can support AMD Morgen and Palamino series CPU. However you need to update the BIOS to VKH0528F .

So far, M7VKB motherboard had designed on two different types, with and without CPU Temperature's sensor. Please refer to following descriptions:

• Version 1.0 & Version 1.1: These two version motherboards had the CPU Temperature's Sensor.
• Version 2.0 & Version 2.1: These two version motherboards had no CPU Temperature's Sensor.

M7VIB Is designed for both Register DDR and Un-buffer DDR memory. The different between Register and Un-buffer memory Is, the Register memory able to control the CAS and RAS timing. This Is because the Register memory has a built-in controller. If the system detects a controller on the DIMM, the memory driving timing will be controlled by the memory itself. As per Un-buffer memory, the system will control the memory timing.

We had tested the M7VIB with following GeForce 4 AGP card, no any problem was observed. MSI-G4MX460-T, ELSA-Gladiac517TV-Out, ABIT-SiluroGF4MX, Winfast-A170R/64MBDDR, PROLINK-Geforce4 MX440, Asus-GeForce4MX440 and SUMA-Platinum GeForceMX440

The problem Is caused by the Memory compatibility Issues. The problem can be resolved by update the BIOS to VIB0726F.

The Windows 2000 Operating System unable to detect the HPT370 chipset automatically, so, we need addition driver for It. Please refer to our CD installation guide under VIA driver CD, path as \MANUAL\SW\MIA.PDF. Please follow the Instruction In order to complete the HPT370 installation procedure.

The problem Is caused by the Chipset coding error. Updating a new BIOS of MIA0517F, will solve the problem.

The timing calibration code in the Network Driver Interface Specification (NDIS) driver causes a divide by zero if the CPU runs at 2.2 GHz or faster. This problem does not occur with CPUs that run at 2.1 GHz or slower. Detail solution that you can contact with Microsoft for the following URL.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q31210