EPoX and AMD-v?
R. C. White
(Anybody here?)
My EPoX MF570sli motherboard is still running fine! I bought it 3 years ago
to install the new Vista Ultimate x64, and it is now running Windows 7
Ultimate x64, with 4 GB RAM and 4 Seagate SATA HDDs.
But when I tried to install Win7's XP Mode yesterday, after a half-hour of
churning (mostly at "94% complete - Do not turn off your computer"), the
installer announced failure and rolled back the VPC software. Then,
belatedly, I ran amdvhyperv.exe to test for compatibility for my AMD Athlon
64 X2 5000 CPU. It reported:
"This system is not compatible with Hyper-VT.
"This utility detected that a necessary BIOS patch is not installed.
"Please contact your system vendor to determine whether a BIOS upgrade is
available.
" If so, upgrade your BIOS and re-run the utility.
" If not, consider upgrading to a new AMD64 system to get the latest in
virtualization capabilities, performance, and power efficiency. AMD's most
current processors do not require a BIOS patch to run Hyper-VT."
I have the latest available BIOS, dated 07/07/2006 (although the BIOS string
on boot up shows 8/1/07) for this mobo, according to the all-but-dead
website, http://www.epox.com/product.asp?id=EP-MF570SLI .
So I have two questions:
1. Is there a later BIOS for the MF570sli?
2. Will a Phenom or other current AMD CPU run in this motherboard?
OK, 3 questions:
3. Any advice?
I still love this mobo and really miss EPoX.
RC
--
R. C. White, CPA
San Marcos, TX
r...@grandecom.net
Microsoft Windows MVP
(Running Win7 Ultimate x64 on EPoX MF570sli)
gdp
has a listing for a bios dated 12/22/2006. The date of the bios bin
file in the zip is Jan 12 2007. The statement of changes for this bios
version is
Added support for new processors, manufactured on 65 nm process technology
Not sure how your bios is identified in the "post" screen on bootup, but
the name of the bios file is m5sl6c22.bin. The m5sl identifies the
motherboard, and the 6c22 is Dec 22 2006. If you try to update the
bios, save the old one in case it actually is newer than the one at the
Russian site. AMD says all Rev F or later desktop processors (except
Semprons) support AMD-V. All socket AM2 processors are Rev F or later.
But my guess is that anything less than very recent processors need to
have a motherboard with a BIOS that recognizes that capability.
With the most recent BIOS no newer than Jan 2007, the Phenoms won't be
recognized. It's *possible* it might be able to boot with one, but even
if so, it likely won't have the right multiplier, voltage, and won't
enable all the features.
Good luck.
gdp
gdp
virtualization on? The following suggests that it needs to be turned
on, and the NX bit set in BIOS
http://4sysops.com/archives/free-detect-intel-and-amd-hyper-v-compatibility/
R. C. White
Thank you for your two Replies!
My understanding is that it MUST be a BIOS implementation. I searched my
BIOS settings today and could find nothing that looked at all hopeful. I'm
an accountant (and retired), not a techie of any kind. I've got 30+ years
of experience with PCs and predecessors, starting with the original TRS-80
in 1977. Nobody else in town knew anything about them, so I had to learn a
lot more than I intended, just for self-defense, but never got much past
GWBASIC and a smattering of Z-80 assembly language. So I'm nowhere near
qualified to modify a BIOS chip.
XP Mode interests me, but I'm not sure why. I haven't even run WinXP in
over 4 years - and don't miss it. I've beta-tested Vista and Win7 and have
run little else in the past few years. But I do enjoy a challenge - and
learning - so I wanted to see if I could get XP Mode going on my rig. I
created a VHD in Win7 a few months ago; I haven't really found a use for it,
but the comments on that 4sysops site suggest that it might be a workaround
to enable Hyper-v. (By the way, in my first post, I typed "Hyper-V"
followed by TM in parentheses. WLM converted that to the trademark symbol
on my screen, but it appears as simply "Hyper-VT" in my post. There is a
picture of that message in the 4sysops article.)
Those links you gave me look interesting. My son is a programmer and reads
Russian (a little), so maybe he can translate the .ru website and help me
decide whether to try that route. I have burned a few BIOS EEPROMs, but
don't think I could hack one to "enable the NX bit".
It's good to know that I'm not the only EPoX diehard who still checks this
NG. Thanks!
RC
--
R. C. White, CPA
San Marcos, TX
r...@grandecom.net
Microsoft Windows MVP
(Running Win7 Ultimate x64 on EPoX MF570sli)
"gdp" <gdp...@cox.invalid> wrote in message
news:UliTm.49629$ky1....@newsfe14.iad...