Linked by Thom Holwerda on Sat 9th Feb 2013 18:54 UTC
"The 16-bit Windows kernel was actually three kernels. One if you were using an 8086 processor, another if you were using an 80286 processor, and a third if you were using an 80386 processor. The 8086 kernel was a completely separate beast, but the 80286 and 80386 kernels shared a lot of code in common." As always, Raymond Chen delivers. If you don't yet follow his blog, you should. Right now. Click that bookmark or RSS button.
Thread beginning with comment 552046
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: The 286 kernel was mostly used for crashing
by moondevil on Sun 10th Feb 2013 15:17
in reply to "RE[4]: The 286 kernel was mostly used for crashing"
Member since:2005-07-08
Your comment:
So this is how windows multitasked on the 286, by continually rebooting the cpu
This was only required if you needed to start a MS-DOS program from inside Windows. Otherwise it was running in full 16 bit protected mode with all required features.
Was there an early generation of 286 mainboards which didn't support a cpu reset?
I am not sure, but that could have been the case with Xenix systems, which did not require MS-DOS compatibility.
RE[6]: The 286 kernel was mostly used for crashing
by Alfman on Sun 10th Feb 2013 20:54
in reply to "RE[5]: The 286 kernel was mostly used for crashing"
Member since:2011-01-28
moondevil,
"This was only required if you needed to start a MS-DOS program from inside Windows. Otherwise it was running in full 16 bit protected mode with all required features."
Yes of course, software could be built for the 16bit protected mode. If you want to say the 286 was capable of multi-tasking, then I'll have to admit that it's technically true, but it required all software to be rewritten for it. The 386 was intel's first processor suited for general purpose multi-tasking, that's my opinion anyways because the 286 needed external chipset logic to continuously reset itself into real mode to run the majority of software avaiable at the time.
Edited 2013-02-10 21:04 UTC
RE[5]: The 286 kernel was mostly used for crashing
by Megol on Sun 10th Feb 2013 23:50
in reply to "RE[4]: The 286 kernel was mostly used for crashing"
Member since:2011-04-11
moondevil,
"You got it wrong. Let me explain as I was already a long time computer user on those days."
I actually agree with everything (else) in your post, but was anything factually wrong in mine? It's definitely possible but your response didn't make it clear what is wrong.
I find it very strange how intel failed to anticipate the need for a mode switch, but mainboard manufacturers did by implementing the external 286 reset logic. Was there an early generation of 286 mainboards which didn't support a cpu reset?
"You got it wrong. Let me explain as I was already a long time computer user on those days."
I actually agree with everything (else) in your post, but was anything factually wrong in mine? It's definitely possible but your response didn't make it clear what is wrong.
I find it very strange how intel failed to anticipate the need for a mode switch, but mainboard manufacturers did by implementing the external 286 reset logic. Was there an early generation of 286 mainboards which didn't support a cpu reset?
No. There could perhaps be mainboards that doesn't support the reset protocol needed but that's unlikely.
Doing the reset itself can be done in software without extra hardware by triggering a triple fault, just load the interrupt description table pointer with something faulty and then do a software interrupt.
RE[6]: The 286 kernel was mostly used for crashing
by Alfman on Mon 11th Feb 2013 01:20
in reply to "RE[5]: The 286 kernel was mostly used for crashing"
Member since:2011-01-28
Megol,
"Doing the reset itself can be done in software without extra hardware by triggering a triple fault, just load the interrupt description table pointer with something faulty and then do a software interrupt."
Ah, very clever! And here I was thinking it was an oversight by the bastards at intel, how wrong I was. My faith is restored 
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Why does Google get so much credit in the technology industry? Why, despite the company's many obvious failings, do many geeks and enthusiasts still hold a somewhat positive view on the all-knowing technology giant? A specific talk at Google I/O this week provides the answer.
Linked by David Adams on 05/16/13 4:23 UTC
OSNews is a sponsor of this year's O'Reilly OSCON in Portland, Oregon, USA. A lucky OSNews reader will win a free three-day pass, including two tutorials days. To win the pass, post a comment on this story saying something about Open Source Software or OSCON. We'll pick a winner at random next week. If you don't have an OSNews account, you may email us your entry. Part of the conference is the 9th annual Open Source Awards, and today the 16th is the deadline for nominations. If you'd like to nominate an outstanding open source contributor, do it here. Read on for more information about OSCON. Update: The 20% discount code for OSNews readers is "OSN."
Linked by Thom Holwerda on 05/11/13 21:41 UTC
"Windows is indeed slower than other operating systems in many scenarios, and the gap is worsening." That's one way to start an insider explanation of why Windows' performance isn't up to snuff. Written by someone who actually contributes code to the Windows NT kernel, the comment on Hacker News, later deleted but reposted with permission on Marc Bevand's blog, paints a very dreary picture of the state of Windows development. The root issue? Think of how Linux is developed, and you'll know the answer.
Linked by Thom Holwerda on 05/08/13 14:22 UTC
This is one of those news items that's fun to write, fun to read, fun to comment on, and where no one will be able to say anything unkind. It's all just one big ball of awesome fluffiness. TuneTracker, the BeOS radio automation software, has just released something very special: TuneTracker System 5, the first version designed entirely and specifically for Haiku. In fact, it actually includes Haiku in the software package. Better yet, TuneTracker also unveiled several system-in-a-box products - which have Haiku and TuneTracker pre-installed.
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Exactly twenty years ago, a document was published that played a huge role in establishing the web as we know it today. Twenty years later, and this simple and straightforward document is proof of an irrefutable fact: while closed technologies can change markets, open technologies can change the world.
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Oh multitasking. That staple of computing that got thrown out the window with many modern smartphones. We got some rudimentary thing in its place - but even as multitasking on phone and tablets improves, its user-visible side remains cumbersome. Windows 8 has a neat implementation, and now it's time Android follows in it footsteps.
Linked by Thom Holwerda on 04/24/13 22:24 UTC
They're here! Whether that excites you or not remains to be seen, but the Galaxy S4, which will most likely become the best selling Android smartphone of the year by a huge margin, has been reviewed by all the major sites, and there's lots of interesting conclusions in there - although I think most of you will get the gist.
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Nokia has posted its quarterly results for the first quarter of 2013, and just like the quarters that came before, there's not a whole lot of good news in there. The rise in Lumia sales still can't even dream of making up for the sales drop in Symbian phones, and when broken down in versions, the sales figures for Windows Phone 8 Lumias in particular are very disappointing. In North America, Nokia is getting slaughtered.
Linked by Thom Holwerda on 04/16/13 9:29 UTC
The day has finally come: Google has started shipping Google Glass to the lucky few early adopters. Now that it's shipping, Google has also unveiled a lot more about the API and the specifications of the device itself. While the company had already given out substantial details at earlier occasions, there are still a few surprises here.
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Almost exactly three years ago, I wrote about why OSNews was no longer OSNews: the alternative operating system scene had died, and OSNews, too, had to go with the times and move towards reporting on a new wave of operating systems - mobile, and all the repercussions that the explosion of smartphones and tablets have caused. Still, I was wondering something today: why aren't we seeing alternative operating systems on mobile?More Features »
Sponsored Links
Member since:
2011-01-28
moondevil,
"You got it wrong. Let me explain as I was already a long time computer user on those days."
I actually agree with everything (else) in your post, but was anything factually wrong in mine? It's definitely possible but your response didn't make it clear what is wrong.
I find it very strange how intel failed to anticipate the need for a mode switch, but mainboard manufacturers did by implementing the external 286 reset logic. Was there an early generation of 286 mainboards which didn't support a cpu reset?