| ECS-L Home Automation and Security Archives |
| Subject: From: Date: | Re: [ECS] ECST v4 status? David Mccoll Wed, 6 Jan 1999 03:44:50 -0800 |
Wayne, Mark, Re 4.0 ECST. Here's a ZIP containing a CPT.TMP and DBG.TMP error showing ECST accessing the HD when F1,2,3 keys are pressed. It's reading or writing C:W0.CFG. This is easily reproducible with the config I provided in the ZIP from any drive other than C: -- following these steps. 1 -- Delete any stray copies of w0.cfg in all dirs.. 2 -- Copy ECST.EXE and ECS.LGO to drive D: 3 -- Copy the ECS.CFG and ECS.DT, provided in the ZIP. to D: 4 -- Execute ECST from D:\ 5 -- Type the following ALT-S C: CD\ D: EXIT This Shells to DOS, logs on C:, changes logged dir. from C:\ECS to C:\, logs back on D:, and EXITs to ECST. 6 -- Press F1,2 or 3 and you get the error: Error:Open error on "C:W0.CFG". The W0.CFG file is created in the currently logged Dir. on C: when ECST starts up. Exiting back into ECST from DOS it will not be able to find it and gives an error as long as there are no w0.CFG files in the currently logged Dir. on C:. Wayne may not have noticed the HD light if he is using Smartdrv or other disc caching program. Regarding Wayne's color problem: If there are multiple copies of the W0 or T0.CFG on the hard disk in different directories could it not read a bogus .CFG file after a reboot with oddball colors in it ? Wayne do you shell out to DOS and change dirs. often ? The cursor bleeds through its current position when the Clear-screen item engages using this config. DAvid M -----Original Message----- From: Wayne Wittenberg <waynew@magicnet.net> To: ecs-list@netbloc.com <ecs-list@netbloc.com> Date: Wednesday, January 06, 1999 5:20 PM Subject: Re: [ECS] ECST v4 status? >At 07:32 PM 1/6/99 -0800, Mark wrote: >>> 1) speed, v4 definitely slower (about 20-25%) than 3.x >> >>I know of no reason why it would be slower, unless there is an overlay >>conflict (resulting in a disk read every pass). Tracking this down could >>be very time consuming. Is such a reduction that big of a deal ? >>If so, my only suggestion would be to create a cfg holding only the >>passes/event item. Then compare the two .EXEs (they SHOULD match). >>Then incrementally add Items until you see the change. If I know >>which type of Item is causing the problem, I can probably fix it >>quickly. > >Sorry, I don't have that kind of time either, this was supposed to be a >painless upgrade, demanded by you. Yes, the reduction IS a big deal, >especially the extra SLOW screen draws when changing between F1,F2,F3. >There are no visible hard disk writes. > >>> 2) losing status of items when rebooting, items such as colors, which are >>> NEVER changed and many others, the ones I don't realize are the scary ones. >> >>I have tried to reproduce such an error, with backup and without. >>Numerous others are using ECST without this problem, leading me >>to suspect something in your ECS.CFG. >>I need to know the steps required to recreate the problem, >>along with ECS.CFG. >>If I can re-create it, I will fix it. If not, I can't. >>I assume you downloaded ECSUPD.ZIP after my last upload notice. > >I have items (such as colors) that are in NO events, how could it be related >to my .cfg file? How many others are using ECST v4 and have tried rebooting? >Recreating the problem seems to be as simple as rebooting. I will try and >deliberately duplicate it, even though it causes major confusion when items >lose their state. >Yes, I believe I am running the latest version, but there is no way to check >the dates when downloading from your web site. Losing the FTP site is a >bummer, cannot tell dates or size before downloading. > >>> 3) debug messages appearing at random times when nobody home, possibly >>> related to my alpha pager >> >>I have walked thru the code and cannot determine how such an error >>was reported. I need to know exactly what steps are required to >>trigger this error, preferrably with a DBG.TMP & CPT.TMP (and ECS.CFG). > >I will try and duplicate it, but I hate to leave it running in capture mode >for long, especially if not at home. > >>> 4) numeric 'enter' key working different than regular 'enter' key, you >>> stated that it was supposed to be that way. I don't have ANY other programs >>> that work that way. > >How do others feel? v3.3 worked correctly (by my definition). > >Thanks, >Wayne > >