Same

same

Same

Same

same

- So... how we are going to detect unicode? - -Meth- Math

@@user-fw8ry1tq4y Meth?

​@@RDCSTi was gonna _crack_ a joke, but that wouldn't be funny

I mean it was good enough because it "rarely" occured, still the amount of false positives is indeed too much and yeah it was pretty bad

It acts like a detector for windows's "Unicode" files that only have English characters, but with a lot of false positives.

wait what

@@Axcyantol A fly (the type of insect) explaining bugs (computer errors, but the word also means insect)

He also... Well creates bugs too (By that I mean destroying windows)

@@amberwingthefairycat no i understood it, i was just surprised about it being a fly explaining bugs

@@Axcyantol Oops, sorry, haha.

"W." stands for WordPad

Amazing how he started hiding the facts at least 7 years before it happened

Now its George L. Bush, 'cause he hid the facts

George Walker Bush Sr. ruled 1089 to 1992, and did secret government stuff with Nixon and Reagan .

do you know what i can believe bush did?

That video is best video.

i think you made the video a little too popular, still, good one 👍

WordPad is too powerful for us mortals

​@@FlyTechVideosyea, nothing can break it

Notepad is a decedent of wordpad

@@npoaccount9154 wasn't there a video about corrupting the heck out of windows 10 and everything was broken except for wordpad

@@npoaccount9154 as soon as i read that, i tried breaking it. i ended up creating a document filled with a creepy smiley face image with the size of 2,306,727,936 bytes (that's 2.3 gb). i cant open it because it's too big, and i think i corrupted the file by closing wordpad while it was saving the file. i still dont think this counts as breaking it, i think its just the file thats broken.

There's not just those variants either. There's the obsolete UTF-7 too (for some reason), and the multi-byte encodings come in both Little Endian and Big Endian flavours.

@@weakspirit_ internally, yes. but when saving text it does default to utf8, since a text in 7-bit ascii and in utf8 are the same, and since in english you rarely need characters beyond that, using utf8 is more space efficient

UCS-2 and UTF-16 is more or less the same (and what windows / C-sharp incorrectly call "unicode encoding".)

Technically ANSI Windows-1252 (what is functionally always used when Windows refers to "ANSI") is incompatible with UTF-8 as there are numerous UTF-8 bytes which are "reserved" (usually for multi-byte characters) which Windows-1252 uses as printable (single-byte) characters. If any of those bytes exist in the string when read as UTF-8 the encoding will break, which in a well developed system will merely produce a few erroneous characters. Now since Windows-1252 extends standard ASCII, most of the bytes in Windows-1252 will be read well in UTF-8, specifically all the common American used characters. The problem with the encoding only occurs when you have these non-ASCII characters either in Windows-1252 or in UTF-8, in which case if you try to read the either UTF-8 from Windows-1252 or Windows-1252 from UTF-8, you will get problems. Experienced this exact issue when dealing with a game that reads and writes Windows-1252 but which has resources written in UTF-8, causing all sorts of weird problems.

@@laurentverweijen9195 UCS-2 can only represent ~6% of the reserved Unicode codepoints and ~69% of the ones already assigned , whereas UTF-16 can represent them all through surrogates. Don't get me wrong, UTF-16 is the worst Unicode encoding, but at least it *is* a Unicode encoding, unlike UCS-2.

I think he not dive, he just wrote his own that works similar... Maybe, idk

@@thevorkman_6551 He went into the code to figure out how it worked, and then wrote his own that worked the same

Don't forget the special... _sources_ ;)

@@mstech-gamingandmore1827 Yes)))

XP source leak probably

I'm an programmer in my free time, and this is actually facts. 😂

@@AlphaFruit-hx4cw which Bush hid

you're spitting FACTS

@@nt-authority-system666bush wasn't

oh wait, but that does mean that a non-word aligned newline could technically trigger it, right? should have spent more time researching nooooo

just make this comment your string so you can win the meta award

Same

Sounds like it'd be related to homer simpson creeping out of that bush gif.

Same

My wife's bush hid some facts. I'm catholic, so I discovered the truth only after the marriage

Yeah, for people not from USA, or not familiar with USA's presidents, the name "Bush" is likely going to refer to an actual bush instead.

what’s that?

yeah what’s that?

@@chri-k To keep It simple, C64 BASIC has a random number generator that, every time you turn on the machine, it always produces the same "random" sequence of floating-point numbers, all between 0 and 1. Using this "feature" someone wrote a small program (4 lines of code) that print the sentence "Bill Gates Sucks" on screen

Windows uses little endian because the x86 CPUs do so .

because x86 (which windows and every single os that supports x86 runs on) use little endian, so fuck intel i guess

Write a simple program converting from integer to string and you will find out why little endian is a thing. Btw, the numbers we are writing everyday is big endian.

@@RedstoneNguyen Both storage directions make perfect sense . Little endian for decimal digits is how Arabs write Arab numerals, big endian is how westerners write the same numbers with the same digits . Because computers gulp up entire binary numbers in one memory clock cycle it's entirely cultural for them too . The x86 and x80 CPU families belong to little endian design cultures, the 68000 and SPARC families belong to big endian design cultures . ARM and PowerPC hardware is bilingual in this matter .

@@johndododoe1411 i didnt say anything about culture. My idea is, little endian is mathematically simpler to implement than big endian.

I tried disassembling it, but it seems to have been moved to the kernel (RtlIsTextUnicode)

It uses the 2 bytes FF and FE shown at 5:24. To make the glitch happen on modern Windows you put ÿþ into the beginning of a text file, then save it, and voila! You don't even need to input any special text after it.

they probably do the sane standard thing and look for 0xFFFE at the start

@@Milennium1902**Icelandic obtains ÿ**

@@lydianlights They did that back then, too, but that's not nearly enough. The _presence_ of the BOM _confirms_ a file is unicode. The _absence_ of the BOM _does not_ mean a file is _not_ Unicode. That is to say, if there is no BOM, you still have to check if it's Unicode.

By not text I mean archives, executables, etc.

but most modern applications ( one exception being Windows itself ) use UTF-8 and not UTF-16. UTF-8 is fully backwards-compatible with ASCII, so this may not be the only reason.

It's not padding, it's the page number . Page 00 is mostly the same as Western ANSI code, there are about 7000 other pages to keep track of, including the ones with smiley faces .

All characters are Unicode characters. Some characters are also in ANSI, but they are also in Unicode.

Saves And Does Not Corrupt On Windows XP Media Center Edition 2005.

@@AdachiVlogsFIN Confirmed on mine

whats M69 doing here

NO WAY LMAO.

tried it on my windows XP vm it worked

does that string really worl?

He hid the fact that he personally assassinated JFK

kzfaq.infoAtu7atNw-kw

what more can you expect from windows 11

​I mean, it's an insider build. You would expect bugs

i'm pretty sure nothing stops you from posting 9/11 in this comment section

@@FlyTechVideos a different commenter said that "11:44 I can't do that as any link (sometimes even links to KZfaq) cause the immediate deletion of the comment, meaning it's visible to its author until page reload, edits fail ("Unknown error") and reloading the page makes it disappear. Only the creator of a video can post links in their own comments section without needing to be worried" youtube likes censoring the comments

UTF-8 didn’t exist when IsTextUnicode() was written. The Unicode encoding in use was UTF-16 (based on the earlier UCS-2). So this is legacy code from the early days of Unicode that was never updated.

69th like

You can hide facts in a bush ... ... ..

@@OrbitalCookie Ah yes, my favourite hobby.

Exactly what I thought!

Thanks! 😀

No

No

Fly!

@@r0fael_programmer and the no chain is already broken

@@busymaan cause its kind of cringe

Thank you! I only ever uploaded 2 of them, and no, I am not planning to continue them as I came to dislike even the 2 videos that I already made.

I tried it with after the video, and the oracle says that it's censored while Notepad still doesn't break

please explain in detail.

by checking if the file starts with 0xFFFE

The Bush that "hid the facts" refers to the junior one, doesn't it? (Iraq war?)

@@FlyTechVideos Bush Sr. hid two facts though: That his son is a liar, and that he was a madman that almost started the WW3.

en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows en.wikipedia.org/wiki/Windows_Notepad

They did - 0xFF 0xFE was consistently recognized as Unicode. The problem is that they assumed that text without this prefix can be Unicode as well, and they used the presented heuristic to guess

@@FlyTechVideos sounds like somebody in Microsoft didn't read the documentation all the way 🤣

Microsoft detects Unicode even without the byte order mark by design since other programs and/or platforms may save text files like that.

UTF-16. Then they wanted some nice 🥵emojis and even ♔chess. Then UTF-32 appeared. yet UTF-8 is variable length which saves the space but not the nervecells of c++ devs

In the old Windows World's favorite unicode encoding. Which they got stuck with, even though it was a bad idea, because they were too eager to use unicode and more sensible unicode encodings hadn't caught on yet.

@@Gameplayer55055 ♔ fits in 16-bit character though

It looks like they encoded the code points directly. They did not use UTF-8 encoding or else ASCII characters would be only one byte, and they did not use UTF-16 encoding either because UTF-16 is not padded with NULL bytes. In other words, they succeed to mess up their Unicode implementation and invent a new encoding while Unicode was supposed to unify everything. Oh the irony...

@@cl00e9ment All ASCII characters do have null byte in high byte when represented in 16-bit integer though. 0x20 in 8-bit becomes 0x0020 in 16-bit, which becomes 0x20 0x00 in little endian, which is the correct little endian representation of space in UTF-16.

correct

He already did: devblogs.microsoft.com/oldnewthing/20070417-00/?p=27223

doesnt work on Windows 10... but on notepad2.

You're right... thanks for the suggestion

💀

If you consider mojibake secret, then yes

@@FlyTechVideos Well no because it's fixed in newer versions of windows.

I live in ukraine and i've seen many university pages full of them (idiot devs, no ) After making essays in vscode i can see some mysterious п»ї too. its shit from BOM as i know

@@nothing-lo8lh You can cause it by adding ÿþ to the start of a .txt file

Which is easily mixed up with all the other 8-bit encodings leading to more glitches!

@@jhgvvetyjj6589 for text, really only plain ASCII or UTF-8 is used, at least in sensible systems

Wow

Character count: 1016 3 * Higher Diff - Lower: -85 Tested successfully on Windows 2000 pro With the heuristic outlined, it's fairly easy to make arbitrarily long strings, especially if you aren't overly concerned about clarity, word flow, or long term sentence structures. I wrote the comment without significant scripting/code assistance (only checking the isUnicode value every sentence or so).

@@liniarc I’ll try making one I think

Not sure if they _can_ , but I think I've seen some. Don't take my word for it though

even blog posts can.

I think so

generally self-published content is not supposed to be used as a reliable source for a citation, but in this case, i guess it could be used as a showcase of a behavior mentioned in the article

@@FlyTechVideos I've been working on that exact same question for a different video lately (a Karl Jobst documentary). The short version is that the video can not be used unless it is published by a reliable source. Since KZfaq videos are self-published, they don't count. An exception can be made if the person who posts the video is considered a subject matter expert. We've discussed that for Karl Jobst, but determined he doesn't qualify. For it to work, Jobst would have to have published articles about his work in trusted sources, outside of KZfaq, and he hasn't done so. What that means for your video: Have you published journal articles about PC bugs, under your name? (Just being cited by them is not enough.) If the answer is "yes" then that's great! Please give us a link to that. With some luck, that will make you pass as a subject matter expert, and THEN we can start thinking about citing your KZfaq video. P.S. For Jobst's video, we could avoid citing the video in the end. Jobst presented all his sources in the video. References to reliable sources that demonstrate that his conclusions were correct. Can you share such a source for your topic? In that case, we can start working on the Wikipedia article as well.

While if someone types with just a few Unicode characters thrown in, the ASCII values will produce the null bytes seen at 5:11, which also won't add to the most-significant-byte-difference counter.

The windows world started using unicode before utf8 was invented. The Java world too. Sometimes it pays to be slow (although I remember switching my old redhat/mandrake systems over to default to utf8 was not fun either).

Unicode was created in the late 1980s. Microsoft and Java chose the early 16 bit Unicode and then had to use UTF-16 to encode the next few thousand pages . Then someone decided that any characters not handled by UTF-16 should be banned from all other encodings .

A unicode string with "simple" characters usually has a lot of null bytes, e.g. 42 00 43 00 44 00 ... and the heuristic is engineered to detect exactly this. As we can see, this leads to false positives

​@@FlyTechVideos Is that logic true across most languages or is this an English bias? Are there any countries where it's not true?

buggy gpu driver?

When I used RTM version of Win 11 on VMware after release, while using paint crashed into BSOD in few seconds so could be a VM problem

10gb+ files

Win11 notepad is very buggy, it can't even display actual text files .

@@johndododoe1411yes, microsoft made notepad slower than notepad++ same with cmd.exe (old one still exists as conhost.exe)

the word "sources" is italic

@@Milenakos Ahhhhhhh ok I'm dumb

@@the-Gammaron I still don't understand that about the sources, can someone explain it to me? is it some joke or something?

@@maximiliano_sv Basically Microsoft does not allow everybody to see the Windows source code or disassemble Windows to get the closest thing to the original source code, ChatGPT explains those things better than me: The source code of Windows is a set of instructions and programs written by Microsoft developers, forming the foundation of the operating system. While there are several reasons why an ordinary person cannot legally read the source code of Windows, here are some of the main ones: - Intellectual property rights: The source code of Windows is owned by Microsoft. The company invests significant resources, time, and effort in developing and improving their operating system. As a result, they have intellectual property rights over the code and can control who has access to it. This means they cannot allow just anyone to access and read their code without authorization. - Protection of trade secrets: The source code of Windows contains valuable and strategic information for Microsoft. Disclosing that code to unauthorized individuals could compromise the security, stability, and competitiveness of their operating system. Protecting their trade secrets is crucial for maintaining their market position and competitive advantage. - Risk of vulnerabilities and hacking: If the source code of Windows were available to the general public, it could be scrutinized by malicious individuals, including hackers and malware developers. This would increase the risk of discovering vulnerabilities and creating targeted attacks on the operating system, jeopardizing the security of millions of users. - License and end-user agreements: By using Windows, users agree to the terms and conditions set by Microsoft in their license and end-user agreement. These documents clearly state that users do not have the right to access, modify, or distribute the source code of the operating system. - In summary, the source code of Windows is owned by Microsoft and is protected by intellectual property rights and trade secrets. Its widespread access is not permitted to safeguard the security, competitiveness, and legal rights of Microsoft, as well as to prevent potential risks to users of the operating system. Disassembling parts of Windows to figure out the source code presents legal and practical challenges. Here are the reasons why an individual cannot easily disassemble Windows to obtain the source code: - Legal restrictions: Reverse engineering, which involves disassembling software to understand its underlying code, is subject to legal restrictions in many jurisdictions. Companies like Microsoft have legal protections in place to prevent unauthorized access, modification, and distribution of their software. Engaging in reverse engineering without proper authorization or a specific legal exception can infringe upon intellectual property laws. - Technical complexity: Disassembling software like Windows is a complex process that requires expertise in low-level programming languages, assembly code, and system architecture. It involves converting machine code (binary instructions) back into human-readable form. Understanding the disassembled code and piecing it together to reveal the original source code is a challenging and time-consuming task that requires significant skill and knowledge. - Incomplete information: Disassembling Windows and examining the disassembled code may provide insights into specific functions or algorithms, but it does not yield the complete source code. The source code of a complex software system like Windows consists of millions of lines of code, libraries, and dependencies, which cannot be fully reconstructed through disassembly alone. - Trade secrets and obfuscation: Software developers often use techniques such as code obfuscation to make disassembly and reverse engineering more difficult. Obfuscation intentionally complicates the disassembled code by adding irrelevant instructions, removing meaningful variable names, or applying other transformations. These measures aim to protect trade secrets and intellectual property by making it harder for unauthorized individuals to understand and reproduce the original source code. - In summary, legal restrictions, technical complexity, incomplete information, and code obfuscation make it challenging and legally risky for an individual to disassemble parts of Windows and obtain the complete source code. Reverse engineering is a highly specialized field that requires expertise, and engaging in it without proper authorization can have legal consequences.

Thank you lol

dreamscape is content-id protected and because i am not desiring to donate all my income to 007 sound system i would rather not but yes

lol

That will overwork him

@@thepikachugamer Why? He is making videos every 4 months! Is it too rare?

​@@CBFNetworksInternational Petition for you to 1. not decide that for another person and 2. to do your math

@@Alexander-oh8ry Petition to you to 1. do not send me messages if you're a alexander (yes, it's on purpose) and 2. not to make me do things that I shouldn't do today or after 2 weeks

@@CBFNetworksInternational dam somebody sounds insulted because they cant force a youtuber to do more videos and is called out for it (and because they cant do math)

Glad you liked it!

You added additional spaces inside words, that's cheating! (Also, you need punctuation) nonetheless a cool attempt at scripting :)