:fa_windows: That's Windows 7 for ya
-
Did I not admit that Zune was a failure? Not forgetting I have more than once criticised the asinine 'cannot open two files with the same name' in Excel. And the Status thread is a testament to the utter shittyness of Azure when something goes wrong. But unlike some around here, I am capable of recognising both the good and the bad of a company.
When did I said that ?
You heavily implied it.I just pointed to a dumb decision with facts, and you answered with "well, they are a multi-million company so they know better".
I said that they did the research and development required to reach a decision, whereas you're pulling 'facts' from your arse.Just pull your head out of MS's ass and use your brain
I have been. I have read plenty of arguments both for and against, and every time, the 'for' always comes out on top.
-
I just pointed to a dumb decision with facts, and you answered with "well, they are a multi-million company so they know better".
Have you considered that they investigated doing it the way you suggested, and likely found reasons why it wouldn't work? I doubt very much that they started with the intention of doing it ass-backwards just because.
I said that they did the research and development required to reach a decision, whereas you're pulling 'facts' from your arse.
Yeah, that.
-
You heavily implied it.
No, I did not.
I said that they did the research and development required to reach a decision, whereas you're pulling 'facts' from your arse.
Where did you get that they did ANY research ? Care to point to a document/article/anything that suggest they did ?The system32/WoW64 is so illogical, I've seen some documents on MS's site in the past that actually said that system32 contained 32-bit DLL while WoW64 contained the 64-bit, which is exactly the opposite of the truth. So confusing, even MS was confused about it.
Instead of saying "they know better because money", why don't you provide arguments as to why they could do the transparent redirect for 32-bit but not for 64-bit ?
-
I've seen some documents on MS's site in the past that actually said that system32 contained 32-bit DLL while WoW64 contained the 64-bit, which is exactly the opposite of the truth.
Documents can become outdated.Where did you get that they did ANY research ? Care to point to a document/article/anything that suggest they did ?
So if you were redesigning your number one product line, you'd do absolutely no research at all? Or would you do as much research as possible to make sure you do the job right?It doesn't take a genius to work out that, when you redesign your flagship product, you do the necessary research. To claim otherwise merely proves you have an agenda to push.
-
Where did you get that they did ANY research ?
Are you saying that you believe Microsoft just did it willy-nilly?
-
It doesn't take a genius to work out that, when you redesign your flagship product, you do the necessary research. To claim otherwise merely proves you have an agenda to push.
An agenda to push ?
You don't have any argument as to why the transparent redirect couldn't work the other way around, so you just accuse me of having an agenda.
It doesn't take a genius to realize that the same kind of redirect could work for 64-bit.
-
It doesn't take a genius to realize that the same kind of redirect could work for 64-bit.
Yet you haven't explained how it would work in the scenarios a number of us have listed above. Nor have you explained how you somehow miraculously know better than a company that's done the research required.
-
Yet you haven't explained how it would work in the scenarios a number of us have listed above.
What scenario ?
When a 32-bit apps opens system32, it gets redirected to WoW64.
What I keep saying is, when a 64-bit apps opens system32 (because morons hardcoded the path), it gets redirected to system64. Simple as that.is wrong with
youthat ?
-
Probably something you haven't thought of, which is why they didn't do it that way.
-
Are you saying that you believe Microsoft just did it willy-nilly?
Often, engineers seems to think that the best solution is the most complicated one.
-
Because Windows 64-bit is emulating Windows 32-bit. That's what WOW stands for, "Windows On Windows (64)".
-
@hungrier said:
Are you saying that you believe Microsoft just did it willy-nilly?
Often, engineers seems to think that the best solution is the most complicated one.Willy-nilly. There is no excuse to name it
WOW64
other than thinkingW32OW64
is more key strokes. Unless it is over engineered to later supportW128OW64
, hmm maybe then
-
Yeah it makes perfect sense, it just has a bad name.
And I'm sure as hell not going to take any guff from a competing OS whose headline graphics program is named "GIMP".
-
from a competing OS whose headline graphics program is named "GIMP".
They did not spend millions of dollars and hire top talents and marketing department with fat salaries. GIMP is a perfect name coming from a bunch of hippies giving free code away and it does the job fine.
-
There is no excuse to name it WOW64 other than thinking W32OW64 is more key strokes.
Since it's actually called
SysWOW64
it could be for backwards compatibility with the 8-character filename limitation.
-
They did not spend millions of dollars and hire top talents and marketing department with fat salaries.
Do you think Microsoft runs the name of the 64-to-32-bit emulation layer by their top talents in the marketing department? Seriously?
-
What I keep saying is, when a 64-bit apps opens system32 (because morons hardcoded the path), it gets redirected to system64. Simple as that.
I bet that was the first solution they tried; the fact they didn't use it means it clearly didn't work.
-
Meanwhile in Windows 10 land...
"So you put me to sleep? OK, no worries."
"Oh my god, WAKE UP, WAKE UP, he unplugged the headphones!!!"
-
unplugged the headphones
Lucky! My laptop somehow lost the ability to detect if I have headphones plugged in or not!
Before-10 process:
- Volume is at 100% because crappy speakers
- Plug in headphones
- Windows notices the output is different and adjusts it to the previous level for my headphones (a paltry 21)
- Move on to next task
Post-10 process:
- Volume is at 100% because crappy speakers
- Remember that plugging in headphones without preparation is a Bad Idea, and manually adjust the volume down.
- Plug in headphones
- Sigh in relief at another eardrum blowout averted.
"Oh my god, WAKE UP, WAKE UP, he
unplugged the headphonesshut the lid!!!"
Also this.
Why I have to tell my PC to sleep at least twice (three times if plugged in and unplugging after sleep, twice only if already unplugged) is beyond me.
-
Why I have to tell my PC to sleep at least twice
Be thankful you do not have to sing lullaby and read 2 good night stories for her to sleep.
-
That's clearly the wanted behavior, since Microsoft spent millions designing Win10 and they have thousand of engineer / designers / etc and they know better than anybody
-
Why I have to tell my PC to sleep at least twice (three times if plugged in and unplugging after sleep, twice only if already unplugged) is beyond me.
Got a Microsoft mouse? Try: immediately after directing the system to sleep (and before it does) turn off your mouse. My mouse sends "wake-up" movements, even if it isn't touched.
-
My mouse sends "wake-up" movements, even if it isn't touched.
That's... Actually a great idea! Except the systems this happens on the most don't typically have external mice plugged in...
-
That's... Actually a great idea! Except the systems this happens on the most don't typically have external mice plugged in...
Well, just an idea.
-
-
OK, now you're just being stupid
-
You seem.... familiar....
-
Lounge<C++> says hi.
-
I figured.
I really wish the C# lounge was as well put together. I learned a lot from just hanging out in C++. Then the company I was at blocked all chat rooms.
So, now I hang out here, where I learn more about getting pissed off at existing technology...
I made friends with sbi on twitter. Turns out, he's very liberal, and doesn't like conservative satire in the least. Like, really hates it... So, I figured it was best for some people if they can pretend other ideas don't exist.
Well, good to have you.
-
You seem to be missing something called humour.
-
You seem to be missing something called inteligence
-
You seem to be missing something called a
l
-
-
That's... Actually a great idea! Except the systems this happens on the most don't typically have external mice plugged in...
-
https://www.amazon.com/dp/B000O3S0PK/ref=cm_sw_r_other_awd_dxk5wb6EBE5DZ
That's hilarious!
-
My wife has a nosy coworker who likes to gossip about who goes idle for how long while they are working from home. I bought one of those for her laptop that she plugs in on her work from home days. Nothing gets installed, so no one ever knows and cunty coworker doesn't say anything snide about her Lync showing idle.
-
So just close the lid without shutting it down.
powercfg -lastwake
... Friendly Name: Description: ACPI Lid Manufacturer: (Standard system devices)
Window7, the Lid wakes up my work laptop out of sleep? While the lid is closed on the desk!
This happened twice now after I was looking for it.
-
-
About the SysWow64/System32 thing, my understanding about the reason they did it in that direction (32-bit programs get redirected) was because the intent was to have 64-bit programs be able to access folders without redirection; that is, the redirection would only take place for older programs, not for new software. A 64-bit program sees folders and their contents as they exist on disk; a 32-bit program run on the 32-bit virtualizer effectively sees a 32-bit system. Going the other way around, newer programs written against the modern instruction set would be seeing disk contents (and registry location) in a way that did not reflect how they actually were- and the older software would see things properly, which is a mechanic that tends to be reserved for compatibility considerations.
-
-
-
-
@FrostCat is that an insider build or are you just from the future? And if it's the latter, how's life under Donald Trump?
-
-
@RaceProUK said:
A lot more than having 64-bit DLL in system32 while the 32-bit are in WOW64
Which wouldn't have been required if it wasn't for 20 years of total retards hardcodingC:\WINDOWS\system32\
in their programsprograms written by retards should fail instead of the OS becoming as retard as them
-
@blakeyrat said:
Except those morons will instead simply advise their company to not upgrade their OS, then Microsoft's supporting Windows XP long into the 23rd century.
they should drop support in their normal schedule. fuck retards.
-
@RaceProUK said:
their hundreds of thousands of developers, analysts, and designers, especially about matters that would have had millions of dollars invested in investigating.
and the technical decisions of importance are still taken by one or two retarded in a suit. that's what happens in wtfbank at least.
-
@fbmac said:
programs written by retards should fail instead of the OS becoming as retard as them
Congratulations, you've just pissed off every enterprise customer you have and lost billions of dollars of revenue
-
@Deadfast said:
Meanwhile in Windows 10 land...
"So you put me to sleep? OK, no worries."
"Oh my god, WAKE UP, WAKE UP, he unplugged the headphones!!!"My family's PC manages to wake up when someone turns the light in the kitchen on. How, I have no idea, but I suspect it has to do with really shitty electrical wiring.
-
@TimeBandit said:
Because the path is hard-coded as system32. Did you miss that part?
Did you miss that part ?
when executing 32-bit applications, WoW64 transparently redirects 32-bit DLLs to %SystemRoot%\SysWoW64, which contains 32-bit libraries and executables. 32-bit applications are generally not aware that they are running on a 64-bit operating system. 32-bit applications can access %SystemRoot%\System32 through the pseudo directory %SystemRoot%\sysnative.
They already do a redirect to WoW64 for 32 bits apps, why not do the other way around instead ?
Oh, right. Because whatever stupid thing Microsoft does, you'll keep defending it while ignoring every proof right in front of you. That's why
Because 64bit apps on 64bit Windows should be the default. Compatibility shims for the default use case are fucking DUMB.