Print

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

[jcgso]

Hi all.  First post here after installing AHP, Iwitness and MyHome on a WIN XP system, using a ATI All in Wonder video card.  When attemting anything to do with cameras, video settings, basically anything to do with iwitness, AHP crashes every time.  After many hours of trying to fix it, I'm pretty frustrated, since I bought this to use as a remote security system. The cameras work fine on TVs in the house.   Any help would be greatly appreciated.

[X10 Pro]

This sounds like a possible conflict with software from ATI. Try this:

1. Look in Program Files\Common Files\X10\Common\ for a file named X10net.dll.
2. Copy that file to \Program Files\ATI MultiMedia\RemCtrl\.

That should replace the file that's causing the error. You may need to stop the X10 Device Network service (from Control Panel | Administrative Tools | Services) before you can overwrite the files.

[jcgso]

OK, so far I have copied the x10net.dll  to \Program Files\ATI MultiMedia\RemCtrl.  I have downloaded the latest version of directx, deleted all of the AHP software and plug ins, installed the newest upgrade to AHP (3.203) and AHP still crashes constantly.  I can not load a camera module directly.  I have to load an appliance module, then change it to a camera.  I am able to get a picture on this one camera, but it does not show up under the cameras menu on the left.  If I try to add another camera (I have 4 I need to have working with AHP/Myhouse and they work fine on my TVs), AHP crashes and will not even open again without crashing.  Then I have to delete everything and reload all.  I am getting very frustrated and would appreciate some assistance.
Thanks

[X10 Pro]

When the crash occurs, can you click More Details and tell me what module name, version, error location information there is for the problem? It sounds like you have some software causing a conflict with one of the X10 components that let iWitness work.

[jcgso]

It only gives the message asking if I want to send an error report to Microsoft, which I have done.  After doing that and clicking on details, Microsodt says it's a known problem with x10net, which has no solution.

[jcgso]

Can anyone help, or does this software just not work as it is supposed to???

[Chris S.]

I captured the following screen shots when AHP crashed as a result of Iwitness video recordings.
WinXP Pro SP2
AHP 3.203

[mike]

I had hard time getting into why the video crashes but your post and others helped me come up with the following possible work around.  I am cc'ing it as post to many video crash posts to get the word around.....
---------------------------------

You do know that their install program often installs an IPB camera driver rather than x10 driver, right?  If this happens, I found that even simple snap shots every 30 seconds would crash AHP anywhere from 1-20 minutes! Getting this install right per their note:

----------------------------------------------
Greetings from X10,

It sounds like the VA11A is not being loaded correctly.  If you have not done so already, please download and install the x10drivers.exe file from the website below:

http://www.x10.com/software

After installing that reboot the computer and then check in the device manager for windows.  Once there look under the imaging devices catagory to and look for the x10 va11a.  If that is not listed but you see a device there called Intel PC camera pro then follow the next steps.

1.  Right click on intel pc camera pro.  Select update driver.
2.  If it askes you to connnect to microsoft say no not at this time.
3.  Next choose to install from a list or a specific location.
4.  Then the choice that says "Dont search, I will choose the driver to install.
5.  On the next screen select the X10 VA11A Video Capture adapter.
6.  It will then begin a found new hardware and begin to install the drivers. On the next windows just choose continue anyway.  And then it should come back up with some found new hardware.  Choose to install automatcially on both of the next screens.

Follow that procedure and the va11a should now work properly.  The procedure might look slightly different that how I have described it but it will be similar.  Try it and then get backto us if there are further problems.


Thanks
-Nathan
X10 Customer Support
1-800-675-3044 Ext 2754
------------------------------------------

So if your driver is ok, then you are victim of their bad coding in AVIdll thingy.  I found what seems so far to be a work around below.  Hope it helps....
---------------------------------

Seems the issue is the poorly written video dll in AHP crashes if you tell it to record AGAIN while still recording - OR MAKING THE AVI FILE AFTERWARDS - TAKES 40 SECONDS ON MY COMPUTER.   X10 could easily fix this by properly closing an open compile session beforer starting another one - this should not have to be taken care of by the user for crying out loud!

So you have to use some condition that stops a macro from trying to START RECORDING while one is in use, or for the time afterwards that it takes AHP to actual compile the Avi file - from what I can see. 

Since flags no longer work as conditions, I did the following and THINK I have a working recording multi camera system....  I sent this to tech support along with abouit 40 others and all they ever send back is canned reply that my driver is wrong, reinstall.....

Guys, I seem to have found a work around somewhat to flags not being useable for conditions.  I made a fake 2 way appliance module called B16 and am setting it when I trigger a macro for a camera that will include capturing 30 seconds of video.  I use it for the condition on the other macros so they do not start if one is already on.  Seems to work so far.

AHP takes  40 seconds - on my computer - to compile the captured video after recording stops and actually make an AVI file - it is 0 bytes long until this time is up at end of recording.  If I trigger another video capture before this time is up, it appears 50-50% chance that I will end up with the first one 0 bytes long and hence lead to the AHP crash.  Is this true?

So I've added a 40 second timer at end of each video recording macro just before I turn B16 flag back off.  So far so good....

[AzCoronaDog]

I was getting the "must shutdown" message any time I tried to change cameras in AHP.
Also, I did not see any cameras under Tools/Preferences Multi-Camera tab.

I bought AHP without iWitness, and had added my cameras as appliance modules, just so I could switch them.  After I added the iWitness plug in, I just edited the modules to be cameras.  THIS DOES NOT WORK PROPERLY!

I deleted all my cameras, then re-added them as cameras to begin with, and it is working (so far!).  They now show up in the Multi-Camera tab, and they switch fine.

Note to X10 - THIS IS A BUG.  If you can't switch from an applicance module to a camera without problems, don't offer the choice.  I have been a professional programmer for 26 years, and I would be thoroughly embarrased if I every let a product this buggy get released.  This programming is not particulary complicated, and it can be fixed.  Hire some talent and get it done!

[BJHENSEL]

WELL I thought I would check up on x10, and see if they have done anything to fix numerous problems with their software , and the last post to this thread is last July, and it is now November, and WOW still nothing. I foolishly bought the AHP with I witness to set up a multi camera security system, and as soon as I fire up I witness, and try to add a camera or anything to AHP CRASH!!!!! Talk about frustration! I had to build another computer with XP operating system installed because my new machine uses XP 64 bit, which is totally not compatable with anything X10 sells. They said they would release a new driver for the VA 11a when Vista is released, but still nothing, these guys care more about there web site with all the flashy circus effects, and annoying popups to sell sell sell. Check out the last time they updated the AHP software, or Iwitness. I guess I will come back sometime next year, and see if I can use their software garbage yet, or just cut my losses, and go to a more reputable company.