[Default] On 28 Jun 2017 08:16:27 -0700, in bit.listserv.ibm-main
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) wrote:
>On Wed, 28 Jun 2017 09:11:30 -0500, Wendell Lovewell wrote:
>
>>Any version of Windows can have the update service disabled.
>>
>OTOH, beware:
>
>
> On Jun 28, 2017, at 10:17 AM, Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> On Wed, 28 Jun 2017 09:11:30 -0500, Wendell Lovewell wrote:
>
>> Any version of Windows can have the update service disabled.
>>
> OTOH, beware:
>
>
On Wed, 28 Jun 2017 09:11:30 -0500, Wendell Lovewell wrote:
>Any version of Windows can have the update service disabled.
>
OTOH, beware:
https://www.usatoday.com/story/tech/news/2017/06/27/petya-ransomware-attack-windows-wannacry-protect/103241420/
Or, just avoid Windows.
>1) From a DOS
Any version of Windows can have the update service disabled.
1) From a DOS window, enter "services.msc".
2) Find the line that has "Windows Update" on it. Right-click and select
"Properties".
3) Change the "Startup Type" to "Disabled". This will prevent it from starting
next boot.
4) Click
> On Jun 27, 2017, at 8:58 AM, Sean Gleann wrote:
>
> I don't know if I'm not as adventurous as others on this thread, but I've
> never once had any problem with Windows Update on any version of Windows.
> All maintenance gets applied when it becomes available/recommended,
000433f07816-dmarc-requ...@listserv.ua.edu (Paul Gilmartin) writes:
> I see the history differently. This is conjectural, but I believe
> that UNIX had at least the user/group/others file protection facility
> at a time when OS/360 had only the primitive data set passwords. I
> recall,
On 2017-06-27, at 10:01, Jesse 1 Robinson wrote:
> Contrast with mainframe software. Windows's descent into an open-range
> free-for-all began when it morphed from its single-user origin into a
> multiuser host platform. As with UNIX and other hands-off-my-gear operating
> systems, there was
, 2017 8:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Windows 10 Pro automatic update
On Tue, 27 Jun 2017 08:47:47 -0500, Wendell Lovewell wrote:
>
>(I had to revert to Firefox release 51 and switched to "Never check for
>updates" because they dropped NPAPI support an
rame Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Boyes
Sent: Tuesday, June 27, 2017 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update
>>I finally figured out how to turn the updates off in the systems settings and
>>have
>>I finally figured out how to turn the updates off in the systems settings and
>>have not had any problems since then.
>How did you do that?
You must be running the Enterprise version or some kind of site licensed
version of Win 10. The mass-market version doesn’t allow turning off updates
On Tue, 27 Jun 2017 08:47:47 -0500, Wendell Lovewell wrote:
>
>(I had to revert to Firefox release 51 and switched to "Never check for
>updates" because they dropped NPAPI support and a some of the web sites I need
>stopped working. I still find myself being forced to use Edge or Chrome now
M Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Clark Morris
Sent: Monday, June 26, 2017 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update: was Re: Eliminating the systems
programmer was Re: IBM cuts contractor billing by 15 percent (our else
I don't know if I'm not as adventurous as others on this thread, but I've
never once had any problem with Windows Update on any version of Windows.
All maintenance gets applied when it becomes available/recommended, and my
system(s) continue to run, sweet as a nut.
Also, I've never once been hit
The automatic updates messed up my systems so frequently that I ended up
disabling the Windows Updates service on them. If/when I decide to apply
service, I'll do it when I want. Imo Microsoft's decision to force Win10
reboots may end up making it less safe because people stop getting
LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update: was Re: Eliminating the systems
programmer was Re: IBM cuts contractor billing by 15 percent (our else)
[Default] On 26 Jun 2017 08:45:34 -0700, in bit.listserv.ibm-main
ebar...@doitt.nyc.gov (Barkow, Eileen) wrote:
>I thought that the
lt;cfmpub...@ns.sympatico.ca>
Sent: Monday, June 26, 2017 6:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update
[Default] On Mon, 26 Jun 2017 11:47:36 -0500, Norbert Friemel
<nf.ibmm...@web.de> wrote:
>On Sun, 25 Jun 2017 16:40:47 -0300, Clark Morris wrote:
>
>&
[Default] On Mon, 26 Jun 2017 11:47:36 -0500, Norbert Friemel
wrote:
>On Sun, 25 Jun 2017 16:40:47 -0300, Clark Morris wrote:
>
>>I don't recall if I updated to the Creator's edition but I have kept
>>fairly up to date on all my computers. Windows 10 itself has not
>>caused
alf of
Barkow, Eileen <ebar...@doitt.nyc.gov>
Sent: Monday, June 26, 2017 4:53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update: was Re: Eliminating the systems
programmer was Re: IBM cuts contractor billing by 15 percent (our else)
There was an option somewhere to turn th
laptop from them
(though at a bargain price of $300 for an 8gb HP)
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Clark Morris
Sent: Monday, June 26, 2017 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update
and
> have not had any problems since then.
How did you do that?
Clark Morris
>
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Bill Wilkie
>Sent: Sunday, June 25, 2017 7:51 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subj
Of Bill Wilkie
Sent: Sunday, June 25, 2017 7:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Windows 10 Pro automatic update: was Re: Eliminating the systems
programmer was Re: IBM cuts contractor billing by 15 percent (our else)
The choices you get are UPDATE AND RESTART or UPDATE AND SHUTDOWN
es how much they must be
> making from Windows 10 updates killing machines and they said a fortune.
>
>
> Bill
>
>
>
>
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
> Clark Morris <cfmpub...@n
wife's machine to Look It up and removed the USB
>> devices and it came up. I asked the guys at Best Buys and Staples how much
>> they must be making from Windows 10 updates killing machines and they said a
>> fortune.
>>
>>
>> Bill
>>
>> __
id a fortune.
Bill
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Clark
Morris <cfmpub...@ns.sympatico.ca>
Sent: Saturday, June 24, 2017 8:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Windows 10 Pro automatic update: was Re: Eliminatin
hines and they said
>> a fortune.
>>
>>
>> Bill
>>
>>
>>
>>
>> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
>> of Clark Morris <cfmpub...@ns.sympatico.ca>
>>
BM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> of Clark Morris <cfmpub...@ns.sympatico.ca>
> Sent: Saturday, June 24, 2017 8:11 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Windows 10 Pro automatic update: was Re: Eliminating the systems
> programmer was
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Clark Morris <cfmpub...@ns.sympatico.ca>
Sent: Saturday, June 24, 2017 8:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Windows 10 Pro automatic update: was Re: Eliminating the systems
programmer was Re: IBM cut
[Default] On 24 Jun 2017 12:43:13 -0700, in bit.listserv.ibm-main
idfli...@gmail.com (scott Ford) wrote:
>Guys,
>
>I am a bit different. We run z/PDT on OpenSuse Leap 42.2 x64..running z/OS
>2.2 .
>But we us Windows and Linux for our LDAP with are STC agents on z/OS. I am
>basically all alone
28 matches
Mail list logo