Vista is truly a pile of dog crap when it comes to SATA drives

[Adam Albright]

Another hour wasted fighting with stupid Vista to get it to "see" a
SATA drive and it refuses. Truly Vista is not ready for prime time.

Consider how utterly stupid Vista can be.

1. I just installed the latest BIOS upgrade for my MB.

2. I installed the latest controller drivers as well.

3. I boot up, BIOS reports correctly the single
IDE drive I have installed and the 2 SATA
internal drives.

4. Vista reports it "see" new hardware and starts
to initialize the the SATA drives. It sees the
smaller 350 GB one and says it needs a reboot.

5. Vists reports it also "sees" my 750 GB SATA
drive starts to initialize it, but reports it
failed to load the driver, the very same one it
just did load to run the smaller 340 GB.

6. I look in Device Manager 2 IDE channels (not SATA)
have been added by Vista both duplicate channel assignments for
channel 0 and 1. My MB only has ONE IDE channel
a single master and slave, 0 and 1.

7. I look for my 750 GB drive in Windows Explorer, not showing.

8. I reboot. The 750 GB drive still doesn't show
but again Vista stupidly now adds a third set
of IDE channels, again 0 and 1. For those that may not be
aware the SATA drives are plugged into SATA channels on my
MB so Vista adding additional IDE channels is shere stupidity
on its part and makes absolutely no sense at all.

9. I go back to Device Manager and attempt to delete
the bogus IDE channels. As soon as I try, brain dead
Vista puts it right back. I try over and over, as soon as I'm
able to delete one bogus IDE channel, Vista again attempts to
reinstall it. No way to stop it.

Disgusted, I shut down, enter BIOS, disable all the advanced SATA
setting, put everything back to IDE mode and reboot. Immediately Vista
now "sees" my 750 GB drive and restores the IDE drivers for them. I
return to Device Manager the bogus IDE channels are now gone.

Now somebody try and tell me this isn't Microsoft's fault.

 

[Michael Jennings]

Vista knows that you are avoiding WinMail by using Forte Agent.
It is encouraging you to use a newsreader with a spelling checker.
Be a sport and start enduring WinMail. Maybe that will cheer Vista
up, and it will no longer need to not recognize your SATA drives.

 

[Adam Albright]

Vista knows that you are avoiding WinMail by using Forte Agent.
It is encouraging you to use a newsreader with a spelling checker.
Be a sport and start enduring WinMail. Maybe that will cheer Vista
up, and it will no longer need to not recognize your SATA drives.

Why would anybody aside from a green as grass newbie that don't know
any better use a piece of junk like WinMail?

 

[Richard Urban]

Looks like someone doesn't know what he is doing when it comes to the SATA
settings in his bios, doesn't it.

 

[Justin]

Vista knows that you are avoiding WinMail by using Forte Agent.
It is encouraging you to use a newsreader with a spelling checker.
Be a sport and start enduring WinMail. Maybe that will cheer Vista
up, and it will no longer need to not recognize your SATA drives.

Good one!

Dog crap? I agree, something sure smells coming from adams direction but I
doubt it's Vista!

Now sit back and wait for the spin

 

[Adam Albright]

Looks like someone doesn't know what he is doing when it comes to the SATA
settings in his bios, doesn't it.

Of course I expect typical smart ass comments from certain MVPs.

Learn how to read fella. I mean beyond the 4th grade level you
typically post at. If you would have, you would already know I DID
change the BIOS settings and I further told you the BIOS properly
reports the drives as SATA on the SATA controller and I see the AHCI
notice for SATA mode on a copywrite notice at boot which ONLY appears
when the BIOS is set to run with full SATA support.

Now don't you feel stupid Richie?

 

[Andyistic]

How about some information about your computer?
What kind of motherboard? What CPU? etc.

I have three SATA drives on my machine in addition to one PATA.
Please note that SATA drives are also IDE. IDE has nothing to do with
Parallel vs. Serial.
Vista recognizes all of them and I have no trouble working with any of the
drives.

It should also be noted that I use Outlook Express (now being called Windows
Mail for unknown reasons).
We need that hardware info - PRONTO!

-- Andy

 

[Justin]

Looks like someone doesn't know what he is doing when it comes to the SATA
settings in his bios, doesn't it.

Agreed. I'm running three SATA drives and an PATA drive. I had to tweak a
certain setting in my BIOS to force a NForce issue to go away.

I guess since I had a scanner that didn't work when XP was first released
and that made me a "dummy" by adams standards then what does that make him
not being able to get drives to work? Hehehe.

 

[Bill Condie]

<<I had to tweak a certain setting in my BIOS to force a NForce issue to go
away.

Tell us more. What setting, What issue?

 

[Michael Jennings]

Why would anybody aside from a green as grass newbie that don't know
any better use a piece of junk like WinMail?

Well, it don't have a grimmer check, but it do come with a spel write.
Andyistic uses it. You seem to be disinterested in his offer of assistance.
oop, you can't click on that link. Well, the post is here in the thread.

Ed Bott says we went through this before, when W95 came out:
http://blogs.zdnet.com/Bott/

 

[kirk jim]

The arrogance that made VISTA the crap it is, has overflown into the MVP's
and vista fanboys too...

 

[mikeyhsd]

here we go again.
anyone else want to agree with his nomination to NUMBER ONE WHINER.




(e-mail address removed)



Another hour wasted fighting with stupid Vista to get it to "see" a
SATA drive and it refuses. Truly Vista is not ready for prime time.

Consider how utterly stupid Vista can be.

1. I just installed the latest BIOS upgrade for my MB.

2. I installed the latest controller drivers as well.

3. I boot up, BIOS reports correctly the single
IDE drive I have installed and the 2 SATA
internal drives.

4. Vista reports it "see" new hardware and starts
to initialize the the SATA drives. It sees the
smaller 350 GB one and says it needs a reboot.

5. Vists reports it also "sees" my 750 GB SATA
drive starts to initialize it, but reports it
failed to load the driver, the very same one it
just did load to run the smaller 340 GB.

6. I look in Device Manager 2 IDE channels (not SATA)
have been added by Vista both duplicate channel assignments for
channel 0 and 1. My MB only has ONE IDE channel
a single master and slave, 0 and 1.

7. I look for my 750 GB drive in Windows Explorer, not showing.

8. I reboot. The 750 GB drive still doesn't show
but again Vista stupidly now adds a third set
of IDE channels, again 0 and 1. For those that may not be
aware the SATA drives are plugged into SATA channels on my
MB so Vista adding additional IDE channels is shere stupidity
on its part and makes absolutely no sense at all.

9. I go back to Device Manager and attempt to delete
the bogus IDE channels. As soon as I try, brain dead
Vista puts it right back. I try over and over, as soon as I'm
able to delete one bogus IDE channel, Vista again attempts to
reinstall it. No way to stop it.

Disgusted, I shut down, enter BIOS, disable all the advanced SATA
setting, put everything back to IDE mode and reboot. Immediately Vista
now "sees" my 750 GB drive and restores the IDE drivers for them. I
return to Device Manager the bogus IDE channels are now gone.

Now somebody try and tell me this isn't Microsoft's fault.

 

[Adam Albright]

How about some information about your computer?
What kind of motherboard? What CPU? etc.

Repeating... Gigabyte GA-965P-DQ6. Note on their web site this is
suppose to be a "Vista Certified" board. The CPU is a Intel Duo Core 2
6400. Running with the lastest BIOS and drivers.

Vista recognizes all of them and I have no trouble working with any of the
drives.

As I said this is a odd situation. I have 2 internal SATA drives in
this setup. They are both Seagate. Without repeating the details Vista
accepts the smaller drive and will run it as a SATA however the larger
goes through what I detailed in my earlier post.

Now the funny part is if I remove both SATA drives, then reboot only
installing the larger, the very same one that Windows refuses to see
when with the small drive then Vista sees this larger drive perfectly
ok and will run it as a SATA. However rebooting again and returning
the smaller drive when the larger is already there so I now have 2
SATA drives the same problem happens only the smaller drive isn't
seen.

Now for those that may be thinking this could be master/slave issue,
no it isn't. SATA drives do not have that configuration. There are no
jumper to change. Each device simply runs on one of the 8 SATA
channels I have on the MB. This sure doesn't seem to be a BIOS issue,
since no matter how I configure the drives they do show up listed
correctly on the BIOS screen at boot that does show the status of all
IDE devices, all IRQ lines and what if anything is connected to the 8
SATA channels. So this is seems to be something Windows is messing up.

Of course what pisses me off is some smartass useless MVP that's
obviously as dumb as a stump trying to be cute and telling me and
others we don't know what we're doing. That isn't what MVP are suppose
to be here for.

 

[Zim Babwe]

I enjoy the banterings between Adam, Richard, Justin, and Kirk. Keep it up
boys!

 

[Adam Albright]

Agreed.

Not surprising that two of this newsgroup's biggest MORONS agee. My
little finger knows more about computers then the two of you combined.

 

[Adam Albright]

Well, it don't have a grimmer check, but it do come with a spel write.
Andyistic uses it. You seem to be disinterested in his offer of assistance.
oop, you can't click on that link. Well, the post is here in the thread.

Ed Bott says we went through this before, when W95 came out:
http://blogs.zdnet.com/Bott/

I see NOTHING even remotely related to the problem I reported.
Hint: SATA drives weren't even around in Windows 95 era.

 

[Adam Albright]

here we go again.
anyone else want to agree with his nomination to NUMBER ONE WHINER.

This perfectly illustrates some poster's maturity level when somebody
takes the time to document real problems with Vista. Clowns like you
simply don't want to know about them. Just like these other monkeys:

http://members.aol.com/unclechris1957/images/29586 see hear speak no evil monkey totem.jpg

 

[Justin]

here we go again.
anyone else want to agree with his nomination to NUMBER ONE WHINER.

YES! He seems to think he's the best thing that ever happened to this NG.
It's no surprise that a flood of people aren't rushing to help him. After
all, he's called just about everyone in this NG a dummy, child and a waste
of time. Among many other things.

Even the one person that is willing to help him, he treats with disrespect.
Andyistic rightfully requested more info about his system. adams reply?
"Repeating... " Then he gives information he never mentioned in the OP.

What a class act!

 

[Andyistic]

If someone's reply to you doesn't provide you with information you can use,
ignore it.
Anyone can reply on this newsgroup. Some will have intelligent comments,
others just nonsense.
It's been like this since newsgroups were started ages ago. Just more of it
these days.

Let's look at the BIOS first: I had a cornocopia of problems whenever I
tried using the JMicron interface.
I don't know why they even bothered installing that onto the motherboard -
it's a total waste.
Needless to say, I won't try to use it again - in my BIOS, it's disabled.

This means I am left with the Intel SATA chipset ICH7R.
This puppy has three modes - Standard, Enhanced (using SATA2 extensions),
and RAID.
I got best results with the Standard mode, especially having an older PATA
included.
If your motherboard has an ICH7R (or similar), I suggest putting each SATA
drive onto the each of the two master channels and not using the slave
connections.
Make sure your BIOS is set for Standard. After you do this, both drives
should appear in the list.

If you have Windows XP installed, boot up into that and see if XP works
properly.
If it does, you can try using the same XP drivers for Vista.
If not, then remove the drivers (in Vista), and try the "Look online"
feature to find drivers from Microsoft's repository on their remote server.
If this doesn't work, contact Seagate and describe the problem.

I recommend using a speakerphone when contacting tech support as the wait to
talk to a real live person can be tedious, and it's much easier to have the
phone resting on the table while doing other things.

Let me know how it goes.

-- Andy (Not necessarly an MVP)

 

[Adam Albright]

YES! He seems to think he's the best thing that ever happened to this NG.
It's no surprise that a flood of people aren't rushing to help him. After
all, he's called just about everyone in this NG a dummy, child and a waste
of time. Among many other things.

Even the one person that is willing to help him, he treats with disrespect.
Andyistic rightfully requested more info about his system. adams reply?
"Repeating... " Then he gives information he never mentioned in the OP.

What a class act!

You truly are a world class dummy. Justin is king of the dummies and
daily needs to reprove it.

I can quickly seperate the samrtass posters (like you) from the people
actually wishing and needing help. I do try and have helped them which
is the only reason I bother visiting this group.

You confuse confidence and experience with the typical wannabe types
that post here to merely stroke their already bloated egos. Many of
those type have MVP behind their name. Like you Justin, clowns like
deserve and receive the back of my hand.