NeroEjectLoadCD() doesn't work - Club CDFreaks

bthomasch · 24-06-2003

I seem to be having some issues with the NeroEjectLoadCD function. My program relies on the Nero API to manage an automated cd burning system, however i can't seem to get NeroEjectLoadCD to work correctly. Running in debug mode, i can see that it is indeed returning successfully (returns 0), it however doesnt eject the cd drive. Other aspects to the Nero API seem to work correctly, including the NeroOpenDevice() API call that is made right before i try to eject the CD.

A little background on my project:
A multi-threaded automated CD burning system using the Primera Bravo Disc Publisher. It is written in C#, however it uses a Managed C++ wrapper to communicate with a native (unmanaged) C++ library which houses the code which uses the Nero API.

So, i soppose my question is are there any known issues with NeroEjectLoadCD()... or any specific ways i could test what exactly is wrong with the function?

PS- This does not appear to be a hardware problem as the drive in question ejects nicely on its own, and the Windows API has no trouble ejecting it.

Thanks in advance.

*matze* · 25-06-2003

Does the problem also appear if you try to eject the drive with NeroCMD (nerocmd --drivename drive --eject)?

If yes, could you please give me some more information:
- What version of NeroAPI do you have?
- Which drive?
- Which Windows version?

If no, it maybe a problem with your wrapper. In what context do you try to eject the drive (after burning, in a different thread than the other NeroAPI methods, etc.)?

bthomasch · 25-06-2003

Thanks for responding matze,

NeroAPITest.exe can eject the drive without problem, so i assume i must be doing something wrong.

NeroAPI 5.5.10.35
Drive E
Windows 2000 SP3

Ejecting the drive is basically the first thing that my program does, as it is sopposed to work an automated disc publishing system, it needs to eject the drive in order to have the robotic arm place a blank cd in it (so NeroEjectLoadCD is the first thing NeroAPI does after initializing itself). Although the program origionally did the burning on a seperate thread than the one which initialized the API, since i've been running into this problem i've attempted to open the drive on the same thread it uses to start (this hasn't worked any better).

The managed c++ wrapper class really doesn't do anything other than create an unmanaged object of the class i use to control the drive (this class is the one that uses the NeroAPI), and acts simply to point to that class for when it comes time to burn something.... meaning i really don't understand how that could be effecting the API.

have people reported problems with using .NET interoperability and NeroAPI before?

*matze* · 26-06-2003

> The managed c++ wrapper class really doesn't do anything other than create an unmanaged object of the class i use to control the drive (this class is the one that uses the NeroAPI), and acts simply to point to that class for when it comes time to burn something.... meaning i really don't understand how that could be effecting the API.

Sorry, I have no experience in this. Maybe someone else on the forum can tell something about this.

> have people reported problems with using .NET interoperability and NeroAPI before?

Nothing I know of.

24-06-2003	#1 (permalink)
bthomasch New on Forum Join Date: Jun 2003 Posts: 3	NeroEjectLoadCD() doesn't work <a href='http://adstats.cdfreaks.com/www/delivery/ck.php?n=a13febf7&cb=INSERT_RANDOM_NUMBER_HERE' target='_blank'><img src='http://adstats.cdfreaks.com/www/delivery/avw.php?zoneid=30&cb=INSERT_RANDOM_NUMBER_HERE&n=a13febf7' border='0' alt='' /></a> I seem to be having some issues with the NeroEjectLoadCD function. My program relies on the Nero API to manage an automated cd burning system, however i can't seem to get NeroEjectLoadCD to work correctly. Running in debug mode, i can see that it is indeed returning successfully (returns 0), it however doesnt eject the cd drive. Other aspects to the Nero API seem to work correctly, including the NeroOpenDevice() API call that is made right before i try to eject the CD. A little background on my project: A multi-threaded automated CD burning system using the Primera Bravo Disc Publisher. It is written in C#, however it uses a Managed C++ wrapper to communicate with a native (unmanaged) C++ library which houses the code which uses the Nero API. So, i soppose my question is are there any known issues with NeroEjectLoadCD()... or any specific ways i could test what exactly is wrong with the function? PS- This does not appear to be a hardware problem as the drive in question ejects nicely on its own, and the Windows API has no trouble ejecting it. Thanks in advance. __________________ Brian G. Thomasch LINE Imaging Systems

25-06-2003	#3 (permalink)
bthomasch New on Forum Join Date: Jun 2003 Posts: 3	Thanks for responding matze, NeroAPITest.exe can eject the drive without problem, so i assume i must be doing something wrong. NeroAPI 5.5.10.35 Drive E Windows 2000 SP3 Ejecting the drive is basically the first thing that my program does, as it is sopposed to work an automated disc publishing system, it needs to eject the drive in order to have the robotic arm place a blank cd in it (so NeroEjectLoadCD is the first thing NeroAPI does after initializing itself). Although the program origionally did the burning on a seperate thread than the one which initialized the API, since i've been running into this problem i've attempted to open the drive on the same thread it uses to start (this hasn't worked any better). The managed c++ wrapper class really doesn't do anything other than create an unmanaged object of the class i use to control the drive (this class is the one that uses the NeroAPI), and acts simply to point to that class for when it comes time to burn something.... meaning i really don't understand how that could be effecting the API. have people reported problems with using .NET interoperability and NeroAPI before? __________________ Brian G. Thomasch LINE Imaging Systems

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
NeroEjectLoadCD() how to know load or eject	CouJo	Nero SDK Discussion Forum	2	27-05-2006 22:15
how do i get it to work	jordonmatt	Newbie Forum	6	19-03-2006 21:00
Why would this work one way but not another?	rdcrumbaker	Nero SDK Discussion Forum	0	26-01-2006 22:16
Will it Work??	triumphm3	NEC / Optiarc Burner	1	18-12-2004 17:01
Cant get it to work!!	JaiJak	General Software	3	09-11-2004 01:27

25-06-2003	#2 (permalink)
matze Nero Developer Join Date: Jun 2003 Posts: 209	Does the problem also appear if you try to eject the drive with NeroCMD (nerocmd --drivename drive --eject)? If yes, could you please give me some more information: - What version of NeroAPI do you have? - Which drive? - Which Windows version? If no, it maybe a problem with your wrapper. In what context do you try to eject the drive (after burning, in a different thread than the other NeroAPI methods, etc.)?

26-06-2003	#4 (permalink)
matze Nero Developer Join Date: Jun 2003 Posts: 209	> The managed c++ wrapper class really doesn't do anything other than create an unmanaged object of the class i use to control the drive (this class is the one that uses the NeroAPI), and acts simply to point to that class for when it comes time to burn something.... meaning i really don't understand how that could be effecting the API. Sorry, I have no experience in this. Maybe someone else on the forum can tell something about this. > have people reported problems with using .NET interoperability and NeroAPI before? Nothing I know of.

Commercial message