Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #146542 > 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 194 — 17 participants |
Back to article view | Back to comp.mobile.android
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 Andy Burns <usenet@andyburns.uk> - 2025-02-01 19:17 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 20:43 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-01 19:57 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-02-01 20:18 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 21:36 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Frank Slootweg <this@ddress.is.invalid> - 2025-02-02 11:39 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 19:56 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-01 21:42 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 05:11 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 14:41 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 18:20 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors AJL <noemail@none.com> - 2025-02-02 13:20 -0700
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 22:28 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors AJL <noemail@none.com> - 2025-02-02 17:01 -0700
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 08:13 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors AJL <noemail@none.com> - 2025-02-03 05:19 -0700
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-03 19:01 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors "Carlos E.R." <robin_listas@es.invalid> - 2025-02-02 23:20 +0100
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-02 22:51 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Andy Burns <usenet@andyburns.uk> - 2025-02-02 14:08 +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 Andy Burns <usenet@andyburns.uk> - 2025-02-01 19:09 +0000
Re: Clever helpful suggestion for portable memory using Windows & Android editors Marion <marion@facts.com> - 2025-02-01 19:38 +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: Clever helpful suggestion for portable memory using Windows & Android editors mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) - 2025-02-04 21:10 +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 5 of 10 — ← Prev page 1 … 3 4 [5] 6 7 … 10 Next page →
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-18 21:55 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vp2vki$1t1e6$3@dont-email.me> |
| In reply to | #146823 |
On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: > Lawrence D'Oliveiro, 2025-02-13 23:15: > >> On Thu, 13 Feb 2025 19:59:35 +0100, Arno Welzel wrote: >> >>> Lawrence D'Oliveiro, 2025-02-11 02:00: >>> >>>> On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: >>>> >>>>> Lawrence D'Oliveiro, 2025-02-09 00:35: >>>>> >>>>>> So you never used core memory. >>>>> >>>>> Correct. But core memory is not intended as *persistent* memory, even >>>>> when it can be used this way. >>>> >>>> It was indeed regularly used that way. Consider that, on machines from >>>> the core memory era ... >>> >>> Anyway - the memory was "RAM" and not "mass storage". >> >> Neither term was used back then. I certainly didn’t use them in this >> context. > > It does not matter, if you use that term. I talk about the real world > usage. So was I. > And core memory is not *intended* to be non volatile storage ... It did work that way, you know. By design.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2025-02-21 09:12 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <m1qqqmF717U1@mid.individual.net> |
| In reply to | #146827 |
Lawrence D'Oliveiro, 2025-02-18 22:55: > On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: [...] >> And core memory is not *intended* to be non volatile storage ... > > It did work that way, you know. By design. Which is irrelevant for what I said. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-21 23:35 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpb2k5$3kapt$3@dont-email.me> |
| In reply to | #146851 |
On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: > Lawrence D'Oliveiro, 2025-02-18 22:55: > >> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: > [...] >>> And core memory is not *intended* to be non volatile storage ... >> >> It did work that way, you know. By design. > > Which is irrelevant for what I said. You said it wasn’t intended to be non-volatile. But it was.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2025-02-25 18:27 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <m26cs6Fn5c8U1@mid.individual.net> |
| In reply to | #146858 |
Lawrence D'Oliveiro, 2025-02-22 00:35: > On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: > >> Lawrence D'Oliveiro, 2025-02-18 22:55: >> >>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: >> [...] >>>> And core memory is not *intended* to be non volatile storage ... >>> >>> It did work that way, you know. By design. >> >> Which is irrelevant for what I said. > > You said it wasn’t intended to be non-volatile. But it was. No, it wasn't. This was just the side-effect of using magnetic cores. If any other technology would have been as cheap and fast as core memory, it would have been used. As soon as *non-volatile* integrated circuits became cheaper, they replaced core memory within a few years, because the proporty "non volatile" was not the important thing. Instead having a lot of cheap RAM was much more important - also when core memory was invented. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-02-25 18:25 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpl5ed.sug.1@ID-201911.user.individual.net> |
| In reply to | #146868 |
Arno Welzel <usenet@arnowelzel.de> wrote: > Lawrence D'Oliveiro, 2025-02-22 00:35: > > > On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: > > > >> Lawrence D'Oliveiro, 2025-02-18 22:55: > >> > >>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: > >> [...] > >>>> And core memory is not *intended* to be non volatile storage ... > >>> > >>> It did work that way, you know. By design. > >> > >> Which is irrelevant for what I said. > > > > You said it wasn?t intended to be non-volatile. But it was. > > No, it wasn't. This was just the side-effect of using magnetic cores. Sorry, but that's nonsense. I gave some examples from that era, where non-volatility was not a 'side-effect', but an essential property without which the system(s) couldn't function,, especially in the abscence of on-line mass-storage. > If > any other technology would have been as cheap and fast as core memory, > it would have been used. That's just your opinion, not a fact. Anyway neither of 'us' can prove that either way. > As soon as *non-volatile* integrated circuits became cheaper, they > replaced core memory within a few years, because the proporty "non > volatile" was not the important thing. Instead having a lot of cheap RAM > was much more important - also when core memory was invented. I think you mean "*volatile* integrated circuits", otherwise the rest of your comments do not make any sense. And indeed, after the second generation HP computers with core memory (2100), the third generation (21MX) had volatile RAM with ICs.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2025-02-26 08:53 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <m27vjfFud22U2@mid.individual.net> |
| In reply to | #146869 |
Frank Slootweg, 2025-02-25 19:25: > Arno Welzel <usenet@arnowelzel.de> wrote: >> Lawrence D'Oliveiro, 2025-02-22 00:35: >> >>> On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: >>> >>>> Lawrence D'Oliveiro, 2025-02-18 22:55: >>>> >>>>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: >>>> [...] >>>>>> And core memory is not *intended* to be non volatile storage ... >>>>> >>>>> It did work that way, you know. By design. >>>> >>>> Which is irrelevant for what I said. >>> >>> You said it wasn?t intended to be non-volatile. But it was. >> >> No, it wasn't. This was just the side-effect of using magnetic cores. > > Sorry, but that's nonsense. I gave some examples from that era, where > non-volatility was not a 'side-effect', but an essential property > without which the system(s) couldn't function,, especially in the > abscence of on-line mass-storage. If a property exists in a technology, it is used - of course. But this does not mean, that a technology was especially designed for this use case. >> As soon as *non-volatile* integrated circuits became cheaper, they >> replaced core memory within a few years, because the proporty "non >> volatile" was not the important thing. Instead having a lot of cheap RAM >> was much more important - also when core memory was invented. > > I think you mean "*volatile* integrated circuits", otherwise the rest > of your comments do not make any sense. And indeed, after the second > generation HP computers with core memory (2100), the third generation > (21MX) had volatile RAM with ICs. Exactly - *volatile* memory chips replaced core memory when they got available and cheaper than core memory, because implementing RAM was the main use case for core memory and not the fact, that it is non-volatile. Even machines with core memory still had some kind of external storage (punched tape, magnetic tape, drum memory etc.) because you still need some kind of permanent storage even with core memory. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Janis Papanagnou <janis_papanagnou+ng@hotmail.com> |
|---|---|
| Date | 2025-02-26 13:10 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpn0ci$2i7ne$1@dont-email.me> |
| In reply to | #146875 |
On 26.02.2025 08:53, Arno Welzel wrote: >> [...] > [...] > > Even machines with core memory still had some kind of external storage > (punched tape, magnetic tape, drum memory etc.) because you still need > some kind of permanent storage even with core memory. Yes, sort of. - It's not that simple, though... External permanent storage was also used because of its "mass storage" property. Consider for example large amounts of data to be processed using tapes; some algorithms like 'merge-sort' still reflect that. And drums were (AFAICT) used as (compared to hard disks) fast-access memory not as permanent storage; their capacity was not that large but they had a lot of fixed heads to read/write data in parallel. As mentioned elsethread; the storage properties define their possible uses, and there are a lot more properties than permanent/volatile. Janis
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-02-26 15:02 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpndtq.egk.1@ID-201911.user.individual.net> |
| In reply to | #146875 |
Arno Welzel <usenet@arnowelzel.de> wrote: > Frank Slootweg, 2025-02-25 19:25: > > > Arno Welzel <usenet@arnowelzel.de> wrote: > >> Lawrence D'Oliveiro, 2025-02-22 00:35: > >> > >>> On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: > >>> > >>>> Lawrence D'Oliveiro, 2025-02-18 22:55: > >>>> > >>>>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: > >>>> [...] > >>>>>> And core memory is not *intended* to be non volatile storage ... > >>>>> > >>>>> It did work that way, you know. By design. > >>>> > >>>> Which is irrelevant for what I said. > >>> > >>> You said it wasn?t intended to be non-volatile. But it was. > >> > >> No, it wasn't. This was just the side-effect of using magnetic cores. > > > > Sorry, but that's nonsense. I gave some examples from that era, where > > non-volatility was not a 'side-effect', but an essential property > > without which the system(s) couldn't function,, especially in the > > abscence of on-line mass-storage. > > If a property exists in a technology, it is used - of course. But this > does not mean, that a technology was especially designed for this use case. Nor does it mean it was *not* designed for this use case. As I mentioned, and you conventienly snipped: "That's just your opinion, not a fact. Anyway neither of 'us' can prove that either way." > >> As soon as *non-volatile* integrated circuits became cheaper, they > >> replaced core memory within a few years, because the proporty "non > >> volatile" was not the important thing. Instead having a lot of cheap RAM > >> was much more important - also when core memory was invented. > > > > I think you mean "*volatile* integrated circuits", otherwise the rest > > of your comments do not make any sense. And indeed, after the second > > generation HP computers with core memory (2100), the third generation > > (21MX) had volatile RAM with ICs. > > Exactly - *volatile* memory chips replaced core memory when they got > available and cheaper than core memory, because implementing RAM was the > main use case for core memory and not the fact, that it is non-volatile. Disagree. I that same period, less expensive mass storage became available, so volatile RAM was less of a problem. N.B. When the first HP computer (2116) came out, there was *no* mass storage device available. That (2757A) came two years later. The 21MX (volatile RAM) came eight years after the 2116 (core memory). > Even machines with core memory still had some kind of external storage > (punched tape, magnetic tape, drum memory etc.) because you still need > some kind of permanent storage even with core memory. Yes, but as I explained, they only needed that external storage *once* to load and for the rest only to save/load the program, not the OS. Mag tape, drum memory, etc. are seperate cases, they are not just to load the OS and save/load programs, but also for mass storage. The systems I mentioned, only used paper tape and magnetic cards. Anyway. let's drop this silly (non-)discussion. As I said, it's just a matter of opinion and we're not going to agree.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-02-25 20:28 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpl95m$25q46$2@dont-email.me> |
| In reply to | #146868 |
On Tue, 25 Feb 2025 18:27:39 +0100, Arno Welzel wrote: > Lawrence D'Oliveiro, 2025-02-22 00:35: > >> On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: >> >>> Lawrence D'Oliveiro, 2025-02-18 22:55: >>> >>>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: >>> [...] >>>>> And core memory is not *intended* to be non volatile storage ... >>>> >>>> It did work that way, you know. By design. >>> >>> Which is irrelevant for what I said. >> >> You said it wasn’t intended to be non-volatile. But it was. > > No, it wasn't. It was non-volatile. That is a matter of indisputable fact. > As soon as *non-volatile* integrated circuits became cheaper, they > replaced core memory within a few years ... Why wait for *non-volatile* ones? If the non-volatility was not important, the replacement would have happened sooner.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2025-02-26 08:54 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <m27vkoFud22U3@mid.individual.net> |
| In reply to | #146872 |
Lawrence D'Oliveiro, 2025-02-25 21:28: > On Tue, 25 Feb 2025 18:27:39 +0100, Arno Welzel wrote: > >> Lawrence D'Oliveiro, 2025-02-22 00:35: >> >>> On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: >>> >>>> Lawrence D'Oliveiro, 2025-02-18 22:55: >>>> >>>>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: >>>> [...] >>>>>> And core memory is not *intended* to be non volatile storage ... >>>>> >>>>> It did work that way, you know. By design. >>>> >>>> Which is irrelevant for what I said. >>> >>> You said it wasn’t intended to be non-volatile. But it was. >> >> No, it wasn't. > > It was non-volatile. That is a matter of indisputable fact. > >> As soon as *non-volatile* integrated circuits became cheaper, they >> replaced core memory within a few years ... > > Why wait for *non-volatile* ones? If the non-volatility was not important, > the replacement would have happened sooner. No, *volatile* of course. I was just not checking my text before sending it. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2025-02-26 08:49 +0100 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <m27vbdFud22U1@mid.individual.net> |
| In reply to | #146868 |
Arno Welzel, 2025-02-25 18:27: > Lawrence D'Oliveiro, 2025-02-22 00:35: > >> On Fri, 21 Feb 2025 09:12:09 +0100, Arno Welzel wrote: >> >>> Lawrence D'Oliveiro, 2025-02-18 22:55: >>> >>>> On Tue, 18 Feb 2025 11:56:41 +0100, Arno Welzel wrote: >>> [...] >>>>> And core memory is not *intended* to be non volatile storage ... >>>> >>>> It did work that way, you know. By design. >>> >>> Which is irrelevant for what I said. >> >> You said it wasn’t intended to be non-volatile. But it was. > > No, it wasn't. This was just the side-effect of using magnetic cores. If > any other technology would have been as cheap and fast as core memory, > it would have been used. > > As soon as *non-volatile* integrated circuits became cheaper, they ... *volatile* of course ... > replaced core memory within a few years, because the proporty "non > volatile" was not the important thing. Instead having a lot of cheap RAM > was much more important - also when core memory was invented. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-02-21 14:12 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vpa557.p90.1@ID-201911.user.individual.net> |
| In reply to | #146823 |
Arno Welzel <usenet@arnowelzel.de> wrote: > Lawrence D'Oliveiro, 2025-02-13 23:15: > > > On Thu, 13 Feb 2025 19:59:35 +0100, Arno Welzel wrote: > > > >> Lawrence D'Oliveiro, 2025-02-11 02:00: > >> > >>> On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: > >>> > >>>> Lawrence D'Oliveiro, 2025-02-09 00:35: > >>>> > >>>>> So you never used core memory. > >>>> > >>>> Correct. But core memory is not intended as *persistent* memory, even > >>>> when it can be used this way. > >>> > >>> It was indeed regularly used that way. Consider that, on machines from > >>> the core memory era ... > >> > >> Anyway - the memory was "RAM" and not "mass storage". > > > > Neither term was used back then. I certainly didn?t use them in this > > context. > > It does not matter, if you use that term. I talk about the real world > usage. And core memory is not *intended* to be non volatile storage, > even if it is technically possible to keep information without powering > the memory. Well, we (HP) sold computers (2116/2115/2114) with BASIC, were the core memory kept the 'OS', the interpreter and the user's program(s). They did not have mass storage, only paper tape for the intitial load of OS/interpreter and to save/load programs. Same for the 9100A/B 'calculator's of the time. Program and data in core memory. Yes, program and data could be loaded from and saved to creditcard-sized magnetic cards, but core memory was definitely intended to be non volatile storage.
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-05-14 21:34 +1000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <1001v4m$2ftun$1@dont-email.me> |
| In reply to | #146753 |
On 11/02/2025 12:00 pm, Lawrence D'Oliveiro wrote: > On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: >> Lawrence D'Oliveiro, 2025-02-09 00:35: >> >>> So you never used core memory. >> >> Correct. But core memory is not intended as *persistent* memory, >> even when it can be used this way. > > It was indeed regularly used that way. Consider that, on machines > from the core memory era, there was no “boot ROM”. The first-stage > bootloader was typically around a dozen machine instructions or so, > which had to be hand- entered using front-panel switches. I remember having to do that on a PDP-8 (was it??) in 1982-3. > (No doubt seasoned operators had this memorized.) It was handy that > this could be preserved across power cycles, assuming it didn’t get > overwritten by some wayward buggy program. > > Then there were applications that ran without an OS as such. For > example, on the PDP-8, you could load a BASIC interpreter. This would > take about 20 minutes to load off paper tape. So the fact that a > power cycle did not wipe memory was helpful if you had a lot of BASIC > programs to run. > -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-14 12:54 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <1002ar6.tqk.1@ID-201911.user.individual.net> |
| In reply to | #148408 |
Daniel70 <daniel47@eternal-september.org> wrote: > On 11/02/2025 12:00 pm, Lawrence D'Oliveiro wrote: > > On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: > >> Lawrence D'Oliveiro, 2025-02-09 00:35: > >> > >>> So you never used core memory. > >> > >> Correct. But core memory is not intended as *persistent* memory, > >> even when it can be used this way. > > > > It was indeed regularly used that way. Consider that, on machines > > from the core memory era, there was no ?boot ROM?. The first-stage > > bootloader was typically around a dozen machine instructions or so, > > which had to be hand- entered using front-panel switches. > > I remember having to do that on a PDP-8 (was it??) in 1982-3. That seems rather late! I used similar machines ((16-bit instead of 12-bit) HP2116 and later) and toggling the precursor to the BBL (Basic Binary Loader) in the late 60s, early 70s. In 1982, I was already using 32-bit (HP) Unix machines which had firmware bootloaders and also the earlier/same_time 16-bit HP RTE (Real Time Executive) machines had firmware bootloaders many years before that. > > (No doubt seasoned operators had this memorized.) It was handy that > > this could be preserved across power cycles, assuming it didn?t get > > overwritten by some wayward buggy program. > > > > Then there were applications that ran without an OS as such. For > > example, on the PDP-8, you could load a BASIC interpreter. This would > > take about 20 minutes to load off paper tape. So the fact that a > > power cycle did not wipe memory was helpful if you had a lot of BASIC > > programs to run.
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-05-16 21:29 +1000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <10077j8$3o72v$1@dont-email.me> |
| In reply to | #148411 |
On 14/05/2025 10:54 pm, Frank Slootweg wrote: > Daniel70 <daniel47@eternal-september.org> wrote: >> On 11/02/2025 12:00 pm, Lawrence D'Oliveiro wrote: >>> On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: >>>> Lawrence D'Oliveiro, 2025-02-09 00:35: >>>> >>>>> So you never used core memory. >>>> >>>> Correct. But core memory is not intended as *persistent* memory, >>>> even when it can be used this way. >>> >>> It was indeed regularly used that way. Consider that, on machines >>> from the core memory era, there was no ?boot ROM?. The first-stage >>> bootloader was typically around a dozen machine instructions or so, >>> which had to be hand- entered using front-panel switches. >> >> I remember having to do that on a PDP-8 (was it??) in 1982-3. > > That seems rather late! For computing, yes, that might seem rather late ... but for its purpose (Training us in how an Aust Army Direction Finding system worked) it was quite reasonable. I don't know what the actual DF system used. -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-16 14:13 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <1007o7u.4d8.1@ID-201911.user.individual.net> |
| In reply to | #148478 |
Daniel70 <daniel47@eternal-september.org> wrote: > On 14/05/2025 10:54 pm, Frank Slootweg wrote: > > Daniel70 <daniel47@eternal-september.org> wrote: > >> On 11/02/2025 12:00 pm, Lawrence D'Oliveiro wrote: > >>> On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: > >>>> Lawrence D'Oliveiro, 2025-02-09 00:35: > >>>> > >>>>> So you never used core memory. > >>>> > >>>> Correct. But core memory is not intended as *persistent* memory, > >>>> even when it can be used this way. > >>> > >>> It was indeed regularly used that way. Consider that, on machines > >>> from the core memory era, there was no ?boot ROM?. The first-stage > >>> bootloader was typically around a dozen machine instructions or so, > >>> which had to be hand- entered using front-panel switches. > >> > >> I remember having to do that on a PDP-8 (was it??) in 1982-3. > > > > That seems rather late! > > For computing, yes, that might seem rather late ... but for its purpose > (Training us in how an Aust Army Direction Finding system worked) it was > quite reasonable. I don't know what the actual DF system used. I see! Yes. Defense Force systems have a very long lifecycle. In aerospace even longer, for obvious reasons. They used HP 21MX (16-bit) mini-computers in some missiles. At the time, it felt rather strange, letting an expensive computer self-destruct. Sadly enough, these days it's no longer strange at all! :-(
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-05-17 21:00 +1000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <1009q9c$c062$1@dont-email.me> |
| In reply to | #148480 |
On 17/05/2025 12:13 am, Frank Slootweg wrote: > Daniel70 <daniel47@eternal-september.org> wrote: >> On 14/05/2025 10:54 pm, Frank Slootweg wrote: >>> Daniel70 <daniel47@eternal-september.org> wrote: >>>> On 11/02/2025 12:00 pm, Lawrence D'Oliveiro wrote: >>>>> On Mon, 10 Feb 2025 08:47:39 +0100, Arno Welzel wrote: >>>>>> Lawrence D'Oliveiro, 2025-02-09 00:35: >>>>>> >>>>>>> So you never used core memory. >>>>>> >>>>>> Correct. But core memory is not intended as *persistent* >>>>>> memory, even when it can be used this way. >>>>> >>>>> It was indeed regularly used that way. Consider that, on >>>>> machines from the core memory era, there was no ?boot ROM?. >>>>> The first-stage bootloader was typically around a dozen >>>>> machine instructions or so, which had to be hand- entered >>>>> using front-panel switches. >>>> >>>> I remember having to do that on a PDP-8 (was it??) in 1982-3. >>> >>> That seems rather late! >> >> For computing, yes, that might seem rather late ... but for its >> purpose (Training us in how an Aust Army Direction Finding system >> worked) it was quite reasonable. I don't know what the actual DF >> system used. > > I see! Yes. Defense Force systems have a very long lifecycle. In > aerospace even longer, for obvious reasons. > > They used HP 21MX (16-bit) mini-computers in some missiles. At the > time, it felt rather strange, letting an expensive computer > self-destruct. Sadly enough, these days it's no longer strange at > all! :-( > Hey, if that missile is aimed at my next door neighbour, I'm glad they are allowing those "expensive computers" to self-destruct. ;-P -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | Daniel70 <daniel47@eternal-september.org> |
|---|---|
| Date | 2025-04-27 20:27 +1000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vul0r0$jn41$2@dont-email.me> |
| In reply to | #146630 |
On 4/02/2025 12:09 am, Kenny McCormack wrote: > In article <m0br40Ff8v9U2@mid.individual.net>, Arno Welzel > <usenet@arnowelzel.de> wrote: ... >>> I don't call an SSD a flash media. >> >> Why not? SSD *is* flash storage. Just because there is a >> controller which takes care of wear leveling, the storage >> technology itself is not different to that of SD cards. > > Chill out, man. > > People often use terminology in idiosyncratic ways. .... which CAN lead to mis-understandings!! > That doesn't make them wrong. I understand Carlo's frame of > reference, and I accept it. You should do likewise. > > Just for one example: In some circles, unless it is a 4 footed > mammal, it is not an "animal". > > I assume Carlo's use of terminology is similar. > Do you recall the saying about what could happen when one "assume"?? -- Daniel70
[toc] | [prev] | [next] | [standalone]
| From | gazelle@shell.xmission.com (Kenny McCormack) |
|---|---|
| Date | 2025-04-27 10:29 +0000 |
| Subject | Re: What is an animal or an SSD drive? (Was: blah, blah, blah) Android editors |
| Message-ID | <vul0uj$2cd1f$1@news.xmission.com> |
| In reply to | #148183 |
In article <vul0r0$jn41$2@dont-email.me>, Daniel70 <daniel47@eternal-september.org> wrote: ... >> Chill out, man. >> >> People often use terminology in idiosyncratic ways. > >.... which CAN lead to mis-understandings!! Most (if not all) of the so-called "misunderstandings" are intentional. I.e., intentional strawmanning. -- Republican Congressman Matt Gaetz claims that only ugly women want abortions, which they will never need since no one will impregnate them.
[toc] | [prev] | [next] | [standalone]
| From | Marion <marion@facts.com> |
|---|---|
| Date | 2025-02-02 04:16 +0000 |
| Message-ID | <vnmrj0$2jq6$1@nnrp.usenet.blueworldhosting.com> |
| In reply to | #146577 |
On Sat, 1 Feb 2025 20:54:19 +0100, Carlos E.R. wrote : >> The editor has no clue that you just swapped out the sd card to a new one! >> But, of course, the editor has to prior be aware of storage on the sd card. > > I don't use editors on phone nor tablet. Hi Carlos, If you don't ever use editors on a mobile device, then that's unusual. Most people experience using editors on a mobile device, even if you don't. But I find it hard to believe you don't use editors on a mobile device. You don't use offline maps for example? Really? Seriously? How do you navigate using your phone when there is no Internet signal? Offline map editors are just one type of editor on an Android phone. I, for one, do a lot of editing on an Android phone. Another editor is Keepass2Android. There are plenty of Android editors. Most (if not almost all) my private data is stored on the sd card. > And, my editor by default inserts photos inside the document file. Photo editors are a different breed of app when it comes to "finding" their files. I'm not sure *how* media is handled differently than, oh, say, text files such as GPX files or PDF files or whatever - but there is some "magic" on a phone that seems to find all media, no matter where it is. So media (such as images & video) I think is a special case in this regard. That is, even if you changed the volume name (aka volume label) of your sd card, the image & video editors still seem to *find* the sd card files. If those on this newsgroup can edify us as to why that magic only works for media files, and not for, oh, say, text files (such as GPX files), please elucidate why other formats (such as PDF, gpx, kml, etc.) aren't easily found. > I can > link to external photos, but then, as I use Linux, I would use relative > paths or symlinks. I love your suggestion of symlinks, but as I painstakingly explained, nobody yet has proposed a way to do it that I know of, for Android. If you can get symlinks to work on the sdcard for Android, you'd be a far more intelligent man than I am, so I'll patiently await how you do it. > Also I *never* edit a file residing in flash storage. I edit in main > storage in the computer, then copy the result over to flash media if needed. Hmm... how do you edit GPX or KML files? Do you copy them from the sd storage to main storage just to edit them? Why? >> I feel sorry for people who don't have Android phones with sd card slots. >> Because if they want to double their portable storage, they can't. > > I haven't had that need in over a decade. Hmm. If you have never done it, and if all your suggestions can't possibly work, why are you making those suggestions which have no hope of working? >> Ignoring that the Volume ID is not changeable by the user, and hence has no >> value to us in controlling how Android editors find their sd card files... >> To your point of being easily able to change the other two using Windows >> (or Linux), why would you want to change the Volume Serial Number? >> Is there some value that you see in doing that which I don't yet comprehend >> which makes doing so of value in terms of controlling Android file editors? > > Fooling Windows into thinking you have not changed computer. Windows > used that value for finding pirated copies. Hmm... you seem to be completely unaware of what the problem set is. The problem set is fooling Android. Specifically editors. By using Windows. > Also you need to write those values when cloning hard disks (or flash > media). Huh? Nobody is suggesting cloning. This solution only requires copying. Cloning, e.g., using dd, is a completely different issue altogether: sudo dd if=/dev/source_disk of=/dev/destination_disk bs=4M status=progress > Storage cards are formatted the same as a hard disk. They contain > partition tables, and all the identifiers of a hard disk and the > partitions inside. And all the tools Windows or Linux have available for > hard disks will work on them. Again, I love your suggestion of symlinks, which is the first thing anyone would think of, but if you can get symlinks to work on non-rooted Android for the sdcard, then you're a far more intelligent man than I am. Please let us know how you accomplished tasks which you keep suggesting.
[toc] | [prev] | [next] | [standalone]
Page 5 of 10 — ← Prev page 1 … 3 4 [5] 6 7 … 10 Next page →
Back to top | Article view | comp.mobile.android
csiph-web