Win 10 Home does not allow Remote Desktop Connection. I know there other methods (BoincTasks) but I liked seeing the Desktop.

I use VNC instead of RDP. Which also allows GPUs to keep crunching if you are using them. As the GPU drivers are not available to BOINC when an RDP session becomes active.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Win 10 Home does not allow Remote Desktop Connection. I know there other methods (BoincTasks) but I liked seeing the Desktop.

I don't think the 'Home' versions of Win 7 or Win XP allowed it either - you needed to go Professional.

BOINC Tasks doesn't give you the desktop either, but I've used Windows 7 Home with TightVNC, and I see the latest versions claim Win 10 compatibility. Not only a full desktop, but the remote computer can continue running GPU tasks while you fiddle - not possible with Remote Desktop.

Win 10 Home does not allow Remote Desktop Connection. I know there other methods (BoincTasks) but I liked seeing the Desktop.

I don't think the 'Home' versions of Win 7 or Win XP allowed it either - you needed to go Professional.

Sad but true; I've paid extra ever generation because I'm too attached to my RDP.

How's that decision to 'upgrade' working out for you (especially if you paid for it)?

♦  Window 10 is less secure than Windows 7
♦  Windows 10 Cannot Protect Insecure Applications Like EMET Can
♦  Microsoft: Windows 10 makes EMET unnecessary. Study: Nope

RDP is working on my Windows 10 Home edition.
Tullio

---

Say goodbye to the MS-DOS command prompt
It had a good 36-year run, but its day is done

Late last month, in Windows 10 Preview Build 14791, the command prompt was put out to pasture. Dona Sarkar, head of the Windows Insider Program, wrote, “PowerShell is now the defacto command shell from File Explorer. It replaces Command Prompt (aka, cmd.exe).”

That “defacto” suggests that it’s not all over for the command prompt. And it’s true that you can still opt out of the default by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off.”

But you might as well wave bye-bye to the old command prompt. Build 14791 isn’t just any beta. It’s the foundation for the Redstone 2 upgrade, a.k.a. Windows 10 SP2. This is the future of Windows 10, and it won’t include this oldest of Microsoft software relics.

---

Say goodbye to the MS-DOS command prompt
It had a good 36-year run, but its day is done

Late last month, in Windows 10 Preview Build 14791, the command prompt was put out to pasture. Dona Sarkar, head of the Windows Insider Program, wrote, “PowerShell is now the defacto command shell from File Explorer. It replaces Command Prompt (aka, cmd.exe).”

That “defacto” suggests that it’s not all over for the command prompt. And it’s true that you can still opt out of the default by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off.”

But you might as well wave bye-bye to the old command prompt. Build 14791 isn’t just any beta. It’s the foundation for the Redstone 2 upgrade, a.k.a. Windows 10 SP2. This is the future of Windows 10, and it won’t include this oldest of Microsoft software relics.

They can have my command prompt when they pry it from my cold dead hands!

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

They can have my command prompt when they pry it from my cold dead hands!

Amen to that. Wonder if I'm going to have to rewrite QOpt ... Sigh ...

---

They can have my command prompt when they pry it from my cold dead hands!

Amen to that. Wonder if I'm going to have to rewrite QOpt ... Sigh ...

+1

---

"Sour Grapes make a bitter Whine." <(0)>

12/9/2016 7:04:45 PM		Starting BOINC client version 7.6.23 for windows_x86_64
12/9/2016 7:04:45 PM		log flags: sched_ops
12/9/2016 7:04:45 PM		Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
12/9/2016 7:04:45 PM		Data directory: C:\BOINC
12/9/2016 7:04:50 PM		CUDA: NVIDIA GPU 0: GeForce GTX 950M (driver version 375.70, CUDA version 8.0, compute capability 5.0, 2048MB, 1689MB available, 1188 GFLOPS peak)
12/9/2016 7:04:50 PM		OpenCL: NVIDIA GPU 0: GeForce GTX 950M (driver version 375.70, device version OpenCL 1.2 CUDA, 2048MB, 1689MB available, 1188 GFLOPS peak)
12/9/2016 7:04:50 PM		OpenCL: Intel GPU 0: Intel(R) HD Graphics 530 (driver version 21.20.16.4542, device version OpenCL 2.0, 3225MB, 3225MB available, 202 GFLOPS peak)
12/9/2016 7:04:50 PM		OpenCL: Intel GPU 1: Intel(R) HD Graphics 530 (driver version 21.20.16.4542, device version OpenCL 2.0, 3225MB, 3225MB available, 202 GFLOPS peak)
12/9/2016 7:04:50 PM		OpenCL CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 6.6.0.370, device version OpenCL 2.0 (Build 370))
12/9/2016 7:04:50 PM		OpenCL CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 6.6.0.370, device version OpenCL 2.0 (Build 370))

My new notebook, that unfortunately came with Windows 10, did some update while I wasn't paying attention. and not I seem to have two Intel GPUs in BOINC. No where else in the system reports two and it's the same driver as prior to the updates getting installed... So that's fun!

I guess I'll be spending the weekend figuring out how to fix that...

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

My new notebook, that unfortunately came with Windows 10, did some update while I wasn't paying attention. and not I seem to have two Intel GPUs in BOINC. No where else in the system reports two and it's the same driver as prior to the updates getting installed... So that's fun!
I guess I'll be spending the weekend figuring out how to fix that...

If you haven't already tried this, might try running a fresh install of the driver installers, specifying the clean install option. Chances are that will solve it.

---

Guess M$ had a (slight?) change of heart about the DOS prompt...

From Computer World: Follow-up: MS-DOS lives on after all
Microsoft wants to make it clear that the last bits of MS-DOS, cmd.exe, aren’t going away

According to a Microsoft spokesperson, “Microsoft is not removing Cmd from Windows, but rather changing the default shell, launched via File Explorer and the [Win] + [X] power-user menu, from Cmd to PowerShell. Users can opt to change the default shell back to Cmd via Settings and can continue to launch whichever shell they prefer, be it Cmd, PowerShell, or Bash (if enabled) via the Start menu. The Windows Cmd shell has a long heritage and is an essential tool used by millions of businesses, users, and developers every day. It remains an integral part of Windows.”

---

But you might as well wave bye-bye to the old command prompt. Build 14791 isn’t just any beta. It’s the foundation for the Redstone 2 upgrade, a.k.a. Windows 10 SP2. This is the future of Windows 10, and it won’t include this oldest of Microsoft software relics.

I think you meant to say Build 14971. Not that it is that important unless you are running the Insider versions.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Another consumer fights back against Windows 10 pushiness and wins
He got $650 and an apology, which is more than most people have gotten.

Jesse Worley, an independent IT contractor, had set up a Windows 7 machine to look like Windows XP for his grandfather, who was suffering from Alzheimer's disease. One of the palliative ways of treating the condition is to surround the sufferer with the familiar, so Worley wanted to make the Windows 7 PC look like XP, which his grandfather knew well before the condition struck.

...
In a lengthy post on his personal website (he eschews all social media, so it took a while for his story to get around), Worley documents the process. Like every other Windows 7 user, Worley's grandfather was bombarded with the Get Windows X (GWX) app.

"My grandfather knows better than to say 'yes' to things that randomly pop up on his screen, so we had absolutely no problem explaining to him that Windows 10 wasn’t something we needed, and that when it came up he just needed to say no. He did so successfully for more than 6 months while Microsoft bothered him with the same pop-up over and over and over again, and would have continued to do so if Microsoft hadn’t gone out of their way to trick him," he wrote.

---

Another consumer fights back against Windows 10 pushiness and wins
He got $650 and an apology, which is more than most people have gotten.

Jesse Worley, an independent IT contractor, had set up a Windows 7 machine to look like Windows XP for his grandfather, who was suffering from Alzheimer's disease. One of the palliative ways of treating the condition is to surround the sufferer with the familiar, so Worley wanted to make the Windows 7 PC look like XP, which his grandfather knew well before the condition struck.

...
In a lengthy post on his personal website (he eschews all social media, so it took a while for his story to get around), Worley documents the process. Like every other Windows 7 user, Worley's grandfather was bombarded with the Get Windows X (GWX) app.

"My grandfather knows better than to say 'yes' to things that randomly pop up on his screen, so we had absolutely no problem explaining to him that Windows 10 wasn’t something we needed, and that when it came up he just needed to say no. He did so successfully for more than 6 months while Microsoft bothered him with the same pop-up over and over and over again, and would have continued to do so if Microsoft hadn’t gone out of their way to trick him," he wrote.

As I had mentioned previously. I had setup a Windows 7 VM and let it sit. When I checked on it sometime later I found I had a Windows 10 VM. Since the "free upgrade" period is over. I was thinking about trying that again to see what would happen.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

As I had mentioned previously. I had setup a Windows 7 VM and let it sit. When I checked on it sometime later I found I had a Windows 10 VM. Since the "free upgrade" period is over. I was thinking about trying that again to see what would happen.

At this point, it will stay Win 7 if you recreate it as such.

---

. . . and it gets even more Orwellian.

Allow Experimentation on Windows 10

With the December 2016 rollup for Win 7 64bit installed, i got 1-2 bsods per day with KMODE_EXCEPTION_NOT_HANDLED in ntoskrnl.exe. I first had the new nvidia driver in mind, but going back to an older driver did not fix the issue. Uninstalling the last December rollup fixed that issue for more than 3 days now. Interestingly uninstalling the rollup and disabling it in windows update triggered to offer the security updates on their own, one by one, not in a big package with tons of unwanted stuff. :O

---

Aloha, Uli

Who would of ever thunk it????

Microsoft Became Too Pushy With Windows 10 Updates, Agrees Chris Capossela

In case you don’t know or have forgotten, Microsoft was very aggressive with its free Windows 10 upgrade offer. The company received a lot of criticism for being too pushy with the customers and technically forcing them to update to the new version of Windows. Many users went on to complain that the Windows 10 update was installed on their computers even after they refused the update.

Well, Microsoft has finally acknowledged that it wasn’t a very smart move on the company’s part. In the latest Windows Weekly edition, Microsoft’s CMO Chris Capossela said that Microsoft went too far when it changed the behaviour of the X button. The two weeks, between the moment when the complaints started pouring in and when the company released a patch to resolve it, were “very painful”, said Capossela.

---

I'm running 7 on my cruncher. And I have zero problems with 10 trying to update. I have something giving 10 a problem when trying to update and it fails. I have no problems with my cruncher giving M$ the finger for the time being.

---