XYplorer Beta Club

As part of the original use case for verification, it would be great if Custom Copy could distinguish between local HD's on the one hand, and portable and network drives on the other. For operations on/between local HD's, verification is superfluous to me, whereas I do value it when working with portable and network drives.

Would it be possible to extend Custom Copy to enable or disable it for different drive types?

nas8e9 wrote:As part of the original use case for verification, it would be great if Custom Copy could distinguish between local HD's on the one hand, and portable and network drives on the other. For operations on/between local HD's, verification is superfluous to me, whereas I do value it when working with portable and network drives.

Would it be possible to extend Custom Copy to enable or disable it for different drive types?

The problem is that I don't know a way to safely distinguish between HDs and SSDs (removable flash drives).

admin wrote:

nas8e9 wrote:As part of the original use case for verification, it would be great if Custom Copy could distinguish between local HD's on the one hand, and portable and network drives on the other. For operations on/between local HD's, verification is superfluous to me, whereas I do value it when working with portable and network drives.

Would it be possible to extend Custom Copy to enable or disable it for different drive types?

The problem is that I don't know a way to safely distinguish between HDs and SSDs (removable flash drives).

Going by the types supported by the drive variable of the <get drives>-command, I'd only want to distinguish between DRIVE_FIXED and all other types.

I'm not sure what you mean by SSD's: I'm guessing that, provided they hang off a SATA controller, they are considered fixed by Windows and to my mind, should be treated as such. Also, the extra operation (verification) is a read operation, so additional wear isn't a consideration.

Distinguishing between Flash drives (which are distinct from SSD's in connection (USB vs. SATA) and performance) and external HD's (which should be as reliable as internal HD''s), might be useful, but I could live with both external drive types always being verified.

nas8e9 wrote:

admin wrote:

nas8e9 wrote:As part of the original use case for verification, it would be great if Custom Copy could distinguish between local HD's on the one hand, and portable and network drives on the other. For operations on/between local HD's, verification is superfluous to me, whereas I do value it when working with portable and network drives.

Would it be possible to extend Custom Copy to enable or disable it for different drive types?

The problem is that I don't know a way to safely distinguish between HDs and SSDs (removable flash drives).

Going by the types supported by the drive variable of the <get drives>-command, I'd only want to distinguish between DRIVE_FIXED and all other types.

I'm not sure what you mean by SSD's: I'm guessing that, provided they hang off a SATA controller, they are considered fixed by Windows and to my mind, should be treated as such. Also, the extra operation (verification) is a read operation, so additional wear isn't a consideration.

Distinguishing between Flash drives (which are distinct from SSD's in connection (USB vs. SATA) and performance) and external HD's (which should be as reliable as internal HD''s), might be useful, but I could live with both external drive types always being verified.

OK, that's easy (and makes sense).

Just to note, it's been my experience that many portable external hard drives still show up as fixed instead of removable. It's related to how it is configured but the details escape me right now.

Don't think that would really have much of an impact on what you're talking about but FYI.

TheQwerty wrote:Just to note, it's been my experience that many portable external hard drives still show up as fixed instead of removable. It's related to how it is configured but the details escape me right now.

Don't think that would really have much of an impact on what you're talking about but FYI.

Thanks for the info. I made a note in the Help file.