HouseBot

Hi Scott.....guess what...when I got home today from work....Housebot wasn't running



It appeared to shut down at 10am exactly



Here's the Dumo file. Do you know what MSVCRT.DLL is used for ?



P.S I've just got myself a wireless card for my IPAQ and have been having great fun remotely controlling my lights !!! This software ROCKS !!





Cheers,



Dave



====== Begin Dump - Tuesday, September 30, 2003 10:00:00 ======

Server Version = 1.51a



==================================

======== House Server Thread =======

==================================

Thread Type = Device Thread [System Time]

Thread ID = 3B4

Exception code: C0000005 ACCESS_VIOLATION

Fault address: 78029033 01:00028033 C:\WINNT\system32\MSVCRT.DLL



Registers:

EAX:FFFFF1F0

EBX:071D9100

ECX:00000009

EDX:0000000B

ESI:00000000

EDI:07A8FDC0

CS:EIP:001B:78029033

SS:ESP07A8FD9C EBP:07A8FDA4

DS:0023 ES:0023 FS:0038 GS:0000

Flags:00010246



Call stack:

Address Frame

78029033 07A8FDA4 mktime+19E

78028EA0 07A8FDE4 mktime+B

004CA35A 00000001 0001:000C935A C:\Program Files\HouseBot\HouseBotServer.exe





====== End Dump ======

Dave,



Make sure you try the version I referenced in the last message (1.51b). It does fix something where your last dump file indicates a problem.

P.S I've just got myself a wireless card for my IPAQ and have been having great fun remotely controlling my lights !!! This software ROCKS !!

It sounds like it is rocking like a Led Zeppelin for you.



Scott

Hi Scott,



I just tried 1.51b and changed my system time to 9.59am and watched Housebot shutdown at exactly 10am now.



Here's the dump



Cheers,



Dave





====== Begin Dump - Wednesday, October 01, 2003 09:59:49 ======

Server Version = 1.51b



==================================

======== House Server Thread =======

==================================

Thread Type = Device Thread [System Time]

Thread ID = 4E4

Exception code: C0000005 ACCESS_VIOLATION

Fault address: 004C63DF 01:000C53DF C:\Program Files\HouseBot\HouseBotServer.exe



Registers:

EAX:00000000

EBX:072CDABC

ECX:072CDAC8

EDX:00A03D40

ESI:072CDAB0

EDI:072CDAC8

CS:EIP:001B:004C63DF

SS:ESP07A9FE28 EBP:072CDAB0

DS:0023 ES:0023 FS:0038 GS:0000

Flags:00010246



Call stack:

Address Frame

004C63DF 072CDAB0 0001:000C53DF C:\Program Files\HouseBot\HouseBotServer.exe

07267F68 0053169C 0000:00000000

004CA7E0 004C9FF0 0001:000C97E0 C:\Program Files\HouseBot\HouseBotServer.exe

FFFFFF58 E8F18B56 0000:00000000





====== End Dump ======

Hi Scott,



I just tried 1.51b and changed my system time to 9.59am and watched Housebot shutdown at exactly 10am now.



Here's the dump



Cheers,



Dave





====== Begin Dump - Wednesday, October 01, 2003 09:59:49 ======

Server Version = 1.51b



==================================

======== House Server Thread =======

==================================

Thread Type = Device Thread [System Time]

Thread ID = 4E4

Exception code: C0000005 ACCESS_VIOLATION

Fault address: 004C63DF 01:000C53DF C:\Program Files\HouseBot\HouseBotServer.exe



Registers:

EAX:00000000

EBX:072CDABC

ECX:072CDAC8

EDX:00A03D40

ESI:072CDAB0

EDI:072CDAC8

CS:EIP:001B:004C63DF

SS:ESP07A9FE28 EBP:072CDAB0

DS:0023 ES:0023 FS:0038 GS:0000

Flags:00010246



Call stack:

Address Frame

004C63DF 072CDAB0 0001:000C53DF C:\Program Files\HouseBot\HouseBotServer.exe

07267F68 0053169C 0000:00000000

004CA7E0 004C9FF0 0001:000C97E0 C:\Program Files\HouseBot\HouseBotServer.exe

FFFFFF58 E8F18B56 0000:00000000





====== End Dump ======

Dave,



It's that same darn spot!



Can you look to see what version your msvcrt.dll and mfc42.dll files are? They are located in your \WINDOWS\SYSTEM32 directory. If you right mouse click on the files in the explorer and select 'Properties' and click on the 'version' tab, it should show the file version there.



I've made another stab at a fix. Please try this version and see how it works. I've got a good feeling about this one



Scott

Dave,



Have you had a chance to try the latest fix yet? Just curious to know whether it worked or not.



Scott

Hi Scott,



I didn't want to post the good news too soon...might be jinxed - but the good news is that Housebot now remains running!!



Thanks for the fix...out of interest what did you change in the last version ?



Cheers,



Dave

Dave,



That's great news! If you can give me an update early next week and let me know if it is still running, that would be great. I'd like to release an update soon with this fix.



I was never really able to put my finger on exactly what the problem was, so I just started reworking anything that seemed slightly out of the ordinary. I could see from the dump file that the problem was in a system call to construct the time, so that's where I have been looking.



One fix involved the way that the value for the 'Time' property was being constructed. The SystemTime Device uses a Time and TimeWithoutSeconds Property. Since the values only use times, I was not really setting the 'date' part of the value. This would mean the the system thought it was a time from 1970, which should be ok. Now I set the 'date' part of the value when constructing the time, even though you never see it.



Another fix involved the way that the TimeWithoutSeconds' value was constructed. In the configuration of these values, the way that they are differentiated from other 'Time' values is that the SECONDS value is set to 61. The 61 value was being used to initialize the SECONDS portion of the time value, which was a bit odd, but had always worked before. I now set this value to 0 when constructing the time instead of 61.



I hope this was not too boringly technical... but you asked



Scott

Hi Scott,



I just wanted to let you know that HouseBot has remained 'up and running' over the past few days with the last fix applied....our issue has been resolved.



Many thanks for your efforts :)



Cheers,



Dave

Dave,



That's great news. Thanks for you help and patience in resolving this.



Scott

I've just released an update (version 1.52) that contains this fix and a few others.



Thanks again,

Scott