Okay, I don't know if this will help, but it is worth a try. I'm not familiar with a Dialogic board, but I'll see if I can help.If the device driver for that board is not Resource Manager aware, you may need to reserve the IO and IRQ stuff for that board, so that nothing else will try and grab those resources. To do this, use the RESERVE.SYS command. There is some more information on reserve.sys at:
http://www.markcrocker.com/rexxtipsntricks/rxtt28.2.0804.html
But here's the quick rundown. Edit your config.sys file (you may need to boot with the ALT-F1 option) and put as your first line in your config.sys file:
BASEDEV=RESERVE.SYS
You'll need some options on the line too. It supports the following - and this information comes from the OS/2 help files (type help reserve.sys at the command prompt):
/IO:n,n - this will reserve an IO port where the first n is the base port number in hex, followed by the length (number of ports) in hex. An example for reserving port 340 would be: /IO:340,4
/MEM:n,n
/MEM:n,n will reserve memory, the first n is the base memory address in hex, with the assumption tha that the address is nnn:2, followed by the length (address number) in hex, separated by a comma. Example: /MEM:CA00,1000
/DMA:n - reserve a DMA channel. Example: /DMA:2
/IRQ:n - reserves an IRQ. Example: /IRQ:5
So, my guess for your card, the reserve line would be something like:
BASEDEV=RESERVE.SYS /MEM:D000,2000 /IRQ:5
That should reserve those addresses for hardware that does not properly cooperate with the resource manager.
As for preventing apps from starting up automatically, from the OS/2 tricks file:
" To prevent applications from restarting during boot, hold down the Ctrl, left Shift, and F1 keys at the same time,
beginning when the mouse pointer appears until the icons begin appearing on the desktop. If you find that disk
activity stops, you may have to release the keys and then quickly hold them down again.
"
I don't know how well this will work, I can't recall if this prevents apps which are started in the STARTUP.CMD file from starting.
Another option is to install a process killer such as Watchcat and see if that can kill the app once it fails. Watchcat installs a driver which allows you to press CTRL-ALT-W when something fails and it will usually activate, and allow you to kill applications, see what is going on, what is hung, etc. It doesn't solve the problem, but may allow you to figure out where the problem is.
http://hobbes.nmsu.edu/cgi-bin/h-search?key=wcat21&pushbutton=Search
Also, RMVIEW will allow you to see what is going on with the resource manager (IO ports, IRQ usage, mem usage, etc.). At a command prompt, type
RMVIEW /?
for an overview of what it can do.
Also, what version and revision of OS/2 are you running? From a command prompt, type:
ver /r
There were a lot of voice mail systems which were built on Warp 3 Connect systems which never had any fixpaks applied, and some of the issues which turned up were fixed by fixpaks. Depending on the situation, it may be worthwhile to install a fixpak.