#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

Hi,



Unfortunately, our WnASPI32.dll does not work under Win98. Only under NT/2000/XP. That is why you should use only original dll under Win98.

ps. Can you discover where is the problem? (try to use our debug dll)
or try to use (just to check) other protections (like ASProtect or something else)

Hi Alexey,

Yes, I am aware of the WnASPI32.dll thing and yes, I am trying to figure out what's wrong. That's why I was hoping you can provide me with some info about how Starburn.dll work with Win98's WnASPI32.dll, in particular when an application that uses starburn.dll closes. Does starburn.dll unload WnASPI32.dll or something ?

I am using Armadillo because it's the best (IMHO), and I already bought it.

Will be happy to do some more tests with the debug dll ... but what exactly do I do with the debug dll ? Please pardon my ignorance, I'm not really a low level programmer.

Chris

Hi,



We don't cal LoadLibrary to load dynamic-link library WnASPI32.DLL.
(Run-Time Dynamic Linking)
It's loaded during initial process startup. (Load-Time Dynamic Linking)
And we don't need to unload it.


ps. And to check Debug version of dll - you can create debug log (using debug view utility http://www.sysinternals.com/). We will check it.

Bye.

Hi Alexey,

I have used the DebugView utility to get the debug log, but it doesn't really contain much info. Here it is below:

[Picoback]
[Picoback] WnASPI32 ASPI Layer for Windows NT/2000/XP/2003 Version 4.0.0 ( 0x20040814 )
[Picoback] Copyright (c) Rocket Division Software 2001-2004. All rights reserved.
.
.
<Snipped>
.
.
[Picoback]
[Picoback] StarBurn.pas : StarBurn.dll version : 0x20040827

Basically, it just shows that the Starburn.dll has been loaded.

Just wondering though, does Starburn.dll do anything different if Starburn's own WnASPI32.dll is used instead of Win98's WnASPI32.dll ? or are both versions of WnASPI32.dll treated the same by Starburn.dll ?

Regards,
Chris

Hi,

Can you check to compile your project with static libs. (not to use DLL)?



WnASPI32.dll provides only two functions which are used by the starBurn.
They are:
GetASPI32SupportInfo
SendASPI32Command
StarBurn does not depend on its implementation.

Bye.

Hi Alexey,

That would be a problem because I am using Delphi ...

Chris

I have got your mail. I will answer by email.