• cheap usb ("thumb") drives

    From Don Y@21:1/5 to All on Wed Nov 29 12:22:09 2023
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Wed Nov 29 19:45:18 2023
    XPost: free.spam

    The idiot Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: cheap usb ("thumb") drives
    Date: Wed, 29 Nov 2023 12:22:09 -0700
    Organization: A noiseless patient Spider
    Lines: 16
    Message-ID: <uk8317$v4vl$1@dont-email.me>
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Wed, 29 Nov 2023 19:22:16 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="b1f386679152db9955f0ef760cfec86e";
    logging-data="1020917"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/3qsYFYxoRsMrwr6zGYjBc"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:7+6lewxtGlUQSGNvZsnq1tnDcgM=
    Content-Language: en-US
    X-Received-Bytes: 1617

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From whit3rd@21:1/5 to Don Y on Wed Nov 29 14:42:41 2023
    On Wednesday, November 29, 2023 at 11:22:23 AM UTC-8, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?

    The USB protocol only identifies 'mass storage device' characteristics, not read/write permissions. Any permission mechanism isn't standard (might
    work only on one filesystem type, or one vendor's mark 3 control model...).

    You'd be better off using SD card (maybe plugging an SDcard micro module
    into a $0.79 USB reader), because the SD card specs DO include
    write locking by a number of mechanisms, some hardware and some software.
    Also, naturally, you'd want a checksum or hash that can be checked
    against the contents of any pretender to legitimacy...

    <https://www.temu.com/high-speed-usb2-0-card-reader-miniature-compact-mobile-phone-memory-card-portable-card-reader-gift-for-birthday-easter-presidents-day-boy-girlfriends-g-601099514249377.html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Don Y on Thu Nov 30 00:24:05 2023
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?


    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.


    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dan Purgert on Wed Nov 29 18:33:23 2023
    On 11/29/2023 5:24 PM, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    They bring the box back to us to be "fixed". This is why I built
    the restore partition hack. (they are underprivileged youth)

    Previously, they would routinely bring their machines in loaded
    with malware, porn, etc. and want us to fix it. Technicians would
    make a serious attempt to try to recover all of their "user files".

    [This was a colossal waste of effort/staff. I was able to persuade
    the powers-that-be that a more automatic method would be to OUR
    benefit.]

    With the "reboot and select RESTORE" solution, it tells them that
    their loss is THEIR loss. Even if they bring a machine in, we
    just "reboot and select RESTORE" -- very *visibly* for them to
    see (i.e., you just wasted a trip to the shop cuz you didn't
    walk away with anything more than you would have if you'd done
    this, yourself).

    A windows upgrade (attempt) hoses my restore utility so they
    have an excuse to bring the machine back -- though we still
    just reinstall from scratch, letting all their stuff disappear.

    We would like NOT to have to spend our time doing this. A few
    bucks for a "restore thumb drive" is a small price to pay (we
    will likely find someone to underwrite the cost of those).

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    If I knew that they would always be running the installed OS,
    I could hack the VID/PID and force a bogus driver for THAT
    thumb drive. But, they could always bring the drive to a "foreign"
    machine that doesn't have this hack in place and overwrite it, there.

    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    At least one of the "failed in R/O mode" drives mentioned above failed
    before it had been completely written, *once*. Costco replaced it
    (but insisted on having the other two drives that came in the three-pack
    so they could just give me a new, complete, three-pack in replacement).

    I've also a few thumb drives, here, that have developed mechanical
    faults -- it seems like the portion in the connector shell "breaks"
    from the rest of the body (though not enough to become two pieces;
    it just "bends" at that joint... enough to make an intermittent).

    But, my usage likely won't mimic theirs -- esp if I can make it R/O
    ("Just put the thumb drive someplace for safe keeping TO SAVE *YOU*
    A TRIP if you need a restore")

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Dan Purgert on Thu Nov 30 02:24:04 2023
    XPost: free.spam

    The idiot Dan Purgert <dan@djph.net> persisting in being an Off-topic troll...

    --
    Dan Purgert <dan@djph.net> wrote:

    Path: not-for-mail
    From: Dan Purgert <dan@djph.net>
    Newsgroups: sci.electronics.design
    Subject: Re: cheap usb ("thumb") drives
    Date: Thu, 30 Nov 2023 00:24:05 -0000 (UTC)
    Organization: A noiseless patient Spider
    Lines: 30
    Message-ID: <slrnumflkc.v1f.dan@djph.net>
    References: <uk8317$v4vl$1@dont-email.me>
    Injection-Date: Thu, 30 Nov 2023 00:24:05 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="bdc08d3977848adc40ee6d5c48a929ca";
    logging-data="1107957"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19AzKGMJjoKas0MW0GEScBVRQWU4w10TnM="
    User-Agent: slrn/1.0.3 (Linux)
    Cancel-Lock: sha1:C7xs9WDDpccsGFJLcPNlMnswu7o=
    X-Received-Bytes: 1919

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From a a@21:1/5 to Don Y on Thu Nov 30 02:24:10 2023
    XPost: free.spam

    The arsehole Don Y <blockedofcourse@foo.invalid> persisting in being an Off-topic troll...

    --
    Don Y <blockedofcourse@foo.invalid> wrote:

    Path: not-for-mail
    From: Don Y <blockedofcourse@foo.invalid>
    Newsgroups: sci.electronics.design
    Subject: Re: cheap usb ("thumb") drives
    Date: Wed, 29 Nov 2023 18:33:23 -0700
    Organization: A noiseless patient Spider
    Lines: 70
    Message-ID: <uk8opa$12d92$2@dont-email.me>
    References: <uk8317$v4vl$1@dont-email.me> <slrnumflkc.v1f.dan@djph.net> MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit
    Injection-Date: Thu, 30 Nov 2023 01:33:31 -0000 (UTC)
    Injection-Info: dont-email.me; posting-host="4e7ef51c610ba137e6aac80b361fc094";
    logging-data="1127714"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/66RX36hNZZrgi/dERo9nC"
    User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
    Thunderbird/102.2.2
    Cancel-Lock: sha1:NCJl7ZKJKlNXAfZhEWNywOWciJk=
    Content-Language: en-US
    In-Reply-To: <slrnumflkc.v1f.dan@djph.net>
    X-Received-Bytes: 4421

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jan Panteltje@21:1/5 to blockedofcourse@foo.invalid on Thu Nov 30 05:48:14 2023
    On a sunny day (Wed, 29 Nov 2023 12:22:09 -0700) it happened Don Y <blockedofcourse@foo.invalid> wrote in <uk8317$v4vl$1@dont-email.me>:

    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    I bought a cheap 1 TB USB stick, it lasted a few weeks.
    Opening it up I found that the PCB had pads for input protection parts
    none were fitted.

    OTOH I have an old 'Duracell' 16 GB USB stick that is still fine after more than 20 years daily use.

    As to write protectioon, no way, one can always do a dd if=/dev/zero of=/dev/USBSTICK if one wants to.
    Old SDcards had a mechanical switch, glue it? LOL

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Layman@21:1/5 to Don Y on Thu Nov 30 09:02:09 2023
    On 29/11/2023 19:22, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    <https://www.computerhope.com/issues/ch001617.htm>

    If you've got something "mission critical" it might be best to avoid a
    cheap drive. If you buy a cheap 32GB drive, perhaps it's a "failed" 64GB
    drive. Is the 32GB you've got left reliable?

    --

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From none) (albert@21:1/5 to dan@djph.net on Thu Nov 30 11:47:05 2023
    In article <slrnumflkc.v1f.dan@djph.net>, Dan Purgert <dan@djph.net> wrote: >On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?


    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    I installed a backup mechanism to copy daily backups to a thumb drive.
    That failed after 6 months or so. The thumb drive is no more
    recognized at all to normal usb software not even as a device.

    So repetitive writing is a bad idea. (The backups were instead
    copied to the mount directories. So they were there.
    It was the idea to have the backups on a different medium.
    Now I write to a different hard drive in the same machine.)

    --
    |_|O|_|

    Groetjes Albert
    --
    Don't praise the day before the evening. One swallow doesn't make spring.
    You must not say "hey" before you have crossed the bridge. Don't sell the
    hide of the bear until you shot it. Better one bird in the hand than ten in
    the air. First gain is a cat spinning. - the Wise from Antrim -

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Dan Purgert on Thu Nov 30 10:53:36 2023
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people break
    USB sticks off (more often TV tuners) leaving part of the thing still in
    the machine. This can be terminal for the USB socket too.

    If it writes and verifies OK then it should be good for quite a few
    reads if it is looked after. Longevity might be an issue longer term so
    not in the sun and kept cool and dry would make sense. I have had the
    odd really cheap and nasty one croak on first use but it is rare.

    Leave it in a machine shop full of metal swarf and all bets are off!

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Martin Brown on Thu Nov 30 11:03:47 2023
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place
    selling refurbished machines. So if the buyer hoses their box, it's not directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Wasn't til his first or second response that he said the "clients" are
    kids (in which case ... "is it the school's property, or ... what?")

    [...]
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people break
    USB sticks off (more often TV tuners) leaving part of the thing still in
    the machine. This can be terminal for the USB socket too.

    Well sure. But "destroyed via misuse" is a far sight different than "it
    just fell apart" (which I've not seen -- even in my cheapo "Microcenter" branded ones)


    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dan Purgert on Thu Nov 30 05:01:14 2023
    On 11/30/2023 4:03 AM, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place
    selling refurbished machines. So if the buyer hoses their box, it's not directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Ah, so, in your mindset, it's perfectly fine for a "supplier" to
    screw over his customers? "Not my problem!"

    Do you take the same attitude with your *designs*: "*I* hae
    been paid so any problems henceforth are the client's!"

    Wasn't til his first or second response that he said the "clients" are
    kids (in which case ... "is it the school's property, or ... what?")

    It was my second post -- first response.

    And, again, why would you ever think it's NOT a supplier's
    problem to ensure he supplies a quality product?

    No, it's not the school's property. These are just individuals (underprivileged youth who can't afford to BUY a computer;
    does that mean they can be screwed over because they haven't
    made any cash outlay?) being serviced by a non-profit. Just
    as if they'd PURCHASED a machine, from a store, they would expect
    to return to that store (for support) if they had a problem.

    In the past, we have been too generous with our (volunteer) time
    in trying to restore machines that had been grossly misused;
    investing hours to recover files from horribly infected/corrupted
    disks. (should we also have just said "not our problem"? How
    does that serve those youth?)

    My approach has reshifted the balance of responsibility to
    the clients -- if you misuse YOUR computer, you risk losing
    YOUR files. The only remedy that we can offer you is to restore
    the computer to the state that it was WHEN WE GAVE IT TO YOU.
    And, hey, look: we'll give YOU the ability to do that so
    you don't have to take the bus to our shop for that repair!
    Aren't we incredibly supportive?!

    [...]
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people break
    USB sticks off (more often TV tuners) leaving part of the thing still in
    the machine. This can be terminal for the USB socket too.

    Well sure. But "destroyed via misuse" is a far sight different than "it
    just fell apart" (which I've not seen -- even in my cheapo "Microcenter" branded ones)

    For our market, it wouldn't matter. Do we get all holier-than-thou and
    tell the (underprivileged youth) client that he's not taken good enough
    care of his computer so we aren't going to help him? What if he breaks
    the keyboard? Screen? Do we "charge" him (underprivileged youth) for
    the repair? (he couldn't afford to BUY the machine but he *can* afford
    to pay for its repair?)

    These sorts quickly learn how to manipulate the system; so you have
    to design "rules" that discourage that:

    "Gee, *so* sorry to see you broke the screen on your laptop.
    But, leave it with us and we'll get it back to you in a FEW WEEKS
    (free of charge) once we've been able to repair it."

    "Can't you just give me a replacement laptop?"

    "Sorry, no (cuz you would then treat each laptop we've given you
    as disposable, knowing any problems will get you a replacement!)."

    "But, you USED TO just give replacements..."

    "Yeah, but we no longer have as many laptops available to be able to
    be able to just DISCARD broken ones...like yours"

    Then, with (some) of the costs for their actions born by them,
    there is a chance they will think twice before engaging in
    similar conduct.

    [Another nonprofit used to offer subsidies to youth. They
    quickly learned that if they wanted money to buy something that
    the group didn't have on hand, they could get a gift certificate
    to one of the local department stores. Of course, their need
    couldn't be for something frivolous (game console?). So, all
    sorts of kids would come in claiming to need *underwear*...
    and, walking out with a gift certificate. No way to track
    HOW that was actually used so no way to close the loop.
    Unless you decide to *stock* underwear: "Hmmm, what size
    are you? And, how many would you like?" Suddenly, kids
    had no overwhelming need for underwear...]

    [[Still other nonprofits will blindly honor their demands and
    use that to justify asking their donors for more money! "We
    had 217 requests for underwear; your donation will help put
    clothing on these poor kiddies bottoms!"]]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Thu Nov 30 05:15:36 2023
    On 11/30/2023 3:53 AM, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    If your (paying) customer trashes the item he BOUGHT from you,
    do you tell him to go suck eggs because he mistreated it?
    How much responsibility can he heap on you for creating a
    product that was so EASILY mistreated?

    Even if you refuse to comp him for his losses, do you, also,
    refuse to do any further business with him?

    When your customer doesn't give you monies for your product,
    the dynamics change! ("You've been a bad boy! We're going to
    cut our ties to you...")

    - Can I make a thumb drive "read only" prior to distribution?
        (so the little urchins don't wipe the installer image)  I've
        encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives?  (can I get a handful
        of *reliable* reads without worrying about a media error
        or mechanical failure)

    Pretty durable.  It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people break USB sticks off (more often TV tuners) leaving part of the thing still in the machine. This can be terminal for the USB socket too.

    If it writes and verifies OK then it should be good for quite a few reads if it
    is looked after.

    "Looked after" is a problem. The beauty of the restore partition was that
    they didn't have to *do* anything to have it available. The thumb drive will require them to keep it on hand... somewhere.

    OTOH, if they misplace it, then THEY are inconvenienced as they will have
    to bring the machine into the shop. On public transportation. Time that
    they could have used for some other purpose (essential or recreational).

    I was hoping the drives could be made non-reusable (R/O) to eliminate
    their being used/traded/sold for purposes other than as THEIR backup:

    "I lost my thumb drive; can I have another?"

    "OK, I'll put in a work order to have one made for you. What's
    your machine's serial number (so we can look up the correct
    image to place on the drive for YOUR machine)? Oh, you don't have
    that handy? Well, get back to us when you do..."

    Longevity might be an issue longer term so not in the sun and
    kept cool and dry would make sense. I have had the odd really cheap and nasty one croak on first use but it is rare.

    Leave it in a machine shop full of metal swarf and all bets are off!

    Many of these kids don't have permanent places to *sleep* (let alone LIVE).
    So, everything that they have to keep track of is a challenge. Our GOAL
    isn't to make their life any harder. OTOH, *they* should assume responsibility for maintaining their improved quality of life and not just ASSUME that
    we'll forever be accommodating their LACK of responsibility.

    We used to give out SFF desktop machines. But, that was limited to
    kids who had a place to SET UP such a machine!

    And, if their living arrangements (inevitably "temporary") changed,
    the machine could get lost (left behind) in the "move".

    Or, *sold*... even $10 is a win if the machine didn't cost you anything
    AND if you think you can get another, for free!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Dan Purgert on Thu Nov 30 13:31:09 2023
    On 30/11/2023 11:03, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:

    [...]
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people break
    USB sticks off (more often TV tuners) leaving part of the thing still in
    the machine. This can be terminal for the USB socket too.

    Well sure. But "destroyed via misuse" is a far sight different than "it
    just fell apart" (which I've not seen -- even in my cheapo "Microcenter" branded ones)

    I recall having one fall apart on me - a cheap and nasty one but it was
    very much a one off and it might have been provoked by previous bad
    handling by the owner. It had some battle scars shall we say...

    Unlike a Fluke multimeter they don't take kindly to being driven over!

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to John Walliker on Thu Nov 30 06:25:36 2023
    On 11/30/2023 5:49 AM, John Walliker wrote:
    On Thursday, 30 November 2023 at 12:15:54 UTC, Don Y wrote:

    Or, *sold*... even $10 is a win if the machine didn't cost you anything
    AND if you think you can get another, for free!

    Some USB sticks can be very reliable. I recently tested a Samsung FIT+ 128Gbyte drive by writing data to it, reading it back and verifying continuously for a few weeks using superspeed mode. (The objective
    was actually to test the superspeed interface rather than the flash.)
    There were no errors.

    I wouldn't doubt it. But, there is likely a direct relationship
    between cost and quality (with exceptions). The thumb drive isn't
    intended to see much use (goal: zero!) so read performance isn't
    a driving force (I can reinstall an image in just a few minutes;
    no need to do a real/slow "install"). This should let us drive
    down the cost of the drive *and* make the drives less valuable
    as possible resale items:
    "Where is your restore drive?"
    "I lost (sold!) it..."

    Our goals are:
    - don't significantly increase our costs (passed on to donors)
    - ensure it's continued availability (i.e., not overwritten!)
    - don't "tempt" the clients (by providing something that has
    other value that they could exploit to OUR detriment)

    If laptops had internal USB slots (like many servers), that
    would be the ideal spot to install it.

    I've lost *one* thumbdrive to malfunction (going R/O). But,
    I have noticed that write speed seems to suffer with more
    frequent writes.

    I had initially advocated for having the kids store "their"
    files on thumb drives so there was no risk of losing anything
    on the disk drive if (when!) it is restored from a backup.
    This seemed idea as it also broke the reliance on a particular
    computer (i.e., their files could be portable).

    In practice, this didn't work because of degradation in the
    thumb drives.

    So, now I have a second partition ("D:") that they are intended
    to use as persistent storage. *If* they don't munge the disk
    (like trying to install an OS upgrade), then I can restore their
    "system" partition and their user files will be right where
    they left them.

    Again, you want to serve THEIR needs but without increasing
    YOUR costs (time/effort/donations) in the process.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to albert on Thu Nov 30 06:32:34 2023
    On 11/30/2023 3:47 AM, albert wrote:
    In article <slrnumflkc.v1f.dan@djph.net>, Dan Purgert <dan@djph.net> wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?


    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    Pretty durable. It's the writes that wear out the flash / cause it to
    fail.

    I installed a backup mechanism to copy daily backups to a thumb drive.
    That failed after 6 months or so. The thumb drive is no more
    recognized at all to normal usb software not even as a device.

    Presumably, exceeded the write wear limit. (many are in the 10K and lower range, depending on technology). This was something you quickly
    learned when using FLASH (and other non-volatile technologies that
    predated it) for parameter storage: "No, you don't want to
    update the store every time the user makes a change because he
    can (effectively) make a lot of changes in a very short time!"

    But, any idea as to why the drive wasn't *recognized*? I'd assume
    a controller *in* the drive could at least respond to the initial
    probe, even if the media is hosed.

    Likewise, why did the one example I cited "go R/O" instead of
    simply dying? (How did it KNOW that it could no longer
    write to the flash? And, why was the failure for ALL of
    the flash instead of just bad blocks??)

    So repetitive writing is a bad idea. (The backups were instead
    copied to the mount directories. So they were there.
    It was the idea to have the backups on a different medium.
    Now I write to a different hard drive in the same machine.)

    I just push the stuff that I want backed up onto some other
    machine on the network. As that target can vary, it makes hunting
    for backups a bit of a challenge -- but, one that isn't
    encountered often!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to Don Y on Thu Nov 30 13:54:39 2023
    Don Y <blockedofcourse@foo.invalid> wrote:
    On 11/30/2023 5:49 AM, John Walliker wrote:
    On Thursday, 30 November 2023 at 12:15:54 UTC, Don Y wrote:

    Or, *sold*... even $10 is a win if the machine didn't cost you anything
    AND if you think you can get another, for free!

    Some USB sticks can be very reliable. I recently tested a Samsung FIT+
    128Gbyte drive by writing data to it, reading it back and verifying
    continuously for a few weeks using superspeed mode. (The objective
    was actually to test the superspeed interface rather than the flash.)
    There were no errors.

    I wouldn't doubt it. But, there is likely a direct relationship
    between cost and quality (with exceptions). The thumb drive isn't
    intended to see much use (goal: zero!) so read performance isn't
    a driving force (I can reinstall an image in just a few minutes;
    no need to do a real/slow "install"). This should let us drive
    down the cost of the drive *and* make the drives less valuable
    as possible resale items:
    "Where is your restore drive?"
    "I lost (sold!) it..."

    Our goals are:
    - don't significantly increase our costs (passed on to donors)
    - ensure it's continued availability (i.e., not overwritten!)
    - don't "tempt" the clients (by providing something that has
    other value that they could exploit to OUR detriment)

    If laptops had internal USB slots (like many servers), that
    would be the ideal spot to install it.

    I've lost *one* thumbdrive to malfunction (going R/O). But,
    I have noticed that write speed seems to suffer with more
    frequent writes.

    I had initially advocated for having the kids store "their"
    files on thumb drives so there was no risk of losing anything
    on the disk drive if (when!) it is restored from a backup.
    This seemed idea as it also broke the reliance on a particular
    computer (i.e., their files could be portable).

    In practice, this didn't work because of degradation in the
    thumb drives.

    So, now I have a second partition ("D:") that they are intended
    to use as persistent storage. *If* they don't munge the disk
    (like trying to install an OS upgrade), then I can restore their
    "system" partition and their user files will be right where
    they left them.

    Again, you want to serve THEIR needs but without increasing
    YOUR costs (time/effort/donations) in the process.



    If your laptops have full size SD card slots, you could use micro-SDs with adapters.

    Lots of adapters have a “read-only” switch, and that plus a drop of epoxy seems like a reasonable solution.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Jeff Layman on Thu Nov 30 07:32:25 2023
    On 11/30/2023 2:02 AM, Jeff Layman wrote:
    On 29/11/2023 19:22, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
        (so the little urchins don't wipe the installer image)  I've
        encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives?  (can I get a handful
        of *reliable* reads without worrying about a media error
        or mechanical failure)

    <https://www.computerhope.com/issues/ch001617.htm>

    If you've got something "mission critical"

    I wouldn't characterize it as thus. At the end of the day, the
    client can always bring the laptop back and we can reload *its*
    image from the server (I archive images "by serial number")

    But, it adds to our cost (time) -- and their inconvenience.

    it might be best to avoid a cheap
    drive. If you buy a cheap 32GB drive, perhaps it's a "failed" 64GB drive. Is the 32GB you've got left reliable?

    There's that.

    But, there are two ways of looking at that issue.

    If you're needs are "small", you can argue that lots of fall-out
    parts (even including GOOD parts) can address those needs. So,
    a manufacturer selling something as a 16G drive that may have
    wanted to be a 64G drive is reasonable (or, abandon that market
    entirely).

    OTOH, if the manufacturer is (likely) trying to chase the bigger
    devices market, is he more inclined to let some devices slip
    through that, strictly speaking, won't be quite as good as they
    should?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Don Y on Thu Nov 30 14:30:37 2023
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 4:03 AM, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place
    selling refurbished machines. So if the buyer hoses their box, it's not
    directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Ah, so, in your mindset, it's perfectly fine for a "supplier" to
    screw over his customers? "Not my problem!"

    How on earth is it "screwing over the customer" to require an exchange
    of money for services rendered? It's not like "hey Don, I tried
    installing Linux, and ruined my PC" is exactly something that should be
    fixed under that "30 day warranty" your PC repair shop offers for
    refurbished machines.


    Do you take the same attitude with your *designs*: "*I* hae
    been paid so any problems henceforth are the client's!"

    When the problem is "hey Dan, so I erased the EEPROM on your board, and
    now it doesn't work!" ... yeah, Not My Problem. I didn't ship the
    product with any interface to that 256-bit EEPROM with my
    super-secret-go-code ("12345" ;) ).

    When the problem is "Hey Dan, so I hooked your thing up like the example
    said, but pin X2 isn't working", well either

    1. I made an error in the design (or example) OR
    2. The user messed up in a recoverable way ("Oh, you plugged the LED
    into pin X1") OR
    3. The user messed up in a partially-recoverable way ("Oh, you forgot
    the resistor on the LED, it burned out. Get a new LED from the
    bin") OR
    3. The user messed up in a completely non-recoverable way ("You tried
    to drive a motor directly from the I/O pins?? Board's dead.")



    Wasn't til his first or second response that he said the "clients" are
    kids (in which case ... "is it the school's property, or ... what?")

    It was my second post -- first response.

    And, again, why would you ever think it's NOT a supplier's
    problem to ensure he supplies a quality product?

    There's a VAST difference between someone designing / selling a product
    that doesn't live up to the measure of "quality" and the idea
    that a vendor is somehow "still responsible" when ownership changes
    hands.



    No, it's not the school's property. These are just individuals (underprivileged youth who can't afford to BUY a computer;
    does that mean they can be screwed over because they haven't
    made any cash outlay?) being serviced by a non-profit.

    AH HAH! A non-profit. That explains so much.

    Just as if they'd PURCHASED a machine, from a store, they would expect
    to return to that store (for support) if they had a problem.

    Indeed, and that support tends to cost money.


    In the past, we have been too generous with our (volunteer) time
    in trying to restore machines that had been grossly misused;
    investing hours to recover files from horribly infected/corrupted
    disks. (should we also have just said "not our problem"? How
    does that serve those youth?)

    If these "underpriveleged kids" are involved with your nonprofit as some
    kind of "care" program (either via school aftercare, or some other
    community outreach thingy via the local community center, etc) ... then
    they are not really "customers" are they; but rather "users" of
    computers that your nonprofit loans out.

    In which case, it sounds like you need better rules around what they can
    do with your equipment, and what the consequences of asking for help
    after they get viruses or fail at installing Linux, etc.


    Well sure. But "destroyed via misuse" is a far sight different than "it
    just fell apart" (which I've not seen -- even in my cheapo "Microcenter"
    branded ones)

    For our market, it wouldn't matter. Do we get all holier-than-thou and
    tell the (underprivileged youth) client that he's not taken good enough
    care of his computer so we aren't going to help him?

    Well, if they broke the USB connector clear off their USB stick, there's
    kind of "literally nothing you can do" at that point.

    My other comment about "it fell apart" is more looking at those super
    chintzy ones that sometimes live in boxes at convenience-store checkout counters. I'm pretty sure that bubble-packing on most products is
    sturdier plastic than the housing on those things.


    What if he breaks the keyboard? Screen? Do we "charge" him
    (underprivileged youth) for the repair? (he couldn't afford to BUY
    the machine but he *can* afford to pay for its repair?)

    Yes. The nature of this "charge" depends on the nature of your
    nonprofit and their relationship with it (and their age). I've seen
    some aftercare type programs require good grades on a week's worth of
    homework, or community outreach type programs require various forms of
    chores (suited to the age of the child, ofc).



    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Layman@21:1/5 to Don Y on Thu Nov 30 14:40:49 2023
    On 30/11/2023 14:32, Don Y wrote:
    On 11/30/2023 2:02 AM, Jeff Layman wrote:

    OTOH, if the manufacturer is (likely) trying to chase the bigger
    devices market, is he more inclined to let some devices slip
    through that, strictly speaking, won't be quite as good as they
    should?

    I guess it depends on how much you value your reputation.

    --

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Jeff Layman on Thu Nov 30 08:22:10 2023
    On 11/30/2023 7:40 AM, Jeff Layman wrote:
    On 30/11/2023 14:32, Don Y wrote:
    On 11/30/2023 2:02 AM, Jeff Layman wrote:

    OTOH, if the manufacturer is (likely) trying to chase the bigger
    devices market, is he more inclined to let some devices slip
    through that, strictly speaking, won't be quite as good as they
    should?

    I guess it depends on how much you value your reputation.

    And, if "you've never heard of the company", how likely do
    you THINK they value their reputation? <frown>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dan Purgert on Thu Nov 30 08:21:11 2023
    On 11/30/2023 7:30 AM, Dan Purgert wrote:
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 4:03 AM, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place
    selling refurbished machines. So if the buyer hoses their box, it's not >>> directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Ah, so, in your mindset, it's perfectly fine for a "supplier" to
    screw over his customers? "Not my problem!"

    How on earth is it "screwing over the customer" to require an exchange
    of money for services rendered? It's not like "hey Don, I tried
    installing Linux, and ruined my PC" is exactly something that should be
    fixed under that "30 day warranty" your PC repair shop offers for
    refurbished machines.

    [Have you missed the point that our "customers" don't EXCHANGE MONEY
    for the products? Will they exchange the same non-money for that
    repair??]

    And, where do you draw the line between sticking to the "letter"
    of a sales agreement -- at the expense of developing a bad
    reputation among ALL your customers?

    I offer lifetime bug-fixes on my designs. This tells the client:
    he's confident in his design AND our costs will be limited to
    what he's quoted. Someone else might nickel-and-dime their
    clients claiming "X wasn't part of the initial design/bid".

    Costco has a "satisfaction guaranteed" policy. How much product
    do you think they *eat* to BUY the goodwill that this instills
    in their customers? Surely, they could say, "Hey, you bought
    it. All sales final!" Or, "Returns only allowed for defective
    merchandise and our SOLE remedy will be to replace the defective item"?

    Not only does their policy have these obvious consequences but,
    also, second-order effects.

    E.g., if an item goes on sale soon after you purchased it at
    regular price, you could opt to return it, for a refund. And,
    turn right around and repurchase it (a *fresh* unit) for the
    sale price.

    Some stores will credit you the current SALE price for such returns
    in an obvious attempt to discourage this sort of practice.

    Costco's solution is to allow you to claim the difference in price
    as a partial refund, KEEPING the original item. Given their
    satisfaction guarantee and its (above) consequences, this actually
    is a better option for them.

    But, there are also THIRD order effects: if you know/suspect an
    item WILL be going on sale, you can purchase early (while the
    item is still in stock at the nondiscounted price) knowing that
    you can either:
    - claim the difference in prices as a partial refund
    - return the item if you don't want to pay full price.

    The point of all this is that customers LEARN these consequences
    and make purchase decisions -- including WHERE to shop -- based
    on them.

    Do you take the same attitude with your *designs*: "*I* hae
    been paid so any problems henceforth are the client's!"

    When the problem is "hey Dan, so I erased the EEPROM on your board, and
    now it doesn't work!" ... yeah, Not My Problem. I didn't ship the
    product with any interface to that 256-bit EEPROM with my super-secret-go-code ("12345" ;) ).

    *I*, OTOH, would offer to help the customer, treating that effort
    as an attempt to build goodwill that could turn into future sales
    (or referrals).

    I have customers call because they've misplaced a deliverable...
    YEARS after the contract was finished. I could legally and morally
    say, "Gee, sorry, I fulfilled ALL of my obligations under the
    contract. You should have taken better care of those key items!".
    There's no way for the client to KNOW that I have (or don't have)
    a copy of those deliverables. Or, if I have them, how costly it
    will be for me to retrieve them and redeliver them. *But*,
    helping him out of his SELF-INFLICTED (whether it was by accident
    or design) bind only improves his impression of me as a SUPPLIER
    OF SERVICES.

    "Dear Costco. I opened this $20 bag of protein drink and think it
    tastes like shit! Please give me a full refund, even though I've
    consumed some of it AND the balance is not resellable!"

    When the problem is "Hey Dan, so I hooked your thing up like the example said, but pin X2 isn't working", well either

    1. I made an error in the design (or example) OR
    2. The user messed up in a recoverable way ("Oh, you plugged the LED
    into pin X1") OR
    3. The user messed up in a partially-recoverable way ("Oh, you forgot
    the resistor on the LED, it burned out. Get a new LED from the
    bin") OR
    3. The user messed up in a completely non-recoverable way ("You tried
    to drive a motor directly from the I/O pins?? Board's dead.")

    I contend that it is good policy to fix the customer;s problem regardless
    of "fault". customers who abuse your good will can be discouraged from continuing that practice easily enough: "Gee, sorry to hear you've
    got this problem. I'll try to get to it sometime next MONTH..." (No,
    I'm not going to drop everything to deal with your LATEST screwup)

    Wasn't til his first or second response that he said the "clients" are
    kids (in which case ... "is it the school's property, or ... what?")

    It was my second post -- first response.

    And, again, why would you ever think it's NOT a supplier's
    problem to ensure he supplies a quality product?

    There's a VAST difference between someone designing / selling a product
    that doesn't live up to the measure of "quality" and the idea
    that a vendor is somehow "still responsible" when ownership changes
    hands.

    You miss the point. "Responsibility" is a legally defined thing.
    I'm never responsible for your mistakes.

    OTOH, how I address your calls for assistance will have an impact
    on your future choice of suppliers IN A MARKET WHERE A CLEAR
    MONOPOLY DOES NOT EXIST.

    My clients may be annoyed/disappointed that I moved on to other
    projects instead of tackling THEIR "sequel". But, that's my
    perogative (and they didn't commit to a retainer, etc.). But,
    they never claim I shirked my responsibility or "got all
    technical" about the terms of the contract, etc.

    How many of the folks who stick to the letter of an agreement
    in the face of unforeseen needs do YOU intentionally rely on?

    No, it's not the school's property. These are just individuals
    (underprivileged youth who can't afford to BUY a computer;
    does that mean they can be screwed over because they haven't
    made any cash outlay?) being serviced by a non-profit.

    AH HAH! A non-profit. That explains so much.

    Just as if they'd PURCHASED a machine, from a store, they would expect
    to return to that store (for support) if they had a problem.

    Indeed, and that support tends to cost money.

    And support from a non-profit also has costs.

    A building still has to be lighted, heated, insured, etc.
    Volunteers have to be available and willing to undertake
    the chores that need to be addressed.

    "Free" labor... isn't. (because free implies it is in
    limitless quantities)

    In the past, we have been too generous with our (volunteer) time
    in trying to restore machines that had been grossly misused;
    investing hours to recover files from horribly infected/corrupted
    disks. (should we also have just said "not our problem"? How
    does that serve those youth?)

    If these "underpriveleged kids" are involved with your nonprofit as some
    kind of "care" program (either via school aftercare, or some other
    community outreach thingy via the local community center, etc) ... then
    they are not really "customers" are they; but rather "users" of
    computers that your nonprofit loans out.

    No. We *gift* them to the kids. Businesses donate their surplus
    kit to us. We repair, refurbish and reuse (by distributing it to
    others). It is theirs to do with as they see fit -- which can
    include selling it!

    [Of course, come back for a *second* one and you may be surprised to
    see that your request has been denied. Ooops!]

    But, sadly, people tend not to place value on things that didn't
    "cost" anything. (This is also true of nonprofits and their
    attitudes towards volunteer hours!) So, we have started trying
    to extract a pound of flesh for each such "gift" -- give us
    4 hours of your time in exchange for the laptop.

    [Yeah, even if you know nothing about computers, you can sit
    and untangle power cords and wrap them up, neatly, so I can
    work on other things]

    In which case, it sounds like you need better rules around what they can
    do with your equipment, and what the consequences of asking for help
    after they get viruses or fail at installing Linux, etc.

    Their lives are already complicated. You KNOW where you are going to
    sleep, tonight. And, where your next meal is coming from. They
    don't have those assurances.

    I would *love* for them to tinker (e.g., install Linux) as it's a
    cheap learning experience.

    But, going to porn sites and getting malware on your machine doesn't
    feel like the same sort of joy, on my part. Yet, I'm not a policeman.
    All I can do is adopt policies that minimize *my* (our) costs. You
    wanna sell your laptop? Fine. Sad, but fine. But, I'm not going
    to invest more of my time building *another* one for you to sell!

    Well sure. But "destroyed via misuse" is a far sight different than "it >>> just fell apart" (which I've not seen -- even in my cheapo "Microcenter" >>> branded ones)

    For our market, it wouldn't matter. Do we get all holier-than-thou and
    tell the (underprivileged youth) client that he's not taken good enough
    care of his computer so we aren't going to help him?

    Well, if they broke the USB connector clear off their USB stick, there's
    kind of "literally nothing you can do" at that point.

    I have a friend who is responsible for a datacenter at a large multinational bank. He once toasted a disk drive by plugging the power connector in backwards. I commented: "That's not possible! (plugging the connector
    in backwards) It won't fit!" His reply: "Yeah, it noticed it was really hard getting it *in*..."

    My other comment about "it fell apart" is more looking at those super
    chintzy ones that sometimes live in boxes at convenience-store checkout counters. I'm pretty sure that bubble-packing on most products is
    sturdier plastic than the housing on those things.

    I have no experience with "cheap thumb drives" -- hence the post.
    I've always tended to buy sandisk and from normal retailers
    (not "we-sandisk-company, chop-chop!"). A quick search on amazon
    turns up all sorts of names I've never heard of -- with price points
    all over the map!

    Are their costs so much lower? Vanity pricing for certain brands?
    OR, is the quality an issue??

    I was annoyed the first time I bought a drive and discovered the
    activity LED had been elided to save a few micropennies. But,
    I can adjust my usage accordingly (assuming the indicator actually
    reflected ongoing activity in the controller).

    But, when I encountered some drives (sandisk) where the connector
    shell (the METAL part) had been replaced with thin plastic... no,
    you can keep those, thankyouverymuch!

    What if he breaks the keyboard? Screen? Do we "charge" him
    (underprivileged youth) for the repair? (he couldn't afford to BUY
    the machine but he *can* afford to pay for its repair?)

    Yes. The nature of this "charge" depends on the nature of your
    nonprofit and their relationship with it (and their age). I've seen
    some aftercare type programs require good grades on a week's worth of homework, or community outreach type programs require various forms of
    chores (suited to the age of the child, ofc).

    Remember, there is no monetary cost to the replacement; all of the
    kit is donated. So, it boils down to how you want to use the
    (limited and not contractually bound!) volunteer resources
    available AND the message you want to send to your clients.

    I've been asked to repair keyboards that neighbors have spilled coffee
    on/in. Surely they weren't trying to be careless...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ralph Mowery@21:1/5 to All on Thu Nov 30 11:17:20 2023
    In article <uka99g$1di0j$1@dont-email.me>, blockedofcourse@foo.invalid
    says...

    E.g., if an item goes on sale soon after you purchased it at
    regular price, you could opt to return it, for a refund. And,
    turn right around and repurchase it (a *fresh* unit) for the
    sale price.

    Some stores will credit you the current SALE price for such returns
    in an obvious attempt to discourage this sort of practice.




    I bought a weedeater on sale at Lowes and could not get it started. No
    Spatk. Took it back and got credit for it and had to buy a new one that
    was not on sale. They should have just given me a replacement.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Don Y on Thu Nov 30 16:39:58 2023
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 7:30 AM, Dan Purgert wrote:
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 4:03 AM, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution. >>>>>>>
    Some of the clients are hosing the backup partition by trying to >>>>>>> upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place
    selling refurbished machines. So if the buyer hoses their box, it's not >>>> directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Ah, so, in your mindset, it's perfectly fine for a "supplier" to
    screw over his customers? "Not my problem!"

    How on earth is it "screwing over the customer" to require an exchange
    of money for services rendered? It's not like "hey Don, I tried
    installing Linux, and ruined my PC" is exactly something that should be
    fixed under that "30 day warranty" your PC repair shop offers for
    refurbished machines.

    [Have you missed the point that our "customers" don't EXCHANGE MONEY
    for the products? Will they exchange the same non-money for that
    repair??

    No. You seem to not understand the concept I'm stating though.

    [...]
    Yes. The nature of this "charge" depends on the nature of your
    nonprofit and their relationship with it (and their age). I've seen
    some aftercare type programs require good grades on a week's worth of
    homework, or community outreach type programs require various forms of
    chores (suited to the age of the child, ofc).

    Remember, there is no monetary cost to the replacement

    So what?

    You're already "charged" them a couple of hours worth of menial labor
    around your facility for the "gift" of the laptop in the first place.
    Now they're getting "charged" for the "gift" of the repair work.


    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Dan Purgert on Thu Nov 30 13:24:46 2023
    On 11/30/2023 9:39 AM, Dan Purgert wrote:
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 7:30 AM, Dan Purgert wrote:
    On 2023-11-30, Don Y wrote:
    On 11/30/2023 4:03 AM, Dan Purgert wrote:
    On 2023-11-30, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution. >>>>>>>>
    Some of the clients are hosing the backup partition by trying to >>>>>>>> upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    Yeah, "might".

    Given the original post, I read it as (effectively) a PC repair place >>>>> selling refurbished machines. So if the buyer hoses their box, it's not >>>>> directly the seller's problem (beyond "yes, I'll take your money to
    reset it to what we sold you as 'Factory Default(tm)'. ")

    Ah, so, in your mindset, it's perfectly fine for a "supplier" to
    screw over his customers? "Not my problem!"

    How on earth is it "screwing over the customer" to require an exchange
    of money for services rendered? It's not like "hey Don, I tried
    installing Linux, and ruined my PC" is exactly something that should be
    fixed under that "30 day warranty" your PC repair shop offers for
    refurbished machines.

    [Have you missed the point that our "customers" don't EXCHANGE MONEY
    for the products? Will they exchange the same non-money for that
    repair??

    No. You seem to not understand the concept I'm stating though.

    Monetary transactions and non-monetary transactions are conceptualized
    (by the parties involved) entirely differently.

    You want to PAY me to do something then (assuming I am willing to do it)
    you have leverage over my actions. You want me to GIVE you my time,
    then *I* have control over that.

    The folks who run non-profits tend to think their volunteers are
    employees that can be "ordered about". Yes, they can dictate the
    direction of the organization and its efforts. But, the folks
    charged with carrying this out are under no obligation to even
    stick around until they've finished their "directions".

    *Employees* tend to have far less freedom of choice; you knew
    you were giving up control over your time in exchange for
    money when you accepted the job.

    The same is true of *clients* of these organizations. They feel
    that "free" means they have no obligations nor qualms about
    asking for more.

    "You GAVE me this one, why can't you GIVE me a replacement?"

    I had a client from Somalia (refugee), about a 15 yrs ago, come to pick
    up his "free" computer. He complained because it had a CRT and not
    an LCD.

    "Do they even have electricity in your country??"

    [...]
    Yes. The nature of this "charge" depends on the nature of your
    nonprofit and their relationship with it (and their age). I've seen
    some aftercare type programs require good grades on a week's worth of
    homework, or community outreach type programs require various forms of
    chores (suited to the age of the child, ofc).

    Remember, there is no monetary cost to the replacement

    So what?

    You're already "charged" them a couple of hours worth of menial labor
    around your facility for the "gift" of the laptop in the first place.
    Now they're getting "charged" for the "gift" of the repair work.

    No, the labor requirement is a recent addition to the mix. For the
    past ~20 years it was just a demonstration of "need" that was
    required.

    They don't see it as a "repair" but as a flaw in the "product"...
    "The computer you gave me doesn't work!"

    People (not just clients) rarely think that something is a consequence
    of their actions (or inactions). "It's a stupid design" "It just
    stopped working" etc.

    If they think they have *partial* blame, they also think the device
    should have anticipated their actions and safeguarded against
    a costly (time/money) failure.

    We bought a glass TTY in ~1978. It "got confused", at one point.
    We powered it off. Then back on.

    And the power supply went south.

    "You should have waited a few seconds between powering it off and on."

    Really? Shouldn't *it* have been designed to handle that possibility?

    Of course, the vendor doesn't want to lose a sale so sends someone out
    to fix the (defective) product.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Ralph Mowery on Thu Nov 30 13:31:29 2023
    On 11/30/2023 9:17 AM, Ralph Mowery wrote:
    In article <uka99g$1di0j$1@dont-email.me>, blockedofcourse@foo.invalid says...

    E.g., if an item goes on sale soon after you purchased it at
    regular price, you could opt to return it, for a refund. And,
    turn right around and repurchase it (a *fresh* unit) for the
    sale price.

    Some stores will credit you the current SALE price for such returns
    in an obvious attempt to discourage this sort of practice.




    I bought a weedeater on sale at Lowes and could not get it started. No Spatk. Took it back and got credit for it and had to buy a new one that
    was not on sale. They should have just given me a replacement.

    Did you suggest this to them? Remember, the folks working at
    these places don't often think about the consequences of their
    remedies FROM THE CUSTOMER'S POINT OF VIEW. I try to put a
    suggestion in front of them so they don't have to do much thinking.

    E.g., I want to buy 6 of these, as advertised, to get the discount.
    But, you only have 5 in stock. Why not prorate the price of 6
    (instead of telling me "no sale")?

    I've had folks refund the purchase amount -- and had to remind
    them that *I* had paid sales tax on the purchase (which they
    had failed to refund).

    No, I'm not pinching pennies. 8.7% of a purchase would be
    a nice discount, and, thus, equally un-nice surcharge!
    Especially if you pay it on "nothing" (the returned item)!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Fri Dec 1 11:08:12 2023
    On 30/11/2023 12:15, Don Y wrote:
    On 11/30/2023 3:53 AM, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    If your (paying) customer trashes the item he BOUGHT from you,
    do you tell him to go suck eggs because he mistreated it?
    How much responsibility can he heap on you for creating a
    product that was so EASILY mistreated?

    Depends on what you mean by easily. Few devices with spinning rust in
    can survive being dropped 3' onto a concrete floor, iPads and mobile
    phones are even more fragile. My old one had a bit missing from its "Indestructible" gorilla glass but still worked. My wife had someone
    drop an iPad destroying it beyond economic repair.

    Even if you refuse to comp him for his losses, do you, also,
    refuse to do any further business with him?

    Potentially. We took to putting telltales into the shipping package
    after one damaged machine came back with clear evidence that it had
    stood upside down in 12" of salty water long enough for mild steel parts
    to go rusty. That pretty much clinched who was at fault (it was the sort
    of kit that is shipped in air floatation supports "this way up!").

    Most spectacular one to repair we ever had was when they dropped one
    from the cargo bay door of a 747. It was never the same again.

    When your customer doesn't give you monies for your product,
    the dynamics change!  ("You've been a bad boy!  We're going to
    cut our ties to you...")

    Absolutely. I had a strict policy of no support for existing work until
    my bills were paid. Some of the large companies I worked for as an
    employee and then later as a contractor would only pay their bigger
    bills when someone from the bailiffs turned up to take the fax machine
    away. I knew their systems and MO so I made damn sure that I got paid on
    time and in full.

    - Can I make a thumb drive "read only" prior to distribution?
        (so the little urchins don't wipe the installer image)  I've
        encountered drives that have *failed* in an R/O mode...

    No, commodity flash drives don't tend to include "write once" features.
    An ISO that they have to burn themselves is probably the most reliable
    option (ref. standard Linux installation ISOs)

    - How durable are *cheap* thumb drives?  (can I get a handful
        of *reliable* reads without worrying about a media error
        or mechanical failure)

    Pretty durable.  It's the writes that wear out the flash / cause it to
    fail.

    That or the mechanics. I have seen particularly cack handed people
    break USB sticks off (more often TV tuners) leaving part of the thing
    still in the machine. This can be terminal for the USB socket too.

    If it writes and verifies OK then it should be good for quite a few
    reads if it is looked after.

    "Looked after" is a problem.  The beauty of the restore partition was that they didn't have to *do* anything to have it available.  The thumb drive will
    require them to keep it on hand... somewhere.

    Why not continue to use the partition method and keep this option as a
    backup. I suspect the USB stick will get reused though. You could
    perhaps make all the important files invisible to naive end users.

    OTOH, if they misplace it, then THEY are inconvenienced as they will have
    to bring the machine into the shop.  On public transportation.  Time that they could have used for some other purpose (essential or recreational).

    I was hoping the drives could be made non-reusable (R/O) to eliminate
    their being used/traded/sold for purposes other than as THEIR backup:

       "I lost my thumb drive; can I have another?"

       "OK, I'll put in a work order to have one made for you.  What's
       your machine's serial number (so we can look up the correct
       image to place on the drive for YOUR machine)?  Oh, you don't have
       that handy?  Well, get back to us when you do..."

    I can see it could be complex if the installed based is inhomogenous.

    Longevity might be an issue longer term so not in the sun and kept
    cool and dry would make sense. I have had the odd really cheap and
    nasty one croak on first use but it is rare.

    Leave it in a machine shop full of metal swarf and all bets are off!

    Many of these kids don't have permanent places to *sleep* (let alone LIVE). So, everything that they have to keep track of is a challenge.  Our GOAL isn't to make their life any harder.  OTOH, *they* should assume responsibility
    for maintaining their improved quality of life and not just ASSUME that
    we'll forever be accommodating their LACK of responsibility.

    We used to give out SFF desktop machines.  But, that was limited to
    kids who had a place to SET UP such a machine!

    And, if their living arrangements (inevitably "temporary") changed,
    the machine could get lost (left behind) in the "move".

    I find it hard to work out what to do for the best under these tricky constraints. I've done some voluntary work for organisations where
    everything had to be chained down to the desks to prevent snatch thieves
    but never anything quite so complicated.

    Or, *sold*... even $10 is a win if the machine didn't cost you anything
    AND if you think you can get another, for free!

    I can see why you need to lock things down.

    There are too many videos of how to format a write protected USB drive
    for you to stand much chance of preventing it. Use cheap nasty small
    ones would be the best idea that I can come up with. Ones that are too
    small to have any resale value.

    Another simple option would be a write once CD and then you could
    include images for a few different machines on one disk. That way any
    copy of the right CD will do to make a trashed machine work again.

    Or even the micro CDs that come with drivers on.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Jones@21:1/5 to Jan Panteltje on Sat Dec 2 00:11:09 2023
    On 30/11/2023 4:48 pm, Jan Panteltje wrote:
    On a sunny day (Wed, 29 Nov 2023 12:22:09 -0700) it happened Don Y <blockedofcourse@foo.invalid> wrote in <uk8317$v4vl$1@dont-email.me>:

    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    I bought a cheap 1 TB USB stick, it lasted a few weeks.
    Opening it up I found that the PCB had pads for input protection parts
    none were fitted.

    OTOH I have an old 'Duracell' 16 GB USB stick that is still fine after more than 20 years daily use.

    As to write protectioon, no way, one can always do a dd if=/dev/zero of=/dev/USBSTICK if one wants to.
    Old SDcards had a mechanical switch, glue it? LOL



    I think the "switch" in a SD card is just a piece of plastic and relies
    on an actual switch in the socket that is activated by that piece of
    plastic. Since the SD card uses a fast serial protocol, and is quite
    likely connected to a processor running software rather than digital
    hardware, quite likely the write protect switch in the socket is at best connected to a GPIO readable by the processor, but possibly connected to nothing at all. Of course software can ignore it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Purgert@21:1/5 to Chris Jones on Fri Dec 1 16:23:44 2023
    On 2023-12-01, Chris Jones wrote:
    On 30/11/2023 4:48 pm, Jan Panteltje wrote:
    [...]
    Old SDcards had a mechanical switch, glue it? LOL



    I think the "switch" in a SD card is just a piece of plastic and relies
    on an actual switch in the socket that is activated by that piece of
    plastic.

    Indeed - the switch is in the reader; much like the old "WP Notch" on
    floppy disks. Granted, I'm not sure if any kids would bother trying to
    tape it up to enable writing :)

    (and yes, it's "honor system" -- a SD Card reader could potentially not
    have that switch/sensor built in; or the driver could ignore it)


    --
    |_|O|_|
    |_|_|O| Github: https://github.com/dpurgert
    |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jan Panteltje@21:1/5 to lugnut808@spam.yahoo.com on Fri Dec 1 16:37:48 2023
    On a sunny day (Sat, 2 Dec 2023 00:11:09 +1100) it happened Chris Jones <lugnut808@spam.yahoo.com> wrote in <OXkaN.516$CVPf.15@fx15.ams4>:

    On 30/11/2023 4:48 pm, Jan Panteltje wrote:
    On a sunny day (Wed, 29 Nov 2023 12:22:09 -0700) it happened Don Y
    <blockedofcourse@foo.invalid> wrote in <uk8317$v4vl$1@dont-email.me>:

    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    I'd like, instead, to offer a thumb drive as installation media
    in lieu of the backup partition.

    - Can I make a thumb drive "read only" prior to distribution?
    (so the little urchins don't wipe the installer image) I've
    encountered drives that have *failed* in an R/O mode...
    - How durable are *cheap* thumb drives? (can I get a handful
    of *reliable* reads without worrying about a media error
    or mechanical failure)

    I bought a cheap 1 TB USB stick, it lasted a few weeks.
    Opening it up I found that the PCB had pads for input protection parts
    none were fitted.

    OTOH I have an old 'Duracell' 16 GB USB stick that is still fine after more than 20 years daily use.

    As to write protectioon, no way, one can always do a dd if=/dev/zero of=/dev/USBSTICK if one wants to.
    Old SDcards had a mechanical switch, glue it? LOL



    I think the "switch" in a SD card is just a piece of plastic and relies
    on an actual switch in the socket that is activated by that piece of
    plastic. Since the SD card uses a fast serial protocol, and is quite
    likely connected to a processor running software rather than digital >hardware, quite likely the write protect switch in the socket is at best >connected to a GPIO readable by the processor, but possibly connected to >nothing at all. Of course software can ignore it.

    Ok
    so then it should not be hard to make something that has a normal USB stick or SDcard embedded and
    an USB conector, piece of asm (PIC?) to make it read only.
    Should be easy to code.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Fri Dec 1 13:29:15 2023
    On 12/1/2023 4:08 AM, Martin Brown wrote:
    On 30/11/2023 12:15, Don Y wrote:
    On 11/30/2023 3:53 AM, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    If your (paying) customer trashes the item he BOUGHT from you,
    do you tell him to go suck eggs because he mistreated it?
    How much responsibility can he heap on you for creating a
    product that was so EASILY mistreated?

    Depends on what you mean by easily.

    You know, like accepting an offer to upgrade to Windows N+1?
    (seems like it would qualify as an "easy" thing to do (read:
    mistake to make) That being the thing that is hosing my restore
    strategy.

    Few devices with spinning rust in can
    survive being dropped 3' onto a concrete floor, iPads and mobile phones are even more fragile. My old one had a bit missing from its "Indestructible" gorilla glass but still worked. My wife had someone drop an iPad destroying it
    beyond economic repair.

    The issue boils down to how much you are willing to accommodate
    "customers" that, LEGALLY, you are not obligated. If you want to
    keep a customer, you tend to "eat" things that your lawyers might
    tell you aren't necessary.

    If you have lots of competition and can easily *lose* a customer,
    then you likely "do them a favor" (esp if the favor only consumes
    the intangible called "time" -- which nonprofits consider to
    be "free").

    Also, if your customer has no other recourse AND your purpose
    for existing (nonprofit) is to cater to that need, then how do
    you rationalize screwing them "on a technicality" (cuz that's
    how THEY will see it -- and they are tuned into "their"
    community of "other customers")

    [This, BTW, is why abuses are so common; one guy discovers a
    way to beat the system and word quickly spreads amongst his
    "peers". It's also why you can't just implement things as
    "policy" -- they will learn "Ask Debbie for a replacement,
    she's a pushover! If you ask Barbara, you're screwed..."]

    Even if you refuse to comp him for his losses, do you, also,
    refuse to do any further business with him?

    Potentially. We took to putting telltales into the shipping package after one damaged machine came back with clear evidence that it had stood upside down in
    12" of salty water long enough for mild steel parts to go rusty. That pretty much clinched who was at fault (it was the sort of kit that is shipped in air floatation supports "this way up!").

    Most spectacular one to repair we ever had was when they dropped one from the cargo bay door of a 747. It was never the same again.

    Again, non-profit world vs. "for profit".

    We had a customer clone our control algorithms (PLC-based) to avoid
    having to pay US for the PLC, etc. Do we stop doing business with
    them (when there are only a dozen or so such customers, worldwide)?

    No. What you do is NOT (significantly) discount the other bits of
    kit that they have to buy from you so their overall costs (buying
    the PLC from someone else) remain unchanged; you just shift the
    margin into other items.

    AND, you refuse to accept contracts to customize the control
    software, going forward! I.e., you let THEM support themselves
    (which is why they argued -- to their management -- that they
    should take on the controls, internally. Now, they are at a
    competitive disadvantage cuz you WILL take on customization
    for other customers -- THEIR COMPETITORS!

    When your customer doesn't give you monies for your product,
    the dynamics change!  ("You've been a bad boy!  We're going to
    cut our ties to you...")

    Absolutely. I had a strict policy of no support for existing work until my bills were paid.

    No, that's "when your customer doesn't give you monies THAT YOU ARE OWED". Different from "when customer is not EXPECTED to give you monies".

    Some of the large companies I worked for as an employee and
    then later as a contractor would only pay their bigger bills when someone from
    the bailiffs turned up to take the fax machine away. I knew their systems and MO so I made damn sure that I got paid on time and in full.

    I had a different approach: I simply wouldn't work for them, ever again.
    And, as the LOCAL community of people on which they could draw for the services I provided was small, it was easy to make sure other folks knew "I'd been stiffed".

    So, if THEY opted to work for said client, they would take steps to
    ensure payment up front.

    [I eventually settled on 1/3 up front -- which means YOU are at risk
    for 1/3 the value of the contract, INITIALLY; then 1/3 at the halfway
    point -- at which point, I had 50% effort invested but only been paid
    for 33% so 33% of what I should expect to receive is at risk until
    the second payment is made; then the final 1/3 at signoff. This
    approach shifts the risk back and forth as well as limiting it's
    magnitude. (I stopped doing T&M jobs long ago as I want control
    over the extent of a project)]

    Pretty durable.  It's the writes that wear out the flash / cause it to >>>> fail.

    That or the mechanics. I have seen particularly cack handed people break USB
    sticks off (more often TV tuners) leaving part of the thing still in the >>> machine. This can be terminal for the USB socket too.

    If it writes and verifies OK then it should be good for quite a few reads if
    it is looked after.

    "Looked after" is a problem.  The beauty of the restore partition was that >> they didn't have to *do* anything to have it available.  The thumb drive will
    require them to keep it on hand... somewhere.

    Why not continue to use the partition method and keep this option as a backup.
    I suspect the USB stick will get reused though. You could perhaps make all the
    important files invisible to naive end users.

    The restore partition was invisible except for a boot prompt/keystroke.
    I hid the image in the HPA so the OS couldn't *normally* muck with it.

    But, if the boot record got clobbered, then my custom bootstrap
    would be toasted so there was no way to even invoke the process.

    OTOH, if they misplace it, then THEY are inconvenienced as they will have
    to bring the machine into the shop.  On public transportation.  Time that >> they could have used for some other purpose (essential or recreational).

    I was hoping the drives could be made non-reusable (R/O) to eliminate
    their being used/traded/sold for purposes other than as THEIR backup:

        "I lost my thumb drive; can I have another?"

        "OK, I'll put in a work order to have one made for you.  What's
        your machine's serial number (so we can look up the correct
        image to place on the drive for YOUR machine)?  Oh, you don't have >>     that handy?  Well, get back to us when you do..."

    I can see it could be complex if the installed based is inhomogenous.

    Machines come to us from a variety of sources. Most often, a business upgrading to some newer version of Windows *or* just upgrading hardware
    (e.g., moving from desktops to diskless workstations).

    So, any solution has to work with a "generic computer". E.g., I can't
    count on the BIOS having support for a restore partition via a hotkey.

    But, disk drives are present in all computers as is the NORMAL boot
    mechanism. And, the HPA.

    If this is now a problem, I can still resort to booting from a USB
    drive (as most BIOSes support this -- though it may be necessary to
    reconfigure boot settings in that particular bios).

    Longevity might be an issue longer term so not in the sun and kept cool and >>> dry would make sense. I have had the odd really cheap and nasty one croak on
    first use but it is rare.

    Leave it in a machine shop full of metal swarf and all bets are off!

    Many of these kids don't have permanent places to *sleep* (let alone LIVE). >> So, everything that they have to keep track of is a challenge.  Our GOAL
    isn't to make their life any harder.  OTOH, *they* should assume responsibility
    for maintaining their improved quality of life and not just ASSUME that
    we'll forever be accommodating their LACK of responsibility.

    We used to give out SFF desktop machines.  But, that was limited to
    kids who had a place to SET UP such a machine!

    And, if their living arrangements (inevitably "temporary") changed,
    the machine could get lost (left behind) in the "move".

    I find it hard to work out what to do for the best under these tricky constraints. I've done some voluntary work for organisations where everything had to be chained down to the desks to prevent snatch thieves but never anything quite so complicated.

    In addition to having (ahem) "dubious" clients, we also have "tenuous" volunteers.

    Most volunteers are developmentally disabled, autistic, physically
    handicapped, etc. (They spend time with us as a form of occupational therapy... give them something to do, something to focus on, etc.)
    Others may be present solely to satisfy court-ordered probation
    ("community service") -- so, they might be *able* to do the work but
    aren't going to bust their ass because they often feel like THEY
    are the victim and this is unfair punishment ("Really? I don't have
    to sign your attendance report. You can pick up trash on the side
    of the highway in 100F weather if you're not happy *here*!")

    I've walked into the bathroom and found folks shooting up. We've
    had to have folks escorted off the property for violent outbursts
    and assaults, etc.

    And, turnover is relatively high -- someone "doing time" is not
    likely to keep coming after his "sentence" has been completed.

    It's just a completely different environment from a 9-to-5
    (where folks are concerned about KEEPING their position!)

    Or, *sold*... even $10 is a win if the machine didn't cost you anything
    AND if you think you can get another, for free!

    I can see why you need to lock things down.

    There are too many videos of how to format a write protected USB drive for you
    to stand much chance of preventing it. Use cheap nasty small ones would be the
    best idea that I can come up with. Ones that are too small to have any resale value.

    I think if I intercept the *normal* driver install (VID/PID for THIS drive),
    I can replace it with something that doesn't support write operations at
    the device level.

    But, that only locks the drive while it is installed in THIS machine.

    Another simple option would be a write once CD and then you could include images for a few different machines on one disk. That way any copy of the right
    CD will do to make a trashed machine work again.

    Machines are now being offered without optical drives. I think the design rationale is that you can access RUNTIME media via the network connection
    and boot media via USB devices.

    This is especially true for smaller machines (which are a favorite of
    the clients because they don't want to have to lug something with a
    17" display)

    [I have a pair of netbooks, here, that I keep because they *are*
    so small. I can slip them BOTH in a desk drawer instead of having
    to store them on a shelf in a laptop bag.]

    Or even the micro CDs that come with drivers on.

    I've been exploring UEFI BIOSes (for another project) with the goal
    of making a machine unusable as a generic PC (prevent the OS from
    being installed). If this bears fruit, I may be able to take some
    information from that and use it to cripple these machines to
    protect the HPA and boot record (e.g., block writes to any of
    those areas so an OS install throws an error)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Wed Dec 6 11:21:28 2023
    On 01/12/2023 20:29, Don Y wrote:
    On 12/1/2023 4:08 AM, Martin Brown wrote:

    Another simple option would be a write once CD and then you could
    include images for a few different machines on one disk. That way any
    copy of the right CD will do to make a trashed machine work again.

    Machines are now being offered without optical drives.  I think the design rationale is that you can access RUNTIME media via the network connection
    and boot media via USB devices.

    This is especially true for smaller machines (which are a favorite of
    the clients because they don't want to have to lug something with a
    17" display)

    If they have a full size sD slot then I favour Phils suggestion of a
    micro sD in an sD carrier write protected with a spec of araldite.

    [I have a pair of netbooks, here, that I keep because they *are*
    so small.  I can slip them BOTH in a desk drawer instead of having
    to store them on a shelf in a laptop bag.]

    My favourite portable for travelling is an ASUS T1000 (not made of
    liquid metal) 11" diagonal screen. It's not fast, a bit long in the
    tooth now but lasts a long time and is very small. It even comes apart
    so that you can use the screen as a tablet.

    Or even the micro CDs that come with drivers on.

    I've been exploring UEFI BIOSes (for another project) with the goal
    of making a machine unusable as a generic PC (prevent the OS from
    being installed).  If this bears fruit, I may be able to take some information from that and use it to cripple these machines to
    protect the HPA and boot record (e.g., block writes to any of
    those areas so an OS install throws an error)

    That sounds like hard work for little gain. BIOSes can also be overwritten.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Wed Dec 6 09:40:34 2023
    On 12/6/2023 4:21 AM, Martin Brown wrote:
    On 01/12/2023 20:29, Don Y wrote:
    On 12/1/2023 4:08 AM, Martin Brown wrote:

    Another simple option would be a write once CD and then you could include >>> images for a few different machines on one disk. That way any copy of the >>> right CD will do to make a trashed machine work again.

    Machines are now being offered without optical drives.  I think the design >> rationale is that you can access RUNTIME media via the network connection
    and boot media via USB devices.

    This is especially true for smaller machines (which are a favorite of
    the clients because they don't want to have to lug something with a
    17" display)

    If they have a full size sD slot then I favour Phils suggestion of a micro sD in an sD carrier write protected with a spec of araldite.

    I don't have a say in the machines we are gifted. And, the clients *technically* don't have a say in the machines that we give *them*
    (though we try to accommodate).

    The homemade restore partition was a win because it could be made
    to work (function) with any laptop that had a keyboard and a boot
    disk. The problem was that there was no easy way to protect it;
    Joe Average could clobber the image in an attempt to install a
    new OS.

    [I have a pair of netbooks, here, that I keep because they *are*
    so small.  I can slip them BOTH in a desk drawer instead of having
    to store them on a shelf in a laptop bag.]

    My favourite portable for travelling is an ASUS T1000 (not made of liquid metal) 11" diagonal screen. It's not fast, a bit long in the tooth now but lasts a long time and is very small. It even comes apart so that you can use the screen as a tablet.

    I used to have a tiny Sony laptop. All of the I/Os were on a dock
    (save for USB and a memory stick). Including the optical drive,
    printer port, etc.

    I could leave that at home and have this slim little device
    that didn't weigh down my carry-on -- the power adapter weighed more
    than the "laptop" (I carry a fat briefcase with laptop and a few
    changes of clothing inside so ALL my luggage fits under *my* seat).

    The keyboard was small/cramped (I like a full size keyboard)
    but I mainly used it to check mail and run demos.

    It's gone, now -- one of my "purges" (I have a shitload of kit!).
    Now, I carry an aircraft carrier. Impractical for use on planes
    but 17" screen and full-sized keyboard make a difference in use.

    Or even the micro CDs that come with drivers on.

    I've been exploring UEFI BIOSes (for another project) with the goal
    of making a machine unusable as a generic PC (prevent the OS from
    being installed).  If this bears fruit, I may be able to take some
    information from that and use it to cripple these machines to
    protect the HPA and boot record (e.g., block writes to any of
    those areas so an OS install throws an error)

    That sounds like hard work for little gain. BIOSes can also be overwritten.

    I have no desire to write any code. Rather, just juggle entry-points
    (function bindings).

    So, when COTS (or FOSS!) software tries to "write to display", the
    code that executes is "read from keyboard". Etc. This will allow me
    to leave the initial boot code in place but cripple any efforts
    of any other software that EXPECTS an ISA BIOS.

    My OS, OTOH, just needs to rearrange the hooks to the machine's
    modified BIOS to take into account this new mapping.

    ANYTHING that I do can be undone. But, you have to know what has
    been done and how to undo it. Try to boot some other installer
    and the machine will appear to lock up. Reboot the *native* OS
    and all works fine. (I.e., the machine isn't broken; just the
    foreign installer!)

    What we're trying to do is prevent the sort of things that have
    happened with folks trying to "repurpose" the machine for some
    other "mainstream" use. E.g., bring it to a pawn shop and
    it won't RUN like a "PC". Their staff won't be able to
    install a new OS so they quickly realize they have a brick
    (and won't buy any other similarly "marked" machines.

    The machines aren't particularly valuable (we get them for free).
    But, we want to be able to control the machines LOANED OUT
    (for this program) so they are all identical. *And*, encourage
    them to come back to us (on completion of the program, each
    participant is gifted a "real" laptop).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Computer Nerd Kev@21:1/5 to Phil Hobbs on Sat Dec 9 07:28:57 2023
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    If your laptops have full size SD card slots, you could use micro-SDs with adapters.

    Lots of adapters have a "read-only" switch, and that plus a drop of epoxy seems like a reasonable solution.

    A better approach for SD/MicroSD cards is to set their controller
    to read-only mode, which can be permanent. I'm not sure whether any
    normal card readers (or their public drivers) support this, but
    there are dedicated devices for doing it:

    https://blog.tindie.com/2021/02/sd-card-locker/

    --
    __ __
    #_ < |\| |< _# | Note: I won't see posts made from Google Groups |

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to '''newspam'''@nonad.co.uk on Fri Dec 8 15:13:14 2023
    On Fri, 1 Dec 2023 11:08:12 +0000, Martin Brown
    <'''newspam'''@nonad.co.uk> wrote:

    On 30/11/2023 12:15, Don Y wrote:
    On 11/30/2023 3:53 AM, Martin Brown wrote:
    On 30/11/2023 00:24, Dan Purgert wrote:
    On 2023-11-29, Don Y wrote:
    I've got a box that builds a "backup partition" on a machine
    and then invokes it to install the OS/apps prior to distribution.

    Some of the clients are hosing the backup partition by trying to
    upgrade to Windows, etc.

    Not your problem if they trash their box, is it?

    It might be.

    If your (paying) customer trashes the item he BOUGHT from you,
    do you tell him to go suck eggs because he mistreated it?
    How much responsibility can he heap on you for creating a
    product that was so EASILY mistreated?

    Depends on what you mean by easily. Few devices with spinning rust in
    can survive being dropped 3' onto a concrete floor, iPads and mobile
    phones are even more fragile. My old one had a bit missing from its >"Indestructible" gorilla glass but still worked. My wife had someone
    drop an iPad destroying it beyond economic repair.

    Even if you refuse to comp him for his losses, do you, also,
    refuse to do any further business with him?

    Potentially. We took to putting telltales into the shipping package
    after one damaged machine came back with clear evidence that it had
    stood upside down in 12" of salty water long enough for mild steel parts
    to go rusty. That pretty much clinched who was at fault (it was the sort
    of kit that is shipped in air floatation supports "this way up!").

    Most spectacular one to repair we ever had was when they dropped one
    from the cargo bay door of a 747. It was never the same again.

    When your customer doesn't give you monies for your product,
    the dynamics change! ("You've been a bad boy! We're going to
    cut our ties to you...")

    Absolutely. I had a strict policy of no support for existing work until
    my bills were paid. Some of the large companies I worked for as an
    employee and then later as a contractor would only pay their bigger
    bills when someone from the bailiffs turned up to take the fax machine
    away. I knew their systems and MO so I made damn sure that I got paid on
    time and in full.

    One of my aerospace customers sometimes expresses concern that we
    aren't making enough money.

    We shipped a bunch of VME modules with a bug. They said "you're a
    small company, let us pay you to fix it." We declined the offer.

    On the other hand, companies in Silicon Valley tend to be cheapskates
    and steal our IP when they can. Different culture.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)