On Sunday 21 December 2008, Richard Acosta wrote: >El 21/12/2008 11:22 p.m., Jim Coleman escribió: >> Richard, I think there might be a misunderstanding. > >That's something where we can agree. > >> Every time that emc crashes, it creates a dmesg file that tells what was >> going on and what happened when it crashed. the guys that are way better >> than I am can look at this info and figure out what to do to fix the >> crashes. >> Every time something is different and it crashes with different errors, >> the dmesg will be different telling what's going on. >> so every time progress is made, we(more like the other guys, wish i could >> personally help) will need a new dmesg and copies of the current >> configurations being used > >OK, here is the fact... the used files are exactly the same every >time... i never changed the hal, ini, etc.. files and the message is the >same every time, and this is why i'm so tired of saying the same thing >over and over again. >NO PROGRESS HAVE BEEN MADE, i have upgraded from 2.2.5 to 2.2.6, then >2.2.7, and now 2.2.8, and the same thing happens at the exact same time, >and the error message is exactly the same since 2.2.6 using the exact >same files that Ted Hyde provided me. >"Uncown Command line XX" and the line referres to the same command on >the same line in the same file, so... if you check the old posts is the >same now carbon copy.
Maybe so, but I, and as I'm a sub to this list, I must assume no one here has seen the file they keep asking you to show us. So I went back through your messages, and it was posted on pastebin.ca, my mistake. They were posted on Oct 8th, at: Hal file http://pastebin.com/f4adbee10 Error http://pastebin.com/f1bee2b21 And neither contains enough debugging data to allow this guesser to make an educated guess, and TBT, I'm not a hal expert. But there are hal experts here, who have asked for further data, which has not been forthcoming, you chose to go into rant mode instead. When you ask for help, be prepared to do as the folks here ask you to do and not just repeat a rant over and over again. The suggestion that you look at that file with mc, in the hex mode, is an excellent one. mc, aka midnight commander, may be an old legacy piece of code, but it is still capable of doing things that all the modern eye candy file managers have't even thought of. The tools to fix it ARE available, but it takes willing hands to run them and to report the results, and that we are not seeing. What we are seeing is described purely by accident, its randomly regenerated every 5 minutes, in my .sig -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Endless Loop, n.: see Loop, Endless. Loop, Endless, n.: see Endless Loop. -- Random Shack Data Processing Dictionary ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
