Running Windows 1.0 Apps on Windows 10?
HTML-код
- Опубликовано: 29 сен 2024
- ● Liked this video? Subscribe for more: mjd.yt/subscribe
Is it possible to run applications from Windows 1.0 on Windows 10? Let's find out!
● Join our forum community: osforums.net
● Gear I use to make these videos: www.kit.com/mjd
● Affiliate Links
Amazon: www.amazon.com...
Save 10% on PDF Expert: pdfexpert.com/...
● Follow Me:
Twitter: / mjdtweets
Instagram: / mjdmichael
Facebook: / mjdmichael
● Music/Credits:
Background/Outro music: www.incompetech... & RUclips Audio Library
Amazon Affiliate Notice: I am a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. All Amazon links that I provide will use my affiliate code with Amazon.
Some materials in this video are used under Section 107 of the Copyright Act of 1976, which allows "fair use" for purposes such as criticism, commenting, news reporting, teaching, and research.
lol I've never seen an app say it was last modified in the 80s.
And date glitches? Like finding a photo made in 1958 on your device
@Weekblues i have that on my phone
@Weekblues Same here. I have a file on my phone's SD card that was last modified on January 1st, 1970. Crazy stuff!
Abu Hamza Muharemović isn’t that the unix epoch?
"apps" didn't exist in the 80's
Goes to show the amazing backward compatibility Windows has... which is part of the reason it still has the same problems as always. They’re stuck in the past.
Me: It's hot in here
Microsoft: Time to open up some windows (windows xp start up plays)
Me: Now it's to cold, shut the darn window (windows xp shutdown plays)
lol
I have noticed the old programs had the Windows 98-esc dropdown menu. This tells us that classic theme is in Windows 10!
It still exists. There are some patches to enable it.
Take out your favourite hex editor and patch the version field in the Windows 1 executables, and they might run.
Tecnicly, windows 2.03 had window controls. Maximise/restore and minimise
Windows 1.0 apps are 16 bit. There’s a feature which lets 16 bit apps run on 32 bit windows, but it isn’t included with 64 bit windows
22:09 - Windows: Please hold on while Windows reports this problem to Microsoft
Microsoft employee: Uhhhh... we just got an error report for the Windows 2.0.3 DOS Executable
edit: Wow, I take a vacation, and this becomes my most popular comment by far.
🤣🤣🤣
thats if they even look at thoes things
Quick Games They probably don’t.
bill gates: wtf?
Hahahaha
Windows 10: Please hold on while we report this problem to Microsoft...
MS Employee: Why is someone still using 2.0.3 DOS executable, and why is it failing?
Bigger question is why isn't it failing
*Skeleton in chair*
Do you think those even make it to windows?
If that was Windows Smartscreen then it would have said something like "Windows protected your PC" and given you the option to run it. "This app can't run" is a compatibility message.
its the same thing iirc
thats because Windows 10 doesnt reconize the Code that Windows 1.0 apps are build
Just think about it - They made clipboard function in windows so good, that they didn't do any significant changes in like 35 years (because the program still recognized everything which wouldn't be the case it they significantly edited the code)
that can be possibly be left untouched until the end of our universe.
it's a divine horror to work with, though.
if it works don't touch it
@@usernameak all of the win32 api is a divine horror to work with, if you really think about it.
@@usernameak reading this after having just committed a fix relating to clipboard access.
MSDOS.exe from Windows 1: *exists*
Windows 7: 'Sure!'
Almost anything made before 2015: *exists*
Windows 10: 'No, I don't think I will.'
backwards compatibility is incredibly inefficient. Do you want a better OS? or a OS that can run all other OS's?
@@ausintune9014 I want windows 7
@@ausintune9014 backwards compatibility is a necessary step backwards. Businesses run on legacy hardware and software, hell even most governments do. If your OS doesn't support some random old software a company relies upon, they won't adopt it. If a lot of old software a lot of businesses rely on don't work, you're losing a lot of customers. That means you're losing a lot of money, and it means youre not introducing the new, efficient and useful features that will eventually be adopted by everyone if they work well. In an ideal world, as soon as something like VR comes about everyone would be hopping onto it, but it takes time to get people to adopt such things. Technology moves much faster than people, and people move much faster than business
@@squabbbb they have to get on with the times and commission new software. Oh wait, most banking still uses fucking COBOL
@@ausintune9014 oh boy just you wait for that Apple Silicon. Wait for the ARM future bb, appstores all around!
15:34 Try to run Control Panel as administrator (Windows doesn't allow to change the time/date without admin rights) and disable the auto-sync in the Settings app
This, again. Changing the system time requires UAC (administrator) because if it didn't malicious users or software could change the system time and make expired certificates valid again. So, you should used "Run as Administrator..." for the Control Panel.
@@Δημήτρης-θ7θ this is a VM security isnt top priority
also the virtual machine might prevent time from being changed, taking it from the host system
@Ocean waves Correct, i kinda forgot my point from a year ago but stuff can detect and even break through VMs however i don't think thats related to this lol
it doesnt work as the control Panel shows that but doesnt allow you to change it
The programs from Windows NT 3.1 work fine in Win10, even on 64bit as they are 32bit native applications. Have Win3.1 paintbrush running in 4k resolution on Win10
It employee from a bank here.
It works, and it's horrible.
That's amazing, eh? I've been pillaging apps from XP (hate what they did to Write and Paint) but never thought to look at older NT.
Because windows 10 is NT 10.1903
THAT IS AWESOME
yeah windows 10 uses NT
This program requires Microsoft Windows.
Windows 10: Am I a joke to you?
Windows 98SE, XP SP1 and 7, all in unison: Yes.
95, ME, Vista, 8.1 also all in unison: *Y E S*
You are on the wrong kernel buddy!
@@ryan1696 exactly
@@ItzYtanimation G O O G L E
Actually, the first kind of window control was introduced in Windows 3.0, where doubleclicking the menu opener thing on the top left of a windows closes it sometimes.
Also, Reversi was removed in specifically Windows 3.1.
Minesweeper is also officially in the Microsoft Store.
With *A D S R E E E E E E*
Yeah. All classic Windows Games (Solitaire, Minesweeper, and that stuff) shouldn't have ads.
Doubleclicking that menu opener was introduced in Win 1.0 . The button still exists today on the very same location, only it appears as the program icon. And doubleclicking it still works, so that might be your oldest windows feature.
@@IrisGalaxis con.
@@mariannmariann2052 These days you can just use WSL to play the Ubuntu version on Windows.
I'm pretty sure the time and date in Windows 10 is set by the internet and you have to disable it to change the time and date manually?
Ye
Yup I tried it with windows 2.03 control panel and it worked
Probably also just run it as administrator as Windows 10 requires that for changing it in the regular settings screen.
the color changes do change throughout the system
15:22 before
20:16 after
It sets colors system-wide, yeah. It's just that current iteration of windows controls/widgets doesnt use that setting. But when you run some old program (win xp and older, I believe) or go to some forgotten places of windows 10 these widgets pop up and respect chosen colors.
I never knew, you could still run apps from Windows 2.0 on Windows 10 so far, you can adjust things in the control panel, and log out from MS DOS Executive. This leads me to beleive, there is still some ancient code that dates back to the 80s is still lurking inside Windows 10's kernel.
Windows NT is based on some OS/2 thing, so yes there is ancient code.
thowse apps run under NTVDM.EXE witch runs a lite and slimed-down version of Windows 3.1.
The Windows 1 MS-DOS executable said "1 byte" when you moused over it.
Well yeah, it's just an empty DOS exe.
But in the Explorer window on the right of the name there was written 1K
@@alessandroceloria 1KB is 1024 bytes.
@@elllieeeeeeeeeeeeeeeeeeeeeeeee I know, but in the Explorer window the reported size of the DOS executable is of 1K = 1024 bytes
EDIT: 3:43 check the size column
MSDOS.EXE from Windows 1.01 is 41904 bytes, so the copy used here was definitely corrupt. It probably wouldn't have worked anyway because the executable image format of 1.x applications isn't supported on NTVDM.
Try to run Windows 10 Apps on Windows 1.0 😂
Can't run a 64bit or 32bit applications on a 16bit os
@@lauriekimani you don't say
@@ElNoobYT1 agachate y conocelo
Nico Neumann lol
this is sadly not possible
Congratulations, you've just convinced me to go through the masochism of installing a Windows 1.0 VM in case, for some remarkably contrived reason, I run into some form of software somewhere that needs it.
I read about this ages ago but can't find it again. It's possible to run 1.0 apps on windows 10. Step one is to use a hex editor and modify the exe header to say it's for windows 2.0. Then you need an old version of the Borland resource editor (or resource compiler? I forgot the name) to recompile the embedded resources from the 1.0 format to a newer format (embedded resources can be icons, text messages, window layouts etc.)
Borland now that is a name I haven't heard in a long time.
I would have liked to see if you open windows 3's regedit if you can edit the windows 10 registry. Another thing, try opening a massive modern day photo with paintbrush
@Nori go to new paint open picture save as (insert name).bmp then open it
You need to rename some of the applications because Windows blocks them if they’re named the same as system files like calc.exe.
That makes sense. It could be a bit more clear with the error, though.
The structure of Windows kernel has definitely been changed a lot with transition to NT kernel for performance and stability.
However Windows has not changed Windows API in NT kernel based Windows for compatibility with DOS kernel based one,
so most Windows APIs (like CreateWindow) used in Windows 1.x are still remained with usable state in Windows 10.
Not surprising. I guess most software developed for Pre - Windows 95 can be run in Windows 10,
if legacy codes for 16 - Bit system (far / near pointer, Local / Glocal Memory Allocation) are replaced with modern ones.
NTVDM pretty much provides a full Windows 3.1 OS that runs in a virtual 8086 process, those old windows programs don't interact with actual Windows 10 APIs or NT APIs.
As much as I can't stand Microsoft these days, they generally do have the best backwards compatibility of all OSes.
I disagree. They will keep all that ancient Win 3.1 crap around but remove just enough crucial bits (such as 256-color modes for DirectX in Windows 2000, or SafeDisc/SecuRom support in Windows 10) to make actually useful apps and games not work anymore.
Yep and why did they end support for windows 7 and vista
Nope. It's ironic but you can run more Windows apps in WINE under Linux than in Windows 10.
@@TarikA Source? That's not possible, considering how many gaps in DirectX 11 support Wine has. Unless you are counting DVD games. But I 'd rather repurchase or download a NoDVD patch than deal with Wine's missing API support.
@@TarikA This is completely incorrect
You have to log out of Win10 and log back in for color changes to reliably take effect.
Also, now I'm wondering if this trick would make XP's color control panel work. Getting rid of white menus would be worth the effort.
Rez Zircon Dark theme for Windows explorer will be released next month, Insh’Allah. So give the official setting a shot before making custom tweaks
I've already banged around in the registry and got at least some workspace and app-fittings to a acceptable colors -- but generally the older the app, the more it accepts my colors. The holdouts that are still glary white or only halfassed changed are mostly either fairly new, or Windows official apps, like the file manager (which is broken and annoying in enough ways that I'm looking for a replacement anyway; so far the least annoying is an old version of Powerdesk).
The provided black and high-contrast themes aren't really usable either. I'd settle for black type on a nice restful grey.
Well, I can tell you that's not true for WordPad or Paint, because I just copied them from XP to Win10 and put them in my \Utilities directory, launched from a desktop shortcut, and they work fine. Didn't rename them or anything (didn't require compatibility settings either). Pretty obvious which is running since these old versions don't have the Ribbon.
*laughs in classic theme on Windows 10*
@@NazmusLabs Muslim?
I think the time is resetting because you have to setting to automatically sync your time on.
The icon for msdos.exe is the old program manager icon for Windows 3.1 - interesting that icon is still included as part of Windows 10.
Windows 10 is based on Windows NT 3.1.
@@EcoScratcher Yes, but Windows NT 3.1 is designed after Windows 3.1 (also I'm pretty sure it can run Windows 3.1 applications).
Would that not just be embedded in the executable?
Exactly the icon is inside the EXE and it pulls the resource from there. It is not included in Windows 10.
@@Planetdune This can't be the case, for two reasons. 1) It shows up for the MS-DOS Executive, which doesn't have that icon (or any at all, I think?), and 2) Since Vista, modern Windows cannot read icons from 16-bit applications to reduce security vulnerability risk.
25:35 This painting must belong in a museum :D
I wonder whether it's the Program Compatibility Assistant service that is preventing the apps from opening...?
Windows On Windows Could you take a look at compatibility layers throughout windows history on your channel? I think you'd be perfect for it, since you have done many videos on the various versions of Windows, dev versions and all.
Well, that would be a little bit ironic: he's doing the very thing he swore to destroy, that is stopping programs from running
To change the time in Coltrol Panel 2.03, you have to turn off the automatic time sync in Windows 10 settings.
I feel like you should have run the Program Manager as an Admin, not too sure why.
This video has some nostalgic moments in it lol. I haven’t seen that Windows 3.0 paint in 15+ years and i still recognize it. And i also remember the file explorer (executive thing) of win 2.0. If you clicked on the A drive button that you would hear the floppy drive buzzing lol. Always a crazy thing to realise that i lay daily on the couch with an iPad which is capable of doing thousands of more things than those old bulky computers with CRT screens could do back then.
Y'know, I actually know a little bit about why 16-bit apps can't run on 64-bit windows.
So, when your PC boots up, it wakes up as an 8088 with a lot more gigahertz. "I had a terrible nightmare!" screams the CPU. The BIOS asks, "What? What happened?", and the CPU spins. "There was so much RAM, so much cache, so much pipilining and out-of-order execution...". The BIOS scoffs. "Why that's not a nightmare, that's heaven! Can't you imagine how fast a booter game boots, and a shooter game shoots?". The CPU spits its words. "That's not what they were doing! They were running all these programs, dozens and dozens, hundreds of megabytes of code, millions and millions of instructions being computed every second!" The BIOS still doesn't see the problem. "Why again, you're saying these computers are all the more capable! Where's the problem?"
"I'll tell you the damned problem," said the CPU. "All that power, all those millions of operations, all those megabytes and megabytes and megabytes of memory, they were all just for loading a RUclips comments section!"
The BIOS stares outwards in a moment of geniune horror; but then it smirks. "What the fuck else do you think you're hear for? You're talking to the devil that helps make it all possible." The BIOS turns to UEFI, and it rips the CPU out of its real 16-bit execution and slams it into protected mode, engages 32-bit execution, fires up the MMU and shoots upwards into 64-bit code where it launches the large masses of MMX, SSE, and AVX registers that have grown into the CPU; it screams and it screams, it burns and it burns, and the fans start spinning to keep it right on the edge of functionality, right on the edge of death, but never able to make one step closer.
You see, 16-bit 'Virtual 8086' execution is a legacy part of standard 32-bit protected mode execution, hence why Windows 98 can run your 16-bit DOS programs just fine, but 64-bit mode is its own entire beast outright. Under 64-bit execution, a new 32-bit legacy mode had to be created, and they couldn't just re-use Virtual 8086 like they did before. It relied on all the 32-bit data structures that the processor was getting rid of, so rather than re-implementing it, they dumped the feature from being accessible at all from 64-bit modes.
But the 16-bit execution never dies. It's still there under the native 32-bit mode. It's still there when your computer starts.
The 8086 screams louder than ever before.
Why aren't you helping it? Why are you letting it live? It's becoming a goddamn living ghost! It's a goddamn living SPECTRE!
If i would get a dollar every time Micheal MJD says "Check that out!" I would be a billionaire!
16 bit software natively on 64 bit Windows? Not a good chance, there’s a higher chance if you try it on 32 bit Windows
Natively, on x64, is outright impossible by specification
this is so cool... tou forgot to run sol.exe ( solitaire ) 😎
This is the beauty of Windows - backwards compatibility. There are several RUclips videos showing upgrading from Windows 1.0 to Windows 10 and several old apps still worked in Windows 10. However, Windows does not carry the settings over from the previous version of Windows
Very interesting video, makes you think how much legacy code is actually in Win 10
There are countless Dll's and Exe's from ancient versions of windows even on 10... There is a LOT of legacy code, but mainly they are duplicates and remnants left there for backwards compatibility, considering that Windows 10 x64 (without NTDVM) officially supports app from 95, which was still a DOS based kernel
Alessandro Celoria Either way NT and 9x both have the Win32 API.
Since the IBM PC!
"Hello everybody and welcome back to another video." Classic Michael intro, and it's perfect!
For the border width check if the area where you can resize windows gets bigger. In Windows 10 the border is hidden to make everything look thin.
Menu bar themes might work on programs that do not support UxTheme.
Maybe the Win2 control panel couldn't change the time because Win10 didn't have the option to automatically synchronize the clock disabled. If you disable automatically synchronizing the clock, does it work then?
Why didn't you try to launch win. com files for each version? Yes, inside win10.
The windows 2 clock in control panel may have worked if you disabled the windows time server in Windows 10. You can either set your time manually, or you can tell the clock to grab time, date, and time zone from the server automatically. This is actually the default; You have to opt out of it and tell the system that you want to set it manually. I'm betting if you turned off the automatic functionality then the control panel would have allowed you to adjust the time. my assumptions come from the fact that the cursor blink actually changed the system functionality of Windows 10.
But can Paintbrush open a modern .BMP made in a newer program? :o That's what I really wanted to see in that part. Everything else was great though, I honestly didn't know what to expect!
Yes! It can, I just tested it. 24-bit color with an 819x409 resolution, in a 486DX; it took around 1 entire minute to open, but it worked!
The time and date settings probably didn't work because windows had automatic time setting on.
It's interesting to see the file sizes of these old programs...
Exactly. Imagine trying to make programs that small today that actually function correctly... Next to impossible.
I would believe the color changes would work for some programs,ones that are kinda older (probably xp age) / ones that have really old menu styles. I have a program for windows that allows me to have tabs in explorer, it uses old unthemed dropdown menus, unlike notepad which uses windows 10 ish ones
Man, this video is really cool but also kinda scary. Imagine all of the vulnerabilities that could be caused by NTVDM.
Windows 1.0 cmd: Shut down the PC, please.
Windows 7: OK, grandpa :(
When upgrading win 8 to win 10:some of u programs broken now hhaaha xd lolololoollloolol
when upgrading wind 2.0 to win 10 ahahahaaahhahahaha msdo works lololool
You forgot to try Windows NT 3.1 workstation executables with latest service pack. Winnt3.1 is theorically all 32bit. I believe some things do run on win10 because there are API leftovers. Some things require NTVDM. Win10 doesnt ship with NTVDM. When Win10 needs NTVDM, it prompts user and downloads it the net, same for .net 2/3. I believe also windows does try to detect which version of windows can run an executable, some will need compatibility mode adjusted.
the fact that some functions work is pretty rad, just goes to show you how much they were able to accomplish in those older versions of windows
the color settings from wwin 2.0 control panel applies to the classic windows skin introduced in 9x, so you will see the changes if you manage to bring it up in windows 10 , it is still here but hidden !
I know Windows 95 and such would do program groups as start menu folders, so try elevating the Program Manager?
Intel seeing red when they realized that all of their old instructions that they kept are basically useless without special attention to the OS
If I recall, you could exit Windows from Task Manager, even back in Win 3. I'm not 100% on that, but it might've been something to try if the ability existed.
I don't remember that, but what I do remember is that if you pressed CTRL+ALT+DEL once, you got that Task Manager window, but if you pressed the keys combo twice, your computer would restart.
Actually, 16-bit DOS and Windows apps will run on Windows 64-bit using the 'emulator' OTVDM. github dot com slash otya128 slash OTVDM
unfortunately, i think due to NTVDM, when you select end session, it ends the NTVDM session, so that functionality won't work on windows 10
Windows 7 also uses NTVDM and it supposedly worked there.
I think 3.1 (not NT) programs can end session in OTVDM.
12:29, I think that when the program checked your windows version it was like "Windows 10? Windows 10 does not exist yet!"
LETS DO THE TIME WARP AGAIN
IT'S JUST A JUMP TO THE LEFT
Mansake Labs AND A STEP TO RIGHT
*Hype Warp
Once I installed a program from a 90s National Geographic CD and it worked like it was made for Windows 10... Windows is the absolute king of backwards compatibility
I understand why the windows 3.0 ones would work, at least windows 3 nt programs would work cause the kernel is the same as windows 10. But the fact the windows 2 programs work, well some, is astonishing. I have no idea why that happens
For all the (sometimes deserved) shit Windows gets they really care about backwards compatibility. I run a mac as a daily driver and am constantly annoyed by the sometimes five years old (or less) programs that just no longer work on a modern mac.
I wonder if there's a way to convert a 16 bit exe into a 32 bit one by just padding all of the zeroes and offsets and then fixing errors that arise
You could do it by hand I suppose but it'd take you ages and ages. I think it'd be difficult to automate in a way that would usually get it 100% right without extra manual intervention.
I've been using a desktop clock called EMICLOCK since Win95, and it still works in Win10. Other apps from the era are more hit-or-miss. That's about as far back as I dare go (w/o resorting to DOSBOX)
13:13 yet another reason why I think Microsoft is the king of backwards compatibility
Apple: aaaaaaa don’t do 32bit apps pls :(
hello, just wondering...why do windows 1.0 to 3.0 files are all in capital letters? just curious
I literally just watched your old 5k special video earlier today!! You do some really interesting stuff! ❤ have you considered try to do the same style upgrade video for linux/Ubuntu ?
Wow good timing. I just stumbled across your 5k video and found it super interesting and here you are posting a related video, sweet
L\ol
TURN OFF AUTOMATIC DATE AND TIME!!!!!!
Just remember whos the real heroes here: NTVDM devs for allowing you to run these programs on NT in the first place 😌
The date and time not working could possibly be windows 10 automatically syncing the time via internet.
I was able to run most (not all) of win 1.0 on 64 bit with otvdm, as well as some 2.0 and 3.1 apps, I couldn’t get 1 executable to work mainly cause i didn’t wanna find the files needed for it but 2 worked flawlessly almost. Reversi, calc, clipbrd, and calendar worked everytime.
For someone who does lots of Windows stuff, you sure know nothing about windows.
That window made you think the smart screen thing was the problem, but it’s the fact this is windows 10, an OS that literally doesn’t have support for 16bit applications lol.
He was using Windows 10 THIRTY-TWO BIT, which can run SIXTEEN BIT APPS 🙄
I think u just wasn't enable to change the time and day, because first u need turn off internet synchronization
wouldnt the msdos exec not open because its attemping to run the msdos that you installed windows 1.0 or 3.0 on? thats why its not opening cause its not there
When you were trying to terminate the Windows session with MS-DOS Executive, in that same menu it said "Format Data Disk"
I wonder what that will do on Windows 10...
Control.exe in windows 3 does not work unless you put the files in c:\windows
**Later**
*_CAN YOU PLAY FORTNITE ON WINDOWS 1.0_*
or Doom
@@samuelthecamel it can launch DOS programs, so....
Does bro really do Ctrl+R ms-settings instead of just Win+i? xd
No you cannot run Windows 1x or 2x software on Windows XP, 7 or 8, I have tried it and it does not work. And you would not want to anyway. If you are going to run 16 bit software you are better off using Windows 3.1 which works great on Windows 7 and 8 as well as XP as long as you have 32 bit Windows. I have software from Windows 3.11 on my Windows 7 and 8 and it will work on Windows 10 32 bit.
I'm somewhat surprised by how many programs still work natively, I'm however not surprised that bmp files happen to open still. It's legacy format for sure but it's so simple it's still being used on some applications.
Pretty cool, I don't use Windows... but the backwards compatibility is really freaking cool.
In the Linux world "backwards compatibility" is usually trying to compile an application against newer libraries or compiling the app and libraries. If that doesn't work or it's a binary then your out of luck.
To be fair, you can run executable binaries from as far back as the i386 platform was supported; the issue with libraries is just that you'll need the older library versions as well, so granted there's a little bit of dependency hell involved for complex ones...
What can we do to address this serious problem? To arise awareness of developers?
The biggest obstacle is that Windows 1.0 and many Windows 2.0 programs were written to run on an original IBM PC with an 8086/8088 processor; i.e. what came to be known as "real mode" on 80286 and later processors.
Beginning with the Windows/286 and Windows/386 editions of Windows 2.0, support was added to the kernel for "standard mode" and "386 enhanced mode" in order to support the protected mode of the 80286 and 80386 processors respectively. This had the consequence that some older programs; having been written to expect the (somewhat peculiar) memory addressing scheme of the 8088, would attempt to access memory in a way that is invalid for an 80286 or later CPU running in protected mode; causing either the program (or, just as likely, Windows itself) to crash with a "general protection fault".
As some others have hinted, Windows 1.0 execuables used the exact same file format as early MS-DOS executables; and all were designed to run in "real mode" Windows, because nothing else existed at the time. Beginning with Windows 2.0, the executables were changed to the modern "NE" (new executable) format that is used by all modern DOS, OS/2, and Windows systems; which includes headers indicating such things as which operating system modes are supported by the program (i.e. DOS real mode, DOS extended mode, OS/2, Win16 real mode, Win16 standard mode, Win16 enhanced mode, Win32, Win64, UWP, etc). This explains why Windows 10 (probably also all versions of Windows NT) cannot recognise the Windows 1.0 executables as Windows programs and instead attempt to execute them as MS-DOS programs (usually just a stub which prints a message stating that the program requires Windows and then exits).
The time thing might be the autotime setting.
That's it I'm gonna be the first one to bluescreen windows 12
I think the End session thing did not work because unlike Windows 7, here it uses NTVDM, but the fact it can still change some system settings like cursor blinking is mind boggling and makes my theory a bit wonky
Every NT-based OS uses NTVDM to run 16-bit apps, so Windows 7 still uses it. Something changed between 7 and 10, maybe security-related, that disabled that functionality and the ability to run Windows 1.0 apps. Maybe the experiment should be tried on Windows 8 and 8.1 to see if the changes were made since then or later.
I think when you disable the automatic time set from win10, you could change it with the windows 2 program
Windows 10 has very good compatibility with old things, not only software but also old hardware. I am running candy crush saga on ati rage pro and framerate is also playable.
Windows 3 was the version that laid the definitive groundwork for the Windows backend, so no surprise that NTVDM barely works until that point. That's about how it is in Windows 3 itself, though users of _that_ had a workaround: if they absolutely had to run something for Windows 2 or earlier, they could start Windows 3.0 in real mode (a function removed in 3.1), though this would then prevent most Windows 3 programs from running. The command is "win /r".
Still interesting after 5 years)
i think some of them rely on ms dos, our current windows is based on NT not ms dos
My favorite Windows:
Win3
Win95
Win98 (more accurately, ie4, which became an extension of 98, but was compatible with win95)
Winxp
Win7
@@zacharyreynolds4303 oh yeah, good point! Win nt4 was a workhorse! And win nt2000 made winxp so great! Thanks!
Win8.1 when modified for me as well as all of the above.
you won't be able to save the time change without disable the windows time sync
16:00 perhaps the VM software is using the host system time and overwriting the guest time. 🤔
18:50 if my observations are correct, windows 10 has at least 3 different context menus - the normal one, the large, W10/UWP one, and a third one which (if I'm correct) is only used for the alt+space on a window menu.
I'd bet it's changing the colour of the alt+space menu. 🤔
Just an idea, try with NTVDM64 (a third party project on source forge) to run the same apps on Windows 10 64 bit
I actually saw that while filming this video. Might take a look at it in the future!
Nice, take your time!
if you ran these in otvdm they wouldve worked i bet