K7T266 Pro2-RU Not Booting

Hello,
I recently got a MSI K7T266 Pro2-RU motherboard and an AMD XP2000+ processor. When I turn it on, I get the 4 red lights and no boot. I flashed the bios with the newest version, and it still won't work. I read in the bios history that 2000+ is supported, so I have no idea what's going on. My old 1ghz tbird works fine with the motherboard.
I run Win 2000
Radeon 9800 pro (actually just installed it along with the processor)
PC2100 DDR 256 (x2)
3 HD's (2 40gb are raided, other is 20gb)
Power Supply I believe is 300w
Any help is appreciated. Thanks.

Well the chip I got was retail. Does that mean its Tbred?
So that means soldering then eh?
Say I puss out on doing it, or mess up doing it, which board should I get instead?
edit: Also, why does the bios page say that the motherboard supports a 2000+ when it doesn't? (without the mod)

Similar Messages

K7t266 pro2 won't boot with USB 2.0 card

Hello, I installed a orangemicro usb 2.0 card for my external cdrom. whenever i cut it on and start to boot, my computer reboots. also happens when iam in windows xp pro, and server 2003. everything works okay while using the usb 1.1 anyon have any ideas what i could do.
Also iam running bios ver 3.7 upgraded lastnight (no fix)
AMD Athlon 1.3MHz
768MB DDR PNY
Maxtor 20 Gig HD
Radeon 7000
soundblaster 5.1
Nic 10/100 netgear
could sure use the help...
Thanks

Hi,
Have you tried these:
1. disable onboard USB?
2. uninstall USB2.0 drivers in WinXP
3. use only the USB card without any other PCI card (just for testing)

K7T266 Pro2 RU: Boot problem, wrong CMOS setting

Hi All,
I have had the Pro2 RU MB for a year now with very few problems. Over Christmas I was cleaning up my computer and was going to do a format :C and reload windows. When I went to start the computer after cleaning it up (remove all cards, clean up dust) I got 4 red leds on d-led. Tried everything (different memory, reset bios, unplug everything except video, ect) always 4 reds. Bought a duron 1.3 GHz put it in started the computer it start to post, went through fastrack raid screen and then I got "CMOS settings wrong" "press F1 to setup", "F2 load defaults" ...... screen I go F1 into setup make ajustments and everytime I save and I get 4 red leds on reboot. If I go F2 load defaults and continue it will try and boot, my hard drives are in a raid 0 array and it will check floppy, ide 0, cdrom by default so it can't boot. If I reboot at this point it will go 4 red leds. I can't flash the bios which is ver 3.2 because the bios protection is enabled and I can't change any settings. I could use some help this one has my stumped.
I have tried 3 different power supplies, and that is not the problem.
K7T266 Pro2 RU
Duron 1.3GHZ, retail box HSF
256MB Cruical pc2100 ram
300w AMD approved PSU
Geforce2 GTS 32MB
2 60GB Quantum HD in raid 0 array
Win 2k pro
Cheers Rugger

I have reset the cmos with pc unplugged...yes.
I have read the FAQ at this site, I have used the search feature at this forum I have googled my problem searched a few other sites and I am stuck. I have been building computers and troubleshooting problems for 3 years now. If it was a new board I would RMA it at my wholesaler.
It seems like there is a problem with the cmos chip because it will not accept any changes to the settings. As soon as you save the changes in the cmos the computer reboots and I get 4 red leds in d-led.
Cheers Rugger

MSI K7T266 Pro2 (MS-6380 v2.0) no boot

Since yesterday I have the following problem. When I restarted my pc it hung on the status (visible via the lights on the motherboard) on the 'boot attempt'. It recognizes all my drives (1x HD, 2xCDROM, 1xfloppy) and the cdrom and the floppy have a bootdisk/cd inserted. So, after the recognition of the devices it should try to boot the devices in the order specified (which I have tried in all combinations). But it just doesn't. You can hear that neither the cdroms nor the floppydrive is being used. The harddrive is empty, so it can't boot from there. But I know that the cdrom and floppy work because my motherboard does recognize them.
And yes, my pc has worked without problems for almost 2 years and I did not remove or add any devices.
I have a MSI K7T266 Pro2 (MS-6380 v2.0)
Can anyone please help me?!?!?

Hello.
2 years running fine and all of a sudden it is not booting?
Maybe after all this time something has finally gone wrong.
The best way to find out what is causing the hang would be to remove all the devices,
Remove hard drive, both cd drives and floppy drives.
Then connect 1 at a time and try to boot from it.
Test the floppy drive in your PC, does it boot from the boot disk?
if it does then put the hard drive back, IDE 1 master.
boot order floppy, hard drive
see if it still boots from the floppy drive
if yes then put 1 cd drive on IDE2 master, see if it boots from floppy.
boot order floppy, CD drive ,hard drive
if yes then put a bootable cd in the cd drive and see if it boot s from the CD drive.
You are using bootable cd's and disks?

Memory module not recognized on K7T266 Pro2

Hello.
I have a computer with only 256 Mb of RAM and I wanted to add 256 Mb but my second memory module of 256 Mo is not recognized whereas it functions very wel.
Here are details :
- Mother board : MSI K7T266 Pro2 (ms-6380 v2.0) with 3 memory slots
- BIOS : Award Modular W6380F1 V3.0 071902
- Memory module of origin : Samsung 256 Mo PC2100 (2 Sides)
- New memory module : Corsair Value 256 Mo PC3200 (1 Side)
Configs Tested :
- Samsung only : OK
- Corsair only : OK
- Samsung in Slot 1 and Corsair in Slot 2 or 3 : the computer starts but with only 256 Mb of RAM (in this config, Everest Ultimate Edition finds both memory modules but also only 256 Mb of RAM)
- Corsair in Slot 1 and Samsung in Slot 2 or 3 : the computer starts with a blank screen and several beeps.
Can somebody help me so that my second memory module is recognized correctly ? I specify that I did not modify the BIOS.
I thank you by advance.

I'm no memory expert, but from being around here I've learned that there is more to a stick of RAM than the MHz speed. If timings etc were perfectly the same for the 3200 and the 2100, the system (the Northbridge) could simply set down memory speed to the slowest of the sticks.
However, I also know that many have been helped by entering BIOS, Advanced Chipset..., and go to the subtitle Memory timings controlled by..., and change from By SPD to By User. Then manually set down to 133 (266 effectively). This is if you absolutely want these two sticks.

K7T266 Pro2 mixing memory ?!?

Hi all,
I am having a problem with mixing memory. The tech. at the computer shop say that a PC2100 and a PC2700 should work whitout problem, so I by one 512MB PC2700 !!!
Here, on my mobo, the memory check pass at boot, but WindowsXP crash when it access the PC2700 memory...
In bios, I set CAS lentacy at 2.5 and force the memory clock to 133MHz...
Note that the PC2700 work fine, alone...
You have idea ? Is PC2100 and PC2700 can be mixted ?
thanks,

Also, I can tell you that this mobo, K7T266 Pro2, is very picky about memory sticks.
Especially when mixing brands.

K7T266 PRO2 (MS6380 Ver 3.0) FDD Controler Problems

I just purchased a new boxed OEM MSI K7T266 PRO2 (MS6380 - Ver 3.0) motherboard from JUST DEALS on E-bay which seems to have very sparce (or none) documentation for download on this site. This is a non-raid board which has the AGP Pro video card socket (with the white lock and release lever at the end of the AGP female connector). The board can also be identified with the following rather unique component/connector layout at the bottom end of the board:
1. In place of where RAID connectors attach to most of these model boards, this board has three aux USB connectors above the connector where the case front panel connectors usually plug in.
2. There are 3 CDROM audio connectors at the lower left below the last PCI slot.
3. To the left of the case front panel connector, there are two rows of connectors and jumpers which appear to be for use with a case which has front panel audio connectors. I believe the jumpers are for the purpose of selecting which audio output to use (front or the standard rear sound output jacks.
4. The area between the last PCI slot and the USB and front panel audio connectors described above, the motherboard is rather blank with no components or even places where optional components have not been installed.
5. This motherboard has a Phoenix bios whereas most other K7T motherboards made by MSI seem to be AMI bios.
6. Finally, when doing a search for MS6380 Ver3.0 on Google, all the hits seem to be in Russian, German or French. I suspect that this MB may have been manufactured for the European market. BIOS display is in English, however.
PROBLEM
I have installed an AMD Athlon TBird 1.2 ghz cpu with 40mb WD hard drive which already had Windows Me and lots of other SW installed. The system boots just fine from the hard drive and all works well except for the Floppy drive. When I try to access the FDD with a know good disk installed with valid data, it comes on and spins up, the front light blinks and after about 30 seconds of continuous running, a message comes up "floppy disk not formated, format now: (Y/N)" If I try to format the disk, it will not format and the system will ask to check to see if a disk is installed. Changing floppy disks does not help, whether this is a disk which has verified data installed or just a formated blank disk. I have tried two different FDD cables and 3 different Floppy drives and always get the same result. I have checked for bent or broken pins in the connectors and found they are all good. The FDD is a 1.44 MB and is connected to the end of the two-drive cable. No other FDD is installed. When I go into the BIOS setup, I verify that Drive A is installed as a 1.44BM 3.5" Floppy and None is selected for Drive B.
I am currently at a loss to know how to proceed here. I am wondering if this could be a BIOS problem but I am not sure if I can find BIOS update on the MSI Web site when they do not even list a MS6380 Ver 3.0 motherboard at all.
I am considering installing a PCI FDD controller card but not sure that these are even manufactured.
Please help.

To Toenne:
Thanks for the reply. This has to be a BIOS problem since the FDD has to be accessed by the BIOS before any software or installed chipset drivers on the HD are ever used. With my problem, I cannot even boot the system from the FDD.
I tried resetting CMOS and that did not help. I wonder if there is some kind of multi-mode floppy disk drive which this BIOS expects to see other that you standard old fashion IBM 3.5" 1.44gb drive. The solution is likely to reflash the BIOS except with this odd MB serial number, I am not sure if I can find the latest BIOS software for this Phoenix chip.
Does anyone know if there are any PCI FDD controller cards on the market where I could disable the on-board controller and use a plug-in card?
Thanks

K7T266 Pro2 RU, Raid-0 & Linux

When I try to install either Red Hat 8.0 or Mandrake 9.0 on my K7T266 Pro2 RU, which has 2 x 40GB drives configured as RAID-0 (ie 1 x 80GB), both versions of Linux see the two physical drives and not the one logical stripe array. Why? It almost seems that the Linux drivers for the Promise 20265R are treating the raid channels and normal IDE channels. I want to install Linux onto the RAID-0 stripe!
I have searched for guides/tutorials on installing Linux on RAID, but all the ones I found only talked about RAID-1 (Mirroring).
Windows 2000/XP only sees the one logical drive.
Any help would be appreciated!
Chris.

The installer is wrecking the /etc/raidtab file when trying to detect existing raid arrays.
Solution: Format a floppy disk with a DOS filesystem (in Linux, you can use the command "mkdosfs /dev/fd0"). Copy
use detect_devices;
package detect_devices;
log::l("PATCHING");
*raidAutoStartRaidtab = sub {
my (@parts) = @_;
log::l("patched raidAutoStartRaidtab");
$::isInstall or return;
require raid;
#- faking a raidtab, it seems to be working )
#- (choosing any inactive md)
raid::inactivate_all();
foreach (@parts) {
   my ($nb) = grep { !raid::is_active("md$_") } 0..7;
   output("/tmp/raidtab", "raiddev /dev/md$nb\n device " . devices::make($_->{device}) . "\n");
   run_program::run('raidstart', '-c', "/tmp/raidtab", devices::make("md$nb"));
unlink "/tmp/raidtab";
use raid;
package raid;
*prepare_prefixed = sub {
my ($raids, $prefix) = @_;
log::l("patched prepare_prefixed");
$raids or return;
&write($raids, "/etc/raidtab") if ! -e "/etc/raidtab";
eval { cp_af("/etc/raidtab", "$prefix/etc/raidtab") };
foreach (grep { $_ } @$raids) {
   devices::make("$prefix/dev/$_->{device}") foreach @{$_->{disks}};
to the floppy disk. Remove the floppy and reboot using the Mandrake Linux 9.0 CD1 to do a CD-ROM installation. During boot, press F1 at the splash screen, then place your floppy disk that contains patch.pl in the floppy drive. At the prompt, type "patch", then follow the installation as usual.
Hope that helps

K7T266 Pro2 & new hard disk

Hi
I have just upgraded my K7T266 Pro2 with a 2400+ chip (with modification & bios) and upgraded RAM to 1 GB. All works OK.
Now I am trying to put in a new 250 GB Western Digital hard disk and installing Windows XP Pro from scratch and I am running into problems. The hard disk is on the main IDE connectors.
The BIOS recognises the hard disk. When installing Windows XP, it seems to only detect a 131 GB disk!. Windows installs but when the computer reboots as part of the installation, the hard disk will not boot, even when forced as the fist boot device.
If I boot from the Windows CD and go through the install again same problem.
Any suggestions?
Chris
Adelaide
Australia

harrisc:
You mentioned that you updated the BIOS - the last release (1.9) had a note that it "Support Maxtor 160GB HDD (4G160J8)" so I would expect the board to support the 250 Gb WD drive, as well.
The problem probably is in Windows - XP versions before SP1 did not support 48 bit LBA (Logical Block Addressing) which is needed for drives larger than 131 Gb to be recognized.
Here is a link to the Microsoft Knowledge Base article with a 'fix':
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303013
If your installation disk is a pre SP1 then that's the problem; if it's SP1 or SP2 then there IS a BIOS limit (contrary to what I assumed above). Your best bet then is to partition the drive with a ~50 Gb primary and 200 Gb extended partition and live with two logical drives.
Good luck,
ss

Bad Motherboard? (K7T266 Pro2)

I've got a K7T266 Pro2 motherboard w/an AMD Athlon XP 1700+. How do I know if the board went bad? My machine will not turn on and I've changed out the power supply. Any solutions? I do have the BIOS set to input a password to boot, but my keyboards are fine. Any help is MUCH APPRECIATED.

well my board is almost a year old and mem slot 2 the one in the middle just went bad
now I'm looking for a cheap mobo to use for I can send this back two MSI
it's real f****** bullshit that MSI can't send a replacement motherboard out
almost all hardware manufacturer do a hot swap another words you give them a credit number they send you a replacement when you get it you send them the damaged board
but not MSI
My next Mobo well not be MSI I'm going back to Iwill or ASUS
(Watch your language, Bas.)

Using K7T266 Pro2, Cannot find BIOS Protection function.

I am using K7T266 Pro2 (MS-6380 v2.0) with BIOS update 3.70. I was reading the manual and suddenly I found a interesting function “BIOS Protection”, quote from manual:
Quote
This function protects the BIOS from accidental corruption by unauthorized users or computer viruses. When enabled, the BIOS’ data cannot be changed when attempting to update the BIOS with a Flash utility. To successfully update the BIOS, you’ll need to disable this Flash BIOS
This is a really useful function but the problem is that I cannot find it! According to the manual it should be in the Advanced Chipset Features section, below the “PCI Delay Transaction” function. But when I go to my BIOS setup there is nothing below the “PCI Delay Transaction” function. And so I ask my self “where is the BIOS Protection function?”, I checked threw all the other sections but I could not find it… please help me, where is this function? Doesn't it include in the new BIOS update 3.70? Is anyone experiencing the same thing?

Quote
Originally posted by elpcmaster
Downgrade to 3.3. It is the best and supports Linux and Norton Ghost, unlike 3.7.
I'm assuming that by this you mean it does not support a network boot?
The reason why I say this is that I recently restored my K7T266 PRO2-RU BIOS Rev. 3.7 using Symantec Ghost Corp. Edition (MultiCast Server). The Ghost image was stored on a remote machine, all that was needed was a floppy disk which was simple enough to configure using the wizard. I had no problems - BUT that doesn't mean the thing (my motherboard) isn't flakey as hell though.

K7T266 Pro2 incompatibilty problem with Nvidia GeForce4 Ti4200

I just bought the GeForce4 Ti 4200 from Siluro and installed it on my MSI K7T266 Pro2 MB and have since then experienced some problems when booting XP pro.
Everything seems to work fine untill the very last application loads in XP after boot. Then the screen turn white, the mouse cursor becomes a black and white stripped square and the system reboots automatically. Generally after second boot, evreything seems to work fine but I get an XP error message stating that "the Nvidia Geforce4 TI 4200 drivers may be the origin of the critical problem encountered".
I have all lastest drivers for both the MB (Bios 3.7 + lastest VIA drivers) and the Nvidia GeForce (Detonator 41.09) and yet experience the problem... Help!!
MB K7T266 Pro2 MS-6380 Ver. 2 (Bios 3.7)
Siluro Geforce4 Ti 4200 (Detonator 41.09
XP Pro

I have an AMD Athlon 1700+
768 MRam DDR 266
Sound card is Sound Blaster Audigy Platinum EX
I have an ADSL connection with Alcatel Modem
I hope this is what you required... If not, let me know exactly what it is as I do not really know what PSU and the rest stands for (or when I can get that information on my PC!)
Thanks again for your help!

Random Clicks and Beeps K7T266 Pro2

For a long while now I have had a small issue with my K7T266 Pro2 motherboard. Every know and than for whatever reason (never have been able to figure it out) my motherboad will click and than I will get a beep from my PC's internal speaker.
I have had this problem soo long I couldn't even tell you when it started or what the situation was when it first started to happen. I have finally decided to see anyone on these forums can help me out.
Here are my system specs.
400 watt power supply
AMD 1700+ xp
Kingston 266mhz DDR ram 2 sticks of 256 megs
Geforce 4 ti 4200 (agp slot of course)
Sound Blaster Audigy sound card
Network card
Ati Tv-wonder (pci) card (it is just a tv tuner not another video card)
DVD rom (ide2 master)
CDRW (ide2 slave)
40gig IBM 7200rpm hard drive (ide1 master)
40gig Seagate 7200rpm hard drive (ide1 slave)
A: drive as well.
Now the above is what my current set up is for the computer. The main components Cpu and Memory have not changed, the sound card and the DVD rom and CDRW have not changed either since I started using the current Motherboard. Everything else has changed a bit over the last couple of years but I still get the same click and beep every now and than no matter what I have changed out. Last year I even got a new box for the comp with a 400 watt power supply and still it happens.
Thanks in advance for any help.

Try remove one of the ram and see if it boot. If it doesn't boot, replace the other with the one that was removed.
If it boot with one ram, then one of the ram is bad.
If both ram will boot by itself, then try lower the memory setting in the bios.

K7T266 Pro2 RU repaired but...

Hello.
Long time no see, I'm back now ^^
Since the glorious times of my first Socket A system, much water have flowed on rivers so to say that many things happened, to me and in the world.
Well, ok, to make long story short here's the thing.
Some time ago (iirc some years) I were trying some spare hardware I have and when I was trying my old K7T266 Pro2 RU motherboard, after some tests, I did a mistake: I didn't installed properly a stick of ram, being partially inserted on one side and not fixed properly in its slot, so, forgetting and/or not noticing it, I switched on the motherboard and the poor board "poofed" out dead. The component that burned was nearby the ram slots, named D7 on the board and it was an SS12, a schottky diode: I thought so that replacing it would have sufficed to bring the board back to life, so I went to a tech assistance shop and they gave me an SS14 diode, claiming that it have the same characteristics of the SS12 being it just stronger than the earlier and that it can stand some more voltage, so I bought it for a few euro.
After that I left all the mess apart since I lost interest to it, until now that I decided to try to fix the motherboard with the new component and see it I were right about it, but here came the first problem: when I were trying to unsolder the old burnt diode, it was really difficult, first off because it was too near the ram slots (so I were fearing to melt the plastics of the retention system), second off because the pin on the opposite side of the ram slots wasn't wanting to let go the track it was soldered! I struggled much to make it let go and after I succeeded, luckily, the track under was lifted from the board and I found it even cut!
After swearing all of my calendar (don't mind about this, it's something we do much in italy, not always tho :P), I then tried to solder the new diode: it wasn't so difficult, and luckily i managed to sold back the cut track rejoining it and, because the whole thing wasn't so fix, I put even a drop of Superattak glue (cyanoacrylate): the result was very good, even tho couldn't be as if it nothing happened, but acceptable in general.
I tried then to reinstall it on one of my old case desktop ATX lying around, throwed my old Athlon XP 1800+ Palomino and a stick of 256 MB DDR266 from an old Intel celeron 1.7GHz Willamette rig I got recently, and powered it up again: first attempt didn't do anything, after some cable checking (I don't remember now but maybe I reversed the reset and power on switches plugs ^^) it finally run... and *drum roll* it even did the POST! I was happy, then, and was thinking that everything were going the good way. But Murphy is always hiding somewhere, so my happiness wasn't lasting long.
Ok, then, I decided to try to test it again to see if the hardware is still going, so I tried to install windows XP on a spare maxtor 80gib I had lying around, but with no much luck: firsts attempts hanged many times always on the same step (still on the early blue text-only screens), so I decided to try to run a memtest first, to check it before everything, and here comes the new main issue.
I've installed memtest86+ v4.20 on an old 256 mb usb pendrive, successfully, because I needed to test the ram on some other computers, so I had the thing already ready for the task: I inserted it on one of the onboard usb plug (the v1.1 ones: naturally on the usb 2.0 it's not even detected) and tried to boot the board from it. Failing.
I then tried it again on other computers: first my notebook, then some other rigs and all of them run the test correctly. To be sure I reinstalled the memtest on the pendrive, to no avail.
I've tried to change the ram stick, I've plugged a 512 MB DDR400 one (not the one of the incident, but surely a working one, since I tried it successfully on other rigs), and change the slot too, still to no avail.
The pendrive "boots", but it hangs prompting me:
Quote
SYSLINUX 3.86 2010-04-01 CBIOS Copyright (C) 1994-2010 H. Peter Anvin et al
No DEFAULT or UI configuration directive found!
Boot:
What should I do?
Is it because of the USB 1.1?
Or maybe a BIOS issue?
Or is it really my motherboard that's still TFU? I really hope not, I want to make it work again :(
Anyway, of anybody of you that still have this glorious motherboard, can you please tell me if you can run memtest86+ from one of the ONBOARD USB (1.1) plugs?
I take it from here, btw: http://www.memtest.org/ (http://www.memtest.org/download/4.20/memtest86+-4.20.usb.installer.zip to be correct).
Please answer me, thank you in advance!!
Edit: I forgot to say that I did the c37 removal mod for making the board compatible with 0.13 µ cpus, successfully, natuarlly :P

Quote from: Bas on 06-February-12, 19:38:58
Looks like the harddisk is broken.
As it complains about the partitions just like XP does.
No, I tried to boot the memtest from usb disconnecting everything else, so no hdd and no cd/dvd. I also tried to disable every integrated periferal and device: fdc, serials and parallel, midi, game, ide, raid, audio, modem and usb (1.1 naturally).
Btw when I said that it complains about the partitions? :o
Quote from: eagle3 on 06-February-12, 20:58:32
Try memtest on a cd and boot from that; or use a linux live cd. Or the marvellous Ultimate Boot cd. http://www.ultimatebootcd.com/
Also that board was built around the time of the bad cap debacle..
I think I would have binned it..
I followed your suggestion (but I thought it by myself too) and tried with the cd version of memtest86+, burning the iso onto a brand new cd (sigh, so much space wasted :p), and tried it: it finally worked, and I found that the 256 Mib ddr266 stick isn't compatible with the board, since the test didn't even started, another stick of 512 Mib ddr333 got errors (even 1 is too much to me, but it didn't have only 1 error), and finally the 512 Mib ddr400 tested fine for about 2 hours! That's a relieve ^^
Unluckily even using the good working ram, it still don't want to boot memtest86+ from the usb pendrive.
I still ask to anyone with my same board if they can do the same test, just to be sure that's just the board that can't boot properly from usb, or maybe a little incompatibility with my old pendrive.
Thanks for now.

K7T266 Pro2-RU BIOS flashed, now dead :panic:

Hi
I have a new AthlonXP 2400+ and tried to run it on the K7T266 Pro2-RU board with no success. I thought it was a BIOS problem because the XP2400+ is listed as supported and flashed the BIOS with my old XP1700+. I took this package to flash the BIOS: http://download.msi.com.tw/support/bos_exe/6593v16.exe
Now my PC is dead!
I saved the old BIOS to a floppy - is there any chance to reanimate the board again?
P.S.: I recognized that I used a KT266 Pro2-R (not K7T266-RU) BIOS to flash.
P.P.S.: A local shop offers flashing of the BIOS chips. How can the chip be removed from (and inserted again to) the mainboard?

http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=29
dont appear you got the right bios
http://www.msi.com.tw/html/support/bios/note/boot.htm
if its still reading the floppy drive
http://www.badflash.com if its not

K7T266 Pro2-RU Not Booting

Similar Messages

Maybe you are looking for