My PC is a Win 7 64-bit box with the above named motherboard.
Inadvertently, a floppy disk from our digital camera was left in the PC
. When I booted up the PC in the morning. POST stopped at booting up at
USB devices which the USB floppy is....at the bottom of the screen there
was a message that there was an "overclocking failure". I have an I7
chip that was minimally overclocked from 2.67 to 3.36 and was incl with
the package.
Then the PC offered me two choices..go into setup or hit F2 to continue
to boot. The PC booted up just fine.
Here are my two issues. (1)When the PC boots up now, it goes to Asus
Express. I can let it sit for a few seconds, or hit exit, then the
motherboard screen appears and offers me to go to setup by hitting DEL
or Tab for POST. I let is sit for few seconds and then it will boot
normally into Windows. (2) A message pops up telling me that the USB
device that I tried to install is not recognizable and was not
successfully installed. I was not attempting to install any devices.
There was no hint, like in Win XP, that there was a non-system disk in
the PC...nothing at all.
I think the BIOS is the issue, but I am not sure what should be done
next. I am not concerned about the overclocking in the least. Can
someone give me a clue (who has only flashed one BIOS upgrade in my
whole life) about the best way to clean up the bootup process.
Thanks,
Diane P.
Enter the BIOS, go to the "Tools" menu, and look for Asus Express Gate.
If you disable that, then the annoying delay should be removed.
Don't forget to use "Save and Exit" from the Exit menu, so that
the change you've made will be saved.
Express Gate is like an alternative to an OS. The idea is, it boots
so fast, that you can use it for things you want to do quickly. Like
checking a weather report on the web, before turning off the computer
again and heading out of the house.
Asus Express Gate wasn't invented by Asus. It is an instance of Linux
SplashTop. You can get more info here. Asus has various options for
installing it, which will be detailed in your manual. Your builder
may have installed it.
http://en.wikipedia.org/wiki/Splashtop
*******
With respect to one aspect of your problem, be aware that Asus has
an overclocking recovery feature (don't remember the name). The BIOS
has some way of determining, whether the last shutdown of the computer
was clean or not. If the system seems to have "crashed" during the
last session, the BIOS may choose to reset the BIOS settings to
safe values. It should return the CPU clock to nominal, so that
you can get into the BIOS screens and fix whatever is wrong.
On some motherboards, maybe only the clock setting is changed. On
other motherboards, all sorts of stuff gets changed, which is not
what most people are looking for.
So that is one way, that all your BIOS settings can be in danger.
A second thing, is if the motherboard CMOS battery dies, and the
settings are lost.
For those occasions, it is a good idea to have digital camera
photos of each BIOS screen. If some day you lose the settings,
for any reason, refer to the digital photos for a record of
the settings.
Some motherboards are fancy enough, that they store a "profile".
Some computers can store more than one profile, and support
restoring the profile using a BIOS option. Those motherboards
reduce the need for digital photos (depending on where the
profiles are stored). It is possible, if the BIOS was reflashed
on a board like that, the profiles would no longer be valid,
and they'd be blown away. So even though some motherboards
do a better job of managing user settings (by storing them in
a profile for easy recovery later), there are still reasons
for taking photos of all the BIOS screens. The profiles are not
completely immune from "attack".
If you don't like the paper manual that came with your
motherboard, you can get a PDF version from the support.asus.com
download site. I find that a bit easier to read, and I can
zoom in to read the fine print. With manual in hand, maybe
you can get that overclock working again :-)
http://support.asus.com.tw/download/download.aspx?SLanguage=en-us
*******
I had a strange case like yours once. I was putting the cables back
on one of my computers. The keyboard and mouse are color coded, but
I had a "senior moment" and stuffed them into the wrong color connector.
When the computer started, it reset all the BIOS settings. Sounds
a bit like what happened to you, with your weirdly formatted floppy.
I guess the BIOS doesn't deal with all situations, equally well.
Some things just send it into the weeds.
Paul
Thanks very much for your thoughtful response. I greatly appreciate the
time you have taken to help me.
I will tackle the USB problem next. I'm sure somebody in a USB forum has
seen this issue before. Happy Holidays to you.
Diane P.
Try looking in the setupapi.log file, near the bottom (where the newest
entry can be found). Use the VID and PID to see if it is your USB floppy
drive that is "being installed" or not.
C:\WINDOWS\setupapi.log
If it is not obvious what device that is, there is an (informally kept)
list of USB devices here. People submit entries, and that is how the
list is maintained. The official USB list is secret, to hide those
companies that aren't ready to go to market yet.
http://www.linux-usb.org/usb.ids
For an example of a USB floppy. VID=03EE hex, PID=6902 hex.
03ee Mitsumi
6902 Floppy Disk Drive
Paul