Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29696
| Date | 2012-09-21 18:47 -0400 |
|---|---|
| From | Dave Angel <d@davea.name> |
| Subject | Re: Blue Screen Python |
| References | <7c8701cc-1bc5-46ee-a83a-3e9a038ceada@googlegroups.com> <k3i09d$in$2@reader1.panix.com> <gb07s.566859$LO.119209@fx26.am4> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.1048.1348267711.27098.python-list@python.org> (permalink) |
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@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. -- DaveA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-09-21 07:04 -0700
Re: Blue Screen Python Chris Angelico <rosuav@gmail.com> - 2012-09-22 00:29 +1000
Re: Blue Screen Python Grant Edwards <invalid@invalid.invalid> - 2012-09-21 15:14 +0000
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-21 16:01 +0000
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-21 16:02 +0000
Re: Blue Screen Python Dave Angel <d@davea.name> - 2012-09-21 18:47 -0400
Re: Blue Screen Python Alister <alister.ware@ntlworld.com> - 2012-09-22 10:53 +0000
Re: Blue Screen Python Dave Angel <d@davea.name> - 2012-09-22 07:44 -0400
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-22 05:19 -0700
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-22 05:19 -0700
Re: Blue Screen Python Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-09-22 13:07 +0000
Re: Blue Screen Python Chris Angelico <rosuav@gmail.com> - 2012-09-23 00:10 +1000
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-23 04:17 -0700
Re: Blue Screen Python 88888 Dihedral <dihedral88888@googlemail.com> - 2012-09-23 04:17 -0700
Re: Blue Screen Python Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-09-22 13:53 +0100
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-09 00:37 -0700
Re: Blue Screen Python Philipp Hagemeister <phihag@phihag.de> - 2012-10-09 12:32 +0200
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-09 05:10 -0700
Re: Blue Screen Python mikcec82 <michele.cecere@gmail.com> - 2012-10-22 06:15 -0700
csiph-web