From: Piet D. <pi...@ww...> - 2003-03-26 09:52:48
|
On Tue, 2003-03-25 at 06:03, Bruce Winter wrote: > > I tried moving my files over to misterhouse-2.79 and > > it fixed the checksum problem. I think I've seen this > > happen before! I suspect that the perl environment is > > saving some state wrong and leaving corruption in the > > environment. (Similar to the Linux 'evolution' mail tool > > generating corrupt binaries and making it necessary to > > delete the binaries and have 'evolution' build it's > > binary files from scratch. > > > > Any thoughts on how the perl data base could be causing this > > kind of problem? I'm running on RedHat 2.8 Linux on a PC. > > > Bad cm11 data send transmition > > > ..............................No data received from cm11 > > > Bad checksum in cm11 send: cs1=50 cs2=. Will retry > > Hmmm, I can't think of anything that would change between mh releases that > might effect this. I think the problem is state that is being saved. How do I discard all of the state that mh saves. I suspect that it will fix the problem. > When you do a mh install, most people simply create a > new directory so they can switch back and forth between different mh > releases. Yes, I still have the dysfunctional older releases. It's possible I made a mistake but with the symptoms being so similar in my memory; I'd give 2:1 odds it's a but like evolution has with the binary files that have saved state in them that are corrupt. > If you have done this, you can still try the old release. If > not, you could re-install the old one to check. I think the old release still fails. If I delete the saved state I think it will work normally. How do I do that? I'll try both once ya tell me how to purge the saved perl state. For example where is the 'dark' variable for the Sensor_Items stored? > > I bet you ment RedHat 8.2, not 2.8. 2.8 That would be a pretty old release > :) Sure. > > If you run into the problem again, check to make sure there is not another > program running on that port and also that mh starts up without errors, > especially the errata when it opens that COM port. How about I experiment again with the old release once I know where state is saved? I'm pretty sure only mh is useing the tty port. The old version was failing, I killed it, installed the latest, and it worked. Before resorting to the newer version I tried a couple of times, even switching back and forth between mh and HeyU. That's when I figured out that I was having a software problem. -piet > > Bruce > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: > The Definitive IT and Networking Event. Be There! > NetWorld+Interop Las Vegas 2003 -- Register today! > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 -- pi...@ww... |