From: Dan A. <da...@gm...> - 2004-02-01 22:14:23
|
Hello, Currently, there are two issues that stand between us and a more stable and easier to develop version of coLinux. BSOD ---- The BSODs that many people are getting are caused by a bug that manifests itself only on some machines. Unfortunately, I can't reproduce it here. Because of that, you should send me results of crash dumps, using tools freely available from Microsoft. Thanks ePAc for enlightening us about kernel dumps. Me and Okajima think it is important for the road ahead. I'd like you to know something aboue me, which should encourge everybody on this developers list to participate in development and debugging. When I started coLinux on November, I had almost no knowledge in Windows Kernel programming. A few years ago, I had no knowledge in Linux kernel programming at all. Don't be afraid to try something that you don't know, especially in the kernel field. I ask for anyone who experiences a BSOD with coLinux, please extract useful information out from the tools Microsoft has provided us: Debug tools at: http://www.microsoft.com/whdc/ddk/debugging/installx86.mspx Debugging symbols at: http://www.microsoft.com/whdc/ddk/debugging/symbolpkg.mspx To enable dumps (as ePAc noted): Right click on "My Computer" Select "Properties" Select "Advanced" tab Under "Startup And Recovery" there is some option to setup different type of memory dump (minidump, kernel dump, full memory dump). Plus, I am planning to add automatic traces to coLinux's build so it would be even more easier to make something out of these dumps. DDK dependency -------------- Making it possible to compile valid .sys files on Linux is something that can be developed quite separately from coLinux devleopment. ReactOS would also benefit from it (binary compatibility with Windows), although they don't depend on it at the moment. I know there must be some very talented developers on this list, so I seek volunteers fir this mini-development. coLinux's source has a CREDITS file, needless to remind ;) -- Dan Aloni da...@gm... |