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.
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.
@@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.
@@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
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" photos.app.goo.gl/YqxeDbYvciPFdWT78
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!
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)
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!!
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.
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.
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
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.
(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
![สาวเมืองเพชร - ธีเดช ทองอภิชาติ [Official MV]](http://i.ytimg.com/vi/kEt7F9PvO3I/mqdefault.jpg)
Unsupported Software: *exists*
Enderman: ( ͡° ͜ʖ ͡°)
"9"
@@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.
ಠ_ಠ
*it's free real estate*
( ͡° ͜ʖ ͡°)
Past Enderman: Windows 9x and above
Present Enderman: Windows 1.0
Future Enderman: MS-DOS 1.0
Sonic CD
The far future enderman:
@@sebmotions What Sonic CD has to do with Windows and MS-DOS?
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.
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:
Halt basically pauses interrupts
what's an interrupt
@@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
In conclusion:
Windows 1 on MS-DOS 7.1 = Major Graphical Glitches
Plus a BSoD.
@@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.
@@avi8aviate he uses VMWare.
And instability.
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.
20 like
@@malwaretestingfan Deaf, you mean?
@@ITAC85 well yes but actually no
@@nickplj12 That's not how you use that meme
I'm sure it said Incorrect DOS version but it's unreadable.
36 like
yes it says it!
i know it
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"
photos.app.goo.gl/YqxeDbYvciPFdWT78
@@sikorsp22 this appears when MS-DOS version is incorrect
1:00 Perfectly synced, as all things should be.
@RabbitFeathers it syncs with the drop
This made a spider come out from under my desk, no lie
finally, a premiere that is not 360p
Yeh.
And in 60fps :)
Waaaaaaáaaaaaaaaaaaaat
And im watching this in 144p
Lol
1:00 Really Legit Microsoft Blue Screen Edit:why is this getting likes?
THATS NOT BSOD. UR FUCKIN IDIOT
@@_-noxxon-_ chill
Is BSOD by Incorrect DOS Version
Oh, hey 7
Is Windows Vista
hey i finally got credited by someone
oof
Umutcan - Earth The Planet
oof indeed
yo
Eper hmmmmmmm ismerős szó
@@lotychannel6126 nagyon ismerős
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
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
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
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.
Oh so thats why windows 1.01 broke on dos 6.22.. i thought it was winworld that screwed the img files
Same
(3:27) looks like a city view
*RUNNING THIS ON MS-DOS 7.10 MAKES WINDOWS 1.0 UNREADABLE*
I think that WIN100.BIN makes that video work properly
Ok
Thanks for discovering Ms Dos 7.10 :)
Software: exists
Enderman: LETS DO SOME RANDOM EXPERIMENTS
MᎾᏢSᏃ ᏦᎥᏒÁᏞᎽ yes
*_YEA_*
That's the.. whole point of his channel...
What do you mean?
That's also the point of virtual machines.
Windows 1.0 on FreeDOS!
Or MS-DOS 8.0 (Windows ME DOS).
Exactly this is why I had to use an older version of MS-DOS to run Windows 1.0
3:34 pause the video eye delusion The texts are moving.
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)
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
i love that the music drops when you see the glitched startup
1:00 Perfect timing with the music
1:00 Music synch
windows is speaking minecraft enchanting table!
2:55 Titanic XDDD
LMAO I JUST REALIZED THAT
1:25 WAIT THATS TOO LESS PIXELS FOR ME TO READ I THINK OR ITS JUST WRONG THING
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.
あなたが彼に命令を叫ぶつもりでないならば。
Now try MS-DOS 8.
1:57 this is a Windows 1's BSOD, man.
1:01 the beeeeep is actually constant, it does not pulse, but the music make it seem as if it was pulsing
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
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!!
1:01 sounds like it’s part of the music
2:57 - I launch Metro Exodus in Core 2 duo)
That work in my computer
0:11 West Germany?
WWII left some scars on old Windows versions,woah.
Communism's fault
@@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....
Because...
New is trying to run old.
@@ChloekabanOfficial Yeah you didn't get it.
r/woooosh
BSOD: *plays my heart will go on*
Windows 1.0: *stops working*
2:55
2:56 Me: Huh...
2:56 Enderman: HAHAHAHA A BLUE SCREEN ON STARTUP
oh heck no.
55 Minutes late :(
93 Minutes :(((((((((((((((((((((
No one cares.
3:01 oof
Me:Installs new software
Enderman:intresting...
2:56 did the beep start a song?
1:01 MY PC IS BROKEN OH MY GOD
Windows: Works fine
Enderman: im gonna end this whole os career
0:59 welcome to Opposite side of the computer world
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.
2:57: Nice tune, Windows.
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
Title: How to crash Microsoft Windows 1.0
Human Enderman: boi
Enderman: LETZ GO BABIES >:3
why you put music on error sound?
Enderman: *exists*
My mind: remember not to look at the eyes
At 1:00 The BSOD sound syncs with the music
1:01 (1:00 also) the best moment for a bass drop. WINDOWS 1.0 BSOD!!!
0:54 :D happy drop
3:25 Internal stack overflow.System halted.
also saying something about the COMMAND.COM/.EXE
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
The bsod on windows 1 sounded like a flute 😭
Which editing software do you use ????
You'll never unsee it at the top, it's an among us 2:01
Windows 1.0 "wait, there's a problem" edition
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
Does it enter graphics mode? The blinking cursor on the buttons indicates text mode, not graphics.
Anyone watching Google I/O 2019 tonight? lol
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)
What build of Windows 1.01 that generates PIF?
Timing is perfect 1:00
imagine doing this to a new computer in 1984?
Now I really wanna get Win1 to work on newer MS-DOS
MS-DOS.EXE has stopped working
The CPU has been disabled. Please restart.
Edit: 3:00
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
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
local Endermom glitches windows 1.0
When the scream of pain perfectly matches the song
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**
well windows 1.0 does no support ms dos 7.10 bot 6.22 or older and ms dos supports 95 and 98
Only works on virtual box
VMware doesn't support win 1
3:03 WTH IS THAT
WHY THE WIN1.0
IS STOPPING THE
CPU!?!?
because he didnt use 86box
It is caused by aspect ratio i think
No, it's made because the video drivers of newer MS-DOS (I think)
Windows 8:i have 10000 terabyte memory
Ms-dos windows 1:not enough memory
What???
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.
1:00 my nerve system when I stub my toe
A.K.A Windows 1 Enchantment Table Edition
Хмм, кириллица. Ты из снг? There was a Cyrillic keyboard in the video, so I suppose that you are from CIS. Is it right?
*1:00** it's so broken you can't even read the error message :D*
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
i've misread it as "windows 10 on ms-dos 7.10"
Next time: playing Minecraft on Windows 1.0
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.
That premiere too
Installing Windows 1x on MS-DOS 6.22 causes a BSOD without all the lines
The BSOD is a logo code bug
This blue screened almost as many times my mom downloaded free anti virus on her laptop
Sounds Painful. 1:00
(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
Can you do windows 1.0 on windows 98?
So basically the first version of Windows could only crash? Don't know about you - I'm not surprised. AT ALL.
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