Sandman
What developer were you talking to when you said:

"I know you can set a back-up protocol to back up multiple drives, but the one-drive system works for most people."

Because now you're saying that the only protocol present in an automated backup is the one defined by the developer, yet above you were talking to Noelle about her being able to set up a "back-up protocol", but she's not a developer of backup systems as far as I'm aware...

Tony Cooper
No, I didn't say that. There's no "only" implied or expressed.

The developer's backup protocol can include the ability to add user-defined steps. One such step is to backup on multiple drives.

And the user adds his own protocol requirements of frequency and destination to the backup protocol of the developer.

Sandman
So clicking a button is now "adding his own protocol"?

Tony Cooper
Jesus! You are completely devoid of reading comprehension ability. I didn't say you "add a protocol". You add protocol *requirements*. The requirements are part of the protocol.

Sandman
Even in the cases where you can determine frequency, you would call clicking a popup and choosing "hourly" (for instance) that the user is "adding his own protocol"?

Tony Cooper
Not as you wrote is, but Yes if you had the ability and smarts to form the statement in line with what I've said. When you click the popup to choose the frequency, you are adding a protocol requirement. Not a protocol, but a step that is a requirement in the protocol.

I can't figure out if you are hampered in your understanding by language, intellectual capacity, or inability to process what you read.

You have so far not demonstrated any understanding of what a "protocol" is.

You seem to think that any step in a process is a protocol.

The protocol is the defined *series* of steps that will be done every time the task is initiated.