Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ViperDragon]

I recently updated my server computer that runs all my X10 equipment to Windows 7 Ultimate 64-bit.  Before I was running on Windows XP Pro SP3.  I use the X10 FireCracker serial module (CM17A) and the Fireck32.exe program to execute my needs via batch files.  I was also using the module via a USB to Serial cable (Prolific brand) in XP with no problems.

Once I updated to Windows 7, using the same setup, I cannot get the batch files to turn devices on/off.  It executes with no errors.  If I use the Windows FireCracker application on the correct COM they work fine.  I tried using the compatibility modes and run as administrator with no luck either.  I installed an actual serial card in the system and still get the same result.

My batch files follow the correct command line sequence:
Fireck32.exe /com=2 /house=a /device=1 /action=on

I am using Fireck32 v.1.1.

Has anyone run into this problem?  Thanks.

[ViperDragon]

I tried some 3rd party applications like FireworX-10 and Watcher and they all turn the equipment on and off.  I can't figure out for the life of me why the Fireck32.exe program is not executing.  I tried manually typing the command sequence out in the Command Prompt and still no luck.  Anyone still using Fireck32.exe under Windows 7 (or Vista)?  It's a real head scratch-er...

I use the batch files to run quietly in the background, which are executed with a macro automated program called Automate.  I have my cameras using the batch file to loop every 60 seconds with the help of the Automate program.  I installed the Watcher program and while it does loop my cameras, it doesn't minimize or hides itself.  Anyone have any recommendations on software I could use to workaround my Fireck32.exe issues, that could run timers and sit hidden in the background?

Thanks any help or suggestions.

[trunner]

Did you get anywhere with this? I am in the same boat. My device (CM17A connecting to a TM751 and several lamp and appliance modules) works great with FireworX-10, but no joy with firecracker or ActiveHome. Running windows XP (32bit). Tried for over 2 hours to get ahold of tech support, I got transferred 8 times to sales and hung up on 3 times.

[ViperDragon]

I found that I had to install the original FireCracker 1.0 version that also installed the missing Visual Basic DLL files (I think it was version 5 or 6), then I just simply copied over the updated FireCracker 1.1 program.