Win7 and SATA drives

snip
Not exactly. The WDM has been completely redesigned in Server 2008, Windows
7 and Vista, where it first appeared. Hot connect is integrated into the
kernel and is transparent.
http://www.microsoft.com/whdc/archiv...vel-rebal.mspx

Are you saying with WIN7 I can plug in an external SATA drive on the fly
and it will be recongnized?

Yes.

Not for me. I have WIN7 PRO 64bit. I have to reboot to see it. My drive is
Calvary CAXE/CAM. Looking at the box it does say plug and play for Windows 20/XP/Vista.

It has both USB/SATA II interface. A USB it's plug an play as SATA it plug and reboot

Maybe I am missing a driver? Guess I needto do some research. Glad I saw this post.

Not for me. I have WIN7 PRO 64bit. I have to reboot to see it. My drive is
Calvary CAXE/CAM. Looking at the box it does say plug and play for Windows
20/XP/Vista.
It has both USB/SATA II interface. A USB it's plug an play as SATA it plug
and reboot

It's likely an issue with that specific drive. I see there's a review on
Newegg where that particular drive has no issues connecting as a USB mass
storage but eSATA mode did not work. My own personal experience is that
every eSATA and SATA device I have hot plugged into my Windows 7 64 systems
have all been recognized and functioned normally. Probably 20 different
devices and drives all told so far.

On 10/12/2009 in message
genious wrote:

snip
Not exactly. The WDM has been completely redesigned in Server 2008,
Windows
7 and Vista, where it first appeared. Hot connect is integrated into
the
kernel and is transparent.
http://www.microsoft.com/whdc/archiv...vel-rebal.mspx

Are you saying with WIN7 I can plug in an external SATA drive on the fly
and it will be recongnized?

Yes.

Not for me. I have WIN7 PRO 64bit. I have to reboot to see it. My drive is
Calvary CAXE/CAM. Looking at the box it does say plug and play for Windows
20/XP/Vista.

It has both USB/SATA II interface. A USB it's plug an play as SATA it plug
and reboot

Maybe I am missing a driver? Guess I needto do some research. Glad I saw
this post.

With internal drives you need to ensure they are set up as AHCI in the
BIOS for hot plugging to work. Many main boards default to legacy or IDE
mode for SATA drives as AHCI needs additional/different drivers. You may
need to change the BIOS setting for the e-SATA socket to AHCI.

If you want to experiment then Google AHCI/SATA before you do anything -
if you change the mode of your internal drives you could well end up with
a non-boot-able PC.

As somebody else has pointed can your try using 'reply to post' or 'reply
to group' in News Leecher, at the moment your replies are starting new
threads,

--
Jeff Gaines Dorset UK
It may be that your sole purpose in life is to serve as a warning to others.

On 10-Dec-2009, "Jeff Gaines" wrote:

With internal drives you need to ensure they are set up as AHCI in the
BIOS for hot plugging to work. Many main boards default to legacy or IDE
mode for SATA drives as AHCI needs additional/different drivers. You may
need to change the BIOS setting for the e-SATA socket to AHCI.

I have my OS drives in caddies, the BIOS and its settings is the same
for each OS. I abandoned USB because of corruption and because it's
speed is lower than SATA. Googling found that some add-on PCI USB
board chipsets are problematical.

My backup drive is on a timer, timer turns on, scheduled backup runs,
timer turns drive off. Drive only runs half an hour a day, and is off if the
system gets hosed by a virus. Just restore from image if that happens.

If the OS drive is XP it works as described, drive turns on, and appears,
backup runs, etc.

Not so if I slot Vista or Win7 drive into the OS C:\ caddy. Not that I
use Vista, for much publicised reasons. Its the same BIOS settings for
the caddies, it's the OS's that act differently to hot plugging eSATA.

Did the research, there is a MS utility called devcon, and the fact that
MS have produced devcon, shows they are aware that there is a need
for it. And what does devcon offer? It offers the switch /rescan.
So the command devcon /rescan runs, and the hot plugged eSATA
drive appears. A right pain in the butt to implement pre backup,
and just another example of how to write crap OS's. That's Win7
for you. Anything just out of warranty, off to landfill "no drivers".
MS "We don't write drivers" mfrs "We don't support products no
longer on sale".
One benefit of OS in a caddy is I can run Linux, that supports
pretty well everything, ancient and modern, why can't MS do the
same?

genious wrote:
snip
Not exactly. The WDM has been completely redesigned in Server 2008, Windows
7 and Vista, where it first appeared. Hot connect is integrated into the
kernel and is transparent.
http://www.microsoft.com/whdc/archiv...vel-rebal.mspx
Are you saying with WIN7 I can plug in an external SATA drive on the fly
and it will be recongnized?

Yes.

Not for me. I have WIN7 PRO 64bit. I have to reboot to see it. My drive is
Calvary CAXE/CAM. Looking at the box it does say plug and play for Windows 20/XP/Vista.

It has both USB/SATA II interface. A USB it's plug an play as SATA it plug and reboot

Maybe I am missing a driver? Guess I needto do some research. Glad I saw this post.

Two days ago I connected (USB2) a Seagate Free Agent External Drive to
my 32 bit Win 7. In about five seconds a message appeared saying that my
new hardware was ready to use. I opened Win Explorer, saw it was listed
as Drive K; clicked on it, looked at the contents and then checked
Properties. I was surprised that everything went right and rapidly.
Couldn't have been faster or easier.

By the way, I suggest that you Google Calvary hard drive; I saw mostly
negative posts in the one link I looked at.
Allen

On Thu, 10 Dec 2009 10:37:31 -0600, Allen
wrote:

genious wrote:
snip
Not exactly. The WDM has been completely redesigned in Server 2008, Windows
7 and Vista, where it first appeared. Hot connect is integrated into the
kernel and is transparent.
http://www.microsoft.com/whdc/archiv...vel-rebal.mspx
Are you saying with WIN7 I can plug in an external SATA drive on the fly
and it will be recongnized?

Yes.

Not for me. I have WIN7 PRO 64bit. I have to reboot to see it. My drive is
Calvary CAXE/CAM. Looking at the box it does say plug and play for Windows 20/XP/Vista.

It has both USB/SATA II interface. A USB it's plug an play as SATA it plug and reboot

Maybe I am missing a driver? Guess I needto do some research. Glad I saw this post.

Two days ago I connected (USB2) a Seagate Free Agent External Drive to
my 32 bit Win 7. In about five seconds a message appeared saying that my
new hardware was ready to use. I opened Win Explorer, saw it was listed
as Drive K; clicked on it, looked at the contents and then checked
Properties. I was surprised that everything went right and rapidly.
Couldn't have been faster or easier.

By the way, I suggest that you Google Calvary hard drive; I saw mostly
negative posts in the one link I looked at.
Allen

I have been unable to use eSATA and tried everything before I checked
with Intel and found out my motherboard does not support eSATA. I'm
stuck using USB for my external drives. I was totally surprised by
this information as I have a fairly recent motherboard (recent enough
that I'm running a quad core Pentium). The board is model DG33FB.

I have been unable to use eSATA and tried everything before I checked
with Intel and found out my motherboard does not support eSATA. I'm
stuck using USB for my external drives. I was totally surprised by
this information as I have a fairly recent motherboard (recent enough
that I'm running a quad core Pentium). The board is model DG33FB.

Get one of these from any computer store....it will allow one of the 4 SATA
mainboard connectors to be used to hook up an external eSATA enclosure. It
will be seen as a standard SATA internal drive. eSATA BIOS support not
required.
http://www.memoryexpress.com/Product...16430(ME).aspx

Shoe écrivait
:

snip

I have been unable to use eSATA and tried everything before I checked
with Intel and found out my motherboard does not support eSATA. I'm
stuck using USB for my external drives. I was totally surprised by
this information as I have a fairly recent motherboard (recent enough
that I'm running a quad core Pentium). The board is model DG33FB.

I thought eSATA was just a backplate you install in your computer case and
you connect on internal SATA connector. I have an eSATA connector installed
that way on my Win7 machine. When I click on the "Safely Remove" icon on
the taskbar, it list all SATA drives installed in that machine, internal or
external.

"Doum" wrote in message
...
Shoe écrivait
:

snip

I have been unable to use eSATA and tried everything before I checked
with Intel and found out my motherboard does not support eSATA. I'm
stuck using USB for my external drives. I was totally surprised by
this information as I have a fairly recent motherboard (recent enough
that I'm running a quad core Pentium). The board is model DG33FB.

I thought eSATA was just a backplate you install in your computer case and
you connect on internal SATA connector. I have an eSATA connector
installed
that way on my Win7 machine. When I click on the "Safely Remove" icon on
the taskbar, it list all SATA drives installed in that machine, internal
or
external.

IIRC, SATA needs to be configured properly in the BIOS to enable
hot-swapping. AHCI, or something to that effect.

"KCB" wrote in message
...

"Doum" wrote in message
...
Shoe écrivait
:

snip

I have been unable to use eSATA and tried everything before I checked
with Intel and found out my motherboard does not support eSATA. I'm
stuck using USB for my external drives. I was totally surprised by
this information as I have a fairly recent motherboard (recent enough
that I'm running a quad core Pentium). The board is model DG33FB.

I thought eSATA was just a backplate you install in your computer case
and
you connect on internal SATA connector. I have an eSATA connector
installed
that way on my Win7 machine. When I click on the "Safely Remove" icon on
the taskbar, it list all SATA drives installed in that machine, internal
or
external.

IIRC, SATA needs to be configured properly in the BIOS to enable
hot-swapping. AHCI, or something to that effect.

I have four SATA headers on my motherboard. Two of them are connected to
internal SATA drives and one of them connects directly to a backplate which
I have connected with an SATA to eSATA cable to an external drive. Those
three drives all show up in my bios as SATA drives. I do not know if they
are hot swappable as I have not attempted to disconnect my external 2TB
drive.

On Thu, 10 Dec 2009 16:10:41 GMT, "Ato_Zee"
wrote:

I have my OS drives in caddies, the BIOS and its settings is the same
for each OS. I abandoned USB because of corruption and because it's
speed is lower than SATA. Googling found that some add-on PCI USB
board chipsets are problematical.

My backup drive is on a timer, timer turns on, scheduled backup runs,
timer turns drive off. Drive only runs half an hour a day, and is off if the
system gets hosed by a virus. Just restore from image if that happens.

If the OS drive is XP it works as described, drive turns on, and appears,
backup runs, etc.

Not so if I slot Vista or Win7 drive into the OS C:\ caddy. Not that I
use Vista, for much publicised reasons. Its the same BIOS settings for
the caddies, it's the OS's that act differently to hot plugging eSATA.

Did the research, there is a MS utility called devcon, and the fact that
MS have produced devcon, shows they are aware that there is a need
for it. And what does devcon offer? It offers the switch /rescan.
So the command devcon /rescan runs, and the hot plugged eSATA
drive appears. A right pain in the butt to implement pre backup,
and just another example of how to write crap OS's. That's Win7
for you. Anything just out of warranty, off to landfill "no drivers".
MS "We don't write drivers" mfrs "We don't support products no
longer on sale".
One benefit of OS in a caddy is I can run Linux, that supports
pretty well everything, ancient and modern, why can't MS do the
same?

Write a small batch file that runs devcon, pauses for a few seconds if
necessary, then launches the backup program. Your scheduled task that
currently launches the backup would need to be changed to launch the
batch file instead. Problem solved?