Welcome to the Lounge

Sandeep Mewara30-Jul-20 1:08

Sandeep Mewara

30-Jul-20 1:08

$Shucks | :-\$

For your read/comments:
Beginners Quick Start to Learn React.js
Quick look into SignalR

Re: CCC 2020-07-30 - solved

david.delaune30-Jul-20 1:36

david.delaune

30-Jul-20 1:36

determined = (definition)
strlen = (letter pool)
repeats and repeats (shuffle operator)
relentless

Someone please have @Richard-MacCutchan check his dictionary.

Greg Utas30-Jul-20 1:40

Greg Utas

30-Jul-20 1:40

And welcome back!

Robust Services Core | Software Techniques for Lemmings | Articles

Richard MacCutchan30-Jul-20 1:41

Richard MacCutchan

30-Jul-20 1:41

Well you got so upset last time, so I will reserve judgement.

musefan30-Jul-20 2:44

musefan

30-Jul-20 2:44

david.delaune wrote:
Someone please have @Richard-MacCutchan check his dictionary.

I think it would be better to check a Thesaurus... when did "repeat" become a synonym of "shuffle"?

Richard MacCutchan30-Jul-20 3:11

Richard MacCutchan

30-Jul-20 3:11

The rules of CCC are: make them up as you go along. (But don't tell Randor).

Robust Services Core | Software Techniques for Lemmings | Articles

Greg Utas30-Jul-20 3:18

Greg Utas

30-Jul-20 3:18

I would just call it a "letter pool" or "letter bank" indicator.

Win 10 2004 is still a steaming pile of ...

OriginalGriff29-Jul-20 21:24

29-Jul-20 21:24

Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface.

OK ... revert to previous version ... come on MS, I thought you'd fixed this!
Didn't this happen back in 2017 as well?

[edit]
Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes.
And ... I have all shares back.

FES, MS ... Sigh | :sigh:

[/edit]

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

pkfox29-Jul-20 22:52

29-Jul-20 22:52

I got notified of one this morning - version 2020-07 - is this the one you installed ?

"We can't stop here - this is bat country" - Hunter S Thompson - RIP

OriginalGriff29-Jul-20 23:10

29-Jul-20 23:10

Yes - and then uninstalled.

I figured they had fixed it by now ... but no.

pkfox29-Jul-20 23:15

29-Jul-20 23:15

The one I received this morning says

2020-07 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4562900)

"We can't stop here - this is bat country" - Hunter S Thompson - RIP

OriginalGriff29-Jul-20 23:41

29-Jul-20 23:41

That one is OK - it's the Win 10 update (from build 1909 to 2020) that gave me grief.

pkfox29-Jul-20 23:58

29-Jul-20 23:58

Which was probably the one before - I must have it installed and got away with it - there again I don't share folders on my main pc

Isn't it time for oi Greg Utas ?

"We can't stop here - this is bat country" - Hunter S Thompson - RIP

OriginalGriff30-Jul-20 0:11

30-Jul-20 0:11

Nor do I - this is a Seagate Black Armour 16TB NAS that I keep "shared" stuff and hourly backups on.
What version does Winver say you are running.

pkfox30-Jul-20 1:13

30-Jul-20 1:13

1909(OS Build 18363.959)

"We can't stop here - this is bat country" - Hunter S Thompson - RIP

OriginalGriff30-Jul-20 1:19

30-Jul-20 1:19

Yep. That's the one I just rolled back to. 2004 is the latest update, and that's the one that stomped on my NAS connections.

Mike Hankey30-Jul-20 1:27

Mike Hankey

30-Jul-20 1:27

10 has a lot of nice features but I get tired of looking at the wait I'm busy spinner. Damn I want 7 back.

I'm not sure how many cookies it makes to be happy, but so far it's not 27.

JaxCoder.com

Re: Win 10 2004 is still a smelly pile of ...

theoldfool30-Jul-20 2:06

theoldfool

30-Jul-20 2:06

One might guess that the MS developers have their priorities set by the lawyers.
1. Make it secure
2. Make it more secure.
3. Don't let it violate any copyrights
4. Make sure it lets mother know of any anomalies.
5. etc.
73. make it usable.

BTW: an always-on backup device is not a backup against malware. Smile | :)

I run W10 in virtual machines and keep the NIC off until I need it. Easy to backup, just copy the files from time to time. My surveillance camera systems are still on W7. Would you believe they rebooted to accommodate the "new Edge", tada. I thought updates were a thing of the past.

If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.

Rusty Bullet31-Jul-20 3:33

Rusty Bullet

31-Jul-20 3:33

Only two digits in 73. I expected more. Of course 72 is "it's a feature!" and pertains to many things...

david.delaune30-Jul-20 2:59

david.delaune

30-Jul-20 2:59

Check to see if your NAS is using the deprecated SMB 1.0[^]

It's impossible to make the old protocol secure that's why it was dropped.

Best Wishes,
-David Delaune

Do not escape reality : improve reality !

Rage30-Jul-20 2:47

Rage

30-Jul-20 2:47

Did not know they had a Win10 version already back in 2004. Maybe you should try the latest 2020 version.

dandy7230-Jul-20 3:14

dandy72

30-Jul-20 3:14

I wouldn't necessarily blame 2004 for this. Long before it came out, every once in a while, Win10 would get into a state where I lose connections to shares on other machines for no obvious reason. Most of the time a reboot fixes it immediately. Shares that I do know worked the day before, or even just a few hours before, and that still work from other machines.

When that happens, and I'm not in a position to reboot, accessing the share (with Explorer or Start/Run) using the remote system's IP instead of its name works. As in, \\192.168.1.50 rather than \\MyNasName. Once I can get connected to that (you might get prompted for credentials), I can access the share as \\192.168.1.50\c$ or \\192.168.1.50\ShareName.

And pinging the machine by name still resolves as the correct address, so it's not a name resolution thing.

I'd be curious to know whether you're seeing the same thing.

GuyThiebaut30-Jul-20 4:00

GuyThiebaut

30-Jul-20 4:00

I am holding off 2004 until either compelled to or until Microsoft withdraw it and release something that won't break my machines.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

dandy7230-Jul-20 4:15

dandy72

30-Jul-20 4:15

Be ready to wait a long time...I'm not always convinced any newer release these days is necessarily better than any previous version.

At this stage in its lifetime, you'd think Windows had reached a point where things would improve. I'd be perfectly okay with MS spending a full year not adding any new "feature" nobody asked for, and dedicating the internal team's time to do nothing but fix what's known to be broken.

The fact that they keep introducing new icons, but break basic functionality with every new release, tells me they've run out of ideas anyway. How one affects the other...I can only speculate.