Blue Screen Python

[Alister]

On Fri, 21 Sep 2012 18:47:57 -0400, Dave Angel wrote:

> On 09/21/2012 12:01 PM, Alister wrote:
>> On Fri, 21 Sep 2012 15:14:53 +0000, Grant Edwards wrote:
>>
>>> On 2012-09-21, mikcec82 <michele.cecere at gmail.com> wrote:
>>>> Hallo to all,
>>>>
>>>> I'm using Python 2.7.3 with Windows 7 @ 64 bit and an Intel Core i3
>>>> -2350M CPU @2.30GHz 2.3GHz.
>>>>
>>>> Sometimes, when I'm programming in Python on my screen compare this
>>> Python is a user-space application.  User-space applications can't
>>> cause blue-screens unless they manage to trigger a bug in hardware, OS
>>> kernel,
>>> or device driver.
> 
> True.  Too bad there are so many of those bugs.
> 
>> But Windows does not have any true concept of user-space (although it
>> does make an almost convincing pretence) it has been hacked up from an
>> operating system that's original security model was "Lock the door when
>> you leave the office"
>>
>>
> That's not true at all.  You're thinking of Windows 3, Windows 95, 98,
> and ME, which were hacked on top of MSDOS.  But Windows NT3.5, 4, 2000,
> XP, Vista and Windows 7 have an entirely different bloodline.
> 
> NT 3.51 was actually very robust, but in 4.0 to gain better performance,
> they apparently did some compromising in the video driver's isolation.
> And who knows what's happened since then.

Although NT upwards has tried to introduce user-space requirements the 
need to maintain backwards compatibility has compromised these efforts.
it is not helped by the end user's (just look at what happened to Vista's 
attempt to make users authorise any changes to the system)



-- 
VMS, n.:
	The world's foremost multi-user adventure game.