A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Bloody Windows (still)



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old August 8th 20, 11:05 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

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?
--

Regards,

Eric Stevens
Ads
  #2  
Old August 8th 20, 12:09 PM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

On Sat, 08 Aug 2020 22:05:17 +1200, 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?


Yep, Corsair can access shareable files on Dell. But while Dell can
now see Corsair, Corsair ignores any attempt by Dell to communicate.

As I said Bloody Windows. I will also add, Bloody Microsoft!
--

Regards,

Eric Stevens
  #4  
Old August 8th 20, 01:07 PM posted to alt.comp.os.windows-10
knuttle
external usenet poster
 
Posts: 262
Default Bloody Windows (still)

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.



  #5  
Old August 8th 20, 01:17 PM posted to alt.comp.os.windows-10
Todesco
external usenet poster
 
Posts: 25
Default Bloody Windows (still)

On 8/8/2020 8:07 AM, 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.

Yup, it seems to have a mind of its own. I have several computers in
the house and want all to be able to freely interconnect. Once working,
I'm happy, however, wait a while and it will probably stop working.
Shhhhhhhh, mine is working now, even with one Linux machine. Let's see
how long that lasts! Maybe going back to W7 is the answer. We hate W10
here; it is slow and aggrevating. I have yet to try a clean W10 install
as it is pretty painfull to do.

  #6  
Old August 9th 20, 03:35 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

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.
--

Regards,

Eric Stevens
  #7  
Old August 11th 20, 06:18 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

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.
--

Regards,

Eric Stevens
  #8  
Old August 11th 20, 08:26 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Bloody Windows (still)

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.

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.

*******

You could boot the Windows 10 installer DVD, go to Troubleshooting
and use the Command Prompt there. Verify that C: in that environment
is where you want to be.

dir c:
dir c:\users\eric
dir c:\users\eric\Downloads

If it doesn't look like C: , sometimes the OS drive letter
ends up being D: instead

dir d:\users\eric\Downloads

Once you know the drive letter which is actually c:, you can
use that copy of sdelete you left on C: . If the sdelete.exe
happened to be on the root of C: , then this should work
(because the boot DVD has caused the drive letter to change,
but you're too smart to fall for that).

D:\sdelete -z d:

This will "whiten" the partition. And reduce recoverability of
deleted user files.

*******

Now, if you're in a mood to experiment, you can
boot the system up again and run Photorec and Recuva
and see how few files they're able to find. the $MFT entries
with the filenames might still be there, but the "clusters"
with your bank account numbers will be zeroed out.

*******

If I'm selling a computer, it goes like this:

1) Boot DBAN, nuke entire drive.

2) Clean Install Windows 10. Set up local account, *not*
an account based on MSA. You don't want any way in
in future, of having any kind of token similar
to your previous token.

DBAN (or some similar method), would visit all the sectors
and overwrite them with something. I only mention this
method because of its relative simplicity, not because
it's the most efficient way to do it. There are better
ways to clean a modern drive (when a drive only needs
a single pass). You can do it from the Command Prompt
of the installer DVD, use diskpart, select disk 1,
list disk, then "clean all" to wipe from end to end.
But DBAN has a GUI and might be a less ugly process.

Once the entire drive is "whitened", then when you CleanInstall
Windows 10 and set up that "LuckyBuyer" account on the
new install, if they run Recuva or Photorec, they're
rewarded with "nothing". No Eric bank numbers. No Eric passwords.

Paul
  #9  
Old August 13th 20, 01:10 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

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
  #10  
Old August 13th 20, 03:41 PM posted to alt.comp.os.windows-10
Ken Blake[_7_]
external usenet poster
 
Posts: 569
Default Bloody Windows (still)

On 8/12/2020 5:10 PM, Eric Stevens wrote:
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.




The ordinary person is highly unlikely to even try. In the vast majority
of cases, simply formatting the drive or doing a clean installation of
Windows (which begins by formatting the drive) is good enough.


--
Ken
  #11  
Old August 13th 20, 03:47 PM posted to alt.comp.os.windows-10
nospam
external usenet poster
 
Posts: 4,718
Default Bloody Windows (still)

In article , Ken Blake
wrote:

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.




The ordinary person is highly unlikely to even try. In the vast majority
of cases, simply formatting the drive or doing a clean installation of
Windows (which begins by formatting the drive) is good enough.


the problem is there is no way to know who might end up with the drive.

a single pass that writes to all blocks is sufficient. beyond that is a
waste of time.
  #12  
Old August 14th 20, 06:13 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

On Thu, 13 Aug 2020 07:41:57 -0700, Ken Blake
wrote:

On 8/12/2020 5:10 PM, Eric Stevens wrote:
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.




The ordinary person is highly unlikely to even try. In the vast majority
of cases, simply formatting the drive or doing a clean installation of
Windows (which begins by formatting the drive) is good enough.


I don't think there is anything to find anyway. My major concern was
leaving applications for which I had paid and held the license.
--

Regards,

Eric Stevens
  #13  
Old August 14th 20, 06:14 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 911
Default Bloody Windows (still)

On Thu, 13 Aug 2020 10:47:30 -0400, nospam
wrote:

In article , Ken Blake
wrote:

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.




The ordinary person is highly unlikely to even try. In the vast majority
of cases, simply formatting the drive or doing a clean installation of
Windows (which begins by formatting the drive) is good enough.


the problem is there is no way to know who might end up with the drive.

a single pass that writes to all blocks is sufficient. beyond that is a
waste of time.


Not if the CIA or NSA is after you. They try harder.
--

Regards,

Eric Stevens
  #14  
Old August 14th 20, 06:31 AM posted to alt.comp.os.windows-10
nospam
external usenet poster
 
Posts: 4,718
Default Bloody Windows (still)

In article , Eric Stevens
wrote:


a single pass that writes to all blocks is sufficient. beyond that is a
waste of time.


Not if the CIA or NSA is after you. They try harder.


if the cia or nsa is after you, then you have far, far bigger problems.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 05:11 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.