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.

Similar Messages

K7T266 Pro2-RU raid crash

I have had this system up for about 8 months. One day when converting mp3 to wav the system crashed. When rebooting I would get a black screen or it would hang during the boot process. I was using XP and W2K server - never had an issue until this crash, and now problems when booting with either.
I attempted to do update the raid drive (got the grand message re: stop what the heck your doing or face certian death or Continue and prepair to die - when updating the driver in xp). Nothing worked. So I fdisked the drive (20gb ibm) drive that was my c: and reinstalled W2k Server...still seeing the same issue.
Raid array says it is functional, but that is about it. System hangs durning boot, and if ide 3 and or 4 is unplugged, I can then boot up and work off of the 20gb drive.
Anyone, anyone?
System:
2000 server on a 20gb ibm
1.5gb of Ram
2- 40gb ibm darkstar hard drives in array
Promise raid lite 1.13
K7T266 Pro2-RU
tried new cables,
changing around the jumper,
latest raid drivers from our friends at msi,
but today I am thinking hammer may do the trick...

Still no luck, today I went out and downloaded
File Scavenger 2.0.
It could see the array, and for 40 dollars I can buy a license to repair the drives...or so they say.
Does MSI have any raid repair utilities, or does anyone know of any good raid repair programs

K7t266 pro2 ru burned diode

Hi everyone. This is a sad day to me :(
I accidentally broke my MicroStar motherboard, burning the diode near the ram slots, maybe the one that were powering them. This was because I were inattentive and I didn't saw that the ddr dimm was not completely installed in the slot ><
Well, apart of buying an used k7t266 pro2 (*not* ru, still an ms6380 ver 2.0) on ebay and cannibalize the diode from there, I want to ask to MSI technicians if I can purchase a new diode and substitute it, the diode is parallelepiped shaped and reports this letters and numbers on it: SS12 (SS in the upper side, near the white line, towards the ram slots and 12 in the opposite side). The mark on the motherboard is D7. Near there's a printed table about SW1 for switch the CPU (base) frequency (100 or 133 MHz).
Thanks in advance, but please, MSI techies, answer me ^^

Thank you for the quick answer, Henry.
Btw, do you think that the damage would be limited to the Shottky diode only?
This kind of accident (dammit, it was for the same reason, still the ram not well placed ><) happened to another Socket A motherboard that I have, an Epox 8rda6+ pro, it burned a mosfet-like (and on the board the 3 pins are marked G, D and S, that iirc is Gate, Drain and Source) component called D408: I took it from another Epox motherboard and soldered in the place of the burned one and now the board is running smooth as if it's new (luckily), but I guess I was lucky. (BTW I want to replace this component to the motherboard that I took it from to repair the other, do you think I can find it easily?)
Thanks again ^^

K7t266-pro2-a Newbie getting WIN stop error

I'm doing my first MB and CPU upgrade from my outdated PII 450. I just bought a new tower (450W PSU), K7t266-Pro2-A MB, Athlon XP 2000+, Mushnik 516MB PC2100 DDR, Volcano 6.0 CPU fan and heatsink. I put all the new components together and added the CD-ROM, NIC card, graphics card and two new western digital drives (purchased 2 months ago) from my old computer.
P.O.S.T recognized all the components, went to NT Loader screen, and selected Windows 2000. 2000 starts to load drivers and "Wham!" stop error 0x0000007B: Inaccessible Boot Device. I've got a triple boot with Win 98, 2000, and XP. Rebooted and tried XP, same error. Rebooted and tried Win 98, PnP pops up finding new Controller etc...., able to boot Win 98 OS. Only problem is that I need the 2000 the most.
I unplugged both CD-ROMS and the slave HD, setting the Primary as a single dirve, reboot. Same thing with 2000 and XP. So I'm figuring the problem has to do with the IDE, Chipset, HD or other MB specific drivers. But I'm using the primary drive right now on my old computer so it isn't corrupt or virus infected. Unfortunately the HD's are my work drives and I have nothing else to use currently. I don't want to re-install all my Os's and software :(. At the moment I'm stuck swapping out the shared components between the working and non-working machine.
Is it necessary to re-install OS's when upgrading MB and CPU? Can I update the 2000 and XP drivers for the MB? Would performing a repair installation work to preserve my current profiles while updating the drivers? I was also thinking that I could Ghost my current 2000 partition to another partion, naming it differently and making it a loader screen option. Then I could use that one to configure the new MB without risking the other?
Sorry about the long post. I've been trying to find info regarding 2000 MB upgrades but have only found the basic upgrade articles. Does anyone have a link to any more info about this? Thanks in advance!

Thanks for the reply! I guess I'll try the Ghost parition and 2000 repair. I'd do the clean install too but I just rebuilt all three OS's last month. :( Do you have an opinion of the K7T266 Pro2-a? I bought it and the Athlon XP 2000 yesterday for $139.

HELP! k7t266 pro2-u winxp install

Hi,
I have a problem with installation of winXP SP1 on my computer. First i got a blue screen in the first step of installation (windows loads drivers, then freezes). It said that acpi.sys is the problem. I disabled it and then the problem was irq not less... . Then i disabled
internal cache, system bios cacheable and shadowing options and installation started but the computer was too slow ( it took about an hour to copy the files on hard disk). After the installation was finished i put back the fields internal cache to writeback and c00 32k shadow to cached and left system bios cacheable on disabled ( i read in the manual that it might be a reason for system hangups) to speed it up. For a while it seemed like it was working ok, i installed the drivers, software... but tomorrow everything up. windows started to freeze when i tried to encode mp3's from audio cd's, when i tried to install new sofware...
I dont know what to do and don't want to disable internal cache because of the huge system slowdown...
Can anyone help !!!
my config is
amd athlon xp 1800+
microstar k7t266 pro2-u with lan
256mb kingston 266 ddr
maxtor 40gb ata133
teac w540e writer
nvidia g-force 2 mx400 64mb

Quote
Hi!
What can your PSU provide in terms of ampères?
Load BIOS setup defaults. Open case.
Have the HDD and the CDRW on different IDE channels and cables, with both as Master respectively at the end of the cable.
Install VIA 4in1 drivers.
When everything works, make proper BIOS adjustments.
Best wishes, and good night!
Can't provide the data about my PSU because i'm not at home right now.
I will do it tomorow.
Cables are already set up like that.
Thank you

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

Raid 0 Failure! XP Pro won't read array on MSI k7T266 pro2 *URGE

Before anything else, thanks for reading and I hope you can help:
I have an MSI k7T266 Pro2A-RU motherboard with 512MB of Mushkin RAM, AMD XP 1600+, a Geforce2 MX400, Audigy Soundcard and a cheap PCI NIC card. I consider myself an above average technician and I've come up on a problem I can't figure out. There is about 80GB of data at stake here:
I have 2 IBM Deskstar 40GB 7200 RPM drives that were configured in a RAID 0 (stripe) configuration over a year and a half ago. This gave me a total of 80GB online. Windows XP Professional was installed and the drives have been running fine every since...
The system was practically bulletproof and it was very rare it ever locked up for any reason. A few days ago, however, the system locked up about 4 or five times. There was no software or hardware that had been added or installed and system use hadn't really changed up or down. I run up to date antivirus software (Command Anti-Virus), run behind a secure firewall and watch what I open. The lock ups were random, but happened when I was away from the computer. ( I leave my system on all the time).
Being a bit paranoid, on 1/28/03, I acquired an 80GB Maxtor drive to install to back up my datafiles. Before the install, I notice the system had locked up at least once that day, so I figured I would hurry up and get the drive in to back up. I installed the 80, booted, configured it in XP and made it active and transfered a few test files over. No problem. I made the decision to back up my data files before bed and continued to work for the next two hours. The system ended up locking up with a windows blue screen STOP error message: KERNEL_FAULT_INPAGE_ERROR when I tried to run a program. Thinking little of it, I rebooted the computer to find I could no longer access the data on the RAID.
I've tried nearly EVERYTHING I can think of. (You can already assume I've done the basics (check/replace the cables, etc). Here's a list and the results:
---- Reboot in all available modes (Safe, Safe with NW, Normal, Last known, etc). They all FAIL. In safe modes, you can see where the system actually tries to boot off the array (runs through driver files and stops on MUP.SYS) and hangs. Same result with all other drives removed except the RAID.
---- Installed another drive, loaded XP with the raid controller files (By the way, it's a Promise ATA 100 "lite" controller), plugged the RAID back in and it hangs on boot up. Safe mode gives the same results. Tried the same thing with Windows 2000 (so I could access the NTFS partition) and Windows 2000 won't load when the array is plugged in, but loads ok when it isn't (used the 2000 driver for the RAID controller for this attempt). Safe mode gives the same results.
---- Removed all drives except the Array and tried to reload XP (with the array drivers downloaded again from the site.) No effect. System hangs.
---- In a last ditch effort, I have access to Winternals Administration Pack 2002 of all of their tools. ERC Commander, designed for this type of problem, Disk Commander, and the other tools all do the same thing: Any time the system attempts to read from or access the arry, the OS will hang. It won't even check for NTFS compatibility in the ERC commander program booting from a boot CD, and for those that are familiar with it, the Disk Commander program blue screens with a STOP: 0x000007B (0xF896963C, 0xC0000034, 0x0, 0x0) error. Research has told me this is an INACCESSABLE BOOT DEVICE message.
These are the main highlight major attempt things and there's a few things in between I've tried (like using Norton Ghost to try and mirror the array to the 80GB. Norton ghost said there is an error reading the partition and can't go any further (Returns an Internal error))
I'm at the point where I have run out of available options and don't know what else to try. I have since purchased the exact same motherboard off e-bay to see if it just so happens to be the controller and to see if my RAID will come back so I can at least read the data off of it. It should be here in a few days. If that doesn't work, I'm toasted. Could I be fighting a hardware (drive or board or controller) problem. Is the array THAT corrupt the OS can't read it???
If anyone has any other bright ideas, I'm willing to try about anything short of damaging the array. Any help is greatly appreciated. Please post here, or e-mail to [email protected].
BTW, the Promise BIOS is Fasttrak 100 "Lite" v 1.31.1(Build 30)
Thanks.
- Chuck! ?( ;( ;( ;( ;( ?(

got one but its lightley used for storage but amd forum storage is full of tales of woe with them
type deskstar and problems in goggle for a laugh

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

K7T266 Pro2-RU Hard drive size limit

What is the maximum size hard drive that the BIOS can handle for the K7T266 Pro2-RU board? The official web site and BIOS updates are sort of vague... I know that the regular limit is 137 GB, and Windows XP Service Pack 1 has some kind of workaround. Will there be problems with installing big hard drives on this board? I'm not planning on using the RAID controller...
Thanks

well that works for drives over 32gb and under 137gb on boards whos bios cannot see drives over 32 gb
but ive never seen it proved to work with drives over 137 gb in a board cannot cope thith drives that big
bios indicates the raid has 48 bit lba support so usde your big drives on that
https://forum-en.msi.com/index.php?threadid=292&sid=

MSI K7T266 Pro2-RU - problem with the lite-raid - would like to use it as a normal ide

Hi!
I tried to install a single drive on the raid-controller and create a single array for it.
For some reason the disk management in Windows XP does not see it, even though
I have updated the related drivers. However, the Disk management showed it the first time after I had installed the HD onto the raid, but as I could not do anything intelligent with Disk management in regard of the HD, I removed the drive from Disk management with that effect that the disk management does not recognize the drive at all, even though I have now re-created the array on the risk, disabled and enabled raid on the Bios.
I read that there exists modified bios for MSI KT3 Ultra ARU BIOS, which will turn the Raid into regular IDE. That would be something that would most probably be the best way to proceed for me. However, do such bioses exist for MSI K7T266 Pro2-RU? Any other suggestions on how to get the disk management to succeed in recornizing the IDE on the raid-controller would be good to hear as well.
Yours sincerely,
Tero

Ok, I tried updating with the hacked 3.7 Full Raid Bios. Now I seem to have another problem: even though the hacked bios recognizes my HD, it thinks it's about 130 GB, when it in reality would be 250 GB. The hacked bios seems to work ok with Disk Management in Windows XP too, so it's a shame that the hacked bios doesn't seem to have a support for large disks. On the other hand the link at Lumberjacker was dead for the hacked bios v3.6, I would have tried it, if it would have provided me with a good solution to my problem.
I then went back and installed the official v3.7 bios and the lite raid does now recognize the HD being 250 GB, but the Disk Management just states "Missing" in regard of the HD and does not let me do anything fruitful with it. I looked the HD's properties and the Device Manager just states "Hardware device not connected code 45".
How in earth could I manage to make this work now (I do not want to move my other HD:s as they are full of stuff and don't want to risk losing any content)?
General specs of the computer: IDE 1: 60 GB and 120 GB Matrox, IDE 2: Nec2500 and Sony DVD-Rom, Athlon 1800+ XP, 512 MB memory, Ati 9700 np, Network adapter card. The new HD to be added is a 250 GB WD (have removed the jumper)
Thank you for any tips,
Tero

K7T266 PRO2 RU constant freezing! need help!

Ok, after two weeks reading every thread in this forum that has this word "K7T266" on it, i decided to write these lines:
My good k7t266 pro2 ru stopped working a few weeks ago, i thought it was the cpu processor (athlon 1800+, i think thorougbred), the thing is that windows xp gots freeze randomly, i have reinstalled almost 10 times, trying everytime different bios combinations (version 3.3 through 3.7) and different settings (the ones written in some tweak/perfomance threads here), i have also tried three different power supplys (250W,350W and 400W) (amps always exceeded your recomendations on other threads), i also have tried different memorys in different combinations (1 bank, 2 banks, etc), tried too 2 different video cards (gforce 4200ti 128mb from evga and a gf4 440mx from excalibur i think), i have removed every other card (nic, usb connectors, etc), also have tried with a different hard disk (40 gb and 60 gb from maxtor and western digital). Tried cleaning and adding new thermal paste to the HSF (is the one that comes with the cpu), tried connectin the cpu fan to the power supply, tried with a different cpu (athlon 1300, palomino i think). I dont remember what else i tested, oh, i have it totally "naked" (no case) , i can send you pictures of it , oh, another thing i tried different via drivers (none, 4.43 and 4.49) , and windows xp has sp1. Ok, i dont remember anything else by now, i am buying a kt6 delta (i saw bas loved it) it must arrive this tuesday but i dont want to throw the k7t266 to the trash, it seems to me that there is some bad capacitor (they dont look abnormal, i have fixed msi boards with blown and inflated capacitors before). Ok , i just wanted to know that i really need your help here, dont know what else to say. Thanks a lot for your answers. :(

Ok, i am not at home to test the voltage thing that h2O proposed (i tried once but was afraid of burning cpu and memory, these things arent cheap in venezuela), and about the temps, they were around 40 (idle) and 50 (playing battlefield1942) (it's very hot in my room), that's why i got the board undressed (no case at all, just PS) . H2O , can you please help me with the voltage thing ? which values are safe and can be tested? tomorrow i will have the kt6 delta but i still want to know if the k7t266 can be used or sold.
Other things
- i have cleared cmos everytime i changed settings proposed here.
- i have clean installed xp (format c: partition) , BTW it sometimes got freeze during the first stages at installation , specially if i set FSB to 133.
- i did not tried to overclock (too hot and too expensive to try, i can not afford and/or find a better cooling device (water, best fan, etc)).
Again, i would really appreciate any help you can give to this poor bastard ;(
PS: sorry for my english, it's not my native language.

K7t266 Pro2 And Pc2700 Ddr Ram?

Does anybody here know if a k7t266 pro2 mobo will support pc2700 ddr ram? COMPUSA Has a great deal on PNY right now--512mb pc2700 ddr for 50 bucks after rebates....As far as I have read, the documentation says pc1600 or pc2100. But we all know that rules are meant to be broken.......
Thanks for any help I receive!!!
My specs are in my signature!

You can use pc2700 ram but without any benefit against pc2100, speed will be the same.
Be aware that it's normally no good idea to mix different ram type, this can cause trouble.

K7T266 Pro2 RU repaired but...

Similar Messages

Maybe you are looking for