#1 Burning Software

I've just downloaded and reinstalled StarBurn as a test version, as I'd been having some trouble with an attempt at DVD burning and figured a fresh download might ensure my various versions of StarBurn would be untangled.

When I call StarBurn_FindDevice, the callback isn't invoked. This occurs both in my test application and in the FindDevice sample.

What might cause this? (I didn't have this problem with the same DLLs before downloading, and don't with version 3.4.)

The log says only:
StarBurn CD/DVD Burning, Grabbing and Mastering Toolkit for Windows 95/98/Me/NT/2000/XP/2003 Version 6.6.30 ( 0x20060630 )
Copyright (c) Rocket Division Software 2001-2006. All rights reserved.

I'm using the FindDevice Delphi example, and the 06302006 build of Starburn.dll and WnAspi32.dll. I changed the BUILD_DATE constant in StarBurn.pas to $20060630 to avoid the "wrong version" error; the original value was $2006430, I believe.

I have StarBurn 3.4 on my system, but the version 6 DLLs are in the directory with my test application and the StarBurn samples.

I don't see WnASPI32.dll banner in the log. So I guess StarBurn.dll did not find WnASPI32.dll and that's the reason why it finds no devices. Double-check the DLLs or change device find method with the CreateEx(...) style enumeration (see FindDeviceEx C sample for this, quite stright-forward).

Thanks. I'll try these suggestions at my next opportunity.



I can't find FindDeviceEx in my download (Personal trial edition).

Check for console "C" samples. Pascal equivalent does not exist yet.

Alas, not straight-forward enough. I can't figure what "CreateEx(...) style enumeration refers to.

Also, I have made sure wnaspi32.dll is in place.

I can't use the method in the FindDeviceEx example, as my application must support Win95/98/ME.

And I neglected to mention I'm using Delphi 5.

1) Indeed, you need Create(...) if you want 95/98/Me compatibility...

2) What OS are running at right now?

3) If there's no WnASPI32.dll banner this means it's not in path or it's some alien ASPI layer, not RDS. Please send us both COMPLETE debug log and FindDevice application console output captured to file with FindDevice.exe >out to support@rocketdivision.com. We'll sort the issue out.

Thanks!

The problem turned out to be the presence of the StarBurn 3.4 driver, staropen.sys, in my Windows\System32\Drivers directory. Version 6.0 of starburn.dll is incompatible with it.

Replacing that with the driver for version 6.0 and rebooting solved the problem.

As one whose application must be run by non-Administrators, I have to distribute staropen.sys.

Just what we've discussed in our e-mail conversation

Nice to know the issue is gone.

Thanks!