4 ms·
It actually wasn’t NT. It followed the NT/Win32 APIs but a very cut down special purpose OS.
by maximilianburke 8y ago
It actually wasn’t NT. It followed the NT/Win32 APIs but a very cut down special purpose OS.
- gok 8y agoInteresting, so they implemented a new scheduler, VM etc?
- iforgotpassword 8y agoThe 360 had a hypervisor. Its kernel was based on the original Xbox's kernel, which in turn was based on the windows 2000 one. Trimmed down would be an understatement here; the ogxbox kernel fit into 256kb, including the bootup animation.
- cududa 8y agoOne day while working on the Xbox 360 Fall 2010 and Spring 2011 updates to redesign the UI for Kinect, we ran into an error “out of memory”. Everyone ran around like chickens with their heads cut off trying to figure out the problem. Turns out, we were just straight up out of memory! Thus began a “fun” 48 hours of converting all PNG assets into vectors, and png crushing what we could. Not to say that was the sole solution - OS UI assets were eating up a ton of resources, but there was a bunch of longer term work around OS memory optimization. I tell that sorry, just because it’s an amusing illustration to me of the twists and turns a project takes from inception to maturity
- gok 8y agoEh so I'm not a Windows expert but wasn't W2K in turn NT-derived?
- yjftsjthsd-h 8y agoWindows 2000 is literally NT 5.0 (see https://en.m.wikipedia.org/wiki/List_of_Microsoft_Windows_versions https://en.m.wikipedia.org/wiki/List_of_Microsoft_Windows_ve... for a mapping of the widely used names to internal NT versions). Edit to clarify: all versions of Windows, server and consumer, are NT, they just stopped using that branding.
- maximilianburke 8y agoThe PPC970 derived processor in the Xbox 360 was also big endian only; the PowerPC port required CPUs that could be switched to (and run in) little endian mode.