Unsupported Software: exists
Enderman: ( ͡° ͜ʖ ͡°)

Unsupported Software: *exists*
Enderman: ( ͡° ͜ʖ ͡°)

@@Anthonythetechguy2004 You can only have PC-DOS 1.0-5.0 or MS-DOS 3-5 in order for Windows 1.0 or 2.03 to work.

@Michal Lebeda I do not trust you at all.

( ͡° _ʖ  ͡°)

( ͡° _ʖ  ͡°)

@@StoneNicolas93 dude ur a roblox youtuber tf u doing here?


Past Enderman: Windows 9x and above
Present Enderman: Windows 1.0
Future Enderman: MS-DOS 1.0

@@sebmotions What Sonic CD has to do with Windows and MS-DOS?

Far Future enderman: <b>Installing Mark 1 on ENIAC</b>

Far Future enderman: *Installing Mark 1 on ENIAC*

MS-DOS 1.0 doesn't exist. 86-DOS was developed by Seattle Computer Products. Microsoft bought rights to this system, renamed it to MS-DOS and published MS-DOS 1.25. It was the first known version of MS-DOS with this name.

far far far far future Enderman:

Picking blocks from an uncapable player
(jk) Abacus

Мистер Помидорный Джо r/woooosh

Мистер Помидорный Джо r/woooosh

No no future Future enderman Windows -10

@@kiwiEverything Far Future Enderman: Memex


3:04 Explanation: This will appear if interrupts are disabled and the guest os execute "hlt"(instruction).
"hlt" is an instruction that halts the CPU until an interrupt occurs. Because interrupts are disabled, "hlt" essentially stops the cpu from running, hence the dialog.

For those who dont know:<br>Halt basically pauses interrupts

For those who dont know:
Halt basically pauses interrupts

@@fireball626 An external signal that informs the CPU something has happened, e.g. the user has pressed a key or the hard drive has finished an I/O operation.

why would interrupts be disabled its not like windows 1.0 runs on 32 bit long mode

@@realzguardian probably because some sort of bug would occur if an interrupt was received while loading, so they disable it until it they're done. Or, the system could've crashed, and disabling interrupts then a halt would essentially freeze the computer, preventing data corruption

there are some cases where an NMI (Non-maskable interrupt) could potentially kick the processor out of the halted state, that's an easy thing to get around, after the hlt instruction, just put a jmp instruction that jumps back to the halt instruction. it would look something like this:

.crash

       sti (stop interrupts)
       hlt (halt)
       jmp .crash


Microsoft Windows 1.0 "help i cant read anything whats going on" Edition

Microsoft Windows 1.0 for Blind People: the ear-rape noise will help you in using the machine.

@@nickplj12 That's not how you use that meme

@@nickplj12 Again, that is <i>not</i> how you use that meme. This is not the situation in which you'd use it.

@@nickplj12 Again, that is _not_ how you use that meme. This is not the situation in which you'd use it.

@@ITAC85 W E L L Y E S B U T A C T U A L L Y N O .

@@nickplj12 Well you need to shut up, but you actually need to shut up for the rest of your life.

@@ITAC85 mmmph mmph mmmph mmph (well yes but actually yes)


In conclusion:<br>Windows 1 on MS-DOS 7.1 = Major Graphical Glitches

In conclusion:
Windows 1 on MS-DOS 7.1 = Major Graphical Glitches

@@avi8aviate Plus an error that "the CPU has been disabled by the VM"

@@_lun4r_ Yeah, that too. I'm surprised there was never a Guru Meditation error.

Eh, since windows 1.0 was designed for nothing higher than dos 3.34, running it on higher dos versions resulted in glitching, but normally not to the extent that it is here. Probably due to the changes to the underlying kernel to dos to work better with windows 9x, such as long file name support.

@@avi8aviate guru meditation is vbox he uses vmware which instead gives "The CPU has been disabled by the VM."


1:00 Perfectly synced, as all things should be.


I'm sure it said Incorrect DOS version but it's unreadable.

you are right, I also installed Windows 1.0 on MS-DOS 7.10, but in VirtualBox and something was readable and while starting Windows it said "49085.Incorrect DOS version"
https://photos.app.goo.gl/YqxeDbYvciPFdWT78

@@sikorsp22 this appears when MS-DOS version is incorrect


This made a spider come out from under my desk, no lie


Welp, aleast this is somewhat more stable than Vista RTM.
I was expecting that to just get stuck in the BSOD.

Also, this doesnt needs a CPU to do a thing!

@Mystery Box it sorta is on old windows even though it spits out garbage data so

@Mystery Box It is. It's a primitive form of it, but it is. That gibberish is from the system memory, is purposely displayed.

You're right. today's phones are more powerful than Windows 1.0 computers.

it did get stuck on BSOD when I did it on MS-DOS 6.22 in VMWare Workstation 14 player on 1 Gigabyte of RAM, intel core i5 8th gen.

Why is everyone hating on Vista, it did nothing to you.

Yeah, the reason it spits out all that random text is because the text “incorrect dos version” isn’t correctly terminated, so it just spits out the rest of the WIN100.BIN file, which is the main kernel for windows 1.0.

emm. windows 10 is very ustable. can someone help. its my new os and its glitching. something like that if i click inti the notifications button it sometimes do bsod. my gpu is AMD Radeon HD 4730 (512MB) CPU AMD ATHLON II (2,60 GHZ, 4 CORES, 64 BIT) MotgerBoard:Something from gigabite. monitor is working well and cables are perfectly connected. it cannot be error of cables, but idk whats that glitching and blinking. (BSODs:VIDEO TDR FAILURE) Windows 10 Pro 2004

The windows vista sp1 is actually really good.


Umutcan - Earth The Planet <br>oof indeed


Oh so thats why windows 1.01 broke on dos 6.22.. i thought it was winworld that screwed the img files


1:00 Really Legit Microsoft Blue Screen Edit:why is this getting likes?

@@_-noxxon-_ you are AN IDIOT HAHAHAHAHA

@@_-noxxon-_ <b>The eight-year-old who just learnt a few things about MS-WIN, who is correcting everyone in an angry tone, even though, they may have just been joking.</b>

@@_-noxxon-_ *The eight-year-old who just learnt a few things about MS-WIN, who is correcting everyone in an angry tone, even though, they may have just been joking.*

@@Windows_98 You Must Be Upgraded to Windows 10


<b>RUNNING THIS ON MS-DOS 7.10 MAKES WINDOWS 1.0 UNREADABLE</b>

*RUNNING THIS ON MS-DOS 7.10 MAKES WINDOWS 1.0 UNREADABLE*

I think that WIN100.BIN makes that video work properly


That is strange:
BSODs, and after it, it runs (i wish it  will be in Modern Windows (although it is impossible))
EDIT: 1:00 - that sync xD

Windows 1.01 startup screen is blue. This is not a BSOD but a glitched startup screen

@@xyzzy-dv6te <br>it is a blue screen of death. a very, very primitive version of it, but a bsod nonetheless.

@@xyzzy-dv6te
it is a blue screen of death. a very, very primitive version of it, but a bsod nonetheless.

@@TELEK1NET1C bsod doesnt exist in primitive OS, but blue color still was used by Windows for startup

@@gasmaskedcitizen <br>ohhh, ok, makes sense. thanks for explaining what it was in more detail

@@gasmaskedcitizen
ohhh, ok, makes sense. thanks for explaining what it was in more detail

It's a broken startup screen. Also BugCheck aka blue screen wasn't formatted on windows 1 so it dumped the whole memory on the screen or smth

@@TELEK1NET1C no, it's not it's the startup screen mixed with the BugCheck message

The glitched startup screen aka Windows 1.0 BSOD is actually a bug in the logo code which is often thought as crash screen


Software: exists

Enderman: LETS DO SOME RANDOM EXPERIMENTS

MᎾᏢSᏃ ᏦᎥᏒÁᏞᎽ yes

MᎾᏢSᏃ ᏦᎥᏒÁᏞᎽ yes

That's the.. whole point of his channel...<br>What do you mean?

That's the.. whole point of his channel...
What do you mean?

That's also the point of virtual machines.


The CPU has been disabled by the guest operating system.

what?

This thing can be done by a ransomware or a malware but somehow when your computer is in a bad situation,this can occur.

CPU meets Enderman
0.0000000001 ms later:
The CPU has been disabled by the guest operating system.

Interruptions have some force. There weren't such security measures that we have now, so software could have do anything with hardware (remember "Chernobyl" virus that made computer unbootable forever)


i love that the music drops when you see the glitched startup


3:34 pause the video eye delusion The texts are moving.


is it just me or did i think the title said "Windows 1.0 on Minecraft 1.7.10?"

Someone with the right skills should actually try this, but on a newer Minecraft version.

@@justsomerandompersononthei2595 time to do it on 1.16

Someone made a mod where you can use VM on there


Unsupported MS-DOS: we cant run Windows 1.0

Him: i dont care

Unsupported MS-DOS: *we cant run Windows 1.0*

Him: i dont care

Windows 1.0 on MS-DOS 7.10: Cue the 144p display!


Come on, can't you freakin' use SETVER WIN100.BIN 3.34? I did it and my Windows 1.01 works perfectly on MS-DOS 7.1...

Not if you are gonna scream the command at him.<br>あなたが彼に命令を叫ぶつもりでないならば。

Not if you are gonna scream the command at him.
あなたが彼に命令を叫ぶつもりでないならば。


0:11 West Germany?
WWII left some scars on old Windows versions,woah.

@@lychy645 Btw it's not even a fault<br>If it was a fault,then it would be Hitler's fault lmao

@@lychy645 Btw it's not even a fault
If it was a fault,then it would be Hitler's fault lmao

@@unknownboi3824 isn't it because communists built a wall in Berlin?


A Microsoft OS that can't run a Microsoft OS....

@@ChloekabanOfficial Yeah you didn't get it.


2:57 - I launch Metro Exodus in Core 2 duo)


It doesn’t work because newer version of dos use the high memory to load but windows 1 and 2 use all of the high memory to boot. Windows doesn’t want to over right the dos stuff so it crashes because some systems weren’t loaded or loaded a bit. You could try to make dos boot into the low memory but that probably impossible with dos 7 due to it being pretty big. Although you could try to do it with dos 5 and 6


Lol I just recently tried to make a Windows 1.0 VM over MS-DOS 6.22 and had the same glitchy behavior happen, didn't know it was because I was trying to run it over an unsupported MS-DOS version, thank you for the info!!


For me:
Windows 1 in:
6.22 - same error beeps, but still works fine.
7.0 - error beeps and vm crash
7.1 - same as above

i did windows 2000 8mb freezes on startup


1:25 WAIT THATS TOO LESS PIXELS FOR ME TO READ I THINK OR ITS JUST WRONG THING


Me:Installs new software
Enderman:intresting...


1:01 the beeeeep is actually constant, it does not pulse, but the music make it seem as if it was pulsing


0:59 welcome to Opposite side of the computer world


The bsod on windows 1 sounded like a flute 😭


Hay Enderman, I had the same issue you need to play around with the video card types and mouse pointer devices. VM Ware is not really supported windows 1.0, but after many tries, I got it to work correctly. If you want me to give you, the working version let me know.


ArtemkaFILL impossible unfortunately since windows 10 is NT


There were all sorts of crazy Windows NT versions in the 1990s. Have you done experiments on those? I'm talking about the RISC and PowerPC versions. It would be interesting if something can be done with MacOS and Windows NT running on PowerPC. 😂


Windows: Works fine<br>Enderman: im gonna end this whole os career

Windows: Works fine
Enderman: im gonna end this whole os career


Hey, Enderman, how do you stretch out the resolution of your VM in VMware?

A: VMware Tools
B: Manually stretching the screen
C: Natural (text mode and Windows 1.0 are always seen in 16:9)


Human Enderman: boi<br>Enderman: LETZ GO BABIES >:3

Human Enderman: boi
Enderman: LETZ GO BABIES >:3


Windows 1.0 : where are my glasses ?
MS-DOS 7.1 : here
Windows 1.0 : Where ?
MS-DOS 7.1 : F*** IM HERE !!!
Windows 1.0: huh
*crashes*

Windows 1.0 : where are my glasses ?
MS-DOS 7.1 : here
Windows 1.0 : Where ?
MS-DOS 7.1 : F*** IM HERE !!!
Windows 1.0: huh
**crashes**


2:56 Me: Huh...
2:56 Enderman: HAHAHAHA A BLUE SCREEN ON STARTUP


BSOD: plays my heart will go on

Windows 1.0: stops working

2:55

BSOD: *plays my heart will go on*

Windows 1.0: *stops working*

2:55


Error: No Hardware In DOS available
Enderman: Logges off

Error: *No Hardware In DOS available*
Enderman: *_Logges off_*


windows is speaking minecraft enchanting table!


Everyone gangsta till windows 1.0 start speaking doctor


1:01 (1:00 also) the best moment for a bass drop. WINDOWS 1.0 BSOD!!!


Does it enter graphics mode? The blinking cursor on the buttons indicates text mode, not graphics.


Title: How to crash Microsoft Windows 1.0


2019 : Windows 1.0 on MS DOS  7.10<br>2053 : Windows 10 on MS DOS 105

2019 : Windows 1.0 on MS DOS  7.10
2053 : Windows 10 on MS DOS 105

2067: Windows 67 on ms-dos 568
2115: Windows 1.0 future edition on MS-DOS 710
3015: Windows 1010 on MS-DOS 7100


Enderman: exists
My mind: remember not to look at the eyes

Enderman: *exists*
My mind: remember not to look at the eyes


A.K.A Windows 1 Enchantment Table Edition


I was about to switch this video for another video cos they both are what i like and youtube reads my mind and the video thats up next is the video i wanted to watch.


how many ms dos did you have for windows 1 it works for ms dos 3, ms dos 4, ms dos 5, ms dos 7


What build of Windows 1.01 that generates PIF?


Хмм, кириллица. Ты из снг? There was a Cyrillic keyboard in the video, so I suppose that you are from CIS. Is it right?


So basically the first version of Windows could only crash? Don't know about you - I'm not surprised. AT ALL.


No, it's made because the video drivers of newer MS-DOS (I think)


You'll never unsee it at the top, it's an among us 2:01


imagine doing this to a new computer in 1984?


Anyone watching Google I/O 2019 tonight? lol


Now I really wanna get Win1 to work on newer MS-DOS


This blue screened almost as many times my mom downloaded free anti virus on her laptop


I tried this because I did not know win 1.0 is not ms dos 7 compatible and I got confused thinking it was the faulty installation


that sound IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII and white symbols on blue screen is 1.0 BSOD, very rare to see is emoji on that Bluescreen


I'm fucking late but I have my bells on!


Windows 1.0 "wait, there's a problem" edition


Windows 8:i have 10000 terabyte memory

Ms-dos windows 1:not enough memory

What???


1 thing i don't understand : what does "win" command do ? I don't get it :|

Starts Windows, maybe there's an executable or the installation modifies COMMAND.COM as it does with AUTOEXEC.BAT

@@BurritoGaming bruh u just linked a tape website


When the scream of pain perfectly matches the song


i've misread it as "windows 10 on ms-dos 7.10"


At 1:00 The BSOD sound syncs with the music


well windows 1.0 does no support ms dos 7.10 bot 6.22 or older and ms dos supports 95 and 98


1:00 it's so broken you can't even read the error message :D

*1:00** it's so broken you can't even read the error message :D*


Bro its Windows Premiere Edition Windows 1.01 wont do this much


I thought that said windows 10 MS-DOS lol


Next time: playing Minecraft on Windows 1.0


Seems like the audio mixing in the video is more Right-ear oriented.


Ah, so that's why windows 1.0 has white lines while starting up when i attempt to install it on MS-DOS 6.22


I've unironically tried 1.01 with ms-dos 5.0 in virtual pc<br>that os was not feeling reallyyyy thaaat goooddd

I've unironically tried 1.01 with ms-dos 5.0 in virtual pc
that os was not feeling reallyyyy thaaat goooddd


This would make you shit your pants if you were a kid just learning PC back then


Oh gosh I wonder what would happen if you tried 2 run Windows 10 0.0


Only works on virtual box<br>VMware doesn't support win 1

Only works on virtual box
VMware doesn't support win 1


Windows 1.0 will run with MS-DOS 5.0 just load  SETVER.exe up upon startup.


Hmmm!

Windows 1 is unstable on newer DOS
But Windows 98 is stable on newer DOS


Yeah when windows 1.01 came out MS-DOS 6.22 was already out so that was the supported version and I'm pretty sure that when dos 7 or 8 rolled around windows 2 and 3 were probably already out so they kept 1.01 on 6.22

No where near Windows 1 is designed to run on MS-DOS 2 by the time 6.22 came out Windows 95 was out. MS-DOS 7.1 is from Windows 98 and what we see here is not officially from Microsoft,  it is from the China DOS Union.


1:07 THIS IS... WINDOWS 1.0 BSOD! BUT IT'S DON'T EXIST!

1:07 THIS IS... *WINDOWS 1.0 BSOD! BUT IT'S DON'T EXIST!*

I have that on dosbox  x
1. Bsod
2. Windows launchs


literally me trying to run windows 1.01 in cmd


Anyone know what all the corrupted text says?

The bsod message was coded incorrectly,so the text was corrupted. I think it says that u must install a supported dos


3:25 Internal stack overflow.System halted.

also saying something about the COMMAND.COM/.EXE


fun fact: the frozen blue booting screen with random text occurs due to incorrect msdos version

See Blue Screen of Death in BetaWiki and BetaWiki says that Windows 1.0 BSOD is a bug in the logo code but the crash screen didn't officially appear until Windows 3.0 but it was changed from black to blue in Windows 3.1


Ops the MC dos is ded uparge to windows1


Thank you!!! you help me in Msdos comands!! for Windows 1.0 is old. im not have Windows 1.0 im not used this computer!!


Can you make a vid of Running win10 on MS-DOS 7.0?


sync with random screen of symbols (1:00)


Also, if you try setver, hopefully, it would run fine, I guess


1:02 BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP


Wow Windows 1.01 has only Bsod sound lol


3:03 WTH IS THAT
WHY THE WIN1.0
IS STOPPING THE
CPU!?!?


Windows 1.0 "i cant see anything whats going on can anyone say me" Edition.


Windows 1.0 on VMware.Not startinBecause MS-DOS version is inorrect


Yes, It was an unsupported. Windows 1.0 must be required in MS-DOS 3.0.

- Yomaru Kasuga.


Type win into c:\windows> to win the game of crashing your computer


its keep crashing because window 1.0 died in 2001


Installing Windows 1x on MS-DOS 6.22 causes a BSOD without all the lines


Windows 10 on MS-DOS 6.99, this is impossible?


Windows 1.0 video thing more like Windows 1.0 corruptions


Killer installed in memory

um, excuse me?

*Killer installed in memory*

um, excuse me?


Somehow Win1 worked on 6.22 for me but I just don't remember


Enderman you are wrong about Ms-dos 6.22 it works on that for me lol.


It will work for sure with MS-DOS 6.0/7.0


do you want make Windows 1.0 on MS-DOS 6.22


1:10 WHEN YOU PLAY GTA 5 AND SETTING CONFIG VERY LOW


Try it on MS-DOS 8 with the WIN100.bin trick.


I did on PCjs.org windows 1.01 on ms-dos 7. Then 2.0, but it worked


The CPU has been disabled. Please restart.
Edit: 3:00


I saw more BSODs in this video than in my entire life

I used Windows 10 on a old Windows XP Acer PC. One BSOD a day. I literally saw more codes than NASA.


please fix this stupid pen drive shortcut virus... (msdaato.com)

one day,im downloaded program from my cousin (virus in his computer) end i see this;only a shotcut


Go test Doom shareware v1.0(v0.99) on this MS-DOS version!
Here a link to download: https://www.doomworld.com/idgames/historic/doom1_0


I don't know if he can, but it maybe not be easy

<i>CORRECTION:</i> Yes you can if you use WIN100.BIN

_CORRECTION:_ Yes you can if you use WIN100.BIN


This is why you should never put windows versions under 5.6 to MS-DOS 7.10


я тебе же писал,что это BSOD на Windows 1.01


0:43 Я так и знал что ты русский!

0:43 Я так и знал что ты русский!


i just fucking did that and windows ran fine, i restarted and it says ''no system'' LMFAOOOOOOOOOO

it did the same in msdos 7.1 and 6.22 it just somehow makes the machine unbootable


Why is it saying doki doki literature club


Weird... It worked on MS-DOS 6.22 and on MS-DOS 7.10 for me. | Странно... У меня оно работало на MS-DOS 6.22 и на MS-DOS 7.10.


I tried installing windows 1.0 in ms-dos 7.10 and it worked ok.


i see one people that doing this as tutorial. i sayd him ti watch this video to see what could happen


Странно но эта дата была на видно с установкой Windows 95


Windows 1.0 doesn't support MS-DOS 7.0, and this is the reaction of Windows (or MS-DOS).

Windows 1.0 doesn't work properly on new MS-DOS, I think that it happens due to the video driver or MS-DOS system incompatibility


Error opening EXPLORER.EXE
You must reinstall windows.
What should i do??.

HUH?


Turn of that horrible noise, it's making my ears bleed. You may call it music but I don't.


Bro u run DR5 not 1.01😂(It wont be that worse)


Thanks For The Help Why Windows 1.0 Doesn't Work For Me


You have 10% CPU
Click to continue
 |
V

You have 100% CPU
Bruh


(Working)
Computer:Error
Me:LOL MY SYSTEM CRASHED! I HAVEN'T GOT AN A ANTI-VIRUS
(A H J)
(Proto appears)
Proto:a anti-virus is not ENOUGHT , Progenet yetz :  download progenet
(Downoading progenet)
Progenet software: 1:01
Me:i need Undownload progenet


that happened to me too. in VMWare. on MS-DOS 6.22. I used the same files. but it stayed on BSOD until I restarted the virtual machine

edit: this also happens on VirtualBox. but without the white lines


Run Windows 10 on MS-DOS 7.10!!!
Run Windows 10 with 255 MB RAM!!!
Run Windows 10 on Pentium i10!

Windows 10 on ms-dos is impossible because it is Windows NT (Windows NT is Windows that runs without DOS)

1- Windows 10 is based on NT, not on DOS
2- Windows 10 at 32 bits it needs 1GB of RAM at least.
3- VirtualBox can't emulate or simulate specific CPU.


I'm confused on what people saw in Windows back then, if it barley worked and was unstable, how did it catch on? A little bit of trivia, Windows was intended to come out in '84, but was delayed because the widely-used 286 wasn't powerful enough for it.


When you open up windows 1.0 and your screen go: brrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr


nobody:
Windows 1.0: jKdjiJjdjdjdnJéjdjdnfjjadhdhdhhdhdjdhdjdjdjdjdhdjdjsohīpóhdjdhxjrndjfjffnfkfjfjf


windows 1.0 on DOS 6.22: beeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee]oFI QP34T89EPGES98GHUISERHUIESTIHSEUIWE0 OHRP9AEWH9F8ERFHER88ERHGERG (insert BSOD here)


https://youtu.be/AenTTt1CqD8
you CAN run it without glitches
btw i'm running it in virtualbox


<b>T H E  C P U  H A S  B E E N  D I S A B L E D</b>

*T H E  C P U  H A S  B E E N  D I S A B L E D*


https://youtu.be/LlP49iUKDAI that's on freedos


How to get Windows 1 VERY FUCKING UNSTABLE EDITION:
Install MSDOS 7.1
Install Windows 1
Launch Windows 1
enjoj ur nuew weendowz one veree faking unstabl edishion


1:01 the face when u see winxp run on 128mb
;-;