ElMonoDelMar
Golden Member
- Apr 29, 2004
- 1,163
- 338
- 136
I didn't have a floppy drive either and still don't so I slipstreamed(integrated) the drivers into a copy of WinXP.
As for the USB idea, AFAIK it's not possible.
As for the USB idea, AFAIK it's not possible.
ElMonoDelMar
Golden Member
- Apr 29, 2004
- 1,163
- 338
- 136
I just got back from staples. 28 dollar internal floppy drive. Dang those things are cheap. I'm gonna see if I can't put that driver on the floppy and see what happens.
I need help please
I have read every post and tried what I could find and no success. Heres my problem(others had similar)
Just bought a 74GB Raptor SATA drive. Connected the Power cable and red cable that mobo comes with and connected it to the VIA controller(the top one on moboSATA1) I enabled Boot SATA. I made CD 1st read so I can install windows, and hit F6 at the screen where it ask. I put the disk with the 378ATA drivers and select XP drivers. then enter to continue. When windows is at setup it says it cant find the HD. I restart, hit TAB and see the WD Drive there on the VIA controller part but I cant move anything with the arrows(WHY?) Since I am using the VIA one I left the Onboard Promise to OFF, right? Someone please tell me what part I am doing wrong. I have read similar incidents and tried what they did and still wont work. I know its something small I am missing. If I set the boot priority to VIA(so it will be the HD first) it goes but i get a blinking cursor and cant install windows. Set it back to the CD boot 1st. On the screen where the IDEs are, i dont see my HD as the primary, it says not detected
I am getting so frustrated because I am usually pretty good at PCs and this is my 1st SATA dribve and its driving me nuts. I swear I will thank whoever helps me step by step, so much and really appreciate it. I will even do IM through ICQ or AIM or email if you guys want to help me =( Thanks and hope to hear answers fast.
I have read every post and tried what I could find and no success. Heres my problem(others had similar)
Just bought a 74GB Raptor SATA drive. Connected the Power cable and red cable that mobo comes with and connected it to the VIA controller(the top one on moboSATA1) I enabled Boot SATA. I made CD 1st read so I can install windows, and hit F6 at the screen where it ask. I put the disk with the 378ATA drivers and select XP drivers. then enter to continue. When windows is at setup it says it cant find the HD. I restart, hit TAB and see the WD Drive there on the VIA controller part but I cant move anything with the arrows(WHY?) Since I am using the VIA one I left the Onboard Promise to OFF, right? Someone please tell me what part I am doing wrong. I have read similar incidents and tried what they did and still wont work. I know its something small I am missing. If I set the boot priority to VIA(so it will be the HD first) it goes but i get a blinking cursor and cant install windows. Set it back to the CD boot 1st. On the screen where the IDEs are, i dont see my HD as the primary, it says not detected
I am getting so frustrated because I am usually pretty good at PCs and this is my 1st SATA dribve and its driving me nuts. I swear I will thank whoever helps me step by step, so much and really appreciate it. I will even do IM through ICQ or AIM or email if you guys want to help me =( Thanks and hope to hear answers fast.
378 ATA drivers aren't the drivers for the VIA SATA controller. Those drivers are for the Promise SATA controller (ATA Mode). For single drive operation I'd probably use the Promise SATA controller over the VIA. Reason being, Any hard drive(stand-alone or in RAID/JBOD) won't display any type of hard drive activity light on your case when connected to the VIA SATA controller.
OTOH if you would rather use the VIA controller regardless. I'd use these drivers for the VIA SATA controller. Your single drive will probably be read as a SCSI device in windows if you choose this method unlike the Promise which will(don't remember for sure) be displayed under windows as a SATA device.
P.S. If you do so decide to use the Promise SATA controller, you may want to enable "Onboard IDE mode" or however it is displayed in the BIOS opposite of "RAID mode" while disabling the Boot option for the VIA.
Come on guys, someone please help me=(
I have tried every combination possible and it wont work on either the promise or VIA connections. I am running out of ideas and setting changes.
I have tried every combination possible and it wont work on either the promise or VIA connections. I am running out of ideas and setting changes.
Thanks for response. Ok, i want to use that file u said but its 7 megs, that wont fit on a floppy to install at F6 ??
I am not installing it as a slave to current setup, i unplugged my ATA drive and use my bros PC to come here and check what to do.
Now, if I connect it on the Promise connections, it wont show up at all, which is why I have been trying to use the VIA, at least there, i see it under the VIA setup screen when you hit tab. But at the windows setup , it sasy no hard disk found. Sorry to bug you but please help me some more.
I am not installing it as a slave to current setup, i unplugged my ATA drive and use my bros PC to come here and check what to do.
Now, if I connect it on the Promise connections, it wont show up at all, which is why I have been trying to use the VIA, at least there, i see it under the VIA setup screen when you hit tab. But at the windows setup , it sasy no hard disk found. Sorry to bug you but please help me some more.
In Addition to my OP: The reason you may not be able to move the arrows might be because it's only movable when you have 2 or more drives ready for RAID/JBOD setup.
That file is 7 megs(about) but within that file there's a small program that makes a driver installation disk for the floppy which is well under 7 MBs.
EDIT: I haven't used the Promise controller for awhile so if my memory serves, if it says not detected it may be because in the BIOS the Promise controller may not be set to IDE mode.
Killa,
Somehow I got beyond windows xp not recognizing I had a hard drive. As I did not write down exactly what I did, please bear with me. After trying like you have been trying for numerous hours to no avail I just got fed up with what I was doing and kept plugging away. I did happen to end up using the fasttrak controller. I ended up connecting my 36 gb wd raptor to the sec_sata connector of all places. I had also hit alt f4 and set up my single hdd in a raid setting. (Why not I figured I had nothing to lose). This of course was after countless times (reformatting a floppy and putting the information i.e. raid or sata driver onto the newer computer). I also had to hit f6 immediately upon windows set up.
What finally happened and why? I have no earthly idea why it finally worked. I'm just glad it did. After setting it up like I did above, I once again used the drivers floppy raid (fasttrak this time) upon windows set up. This time the computer took those drivers and ran with them and I was able to set up Windows XP on my computer.
{My current roadblock happens to be with something more mundane. I can not get my New computer to work ethernet wise. I' thought this board had ethernet capability. How do I turn that on? Where do I find it? I've turned it on in the bios. I figured out where to look to toss in the tcp/ip settings. But all I find under network settings is the 1394 adapter. Any info will be appreciated in return too lol.}
Somehow I got beyond windows xp not recognizing I had a hard drive. As I did not write down exactly what I did, please bear with me. After trying like you have been trying for numerous hours to no avail I just got fed up with what I was doing and kept plugging away. I did happen to end up using the fasttrak controller. I ended up connecting my 36 gb wd raptor to the sec_sata connector of all places. I had also hit alt f4 and set up my single hdd in a raid setting. (Why not I figured I had nothing to lose). This of course was after countless times (reformatting a floppy and putting the information i.e. raid or sata driver onto the newer computer). I also had to hit f6 immediately upon windows set up.
What finally happened and why? I have no earthly idea why it finally worked. I'm just glad it did. After setting it up like I did above, I once again used the drivers floppy raid (fasttrak this time) upon windows set up. This time the computer took those drivers and ran with them and I was able to set up Windows XP on my computer.
{My current roadblock happens to be with something more mundane. I can not get my New computer to work ethernet wise. I' thought this board had ethernet capability. How do I turn that on? Where do I find it? I've turned it on in the bios. I figured out where to look to toss in the tcp/ip settings. But all I find under network settings is the 1394 adapter. Any info will be appreciated in return too lol.}
I don't see mention of installing the drivers. After you get windows installed you'll need to install the ether drivers off of the Asus CDROM. I have the K8V and it seemed like I had to have a cable properly plugged in before the marvell driver installer will run properly. (I say properly because I had a prong from the I/O shield in the way of my jack such that the jack wasn't all the way plugged in, the Marvell installer didn't seem to be running correctly, and it took me a while to realize what was going on).
I'd like to post my positive experiences with this board since so many seem to have negative experiences.
About 8 days ago I built my first ever 'computer from parts'. I'm a programmer (and game player) who's only prior knowledge of hardware was pretty much limited to some knowledge of video cards. I did a lot of research at this site and others to figure out component compatibility and to figure out what I actually wanted to buy. Three weeks ago I had no clue what cpu sockets, chipsets, ram latency, and a lot of other stuff meant (and I still only know the basics). My goal was to build a solid gaming PC within a limited budget and with no intentions of overclocking.
I decided to go with the Asus K8V board because Asus has a solid reputation and I didn't need the extra stuff from the deluxe type of boards. Throughout all my research I failed to read this thread until *after* I'd ordered my mobo from NewEgg...and I was a bit scared when I did read this thread. Although I was feeling a little uneasy after reading this thread, I also felt like I knew some of the pitfalls I needed to watch out for, like making a driver disk for SATA and the like - which is covered in the Asus manual but it could probably stand to be bolded, red, and highlighted or something since it's kinda important.
I was already intending to read all my manuals before building and reading this thread further cemented it. I'm a noob to hardware and figured I needed all the info and instructions I could get. I also used "mechBgon's (awesome) guide to building your first PC from parts" which was a huge help. As mechBgon indicates, you need manuals for specifics - but, in my noob opinion, manuals can only take you so far - for a noob builder like me it was nice to have mechBgon's guide to help with an overall build plan and strategy (not to mention that it's amusing in places.)
It took me 2-3 hours or so to assemble my PC, since I'm a noob and was being methodical, needing to refer to manuals a lot, and taking breaks between steps to refresh from mechBgon's guide. When I did my last check for loose wires and thought I was ready to boot I kinds felt like I might have a heart attack - I was sure I'd screwed something up or would have a motherboard horror story. However, my machine booted up perfectly on my first boot - and has been running smoothly nonstop ever since.
I had no problems at all with the Asus board or included bios. I found the board to be easy to work with - everything seemed nicely laid out and spaced for the components I had (keeping in mind that this was my first build and I have nothing to compare it to - and I have no intentions of overclocking). The manual, while it might've been a little more bold about pointing out some key issues like SATA setup, did contain all the necessary info to get setup correctly. I was a tiny bit concerned about the onboard sound since my older PC is SoundMax and had been screwing up a bit lately - but I'm impressed with the sound.
The one thing I do wish was a LOT more clear in the manual is which SATA controller is most ideal for a single SATA drive setup. I dunno how many times I read through that stuff but I swear all they talk about is raid setups. I also swear that I read somewhere earlier in this thread that the VIA was the most ideal for a single drive setup - but now I've read several more recent posts in this thread saying the promise is the more ideal (and that's why I don't see HD activity lights). I wish the manual was more clear on this topic. I ended up using the VIA controller - and it seems to work nicely - but I'm lacking HD indicators (no biggie).
One other thing I didn't read about until it was too late was the recommended memory for the board at the Asus site. I picked decent quality RAM and it seems to be working properly despite not being on the recommended list so I guess I got lucky.
The final system:
Antec Sonata Case (comes with 380W PSU)
Asus K8V Motherboard
AMD Athlon64 3000+ (retail - using stock HSF)
1GB Corsair Value Select RAM PC3200
Maxtor 120GB HD (SATA, 7200 RPM, 8MB Cache)
Lite-On 16x/48x DVD-ROM
Sony 3.5" Floppy
ATI Radeon 9800 Pro (128MB)
MS Windows XP Pro
(Using existing 19" monitor, MS optical mouse, and MS (original) natural keyboard)
(no burner since I have one in my old box and rarely use it)
I happened to catch the RAM and video card at the Fry's anniversary sale at nice prices - everything else I ordered from NewEgg (along with FarCry and UT2004 - gotta have some new candy to go with a new gaming system!).
I'm quite pleased with the system. It seems to idle around 34/35C and I've seen it up to 45ishC after a good gaming session - which seems reasonable from what I've read here (considering I'm using stock HSF and just the one stock fan on the Antec case - and considering I'm in Arizona where everying is friggin hot).
It's not the most state-of-the-art machine but I think it's decent for my needs and budget and it completely smokes my old (don't hurl) HP Pavillion P4 1.5ghz, 768RAM, GeForce FX 5200. (I can't dog my old system too much - I ran it hard 24/7 for over 1.5 years, put more RAM in it, went through 3 vid card upgrades, and it performed like a champ - and continues to do so for my wife.)
Cheers,
Paul
PS - Forgive my rambling. I tend to be verbose!
About 8 days ago I built my first ever 'computer from parts'. I'm a programmer (and game player) who's only prior knowledge of hardware was pretty much limited to some knowledge of video cards. I did a lot of research at this site and others to figure out component compatibility and to figure out what I actually wanted to buy. Three weeks ago I had no clue what cpu sockets, chipsets, ram latency, and a lot of other stuff meant (and I still only know the basics). My goal was to build a solid gaming PC within a limited budget and with no intentions of overclocking.
I decided to go with the Asus K8V board because Asus has a solid reputation and I didn't need the extra stuff from the deluxe type of boards. Throughout all my research I failed to read this thread until *after* I'd ordered my mobo from NewEgg...and I was a bit scared when I did read this thread. Although I was feeling a little uneasy after reading this thread, I also felt like I knew some of the pitfalls I needed to watch out for, like making a driver disk for SATA and the like - which is covered in the Asus manual but it could probably stand to be bolded, red, and highlighted or something since it's kinda important.
I was already intending to read all my manuals before building and reading this thread further cemented it. I'm a noob to hardware and figured I needed all the info and instructions I could get. I also used "mechBgon's (awesome) guide to building your first PC from parts" which was a huge help. As mechBgon indicates, you need manuals for specifics - but, in my noob opinion, manuals can only take you so far - for a noob builder like me it was nice to have mechBgon's guide to help with an overall build plan and strategy (not to mention that it's amusing in places.)
It took me 2-3 hours or so to assemble my PC, since I'm a noob and was being methodical, needing to refer to manuals a lot, and taking breaks between steps to refresh from mechBgon's guide. When I did my last check for loose wires and thought I was ready to boot I kinds felt like I might have a heart attack - I was sure I'd screwed something up or would have a motherboard horror story. However, my machine booted up perfectly on my first boot - and has been running smoothly nonstop ever since.
I had no problems at all with the Asus board or included bios. I found the board to be easy to work with - everything seemed nicely laid out and spaced for the components I had (keeping in mind that this was my first build and I have nothing to compare it to - and I have no intentions of overclocking). The manual, while it might've been a little more bold about pointing out some key issues like SATA setup, did contain all the necessary info to get setup correctly. I was a tiny bit concerned about the onboard sound since my older PC is SoundMax and had been screwing up a bit lately - but I'm impressed with the sound.
The one thing I do wish was a LOT more clear in the manual is which SATA controller is most ideal for a single SATA drive setup. I dunno how many times I read through that stuff but I swear all they talk about is raid setups. I also swear that I read somewhere earlier in this thread that the VIA was the most ideal for a single drive setup - but now I've read several more recent posts in this thread saying the promise is the more ideal (and that's why I don't see HD activity lights). I wish the manual was more clear on this topic. I ended up using the VIA controller - and it seems to work nicely - but I'm lacking HD indicators (no biggie).
One other thing I didn't read about until it was too late was the recommended memory for the board at the Asus site. I picked decent quality RAM and it seems to be working properly despite not being on the recommended list so I guess I got lucky.
The final system:
Antec Sonata Case (comes with 380W PSU)
Asus K8V Motherboard
AMD Athlon64 3000+ (retail - using stock HSF)
1GB Corsair Value Select RAM PC3200
Maxtor 120GB HD (SATA, 7200 RPM, 8MB Cache)
Lite-On 16x/48x DVD-ROM
Sony 3.5" Floppy
ATI Radeon 9800 Pro (128MB)
MS Windows XP Pro
(Using existing 19" monitor, MS optical mouse, and MS (original) natural keyboard)
(no burner since I have one in my old box and rarely use it)
I happened to catch the RAM and video card at the Fry's anniversary sale at nice prices - everything else I ordered from NewEgg (along with FarCry and UT2004 - gotta have some new candy to go with a new gaming system!).
I'm quite pleased with the system. It seems to idle around 34/35C and I've seen it up to 45ishC after a good gaming session - which seems reasonable from what I've read here (considering I'm using stock HSF and just the one stock fan on the Antec case - and considering I'm in Arizona where everying is friggin hot).
It's not the most state-of-the-art machine but I think it's decent for my needs and budget and it completely smokes my old (don't hurl) HP Pavillion P4 1.5ghz, 768RAM, GeForce FX 5200. (I can't dog my old system too much - I ran it hard 24/7 for over 1.5 years, put more RAM in it, went through 3 vid card upgrades, and it performed like a champ - and continues to do so for my wife.)
Cheers,
Paul
PS - Forgive my rambling. I tend to be verbose!
I haven't had a negative experience with this board either, nothing I couldn't handle on my own anyways.
Obviously ppl who actually don't have problems with this board don't usually post here unless they're giving advice. It's the ppl who do have problems with this board that do.
Anyways your experience was entertaining to read nevertheless.
Obviously ppl who actually don't have problems with this board don't usually post here unless they're giving advice. It's the ppl who do have problems with this board that do.
Anyways your experience was entertaining to read nevertheless.
Well thanks for you help, you guys are the best!!
Well I finally tried those 7MB drivers and found the VIA SATA you were talking about. I put them in a disk and lord and nehold, windows finally saw it. Thank you.
No when It reboots to continue the setup i get thisfatal error i remember I got when I first installed windows on my ATA HD back in february. But I cant remember what I did to get past that error because I obviously did. I think and think of what I did to get past that and still cant remember. The error was something like 1894 ...cant recall, ill check tonight. Any ideas as to what it might be. If I am not mistaken i think i used my bros 2100 512mb stick because i have 2x 512LL XMA sticks and maybe it doesnt like them. But my girlfriend came over and didnt have a chance to continue until today when I get home. Hopefully by then, someone in here would have an idea or suggestion.
BTW, before i had the SATA driver, this board never gave me problems, so if people in here are reading complaints, I really didnt have any till this SATA thing, but then again, its my first so....
Anyways, thanks guys.
Well I finally tried those 7MB drivers and found the VIA SATA you were talking about. I put them in a disk and lord and nehold, windows finally saw it. Thank you.
No when It reboots to continue the setup i get thisfatal error i remember I got when I first installed windows on my ATA HD back in february. But I cant remember what I did to get past that error because I obviously did. I think and think of what I did to get past that and still cant remember. The error was something like 1894 ...cant recall, ill check tonight. Any ideas as to what it might be. If I am not mistaken i think i used my bros 2100 512mb stick because i have 2x 512LL XMA sticks and maybe it doesnt like them. But my girlfriend came over and didnt have a chance to continue until today when I get home. Hopefully by then, someone in here would have an idea or suggestion.
BTW, before i had the SATA driver, this board never gave me problems, so if people in here are reading complaints, I really didnt have any till this SATA thing, but then again, its my first so....
Anyways, thanks guys.
Ok i got home and wrote down the error i get when windows is gonna install after the reboot.
Error Instalation Failed\1386\asms
The Parameter is incorrect
Fatal Error
One of the components that windows needs to continue setup could not be installed.
The parameter is incorrect.
This happened to me like i said, back in february when I built my system, but I forgot what I did to get pass it. Please help.
I finally get the raptor to work, and now this.....OMG!
Error Instalation Failed
\1386\asmsThe Parameter is incorrect
Fatal Error
One of the components that windows needs to continue setup could not be installed.
The parameter is incorrect.
This happened to me like i said, back in february when I built my system, but I forgot what I did to get pass it. Please help.
I finally get the raptor to work, and now this.....OMG!
Woohoo! I remember what it was. The freakin CD drive gave me this error. I used the other drive and it worked, im glad I remembered.
Now to install all mobo drivers and XP updates etc.
One thing I noticed is that when I shut down windows, i get a "It is now ok to shut down your computer", and I have to push the power button on my case. Why? Before it would shutdown automatically, is it something to do with the SATA or what?
Also, its true i see barely to no HD light activity light. Can i now switch to the promise controller like you said, or since i installed windows on VIA, i have to stick with it?
Thanks again
Now to install all mobo drivers and XP updates etc.
One thing I noticed is that when I shut down windows, i get a "It is now ok to shut down your computer", and I have to push the power button on my case. Why? Before it would shutdown automatically, is it something to do with the SATA or what?
Also, its true i see barely to no HD light activity light. Can i now switch to the promise controller like you said, or since i installed windows on VIA, i have to stick with it?
Thanks again
I have the k8v SE deluxe with Athlon 64 3200+ also and had the same problem when upgrading to BIOS 1003 from 1001 using the alt f2 method (aka ASUS EZ Flash). I was also unable to boot up to recover the BIOS from a floppy or CD. My monitor was black - the only sign of life was the green LED on the mobo. I called ASUS BIOS support they sent out a new BIOS chip with 1003 - still no go. (this cost $40 for the express option). ASUS tech support suggested that the AFUDOS method is the safest wasy to upgrade - too late for me. My mobo combo is on its way back to the retailer for replacement.
The "It is now ok to shut down your computer" message may have to do with something else other than the SATA drive. Maybe updating Windows, installing drivers, etc. will fix it.
As for switching over from the VIA controller to the Promise. See if you can successfully install the Promise 378 "ATA Mode" drivers while the drive is connected/operating on the VIA controller.
I'll assume if you can then it's possible to switch over. However, I've personally never done this myself.
Well once again thanks for all your help guys! Finally got the SATA raptor working just right.
Now, I have 2 spare regualr ATA drives that I want to connect as slaves. How do I go about doing that, and what jumper settings do the drives need?(Slave both I assume right) And both connected to the primary IDE connecotr right? I tried that, and the ATA drives became the primary and the SATA wouldnt boot to XP because the ATA were there *+(with no OS in them) How can I make them slaves and boot of SATA drive?
Now, I have 2 spare regualr ATA drives that I want to connect as slaves. How do I go about doing that, and what jumper settings do the drives need?(Slave both I assume right) And both connected to the primary IDE connecotr right? I tried that, and the ATA drives became the primary and the SATA wouldnt boot to XP because the ATA were there *+(with no OS in them) How can I make them slaves and boot of SATA drive?
Maybe you can try the secondary PATA IDE channel or the Promise Controller's PATA channel.
P.S. Correct on setting both to slave AFAIK.
P.S. Correct on setting both to slave AFAIK.
Aye
The blue one is the Promise PATA channel and the black one parallel to the other blue one is the secondary PATA channel IIRC.
The blue one is the Promise PATA channel and the black one parallel to the other blue one is the secondary PATA channel IIRC.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter