Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #181812 > unrolled thread
| Started by | Marion <marion@facts.com> |
|---|---|
| First post | 2025-01-31 17:48 +0000 |
| Last post | 2025-02-02 22:54 +0000 |
| Articles | 20 on this page of 171 — 15 participants |
Back to article view | Back to alt.comp.os.windows-10
Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-01-31 17:48 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-01-31 19:09 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 19:26 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-01-31 21:18 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-01-31 23:19 +0100
The "label" command (Was: Clever helpful suggestion for portable memory using Windows &) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:24 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-01-31 22:25 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:38 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-01-31 23:39 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-01-31 22:48 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Quincy the fifth <quincythefifth@telekom.net> - 2025-02-01 00:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 06:03 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-02-01 10:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:45 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:51 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 00:07 +1000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-04-26 21:37 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:23 +1000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-04-27 14:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 14:55 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 19:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 20:54 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:21 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 14:43 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 00:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 01:59 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:06 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-03 13:28 +0100
What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-03 13:09 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 14:34 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors knuttle <keith_nuttle@yahoo.com> - 2025-02-03 10:47 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:30 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Newyana2 <newyana@invalid.nospam> - 2025-02-03 15:15 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:25 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Newyana2 <newyana@invalid.nospam> - 2025-02-05 09:32 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 20:46 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:39 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Paul <nospam@needed.invalid> - 2025-02-03 15:42 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 22:40 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:45 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-04 15:41 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:18 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:05 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Paul <nospam@needed.invalid> - 2025-02-05 20:04 -0500
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:17 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 21:02 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:47 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:28 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-08 10:18 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 23:35 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-10 08:47 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-10 10:55 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-11 01:00 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-13 19:59 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-13 22:15 +0000
[OT] Storage technology "back then" (was Re: What is an animal or an SSD drive? [...]) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-14 02:10 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-18 11:56 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-18 21:55 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-21 09:12 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-21 23:35 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-25 18:27 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-25 18:25 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:53 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-26 13:10 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-26 15:02 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-25 20:28 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:54 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-26 08:49 +0100
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-21 14:12 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-05-14 21:34 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-05-14 12:54 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-05-16 21:29 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-05-16 14:13 +0000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-05-17 21:00 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors Daniel70 <daniel47@eternal-september.org> - 2025-04-27 20:27 +1000
Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-04-27 10:29 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 04:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 05:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 06:05 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 21:34 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 00:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 09:42 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:54 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-08 04:22 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:07 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 23:42 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 02:21 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:05 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 09:59 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 03:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 19:12 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 10:30 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 11:31 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-05 14:27 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-05 14:35 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:21 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-06 23:58 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 05:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 10:30 +0100
Editing binary data with editors - or is there no difference of text and binary? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-07 10:57 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 11:44 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-07 14:39 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? "Carlos E.R." <robin_listas@es.invalid> - 2025-02-07 19:39 +0100
Re: Editing binary data with editors - or is there no difference of text and binary? Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:26 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 18:12 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 23:14 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-06 20:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 20:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Arno Welzel <usenet@arnowelzel.de> - 2025-02-07 21:50 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-08 03:27 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:21 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:07 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-02 03:20 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 05:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-01 16:34 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-01 16:29 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 18:10 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 15:44 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 10:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 15:14 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-04 10:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-04 13:22 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-04 19:51 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-04 23:12 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 15:24 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 15:50 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 16:04 +0100
[meta] posting mistake Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-02 16:26 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-02 16:29 +0000
ext4 on Android (Was: blah, blah, blah...) gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-02 16:37 +0000
Re: ext4 on Android (Was: blah, blah, blah...) Jeff Layman <Jeff@invalid.invalid> - 2025-02-03 09:14 +0000
ext4 on Android (Was: blah, blah, blah...) "Carlos E.R." <robin_listas@es.invalid> - 2025-02-03 15:16 +0100
Re: ext4 on Android (Was: blah, blah, blah...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:59 +0000
Re: ext4 on Android Frank Slootweg <this@ddress.is.invalid> - 2025-02-04 10:23 +0000
Re: ext4 on Android (Was: blah, blah, blah...) Marion <marion@facts.com> - 2025-02-04 22:48 +0000
Re: ext4 on Android (Was: blah, blah, blah...) "Carlos E.R." <robin_listas@es.invalid> - 2025-02-25 23:16 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-03 19:00 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 22:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-05 18:50 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-05 14:26 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:16 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-06 20:50 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-03 19:58 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-04 01:15 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Paul <nospam@needed.invalid> - 2025-02-04 00:24 -0500
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-04 21:40 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-04 22:11 +0000
External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 02:24 +0100
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-04 22:06 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 04:41 +0000
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-05 04:43 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 02:10 -0500
Re: External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 17:40 +0100
Re: External media file systems (was Re: ...) candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-05 18:50 +0000
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:11 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 20:59 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 03:04 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-05 22:48 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 21:00 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-06 16:20 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 22:42 +0000
Re: External media file systems (was Re: ...) Paul <nospam@needed.invalid> - 2025-02-07 00:44 -0500
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-07 06:00 +0000
Re: External media file systems (was Re: ...) Janis Papanagnou <janis_papanagnou+ng@hotmail.com> - 2025-02-05 17:38 +0100
Re: External media file systems (was Re: ...) Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-06 00:06 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-02-03 21:56 +0000
A little bit of discussion between Janis and me (Was: Stupid suggestion(s) for "portable" "memory" using Windows & Android "editors") gazelle@shell.xmission.com (Kenny McCormack) - 2025-02-02 14:53 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 20:59 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 22:54 +0000
Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-01-31 17:48 +0000 |
| Subject | Clever helpful suggestion for portable memory using Windows & Android editors |
| Message-ID | <vnj2dj$2daj$1@nnrp.usenet.blueworldhosting.com> |
Below is both a clever suggestion - and - a quizzical question.
Here's the problem set (which I experienced myself, recently):
A. You're a typical Android/Windows/editor owner with a 64GB sdcard
B. Most of your editing data is kept on that 64GB portable memory card
C. But then you need to double your memory (to 128GB, which costs ~$10)
What happens?
Well, for most people, they lose many editing associations to the files.
Why?
Because for many editors, they don't "search" for file associations.
Coupled with the filespec having changed between the 64GB & 128GB sd cards.
Huh?
You need to know that every sdcard comes with a "volume name".
An example volume name could be, for example, "A1B1-C1D1" (or whatever).
Another example volume name could be, for example, "A2B2-C2D2".
The point is that every sdcard comes with an (almost) unique volume name.
So?
Well, the old card filespec to your data is now *different* than the new!
OLD: /storage/A1B1-C1D1/{editors}/{files}
NEW: /storage/A2B2-C2D2/{editors}/{files}
OK. That sucks. So now you have to manually re-establish the filespec.
For every modern editor. For every file that the editor associates with.
Why did you insert "modern" editor in that sentence?
Are you being sneaky?
Well, a good editor will save its own files wherever you want them to be.
Some editors are good (such as map editing programs, for example).
Those good (aka modern) editors will access your files on the sdcard.
Just like cameras do (but cameras have another trick up their sleeve).
Cameras will *find* all their "media" files, so they don't have this issue.
But many editors do have this issue - particularly map editors.
And GPX editors. And PDF editors. And text editors. (and so on)
So what's the trivially simple (yet devilishly clever) solution then?
Heh heh heh... it's so simple - it should be outlawed as too simple.
Simply format your new sdcard to the same volume name as the old sdcard.
Yup. It's that simple.
STEP 1: Determine the old 64GB sd card volume name (e.g., 0000-0001).
STEP 2: On Windows, quick format the new 128GB sd card to the same name.
STEP 3: On Windows, copy all the old data to the new 128GB sd card.
That's it!
You pop in the new sdcard and everything works exactly as it should.
Ask me how I know that this concept of "portable memory" just works.
Now... for my quizzical question, where the problem set is similar:
A. You're a typical HP Stream owner with a permanent 32GB C: drive
B. So you've added a 64GB portable memory card as the D: drive
C. But then you need to double the D: drive (to 128GB, which costs ~$10)
Does the same trick of formatting the volume name work in that scenario?
[toc] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-01-31 19:09 +0000 |
| Message-ID | <m04lg5Famh9U1@mid.individual.net> |
| In reply to | #181812 |
Marion wrote: > A. You're a typical HP Stream owner with a permanent 32GB C: drive > B. So you've added a 64GB portable memory card as the D: drive > C. But then you need to double the D: drive (to 128GB, which costs ~$10) > > Does the same trick of formatting the volume name work in that scenario? I would expect that as long as the laptop sees the new SD card as D:\ drive, nothing will really care ...
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-01-31 19:26 +0000 |
| Message-ID | <vnj85u$3mbjb$1@news.xmission.com> |
| In reply to | #181814 |
In article <m04lg5Famh9U1@mid.individual.net>, Andy Burns <usenet@andyburns.uk> wrote: >Marion wrote: > >> A. You're a typical HP Stream owner with a permanent 32GB C: drive >> B. So you've added a 64GB portable memory card as the D: drive >> C. But then you need to double the D: drive (to 128GB, which costs ~$10) >> >> Does the same trick of formatting the volume name work in that scenario? > >I would expect that as long as the laptop sees the new SD card as D:\ >drive, nothing will really care ... Arlen is very good at dreaming up non-problems, and then dreaming up "solutions" to those non-problems. -- On the subject of racism being depicted in the media, the far right and the far left have met up in agreement (sort of like how plus infinity meets up with minus infinity). The far left doesn't want it, because they are afraid it will make people racist. The far right doesn't want it, because they are afraid it will make people feel bad about being racist.
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-01-31 21:18 +0000 |
| Message-ID | <vnjeno$r1p$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #181816 |
On Fri, 31 Jan 2025 19:26:54 -0000 (UTC), Kenny McCormack wrote : > very good at dreaming up non-problems The main point of this thread was to purposefully helpfully inform people of the rather useful approach of formatting the volume label of sd cards. I have tested two scenarios, both of which work perfectly when you change out the sd card - but only if you've matched their respective volume labels 1. When you move from phone a to phone b where b is a clone of a, and, 2. When you double (or triple, or whatever) the size of the memory card. Having said that the most important point in this thread is that... I realize Kenny McCormack is a common troll, but the point that shouldn't be lost when these trolls try to waste our time is that formatting the new sd card with the same name as the old sd card is a rather useful approach. For media, in general, it doesn't matter if you copied your old DCIM folder from your 64GB sd card to your new sd card, but for most modern editors (which can store files on the external portable memory card), it does matter. A classic example these ignorant trolls like Kenny McCormack don't understand is the case of OSM map editors, which can store their *huge* map (and other associated KML, GPX, etc.) databases on the external sd card. When you double the size of your portable memory, the existing installed editors such as OSMAnd~ don't even realize the card was swapped out on it. Likewise for most modern editors. They still find their external files, but only if you've thought ahead by matching the entire filespec exactly. Interestingly, what does seem to work even without matching the volume label, is "media files" tend to be found even when the volume label changes (which I suspect is due to a file-type tag that the operating system adds). Does anyone have more detail on how that file-type tag works in the specific case of switching from one filespec to another in the volume label when a typical user (who doesn't know the trick) inserts a new sd card?
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-01-31 23:19 +0100 |
| Message-ID | <2suv6lxdht.ln2@Telcontar.valinor> |
| In reply to | #181821 |
On 2025-01-31 22:18, Marion wrote: > On Fri, 31 Jan 2025 19:26:54 -0000 (UTC), Kenny McCormack wrote : > > >> very good at dreaming up non-problems > > The main point of this thread was to purposefully helpfully inform people > of the rather useful approach of formatting the volume label of sd cards. It would be clever if you used the label command instead of format :-p > > I have tested two scenarios, both of which work perfectly when you change > out the sd card - but only if you've matched their respective volume labels > 1. When you move from phone a to phone b where b is a clone of a, and, > 2. When you double (or triple, or whatever) the size of the memory card. > > Having said that the most important point in this thread is that... > I realize Kenny McCormack is a common troll, but the point that shouldn't > be lost when these trolls try to waste our time is that formatting the new > sd card with the same name as the old sd card is a rather useful approach. I disagree. It is useful for your scenario, it is not for my scenarios. > > For media, in general, it doesn't matter if you copied your old DCIM folder > from your 64GB sd card to your new sd card, but for most modern editors > (which can store files on the external portable memory card), it does > matter. > > A classic example these ignorant trolls like Kenny McCormack don't > understand is the case of OSM map editors, which can store their *huge* map > (and other associated KML, GPX, etc.) databases on the external sd card. > > When you double the size of your portable memory, the existing installed > editors such as OSMAnd~ don't even realize the card was swapped out on it. > > Likewise for most modern editors. They still find their external files, but > only if you've thought ahead by matching the entire filespec exactly. Not so. You can use relative paths. > > Interestingly, what does seem to work even without matching the volume > label, is "media files" tend to be found even when the volume label changes > (which I suspect is due to a file-type tag that the operating system adds). > > Does anyone have more detail on how that file-type tag works in the > specific case of switching from one filespec to another in the volume label > when a typical user (who doesn't know the trick) inserts a new sd card? -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-01-31 22:24 +0000 |
| Subject | The "label" command (Was: Clever helpful suggestion for portable memory using Windows &) Android editors |
| Message-ID | <vnjijb$3mh57$1@news.xmission.com> |
| In reply to | #181822 |
In article <2suv6lxdht.ln2@Telcontar.valinor>, Carlos E.R. <robin_listas@es.invalid> wrote: >On 2025-01-31 22:18, Marion wrote: >> On Fri, 31 Jan 2025 19:26:54 -0000 (UTC), Kenny McCormack wrote : >> >> >>> very good at dreaming up non-problems >> >> The main point of this thread was to purposefully helpfully inform people >> of the rather useful approach of formatting the volume label of sd cards. > >It would be clever if you used the label command instead of format :-p That was my immediate thought as well. -- John Steinbeck: "Socialism never took root in America because the poor see themselves not as an exploited proletariat but as temporarily embarrassed millionaires."
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-01-31 22:25 +0000 |
| Message-ID | <m050veFcalhU2@mid.individual.net> |
| In reply to | #181822 |
Carlos E.R. wrote: > It would be clever if you used the label command instead of format 😛 Are we discussing the label, or the volume ID?
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-01-31 22:38 +0000 |
| Message-ID | <vnjjdt$3mh57$3@news.xmission.com> |
| In reply to | #181824 |
In article <m050veFcalhU2@mid.individual.net>, Andy Burns <usenet@andyburns.uk> wrote: >Carlos E.R. wrote: > >> It would be clever if you used the label command instead of format > >Are we discussing the label, or the volume ID? I assume the former, because I don't think the DOS/Windows "format" command allows you to set the UUID or PARTUUID. Arlen's ideas are based on using DOS/Windows "format" to make the change. -- People often ask what is the difference between liberals and conservatives. It is this. Libs see the government helping them and are OK with the government also helping other people. Cons see the government screwing them and are OK with that as long as the government is also screwing other people.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-01-31 23:39 +0100 |
| Message-ID | <j2007lx7q3.ln2@Telcontar.valinor> |
| In reply to | #181824 |
On 2025-01-31 23:25, Andy Burns wrote: > Carlos E.R. wrote: > >> It would be clever if you used the label command instead of format 😛 > > Are we discussing the label, or the volume ID? He said label :-) -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-01-31 22:48 +0000 |
| Message-ID | <vnjk0d$3mh57$4@news.xmission.com> |
| In reply to | #181826 |
In article <j2007lx7q3.ln2@Telcontar.valinor>, Carlos E.R. <robin_listas@es.invalid> wrote: >On 2025-01-31 23:25, Andy Burns wrote: >> Carlos E.R. wrote: >> >>> It would be clever if you used the label command instead of format >> >> Are we discussing the label, or the volume ID? > >He said label :-) When it says Libby's Libby's Libby's on the label label label... -- Just like Donald Trump today, Jesus Christ had a Messiah complex. And, in fact, the similarities between the two figures are quite striking. For example, both have a ragtag band of followers, whose faith cannot be shaken.
[toc] | [prev] | [next] | [standalone]
| From | Quincy the fifth <quincythefifth@telekom.net> |
|---|---|
| Date | 2025-02-01 00:22 +0100 |
| Message-ID | <vnjlvp$b1fb$1@paganini.bofh.team> |
| In reply to | #181827 |
On Fri, 31 Jan 2025 22:48:45 -0000 (UTC), Kenny McCormack wrote: > When it says Libby's Libby's Libby's on the label label label... This fucking troll McCormack has already infested all the political newsgroups and now he's infecting this group with his troll rot. > From: Kenny McCormack <gazelle@shell.xmission.com> > Newsgroups: alt.global-warming,alt.home.lawn.garden,alt.home.repair,sac.politics,talk.politics.guns > Subject: Besides being completely wrong on the facts, your logic sucks, too > Date: Mon, 21 Oct 2024 13:31:24 -0000 (UTC) > Organization: The official candy of the new Millennium > Message-ID: <vf5l3c$3g545$1@news.xmission.com> > > In article <WexmTqqSkCMaqmqkqLqPrxNUzmCylASM@news.usenet.farm>, > Jamaal Bowman <jamaal.bowman@dumpster-fire.guv> wrote: > ... >> The dictator Democrats keeping chanting "democracy" yet the hypocrite >> overlords never allow We the People to decide for ourselves. > > It is the Trumprepublicans who are the authoritarians, not the Democrats. > Just look at Project 2025. Or any rational analysis of the American > political parties and their stances. > > But that aside, it is pretty clear that people like you simply should not > be allowed to make your own choices. You are a hazard to yourself and > others. You probably voted for the Orange Monster (and probably more than > once). That in and of itself shows you're not competent to be in the > voting booth. I'm serious about this; you are clearly voting against your > own interests. Die fucking troll, Die.
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-02-01 06:03 +0000 |
| Message-ID | <vnkdg4$lha$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #181826 |
On Fri, 31 Jan 2025 23:39:47 +0100, Carlos E.R. wrote :
>> Are we discussing the label, or the volume ID?
>
> He said label :-)
Hi Carlos,
I love your suggestion because it allows us to always add more value.
As the entire point of being on Usenet is to learn & disseminate value.
SD card terminology confuses people because there are at least 3 terms:
1. Volume ID (CID)
2. Volume Serial Number
3. Volume Name (aka Volume Label)
Some can be changed by the user and some can't be changed by the user.
But what matters is only what the software sees on the Android phone.
Particularly the filespec when you double the external memory size.
But I do agree with you that the terms can be confusing to some people.
Here's an old output from Gemini which helped explain the differences:
<https://i.postimg.cc/8cYnsxDm/sdcard17.jpg>
1. Volume ID (CID):
Purpose: This is the most fundamental and permanent identifier of the
SD card. It's a unique code programmed into the card's hardware by the
manufacturer.
Format: A 128-bit (16-byte) code, often represented in hexadecimal.
How it's assigned: Assigned by the SD card manufacturer and cannot be
changed by the user.
How it's used: Used for low-level identification and tracking of the SD
card at the hardware level. It's crucial for card authentication and
security.
User-changeable? No, this is locked by the manufacturer.
2. Volume Serial Number:
Purpose: A unique numerical identifier for the SD card volume
(partition). Think of it as a fingerprint for that specific formatted
instance of the card.
Format: A 32-bit number, usually displayed as 8 hexadecimal characters
(e.g., A1B2C3D4).
How it's assigned: Generated when the SD card is formatted. It can
change if you reformat the card.
How it's used: Primarily used by the operating system for internal
identification and tracking of the SD card volume. You might see it in
system tools or when using command-line prompts.
User-changeable? Yes, you can change the volume serial number using
third-party software like AOMEI Partition Assistant, or by formatting the
card.
3. Volume Name (or Label):
Purpose: A user-friendly name that you assign to the SD card volume.
It's like giving your SD card a nickname.
Format: A string of characters (letters, numbers, spaces) that you
choose.
How it's assigned: You set the volume name when you format the card or
later through the operating system's file manager.
How it's used: Displayed in File Explorer (Windows) or Finder (Mac) to help
you easily identify your SD card.
User-changeable? Yes, you can easily change the volume name at any time
through the operating system's file manager.
Key Differences:
Permanence: The Volume ID (CID) is permanent, while the Volume Serial
Number and Volume Name can be changed.
Level: The Volume ID is at the hardware level, while the Volume Serial
Number and Volume Name are at the software (file system) level.
Purpose: The Volume ID is for secure identification, the Volume Serial
Number is for system tracking, and the Volume Name is for user convenience.
Analogy:
Imagine a library:
The Volume ID (CID) is like the library's unique registration number
for the book. It's permanent and unchangeable.
The Volume Serial Number is like the barcode on a specific copy of the
book. It's unique to that copy and might change if the copy is replaced.
The Volume Name (Label) is like the title of the book. It's
user-friendly and helps you find the book you're looking for.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-02-01 10:15 +0000 |
| Message-ID | <m06ahbFin86U1@mid.individual.net> |
| In reply to | #181836 |
Marion wrote: > SD card terminology confuses people because there are at least 3 terms: > 1. Volume ID (CID) > 2. Volume Serial Number > 3. Volume Name (aka Volume Label) > > Some can be changed by the user and some can't be changed by the user. > But what matters is only what the software sees on the Android phone. Take into account, my first Android device (Nexus1) had a microSD slot, which it certainly needed due to only having 512MB of onboard flash and 512MB of RAM, so plenty of swapfile and moving parts of the system to SD ... but no phone I've owned since then has had a card slot.
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-02-01 18:45 +0000 |
| Message-ID | <vnlq44$dar$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #181843 |
On Sat, 1 Feb 2025 10:15:04 +0000, Andy Burns wrote : > Take into account, my first Android device (Nexus1) had a microSD slot, > which it certainly needed due to only having 512MB of onboard flash and > 512MB of RAM, so plenty of swapfile and moving parts of the system to SD > ... but no phone I've owned since then has had a card slot. Hi Andy, You bring up a good point that people have to live with their decisions. With that in mind... as you're quite well aware... We've had the lack of sd discussion so many times on both the Android & on (paradoxically) the Apple newsgroups, that I'm sure you realize the last time we checked, the vast majority of Android phones have an sd card slot. With that observation that, last I had checked most Androids still have an sd slot in mind... And... without rehashing the glaringly obvious fact that it was your choice to NOT have an sd card slot... Q: How do *you* double your portable storage when you need to, Andy? A: ? You can't, right? For about $10, I (we) can. Seamlessly. As long as I (rather elegantly) plan years ahead, that is. <https://i.postimg.cc/bNGTzR6q/sdcard1.jpg> I can triple & quadruple that portable storage, any time I feel like it. You can't. Right? <https://i.postimg.cc/j2VCtRPX/sdcard02.jpg> For as many phones as I want to do it for, right? (Note: I have 3 free Samsung Galaxy A32-5Gs in my household right now.) <https://i.postimg.cc/Xq5SpS4D/tmopromo02.jpg> So, for about $30, I can double the memory of every Android in the house! You can't do *any* of that, right? Personally, unless I was made out of pure money, I wouldn't touch an Android phone that didn't have both the sd card slot & the aux jack. Please see the sig for the caveats. -- Note: We all know that Apple & Google want to push people toward storing their editing files being stored on 'someone else's computer', but this is not "portable storage" in the sense that I'm using the term. The way I'm using "Portable Storage" is in the examples I already provided, where I've replaced (twice now!) the same model phone with a free replacement under warranty where the sd card was swapped out and the editors on Android didn't even realize they were on a different phone. In addition, as Andy is also well aware, I even tested *doubling* the storage size on the third phone, and the Android editors didn't even flinch. That's the huge significance of "portable" in the term "portable storage".
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-02-01 18:51 +0000 |
| Message-ID | <vnlqg5$25jh$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #181865 |
On Sat, 1 Feb 2025 18:45:25 -0000 (UTC), Marion wrote : > <https://i.postimg.cc/Xq5SpS4D/tmopromo02.jpg> > > So, for about $30, I can double the memory of every Android in the house! > You can't do *any* of that, right? In all fairness to Andy, whom I know to be an intelligent and thoughtful person, I belatedly realize that Andy seems to think the sd card has only one purpose - which is to *extend* the memory of the Android phone. Which is a worthless concept nowadays... I agree. I partly helped Andy be confused because I interchangably used the word "storage" and "memory" where that's what threw Andy off the main track. Suffice to say that nobody (well, almost nobody) needs to "extend" the memory of their Android phone nowadays ... even I don't need to do that and all my phones are always free (just like all my Amazon purchases are free). <https://amazon.com/vine/about> What I'm talking about here, is NOT extending the memory but DOUBLING the storage (tripling the storage, quadrupling the storage, whatever). As sdcards get cheaper, I pop a new triple-sized sdcard into my phone, and Voila! Instantly all my editors have TRIPLE the storage to store files in! That's what I mean by "portable storage". Given that important clarification that it's not "memory" I'm doubling, but portable storage that I'm doubling, I can ask again Andy this question: Q: How do *you* double your portable storage when you need to, Andy? A: ? You can't, right?
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-04-27 00:07 +1000 |
| Message-ID | <vuipc2$2hj0d$1@dont-email.me> |
| In reply to | #181866 |
On 2/02/2025 5:51 am, Marion wrote: <Snip> > What I'm talking about here, is NOT extending the memory but DOUBLING the > storage (tripling the storage, quadrupling the storage, whatever). > > As sdcards get cheaper, I pop a new triple-sized sdcard into my phone, and > Voila! Instantly all my editors have TRIPLE the storage to store files in! > > That's what I mean by "portable storage". Presumably, this "portable storage" is being used by your phone (photos, SMS. whatever). When you "pop a new triple-sized sdcard into your phone", how do you get whatever information (photos, SMS. whatever) that were on the old "portable storage" onto the new "portable storage"?? -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-04-26 21:37 +0000 |
| Message-ID | <vujjmp$1p5r$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #184059 |
On Sun, 27 Apr 2025 00:07:58 +1000, Daniel70 wrote :
>> What I'm talking about here, is NOT extending the memory but DOUBLING the
>> storage (tripling the storage, quadrupling the storage, whatever).
>>
>> As sdcards get cheaper, I pop a new triple-sized sdcard into my phone, and
>> Voila! Instantly all my editors have TRIPLE the storage to store files in!
>>
>> That's what I mean by "portable storage".
>
> Presumably, this "portable storage" is being used by your phone (photos,
> SMS. whatever). When you "pop a new triple-sized sdcard into your
> phone", how do you get whatever information (photos, SMS. whatever) that
> were on the old "portable storage" onto the new "portable storage"??
Hi Daniel,
That's an insightful question, where it's my estimate that something like
one in a thousand people understand enough of portable storage in this
context to make it so convenient that it's actually seamless to do.
Most people have no idea that it's *impossible* to replicate what an sdcard
does when it comes to the inherent beauty of "portable storage" swaps.
The key is a bit of magic that only 0.1% (1/1000) of people understand.
a. You match the volume name.
b. That way, the phone doesn't even know it's a different sd card!
c. Then you copy everything over
It's that easy!
If you think ahead, you won't have to match a crazy volume name.
1. The day you get any sdcard, you format it to a given volume name.
2. I use "0000-0001" (but you can use any name you want to use for it).
3. That way, *all* your phone sdcards are completely portable among phones.
I have multiple phones in my family, all of which have their sdcard
formatted to the same volume name so all the sdcards are swappable.
Let's say, for example, all your OSMAnd map data is on the sdcard.
That will be on /sd1/0000-0001/{wherever OSMAnd puts data} right?
Let's say all your camera data is also on the external sdcard.
That will likely be in /sd1/0000-0001/DCIM right?
Let's say you have personal data that apps interact with on the sdcard.
You always put personal data in a separate-from-Android folder, right?
So that personal data will be in /sd1/0000-0001/0001/{your data} right?
Note: You can pick any unused name for your top-level personal data folder.
I pick /sd0/0000 for the internal sdcard, and 0001 for the external.
that way, when I'm looking at the card from the PC, I instantly know which
is which as the hierarchy looks similar between sd0 and sd1 file systems.
If you haven't thought ahead though, you can still swap cards.
A. Your 64GB sdcard is full, so you buy a 256GB sdcard to replace it.
B. You determine the 64GB sdcard volume label is ABCD-1234 (for example).
C. You format the 256GB sdcard to the *same volume label* (this is key!).
D. Then you plug in the phone over USB to the PC which exposes the sdcard.
E. You connect the brand new 256GB sdcard to the PC (usually via a slot).
F. You COPY the 64GB sdcard contents over to the 128GB sdcard
G. You turn off the phone & swap the two cards & reboot
The phone doesn't even realize you've quadrupled your portable storage!
Note that you'd think there must be protected files on the sdcard, right?
In my experience, there is not (e.g., OSMAnd has no problem with the swap).
However, if you were worried about "protected data" on the external sdcard,
popping it out of the phone would solve that problem instantly, right?
But in my experience, none of the data on the external sdcard has been
protected (or if it was protected, I saw no hiccups in the swap).
In summary, those poor people on iPhones who have crappy substandard
hardware, and even those suckers on Android with substandard hardware, have
to pay more than a phone costs (over time) just for the privilege of being
able to store 64GB to 256GB (or any amount) of storage on the cloud.
Since I'm a kind-hearted purposefully helpful person, let me know if you
have any questions, as I've done this portable storage swap many times.
--
Note in the beginning I didn't know enough to format to the same volume
name, and I also didn't know enough to put all my user data in one place.
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-04-27 20:23 +1000 |
| Message-ID | <vul0jg$jn41$1@dont-email.me> |
| In reply to | #184079 |
On 27/04/2025 7:37 am, Marion wrote: > On Sun, 27 Apr 2025 00:07:58 +1000, Daniel70 wrote : > >>> What I'm talking about here, is NOT extending the memory but DOUBLING the >>> storage (tripling the storage, quadrupling the storage, whatever). >>> >>> As sdcards get cheaper, I pop a new triple-sized sdcard into my phone, and >>> Voila! Instantly all my editors have TRIPLE the storage to store files in! >>> >>> That's what I mean by "portable storage". >> >> Presumably, this "portable storage" is being used by your phone (photos, >> SMS. whatever). When you "pop a new triple-sized sdcard into your >> phone", how do you get whatever information (photos, SMS. whatever) that >> were on the old "portable storage" onto the new "portable storage"?? > > Hi Daniel, > > That's an insightful question, where it's my estimate that something like > one in a thousand people understand enough of portable storage in this > context to make it so convenient that it's actually seamless to do. Thank you for your detailed response. My query stemmed from my 'belief' that you were working with just the phone and the old and new SD Cards. Only one SD plugged in at a time so how did you get data from one to the other ..... unless you removed the "Phone System" SD (losing the phone function, maybe), plugged in the "new" SD then did the tranfer from "old" SD content to "new" SD then reorganised things so you could plug in the "Phone System" SD again. -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-04-27 14:15 +0000 |
| Message-ID | <vule65$31a2$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #184096 |
On Sun, 27 Apr 2025 20:23:42 +1000, Daniel70 wrote : >> That's an insightful question, where it's my estimate that something like >> one in a thousand people understand enough of portable storage in this >> context to make it so convenient that it's actually seamless to do. > > Thank you for your detailed response. > > My query stemmed from my 'belief' that you were working with just the > phone and the old and new SD Cards. Only one SD plugged in at a time so > how did you get data from one to the other ..... unless you removed the > "Phone System" SD (losing the phone function, maybe), plugged in the > "new" SD then did the tranfer from "old" SD content to "new" SD then > reorganised things so you could plug in the "Phone System" SD again. You don't have a PC? Where do you live? On Mount Everest? If you're in the middle of nowhere, then you use the clusterfuck method. You know the clusterfuck method. It's what Apple sells all day every day. Everest is at ~30K feet & the lowest comms satellites are ~350 miles. A round trip is about 700 miles but you have to add the server connection. So let's just count it at 4 hops of ~350 miles which is ~1500 miles. Instead of going a few inches back and forth in two hops to your PC, what you seem to be proposing is about 1500 miles to do the same thing? I get it that all Apple owners think nothing of that clusterfuck. But it's one of the reasons Apple users are so paranoid about encryption. But, you're the one asking the questions, so here's your rightful answer. I get it that your situation is you sit on top of Mount Everest, which is as far as you can get from your home PC, so you have only the Internet. Step one of the Apple clusterfuck is you purchase 64GB of cloud storage. Don't forget that step because it's part of why Apple is so profitable. Then, since you have no access to anything but the Internet (which is how the Apple clusterfuck method works, as you must be aware of by now), you upload to the satellite your 64GB of data from the top of Mount Everest. Luckily, that's the SHORTEST distance that the Apple clusterfuck works at. But that's only one hop of 350 miles because the satellite has to log into the Cupertino matrix to store your 64GB of data on that sd card, right? So your precious private data just went 700 miles to be on the cloud. Then you shut the phone; swap out the sd cards; and boot the phone back. And then you download back the 64 GB of data stored on the Apple cloud. That's another two hops, so add another 700 miles for your private data. (And a bunch of Internet hosts in between, some of whom are nefarious). Voila! After pushing your data 700 miles and pulling it back another 700 miles, you have successfully completed an Apple clusterfuck round trip for data. Instead of copying your private data directly the few inches from your PC. Congratulations.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-02-01 14:55 +0100 |
| Message-ID | <6ol17lxpiu.ln2@Telcontar.valinor> |
| In reply to | #181836 |
On 2025-02-01 07:03, Marion wrote: > On Fri, 31 Jan 2025 23:39:47 +0100, Carlos E.R. wrote : > > >>> Are we discussing the label, or the volume ID? >> >> He said label :-) > > Hi Carlos, > > I love your suggestion because it allows us to always add more value. > As the entire point of being on Usenet is to learn & disseminate value. > > SD card terminology confuses people because there are at least 3 terms: > 1. Volume ID (CID) > 2. Volume Serial Number > 3. Volume Name (aka Volume Label) You can change them in Linux. Going from memory, one of them you change in the partitioner (fdisk). This one was crucial with Windows 7 because M$ would use it to detect machine change or pirated copy. All these changes can be done without formatting and losing the content. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
Back to top | Article view | alt.comp.os.windows-10
csiph-web