Recent content by Brambory

Well, the problem is solved, by a move that I never would have thought had anything to do with it. I swapped the video cards from case a to case b. The two cards in question are Matrox G400 and a Matrox G550. When I checked through all of the system information stuff and device manager...

Yes, I have the mainboard sitting up on standoffs. It works fine in safe mode. I think that if it was shorted that it would not work. Going into system information and device manager turns up with everything looking fine. But it still reboots automatically after the welcome screen or just when...

I haven't tried switching the power supplies yet. I googled the problem and came up with the idea to go to safe mode and disable the automatic restart on error message. So then when the reboot cycle started again I could read the error message BAD__POOL__HEADER. So now I'm trying to find out...

I checked and double checked, and I've got them right. Plus, I have an almost identical computer that is set up the same way. I took the mainboard, hard drive, and dvd burner from case A and put them into case B. I also did the reverse--swapped the guts from case B into case A. I left the...

I checked those connections. I unplugged and reversed polarity on the three that are the seven pin header (hdd led, reset sw, and power sw) and no change. I didn't think that it mattered which way they went, since they fit on both ways, and most mainboard connectors are made so they can only be...

I just transferred all of the guts of a homebuilt computer into another case. The computer components in that case were working fine, so I know the case itself was okay before the transfer. On the first startup it reboots as soon as the desktop is displayed after going thru what looks like the...

Thanks. I don't know how to change the memory voltage. Is is easy to do without frying it? My psu is a Zalman 300w. I just spent some time on the MSI mainboard and memory forums and read some pretty frustrated posts by people trying to run Crucial RAM, or for that matter any amount of RAM over...

The Crucial is the same timing as the Samsung. I already have the BIOS set to auto-detect RAM timings. I didn't think of taking out the Samsung and running only the Crucial. I'll try that tonite. Thanks. If that doesn't work maybe it's an excuse to upgrade. This time I'm thinking of being less...

I put two new sticks of 512 Crucial 2100 DDR SDRAM CL 2.5 on my MSI KT266 Pro2 running XP Home and Athlon XP 2100+. The two new sticks are in addition to the 512 Samsung (CL 2.5) that was already there. It seemed to run okay for awhile, then I got a blue screen that I have never seen before...

I'm having a problem diagnosing a problem with my folk's computer. They are in a residence with a T1 ine which is then distributed to each apartment. It was running fine for several months, then it slowed to a crawl. I tested it on a bandwidth test site at about 3kb per second! I tried the...

Oops, sorry. 98SE MSI K7T266 Pro2, Athlon 1800+, 512 Corsair 2100 RAM, Sony GDM F400, Seagate Barracuda IV, etc BTW I'm moving to XP Home as soon as my Radeon 9600 Pro comes next week

After going in circles for 2 hours I thought that I would ask you guys to save the day. After a botched game installation where I tried to reinstall graphics drivers, I have no picture, except in safe mode. In device manager the name of the graphics adapter is there, Matrox G550, but has a red X...

I got the unit used and it didn't come with a cd. It originally had Windows 95 on it. When I replaced the HDD I put 98SE on it The original HDD had a bunch of things to download onto floppies to transfer to a new HDD should the need arise. I did most of those. I'm tempted to put the old HDD...

I have a Dell Latitude Cpi laptop that has several problems since putting in a new HDD, new BIOS, then 98SE, and I wonder if the problems are connected. When it boots up there are two beeps which I assume are some sort of code that means something is wrong (a low tone long and a higher tone...

Thank you very much for suggesting to go to Device Mgr and delete the cdrom. That did the trick. But, like everthing else with computers, it was wierd because when I rebooted there was a different cdrom listed in Device Mgr. Before there was only one, a different one from what is there now. And...