From: Steve F. <ste...@be...> - 2004-09-15 13:31:27
|
Okay, I figured this out and I'll post it here so if others see this happen. The problem is due to the combination of Windows XP SP2 with DEP enabled on an Athlon64 processor. After trying combination after combination and seeing a ton of blue screens, I was able to get coLinux to operate by changing the /NoExecute to be AlwaysOff in my boot.ini. I consider this a little bit of a bug with coLinux, and it's bitten the DivX encoder too on this processor. =20 DEP =3D Data Execution Prevention, which basically enables the flagging = of memory as being non-executable, thereby preventing injected code from being run if pushed in via a buffer overrun. Lots of details are here at Microsoft's site: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr. mspx Something in coLinux isn't playing nice with this, and I end up with a STOP error everytime I start up the app. I tried flagging just the colinux-daemon.exe to be bypassed with this stuff, but it still BSOD'd, probably because of something in the linux.sys because it was not flagged to run without DEP. I had to disable it for the entire OS. This isn't really desirable from a security perspective long term, but short term it really doesn't make my machine less secure than when I was running service pack 1, because SP1 didn't enable this capability in the first place. FWIW, on my work machine, a Pentium4 desktop, this doesn't crash. DEP is enforced by the OS, not relying on the underlying hardware to do it, since DEP isn't available on this processor, and according to the above link: By default, software-enforced DEP only protects limited system binaries, regardless of the hardware-enforced DEP capabilities of the processor. I'm curious if the OS considers linux.sys to be part of the OS or not?=20 I believe the new E64MT Pentium 4 procs have this enabled, so this problem may or may not appear on that platform. With more people moving towards the Athlon64 processors (they are getting cheaper now), this problem might affect more coLinux people in the near future. Thanks, hope this helps others! Steve=20 > -----Original Message----- > From: col...@li...=20 > [mailto:col...@li...] On Behalf=20 > Of Steve Frank > Sent: Saturday, September 11, 2004 3:27 PM > To: col...@li... > Subject: [coLinux-users] Newbie question: linux.sys causing a BSOD >=20 > Hi, I'm getting a STOP error (Blue scree o' death) whenever I=20 > try to start up colinux, with the failure on the linux.sys=20 > driver. I'm on XP > SP2 (and it works on another SP2 machine fine). Immediately=20 > on startup a 0x8e error occurs, so this is a no go. The=20 > system is an Athlon64 with a Via KT800Pro chipset, if that=20 > matters. Any ideas? >=20 > =20 >=20 > Steve >=20 > =20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one=20 > of 170 Project Admins to receive an Apple iPod Mini FREE for=20 > your judgement on who ports your project to Linux PPC the=20 > best. Sponsored by IBM.=20 > Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php=20 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users >=20 |