Bug: Drive letter A and B not recognised

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Hi,

if you change the drive letter of a burning device to A or B using the Windows drive manager, the drive is no longer available through the StarBurn SDK.
No log necessary, easy to reproduce.

Regards,
Florian

anton (staff) · **Posted:** Fri Jun 18, 2010 8:38 pm

Don't use ASPI to enumerate the devices. And don't use ASPI at all (it's still in SDK for compatibility reasons, I think we'll drop ASPI support in V13 this summer as Windows 9x is gone long time ago). Stick with SPTI (backward compatibility) or SPTD (recommended). For ASPI device enumeration cannot use A: and B: as they are legacy drive letters used for floppy. Trying to open such a device w/o media can hang machine. So it's not a BUG it's a FEATURE and SCSI communication layer misuse.

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

I'm not using ASPI.

anton (staff) · **Posted:** Sat Jun 19, 2010 7:15 am

Good. So just change enumeration loop to start from A: letter rather then C: letter. And you should be fine. Issue has nothing to do with StarBurn from what I see now.

flöle wrote:

I'm not using ASPI.

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Seriously. Do you think I'd start enumerating at "C" and then complain that StarBurn doesn't show drive A and B!?

That's the code, if you have doubts.

Code:

for (int i = 0; i < StarBurnEngine.Drives.Count; i++)
{ ... }

anton (staff) · **Posted:** Sat Jun 19, 2010 7:40 am

OK, so do you use SPTI or SPTD to create device object? StarBurn or StarBurnX? And what error do you have or attempt to create it?

P.S. A log posted initially would speed up the whole thing quite a lot...

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

SPTI / StarBurnX. I don't have any error, just a missing device.

anton (staff) · **Posted:** Sat Jun 19, 2010 5:07 pm

I'll check with Dima on Monday. We don't use drive letter based enumeration sequence inside StarBurn or StarBurnX. Rather it's \\.\CdRom%d style symbolic link. There's a way to get EXACT drive names (w/o manual enumeration when working thru SetupDiXxx calls) so I think we'll implement it in one of the upcoming builds. Thank you for letting know!

dima (staff) · **Joined:** Thu Dec 13, 2007 8:44 am **Posts:** 609

Hello,

Yes, you are right ... already fixed

Thanx!!

Dimitry

anton (staff) · **Posted:** Mon Jun 21, 2010 6:11 am

I'll change FindDeviceEx and FindDeviceExEx samples to use SetupDiXxx enumeration in any case.

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

You'll let me know when there is a new StarBurnX version downloadable?

anton (staff) · **Posted:** Mon Jun 21, 2010 7:16 am

V13 release is scheduled for mid-July.

flöle wrote:

You'll let me know when there is a new StarBurnX version downloadable?

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

A beta would be fine for me as well. I guess that V13 will be delayed anyway

anton (staff) · **Posted:** Mon Jun 21, 2010 12:06 pm

Sure.

flöle wrote:

A beta would be fine for me as well. I guess that V13 will be delayed anyway

flöle · **Joined:** Sun Jun 14, 2009 6:00 pm **Posts:** 542

Any news?

#1 Burning Software

Bug: Drive letter A and B not recognised

Who is online