Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #683622 > unrolled thread
| Started by | CrudeSausage <crude@sausa.ge> |
|---|---|
| First post | 2025-01-10 12:37 -0500 |
| Last post | 2025-01-16 11:35 -0500 |
| Articles | 20 on this page of 186 — 27 participants |
Back to article view | Back to comp.os.linux.advocacy
Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-10 12:37 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-10 12:43 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-10 13:59 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-11 09:30 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-11 07:30 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-20 16:39 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-20 20:39 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs chrisv <chrisv@nospam.invalid> - 2025-01-21 06:05 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-21 08:49 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-10 20:14 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-01-10 16:35 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-11 09:31 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-11 12:15 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-12 23:20 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-13 12:45 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-13 22:50 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-21 22:43 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-10 12:54 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-11 09:27 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-11 04:32 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-11 07:38 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-11 07:28 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-12 08:38 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-12 09:36 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-13 12:40 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-13 10:05 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-11 20:11 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-11 17:28 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-12 08:40 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-12 09:55 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-13 12:44 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-12 08:39 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-12 23:23 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs MikeS <MikeS@fred.com> - 2025-01-13 21:25 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-13 16:32 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-13 17:44 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-13 17:54 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-13 18:10 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-13 18:25 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Hank Rogers <Hank@nospam.invalid> - 2025-01-13 17:52 -0600
Cult of Unix (was: Re: Microsoft to force new Outlook on Windows 10 PCs) vallor <vallor@cultnix.org> - 2025-01-15 00:30 +0000
Re: Cult of Unix Hank Rogers <Hank@nospam.invalid> - 2025-01-14 20:05 -0600
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-15 03:16 -0500
Re: Cult of Unix vallor <vallor@cultnix.org> - 2025-01-15 09:02 +0000
Re: Cult of Unix ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2025-01-15 11:10 -0700
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-16 05:03 +0000
Re: 🏳️🌈Cult of Unix🏳️🌈 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Dershmender 💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> - 2025-01-16 05:28 +0000
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-16 10:34 -0500
Re: Cult of Unix vallor <vallor@cultnix.org> - 2025-01-16 16:04 +0000
Re: Cult of Unix Hank Rogers <Hank@nospam.invalid> - 2025-01-16 14:48 -0600
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-16 18:06 -0500
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 02:49 +0000
Re: Cult of Unix vallor <vallor@cultnix.org> - 2025-01-17 03:51 +0000
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-17 02:10 -0500
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 23:55 +0000
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-17 20:53 -0500
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-19 00:54 +0000
Re: Cult of Unix Frank Slootweg <this@ddress.is.invalid> - 2025-01-17 16:46 +0000
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 23:56 +0000
Re: Cult of Unix Paul <nospam@needed.invalid> - 2025-01-17 20:54 -0500
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-19 00:55 +0000
Re: Cult of Unix Joel <joelcrump@gmail.com> - 2025-01-18 20:01 -0500
Re: Cult of Unix Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 00:10 +0000
Re: 🏳️🌈Cult of Unix (was: Re: Microsoft to force new Outlook on Windows 10 PCs)🏳️🌈 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Dershmender 💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> - 2025-01-15 05:24 +0000
Setting up old-style backup on Windows 11 (was: Re: Cult of Unix) vallor <vallor@cultnix.org> - 2025-01-15 08:38 +0000
Re: 🏳️🌈Setting up old-style backup on Windows 11 (was: Re: Cult of Unix)🏳️🌈 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Dershmender 💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> - 2025-01-15 17:22 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-13 21:44 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Manu Raju <MR@invalid.invalid> - 2025-01-14 03:09 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-15 06:56 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-15 02:52 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 00:11 +0000
Defragging (was: Re: Microsoft to force new Outlook on Windows 10 PCs) vallor <vallor@cultnix.org> - 2025-01-17 03:45 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 23:10 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-15 10:40 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-15 23:14 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-15 20:15 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs pothead <pothead@snakebite.com> - 2025-01-16 01:29 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-17 05:05 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-17 08:53 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-17 10:43 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-17 11:07 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-17 17:19 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-17 18:17 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-20 16:40 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-20 20:41 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-17 17:18 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-17 18:15 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-18 13:07 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-18 16:08 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-18 17:22 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-18 23:30 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-18 19:04 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-19 04:40 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-18 18:50 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-18 19:08 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-18 21:10 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-18 22:14 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 11:38 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-19 12:23 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 12:32 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-19 15:54 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 15:59 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-19 18:44 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 20:28 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-19 21:10 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 22:22 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-19 07:22 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-19 06:03 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-20 03:53 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-19 23:08 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-20 08:45 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-21 06:40 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-19 19:36 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs RonB <ronb02NOSPAM@gmail.com> - 2025-01-20 03:56 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-01-19 08:53 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-19 06:09 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-14 12:46 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs "Carlos E.R." <robin_listas@es.invalid> - 2025-01-15 13:51 +0100
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-15 09:58 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs "Carlos E.R." <robin_listas@es.invalid> - 2025-01-15 16:20 +0100
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-15 23:20 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs "Carlos E.R." <robin_listas@es.invalid> - 2025-01-16 15:36 +0100
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-17 00:12 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Chris <ithinkiam@gmail.com> - 2025-01-15 18:09 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs "Carlos E.R." <robin_listas@es.invalid> - 2025-01-16 15:47 +0100
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-14 05:48 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Hank Rogers <Hank@nospam.invalid> - 2025-01-13 16:48 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-13 23:54 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Chris <ithinkiam@gmail.com> - 2025-01-15 11:33 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-15 10:46 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-15 11:33 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs vallor <vallor@cultnix.org> - 2025-01-15 17:02 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-15 12:33 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-16 05:40 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 06:27 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-27 22:49 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-15 14:32 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-15 15:52 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-15 20:34 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 00:41 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 06:42 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 14:40 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 16:34 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 16:56 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 22:40 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-17 02:04 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs chrisv <chrisv@nospam.invalid> - 2025-01-17 07:34 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs roger <rduffy@hotmail.com.invalid - 2025-01-17 14:01 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-17 17:15 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-17 15:57 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-17 16:50 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-17 21:52 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Farley Flud <ff@linux.rocks> - 2025-01-16 21:38 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-16 18:33 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 15:44 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 15:51 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-16 16:11 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs Farley Flud <fsquared@fsquared.linux> - 2025-01-17 13:03 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-17 16:00 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs Farley Flud <ff@linux.rocks> - 2025-01-17 23:15 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-17 18:10 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs Physfitfreak <physfitfreak@gmail.com> - 2025-01-17 18:13 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-30 13:35 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-01-30 17:32 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs pothead <pothead@snakebite.com> - 2025-02-01 00:20 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-02-01 06:58 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs CrudeSausage <crude@sausa.ge> - 2025-02-01 07:18 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs chrisv <chrisv@nospam.invalid> - 2025-02-01 06:31 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs vallor <vallor@cultnix.org> - 2025-02-01 12:39 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-02-02 16:00 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-02-02 15:59 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 06:22 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-16 12:10 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs chrisv <chrisv@nospam.invalid> - 2025-01-16 12:28 -0600
Re: Microsoft to force new Outlook on Windows 10 PCs rbowman <bowman@montana.com> - 2025-01-17 00:27 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Paul <nospam@needed.invalid> - 2025-01-16 23:47 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs DFS <guhnoo-basher@linux.advocaca> - 2025-01-20 16:41 -0500
Gaming Laptops (was: Re: Microsoft to force new Outlook on Windows 10 PCs) vallor <vallor@cultnix.org> - 2025-02-01 12:58 +0000
Re: Gaming Laptops Paul <nospam@needed.invalid> - 2025-02-01 19:22 -0500
Re: Gaming Laptops chrisv <chrisv@nospam.invalid> - 2025-02-02 08:05 -0600
Re: Gaming Laptops candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-02-03 20:10 +0000
Re: Gaming Laptops Paul <nospam@needed.invalid> - 2025-02-03 19:24 -0500
Re: Gaming Laptops pothead <pothead@snakebite.com> - 2025-02-04 00:45 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs Mark Lloyd <not.email@all.invalid> - 2025-01-16 18:45 +0000
Re: Microsoft to force new Outlook on Windows 10 PCs -hh <recscuba_google@huntzinger.com> - 2025-01-16 16:05 -0500
Re: Microsoft to force new Outlook on Windows 10 PCs Joel <joelcrump@gmail.com> - 2025-01-16 11:35 -0500
Page 2 of 10 — ← Prev page 1 [2] 3 4 … 10 Next page →
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-11 07:38 -0500 |
| Message-ID | <4DtgP.73430$2xE6.27422@fx18.iad> |
| In reply to | #683700 |
On 2025-01-11 04:32, Joel wrote: > RonB <ronb02NOSPAM@gmail.com> wrote: >> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: > >>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >>> >>> Microsoft will force install the new Outlook email client on Windows 10 >>> systems starting with next month's security update. >>> >>> The announcement was made in a new message added to the company's >>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >>> 365 apps users. >>> >>> As Redmond explains, the new Outlook app will be installed on Windows 10 >>> devices for users who deploy the optional January 28 update and force >>> installed for all who install the February 11 security update. >>> >>> The new Outlook client will run alongside the classic Outlook app and >>> will not modify configurations or user defaults. Microsoft added that >>> there's no way to block it from being installed on Windows 10 devices; >>> however, those who don't want it can remove it afterward. >>> >>> "New Outlook exists as an installed app on the device. For instance, it >>> can be found in the Apps section of the Start Menu. It does not replace >>> existing (classic) Outlook or change any configurations / user defaults. >>> Both (classic) Outlook and New Outlook for Windows can run side by >>> side," Microsoft says. >>> >>> "Currently, there isn't a way to block the new Outlook from being >>> installed - if you prefer not to have new Outlook show up on your >>> organization's devices, you can remove it after it's installed as part >>> of the update," the company added in a support document updated on Thursday. >>> >>> New Outlook user interface >>> New Outlook user interface (Microsoft) >>> To remove the new Outlook app package after it's force installed on your >>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>> with the PackageName parameter value Microsoft.OutlookForWindows. >>> >>> This can be done by running the following command from a Windows >>> PowerShell prompt and adding a new reg value: >>> >>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >>> >>> REG VALUE: >>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >>> value of ["MS_Outlook"]. After removing the Outlook package, Windows >>> Updates will not reinstall the new Outlook client. >>> >>> The first preview version of the new Outlook for Windows was introduced >>> in May 2022. The app was generally available for personal accounts in >>> September 2023 (via the September 26 Windows fall update and the >>> Microsoft Store on Windows 11) and for commercial customers in August 2024. >> >> Even if I used Windows I wouldn't use Outlook. > > > I would use it under Win11 in another life, where I wasn't supported > by the OSS community. In my case, I won't use it again unless there is an assurance that the fTPM problem I mentioned weeks ago was fixed. However, I have to admit that even if I were to install it once more, the reality is that I spend most of my time cleaning Windows and checking for corruption in the system files. The damned operating system breaks so often that I find it necessary to run sfc periodically just to be sure that I won't suddenly experience a bizarre slowdown or components not working as they should. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-11 07:28 -0500 |
| Message-ID | <ZttgP.479487$DPl.216049@fx13.iad> |
| In reply to | #683697 |
On 2025-01-11 04:27, RonB wrote: > On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: >> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >> >> Microsoft will force install the new Outlook email client on Windows 10 >> systems starting with next month's security update. >> >> The announcement was made in a new message added to the company's >> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >> 365 apps users. >> >> As Redmond explains, the new Outlook app will be installed on Windows 10 >> devices for users who deploy the optional January 28 update and force >> installed for all who install the February 11 security update. >> >> The new Outlook client will run alongside the classic Outlook app and >> will not modify configurations or user defaults. Microsoft added that >> there's no way to block it from being installed on Windows 10 devices; >> however, those who don't want it can remove it afterward. >> >> "New Outlook exists as an installed app on the device. For instance, it >> can be found in the Apps section of the Start Menu. It does not replace >> existing (classic) Outlook or change any configurations / user defaults. >> Both (classic) Outlook and New Outlook for Windows can run side by >> side," Microsoft says. >> >> "Currently, there isn't a way to block the new Outlook from being >> installed - if you prefer not to have new Outlook show up on your >> organization's devices, you can remove it after it's installed as part >> of the update," the company added in a support document updated on Thursday. >> >> New Outlook user interface >> New Outlook user interface (Microsoft) >> To remove the new Outlook app package after it's force installed on your >> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >> with the PackageName parameter value Microsoft.OutlookForWindows. >> >> This can be done by running the following command from a Windows >> PowerShell prompt and adding a new reg value: >> >> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >> >> REG VALUE: >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >> value of ["MS_Outlook"]. After removing the Outlook package, Windows >> Updates will not reinstall the new Outlook client. >> >> The first preview version of the new Outlook for Windows was introduced >> in May 2022. The app was generally available for personal accounts in >> September 2023 (via the September 26 Windows fall update and the >> Microsoft Store on Windows 11) and for commercial customers in August 2024. > > Even if I used Windows I wouldn't use Outlook. If you use a Microsoft account, the new Outlook is light enough to be fun to use. It's a lot less clunky than the older Outlook application albeit not as functional. Still, I would rather these people actually give me a choice as to whether I have the program on my computer or not. I quite like how I can remove anything and everything from a Linux installation. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2025-01-12 08:38 +0000 |
| Message-ID | <vlvv1p$12kg2$14@dont-email.me> |
| In reply to | #683726 |
On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: > On 2025-01-11 04:27, RonB wrote: >> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: >>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >>> >>> Microsoft will force install the new Outlook email client on Windows 10 >>> systems starting with next month's security update. >>> >>> The announcement was made in a new message added to the company's >>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >>> 365 apps users. >>> >>> As Redmond explains, the new Outlook app will be installed on Windows 10 >>> devices for users who deploy the optional January 28 update and force >>> installed for all who install the February 11 security update. >>> >>> The new Outlook client will run alongside the classic Outlook app and >>> will not modify configurations or user defaults. Microsoft added that >>> there's no way to block it from being installed on Windows 10 devices; >>> however, those who don't want it can remove it afterward. >>> >>> "New Outlook exists as an installed app on the device. For instance, it >>> can be found in the Apps section of the Start Menu. It does not replace >>> existing (classic) Outlook or change any configurations / user defaults. >>> Both (classic) Outlook and New Outlook for Windows can run side by >>> side," Microsoft says. >>> >>> "Currently, there isn't a way to block the new Outlook from being >>> installed - if you prefer not to have new Outlook show up on your >>> organization's devices, you can remove it after it's installed as part >>> of the update," the company added in a support document updated on Thursday. >>> >>> New Outlook user interface >>> New Outlook user interface (Microsoft) >>> To remove the new Outlook app package after it's force installed on your >>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>> with the PackageName parameter value Microsoft.OutlookForWindows. >>> >>> This can be done by running the following command from a Windows >>> PowerShell prompt and adding a new reg value: >>> >>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >>> >>> REG VALUE: >>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >>> value of ["MS_Outlook"]. After removing the Outlook package, Windows >>> Updates will not reinstall the new Outlook client. >>> >>> The first preview version of the new Outlook for Windows was introduced >>> in May 2022. The app was generally available for personal accounts in >>> September 2023 (via the September 26 Windows fall update and the >>> Microsoft Store on Windows 11) and for commercial customers in August 2024. >> >> Even if I used Windows I wouldn't use Outlook. > > If you use a Microsoft account, the new Outlook is light enough to be > fun to use. It's a lot less clunky than the older Outlook application > albeit not as functional. Still, I would rather these people actually > give me a choice as to whether I have the program on my computer or not. > I quite like how I can remove anything and everything from a Linux > installation. Light or not light, I have zero interest in Outlook. I never even used it when I used Windows. Speaking of Windows... my son's Windows 10 computer was hosed (probably because he wouldn't let it update). So we got him an SSD where I was planning on doing a new install. I thought I was using a Windows 10 USB for the install, but apparently it was Windows 11 from 2022. At any rate it installed and updated, but threw an error (can't update). TPC 2.0 wasn't turned on in the BIOS, which was required to get it past a certain point. So I turned that on, still wouldn't update. So I finally found out I had to use one of the options on Microsoft's download page to update it. It got to about 76% (or so) and the update stopped because the NVMe's firmware wasn't updated(?). Really? The damned firmware not being updated on the (obviously) working SSD and Windows 11 wouldn't update? Is this the kind of crap everyone is going to run into when trying to update to Windows 11 from Windows 10? Anyhow I downloaded and installed the firmware for the WD Blue SSD (when did San-disk buy Western Digital?) and hit the "Refresh" button on the install page. Hit it again... and again... and again... Zero response. So I had to start the install again. Of course it stopped — again — with the SSD firmware issue. I realized ah, crap, I'll have to restart the computer. (Crappy Windows) before it will see the firmware update. It took forever again, but the update finished with only one more restart... and about another fifteen minutes of waiting. But, *finally* the update was complete... wait a minute, Windows immediately started downloading the next update... so I guess the loop goes on and on. Windows 11 updates may be better than than Windows 10 ones, but it's still total crap compared to Linux. -- “Evil is not able to create anything new, it can only distort and destroy what has been invented or made by the forces of good.” —J.R.R. Tolkien
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-12 09:36 -0500 |
| Message-ID | <prQgP.44663$nlJ1.37958@fx41.iad> |
| In reply to | #683818 |
On 2025-01-12 03:38, RonB wrote: > On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: >> On 2025-01-11 04:27, RonB wrote: >>> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: >>>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >>>> >>>> Microsoft will force install the new Outlook email client on Windows 10 >>>> systems starting with next month's security update. >>>> >>>> The announcement was made in a new message added to the company's >>>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >>>> 365 apps users. >>>> >>>> As Redmond explains, the new Outlook app will be installed on Windows 10 >>>> devices for users who deploy the optional January 28 update and force >>>> installed for all who install the February 11 security update. >>>> >>>> The new Outlook client will run alongside the classic Outlook app and >>>> will not modify configurations or user defaults. Microsoft added that >>>> there's no way to block it from being installed on Windows 10 devices; >>>> however, those who don't want it can remove it afterward. >>>> >>>> "New Outlook exists as an installed app on the device. For instance, it >>>> can be found in the Apps section of the Start Menu. It does not replace >>>> existing (classic) Outlook or change any configurations / user defaults. >>>> Both (classic) Outlook and New Outlook for Windows can run side by >>>> side," Microsoft says. >>>> >>>> "Currently, there isn't a way to block the new Outlook from being >>>> installed - if you prefer not to have new Outlook show up on your >>>> organization's devices, you can remove it after it's installed as part >>>> of the update," the company added in a support document updated on Thursday. >>>> >>>> New Outlook user interface >>>> New Outlook user interface (Microsoft) >>>> To remove the new Outlook app package after it's force installed on your >>>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>>> with the PackageName parameter value Microsoft.OutlookForWindows. >>>> >>>> This can be done by running the following command from a Windows >>>> PowerShell prompt and adding a new reg value: >>>> >>>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >>>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >>>> >>>> REG VALUE: >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >>>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >>>> value of ["MS_Outlook"]. After removing the Outlook package, Windows >>>> Updates will not reinstall the new Outlook client. >>>> >>>> The first preview version of the new Outlook for Windows was introduced >>>> in May 2022. The app was generally available for personal accounts in >>>> September 2023 (via the September 26 Windows fall update and the >>>> Microsoft Store on Windows 11) and for commercial customers in August 2024. >>> >>> Even if I used Windows I wouldn't use Outlook. >> >> If you use a Microsoft account, the new Outlook is light enough to be >> fun to use. It's a lot less clunky than the older Outlook application >> albeit not as functional. Still, I would rather these people actually >> give me a choice as to whether I have the program on my computer or not. >> I quite like how I can remove anything and everything from a Linux >> installation. > > Light or not light, I have zero interest in Outlook. I never even used it > when I used Windows. > > Speaking of Windows... my son's Windows 10 computer was hosed (probably > because he wouldn't let it update). So we got him an SSD where I was > planning on doing a new install. I thought I was using a Windows 10 USB for > the install, but apparently it was Windows 11 from 2022. At any rate it > installed and updated, but threw an error (can't update). > > TPC 2.0 wasn't turned on in the BIOS, which was required to get it past a > certain point. So I turned that on, still wouldn't update. So I finally > found out I had to use one of the options on Microsoft's download page to > update it. It got to about 76% (or so) and the update stopped because the > NVMe's firmware wasn't updated(?). Really? The damned firmware not being > updated on the (obviously) working SSD and Windows 11 wouldn't update? Is > this the kind of crap everyone is going to run into when trying to update to > Windows 11 from Windows 10? If the firmware were a problem, the computer should not have even allowed the SSD to be detected. Either way, you can use a Linux live environment to either use fwupd or the GUI alternative and update the firmware before trying again. I notice fwupd is much better than Microsoft or ASUS's own tools when it comes to updating secure boot. > Anyhow I downloaded and installed the firmware for the WD Blue SSD (when did > San-disk buy Western Digital?) and hit the "Refresh" button on the install > page. Hit it again... and again... and again... Zero response. So I had to > start the install again. Of course it stopped — again — with the SSD > firmware issue. I realized ah, crap, I'll have to restart the computer. > (Crappy Windows) before it will see the firmware update. It took forever > again, but the update finished with only one more restart... and about > another fifteen minutes of waiting. But, *finally* the update was > complete... wait a minute, Windows immediately started downloading the next > update... so I guess the loop goes on and on. > > Windows 11 updates may be better than than Windows 10 ones, but it's still > total crap compared to Linux. Well, possibly. However, whenever I update this Fedora installation, it refuses to restart, I have to force it to shut down and then have to rebuild the NVIDIA driver. It's annoying, but I can live with what is essentially a daily frustration. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2025-01-13 12:40 +0000 |
| Message-ID | <vm31jb$1pbsb$7@dont-email.me> |
| In reply to | #683838 |
On 2025-01-12, CrudeSausage <crude@sausa.ge> wrote: > On 2025-01-12 03:38, RonB wrote: >> On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: >>> On 2025-01-11 04:27, RonB wrote: >>>> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: >>>>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >>>>> >>>>> Microsoft will force install the new Outlook email client on Windows 10 >>>>> systems starting with next month's security update. >>>>> >>>>> The announcement was made in a new message added to the company's >>>>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >>>>> 365 apps users. >>>>> >>>>> As Redmond explains, the new Outlook app will be installed on Windows 10 >>>>> devices for users who deploy the optional January 28 update and force >>>>> installed for all who install the February 11 security update. >>>>> >>>>> The new Outlook client will run alongside the classic Outlook app and >>>>> will not modify configurations or user defaults. Microsoft added that >>>>> there's no way to block it from being installed on Windows 10 devices; >>>>> however, those who don't want it can remove it afterward. >>>>> >>>>> "New Outlook exists as an installed app on the device. For instance, it >>>>> can be found in the Apps section of the Start Menu. It does not replace >>>>> existing (classic) Outlook or change any configurations / user defaults. >>>>> Both (classic) Outlook and New Outlook for Windows can run side by >>>>> side," Microsoft says. >>>>> >>>>> "Currently, there isn't a way to block the new Outlook from being >>>>> installed - if you prefer not to have new Outlook show up on your >>>>> organization's devices, you can remove it after it's installed as part >>>>> of the update," the company added in a support document updated on Thursday. >>>>> >>>>> New Outlook user interface >>>>> New Outlook user interface (Microsoft) >>>>> To remove the new Outlook app package after it's force installed on your >>>>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>>>> with the PackageName parameter value Microsoft.OutlookForWindows. >>>>> >>>>> This can be done by running the following command from a Windows >>>>> PowerShell prompt and adding a new reg value: >>>>> >>>>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >>>>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >>>>> >>>>> REG VALUE: >>>>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >>>>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >>>>> value of ["MS_Outlook"]. After removing the Outlook package, Windows >>>>> Updates will not reinstall the new Outlook client. >>>>> >>>>> The first preview version of the new Outlook for Windows was introduced >>>>> in May 2022. The app was generally available for personal accounts in >>>>> September 2023 (via the September 26 Windows fall update and the >>>>> Microsoft Store on Windows 11) and for commercial customers in August 2024. >>>> >>>> Even if I used Windows I wouldn't use Outlook. >>> >>> If you use a Microsoft account, the new Outlook is light enough to be >>> fun to use. It's a lot less clunky than the older Outlook application >>> albeit not as functional. Still, I would rather these people actually >>> give me a choice as to whether I have the program on my computer or not. >>> I quite like how I can remove anything and everything from a Linux >>> installation. >> >> Light or not light, I have zero interest in Outlook. I never even used it >> when I used Windows. >> >> Speaking of Windows... my son's Windows 10 computer was hosed (probably >> because he wouldn't let it update). So we got him an SSD where I was >> planning on doing a new install. I thought I was using a Windows 10 USB for >> the install, but apparently it was Windows 11 from 2022. At any rate it >> installed and updated, but threw an error (can't update). >> >> TPC 2.0 wasn't turned on in the BIOS, which was required to get it past a >> certain point. So I turned that on, still wouldn't update. So I finally >> found out I had to use one of the options on Microsoft's download page to >> update it. It got to about 76% (or so) and the update stopped because the >> NVMe's firmware wasn't updated(?). Really? The damned firmware not being >> updated on the (obviously) working SSD and Windows 11 wouldn't update? Is >> this the kind of crap everyone is going to run into when trying to update to >> Windows 11 from Windows 10? > > If the firmware were a problem, the computer should not have even > allowed the SSD to be detected. Either way, you can use a Linux live > environment to either use fwupd or the GUI alternative and update the > firmware before trying again. I notice fwupd is much better than > Microsoft or ASUS's own tools when it comes to updating secure boot. I totally agree. And why doesn't Windows check all the requirements BEFORE it spends an hour or an hour and a half "installing." How stupid are these people? I had no idea TPM was shut in the BIOS. I forgot to mention that, since we couldn't fix the issues with Windows 10 on the hard drive, I had to buy another license for Windows 11, so now the the same computer has two licenses. I just found out that a different son has been using an "unactivated" Windows install since he replaced his motherboard. Fortunately you can pick up these license keys on eBay for about $5 to $10 (and I don't feel bad at all about it). I think it's stupid to have to re-license a computer that's already licensed. Just more reasons to hate hobbyware Windows. >> Anyhow I downloaded and installed the firmware for the WD Blue SSD (when did >> San-disk buy Western Digital?) and hit the "Refresh" button on the install >> page. Hit it again... and again... and again... Zero response. So I had to >> start the install again. Of course it stopped — again — with the SSD >> firmware issue. I realized ah, crap, I'll have to restart the computer. >> (Crappy Windows) before it will see the firmware update. It took forever >> again, but the update finished with only one more restart... and about >> another fifteen minutes of waiting. But, *finally* the update was >> complete... wait a minute, Windows immediately started downloading the next >> update... so I guess the loop goes on and on. >> >> Windows 11 updates may be better than than Windows 10 ones, but it's still >> total crap compared to Linux. > > Well, possibly. However, whenever I update this Fedora installation, it > refuses to restart, I have to force it to shut down and then have to > rebuild the NVIDIA driver. It's annoying, but I can live with what is > essentially a daily frustration. I haven't had these kinds of problems with Fedora (or Linux Mint) but I have simple machines — as mentioned many times. If Fedora gives you that trouble every time you update it, I would only update it every other week or so. Maybe every third week. -- “Evil is not able to create anything new, it can only distort and destroy what has been invented or made by the forces of good.” —J.R.R. Tolkien
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-13 10:05 -0500 |
| Message-ID | <rZ9hP.188033$2xE6.10447@fx18.iad> |
| In reply to | #683907 |
On 2025-01-13 07:40, RonB wrote: > On 2025-01-12, CrudeSausage <crude@sausa.ge> wrote: >> On 2025-01-12 03:38, RonB wrote: >>> On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: >>>> On 2025-01-11 04:27, RonB wrote: >>>>> On 2025-01-10, CrudeSausage <crude@sausa.ge> wrote: >>>>>> <https://www.bleepingcomputer.com/news/microsoft/microsoft-to-force-install-new-outlook-on-windows-10-pcs-in-february/> >>>>>> >>>>>> Microsoft will force install the new Outlook email client on Windows 10 >>>>>> systems starting with next month's security update. >>>>>> >>>>>> The announcement was made in a new message added to the company's >>>>>> Microsoft 365 Admin Center, tagged MC976059, and it applies to Microsoft >>>>>> 365 apps users. >>>>>> >>>>>> As Redmond explains, the new Outlook app will be installed on Windows 10 >>>>>> devices for users who deploy the optional January 28 update and force >>>>>> installed for all who install the February 11 security update. >>>>>> >>>>>> The new Outlook client will run alongside the classic Outlook app and >>>>>> will not modify configurations or user defaults. Microsoft added that >>>>>> there's no way to block it from being installed on Windows 10 devices; >>>>>> however, those who don't want it can remove it afterward. >>>>>> >>>>>> "New Outlook exists as an installed app on the device. For instance, it >>>>>> can be found in the Apps section of the Start Menu. It does not replace >>>>>> existing (classic) Outlook or change any configurations / user defaults. >>>>>> Both (classic) Outlook and New Outlook for Windows can run side by >>>>>> side," Microsoft says. >>>>>> >>>>>> "Currently, there isn't a way to block the new Outlook from being >>>>>> installed - if you prefer not to have new Outlook show up on your >>>>>> organization's devices, you can remove it after it's installed as part >>>>>> of the update," the company added in a support document updated on Thursday. >>>>>> >>>>>> New Outlook user interface >>>>>> New Outlook user interface (Microsoft) >>>>>> To remove the new Outlook app package after it's force installed on your >>>>>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>>>>> with the PackageName parameter value Microsoft.OutlookForWindows. >>>>>> >>>>>> This can be done by running the following command from a Windows >>>>>> PowerShell prompt and adding a new reg value: >>>>>> >>>>>> PowerShell: Remove-AppxProvisionedPackage -AllUsers -Online -PackageName >>>>>> (Get-AppxPackage Microsoft.OutlookForWindows).PackageFullName >>>>>> >>>>>> REG VALUE: >>>>>> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\Orchestrator\UScheduler_Oobe\OutlookUpdate >>>>>> Next, add a REG_SZ registry setting named BlockedOobeUpdaters with a >>>>>> value of ["MS_Outlook"]. After removing the Outlook package, Windows >>>>>> Updates will not reinstall the new Outlook client. >>>>>> >>>>>> The first preview version of the new Outlook for Windows was introduced >>>>>> in May 2022. The app was generally available for personal accounts in >>>>>> September 2023 (via the September 26 Windows fall update and the >>>>>> Microsoft Store on Windows 11) and for commercial customers in August 2024. >>>>> >>>>> Even if I used Windows I wouldn't use Outlook. >>>> >>>> If you use a Microsoft account, the new Outlook is light enough to be >>>> fun to use. It's a lot less clunky than the older Outlook application >>>> albeit not as functional. Still, I would rather these people actually >>>> give me a choice as to whether I have the program on my computer or not. >>>> I quite like how I can remove anything and everything from a Linux >>>> installation. >>> >>> Light or not light, I have zero interest in Outlook. I never even used it >>> when I used Windows. >>> >>> Speaking of Windows... my son's Windows 10 computer was hosed (probably >>> because he wouldn't let it update). So we got him an SSD where I was >>> planning on doing a new install. I thought I was using a Windows 10 USB for >>> the install, but apparently it was Windows 11 from 2022. At any rate it >>> installed and updated, but threw an error (can't update). >>> >>> TPC 2.0 wasn't turned on in the BIOS, which was required to get it past a >>> certain point. So I turned that on, still wouldn't update. So I finally >>> found out I had to use one of the options on Microsoft's download page to >>> update it. It got to about 76% (or so) and the update stopped because the >>> NVMe's firmware wasn't updated(?). Really? The damned firmware not being >>> updated on the (obviously) working SSD and Windows 11 wouldn't update? Is >>> this the kind of crap everyone is going to run into when trying to update to >>> Windows 11 from Windows 10? >> >> If the firmware were a problem, the computer should not have even >> allowed the SSD to be detected. Either way, you can use a Linux live >> environment to either use fwupd or the GUI alternative and update the >> firmware before trying again. I notice fwupd is much better than >> Microsoft or ASUS's own tools when it comes to updating secure boot. > > I totally agree. And why doesn't Windows check all the requirements BEFORE it > spends an hour or an hour and a half "installing." How stupid are these > people? I had no idea TPM was shut in the BIOS. I forgot to mention that, > since we couldn't fix the issues with Windows 10 on the hard drive, I had to > buy another license for Windows 11, so now the the same computer has two > licenses. I just found out that a different son has been using an > "unactivated" Windows install since he replaced his motherboard. Fortunately > you can pick up these license keys on eBay for about $5 to $10 (and I don't > feel bad at all about it). I think it's stupid to have to re-license a > computer that's already licensed. > > Just more reasons to hate hobbyware Windows. I actually lose the Windows 10 license that was attached to this computer when they replaced the motherboard, but I don't really care. I have a 10 Pro license I can use whenever I want if I really insist on having Windows on the machine. However, I like Fedora, a lot. Everything but the fingerprint reader works as it should and I can even play my games (I'm not even using compatibility at this point, I'm focusing on the ones which have a native Linux edition). I don't have access to a lot of my movies anymore, but that's fine: I have them on the Xbox Series S and they're still attached to my account anyway. If Microsoft one day wakes up and smells the coffee and starts offering them on the web like everyone else, I'll have access to them on Linux too. It is just refreshing after three years to know that I _can_ escape the dreaded stuttering I was having in Windows. Nobody knew what it was and nobody would admit to it happening, until someone pin-pointed the problem and forced AMD to admit to it. Meanwhile, it still isn't fixed on laptops and you are forced to use the machine knowing that occasionally, the sound, mouse cursor and video will chop for 2-3 seconds at a time. The mere fact that they won't fix a _known_ problem is evidence that they don't deserve the support. >>> Anyhow I downloaded and installed the firmware for the WD Blue SSD (when did >>> San-disk buy Western Digital?) and hit the "Refresh" button on the install >>> page. Hit it again... and again... and again... Zero response. So I had to >>> start the install again. Of course it stopped — again — with the SSD >>> firmware issue. I realized ah, crap, I'll have to restart the computer. >>> (Crappy Windows) before it will see the firmware update. It took forever >>> again, but the update finished with only one more restart... and about >>> another fifteen minutes of waiting. But, *finally* the update was >>> complete... wait a minute, Windows immediately started downloading the next >>> update... so I guess the loop goes on and on. >>> >>> Windows 11 updates may be better than than Windows 10 ones, but it's still >>> total crap compared to Linux. >> >> Well, possibly. However, whenever I update this Fedora installation, it >> refuses to restart, I have to force it to shut down and then have to >> rebuild the NVIDIA driver. It's annoying, but I can live with what is >> essentially a daily frustration. > > I haven't had these kinds of problems with Fedora (or Linux Mint) but I have > simple machines — as mentioned many times. If Fedora gives you that trouble > every time you update it, I would only update it every other week or so. > Maybe every third week. I think the problem was caused by my switching over to S3 suspend, at some point. Linux can manage through it, but I believe that the settings ended up being screwed up, even after I reverted back to S0. I took the opportunity to try OpenMandriva yesterday (it's fine), before reinstalling Fedora. It seems to be working right now. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-01-11 20:11 +0000 |
| Message-ID | <lug1irFotnoU5@mid.individual.net> |
| In reply to | #683697 |
On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: > Even if I used Windows I wouldn't use Outlook. I use the Outlook web interface for the company email when at home. At work I can directly access the mail server with Thunderbird.
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-11 17:28 -0500 |
| Message-ID | <QfCgP.3634$TgDc.933@fx38.iad> |
| In reply to | #683764 |
On 2025-01-11 15:11, rbowman wrote: > On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: > >> Even if I used Windows I wouldn't use Outlook. > > I use the Outlook web interface for the company email when at home. At > work I can directly access the mail server with Thunderbird. I made the mistake of setting up my work e-mail in Thunderbird in the past. By accident, you'll end up sending more than one message with the wrong e-mail adress. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2025-01-12 08:40 +0000 |
| Message-ID | <vlvv6d$12kg2$16@dont-email.me> |
| In reply to | #683786 |
On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: > On 2025-01-11 15:11, rbowman wrote: >> On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: >> >>> Even if I used Windows I wouldn't use Outlook. >> >> I use the Outlook web interface for the company email when at home. At >> work I can directly access the mail server with Thunderbird. > > I made the mistake of setting up my work e-mail in Thunderbird in the > past. By accident, you'll end up sending more than one message with the > wrong e-mail adress. I can understand that. That's why I quit using Thunderbird for Newsgroup posts. -- “Evil is not able to create anything new, it can only distort and destroy what has been invented or made by the forces of good.” —J.R.R. Tolkien
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-12 09:55 -0500 |
| Message-ID | <AJQgP.631580$DYF8.414903@fx14.iad> |
| In reply to | #683820 |
On 2025-01-12 03:40, RonB wrote: > On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: >> On 2025-01-11 15:11, rbowman wrote: >>> On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: >>> >>>> Even if I used Windows I wouldn't use Outlook. >>> >>> I use the Outlook web interface for the company email when at home. At >>> work I can directly access the mail server with Thunderbird. >> >> I made the mistake of setting up my work e-mail in Thunderbird in the >> past. By accident, you'll end up sending more than one message with the >> wrong e-mail adress. > > I can understand that. That's why I quit using Thunderbird for Newsgroup > posts. Yet, it is still the best newsgroup client because of its excellent filtering features. I can filter out Larry Pietraskiewicz without any effort as a result of it. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2025-01-13 12:44 +0000 |
| Message-ID | <vm31r9$1pbsb$8@dont-email.me> |
| In reply to | #683843 |
On 2025-01-12, CrudeSausage <crude@sausa.ge> wrote: > On 2025-01-12 03:40, RonB wrote: >> On 2025-01-11, CrudeSausage <crude@sausa.ge> wrote: >>> On 2025-01-11 15:11, rbowman wrote: >>>> On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: >>>> >>>>> Even if I used Windows I wouldn't use Outlook. >>>> >>>> I use the Outlook web interface for the company email when at home. At >>>> work I can directly access the mail server with Thunderbird. >>> >>> I made the mistake of setting up my work e-mail in Thunderbird in the >>> past. By accident, you'll end up sending more than one message with the >>> wrong e-mail adress. >> >> I can understand that. That's why I quit using Thunderbird for Newsgroup >> posts. > > Yet, it is still the best newsgroup client because of its excellent > filtering features. I can filter out Larry Pietraskiewicz without any > effort as a result of it. I do that in slrn as well. At least I don't think I see him (or his nyms). I only see about ten posters, total, here. And no crossposts at all. -- “Evil is not able to create anything new, it can only distort and destroy what has been invented or made by the forces of good.” —J.R.R. Tolkien
[toc] | [prev] | [next] | [standalone]
| From | RonB <ronb02NOSPAM@gmail.com> |
|---|---|
| Date | 2025-01-12 08:39 +0000 |
| Message-ID | <vlvv4p$12kg2$15@dont-email.me> |
| In reply to | #683764 |
On 2025-01-11, rbowman <bowman@montana.com> wrote: > On Sat, 11 Jan 2025 09:27:35 -0000 (UTC), RonB wrote: > >> Even if I used Windows I wouldn't use Outlook. > > I use the Outlook web interface for the company email when at home. At > work I can directly access the mail server with Thunderbird. I don't have to worry about company email. I guess I did use Outlook at a few jobs (on company computers). -- “Evil is not able to create anything new, it can only distort and destroy what has been invented or made by the forces of good.” —J.R.R. Tolkien
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-01-12 23:23 +0000 |
| Message-ID | <vm1itg$1f1ma$3@dont-email.me> |
| In reply to | #683622 |
On Fri, 10 Jan 2025 12:37:00 -0500, CrudeSausage wrote: > To remove the new Outlook app package after it's force installed on your > Windows device, you can use the Remove-AppxProvisionedPackage cmdlet > with the PackageName parameter value Microsoft.OutlookForWindows. > > This can be done by running the following command from a Windows > PowerShell prompt and adding a new reg value: > > [Blah blah hoyvin-glayvin blah blah] This is why they say, Windows is a great OS -- if your time is worth nothing.
[toc] | [prev] | [next] | [standalone]
| From | MikeS <MikeS@fred.com> |
|---|---|
| Date | 2025-01-13 21:25 +0000 |
| Message-ID | <vm40cl$21e8l$2@dont-email.me> |
| In reply to | #683882 |
On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: > On Fri, 10 Jan 2025 12:37:00 -0500, CrudeSausage wrote: > >> To remove the new Outlook app package after it's force installed on your >> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >> with the PackageName parameter value Microsoft.OutlookForWindows. >> >> This can be done by running the following command from a Windows >> PowerShell prompt and adding a new reg value: >> >> [Blah blah hoyvin-glayvin blah blah] > > This is why they say, Windows is a great OS -- if your time is worth > nothing. > So which OS do you choose to expend your valuable time on?
[toc] | [prev] | [next] | [standalone]
| From | Joel <joelcrump@gmail.com> |
|---|---|
| Date | 2025-01-13 16:32 -0500 |
| Message-ID | <6h1bojt7kdp4d5euq0f78rtuvqpg7edc3e@4ax.com> |
| In reply to | #683940 |
MikeS <MikeS@fred.com> wrote: >On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >> On Fri, 10 Jan 2025 12:37:00 -0500, CrudeSausage wrote: >> >>> To remove the new Outlook app package after it's force installed on your >>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>> with the PackageName parameter value Microsoft.OutlookForWindows. >>> >>> This can be done by running the following command from a Windows >>> PowerShell prompt and adding a new reg value: >>> >>> [Blah blah hoyvin-glayvin blah blah] >> >> This is why they say, Windows is a great OS -- if your time is worth >> nothing. >> >So which OS do you choose to expend your valuable time on? Linux is the only option worth pursuing. macOS is weird and expensive, Windows is bloatware beyond belief. -- Joel W. Crump Amendment XIV Section 1. [...] No state shall make or enforce any law which shall abridge the privileges or immunities of citizens of the United States; nor shall any state deprive any person of life, liberty, or property, without due process of law; nor deny to any person within its jurisdiction the equal protection of the laws. Dobbs rewrites this, it is invalid precedent. States are liable for denying needed abortions, e.g. TX.
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-13 17:44 -0500 |
| Message-ID | <HHghP.135123$5c34.129668@fx47.iad> |
| In reply to | #683942 |
On 2025-01-13 16:32, Joel wrote: > MikeS <MikeS@fred.com> wrote: >> On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >>> On Fri, 10 Jan 2025 12:37:00 -0500, CrudeSausage wrote: >>> >>>> To remove the new Outlook app package after it's force installed on your >>>> Windows device, you can use the Remove-AppxProvisionedPackage cmdlet >>>> with the PackageName parameter value Microsoft.OutlookForWindows. >>>> >>>> This can be done by running the following command from a Windows >>>> PowerShell prompt and adding a new reg value: >>>> >>>> [Blah blah hoyvin-glayvin blah blah] >>> >>> This is why they say, Windows is a great OS -- if your time is worth >>> nothing. >>> >> So which OS do you choose to expend your valuable time on? > > > Linux is the only option worth pursuing. macOS is weird and > expensive, Windows is bloatware beyond belief. There's not much to pursue in MacOS. It works as it should and it is a fairly pleasant experience. However, I would agree that it's expensive. After a while, you'll need tools to do additional things and on MacOS, you're going to be paying money in most cases. Open-source is available for it too, mind you. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | Joel <joelcrump@gmail.com> |
|---|---|
| Date | 2025-01-13 17:54 -0500 |
| Message-ID | <la6bojl7t4686ll2teomlj0ig70ma8o8c8@4ax.com> |
| In reply to | #683945 |
CrudeSausage <crude@sausa.ge> wrote: >On 2025-01-13 16:32, Joel wrote: >> MikeS <MikeS@fred.com> wrote: >>> On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >>>> >>>> Windows is a great OS -- if your time is worth >>>> nothing. >>>> >>> So which OS do you choose to expend your valuable time on? >> >> Linux is the only option worth pursuing. macOS is weird and >> expensive, Windows is bloatware beyond belief. > >There's not much to pursue in MacOS. It works as it should and it is a >fairly pleasant experience. However, I would agree that it's expensive. >After a while, you'll need tools to do additional things and on MacOS, >you're going to be paying money in most cases. Open-source is available >for it too, mind you. I just dislike Windows and macOS, it might be my own opinion but it's right for me. -- Joel W. Crump Amendment XIV Section 1. [...] No state shall make or enforce any law which shall abridge the privileges or immunities of citizens of the United States; nor shall any state deprive any person of life, liberty, or property, without due process of law; nor deny to any person within its jurisdiction the equal protection of the laws. Dobbs rewrites this, it is invalid precedent. States are liable for denying needed abortions, e.g. TX.
[toc] | [prev] | [next] | [standalone]
| From | CrudeSausage <crude@sausa.ge> |
|---|---|
| Date | 2025-01-13 18:10 -0500 |
| Message-ID | <Q3hhP.45732$nlJ1.37298@fx41.iad> |
| In reply to | #683947 |
On 2025-01-13 17:54, Joel wrote: > CrudeSausage <crude@sausa.ge> wrote: >> On 2025-01-13 16:32, Joel wrote: >>> MikeS <MikeS@fred.com> wrote: >>>> On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >>>>> >>>>> Windows is a great OS -- if your time is worth >>>>> nothing. >>>>> >>>> So which OS do you choose to expend your valuable time on? >>> >>> Linux is the only option worth pursuing. macOS is weird and >>> expensive, Windows is bloatware beyond belief. >> >> There's not much to pursue in MacOS. It works as it should and it is a >> fairly pleasant experience. However, I would agree that it's expensive. >> After a while, you'll need tools to do additional things and on MacOS, >> you're going to be paying money in most cases. Open-source is available >> for it too, mind you. > > > I just dislike Windows and macOS, it might be my own opinion but it's > right for me. MacOS machines have a shelf life of about seven years before Apple decides that your machine is no longer worth supporting with updates. As we've seen, Windows machines get about seven, so it's a fair amount of time. However, Linux has them both beat with unlimited support no matter how pathetic the machine you're running it on is. -- CrudeSausage Gab: @CrudeSausage Unapologetic paleoconservative
[toc] | [prev] | [next] | [standalone]
| From | Joel <joelcrump@gmail.com> |
|---|---|
| Date | 2025-01-13 18:25 -0500 |
| Message-ID | <ru7bojpl0j6ot182uuhhvrakcflqsadi30@4ax.com> |
| In reply to | #683948 |
CrudeSausage <crude@sausa.ge> wrote: >On 2025-01-13 17:54, Joel wrote: >> CrudeSausage <crude@sausa.ge> wrote: >>> On 2025-01-13 16:32, Joel wrote: >>>> MikeS <MikeS@fred.com> wrote: >>>>> On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >>>>>> >>>>>> Windows is a great OS -- if your time is worth >>>>>> nothing. >>>>>> >>>>> So which OS do you choose to expend your valuable time on? >>>> >>>> Linux is the only option worth pursuing. macOS is weird and >>>> expensive, Windows is bloatware beyond belief. >>> >>> There's not much to pursue in MacOS. It works as it should and it is a >>> fairly pleasant experience. However, I would agree that it's expensive. >>> After a while, you'll need tools to do additional things and on MacOS, >>> you're going to be paying money in most cases. Open-source is available >>> for it too, mind you. >> >> I just dislike Windows and macOS, it might be my own opinion but it's >> right for me. > >MacOS machines have a shelf life of about seven years before Apple >decides that your machine is no longer worth supporting with updates. As >we've seen, Windows machines get about seven, so it's a fair amount of >time. However, Linux has them both beat with unlimited support no matter >how pathetic the machine you're running it on is. My machine is an interesting example - if I'd stayed with Win10, it'd be slammin', but then support would end relatively early in its life. So upgrade to 11, great, until the bloat overtakes it, as in my view it already began to with 23H2. Linux is the only way to solve this dilemma. -- Joel W. Crump Amendment XIV Section 1. [...] No state shall make or enforce any law which shall abridge the privileges or immunities of citizens of the United States; nor shall any state deprive any person of life, liberty, or property, without due process of law; nor deny to any person within its jurisdiction the equal protection of the laws. Dobbs rewrites this, it is invalid precedent. States are liable for denying needed abortions, e.g. TX.
[toc] | [prev] | [next] | [standalone]
| From | Hank Rogers <Hank@nospam.invalid> |
|---|---|
| Date | 2025-01-13 17:52 -0600 |
| Message-ID | <vm48v6$23a1f$2@dont-email.me> |
| In reply to | #683949 |
Joel wrote: > CrudeSausage <crude@sausa.ge> wrote: >> On 2025-01-13 17:54, Joel wrote: >>> CrudeSausage <crude@sausa.ge> wrote: >>>> On 2025-01-13 16:32, Joel wrote: >>>>> MikeS <MikeS@fred.com> wrote: >>>>>> On 12/01/2025 23:23, Lawrence D'Oliveiro wrote: >>>>>>> >>>>>>> Windows is a great OS -- if your time is worth >>>>>>> nothing. >>>>>>> >>>>>> So which OS do you choose to expend your valuable time on? >>>>> >>>>> Linux is the only option worth pursuing. macOS is weird and >>>>> expensive, Windows is bloatware beyond belief. >>>> >>>> There's not much to pursue in MacOS. It works as it should and it is a >>>> fairly pleasant experience. However, I would agree that it's expensive. >>>> After a while, you'll need tools to do additional things and on MacOS, >>>> you're going to be paying money in most cases. Open-source is available >>>> for it too, mind you. >>> >>> I just dislike Windows and macOS, it might be my own opinion but it's >>> right for me. >> >> MacOS machines have a shelf life of about seven years before Apple >> decides that your machine is no longer worth supporting with updates. As >> we've seen, Windows machines get about seven, so it's a fair amount of >> time. However, Linux has them both beat with unlimited support no matter >> how pathetic the machine you're running it on is. > > > My machine is an interesting example - if I'd stayed with Win10, it'd > be slammin', but then support would end relatively early in its life. > So upgrade to 11, great, until the bloat overtakes it, as in my view > it already began to with 23H2. Linux is the only way to solve this > dilemma. > Indeed, linux is the only way to salvation.
[toc] | [prev] | [next] | [standalone]
Page 2 of 10 — ← Prev page 1 [2] 3 4 … 10 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web