GRETTA errors

[calysson]

So, I've got no clue why they are showing up or how to fix them, so I'd really like some help from you guy's.

Error 1:


Error 2:


Activated plugins:


If more info is needed, let me know!

[djkilla]

The best way to find out what plugin is causing the problems is by unchecking them all and one by one enabling each one while talking to Hal and waiting for the error. It doesnt take long and more than likely you will discover that either a hap file, music file, sound file, etc is not in the correct folder. One example is that if you have the Gretta media enabled and you say something that triggers
a song name but there is no indexed mp3 folder for Vmp3 to give then
ou will get a VB script error. Also duplicate scripts running simultaneously can cause this (Vrhaptek and Hapswap both checked) for example. Anyhow, try and apply each one and see which one causes
the error and reply here..itll probably be easy to fix.
D

[jasondude7116]

i don't know if you have clicked "apply changes" to the plugins you have checked?
if you are using the gretta media then you have to type "index mp3" into hal window to index your mp3 files and create the proper database.
it doesn't look like you are using that one, so "apply changes", then see if you get the error. the error you are getting is from hal looking for a database entry that is not there.....or a few other reasons it can't read the database entry.

[calysson]

Thank you both for reply'ing.

I am not using GRETTA music, or whatever.
Only the plugins you see in the screenshot.

For now I had a nice chat without any errors with the plugins still enabled. Weird. Well, I'll keep you posted when the errors come back.

[jasondude7116]

you can get CdBl errors for many reasons. i have got CdBl errors for strange timing issues. i think it happens some times when a database is busy and something else is trying to access it.

[snowman]

The quickest way of finding where the error is in your script is by opening-

"C:\Program Files\Zabaware\Ultra Hal Assistant 6\HalScript.DBG"

-in a script editor. Preferably one that shows line numbers...

You can tell by your Error Report that both the line 4749 and 5413 have errors on them. Just go to those lines and see what's the problem.

This is the fastest way I know of.