See the help inside the Comm Engine on ways to start user defined programs triggered by X-10 events.

On a 200 MHz Pentium it takes approximately 10 seconds to load HOUSE/290 when classic REXX is used. If Object REXX is used, then the load time increases to 15 seconds because of the additional syntax check. On a slower system, load time will increase as expected.

HOUSE/290 first comes up with a splash screen which loads the main program and communications engine. The splash screen displays a Close button after a few seconds and it may be closed by clicking on it. The splash screen will close automatically once the main program has loaded. By default, the communications engine is minimized and it can be made visible by restoring it to screen from the windows list.

When performing direct control of modules through the switches on screen, the program will wait for confirmation from the CP290. It will then update the slider and toggle positions. During that time, you cannot control any other switches or access any of the CP290 tools like the clock. Also, changing groups, deleting, moving and creating modules and disconnecting from the CP290 or Comm Engine are locked out. It only takes about one second to receive confirmation before all mentioned items are accessible again.

Problem 1:

Slow loading of module edit windows. This is expected if you run HOUSE/290 on a 486 computer. This delay is considerable, but normal. Opening the module edit window needs to load all objects required for editing. Using HOUSE/290 on a Pentium improves the load time of the edit windows considerably.

Problem 2:

If you are running this program at resolutions lower than 1024x768x256, the button bar icons will look a little fuzzy and the program will look grainy because of the gray color background. I will correct the fuzzy icons in a future version. Please note that the program is designed for a 256 color minimum system and will look the best at 1024x768x256. See also the help sections on Start-up Options and Troubleshooting for possible solutions.

Problem 3:

If you use version 30.539 or later of the HP Laser printer driver, the Job Properties button on the print window will not work. Please read the explanation under File - Print for more details.

Problem 4:

Modules do not display the correct status under certain circumstances. Note that it is impossible for HOUSE/290 to know what the module status is because the CP290 does not send out any X-10 commands that do not originate from it's own switches. To make certain to what level a particular module is set to, do the following: From the desktop turn the module fully on or set to the desired dim value.

The CP290 does not support the extended features of the new Two-Way modules like status request. ON, OFF and DIM are however supported.

Problem 5:

You may experience a growth in swap file under the following circumstances: You run another Vispro/REXX compiled program at the same time as HOUSE/290 AND Object REXX is active. If you repeatedly start and exit HOUSE/290 while another Vispro/REXX program is running, the swap file keeps growing. You may have to start and exit HOUSE/290 5-10 times before you see a growth. The memory is not released until both Vispro/REXX-compiled programs are closed. If you close both programs, the swap file will return to it's original size. I have been able to duplicate this problem with UPS Monitor for OS/2 and the HOUSE/290 main and X-10 Comm Tester program. This memory leak may not be specific to these programs as the source of the problem points to Object REXX. If you use classic REXX, this problem will not occur.