#1 Burning Software

Is the devicename argument the windows device path? If so can I use this instead to create my object. Currently I am finding the burner device by parsing the USB chain(My burner is always connected to a hub that has a custom USB device on it) which gives me a windows device path. I then use a Win2K+ command to get the volume name(ie E:,G: etc...) which means we can only support win2k and up, and then I use the StarBurn_GetDeviceNameByDeviceAddress to get the volume name of every device Starburn sees to match to. I'd much rather just use the windows device path to open/create the burner object which would also let me keep 98/ME compatibility.

Nathan

1) It's device symbolic link name. It *can* be drive letter (f.e. "G:") or it can be "CdRom0" or it can be GUID got from SetupDiXxx enumeration if device does not have symbolic link name.

2) CreateEx is SPTI and would *NOT* work under Windows 9x/Me. Stick with ASPI and Create if you need both NT and 95 compatibility.

I guess it doesn't matter then as far as 9X/ME compatibility. Since I have to use a Win2K+ command to get the drive letter(which I need to find out the SCSI address when using Create). But it does sound like I can use the devicepath I'm getting from windows(SetupDi). Am I correct when I say I get exclusive access to the drive when I use SPTI(no external "drivers" can interfere)?

Nathan

No. Other software could keep the handles opened ALREADY.

Use StarOpen (kernel helper driver) exclusive access configured to get exclusive access. True "stealth mode" is available only with own hook-based SCSI filter driver (like the one in Deamon Tools f.e.).

Thanks, Exclusive is not required for us. If we have to we can tell our users not to install other burning software(eg. Sonic). Nero doesn't seem to be a problem anyways. I did notice that when I had Alcohol installed one of my drives would no longer work with GrabDisc.exe. After uninstalling Alcohol the problem went away.

Nathan

Alcohol also uses filters. You may write down to their support forum put some info here. We're in contact with their driver tools developers and I think we'll find a solution.

Thanks, I was hoping I could tell our customers they could use Alcohol with MDS files generated with our autoloader app.

Nathan

Better it would be Daemon Tools as they are free. And in next update StarBurn would go with own CD/DVD emulator.

Thanks I'll keep that in mind and be looking forward to the addition to Starburn.

Nathan

What type of the images you need to emulate? Generic? Of something special (like only DVD-Video)? Do you need network support?

Right now that ability is something I'm only thinking of added much later to our software. For the first release I'm only focusing on the basic abilities. Eventually though I think DVD-Video is the main focus.

Nathan

Good! B/s we're planning to start with DVD emulation frm .iso and .mds images