|
His parents must've known something when they called him No Vac.
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
Dressed up as Rafa - why didn't I think of that ?
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
|
Cats are the best.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Hi all,
My brother inlaw called me today asking for help.
He has a desktop and a laptop.
When he plugs the external HDD to the laptop everything works as expected.
When he plugs the external HDD to the desktop nothing happens.
I've remotely connected to his desktop, went to device manager and nothing appears there. Nothing in the partitions manager, installed AOMEI partition assistant and nothing.
Tomorrow I'll go his place and will try to connect all USB devices into a USB hub (just in case the power supply is not enough to power it).
This started happening after replacing the original mechanical HDD for a SSD, and keeping the original one too (to have more space).
Any idea of what could be going on?
Thank you all in aadvance!
|
|
|
|
|
This might be helpful to have in the toolbox:
USBDeview[^]
Chances are that some flavor of USB is preventing the plugged-in HDD to advance the cause of vast local storage. My box has three, black, blue, and (pink) red; none of which I have ever really cared to figure out what the reason each rejected/accepted the various things I've plugged in. Whatever worked worked. Or it didn't.
Good luck!
|
|
|
|
|
Run adwcleaner and / or malwarebytes on that desktop. I have seen countless malware infected machined where usb storage no longer works. I makes no difference if they have this or that antivirus, do it anyway.
|
|
|
|
|
After updating Windows, merging all partitions of the old HDD and uninstalling the external HDD driver yesterday night, today it started working again.
In any case, thanks for your post.
|
|
|
|
|
I once had a strange situation similar to that, a PC from a friend had startup problems.
Disconnecting the bunch of USB devices that were attached to the PC, and several restarts of Windows helped.
|
|
|
|
|
After updating Windows, merging all partitions of the old HDD and uninstalling the external HDD driver yesterday night, today it started working again.
In any case, thanks for your post.
|
|
|
|
|
Check if the usb delivers enough power to the HDD.
|
|
|
|
|
After updating Windows, merging all partitions of the old HDD and uninstalling the external HDD driver yesterday night, today it started working again.
In any case, thanks for your post.
|
|
|
|
|
Keep in mind that there is an Explorer setting to hide empty drives. If the external drive is empty, it might not show up.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
After updating Windows, merging all partitions of the old HDD and uninstalling the external HDD driver yesterday night, today it started working again.
In any case, thanks for your post.
|
|
|
|
|
You do not give enough information to diagnose quickly so let's go in slow mode
I assume that both computers are using the same OS (either windows or linux). If not, the instructions below may not apply. Also, the instructions are ordered from the quickest to do to the hardest.
* Try different USB ports on the desktop. Use ports directly from the motherboard. Some case ports have bad cables that affect the speed and power delivery. Preferably use USB 2 ports instead of USB 3 ports. Even today, some drivers have issues with some USB 3 hardware. My current board has this problem in Linux.
* Use a Y USB cable to connect the external drive to two USB ports (if you have one). It might be under powered.
* Double check that the external box specifications are sufficient for the disk you put inside. It may be working on the laptop (due to different drivers than the desktop) but might be corrupting the disk. I had this problem once were a box appeared to work but was clipping anything above 1TB corrupting the HDD (which, to make maters worse, was a backup drive ).
* If you made an exact copy of the disk on to the SSD and they are both on the desktop, they have the same ID which is unacceptable by the OS so only the first disk to be connected is made available. In this case you have to change the disk ID. The following links from a quick internet search might help (even if they do not present the most appropriate solution)
Linux:
https://www.linuxquestions.org/questions/linux-general-1/what-is-disk-identifier-740408/[^]
How do I change the disk ID in Linux?[^]
Windows:
How to change Hard Disk's Volume Serial Number (Volume ID) - wintips.org - Windows Tips & How-tos[^]
Good luck.
|
|
|
|
|
After updating Windows, merging all partitions of the old HDD and uninstalling the external HDD driver yesterday night, today it started working again.
In any case, thanks for your post.
|
|
|
|
|
That sounds more and more like a duplicate ID problem. When you merged the partitions the drive gets assigned a new ID.
Had you made an exact copy of the disks before?
Understanding what happened might help you prevent it in the future.
Either way, problem solved
|
|
|
|
|
ElectronProgrammer wrote: Either way, problem solved
Yesssss...
My brother inlaw did it after seeing a youtube tutorial... he used macrium reflect to make the duplicate... I would have formatted the old disk after seeing the new one worked properly to keep it empty and ready to receive music, films and other files.
ElectronProgrammer wrote: That sounds more and more like a duplicate ID problem. When you merged the partitions the drive gets assigned a new ID.
I agree you.
|
|
|
|
|
While reading the introduction to C# 10 In A Nutshell[^]
Quote .NET 6’s predecessor was .NET 5, whose predecessor was .NET Core 3. (Microsoft removed “Core” from the name, and skipped version 4). The reason for skipping a version was to avoid confusion with .NET Framework 4.x.
Then a little later…
Quote: This means that Microsoft’s renaming of .NET Core to .NET has created an unfortunate ambiguity. In this book, we’ll refer to the new .NET as .NET 5+. And to refer to .NET Core and its successors, we’ll use the phrase “.NET Core and .NET 5+.”
To add to the confusion, .NET (5+) is a framework, yet it’s very different from the .NET Framework. Hence, we’ll use the term runtime in preference to framework, where possible
If you understand that, you are Genius!
But this book is named C# _10_ In A Nutshell?!?
Then a little further down…
Quote: C# 10 ships with Visual Studio 2022, and is used when you target .NET 6.
I’m not sure why you were confused.
Happy 20th anniversary .Net!!
Or maybe it’s really 20th birthday since .Net isn’t married to anyone??
Which means .Net still not old enough to drink but drives many others to it.
modified 29-Jan-22 16:39pm.
|
|
|
|
|
.NET Framework: .NET 1.0 - 4.8
.NET (formerly .NET Core): .NET Core 1.0 - 3.0, .NET 5 and later
The framework specifier is what MS uses to differentiate them. It's confusing now but I think their goal is to make it less so going forward since now there's just the unified .NET.
|
|
|
|
|
It's still just the .net framework.
|
|
|
|
|
And if you create a .NET (the framework formerly known as .NET Core) project with:
dotnet new classlib -n "foo" -lang C#
Which is the only way I know to create a .NET (the framework formerly known as .NET Core) library project, since I was using that because I couldn't find "Class Library" as there are so many freaking templates now and I just now searched for "library" for some reason and there it is "a class library that targets .NET Standard or .NET Core"...
...anyways...
It creates a .NET 6.0 project. But if you want it compatible with .NET Core 3.1 and you change the target project, it leaves this kruft in the .csproj:
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
and the ImplicitUsings and Nullable are not compatible with .NET Core 3.1 so you spend an hour googling and stumble across an SO post that says, go to the .csproj and set those to "disable."
So many emotions because VS 2022 doesn't do this one simple thing for you.
|
|
|
|
|
Marc Clifton wrote: the ImplicitUsings and Nullable are not compatible with .NET Core 3.1 so you spend an hour googling and stumble across an SO post that says, go to the .csproj and set those to "disable."
That is crazy! It’s no fun being the one to discover this nutty stuff when you’re just trying to get work done.
|
|
|
|
|
So where does .NET Standard fit in?
Oh wait, that's already being deprecated...
|
|
|
|
|
That was a typo - Microsoft never meant to make it standard... not one at least...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
modified 31-Jan-22 1:07am.
|
|
|
|