neu² wrote:
neu² a formulé la demande :
Hi

i have this mainboard : gigabyte p55-usb3
i have some difficults to install win xp pro and recognize the memory
( 4096 and it recognizes only 3,4)
So i was with bios F2 and i ve installed bios f4 ( downloaded on the
server of gigabyte )
for install this bios i've used @bios and file downloaded in my
personnal docs
But now , my computer reboot and reboot and reboot etc...........
impossible to load new and old bios

how resolve this big difficulty ?

thx at all

no help in giga website , no help here = return to asus mobo
giga no resolve this ****ty problem ,infinity reboot



Have you tried to install the old BIOS again, so that the dual
BIOS versions match ?

My understanding was, that dual BIOS is not a true dual BIOS.
There may be two storage areas, but they share one boot block.
So you have boot block, main code #1, main code #2. If the
boot block is damaged, then it may not start. I don't know if
that description is correct or not, and I don't even know how
you'd go about verifying it. (I don't know if a BIOS utility
can even see both chips at the same time in the address space.)

In any case, you'd try to get back to where you were, rather
than trying to run some mix that doesn't work. It really all
depends on whether the two BIOS are happy to coexist at the same
time. For example, if Gigabyte really needed to update the boot
block, and didn't take care to test with the other BIOS releases,
maybe that could mess it up.

If you change a BIOS, strictly speaking you should do "Load Setup
Defaults" or the equivalent, as it is possible the BIOS settings
can change definitions after a flash upgrade. Again, this would be
a stupid thing for Gigabyte to do to the source code of the BIOS,
but it could happen.

If you're finding the system won't boot, it could be the BIOS setting
for the disk operating mode, no longer matches what it was previously.
ACHI versus RAID versus IDE. That kind of thing. Double check
the BIOS settings for the SATA ports, and that something there
hasn't changed.

Your original premise was wrong. It is perfectly correct for a
*Microsoft* 32 bit OS, when confronted with 4GB of physical memory,
to report only 3.4GB is free. This is an address space problem, and
a purposeful decision by Microsoft. While PAE exists, and could solve
the problem, Microsoft changed things, such that the 32 bit version
of Windows is restricted to a 32 bit address space. Some room in the
address space is needed for PCI Express bus (video card memory) and
PCI bus devices. Typically, the BIOS assigns a minimum address space
of 256MB each for those. So you'd expect 3.5GB free at most (for a
system with two busses, and some hardware present on each bus). Then,
depending on how much memory is present on the video card, the BIOS
can allocate more chunks of 256MB size for that (chunks of address space,
not memory). The remaining address space is then used to address the
system memory. If there aren't enough addresses left, to address the
entire installed memory, that is when you get the "3.4GB free" in
Windows. So flashing the BIOS was unnecessary.

For some background of the Microsoft approach, try here.

http://www.geoffchappell.com/viewer....nse/memory.htm

PAE has existed for a long time, and the original Intel implementation
allows a 32 bit virtual address to map to a 36 bit physical address.
Larger implementations are possible, and AMD has a 40 bit physical address
in their current implementation. A single operating program, can address
a 32 bit limited area, out of the entire memory, by using PAE. So if you
had 64GB of memory installed on a PAE setup, a single program could use
4GB. That is the basic idea. It isn't as flexible as a pure 64 bit
environment, where a single 64 bit program running on a 64 bit OS
could access all 64GB or more.

Perhaps you can use Q-Flash, to get back to the original BIOS setup.

Paul