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.
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:
@@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
@@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.
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.
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
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
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.
@@_-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.
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.
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. 😂
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.
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.
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
(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
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.
windows 1.0 on DOS 6.22: beeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee]oFI QP34T89EPGES98GHUISERHUIESTIHSEUIWE0 OHRP9AEWH9F8ERFHER88ERHGERG (insert BSOD here)
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
Unsupported Software: exists
518 likesEnderman: ( ͡° ͜ʖ ͡°)
Replies (15)
@@StoneNicolas93 dude ur a roblox youtuber tf u doing here?
0 likesHow did you do that face thing
0 likes;+)
0 likes¯\_ಠ_ಠ_/¯
0 likes@@windows203 :+)
0 likes( º _ ºノ)
0 likes( ͡° _ʖ ͡°)
1 like@Michal Lebeda I do not trust you at all.
1 like@@Anthonythetechguy2004 You are me?
1 like#kaomoji
1 like( ͡° ͜ʖ ͡°)
1 likeit's free real estate
2 likesಠ_ಠ
2 likes@@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.
2 likes"9"
3 likesPast Enderman: Windows 9x and above
278 likesPresent Enderman: Windows 1.0
Future Enderman: MS-DOS 1.0
Replies (16)
Installing Windows 35 on my brain
0 likes@@kiwiEverything Far Future Enderman: Memex
1 likePresent Enderman: Windows 11
1 likeWe are evolving, just backwards.
1 likeNo no future Future enderman Windows -10
1 likeDistant Future Enderman: ENIAC
1 likeFar Future Enderman: UNIX Sixth Edition
1 like125 like
1 likeМистер Помидорный Джо r/woooosh
1 likeTech Enderman: blocks
2 likesfar far far far future Enderman:
1 likePicking blocks from an uncapable player
(jk) Abacus
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 likesFar Future enderman: Installing Mark 1 on ENIAC
11 likes@@sebmotions What Sonic CD has to do with Windows and MS-DOS?
6 likesThe far future enderman:
1 likeSonic CD
3 likes3:04 Explanation: This will appear if interrupts are disabled and the guest os execute "hlt"(instruction).
68 likes"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.
Replies (7)
@@TrolleyMC hmm that might be it
0 likesthere 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:
1 like.crash
sti (stop interrupts)
hlt (halt)
jmp .crash
@@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
6 likeswhy would interrupts be disabled its not like windows 1.0 runs on 32 bit long mode
0 likes@@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.
6 likeswhat's an interrupt
0 likesFor those who dont know:
4 likesHalt basically pauses interrupts
Microsoft Windows 1.0 "help i cant read anything whats going on" Edition
92 likesReplies (14)
Offf he didnt heart you
0 likes@@TheProGam3r Why bother?
0 likes@@ITAC85 well yes but actually no
0 likes@@thedogfan5126 maybe not
0 likes@@ITAC85 mmmph mmph mmmph mmph (well yes but actually yes)
0 likes@@nickplj12 Well you need to shut up, but you actually need to shut up for the rest of your life.
0 likes@@ITAC85 W E L L Y E S B U T A C T U A L L Y N O .
0 likes@@nickplj12 Again, that is not how you use that meme. This is not the situation in which you'd use it.
0 likes@@ITAC85 well yes but actually no
0 likes@@nickplj12 That's not how you use that meme
0 likes@@ITAC85 well yes but actually no
0 likes@@malwaretestingfan Deaf, you mean?
0 likes20 like
0 likesMicrosoft Windows 1.0 for Blind People: the ear-rape noise will help you in using the machine.
5 likesIn conclusion:
123 likesWindows 1 on MS-DOS 7.1 = Major Graphical Glitches
Replies (11)
@@OGuiBlindao Oh.
0 likes@@avi8aviate guru meditation is vbox he uses vmware which instead gives "The CPU has been disabled by the VM."
0 likesWindows MGG 1.0
0 likesEh, 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.
0 likesTrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr>>> .... oooooof
0 likesplus beeps, fuckiness, and crashes.
2 likesAnd instability.
0 likes@@avi8aviate he uses VMWare.
0 likes@@_lun4r_ Yeah, that too. I'm surprised there was never a Guru Meditation error.
0 likes@@avi8aviate Plus an error that "the CPU has been disabled by the VM"
4 likesPlus a BSoD.
6 likes1:00 Perfectly synced, as all things should be.
42 likesReplies (1)
@RabbitFeathers it syncs with the drop
0 likesI'm sure it said Incorrect DOS version but it's unreadable.
66 likesReplies (4)
@@sikorsp22 this appears when MS-DOS version is incorrect
0 likesyou 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"
4 likeshttps://photos.app.goo.gl/YqxeDbYvciPFdWT78
yes it says it!
0 likesi know it
36 like
0 likesfinally, a premiere that is not 360p
77 likesReplies (7)
@@enurzia6918 me in 480p
0 likes69 like
0 likesLol
0 likesAnd im watching this in 144p
0 likesWaaaaaaáaaaaaaaaaaaaat
0 likesAnd in 60fps :)
2 likesYeh.
0 likesThis made a spider come out from under my desk, no lie
31 likesWelp, aleast this is somewhat more stable than Vista RTM.
66 likesI was expecting that to just get stuck in the BSOD.
Also, this doesnt needs a CPU to do a thing!
Replies (9)
The windows vista sp1 is actually really good.
0 likes@@_-noxxon-_ its a driver problem
0 likesemm. 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
0 likesYeah, 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.
0 likesWhy is everyone hating on Vista, it did nothing to you.
0 likesit 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.
0 likesYou're right. today's phones are more powerful than Windows 1.0 computers.
1 like@Mystery Box It is. It's a primitive form of it, but it is. That gibberish is from the system memory, is purposely displayed.
4 likes@Mystery Box it sorta is on old windows even though it spits out garbage data so
0 likeshey i finally got credited by someone
192 likesReplies (7)
That means you copied.
0 likesYo
0 likes@@lotychannel6126 nagyon ismerős
0 likesEper hmmmmmmm ismerős szó
0 likesyo
0 likesUmutcan - Earth The Planet
2 likesoof indeed
oof
3 likesOh so thats why windows 1.01 broke on dos 6.22.. i thought it was winworld that screwed the img files
16 likesReplies (1)
Same
0 likes1:00 Really Legit Microsoft Blue Screen Edit:why is this getting likes?
56 likesReplies (11)
That a Blue screen of death
0 likes@@Windows_98 You Must Be Upgraded to Windows 10
0 likes@@natalializarazo7824 Did I tho?
0 likes@@Windows_98 YOU DIED ON JULY 11, 2006
0 likes@@_-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.
1 like@@_-noxxon-_ you are AN IDIOT HAHAHAHAHA
0 likesIs Windows Vista
0 likesOh, hey 7
0 likesIs BSOD by Incorrect DOS Version
1 like@@_-noxxon-_ chill
0 likesTHATS NOT BSOD. UR FUCKIN IDIOT
0 likesRUNNING THIS ON MS-DOS 7.10 MAKES WINDOWS 1.0 UNREADABLE
24 likesReplies (2)
Ok
0 likesI think that WIN100.BIN makes that video work properly
1 likeThat is strange:
18 likesBSODs, and after it, it runs (i wish it will be in Modern Windows (although it is impossible))
EDIT: 1:00 - that sync xD
Replies (7)
The glitched startup screen aka Windows 1.0 BSOD is actually a bug in the logo code which is often thought as crash screen
0 likes@@TELEK1NET1C no, it's not it's the startup screen mixed with the BugCheck message
0 likesIt'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
0 likes@@gasmaskedcitizen
0 likesohhh, ok, makes sense. thanks for explaining what it was in more detail
@@TELEK1NET1C bsod doesnt exist in primitive OS, but blue color still was used by Windows for startup
0 likes@@xyzzy-dv6te
1 likeit is a blue screen of death. a very, very primitive version of it, but a bsod nonetheless.
Windows 1.01 startup screen is blue. This is not a BSOD but a glitched startup screen
0 likesSoftware: exists
11 likesEnderman: LETS DO SOME RANDOM EXPERIMENTS
Replies (4)
That's also the point of virtual machines.
0 likesThat's the.. whole point of his channel...
0 likesWhat do you mean?
YEA
0 likesMᎾᏢSᏃ ᏦᎥᏒÁᏞᎽ yes
0 likesWindows 1.0 on FreeDOS!
41 likesReplies (1)
Or MS-DOS 8.0 (Windows ME DOS).
1 likeThe CPU has been disabled by the guest operating system.
9 likeswhat?
Replies (3)
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)
0 likesCPU meets Enderman
0 likes0.0000000001 ms later:
The CPU has been disabled by the guest operating system.
This thing can be done by a ransomware or a malware but somehow when your computer is in a bad situation,this can occur.
2 likesThanks for discovering Ms Dos 7.10 :)
9 likes(3:27) looks like a city view
4 likesi love that the music drops when you see the glitched startup
2 likes2:55 Titanic XDDD
6 likesReplies (1)
LMAO I JUST REALIZED THAT
1 like3:34 pause the video eye delusion The texts are moving.
10 likesis it just me or did i think the title said "Windows 1.0 on Minecraft 1.7.10?"
7 likesReplies (3)
Someone made a mod where you can use VM on there
0 likes@@justsomerandompersononthei2595 time to do it on 1.16
0 likesSomeone with the right skills should actually try this, but on a newer Minecraft version.
0 likesUnsupported MS-DOS: we cant run Windows 1.0
3 likesHim: i dont care
Replies (1)
Windows 1.0 on MS-DOS 7.10: Cue the 144p display!
0 likes1:00 Perfect timing with the music
1 like1:57 this is a Windows 1's BSOD, man.
3 likesCome 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...
10 likesReplies (2)
Now try MS-DOS 8.
0 likesNot if you are gonna scream the command at him.
0 likesあなたが彼に命令を叫ぶつもりでないならば。
0:11 West Germany?
1 likeWWII left some scars on old Windows versions,woah.
Replies (3)
@@unknownboi3824 isn't it because communists built a wall in Berlin?
0 likes@@lychy645 Btw it's not even a fault
1 likeIf it was a fault,then it would be Hitler's fault lmao
Communism's fault
0 likesA Microsoft OS that can't run a Microsoft OS....
5 likesReplies (3)
r/woooosh
2 likes@@ChloekabanOfficial Yeah you didn't get it.
0 likesBecause...
1 likeNew is trying to run old.
2:57 - I launch Metro Exodus in Core 2 duo)
3 likesReplies (1)
That work in my computer
0 likesIt 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
4 likesLol 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!!
0 likesFor me:
3 likesWindows 1 in:
6.22 - same error beeps, but still works fine.
7.0 - error beeps and vm crash
7.1 - same as above
Replies (1)
i did windows 2000 8mb freezes on startup
0 likes1:25 WAIT THATS TOO LESS PIXELS FOR ME TO READ I THINK OR ITS JUST WRONG THING
2 likesoh heck no.
11 likes55 Minutes late :(
Replies (2)
No one cares.
1 like93 Minutes :(((((((((((((((((((((
0 likesMe:Installs new software
0 likesEnderman:intresting...
1:01 the beeeeep is actually constant, it does not pulse, but the music make it seem as if it was pulsing
0 likes0:59 welcome to Opposite side of the computer world
0 likesThe bsod on windows 1 sounded like a flute 😭
1 likeHay 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.
3 likeswhy you put music on error sound?
2 likesWindows 10 in dos
4 likesReplies (4)
BurritoGaming i know ...
0 likesWindows 10 is based on NT, not on DOS
0 likesNope.
0 likesArtemkaFILL impossible unfortunately since windows 10 is NT
2 likesThere 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. 😂
0 likesWindows: Works fine
0 likesEnderman: im gonna end this whole os career
2:57: Nice tune, Windows.
0 likesHey, Enderman, how do you stretch out the resolution of your VM in VMware?
1 likeReplies (1)
A: VMware Tools
2 likesB: Manually stretching the screen
C: Natural (text mode and Windows 1.0 are always seen in 16:9)
Human Enderman: boi
0 likesEnderman: LETZ GO BABIES >:3
Windows 1.0 : where are my glasses ?
0 likesMS-DOS 7.1 : here
Windows 1.0 : Where ?
MS-DOS 7.1 : F*** IM HERE !!!
Windows 1.0: huh
*crashes*
2:56 Me: Huh...
0 likes2:56 Enderman: HAHAHAHA A BLUE SCREEN ON STARTUP
BSOD: plays my heart will go on
0 likesWindows 1.0: stops working
2:55
Error: No Hardware In DOS available
1 likeEnderman: Logges off
windows is speaking minecraft enchanting table!
1 like3:01 oof
2 likesEveryone gangsta till windows 1.0 start speaking doctor
0 likes1:01 (1:00 also) the best moment for a bass drop. WINDOWS 1.0 BSOD!!!
0 likesDoes it enter graphics mode? The blinking cursor on the buttons indicates text mode, not graphics.
0 likesTitle: How to crash Microsoft Windows 1.0
3 likes1:01 sounds like it’s part of the music
0 likesWhich editing software do you use ????
0 likes2019 : Windows 1.0 on MS DOS 7.10
0 likes2053 : Windows 10 on MS DOS 105
Replies (1)
2067: Windows 67 on ms-dos 568
1 like2115: Windows 1.0 future edition on MS-DOS 710
3015: Windows 1010 on MS-DOS 7100
Enderman: exists
0 likesMy mind: remember not to look at the eyes
1:00 Music synch
1 likelocal Endermom glitches windows 1.0
0 likesA.K.A Windows 1 Enchantment Table Edition
1 likeI 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.
0 likeshow many ms dos did you have for windows 1 it works for ms dos 3, ms dos 4, ms dos 5, ms dos 7
0 likes1:00 my nerve system when I stub my toe
0 likesWhat build of Windows 1.01 that generates PIF?
0 likesХмм, кириллица. Ты из снг? There was a Cyrillic keyboard in the video, so I suppose that you are from CIS. Is it right?
0 likes0:54 :D happy drop
0 likesSo basically the first version of Windows could only crash? Don't know about you - I'm not surprised. AT ALL.
1 likeWhen u try to play pong on moms pc
2 likesIt is caused by aspect ratio i think
1 likeReplies (1)
No, it's made because the video drivers of newer MS-DOS (I think)
1 likeYou'll never unsee it at the top, it's an among us 2:01
0 likesimagine doing this to a new computer in 1984?
0 likesAnyone watching Google I/O 2019 tonight? lol
3 likesNow I really wanna get Win1 to work on newer MS-DOS
0 likesThis blue screened almost as many times my mom downloaded free anti virus on her laptop
1 likeI 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
0 likesthat sound IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII and white symbols on blue screen is 1.0 BSOD, very rare to see is emoji on that Bluescreen
0 likes2:56 did the beep start a song?
0 likesI'm fucking late but I have my bells on!
0 likesWindows 1.0 "wait, there's a problem" edition
0 likesWindows 8:i have 10000 terabyte memory
0 likesMs-dos windows 1:not enough memory
What???
1 thing i don't understand : what does "win" command do ? I don't get it :|
1 likeReplies (4)
Autoexec.bat
1 like@@BurritoGaming oh Thanks
0 likes@@BurritoGaming bruh u just linked a tape website
0 likesStarts Windows, maybe there's an executable or the installation modifies COMMAND.COM as it does with AUTOEXEC.BAT
0 likes1:01 MY PC IS BROKEN OH MY GOD
1 likei did 6.22 and it worked fine
1 likeMS-DOS.EXE has stopped working
1 likeWhen the scream of pain perfectly matches the song
0 likesKatie's in a wardrobe!!
0 likesi've misread it as "windows 10 on ms-dos 7.10"
0 likesAt 1:00 The BSOD sound syncs with the music
0 likeswell windows 1.0 does no support ms dos 7.10 bot 6.22 or older and ms dos supports 95 and 98
0 likes1:00 it's so broken you can't even read the error message :D
0 likesOMG
0 likesPERFECT TIMING
Bro its Windows Premiere Edition Windows 1.01 wont do this much
0 likesI thought that said windows 10 MS-DOS lol
1 likeNext time: playing Minecraft on Windows 1.0
0 likesSeems like the audio mixing in the video is more Right-ear oriented.
0 likesAh, so that's why windows 1.0 has white lines while starting up when i attempt to install it on MS-DOS 6.22
0 likeshow do you install dos 7.1
0 likesI've unironically tried 1.01 with ms-dos 5.0 in virtual pc
0 likesthat os was not feeling reallyyyy thaaat goooddd
This would make you shit your pants if you were a kid just learning PC back then
0 likesOh gosh I wonder what would happen if you tried 2 run Windows 10 0.0
1 likeOnly works on virtual box
0 likesVMware doesn't support win 1
1:07 blue screen of death!!!!!!!!!!!!!!!!!!!!
0 likesThat premiere too
1 likePatrick: this stinks
0 likesok im here. i think i'll try it.
0 likesMS DOS 7 is just regular MS DOS, right?
0 likesCan you do windows 1.0 on windows 98?
1 likeWindows 1.0 will run with MS-DOS 5.0 just load SETVER.exe up upon startup.
0 likesNow Windows 7 with MS-DOS 1.0!
0 likesso ms dos 7 is real?
1 likeUsing setver will make compatible
0 likesEnderman is at 69.4k subs.. nice
0 likesHow do you understand that
0 likesi have my big collection of windowses
0 likesHmmm!
0 likesWindows 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
0 likesReplies (1)
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.
0 likes1:07 THIS IS... WINDOWS 1.0 BSOD! BUT IT'S DON'T EXIST!
1 likeReplies (1)
I have that on dosbox x
0 likes1. Bsod
2. Windows launchs
Killer installed in memory?
0 likesliterally me trying to run windows 1.01 in cmd
0 likesAnyone know what all the corrupted text says?
0 likesReplies (1)
The bsod message was coded incorrectly,so the text was corrupted. I think it says that u must install a supported dos
1 likeI got a dream of this when I’m sleeping
0 likes3:25 Internal stack overflow.System halted.
0 likesReplies (1)
also saying something about the COMMAND.COM/.EXE
0 likesfun fact: the frozen blue booting screen with random text occurs due to incorrect msdos version
0 likesReplies (1)
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
0 likesOps the MC dos is ded uparge to windows1
1 likeThank you!!! you help me in Msdos comands!! for Windows 1.0 is old. im not have Windows 1.0 im not used this computer!!
0 likesCan you make a vid of Running win10 on MS-DOS 7.0?
0 likessync with random screen of symbols (1:00)
0 likesSync with bsos (Blue screen of symbols)
0 likesEpic
1 likeAlso, if you try setver, hopefully, it would run fine, I guess
0 likesMy mind when I try and think 1:02
0 likes1:02 BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP BEEP
0 likesI love ❤️ MS-DOS
1 likeWow Windows 1.01 has only Bsod sound lol
0 likesTiming is perfect 1:00
0 likes1:05 BSOD
0 likes3:03 WTH IS THAT
0 likesWHY THE WIN1.0
IS STOPPING THE
CPU!?!?
Replies (1)
because he didnt use 86box
0 likesMost Cursed Windows 1.0 i ever seen
0 likesWindows 1.0 "i cant see anything whats going on can anyone say me" Edition.
0 likesWindows 1.0 on VMware.Not startinBecause MS-DOS version is inorrect
0 likesYes, It was an unsupported. Windows 1.0 must be required in MS-DOS 3.0.
0 likes- Yomaru Kasuga.
Type win into c:\windows> to win the game of crashing your computer
0 likesProblem:cpu and graphics adapter
0 likesSounds Painful. 1:00
0 likeswhy not 86box
0 likesWhy W I N D O W S 😕
1 likeI Like Your Videos
1 likeits keep crashing because window 1.0 died in 2001
0 likesInstalling Windows 1x on MS-DOS 6.22 causes a BSOD without all the lines
0 likesReplies (1)
The BSOD is a logo code bug
0 likesbecause you selected monochrome
0 likesWindows 10 on MS-DOS 6.99, this is impossible?
0 likesow if was start in virtualbox 5.0
0 likesWindows 1.0 video thing more like Windows 1.0 corruptions
0 likesNext video: Ms dos On windows 1.0
0 likesKiller installed in memory
0 likesum, excuse me?
Somehow Win1 worked on 6.22 for me but I just don't remember
0 likesEnderman you are wrong about Ms-dos 6.22 it works on that for me lol.
0 likesLOL!!!
1 likeTry win 2.0?
1 likeReplies (1)
It will work for sure with MS-DOS 6.0/7.0
0 likesWhat about ms dos 8
0 likesEnjoy so far
0 likesdo you want make Windows 1.0 on MS-DOS 6.22
0 likestime to install windows
0 likes1:10 WHEN YOU PLAY GTA 5 AND SETTING CONFIG VERY LOW
0 likesUm yeah... MS-DOS 6.22 will do fine
0 likesTry it on MS-DOS 8 with the WIN100.bin trick.
0 likesI did on PCjs.org windows 1.01 on ms-dos 7. Then 2.0, but it worked
0 likesGraphics in a potato pc
2 likes😲🌚
0 likesThe CPU has been disabled. Please restart.
0 likesEdit: 3:00
Win 1.0 what the heck is DOS 7.10?
0 likes1:09 Windows 1 BSoD
0 likesПрикол
1 likexD 2:56
0 likesWow
0 likesI loaded it successfully in 6.22
0 likesI think you got an incorrect dos
0 likesI saw more BSODs in this video than in my entire life
0 likesReplies (2)
@@malwaretestingfan 🤣🤣🤣🤣🤣
1 likeI used Windows 10 on a old Windows XP Acer PC. One BSOD a day. I literally saw more codes than NASA.
2 likesEnderman kayak minecraft
0 likesplease fix this stupid pen drive shortcut virus... (msdaato.com)
2 likesReplies (2)
one day,im downloaded program from my cousin (virus in his computer) end i see this;only a shotcut
0 likeswhat
0 likesGo test Doom shareware v1.0(v0.99) on this MS-DOS version!
0 likesHere a link to download: https://www.doomworld.com/idgames/historic/doom1_0
scary
0 likesCan You try to fix ??
1 likeReplies (2)
CORRECTION: Yes you can if you use WIN100.BIN
0 likesI don't know if he can, but it maybe not be easy
0 likesThis is why you should never put windows versions under 5.6 to MS-DOS 7.10
0 likesI thought it said windows 10
1 likeReplies (1)
well you thought wrong
0 likesI tryed this and got better results
0 likesIs bios
1 likewindows bsod
1 likeYou are using windows 1.0 prototype
0 likesWindows 98 on MS-DOS 1.0?
0 likes1?
1 likeReplies (1)
Two
0 likesA N E X C I T I N G N E W L O O K
0 likesя тебе же писал,что это BSOD на Windows 1.01
0 likeshi
2 likes0:43 Я так и знал что ты русский!
1 likei just fucking did that and windows ran fine, i restarted and it says ''no system'' LMFAOOOOOOOOOO
0 likesReplies (1)
it did the same in msdos 7.1 and 6.22 it just somehow makes the machine unbootable
0 likesthumbnail: mior soft
0 likesWindows 1.01 is on MS-DOS 7.10?
0 likesWhy is it saying doki doki literature club
0 likesI Subscribe Your Channel
1 likeFor me it runs perfectly
0 likesWeird... It worked on MS-DOS 6.22 and on MS-DOS 7.10 for me. | Странно... У меня оно работало на MS-DOS 6.22 и на MS-DOS 7.10.
0 likeswindows 10 on MS-DOA 1.0
0 likesI tried installing windows 1.0 in ms-dos 7.10 and it worked ok.
0 likesi see one people that doing this as tutorial. i sayd him ti watch this video to see what could happen
0 likesTry windows 2.0 on ms dos 12.0
0 likesi cant read
0 likesExist emulator windows 1.0
0 likesСтранно но эта дата была на видно с установкой Windows 95
0 likesWindows Vista v2
0 likes1.9k likes is gooooooooooood 50 p m no
0 likesms dos from temu😂
0 likesTry 3.1 now
0 likesWindows 1.0 unstable edition
0 likeswhy are the white lines appearing?
0 likesReplies (2)
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
0 likesWindows 1.0 doesn't support MS-DOS 7.0, and this is the reaction of Windows (or MS-DOS).
1 likeIs an website
0 likesthis is video is not live
0 likesError opening EXPLORER.EXE
0 likesYou must reinstall windows.
What should i do??.
HUH?
0.5x0.5
0 likesHey everyone 👏💁♂️
2 likeshey ender guy can you teleport
0 likesTry
0 likessetver C:\DOS win100.bin 3.31
Turn of that horrible noise, it's making my ears bleed. You may call it music but I don't.
0 likesCommoands: A: , win
0 likesBro u run DR5 not 1.01😂(It wont be that worse)
0 likeshmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
0 likesexelent :) wow what music
0 likesttie take over the website
0 likesMS-DICK Winf*** 1.0 broken edition
0 likes3%
0 likessetver win100.bin 3.30
0 likesglitchy
0 likes0:27 insert diskette #123123123
0 likesThanks For The Help Why Windows 1.0 Doesn't Work For Me
0 likesYou have 10% CPU
0 likesClick to continue
|
V
You have 100% CPU
Bruh
Finally i come late :)
4 likesthis is the not good operating system
0 likesWin 10+linux
0 likesInstall ms dos on windows nt
0 likes(Working)
0 likesComputer: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
sync
0 likesWay
0 likesIt's work
0 likesBut Windows 3.1 is fine :)
0 likesIt crashed!!!!!! Ahaaaaaaaaaaaa.
0 likes8 bit
0 likes1 minute
1 likeenderman you fille is errer what
0 likesIt's worse then the review.
0 likesWtf
0 likesツ
0 likesbeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeep
0 likesthat 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
0 likesedit: this also happens on VirtualBox. but without the white lines
im on premiere!
1 likeits for blind poeple 2:03
0 likesRun Windows 10 on MS-DOS 7.10!!!
3 likesRun Windows 10 with 255 MB RAM!!!
Run Windows 10 on Pentium i10!
Replies (2)
1- Windows 10 is based on NT, not on DOS
0 likes2- Windows 10 at 32 bits it needs 1GB of RAM at least.
3- VirtualBox can't emulate or simulate specific CPU.
Windows 10 on ms-dos is impossible because it is Windows NT (Windows NT is Windows that runs without DOS)
0 likesWindows 1.0 is stupid
0 likesBosd
0 likesMorosoft
0 likesI'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.
0 likesEarly
1 like1 dislike
0 likeswhat 480
0 likeshttps://youtube.com/shorts/d6O5oPhZeCo?si=UZvdyUWSG4cdVdmF
0 likeshttps://youtu.be/In6Ze5xTVmc
0 likesWhen you open up windows 1.0 and your screen go: brrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
0 likesnobody:
0 likesWindows 1.0: jKdjiJjdjdjdnJéjdjdnfjjadhdhdhhdhdjdhdjdjdjdjdhdjdjsohīpóhdjdhxjrndjfjffnfkfjfjf
________
1 like| |
| o o |
| ____ |
-----------------
|
___|______
|
|
|
/ \
/ \
1:02 BSOD!
0 likesFLOPPY DISK 💾
0 likes( ͡° ͜ʖ ͡°)
0 likesLol bsod
0 likeswindows 1.0 on DOS 6.22: beeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee]oFI QP34T89EPGES98GHUISERHUIESTIHSEUIWE0 OHRP9AEWH9F8ERFHER88ERHGERG (insert BSOD here)
0 likes0:59 BSOD
0 likesBSODS
0 likes1:04 you ran into a BSOD
0 likesfuck you
0 likeshttps://youtu.be/AenTTt1CqD8
0 likesyou CAN run it without glitches
btw i'm running it in virtualbox
this is how it turned out for me on ms-dos 6.2 (not 6.22)
0 likeshttps://cdn.discordapp.com/attachments/478458278540476417/575247367956332544/2019-05-07_12-03-25.mp4
T H E C P U H A S B E E N D I S A B L E D
1 likenoob
0 likeshttps://youtu.be/LlP49iUKDAI that's on freedos
0 likesHow to get Windows 1 VERY FUCKING UNSTABLE EDITION:
0 likesInstall MSDOS 7.1
Install Windows 1
Launch Windows 1
enjoj ur nuew weendowz one veree faking unstabl edishion
1:01 a bsod
0 likes1:00 future BSOD
4 likesReplies (2)
1:01 the face when u see winxp run on 128mb
0 likes;-;
3 likes yes!
0 likes