Slow FindDevice with network burner

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Hi

I've had a report of my app (with StarBurn 7.2.20.544) taking a particularly long time to perform drive discovery with a network burner.

Here is our log with seconds on the left:

65 - [BurnerLog] UpStartEx
65 - [GetTransportType] UseSptiTransport: True
65 - [PrepareBurnerList] Start
65 - [BurnerLog] CdvdBurnerGrabber_GetDeviceInformation
65 - [BurnerLog] CdvdBurnerGrabber_GetSupportedMediaFormats
65 - [BurnerLog] CdvdBurnerGrabber_GetSupportedMediaFormatsExEx
65 - [BurnerLog] CdvdBurnerGrabber_ProbeSupportedWriteModes
65 - [BurnerLog] CdvdBurnerGrabber_ProbeSupportedReadModes
66 - [BurnerLog] CdvdBurnerGrabber_TestUnitReady
66 - [BurnerLog] Destroy: Grabber
129 - [BurnerLog] CdvdBurnerGrabber_GetDeviceInformation
129 - [BurnerLog] CdvdBurnerGrabber_GetSupportedMediaFormats
129 - [BurnerLog] CdvdBurnerGrabber_GetSupportedMediaFormatsExEx
177 - [BurnerLog] CdvdBurnerGrabber_ProbeSupportedWriteModes
226 - [BurnerLog] CdvdBurnerGrabber_ProbeSupportedReadModes
226 - [BurnerLog] CdvdBurnerGrabber_TestUnitReady
242 - [BurnerLog] Destroy: Grabber
242 - [PrepareBurnerList] Device 0: E: DVD RW DRU-820A
242 - [PrepareBurnerList] Device 1: F: WRR-4848
242 - [cbDrivesChange] Selected Device 0: 0^E: DVD RW DRU-820A
242 - [PrepareBurnerList] End, Burner count: 2

IOW it takes nearly two minutes to fully initialize StarBurn and get a list of all burners.

On our test systems with regular burners it is reasonably quick, but there is still a noticeable pause.

Is there an easy way for the burner information to be persisted between sessions to speed this up?

Also, I may call StarBurn_FindDevice twice (initializing the list and again before burning to ensure they have a valid disk inserted). Is there a better way I can simply refresh the status of a particular device (in particular to get details on the inserted disk).

Regards

x

anton (staff) · **Posted:** Mon May 12, 2008 1:50 am

It's a very bad idea to use FindDevice as it's ASPI call acually. Re-check SPTI and SPTD samples, they have totally different device enumeration loop. ASPI lookup is made slow as it uses polling (backward compatiblity with Windows 98 broken "get device" call). Just don't call it at all...

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Hi Anton

If it's such a bad idea, why is it done in the (GUI) demo projects? :shock:

So is Samples\Console\Pascal\FindDevice.dpr a suitable code model?

(In tandem with StarBurn_CdvdBurnerGrabber_CreateEx if SPTI transport is enabled).

anton (staff) · **Posted:** Mon May 12, 2008 5:46 am

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

anton (staff) · **Posted:** Mon May 12, 2008 7:30 am

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

aaron (staff) · **Posted:** Wed May 14, 2008 8:36 am

xexx · **Joined:** Tue Oct 31, 2006 12:25 am **Posts:** 43

Those are not applications that are typically installed by typical users, so i'd have to say there is only a chance, rather than a great one :wink:

I can't find much info on SPTD, such as:
- How can one determine if SPTD is installed?
- How can one install it silently?

anton (staff) · **Posted:** Wed May 21, 2008 10:07 am

#1 Burning Software

Slow FindDevice with network burner

Who is online