|
The display could be tied to international settings?
How does it report a MB size file like TrackingData.log?
Mac was the only platform that I knew that used 1,000 bytes to equal 1KB. This let their 1.44 3.5inch floppy disks appear even larger than the 1.2MB 5inch floppy that many DOS/Windows competitors used at the time. (circa 1986)
|
|
|
|
|
Yes, it is "international" in the sense that it honors my format preferences. I prefer grouping digits 3 by 3, I prefer a decimal comma rather a decimal point, and if I set the number of decimals to 3, an MB file size is reported like '15,9 MB (16 693 612,000 bytes)'.
The issue here is neither the use of M rather than the correct Mi, the kind of digit grouping or kind of separator, but the use of a decimal point (/comma) and fractional part when presenting an integer number. When teaching programming, I always refer to count values, which programmers like to call 'int' or 'long', and measurement values, which programmers like to call 'float' or 'double'. That makes it much easier for the students to learn when to use int and when to use float. Those programming this Property sheet obviously has not grasped the idea of the number of bytes being a count of bytes in the file. They treat it as if it were a measurement on a continuous scale.
For the Ki/k and Mi/M question (which is a different issue): All hard disks I ever have been in touch with, regardless of computer family, have had their total size specified in decimal units, like k, M, G and T. Networking people always specified line speeds in decimal units - in bits, not bytes. A 64 kbps line (56 kbps for those in North America) transfers 64000 (56000) bits per second.
Floppies arrived before ISO had defined the Ki, Mi, Gi, Ti, ... prefixes, and things were kind of messy - that is why ISO/IEC decided to clean up the mess by defining the standard binary prefixes. There are lots of examples of mixed use of e.g. decimal number of binary units. (The ISO/IEC standard is well above 20 years old now; yet there are lots of people stubbornly resisting to relate to it, insisting that 'We have been using ambiguous units for years, we insist on continuing to do that and do not want to clean up the mess!'
For the 1.44 MB floppy disks: They did have higher capacity than the 1.2 MB floppies. Maybe it wasn't quite 1.2 times as much - I am not taking the effort to look up the historical details, but when the 3.5" floppies arrived, they did have a (real) higher capacity than the 5.25" ones.
If you go far back in history: In the 1950-60s, machines addressed memory by the word, not by the byte. Memory sizes where given by the number of addressable units: words. Then IBM came with their 360 series, the first major computer series that were byte addressable, and they marketed their memory options by the byte. But their 'kilo' was 1/4 or 1/4.5 (there were lots of 36 bits machines at the time) of the 'kilo' of the competitors. This caused a lot of uproar in the 1960s.
Another unit that has been argued: Well into the 1980s (maybe someone may say even slightly into the 1990s), a byte was recognized as the space required to store a textual character. The Univac 1100 series had two byte size options: Either 6 bit, for 'Fieldata' code, uppercase only, 6 characters to a 36 bit word. Or 9 bit code, usually for ASCII, but when 8 bit character encodings entered the scene, they could be held in a 9 bit byte. The DECsystem 10 and 20 mainframes, also 36 bit machines, went for 7 bit bytes, fitting 5 characters into a word with 1 bit to spare.
In those days, if you were a radio amateur wanting to transmit digital data over your shortwave radio, in many countries you were required to use the 5 bit bytes defined by 'Baudot' telegram code standard. I don't know if that limitation ever existed in North America, and I have never heard of it being enforced in Norway, but formally, it existed longer than anyone would believe.
|
|
|
|
|
Thanks for the followup. I have been in my current post longer than the standard!
“kibibytes” sounds like a good name for a dogfood! (kibble)
I guess comp sci graduates after 1999 will know this.
I am curious now to see if advertisements for memory modules will use the correct prefixes.
|
|
|
|
|
What to expect?
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
chaos, mayhem and rivers of blood.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
So everything in normal then...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
Yes, it's Windows nothing more to say.
|
|
|
|
|
Is that cynicism still warranted?
I manage several industrial automation networks. We did have to do a lot of work for the DCOM hardening changes that were rolled out over the past 18 months. But other than that I cannot remember having breaking changes in many years.
|
|
|
|
|
Maximilien wrote: rivers of blood.
Plural?
I was hoping for only one river this time.
|
|
|
|
|
well, it's a multi-threaded OS ...
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
Yes, expect chaos! I don't know what it was, but a couple of days ago my laptop started making noises whenever it went into sleep mode. At first, I couldn't figure out where it was coming from. I opened my door and looked outside. I could swear I was hearing gusts of wind, but there was no wind. Then, I realized the noise was coming from my laptop. I can't tell if it's some sort of virus/malware, or if it's a feature implemented by Microsoft. If it's Microsoft, then it's the most stupid thing I've ever seen Microsoft do, and that's saying a lot. There's no shortage of stupidity when it comes to Microsoft. Why would I want my laptop to make breathing sounds as though it were actually sleeping? What's next? Snoring? Will the next update cause my laptop to scream upon exiting Windows?
|
|
|
|
|
Steve Raw wrote: I can't tell if it's some sort of virus/malware, or if it's a feature implemented by Microsoft. I thought lately it was more or less the same...
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.
|
|
|
|
|
That's what makes it so difficult. I have to ask myself, is Microsoft really that dumb? They must be.
I've been looking everywhere to figure out what it is and how to turn it off. It only comes on when my laptop goes into sleep mode. If it were a virus/malware, then I have to wonder. Who is dumb enough to make such a stupid thing?
Either way, one thing that I am sure of is that we have an idiot on the loose, somewhere out there. Finding out who that imbecile is would be like searching for a needle in a haystack.
|
|
|
|
|
Steve Raw wrote: It only comes on when my laptop goes into sleep mode. Suddenly from the very beginning? Maybe the fans? I remember having a friend with similar complains and in his case was a problem of temperature. In the moment he closed the lid the sleeping mode was not switching everything "off", so it became hotter and the fans started to yell.
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.
|
|
|
|
|
Nelek wrote: Suddenly from the very beginning? Maybe the fans? I remember having a friend with similar complains and in his case was a problem of temperature. In the moment he closed the lid the sleeping mode was not switching everything "off", so it became hotter and the fans started to yell.
I know for sure that the sound is coming from my speakers. I turned the system sound off and was no longer able to hear it. It sounds just like someone sleeping. You can hear it breathe and then it pauses for a few seconds. It repeats indefinitely as though it's on a loop.
|
|
|
|
|
Steve Raw wrote: You can hear it breathe and then it pauses for a few seconds. It repeats indefinitely as though it's on a loop.
:shiver:
This thread is beginning to scare me.
|
|
|
|
|
Ok... that's weird.
I remember hearing the radio in the interphone of my old school during the night... the first time I hear it I was smoking a joint and I thought I was having auditive allucinations
And it was damned consistant... everynight, the whole night.
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.
|
|
|
|
|
you have got to be kidding me! wait one..... okay, it's not april 1. Seriously, it makes SLEEPING noises? That has got to be some punking code that got missed by QA.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
charlieg wrote: That has got to be some punking code that got missed by QA. Or that came with copy+paste from the Q&A
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.
|
|
|
|
|
Does the computer also pant when running a heavy program? Breath heavily when displaying pr0n?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I was hoping for rivers of lava, not blood.
|
|
|
|
|
A non-event.
Shortly after it became available, I had to set up a brand new machine that came with 11, so the first thing I did (after completing the initial setup) was to install the update.
I'm really not used to Win11, so I'm not in a good position to point out what's new/different.
[Edit]
Actually I misremembered. Since there was still nothing on that system, I just blew the OS away and did a clean install from the ISO, rather than upgrading, which always takes a lot longer.
Worked fine. Again, I'm not sure what it is I can bring up. If a clean install hadn't worked, it'd be in rough shape.
|
|
|
|
|
I did the update. A day later my machine reported another update! I did the last update and have had no issues. I don't know what was wrong with the first version of the update.
Ok, I have had my coffee, so you can all come out now!
|
|
|
|
|
I don't believe major updates (such as 21H2 -> 22H2 -> 23H2) streamline the monthly updates. So you probably went 22H2 -> 23H2, and then 23H2 immediately queried Windows Update and fetched the Cumulative Update for November (KB5032190).
|
|
|
|
|
no problems on my machines
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|