public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Memory cards and deleting files.
Date: Mon, 22 Jun 2020 21:42:29 +0100	[thread overview]
Message-ID: <20200622214229.76e3fa60@digimed.co.uk> (raw)
In-Reply-To: <94559278-c6ec-374e-a1ce-e04d2c8e4537@youngman.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]

On Mon, 22 Jun 2020 20:40:49 +0100, antlists wrote:

> >> Warning 2: I did exactly that, and it LOOKED like it was working
> >> happily, until it overflowed some internal limit and my 1G card
> >> turned into a 128M card or whatever it was. Have you actually TESTED
> >> that card IN THE DASHCAM and made sure it can actually use that
> >> 128G? Or will it only be able to use 4G of that card?  
> 
> > There are a lot of SD cards with fake capacities, they appear to be
> > large but are actually a smaller card reprogrammed to do so. You only
> > find out when you go beyond the true capacity. There are tools to
> > check this, such as sys-block/f3.  
> 
> Did you look at the card sizes I quoted? :-) I think the reason I tried 
> a 1GB card was because the camera said it took a max of 512MB. It
> didn't work ... (Oh and the card was good. It was small by the
> standards of the day.)

So that was SDHC vs SD? Or was it even that? 2GB was the original SD
limit IIRC correctly, so you weren't trying to use the wrong spec. Was it
just a case of a faulty card, either through accident or design.

However, those cards were more expensive than current huge cards, so the
temptation to sell fakes would have been even greater. Many years ago I
got burned like that with a large (for the time) capacity USB stick
bought on Ebay.


-- 
Neil Bothwick

Frog philosophy: Time's fun when you're having flies.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-22 20:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 17:09 [gentoo-user] Memory cards and deleting files Dale
2020-06-20 22:14 ` Neil Bothwick
2020-06-20 23:08   ` Wols Lists
2020-06-20 23:11     ` Michael
2020-06-20 23:26       ` Wols Lists
2020-06-21 11:52         ` Michael
2020-06-22 10:28           ` Neil Bothwick
2020-06-22 10:56             ` Walter Dnes
2020-06-22 11:12               ` Neil Bothwick
2020-06-22 13:19                 ` Dale
2020-06-22 13:46                   ` Neil Bothwick
2020-06-22 15:04                     ` Dale
2020-06-22 18:25                   ` antlists
2020-06-22 18:50                     ` Dale
2020-06-22 19:34                       ` antlists
2020-06-22 20:35                         ` Dale
2020-06-22 18:25               ` antlists
2020-06-22 18:52                 ` Dale
2020-06-22 19:22                 ` Neil Bothwick
2020-06-22 19:40                   ` antlists
2020-06-22 20:42                     ` Neil Bothwick [this message]
2020-06-23 15:49                       ` antlists
2020-06-21 12:23       ` Dale
2020-06-21 12:32 ` Franz Fellner
2020-06-21 14:21   ` Dale
2020-06-21 14:50     ` Franz Fellner
2020-06-21 16:17       ` John Covici
2020-06-21 16:55         ` Dale
2020-06-22 10:30         ` Neil Bothwick
2020-06-22 13:47           ` [gentoo-user] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200622214229.76e3fa60@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox