Re: [slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-10-19 Thread Olaf
dean blackketter [EMAIL PROTECTED] writes: Both of those errors imply some kind of corruption in the software or memory. First thing I'd do is run some diagnostics on your machine (memory test, disk test), just to be on the safe side. Just for the record, Dean: you were spot on; 1

Re: [slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-09-14 Thread Olaf
dean blackketter [EMAIL PROTECTED] writes: Both of those errors imply some kind of corruption in the software or memory. First thing I'd do is run some diagnostics on your machine (memory test, disk test), just to be on the safe side. Then I'd try reinstalling SlimServer and see if

[slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-09-13 Thread Olaf
My SB failed to wake me this morning because the SlimServer had died on my XP box, leaving the following msg in the event log The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to

Re: [slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-09-13 Thread dean blackketter
Hi Olaf, Does this happen every time that your alarm goes off? Looking at that portion of SlimServer, I can't see why this error would be triggered, so I'd need a way to reproduce this issue. -dean On Sep 12, 2005, at 11:19 PM, Olaf wrote: My SB failed to wake me this morning because

Re: [slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-09-13 Thread Olaf
dean blackketter [EMAIL PROTECTED] writes: Does this happen every time that your alarm goes off? I wish it was that simple, Dean. No, it does not happen every day. But I am having no ends of trouble with SS since I installed the last MS security updates. SS has since become notoriously

Re: [slim] SlimServer 6.1.1. dies in call to time2str upon ALARM

2005-09-13 Thread dean blackketter
Both of those errors imply some kind of corruption in the software or memory. First thing I'd do is run some diagnostics on your machine (memory test, disk test), just to be on the safe side. Then I'd try reinstalling SlimServer and see if it's better.