yeah, you need balabolka because ultrahal does not do Sapi asynchronously. umm...you need it for long responses.

as far as figuring out error lines...if you open the file: "halscrpt.dbg" with a "line editor" (i use crimson editor), you can "go to" that line number and see what it is.
note: you have to do this with the error popup still up. if you reload ultrahal in any way, the halscript.dbg file can change....the line will be different.
also, the halscript.dbg file is a copy of the current (brain and plugin combined) script you are running. you will see the error line, but you will have to figure out whatever plugin it might be in or the brain file you are using. that is what you want to edit....not the halscript.dbg file. halscript.dbg is just a temporary copy of the "whole" script. but that is what the error line number refers to....that file. not the line number in the plugin script file. I hope that wasn't too confusing.
you might need to look in the plugin to make sure that paths are correct for your system. mine might be C:\Program Files (x86) and you might need to change them to C:\Program Files or something. check all the file paths and make sure they reflect your system properly.
wish i had more time to help. good luck.
will always drop in when i can.