Prev: BSOD in ksthunk.sys when attempting kernel streaming audio
Next: Romdump.com error on administrative logon
From: Tom Ferguson on 7 Dec 2006 18:33
Classic View, Control Panel Administrative Tools Computer
Management Disk Management

Does it show up there?

Tom
MSMVP
Windows Shell/User


"RomeoJ" <trailzman7(a)hotmail.com*n0_5pam*> wrote in message
news:953B7C88-8916-4184-B0B9-29053B1CD092(a)microsoft.com...
> Did some searching, found the nVidia drivers, and installed them. Got
> the
> RAID controller and the RAID array to show up in Device Manager. The
> array
> shows up as "NVIDIA STRIPE 465.77 GB" in Disk Drives. Still a no show
> in My
> Computer.
>
> Do I need to format the drives, or do something special to actually be
> able
> to use the array? It's working properly according to Device Manager

From: Noone on 7 Dec 2006 18:41
Yes. You have to go to disk manager and create a partition and then format
the drive before it will show up in "My Computer".
"RomeoJ" <trailzman7(a)hotmail.com*n0_5pam*> wrote in message
news:953B7C88-8916-4184-B0B9-29053B1CD092(a)microsoft.com...
> Did some searching, found the nVidia drivers, and installed them. Got the
> RAID controller and the RAID array to show up in Device Manager. The array
> shows up as "NVIDIA STRIPE 465.77 GB" in Disk Drives. Still a no show in
> My
> Computer.
>
> Do I need to format the drives, or do something special to actually be
> able
> to use the array? It's working properly according to Device Manager


From: Tony Sperling on 7 Dec 2006 18:59
Yes, I'm begining to realize that, and that in turn makes me realize that
perhaps the only responsibility the driver has is to attach the RAID
contrroller to the OS's SCSI subsystem! Data arriving at the controller will
see an ordinary drive in all circumstances, so should the OS - why SCSI?

It's a rethorical question, unless someone feels like throwing some light on
it.

I still don't know why this is a convenient way to handle this - just as I
have always wondered why 'burner' devices was hooked up to the SCSI
subsystem, it's a curious thing, but it will not keep me awake for very
long.


Tony. . .


From: RomeoJ on 7 Dec 2006 19:49
Thanks! Wasn't aware of compmgmt.crm - did the trick! Now, please check my
new thread on how to install the RAID drivers again during Windows install
from a CD.
From: Larry Hodges on 7 Dec 2006 21:22
Even onboard SATA controllers require the drivers. In his case, he's
probably talking SATA, not SCSI.

In my case, my Adaptec 39320 PCI controller was recognized by x64 and had
drivers on the install CD. I originally installed to a single disk. After
some time, I acquired some other drives, so I created a RAID0 array with two
Fujitsu 15k U320 drives using Adaptec's Storage Manager software from within
x64. I then used Norton Ghost to move my installation from the single drive
to the new array. Booted right up. I use the other 10k SCSI drive for data
storage and backups now.

Many here advise against RAID0 because of data loss potential. I back up to
DAT and HDD so that isn't an issue for me. And the performance increase is
striking...I'll risk it.

-Larry


"Tony Sperling" <tony.sperling(a)dbREMOVEmail.dk> wrote in message
news:eEAuPvlGHHA.1188(a)TK2MSFTNGP06.phx.gbl...
> Yes, I'm begining to realize that, and that in turn makes me realize that
> perhaps the only responsibility the driver has is to attach the RAID
> contrroller to the OS's SCSI subsystem! Data arriving at the controller
> will
> see an ordinary drive in all circumstances, so should the OS - why SCSI?
>
> It's a rethorical question, unless someone feels like throwing some light
> on
> it.
>
> I still don't know why this is a convenient way to handle this - just as I
> have always wondered why 'burner' devices was hooked up to the SCSI
> subsystem, it's a curious thing, but it will not keep me awake for very
> long.
>
>
> Tony. . .
>
>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: BSOD in ksthunk.sys when attempting kernel streaming audio
Next: Romdump.com error on administrative logon