On Tue, 11 Aug 2020 03:26:53 -0400, Paul
wrote:

Eric Stevens wrote:
On Sun, 09 Aug 2020 14:35:49 +1200, Eric Stevens
wrote:

On Sat, 8 Aug 2020 08:07:15 -0400, knuttle
wrote:

On 8/8/2020 6:05 AM, Eric Stevens wrote:
I've previously let off steam about the problems I have had with
networking my two computer, how first Corsair could seel Dell but not
vice versa, or Dell could see Corsair but not the other way around, or
neither could see the other and what I did with the controls I knew
about could make much difference. Well, a week ago I got that fixed
when Dell was updated to 2004. Corsair could at least see Dell.

And then there was computer sleep and shut down. A long time ago it
worked perfectly. Then it wouldn't. Then it would. For the last
several months it wouldn't. None of this was my doing. It just kept
changing at the whim of Microsoft's latest update.

Other things have come and gone, like very slow keyboard response
(measured in seconds) on Dell following bootup. But I got that fixed.

But now Corsair has been updated to 2004, build 19041.388, the same
build as Dell. Now the slow key response has returned to Dell, the
rudimentary networking has vanished, but Corsair now sleeps. All these
magical changes with human intervention.

I hope to get minimal networking back by resetting the network on both
machines. But I wonder what is coming next?
Have you made sure that the user that gives permission to shares a
folder or drive is the owner is the owner of the folder or drive.

The user that is currently using the computer can not give access to
folders of drives that he does not own.

What is the name of the user using the computer when access was given?

What is the name of the owner of the asset being shared.

Even though someone has Administrator privileges, they can not share
assets they do not own.

The owner can be found from the Advance Button on the Security Tab of
the Properties window,

https://www.techrepublic.com/article...in-windows-10/

This is an involved procedure that will fix the problem. However in my
experience a major upgrade may loose the change and it has to be redone.
Before I upgrade to 2004 I had bidirectional access on both computers.
After the upgrade only one could access they other. Now, I am going to
have to go back and change the ownership on my one computer.

I've sorted all this out in the past (nightmare) but I have yet to
find out what if anything the update has done in this respect. I will
probably get it working just in time for the next update.

I've solved the problem. I've emptied out the old computer and deleted
all users but for a new fictitious user. I'm going to sell it.

Before selling a computer in this way (with a mature ripe OS having applications
on it and some new admin user account), you should zero the white space.

This technique is necessary, to avoid the buyer using Photorec or Recuva
and bringing *all* your files back. You are running a big risk with the
method you've described.

Don't worry. I've used Revo uninstaller to remove all of everything
but for a few useful apps of no personal significance. I've cleaned
out Drive C with CC cleaner. I twice deep formatted Drive D. The first
time with DiskPart, the second with Windows format. I don't think the
ordinary person is going to recover anything of significance.

In a salt test here, I salted a drive and ran sdelete, and there was
plenty of salt showing afterwards in HxD. I'm not convinced the method
is "El Chapo" quality (El Chapos IT guy kinda let him down). But for the
vast majority of erased files on the machine, it's going to make them
unrecoverable.

https://docs.microsoft.com/en-us/sys...nloads/sdelete

sdelete -z c:

http://blog.raxco.com/2013/03/26/use...e-just-say-no/

Well, at least that article verifies the syntax :-)

There's nothing wrong with running sdelete, warts and all.
It's a good approximate method, when you insist on doing
it this way. It's a "better than nothing" cleaning method,
trying to make a little effort at keeping you safer.

--- snip ---
--

Regards,

Eric Stevens