[dtomcat]

Tim,
Mine does not through any errors. Only the HALi will through something, but no logs are left in HAL. In the PC's system log I believe I read something that the error is happening when trying to initialize HALi.ocx. Again, once I rebuilt the application with the new OCX supplied, it runs fine. I'm guessing something was changed in the newest OCX that old applications don't know what do. As for Dad's problem... I'm not sure... but his surely must through some errors since HAL itself is crashing.




and as a side note, Tim, Your automatedliving email isn't working... my email attempted to deliver since the day I posted this thread and finally came back as undeliverable.

[TimShriver]

Hi Rob,

Yes HALi required a change that caused use to break compatibility. It turns out the QuickInit routine did not initialize some of the areas it was intended to init. So it was a tough call but we thought it was more important that the init areas outlined in the HALi documentation were actually performed.

We have had a couple of reports from customers regarding HAL after a recent windows update. We are trying to identify the common thread between the 3 reports we have, so more data would be great. What we have tried to collect are the typical HAL configuration information along with the hardware and OS details.

Thank you,

Tim

[TimShriver]

Rob,

Mike suggested that one way to isolate the area of the potential crash would be to disable a number of system settings. If HAL runs fine, then systematically enable those areas again one at a time and restarting HAL to see if one of these settings is causing the issue. Be sure HAL is running fine before trying to enable a setting and be sure to restart HAL after the setting change.

I did this same maneuver months ago and identified a modem issue. Also if you disable the modem be sure to also disable the Telephone ASR under voice recognition...

Tim