#1 Burning Software

Hi,

I tried your sample apps on a machine with Windows ME and had no luck (another try with Window 98 was the same). The FindDevice-Sample doesn't find any device (the computer has two devices build in).
Your GUI-Sample "DataBurner" hangs while "Refreshing devices" (maybe it waits for a callback).

I used the debug versions of the dll and enabled the registry key:
But the file BurnLog.txt does not contain any content except this:


What do I have to do to make the burn engine work with Windows 98/ME?

Please try FindDevice console sample from DEBUG directory first. And post the log and console output here. Thanks!

I used the debug version (DLLs and executeable) but there is no detailed log.
I retried it with the C-Version: "StarBurn SDK\Bin\Samples\Console\C\Dynamic\Debug\FindDevice.exe". I also tried the static version. It's the same.

Here is the console output:


On Windows XP it works fine with the detailed logs, but there is no problem finding the devices.

I found the problem: "ASPI Layer for Windows NT/2000/XP/2003". When I delete the wnASPI32.dll it works fine.
But now is the question how to deploy (I prefer xcopy) an application which works with Windows 9x as well es Win 2000/XP? Can StarBurn ignore the DLL in Window 9x-Mode or do I have to make sure that this DLL is not installed on Win9x?

Here's what written in the FAQ...

-->

Q3: What's ASPI and why should I have WnASPI32.dll shipped with my software?

A3: ASPI stands for Advanced SCSI Programming Interface and it was standard way for accessing SCSI devices under early versions of Windows. Later ATAPI (and other interface) devices got SCSI-like interface and it was easy to have single way of programming them at low level. Starting from Windows NT ASPI support was dropped by Microsoft (and replaced with SPTI - SCSI Pass Thru Interface) but a lot of people found it's easier to have ONE way of coding for all of the supported OSes then just treat every single OS in the other way. So if you need Windows 95/98/Me line of the OSes - please stick with ASPI and use StarBurn_CdvdBurnerGrabber_Create(...) API call to create burning device object. Windows 95/98/Me has ASPI stack built-in and you may use Rocket Division Software ASPI layer as redistributable WnASPI32.dll file shipped together with your software if you run it under Windows NT/2000/XP/2003. Please note that other ASPI layers may work with StarBurn and may not work with StarBurn. We've been tested with own one and Adaptec ASPI layers only.

However if you don't old junk and want to stick with only NT like of the OSes - just use StarBurn_CdvdBurnerGrabber_CreateEx(...) API call. It would end with SPTI calls finally. In such a case you don't need WnASPI32.dll at all. Please see FindDevice and FindDeviceEx samples from Samples\C[Pascal] for more of the details.

Also there's third way to send commands to the device. Thru the special filder driver which is part of the Daemon Tools (our friendly software). It has a great feature of hiding all of the data traffic between application and raw device. So it's nearly impossible to trace it and break the burning process (quite a lot of poorly designed software like antiviruses and other burning applications can do this). If you want to have this feature enabled - please contact us via the support@rocketdivision.com e-mail account.

So, if other burning software forces you to stick with only one of the programming interfaces to talk to raw device - StarBurn know THREE diffeent ways to do this. And you can pick up the one working for you in the best way.

<--

It's your job to detect the OS version (GetVersion(Ex) Win32 API call) and either use Create(...) or CreateEx(...) StarBurn API call or stick with Create(...) always but copy or not copy RDS own WnASPI32.dll during installation phase.