A much lighter version of NTFS was running on it. Perhaps being limited to what it was, it'd be easier to study the native api and how it was being accessed by the several subsystems (Win32, OS/2, POSIX). Nonetheless it was solid compared to Windows 3.1 and 95. I had been dual booting NetBSD and OS/2 2.1 before that.
I really began to appreciate the text file based UNIX philosphy over the point-and-click Microsoft approach. It installs ATDISK.SYS if you don't have a CD. It turns out that it installs ATAPI.SYS if you have a CD, which won't boot without it. When I gave the CD drive back, NT wouldn't boot.
#Original xbox wine emulator install
I lacked a CD drive and borrowed one to install NT 3.51. It had the Windows 3 user interface and a number of enterprisey things like telephony (TAPI) and UPS control, but was overall pretty bare-bones.
#Original xbox wine emulator code
I'm trying to think of a good use case for exploring the NT 3.5 source code but I can't really think of one. It's obvious that the GUI was not taken from Windows, that you won't be able to maybe install a printer and so over, and it is probable that tons of custom code was also written, but that does not make the relationship disappear completely. The high level API seems to be based on a subset of DirectX and even a few pieces of Win32, so that's not completely unrelated either. whole windows OS think that they would take explorer.exe and random obscure IT stuff and so over, and 150k is not crazy big, but for a core OS kernel this is completely expected. But nobody who knows the difference about kernel vs. They took the networking stack and a couple other bits from NT, but otherwise it was built from scratch.įrom the whole Win2k obviously not, and it is common for journalists to not be very precise, but at least the kernel seems to have tons of architectural similarities with the NT kernel, and I would not be surprised if it was a derivative? The Xbox OS isn't "a custom version of Windows 2000".
0 kommentar(er)
