K7D master, Scsi raid cards, bios flashes and confusion
K7d master-l
Ram, crucial reg+ecc
psu more than enough, zippy/emacs
2*amd 2500+ pin moded to 2000mhz (will do 2.2ghz very stable, your pick fold for 2 mouths between reboots or prime? Longest prime run I allowed was 72 hours both CPUs.)
To cut to the chase when I install a fully functional Hp netraid-4m in an available 66/64 slot or any other for that matter the computer hangs at point "initializing hard drive controller".
The card caries on doing its self-test and then nothing. No beep no message just a blinking cursor --> _ *<--blink*
First thing I tried was sans 3ware raid card but same problem.
The next thing I tried was graphics card and NetRaid only in multiple slots, same problem.
Thought "...well maybe a BIOS could solve the problem?" I have done a few flashes before but not on this.
Downloaded two separate BIOS from main site and they both stop responding just after I agree to it reprogramming the bios chip.
Nothing is done when it hangs here. The computer is bootable. First time it hung I waited an hour each subsequent time 10 minutes.
Interestingly my bios does not appear to be in this list.--> http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=73&kind=3
The date on my bios is 13/12/2002 (that’s dd/mm/yyyy) and is v6.00 ?? ???
I couldn’t find any option in the bios for write protect.
If I try: "4. Input "awfl823d w6501kms.xxx /sn/py/cc/cp/f", then press ENTER" nothing happens, computer crashes, ctrl+alt+del don’t reboot it, caps doest toggle.
Flashing done from a bootable dos cd and the bios and flash utill are stored on a fat16 hard drive partition. And have tried 5 times.
Any help with these two rather odd problems would really be appreciated.
Thanks
edit: my graphics card takes up 2 slots its a x800xtpe with a silencer. 256mb.
edit2: https://forum-en.msi.com/index.php?topic=24059.0 <-- im hoping that its a bios ishue like this person had but with a different card.
Quote from: jefuk on 11-September-06, 18:52:30
thanks for the reply. I am not convinced by flashing in windows though so i used good old dos on the made for the purpose boot cd. I keep a fat16 partition for things like this too.
my steps were as follows
1 pull plug
2 clear cmos
3 plug in. "what why did u turn your self on?"
4 insert dos cd
5 flash "its working!"
6 reboot
7 panic "whys nothing happening?"
8 unplug, clear cmos etc "ITS ALIVE {insert manic laugh}"
now iv seen windows works ill shut down and test the card
I have used 191 I don’t know where you found that bios from its not on an msi server ether? sorry to say i don’t trust much :(
what benefits/bug fixes does it have?
Edit: Well the card is now detected it reports 6 disks attached each with a unique id and then it stops responding, wont let me into config. I’m figuring one disk could be at fault but my original problems are all resolved thanks to a bios update.
little hard but nice you have finaly able to update it.
"what benefits/bug fixes does it have?"
Changes from 1.91(old) to 1.90(newest):
Added support for Athlon MP 2800+
Fix somethink about Vcore problem but cant translate it (Behebt Probleme mit der CPU Kernspannung (VCore).)
"I have used 191 I don’t know where you found that bios from its not on an msi server ether? sorry to say i don’t trust much :( "
dont worry we are never give/suggest you somethink that gona do damage/unsure its work correctly or somethink like that, especially when we are talking about BIOS updates. im thinking always from other side(etc in this case from your side what will be best for you) BIOS is tested and proved himself in time, thats why i recommend him. MSI Global servers are not always up to date.
Here you can look from MSI official also but not global:
http://www.msicomputer.cz/soubor.php?produkt=MS-6501+(K7D+Master-L)&typ=%25
http://www.msi-computer.de/produkte/main_idx_view.php?Prod_id=191&Seite=BIOS
There is also newest beta version (2.01 which added support for Sempron CPUs) exist at German MSI, but i didnt recommend couse didnt tested and lag of info about it, you can test it also at own risk. Probably will work good also but personally cant gurantee for issues or anythink about it.(but that is my guess only and i dont work with gueses.)
"I’m figuring one disk could be at fault but my original problems are all resolved thanks to a bios update. "
you are welcome mate
Similar Messages
-
Raid card bios not working/G31m
hello,
mb bios updated to newest version 7.4. anyway, still
not able to configure Raid card.
thanks.what's current bios version? and what bios you version you want to flash?
Quote
mb is g31m.
what's your mainboard http://eu.msi.com/index.php?func=searchresult&keywords=g31m -
K7D Master Freezing in several Linux Distros and Kernels
It seems that no matter what I do, I can not get linux to function correctly in SMP on my box. It works fine in single processor mode. The only non-user caused problem is that the box freezes in SMP mode somewhat intermittantly . It will freeze for quite some time, then when it gets going again, it works fine for a while, then freezes again. I have tried to get it to duplicate when I am doing things, but there doesn't seem to be anything specific that sets it off.
I have tried to change the SMP mode in bios to no avail..
I have used several different distros including Mandrake, Redhat, and SuSe. I have gotten the latest SMP kernel to no avail. The box works fine in XP Pro, and is just OK in 2K (It is a bit slow and choppy till I get SP3 on for some reason... Oh well...). It works great in any distro of linux in single mode, but SMP just won't work.
Specs:
1X MSI K7D Master
1X Leadtek GeForce 3TD AGP
2X AMD Athlon MP 1900+
1X Crucial 512MB Registered DDR Dimm (PC2100)
1X Creative Labs SB Audigy Gamer
1X Plextor 16/10/40 CDRW
1X Toshiba 16X DVD
1X Antec 400W PS
If you need more information, please email me or just post here... I will check fairly often as this is getting to be quite annoying now, and I can't seem to figure it out.
Phobia
[email protected]>>
Did that one... They were all fine and dandy...
>>
Did that one too... Should have mentioned that in my first post...
>>
I had it on checking only... Changed to scrub... Didn't change a whole lot though. I guess it was worth a try though.
>>
Still freezes... Had Scrub enabled... still freezes... I also threw in a stick of Corsair registered and it does the same thing. I also switched CPU positions on an off chance, and that didn't help.
I am beginning to wonder if I have a bad board. The only thing that keeps me from thinking that is that it works with XP and 2K just fine.
Thanx for the suggestions, if you can think of anything else please post it. I am getting desperate.
Phobia
[email protected] -
BIOS FLASHING
We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
>>>MSI Forum HQ USB Flashing Tool<<<
If you are unable to use the MSI HQ USB BIOS Flashing Tool
>>How to create a dos bootable USB stick>>
It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
For Intel Users, flash via FPT
Socket LGA 1150 : >>ME 9 FPT files & Instruction>>
Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
Linux users
See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
Modified and BETA BIOSes
Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
WHEN IT ALL GOES WRONG...
BIOS RECOVERY
In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
For Modern MSI Systems, refer to:
<<Multi-Bios Equipped Mainboards>>
<<Single-Bios Equipped Mainboards>>
Legacy Systems:
For Award BIOS
Make a bootable floppy disk*
Copy the Award flash utility & BIOS file to the said floppy disk
Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
Sample on how to create an autoexec:
a. On Windows, open the notepad
b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
c. Save the file as autoexec.bat
Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
Re-flash the BIOS & reboot.
*Need a bootable floppy disk? Look here: http://www.bootdisk.com
**Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
For AMI BIOS
Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
When 4 beeps are heard you may remove the floppy disk and restart the computer.
For new boards with AMI BIOS core 8 (4MB)
Discovered by Jack The Newbie:
Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
What has to be done (tested on P45 Platinum):
1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller. Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
4. Press CTRL + Home to trigger BIOS Recovery. -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard. However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
What should happen now:
1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
4. Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
BIOS recovery on Wind netbooks
See this post here:
https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
BIOS recovery on non-UEFI notebooks
In order to recovery this type of system you will need an FAT32 formatted USB stick.
Download the applicable bios from MSI's website and rename this bios.
It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM You may need to try each way to determine which one is necessary.
Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
Now you are ready to cover the Notebook.
To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
IF ALL ELSE FAILS...
Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
If your BIOS chip is in a socket, like...
...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
Updated 11/21/2013, original post by StuA.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
B.) Download and install the >>MSI HQ Forum USB flasher<< .
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB from working bios B.
G.) Once it booted successfully switch to bios A without powering down or rebooting
H.) Now follow the directions and let the tool flash bios A with desired version -
Apple Raid Card, multiple drives and volumes
Hallo,
my xserve (early-2008) has an Apple Raid Card and two 300GB SAS-drives installed (mirroring).
Is it possible to install a third disk (300GB SAS) and to use it as a separate Volume ?
Disk 1 (300GB SAS) - Apple Raid Card mirroring: Volume 1 (300GB)
Disk 2 (300GB SAS) - Apple Raid Card mirroring: Volume 1 (300GB)
Disk 3 (300GB SAS) - Volume 2 (300GB)
How do I have to set this up using Apple Raid Utility ?
Thanks for your help !Is it possible to install a third disk (300GB SAS) and to use it as a separate Volume ?
Yes. Of course.
How do I have to set this up using Apple Raid Utility ?
No. A third drive should just appear on the desktop. You only need RAID utility if you want to add that drive to an array, which doesn't sound like the case here. -
MOVED: MB:MS-7366 Udated with latest bios flash and am getting Device Manager error
This topic has been moved to Older MSI motherboards.
https://forum-en.msi.com/index.php?topic=180048.0Hello Svet,
Quote from: Svet on 05-May-14, 20:27:12
delete the device with yellow mark then reboot and let windows to redetect it
Many Thanks for your reply! I tried deleting the Other Devices/Coprocessor entry and restart, but with no luck.... it came right back.
As I said, it's more of an annoyance than it seems to be a hindrance The device manager does give me the option to "disable" it, but I'm just going "to leave well enough alone" .
Again, thanks for your help..... Mark
-
Apple RAID Card and 3TB Drives only show 2.2 TB
I tried a 3TB Seagate Barracuda XT drive in the July 2010 Mac Pro (and a Jan 2008 Mac Pro) on the RAID Card that came with the machines (so one is the RAID Card now shipping) and both show a maximum of 2.2 TB with a 3TB drive.
I'm curious if anyone else has tried this with different results. Any luck in getting the RAID Card to see the full 3TB in the drives?
By the way, without the RAID Card, the Mac (OS 10.6.4) sees the full 3TB, but not with it.
Anyone else seeing this?Okay. Seems Apple didn't plan for or certify 3TB.
However, Apple doesn't support using 3rd party drives. Some do, and in some situations, drives you would think work don't, or they work but only briefly.
When I said read FAQ I was thinking of all the points like this:
Question: *Which drives does Apple support for the Mac Pro RAID Card and the Xserve RAID Card?*
Answer: Only Apple SATA drives and Promise 450GB SAS Drive modules sold through the Apple Store are supported for use with the Mac Pro RAID Card (Early 2009) and the Xserve RAID Card (Early 2009).
Apple 300GB SAS Drive modules are supported with the Mac Pro RAID Card (Late 2007) and Xserve RAID Card (Early 2007).
Drives must be either all Serial ATA (SATA) or all Serial Attached SCSI (SAS) drives. SSD drive modules are not recommended for the Apple RAID Card because these drives use their own on-disk cache and cannot take advantage of the protection provided by the battery-backed cache on the RAID card.
http://support.apple.com/kb/HT1346#faq8
http://www.apple.com/support/macpro/
Apple Knowledge Base: recent changes:
http://support.apple.com/kb/index?page=articles -
Raid Card and Multiple Hardrives.
does anyone have any idea if I can use the raid card to use a seperate hard drive to run windows and then use another drive for mac OSX? That way I don't have to worry about partitioning my hardrive. If there is any way to do so I would really like to know. Also any cheaper suggestions for a raid card?
Fact is you cannot use the APPLE RAID CARD and also run Windows on any of the internal SATA ports. Unless you want to play around with iPass or reroute the cables.
http://www.apple.com/support/macpro/
I consider the RAID card more hinderance, and not just in terms of Boot Camp.
http://www.apple.com/support/bootcamp/
Windows 7 is fine, more users probably than use Leopard, and runs well, no issues, and better than Vista even with SP2. -
K7D Master L & Promise FastTrak SX4000 boot hang
I am having major trouble getting a Promise FastTrak SX4000 RAID controller to work with a K7D Master-L (MSI-6501-030). I would appreciate any and all input, especially from those of you who have similar or identical hardware (same motherboard/chipset, same RAID controller or similar Promise card) and are able to get them working.
Brief description :
The SX4000 controller will hang at the IDE drive detection stage when installed on this board alone (plus an AGP video card) or alongside various combinations of PCI adapters, in various PCI slots available, and using various BIOS settings. The SX4000 appears to work fine in another Intel chipset system with the same AGP video cards. Both the motherboard and the SX4000 controller appear to have the latest BIOSes available.
Symptoms :
When the system is turned on with the SX4000 controller installed, it completes POST successfully, then loads the Promise FastTrak BIOS from the SX4000, and stalls after displaying "Scanning for IDE drives". Waiting for extended periods of time verifies the system is just 'stuck' here. It appears to be a 'hang' rather than a 'freeze', since the keyboard continues to operate and Ctrl-Alt-Del will still reboot the system at this point. The D-LED diagnostic LED bracket indicates (according to the included user manual), the system is at the "Initializing Hard Drive Controller" stage at this point.
The system continues to boot fine if the SX4000 controller is not installed.
The SX4000 controller functions fine on another system, a Dell OptiPlex GX400--a Pentium 4-based system built around the Intel i850 chipset. This OptiPlex GX400 has only a TNT RIVA 128 AGP video card installed, but has built-in audio and NIC. The SX4000 controller also works in this system using a GeForce2 MX TwinView AGP video card as well as a GeForce FX5600 AGP video card. It does not work on the K7D Master-L with either card, with the following exception. With only the TNT RIVA 128 AGP video card, it will in fact scan for IDE drives (indicated by ~10 - 15 dots/periods, ".", displayed after the "Scanning for IDE drives" message), but then will also hang as soon as the scan is complete without additional messages.
All of the above is true whether hard disks are connected to the SX4000 controller or not.
Disclaimer : I am not a newbie. I've built hundreds of systems over the past 10 years and know what I am talking about. :)
What I have tried so far, and what I've been able to determine :
I have gone through quite a bit of research about this. I've tried both Promise and MSI Web sites (both US and Taiwan), the Web at large through Google, as well as various newsgroups including alt.comp.periphs.mainboard.msi-microstar through Google, the MSI forums on their Web site, the AMDMB Forums, 2CPU forums, HardForum, AnandTech Forums, SysOpt forums, and Tom's Hardware Community. While there are many posts about the AMD 760MPX chipsets and various Promise RAID and non-RAID IDE controller cards, none describes my problem exactly. Hence my posting here.
o There isn't a problem with the DIMM I am using on the SX4000. It's a 256 MB PC133 DIMM, with 8 HT33S328256K (32Mx8) DRAM chips on it. I am certain it's not a problem because the card works as expected in the Dell OptiPlex GX400 with the same DIMM. I have also tried a 64 MB PC100 DIMM (Crucial) and there is no difference--the SX4000 controller hangs the K7D Master-L, but works with the OptiPlex GX400.
o Moving the card around to different PCI slots on the K7D Master-L doesn't make a difference, if only so to avoid a problem with a shared interrupt. I have tried the board in all 5 available PCI slots--the upper two 66MHz/64-bit PCI slots as well as the lower three 33MHz/32-bit PCI slots. I have looked at the IRQ assignment scheme for this board, and tried putting the SX4000 (alone or with other PCI cards--see configuration info at the end) in the first PCI slot, next to the AGP slot such that it doesn't share an IRQ with the video card. No luck. I have also tried the lowest PCI slot (#5), which should have a distinct IRQ ideally, based on the above scheme, but that also makes no difference.
o Disabling various components, including all on-board peripherals (audio, LAN, serial, parallel, and USB ports, legacy USB emulation, ACPI), disabling all caching/shadowing (video/system BIOS) makes no difference.
o The SX4000 controller came with the latest available BIOS according to the Promise Web site (http://www.promise.com/support/download/download2_eng.asp?productId=94&category=All&os=100), v1.02.0.5. Just for the hell of it, I copied the controller BIOS from the flash ROM to an image using Promise's own PFLASH.EXE utility and file-compared it with the latest BIOS on the Web site to ensure they are exactly the same.
o The K7D Master-L came with BIOS v1.6, which, according to MSI's US (search for the K7D Master L) or Taiwanese (lists a v1.82, but I am hesitant since it doesn't recommend or caution against using it on the -L model of the motherboard) Web sites is not available. These list either v1.3 or v1.5 (the latter for the K7D Master) as the latest available that I can verify for K7D Master-L.
o I tried downgrading the SX4000 controller BIOS to the other, earlier one available on the Promise Web site, to v1.01.0.15. No changes. The card still doesn't work in any slot on the K7D Master-L, and works fine in any slot on the OptiPlex GX400.
o There *are* people on these forums who have similar systems, some with the same motherboard and controller, others with the same motherboard and similar cards like the FastTrak SX6000 who apparently are able to make it work. I know this only because they have open threads on other issues and happen to provide their configuration info. For example:
--same mobo and controller card, apparently working as reported problems are other issues--
2CPU forum post #1
2CPU forum post #2
2CPU forum post #3
MSI forum post #1
newsgroup post #1
--same mobo, very similar controller card--this person first asked on MSI forums and then walked the AMDMB, Tom's Hardware forums, with no response except a supposed "will not work" from MSI; the last one is another person describing my exact problem I think--only one so far--but with an SX6000--
MSI forum post #2
AMDforums post #1
Tom's HW Community post #1
newsgroup post #2
--same chipset though different mobo--
2CPU forum post #4
2CPU forum post #5
2CPU forum post #6 (the K7D Master L has no "jumperless mode")
--people building similar/identical setups--
2CPU forum post #7
AMDforums post #2
AMDforums post #3
What I have not done :
o I have not tried downgrading the BIOS on the K7D Master-L to an earlier (pre-1.6) version. I don't know if this is wise, though, considering this appears to be a newer (with working USB 1.x) revision of the motherboard that might minimally need the BIOS currently on it.
o I have not tried another SX4000 controller card, which I do not have. However, the card working fine on the OptiPlex GX400 indicates to me clearly that there isn't a functional problem per se on the card itself.
o No components are overclocked.
What I suspect :
o The fact that the two GeForce-based cards behave slightly differently than the TNT RIVA 128 (see above about how the hang occurs slightly later with the latter card) indicates to me that the problem is some combination of the motherboard, RAID controller, and video card conflicting (conspiring?) together. I am looking for the plainest AGP video card I have around to further test this.
o There appears to be a resource conflict *or* a BIOS/handover problem going on. It's not likely an IRQ conflict/sharing issue, since on the OptiPlex GX400, the SX4000 happily shares an IRQ with the video card (verified through the BIOS). The resources the SX4000 uses when on the OptiPlex GX400, as seen through its own BIOS/array utility are:
Installed Memory Address FF1F8000 Size 256M
Controller IRQ9
ATA IO Address EC00
XOR and HDMA IO Address E800
Sequence Control IO Address E400
Flash and SRAM Memory Address FF200000
I do not know which of these are retained as is when in the K7D Master-L (the IRQ certainly isn't necessarily retained, but don't know about the rest). I also am not able to easily check for a conflict with these. I can verify that as Windows XP can see it (which does assign its own resources via ACPI, of course,) there are not system or motherboard resources overlapping with any of these.
Also note this older K7T issue that may be relevant
What I need help with :
If you have a K7D Master-L and an SX4000, SX6000, or other similar Promise controller, please let me know how your system is configured.
What other peripherals, particularly video card do you have?
Which slots are all the cards in, particularly the SX4000?
What BIOS version of the K7D Master-L are you using?
What BIOS version is the SX4000?
Many thanks in advance,
MacGyverHi, I believe of having your same problem..sorry, I do not speak well English,
this is my system:
Mainboard Microstar MSI K7D MasterL chipset AMD 761MPX
CPU dual AMD MP2400+
RAM 2x512 Corsair pc2100 ECC Reg.
Primary Master DVD Rom Toshiba SD-M1712
1° slot PCI(66Mhz) controller FASTRACK SX4000
3° slot PCI controller USB
AGP 3Dlabs VP970
3 HD Western Digital WD0800JB 80Gb with 8Mb buffer (new)
AUDIO ONBOARD AC97
LAN ONBOARD INTEL
IRQ 11
RAID 5
BIOS FASTRACK SX4000 1.02.0.5
RAM Dimm 256Mb (test OK)
this is my problem:
1) the HD in master or slave the HD do not come recognized from the bios of the fastrack..HD not found..control cables ide or current
2) cable select or removing jumper from the HD the these they come recognized, it allows to make the Array (tried raid 5, 0 and the 1) ago boot of the fastrack but at the moment of the boot from floppy or cd rom (as from bios of the mainboard) remains the underscore that flashes. The PC is not of an all out..con ctrl+alt+del reboot.
3) tried to use also only 2 of aforesaid the HD, invert channel, user also channel 4, same problems
4) it recognizes the HD in master if I mount cables IDE to the contrary.. with the blue connector on the HD..ma remains problem of the boot from floppy or cd
5) I have tried to install others 2 not new HD (samsung 6,4 Gb + seagate4,6 Gb)..il fastrack recognizes them also in master..it allows the Array in raid 0 or raid1 but it remains the problem of the boot from floppy or cd.
6) tried to move fastrack on other slot Pci (also on one of those to 33Mhz) identical problems
7) bios mainboard all ok..also why if I do not make array..part the boot from floppy or cdrom..also if then to the fine ones it says nonexistent disc to me (lacks the Array..)
8) changed to cables courrent..do not creed is that one the problem..Enermax 460W..e then if septum in a determined way jumper the recognized HD
9) modernized bios..le tests son been made it is with that old one that with last (the 1.02.0.5)
10) tried to use other cable 80 pin connecting a single HD WD in master..l' HD it is not recognized!
11) tried also to detach controller USB
12) moved reader DVD in primary slave and also in secondary (it is master that slave)
13) mounted same fastrack SX4000 on other pc..same problems
14) I have modernized bios to version 1,3 (last the available on the site US..on the taiwanese site is version 1,82 but I do not trust myself)
15) I do not know what other to make!
I have read on the situated one that not there were problems of incompatible with my Mainboard and was compatible with HD Western WD0800BB (80 GB and 2 Digital Mb of buffer) and with WD1200JB (120Gb and 8 Mb of buffer)..i 8 WD0800JB are 80Gb and have Mb of buffer..but creed are not a problem of HD..inasmuch as the problems remain also changing discs (seagate and samsung).
I absolutely have need of this PC for job
if it finds one solution..please it makes to know me! ;( thanks -
K7D Master multiplier over 12.5?
I'm just about to get my ordered K7D Master (hopefully L version - depends if they can get it) today or tomorrow and I'm wondering if the multiplier will go higher than 12.5 and if the limitation is due to hardware or bios. I'm assuming a bios update will fix it as user Mr. Heat (also saw him at http://www.2cpu.com) is using 2100 or 2200 MP's cpu's (13X multiplier) which work automatically but he wasn't able to change the multiplier even with unlocked MP cpu's.
So... my question is: Can the K7D Master run future MP 2400 or MP 2600 or XP 2400, etc cpu's without problems? ?(
On a side note, is software IDE raid easier to setup with XP than 2k? (will probably get XP with new mobo)
Mr. Heat Are you running XP or win2k for stability?Hi, I checked the K7D Master CPU Support Status web page and Athlon MP 2200+ is listed, but I can't install windows 2k or windows xp, stop errors and blue screens appear during the instalation process.
Is there any bios configuration specially for this processors?
When is going to be released the next version of bios?
I had to downgrade the bios to 1.3 version and only windows 2k works, but it detects the 2 processors as Athlon XP.
Thanks in advance ...
My configuration:
2 Athlon MP 2200+
1.5 gb PC2100 ECC
GeForce4 TI4400
Audigy 1394
C-net Lan card and modem
2 Maxtor 120 gb, 7200 rpms
CDRW Lite-on 52x -
Hello
I have a K7D Master with dual 2100+ CPUs, 1GB ram, BIOS v1.82. It started having problems so I sent it back to MSI for repair. When I got it back and started to put it together I noticed that I damaged one of the processors. I looked on pricewatch and saw that a new 2800+ is only $40 more then a 2100+. Can I run the board with a 2800+ in the primary socket and the other 2100+ in the secondary socket. If so, I assume that they will run no faster then the 2100+, however, I would upgrade the other 2100 shortly after. I have to pay tuition this month so I can't buy both 28's right now.
Also I tried to run the board with the one good processor in the primary socket but the computer won't boot. Does any one know why this would happen?
Thanks
ScottHi, I checked the K7D Master CPU Support Status web page and Athlon MP 2200+ is listed, but I can't install windows 2k or windows xp, stop errors and blue screens appear during the instalation process.
Is there any bios configuration specially for this processors?
When is going to be released the next version of bios?
I had to downgrade the bios to 1.3 version and only windows 2k works, but it detects the 2 processors as Athlon XP.
Thanks in advance ...
My configuration:
2 Athlon MP 2200+
1.5 gb PC2100 ECC
GeForce4 TI4400
Audigy 1394
C-net Lan card and modem
2 Maxtor 120 gb, 7200 rpms
CDRW Lite-on 52x -
MacPro RAID card - best drives?
Hey, anybody have any experience they'd like to share on a good set of drives to go with the Apple RAID card? I want to get 4 and I'm looking for maximum speed, but I can't break the bank, so no Raptors.
cheers,
-rWell, save your $$ and just DON'T! get the Apple RAID card, then you could afford some decent drives.
600GB 10K VRs $279 x 2
OWC SSD 100GB x 2
As for what drives, bare in mind -
If you read the Apple Support Mac Pro link to RAID card FAQ:
Question: *Which drives does Apple support for the Mac Pro RAID Card and the Xserve RAID Card?*
Answer: Only Apple SATA drives and Promise 450GB SAS Drive modules sold through the Apple Store are supported for use with the Mac Pro RAID Card (Early 2009) and the Xserve RAID Card (Early 2009). Apple 300GB SAS Drive modules are supported with the Mac Pro RAID Card (Late 2007) and Xserve RAID Card (Early 2007). Drives must be either all Serial ATA (SATA) or all Serial Attached SCSI (SAS) drives. SSD drive modules are not recommended for the Apple RAID Card because these drives use their own on-disk cache and cannot take advantage of the protection provided by the battery-backed cache on the RAID card.
http://support.apple.com/kb/HT1346#faq8
People do try and use retail SATA drives, with mixed results. I have never seen anyone mix SAS and SATA. -
User guide: MSI HQ USB BIOS Flash Tool
Guide based on USB tool v1.17c
HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation. It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation. (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
Symptoms that your USB key need a fix after booting from the USB key:
* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.
Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
Read the three notes that follow first before you move on:
1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
Contents of the Guide:
0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
3.2. Method 2: Processing a BIOS File Directly
3.3. Method 3: SureHands Live Update
3.4. Method 4: Geometry Change
4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
5.1. BIOS Settings to Check
5.2. Booting from USB Flash Drive
5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
6. FAQ: Common Problems & Solutions
7. Version History
0. Preconditions & System Requirements
The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash. The Tool is designed to work with MSI Retail Boards & Laptops only.
Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32). NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
1. Basic Description of Functionality
The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure. Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
* Excluding the Geometry Change method which will destroy all data on the USB storage device.
2. Installing/Starting the tool
Treat the forum's USB Flashing Tool like a regular application. Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing. Both, the installer version and the stand-alone version, do precisely the same job. Which of the two versions you use, is solely up to you and your preferences. The stand-alone version can be started directly by clicking on the executable file. The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
When you start the tool a DOS box should open up to provide you with status messages and prompts. Do not close that box unless you want to abort the preparation procedure!
Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
3. Choosing a Preparation Method
If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes. The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board). If you have downloaded such an archive, you should choose the first method from the option box.
You do not need to extract the files from the BIOS archive. The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive. You don't have to worry about anything else. All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
3.2. Method 2: Processing a BIOS File Directly
If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box. In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility. If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used. All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
3.3. Method 3: SureHands Live Update
"SureHands Live Update" is the third operation method you can choose from the option box. It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well. If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
Not all MSI Retail Boards are currently supported. With every update of the USB Flashing Tool more boards will be added. At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)
Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)
After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard. It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash. SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist. If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment. That message is part of a prediction feature that tries to determine future BIOS Releases. If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
3.4 Geometry Change
If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
Select your drive then let the tool do it's business.
Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.
4. Selecting the USB Flash Drive for preparation
When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it. This can happen in rare cases, but it is usually no problem.
The tool will check the selected drive and will provide you with status messages. If everything is okay, the message should look like this:
The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing. If the procedure was successful, you will get the following message in the DOS box:
5. BIOS-Settings, Booting & Flashing
If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
5.1. BIOS Settings to Check
Check USB-related Options in BIOS:
- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.
Not all of these options may be found in BIOS and the precise name may vary as well. Just make sure you checked for such options and that they are enabled (if present).
Another option you should check for is "Boot Sector Protection". If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
5.2. Booting from USB Flash Drive
To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu. From here, you can select you drive directly without having to adjust the boot sequence in BIOS. Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
5.3. Flashing Procedure/Running MemTest86+
As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
The flashing procedure will automatically be initiated from there. You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash. A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts. You do not need to enter any commands in DOS. All you have to do is acknowledge the information on the screen by pressing a key.
The flash itself will only take a couple of seconds (20-30s at the most). If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU. Read the >>Clear CMOS Guide<< for further information.
After clearing CMOS you have completed the BIOS-Flash.
Guide created by Jack The Newbie and the forum teamVersion updated to 1.18x:
* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0
* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.
Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
How i can roll back to my old BIOS version?
The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
How i can re-flash to my original BIOS version and from where can i get it?
A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.3
BIOS Date: 05/08/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.6
BIOS Date: 11/30/2009
Then choose your old BIOS version from the list:
The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:
It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:
The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:
"K9A2 CF wont flash to Bios v. 1.A !!!"
Quote from: Fingon on 25-October-09, 16:53:15
Hi MSI,
I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
My questions are:
1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
Thank you for any help!!
EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?
Thx for replies!
Quote from: Jack t.N. on 25-October-09, 17:16:16
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear. The fact that this message appears, shows, that there was actually something programmed to the chip.
If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
The BIOS Version should be shown on the POST Status Screen and there should be a date behind it. Please check the BIOS Date and write it down:
Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"? Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten). The hexadecimal notation is only used in the BIOS File Ending. Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
Here is a piece of well-meant advice for now and the future: MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version. Why? Because this tool is stupid and one of there most risky applications for performing a BIOS Flash. Please uninstall it completely.
Why do I call it stupid? I call it stupid because it does not differentiate between hexadecimal notation and decimal notation. It will show you that "v1.A0" is available. The it will flash it, if you allow it to do so. Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten). When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you. The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Quote from: Fingon on 25-October-09, 18:03:44
Thank you for the quick reply!!
Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
So thank you! Problem is solved.
Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
Quote from: Lostsoul777 on 14-August-09, 05:46:25
I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
Quote from: LinuxGuy on 29-December-09, 01:17:45
My computer does not have a floppy drive. How do I update the BIOS? (I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults. So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around). So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated. Either way, I would like to manually flash it in DOS. Is it safe to burn the setup files to CD and boot from CD into DOS?
That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
Quote
I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
What's going on?
Just run the MSIHQ USB Flash Tool and will show you all that you need to know
Examples[with real/accurate info]:
MSI Eclipse:
BIOS version 1.9:
BIOS version 1.10:[Tool now shows both BIOS versions alias]
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:30:55,34
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.9
BIOS Date: 09/22/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:37:25,66
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date: 10/27/2009
More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
More examples =>945GCM5-F V2 (FSB 1333) :
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:47:34,35
Mainboard: MS-7267
PCB Version: 4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date: 11/20/2008
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:52:46,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date: 06/02/2009
More examples =>780GT-E63 [N/A at MSI web yet] :
For MSI Notebooks such decoding isn't need, examples:
* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
- In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
- This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:00:53,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.DX2
Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:12:23,95
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.KV7
Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:18:34,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V3.9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.390
Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:22:24,04
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V8.1B9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.819
Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:25:38,51
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.4E0
Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:28:16,62
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.1B1
Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:31:57,78
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.IF5
Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:36:02,40
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.7O0
Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:39:11,84
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.C86
Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:49:38,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.GP6
Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:53:17,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.UH0
Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3] -
Using a Mac Pro w / Apple Internal Hardware RAID Card?
Anyone using a Mac Pro with a Apple Hardware RAID Card 2010?
( I have a 12 Core )
Is it worth the $600-700 ?
How much faster than the software RAID 0?
I see Hamm's RAID tips chart .. but it doesn't include such options .. plus it is based on a PC system.
Any tips would be great ..
I find many areas where the application is slow / unresponsive .. and I'm not sure where the bottleneck is ... Maybe the hardware RAID will solve it?
I'm really am impressed with CS5 .. it would be even better with some adjustments .. but I am absolutely disappointed with sluggish performance on my top-of-the-line Mac Pro 12 Core.
This is not what I expected for a $8,000 machine.
Some users says that the port of CS5 for the Mac has taken a back seat to the Windows version at Adobe.
I can't imagine that Adobe would not put 100% effort into Mac products.
Go Team!!!I have a 2009 Mac Pro 3.33GHz Quad core w/ Apple RAID card, 16GB RAM from OWC, and Apple's Radeon HD 5870 GPU.
I have RAID 0 set across 3x1TB drives internally, and the standard 640GB drive for OSX and all program files. I set all video assets, renders, previews and such on the 3TB RAID.
This seems to work wonderfully. I built this system specifically to edit a feature film shot on P2 DVCProHD, and I've been impressed with how it handles it. This was all built prior to CS5, which took me by surprise. Had I known nVidia would become such a problem for Apple, I would have built a PC, but that's another story.
I just started a new project in CS5 on the same system, this time using H.264 video from my Nikon D7000, and so far, it seems to play just as nicely, despite not having hardware acceleration via CUDA technology. Yellow bars on top, even. I haven't had any problems with clips taking a long time to populate on the timeline or any of that, so perhaps the RAID card helps there.
All this aside, I've already decided to upgrade my RAID for another reason. Right now, my backup is performed via an eSATA-connected external drive through a PCI eSATA card. After every edit session, I dump everything on the RAID onto the external drive, and it goes much faster than the old FW800 transfer used to. I'm about to replace my Apple RAID card with an Areca card and set up a 4-bay RAID 3 via an SAS connection. This will allow for excellent data throughput while offering more security than my current RAID 0 / manual backup system, and free up the internal drives for backups, exports and render files.
I believe in hardware RAID, but I'm not as knowledgeable as Harm and others are about it. I had my Mac built to order with the Apple RAID card, so I have no experience using Premiere with a software RAID. Due to my smooth experience using it, I think it was worth it, but plenty of people say the Apple RAID card is rubbish, and to go with Areca or Atto cards. I didn't know about them until after I built my system, and even though it will cost a couple thousand to upgrade my RAID from this point, I expect to have an even better system than I already have.
I hope this helps, and feel free to ask any questions I didn't address. -
Hard-Power off caused BIOS to stop working (NOT because of BIOS Flash)
I was trying to boot up a live CD on my Toshiba Satellite P305D-S8900. The F12 key to pull up the boot menu didn't work, and it started to boot to Windows. I let it get past the "Starting Windows" Orab (running Windows 7), and hard-powered it off when it got to "Please Wait..." right before the login screen. After that, when ever I turn it on, the BIOS isn't loading. The Only LED lights going on are the Power button one, and the three that indicates it plugged in, the power is on, and the Battery indicator. The media buttons and the one above the trackpad doesn't work. The track pad one lights up when I hit the power button to turn it off. The fans are working (indicating the power management is working), the CD Drive is reading to see if there is a disc in there, and the screen remains black. There is no hard drive activity whatsoever. And the strangest thing of all...no beep code!!
I have so far tried taking out my MAIN battery for 24 hours (NOT the CMOS battery) and a Pheniox Crisis Disk with these combinations: "Win+B", "Fn+B", and "Fn+F". There is no beep codes when I do it or even any beeping to indicate the BIOS is getting flashed for that matter. Are there any other key combinations I could try? And yes, I from the start took out the battery, plugged in the drive, and pressed and held the key combinations while plugging in the AC, turning it on, and waiting about 30 seconds to release the key combinations. Like I said, this was not during any BIOS flashing, and what went wrong really stumps me.
Is there any other solution I could try? As of right now, sending into repair is not an option. Can anyone help me fix this? Thanks in advanced!I was trying to boot up a live CD on my Toshiba Satellite P305D-S8900. The F12 key to pull up the boot menu didn't work, and it started to boot to Windows. I let it get past the "Starting Windows" Orab (running Windows 7), and hard-powered it off when it got to "Please Wait..." right before the login screen. After that, when ever I turn it on, the BIOS isn't loading. The Only LED lights going on are the Power button one, and the three that indicates it plugged in, the power is on, and the Battery indicator. The media buttons and the one above the trackpad doesn't work. The track pad one lights up when I hit the power button to turn it off. The fans are working (indicating the power management is working), the CD Drive is reading to see if there is a disc in there, and the screen remains black. There is no hard drive activity whatsoever. And the strangest thing of all...no beep code!!
I have so far tried taking out my MAIN battery for 24 hours (NOT the CMOS battery) and a Pheniox Crisis Disk with these combinations: "Win+B", "Fn+B", and "Fn+F". There is no beep codes when I do it or even any beeping to indicate the BIOS is getting flashed for that matter. Are there any other key combinations I could try? And yes, I from the start took out the battery, plugged in the drive, and pressed and held the key combinations while plugging in the AC, turning it on, and waiting about 30 seconds to release the key combinations. Like I said, this was not during any BIOS flashing, and what went wrong really stumps me.
Is there any other solution I could try? As of right now, sending into repair is not an option. Can anyone help me fix this? Thanks in advanced!
Maybe you are looking for
-
6-full-size page brochure - want it to be larger in PDF view
I hope I can explain this correctly. I created a 6-page (8.5 x 11) brochure/report in InDesign using a page size of 25.5 x 11. When I create the PDF, it makes it into two 3-page spreads that are very tiny. When the client goes to print it, the 3 page
-
Can anyone help me figure out why the setting in System Preferences and CDs & DVDs will always revert to Ignore when I set the drop-down menu to When you insert a music CD, to Open ITunes? I've tried iTunes Help and it told me exactly what I have bee
-
Crystal Report for Enterprise Bex Text Variables
Hi We are on Crystal Reports for Enterprise XI 4.0, Version 14.02.2. We have a text variable for cost center in our column heading that displays "Cost Center XXXX Budget" where XXXX is populated by the text variable. When this column element displays
-
Hello, is it possible to sign PDF on Pocket PC with Windows Mobile 5 and Reader? I know i need Reader Extension, but it looks like Signature Field on Pocket PC are simply missing (i reader extended the form). Does anyone done something similar ? Łuka
-
New Macbook Pro - less than a week old
Hi all, I just recently got a Macbook Pro, had it for 3 weeks before it got stolen and got it replaced through insurance. Since getting this new one, I have noticed its considerably slow to start compared my previous one. Anyone can suggest why? befo