|
honey the codewitch wrote: i had to run out and buy a DVD-ROM to fix it. Couldn't use the bootable USB using the Media Tool? I have re-installed my in-laws pc from there a couple of times and was surprisingly fast and "friendly"
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I did, hence the bluescreens.
Old windows 10 isos hate Ryzen cpus.
Real programmers use butterflies
|
|
|
|
|
Really?
I wanted to change to a Ryzen 7 in my next setup...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
They're great CPUs, even if Microsoft screwed up an old copy of windows 10
Real programmers use butterflies
|
|
|
|
|
Why would you use an old ISO?
|
|
|
|
|
Because it's what I had on a flash drive + had a license to (a copy of pro, but home shipped with my PC, except the product key was defaced - joy)
Real programmers use butterflies
|
|
|
|
|
If you have a license for win 10, you are good to go with the latest iso. All you save is the download time, and you will pay that back with interest as it updates.
|
|
|
|
|
I didn't have a product key that would work. In the end I didn't need one. I guess there was one stashed in my UEFI after all, it's just the tool i used to check for it didn't pick it up for some reason (though it was in the registry of my old install)
Like an elephant, I didn't check the back of my PC for the product key - the fact that there was one of those product key labels on the disc envelope which was defaced had me fixated on that, rather than it occurring to me that they could have put it somewhere else. Anyway, it didn't matter because I had that product key from the registry of my old install.
It didn't work on any of those isos i could download from microsoft.
It *does* work if i choose "i don't have a product key" - then it activates. Also didn't occur to me to try that, since i had a product key.
I still think it's weird that the product key won't work. It *is* the product key for this machine.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: The windows install was utter hell. At least a dozen blue screens and i had to run out and buy a DVD-ROM to fix it.
Check your hardware.
In an earlier life I worked as the "IT-guy" handling a few hundred computers, servers and networks, and if it wasn't a driver issue (seldom), it was a hardware issue (usually).
Hardware issues can be hard to pinpoint, sometimes it's even a combination that won't play nice
|
|
|
|
|
My hardware is fine and brand new. The new system drive was unboxed the day of the install.
The issue was that old windows 10 isos hate Ryzen cpus.
Changing the iso fixed the problem.
Real programmers use butterflies
|
|
|
|
|
I'll write that down as a driver issue (hardware not supported), even if there's no driver involved.
Out of curiosity: Did you get any warnings?
|
|
|
|
|
It's a bug in Microsoft produced drivers. they also put a typo in one of of their USB drivers in that iso and they were registering a CPU device as a "USB HID Button" and failing to install it (of course)
Real programmers use butterflies
|
|
|
|
|
So they HID the driver?
Sorry, couldn't resist
|
|
|
|
|
Actually, that's accurate.
I don't know if it's related to the bluescreen issue. I just know there's at least one, perhaps two errors in that ISO and one of them was making it bluescreen.
Real programmers use butterflies
|
|
|
|
|
Here in Florida I have Spectrum service. On an Ethernet connection (not WiFi) I get 496 MB/s. That is more than we need.
Get me coffee and no one gets hurt!
|
|
|
|
|
Wow. I wonder if my Palm Beach client knows about that. That's amazing.
Real programmers use butterflies
|
|
|
|
|
I forgot to mention: That is the download speed. The upload speed is less than 30MB/s.
Get me coffee and no one gets hurt!
|
|
|
|
|
honey the codewitch wrote: plugged it into a wire today
That's probably the best decision some people could have made in a long, long time.
As much as I hate getting tangled in wires, I hate wireless. With a passion.
|
|
|
|
|
(I broach this subject here because I don't think there's an answer. Note the "rant" icon.)
Consider:
ObsoleteAttribute -- Marks the program elements that are no longer in use.
What would be the opposite/complement? A way to mark some code as not-yet-ready-for-primetime?
Not to the extent of throwing a NotImplementedException , because the code exists and works (mostly).
Not a todo either; that's too passive.
But, if I have a kludgey Method I intend to rework at some convenient future time, I want to be reminded about it every time I compile code which calls it. Even if the Method has been compiled into a DLL.
An ObsoleteAttribute will do this -- but I expect that it would be confusing to my colleagues.
Even a UseAtYourOwnRiskAttribute would be better.
|
|
|
|
|
PIEBALDconsult wrote: A way to mark some code as not-yet-ready-for-primetime?
[UnderDevelopment]
[Future]
[ComingSoon]
PIEBALDconsult wrote: But, if I have a kludgey Method I intend to rework at some convenient future time, I want to be reminded about it every time I compile code which calls it.
[Sh*ttyCodeAhead] (self-sensored that, lol)
[KludgeyCode]
|
|
|
|
|
Marc Clifton wrote: [UnderDevelopment]
[Future]
[ComingSoon]
[BetaQuality], and presumably [AlphaQuality].
Not a .Net developer, but it looks like you can create your own Attributes: Writing Custom Attributes | Microsoft Docs, so maybe actually doable?
Keep Calm and Carry On
|
|
|
|
|
Could work if they allowed deriving from ObsoleteAttribute . But. They. Don't.
|
|
|
|
|
For probably good reason. [^]
Also that article is a solid introduction
|
|
|
|
|
Idea:
what about a Custom Codeanalyser NuGet-Packet, witch contains the Attributes and does the Messages for them.
but might be a little overkill
|
|
|
|
|
[Incomplete]
[LitelyTested]
[CutAndPasteAtYourOwnRisk]
[CodeProjectQAQuality]
[hmmmmNotSureAboutThis]
[YouFeelLucky]
|
|
|
|