From: ePAc <ep...@ko...> - 2004-01-31 22:54:31
|
> > > IRQL_NOT_LESS_OR_EQUAL > > > > > > Larry > > > > I got this as well, and i'm now waiting for the system to dump the whole > > memory. would any kind of processing on the memdump be useful to anyone ? > > These memory dumps sound useful. Do you know some reference about how to > enable them and other info that might be useful? 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). i had mine setup as "Full Memory Dump" (512M). as for analysis, there used to be some tools on the MS web site, i'll track those down. DebugView was able to "process" that memdump and give me 3 messages: 1 - 2:06:06 PM - Driver Unloaded (*) 2 - 2:07:38 PM - Driver Loaded 3 - 2:07:38 PM - Allocated cmon0 (*) might be from the first attempt for which Memdump wasn't enabled during the previous boot or something [/me clueless]... this was running under XP. Have you done any kind of testing with XP ? or was it all win2k ? my other machine (win2K) is loading properly, and the console is coming up, and i'm having the same set of problem with the e2fsck (i will write down those numbers next time). All in all, "This is fantastic !"(TM). You have now access to probably a couple dozen different config (mine included) which will allow us all to run linux on our poor windows machine :o) is there anyone on the list who has access to the newer DDK (2003/XP version), and that could compile the linux.sys with that OS. It would make sense that the linux.sys driver need to be compiled for the proper target OS. is there any success on XP ? Thanks, Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |