#1 Burning Software

Hi,

Can I ask if Starburn.dll does things very different on Windows 98 where the WnASPI32.dll that comes with Win98 is used, rather than Starburn's own WnASPI32.dll ?

The reason I am asking is because the software that I am developing is protected using Armadillo (HTTP://SILICONREALMS.COM/INDEX.SHTML), and for some weird reason, it is interfering with Starburn IF Window's WnASPI 32.dll is used, rather than Starburn's own WnASPI32.dll.

Here are the symptoms of the problem:

(1) On Windows 98, the first time I run my app, everything works just fine without any problems. However, if I close it, then run it again for either the second or third time, it will cause Win98 to BSOD with fatal exception. It's always never the first time.

(2) If I run five instances of my app consecutively without closing any of them, all runs fine. Now, if I start to close them one by one, when I get to closing the third instance, Win98 just freezes.

From the above tests, it would seem that my app, when closed, something isn't unloaded properly. My guess is that Armadillo protection is interfering with something that starburn.dll is doing with Window's WnASPI32.dll, but NOT Starburn's own WnASPI32.dll, that's why I am asking how they differ so that I can pass on the information to the Armadillo developers to help them debug the problem faster.

Thanks in advance for your help.

Kind regards,
Christopher Tan