#1 Burning Software

Hi,
I have a combo drive (cd + dvd writer) configured on my machine. The API StarBurn_FindDevice does not detect the device. I am passing the following parameters
int num = StarBurn_FindDevice(SCSI_DEVICE_RO_DIRECT_ACCESS, FALSE, (PCALLBACK)(CCDRecordBurner::FindDeviceCallback), NULL);
But it is returning zero .

What seems to be the problem?

Here's the quotation from the FAQ. Does it fix the issue?

<---

StarBurn works perfectly from Administrator account but does not work at all (no devices found) w/o admin rights. What should I do?

Historically (from early UNIX times) it was decided it's a bad idea to provide raw device access to the users w/o root (Admin) rights because of the security reasons. So StarBurn by default does not work w/o such rights as well. However if it's critical features for you there's a way to make it work. Using special driver located in Bin\Dynamic\Debug[Release]\i386[amd64] (paths are different for debug and release version and for 32-bit and 64-bit operating systems). Just copy it to Windows [or whatever your Windows folder is called]\System32\Drivers folder, apply StarOpen.reg from Reg folder and reboot. After rebooting you'll have StarBurn and all of it applications having free access to your CD/DVD burners w/o Admin rights. StarOpen has extra feature - it allows opening devices in truly "exclusive" way. So no single software would be able to access them while they are used by StarBurn or StarBurn applications. You need to set "Exclusive" to "1" in StarOpen.reg. Driver restart required to update the parameters.

Please keep in mind: there is other software hacking system registry to allow software running w/o Admin rights to access raw devices. However if in case of StarBurn this feature is private, other software just creates backdoor lowering down system security level. Just never allow anybody to have any backdoors or you'd lose your system installation and critical data one day...

--->

Negative.
I have the admin rights of the machine but still no required result

Good...

1) Are you sure you have our WnASPI32.dll wrapper near your application executable?

2) Does burner have symbolic links (D:\ F:\ etc)?

3) Can you send us debug log (see FAQ on how to generate it)?

Thanks!

1] I am having the WnASPI32.dll in my executable folder.
2] The burner has E:\ link
3] I searched the FAQ section but couldnt find anything describing how to generate the debug log. Please can you give the specific location?

1) OK.

2) Good.

3) This is question/answer number ONE. Please follow it and send us via e-mail debug logs from your app and our FindDevice and FindDeviceEx console samples. Thank you!

<---

How can I enable debug logging with StarBurn?

First of all you'll have to use Debug version of StarBurn. Either statically link to StarBurn.lib from Lib\Static\Debug or replace StarBurn.dll with the one shipped in Bin\Dynamic\Debug folder (StarBurn OCX component is already built with log files support so no additional activities required). Then you need to decide - how do you want to catch logs? You can either have them traced to system debug output (any debug output hooker can view them - we recommend either DebugView from www.sysinternals.com or DbgMon from www.osr.com) or just saved to the log file. In last case you need to run StarBurn.reg file located in Reg folder of StarBurn installation to enable log file generation. Edit DebugFileName field and replace default log file name ("C:\StarBurn.log") with the one you want to use.

Please keep in mind: all of the file log entries are appended! So it's a good idea to delete old file before starting StarBurn application if you want to send log to somebody (for example to us for analyze). We don't need whole of your development history stored there from the very beginning of the Earth 

--->

Try SCSI_DEVICE_RO_DIRECT_ACCESS change to SCSI_DEVICE_WILDCARD.


May be in your system was installed Adaptec ASPI Layer? In that case you have conflict of drivers...

FindDeviceEx uses SPTI so does not care about ASPI layer at all... So I need BOTH logs from OP to find out what's wrong.