Dang SCSI controller!!!

Bobo · 08-13-2006, 02:55 AM

OK, so I wanted to get some data off of 2 SCSI hard drives that I have. So no big deal, I plug the hard drives and the SCSI controller card into my computer. I had successfully done this before, and it wasn't hard. Not to be this time. The computer turns on, but it gives me a long beep, waits a couple seconds, then a short beep and turns on. According to the motherboard manual, this means either a DRAM or mobo issue. So it boots fine, but after the Windows loading screen, it gives me a BSOD for about .02 seconds and restarts. I think the BSOD said something about a physical memory dump. So it restarts, and after the Windows loading, up comes a CHKDisk screen. It gets to 5% before doing the same thing again. So I try to boot into Vista, it runs the CHK disk just fine and boots. But it can't see the SCSI drive. So I give up with the SCSI and reboot it. It still won't boot into XP. So I run CHKdisk again from Vista, and then XP boots. But it still gives me the beeps when it boots. And I have gotten one or 2 random restarts while the system has been running.

What the heck did this SCSI card do to my computer? How can I fix it?

PC eye · 08-13-2006, 03:15 AM

You are running the Vista beta version without drivers for your SCSI controller? is one immediate thought there. Both OSs need drivers. Have you installed the XP drivers on the XP side? Bios settings can also play a role too.

Bobo · 08-13-2006, 03:27 AM

I don't have drivers. I had worked it before without drivers.

Vista really doesn't play a role here, just that I used CHKDisk from the Vista boot screen to fix the hard drive so that it would boot XP.

Should I try resetting the BIOS?

PC eye · 08-13-2006, 04:56 AM

You were fortunate when it worked before probably due to XP having a generic driver onboard to load. Now you are most likely stuck because like any other hardware it's needs drivers in order to work correctly. That would be the first thing to try there.

Bobo · 08-13-2006, 01:36 PM

Well yeah, I will try to find drivers. But why is my system so screwed up even when it is not plugged in?

PC eye · 08-13-2006, 10:30 PM

Just where did you did install the beta release of Vista? Was that put on a second partition or a second drive? When dual OSing the older version of Windows goes onto the first primary partition. The newer version is always installed following the first even if it goes on a separate hard drive. To avoid the newer version from autoloading both you would install that to a separate drive with the primary unplugged. The boot device order in the bios then decides which OS is loaded by the setting there unless you use a boot loader like ubuntu's boot manager on floppy that will ask which drive/partition do you want to load. It then finds the OS there and loads it.

On the other thread I gave you some tools to work with on cleaning up the software side of this while you may have to look at the bios settings as well as your jumper settings with more then one ide drive if you are running one as well as adding the array. When you mention hearing a long and then later a short beep what bios do you have on the board? Do you know? Is it Award, AMI, Phoenix? A single long beep doesn't always mean a hardware fault. http://pcsupport.about.com/cs/mother.../beepcodes.htm

Bobo · 08-14-2006, 01:48 AM

Quote:

Originally Posted by PC eye

Just where did you did install the beta release of Vista? Was that put on a second partition or a second drive? When dual OSing the older version of Windows goes onto the first primary partition. The newer version is always installed following the first even if it goes on a separate hard drive. To avoid the newer version from autoloading both you would install that to a separate drive with the primary unplugged. The boot device order in the bios then decides which OS is loaded by the setting there unless you use a boot loader like ubuntu's boot manager on floppy that will ask which drive/partition do you want to load. It then finds the OS there and loads it.

What the heck are you talking about? I have no problems with booting dual operating systems, and I do know how to do so.

Quote:

On the other thread I gave you some tools to work with on cleaning up the software side of this while you may have to look at the bios settings as well as your jumper settings with more then one ide drive if you are running one as well as adding the array. When you mention hearing a long and then later a short beep what bios do you have on the board? Do you know? Is it Award, AMI, Phoenix? A single long beep doesn't always mean a hardware fault. http://pcsupport.about.com/cs/mother.../beepcodes.htm

I looked it up in my motherboard moanual like I am supposed to. It is Award, but I know what the codes mean.

PC eye · 08-14-2006, 01:59 AM

AWARD BIOS BEEP CODES

Below are Award BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary.

Beep CodeDescription1 long, 2 shortIndicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional informationAny other beep(s)RAM problem.

If any other correctable hardware issues, the BIOS will display a message.

Bobo · 08-14-2006, 02:45 AM

According to the motherboard manual:

1 long, 1 short indicates a DRAM or M/B problem.

PC eye · 08-14-2006, 03:49 AM

If you notice from the mention seen at one site that "anything else" other then "1 long 2short" equals "RAM problem". Are those beeps heard close together or is there a long pause inbetween. On some bioses a single long beep followed by the normal quick beep later implies post tests were successful.

08-13-2006, 02:55 AM	#1 (permalink)
Bobo banned Join Date: Nov 2004 Location: Pittsburgh Age: 18 Posts: 6,623	Dang SCSI controller!!! OK, so I wanted to get some data off of 2 SCSI hard drives that I have. So no big deal, I plug the hard drives and the SCSI controller card into my computer. I had successfully done this before, and it wasn't hard. Not to be this time. The computer turns on, but it gives me a long beep, waits a couple seconds, then a short beep and turns on. According to the motherboard manual, this means either a DRAM or mobo issue. So it boots fine, but after the Windows loading screen, it gives me a BSOD for about .02 seconds and restarts. I think the BSOD said something about a physical memory dump. So it restarts, and after the Windows loading, up comes a CHKDisk screen. It gets to 5% before doing the same thing again. So I try to boot into Vista, it runs the CHK disk just fine and boots. But it can't see the SCSI drive. So I give up with the SCSI and reboot it. It still won't boot into XP. So I run CHKdisk again from Vista, and then XP boots. But it still gives me the beeps when it boots. And I have gotten one or 2 random restarts while the system has been running. What the heck did this SCSI card do to my computer? How can I fix it?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
4 questions	kgod86	General Computer Chat	13	07-15-2006 03:49 AM
Computer Freezes randomly	wwfc_barmy_army	Desktop Computers	16	05-30-2006 02:38 PM
Laptop CPU Operating Too Hot???	ghghgh	Laptop and Smartphones	15	10-10-2005 03:34 PM
Hdd 101	Praetor	Computer Memory and Hard Drives	7	04-04-2005 12:55 AM
SCSI daisy chain or seperate SCSI connections to adapter?	MJR	Computer Memory and Hard Drives	5	03-25-2005 04:33 PM

08-13-2006, 03:15 AM	#2 (permalink)
PC eye banned Join Date: Apr 2006 Posts: 21,091	You are running the Vista beta version without drivers for your SCSI controller? is one immediate thought there. Both OSs need drivers. Have you installed the XP drivers on the XP side? Bios settings can also play a role too.

08-13-2006, 03:27 AM	#3 (permalink)
Bobo banned Join Date: Nov 2004 Location: Pittsburgh Age: 18 Posts: 6,623	I don't have drivers. I had worked it before without drivers. Vista really doesn't play a role here, just that I used CHKDisk from the Vista boot screen to fix the hard drive so that it would boot XP. Should I try resetting the BIOS?

08-13-2006, 04:56 AM	#4 (permalink)
PC eye banned Join Date: Apr 2006 Posts: 21,091	You were fortunate when it worked before probably due to XP having a generic driver onboard to load. Now you are most likely stuck because like any other hardware it's needs drivers in order to work correctly. That would be the first thing to try there.

08-13-2006, 01:36 PM	#5 (permalink)
Bobo banned Join Date: Nov 2004 Location: Pittsburgh Age: 18 Posts: 6,623	Well yeah, I will try to find drivers. But why is my system so screwed up even when it is not plugged in?

08-13-2006, 10:30 PM	#6 (permalink)
PC eye banned Join Date: Apr 2006 Posts: 21,091	Just where did you did install the beta release of Vista? Was that put on a second partition or a second drive? When dual OSing the older version of Windows goes onto the first primary partition. The newer version is always installed following the first even if it goes on a separate hard drive. To avoid the newer version from autoloading both you would install that to a separate drive with the primary unplugged. The boot device order in the bios then decides which OS is loaded by the setting there unless you use a boot loader like ubuntu's boot manager on floppy that will ask which drive/partition do you want to load. It then finds the OS there and loads it. On the other thread I gave you some tools to work with on cleaning up the software side of this while you may have to look at the bios settings as well as your jumper settings with more then one ide drive if you are running one as well as adding the array. When you mention hearing a long and then later a short beep what bios do you have on the board? Do you know? Is it Award, AMI, Phoenix? A single long beep doesn't always mean a hardware fault. http://pcsupport.about.com/cs/mother.../beepcodes.htm

08-14-2006, 01:59 AM	#8 (permalink)
PC eye banned Join Date: Apr 2006 Posts: 21,091	AWARD BIOS BEEP CODES Below are Award BIOS Beep codes that can occur. However, because of the wide variety of different computer manufacturers with this BIOS, the beep codes may vary. Beep CodeDescription1 long, 2 shortIndicates a video error has occurred and the BIOS cannot initialize the video screen to display any additional informationAny other beep(s)RAM problem. If any other correctable hardware issues, the BIOS will display a message.

08-14-2006, 02:45 AM	#9 (permalink)
Bobo banned Join Date: Nov 2004 Location: Pittsburgh Age: 18 Posts: 6,623	According to the motherboard manual: 1 long, 1 short indicates a DRAM or M/B problem.

08-14-2006, 03:49 AM	#10 (permalink)
PC eye banned Join Date: Apr 2006 Posts: 21,091	If you notice from the mention seen at one site that "anything else" other then "1 long 2short" equals "RAM problem". Are those beeps heard close together or is there a long pause inbetween. On some bioses a single long beep followed by the normal quick beep later implies post tests were successful.