MB Help

Toggle sidebar Toggle sidebar
J

JShaffer

Distinguished
Feb 12, 2004
19
0
18,510
I recently had to change out my intel MB and 3.2 processor with a Shuttle AV49P/9 and a 2.4C. After install went well, I went to power up the comp and naturally windows wouldn't start, even in safe mode. Booting up from the CD, however, leds me to a problem: The install CD tells me that no HD is attached.
I'm using a Maxtor SATA drive, and SATA is enabled in the BIOS. On startup, the BIOS and the RAID utility attached to BIOS (two seperate menus) both recognize the drive as being attached. The BIOS, like all of them, is pretty straight forward and I'm almost 100% certain that every possible configuration dealing with serial drives/IDE is correct.

Secondly, at startup, the computer recognizes that the processor is a 1.2ghz P4 instead of the 2.4.

Any help would be greatly appreciated.

-James
 
Good! You listened to my advise!

For your CPU detection problem, it's probably your FSB. In the BIOS fix the FSB speed to 200MHz (200MHzx4 = 800MHz FSB). Your multiplier will be 12 (200MHzx12 = 2.4GHz).

What is your Windows version? Your SATA controller might not be compatible with old windows version.

--
<b><font color=red>GO!</font color=red> <font color=blue>HABS!</font color=blue> <font color=red>GO!</font color=red></b>
 
XP Pro both on the HD and on the instal CD.

Looking through the BIOS menu and the manual, I don't see a way to change the FSB settings. The closest AMIBIOS offers as far as I can tell is enabling and disabling Hyperthreading. There is a jumper setting, I believe, that I can select between 100, 133, and 200 for the CPU freq- is that what you mean?

-James
 
What is your MB manufacturer/model? Have you check their website for FAQ about SATA controller?

Yes, you must set the jumper to 200MHz, it's probably why you only get 1.2GHz instead of 2.4GHz, it runs the FSB at 100MHz instead of 200MHz.

--
<b><font color=red>GO!</font color=red> <font color=blue>HABS!</font color=blue> <font color=red>GO!</font color=red></b>
 
Humm... I'm not used to SATA controllers, what I would suggest you is to try to install WinXP from a standard IDE drive and see if Windows can see your HDD after the installation and drivers updates. If not, it might be a defective controller. If Windows sees the HDD AFTER you have installed some SATA drivers, it's because Windows XP don't "natively" support your SATA controller, so you might need to put your driver on CD/diskette and use them at the WinXP install screen. When you boot from the WinXP install CD, at one point it asks you to install thrd party drivers for unsupported controllers.

--
<b><font color=red>GO!</font color=red> <font color=blue>HABS!</font color=blue> <font color=red>GO!</font color=red></b>
 
Windows XP doesn't natively support any SATA drivesr that I've seen. To get Windows install to see the drive at all you neeed to copy the controller drivers to a disk and then hit F6 during the isntall when it asks you if you need to install any additional drivers.
 
Changing the jumpers fixed the comp speed issue, but I can't seem to locate the actual drivers. Downloading the RAID drivers from their website is 8MB large, and I'm not sure which files to copy onto a floppy. On insert, it looks for a .oem file, naturally: any suggestions on which drivers I looking for, what files associated I need, and where to find them?

Thanks again for the help.
 
I've always found the needed drivers on the motherboard CD. In fact they are often accompanied with a (floppy) disk creator program that formats the floppy and installs the drivers to it.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
 
no additional floppy was provided. Their tech help leaves much to be desired, I must say.
I'm fairly certain from all the good advice I've been given here that a simple driver update during windows installation will fix the problem, however, again, out of the 8mbs of files, I need to know which ones to put onto a 1.44 floppy...
 
Since SHuttle(and everyone else) doesn't seem to think there is an AV49P/9, I'm figuring you mean the AV49P/N.
Did you read the readme.txt in the raid driver file? Specifically of interest, would be section 7.2, near as I can figure

2. Install Windows NT 4.0, 2000, XP, or Server 2003

* Copy all files and directories of DriverDisk\SATA folder to a floppy disk. Make sure following directories and files are copied into floppy disk.
A:\
\2003IA32
VIAsraid.inf
VIAsraid.sys
VIAsraid.cat
\Win2000
VIAsraid.inf
VIAsraid.sys
VIAsraid.cat
\Winnt40
VIAsraid.inf
VIAsraid.sys
\WinXP
VIAsraid.inf
VIAsraid.sys
VIAsraid.cat
Txtsetup.oem
VT8237

* Boot system from OS installing CD-ROM.
* Make sure VT6420 BIOS is executed by the system BIOS when POST.
* Press "F6" when OS installer starts running.
* Insert floppy disk.
* Choose the OS device driver wanted for loading.
* Install OS.
* Run setup.exe after OS is installed.


Can't say that the writer of the Readme had the best command of the English language, but still seems pretty clear.
 
wow, can't believe I missed that.

when it rains, it pours... after following your (and the manual's) directions, I get this error:
"\winxp\viasraid.sys unexpected error (4100) at line 2108 in d:xpclient\base\boot\setup\oemdisk.c" and then back to setup. Any thoughts on this one?

-James
 
See? I told you the files would be on the CD. I probably should have mentioned you have to use your own floppy disk, but I figured that was implied.

Anyway, did you wait for the F6 prompt from XP setup? I think the most likely problem is a missing or bad file on your floppy. Floppy disks aren't very reliable, so bad files are common, you might have to use a different disk.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
 
Same file error every time? Are you pulling those files from the driver directory correct for the OS you're installing?

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
 
Wow, you could have a bad driver revision on the CD!

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>
 
What Crash said is completely possible, I had something similar(dont' remember exact text of error now) installing XP on Via raid chipset(pide, not sata, but same type of problem) on my p4p800dlx. I had to look around and find another version of the driver. SHould be a lot of boards around with that Via controller, I'd look around on other SHuttle boards, or boards from other manufacturers, and try to find a different driver version(older version, if my experience holds through that far)
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom