🚀 go-pugleaf

You have some misunderstandings here. For background, please see any of
the usual references: the CD-R FAQ, Adaptec's WWW site or the primer at
my CD-R site.

Peter Barton wrote:

> The big problem is ejecting discs, and also formatting discs. DirectCD
> won't let a disc be ejected until it is closed

Not so. It will not let you eject until the cached writes are completed.

> - you can't even eject
> using the eject button on the CD drive. Problem is that there will be
> no way for the user to open the DirectCD Wizard and close the disc
> manually. Is there any way programatically that I can either close the
> disc myself, tell DirectCD to close it, or even just force the disc
> out unclosed? The source code I found will only spit out a closed
> disc, otherwise it fails. I notice that Eject from Windows Explorer
> still works, so I guess they're either forcing it, or there is
> something special happening there that DirectCD knows about.

There is nothing special here; Explorer, like any other s/w eject, will
hang until the cached writes are completed, then implement the command.

That said, I know of no programs or components to accomplish your
objective.

Mike

mrichter@cpl.net
http://mrichter.simplenet.com
CD-R http://resource.simplenet.com

You have cross-posted to the universe and e-mailed me privately. That is
excessive and probably objectionable to many afflicted with these
replies.

In my private reply, I suggested that if you plan to use UDF, you need
to understand UDF. There are many references available including the
CD-R FAQ, Adaptec's WWW site and the primer at my site. Please use them
instead of inflicting yourself on the computing universe.

Specifically, we are all still learning. The way UDF works, information
is vulnerable as long as a disc is in a drive, particularly if it is in
fixed-length packets.

Mike

Peter Barton wrote:
> 
> On Thu, 07 Oct 1999 11:28:42 -0700, Mike Richter <mrichter@cpl.net>
> wrote:
> >> The big problem is ejecting discs, and also formatting discs. DirectCD
> >> won't let a disc be ejected until it is closed
> >
> >Not so. It will not let you eject until the cached writes are completed.
> 
> Ah, OK, still learning :) Why don't cached writes complete within a
> few minutes though? I had my PC crash during shutdown today, and when
> I rebooted a directory I created on a CD had disappeared, presumably
> because the data was never physically written to the CD (even though
> it showed up in Explorer).
> 
> >There is nothing special here; Explorer, like any other s/w eject, will
> >hang until the cached writes are completed, then implement the command.
> 
> Actually Explorer DOES Eject, when all other s/w fails. My only
> assumption here is that DirectCD either has an Explorer extension, or
> some other patch, which calls the Adaptec eject.
> 
> >That said, I know of no programs or components to accomplish your
> >objective.
> 
> Somehow I knew this answer was coming. Does anyone know if other
> packages behave the same way? I'm guessing they probably do.
> 
> Thanks for the quick response Mike, it's good to at least have someone
> else's view on this and get some answers, even if they're not the ones
> I wanted to hear!
> 
> Peter Barton: pbarton@tig.com.au
> P.O. Box 364, Bulleen, VIC 3105, Australia
> http://www.madmaxmovies.com/ - Mad Max!

-- 
mrichter@cpl.net
http://mrichter.simplenet.com
CD-R http://resource.simplenet.com

On Thu, 07 Oct 1999 11:28:42 -0700, Mike Richter <mrichter@cpl.net>
wrote:
>> The big problem is ejecting discs, and also formatting discs. DirectCD
>> won't let a disc be ejected until it is closed
>
>Not so. It will not let you eject until the cached writes are completed.

Ah, OK, still learning :) Why don't cached writes complete within a
few minutes though? I had my PC crash during shutdown today, and when
I rebooted a directory I created on a CD had disappeared, presumably
because the data was never physically written to the CD (even though
it showed up in Explorer).

>There is nothing special here; Explorer, like any other s/w eject, will
>hang until the cached writes are completed, then implement the command.

Actually Explorer DOES Eject, when all other s/w fails. My only
assumption here is that DirectCD either has an Explorer extension, or
some other patch, which calls the Adaptec eject.

>That said, I know of no programs or components to accomplish your
>objective.

Somehow I knew this answer was coming. Does anyone know if other
packages behave the same way? I'm guessing they probably do.

Thanks for the quick response Mike, it's good to at least have someone
else's view on this and get some answers, even if they're not the ones
I wanted to hear!



Peter Barton: pbarton@tig.com.au
P.O. Box 364, Bulleen, VIC 3105, Australia
http://www.madmaxmovies.com/ - Mad Max!

If you get annoyed by his crossposting, you can simply not answer instead 
of adding to this crossposting.

Mike Richter <mrichter@cpl.net> wrote in <37FD9352.3C37FB13@cpl.net>:

>You have cross-posted to the universe and e-mailed me privately. That is
>excessive and probably objectionable to many afflicted with these
>replies.
>
>In my private reply, I suggested that if you plan to use UDF, you need
>to understand UDF. There are many references available including the
>CD-R FAQ, Adaptec's WWW site and the primer at my site. Please use them
>instead of inflicting yourself on the computing universe.
>
>Specifically, we are all still learning. The way UDF works, information
>is vulnerable as long as a disc is in a drive, particularly if it is in
>fixed-length packets.
>
>Mike
>
>Peter Barton wrote:
>> 

On Thu, 07 Oct 1999 23:46:42 -0700, Mike Richter <mrichter@cpl.net>
wrote:
>In my private reply, I suggested that if you plan to use UDF, you need
>to understand UDF. There are many references available including the
>CD-R FAQ, Adaptec's WWW site and the primer at my site. Please use them
>instead of inflicting yourself on the computing universe.

I did search those places, and they didn't have any definitive answers
to the questions I was asking. And to me, ejecting the disc has
nothing to do with UDF itself, just how Adaptec implements their Eject
behaviour in their driver.

Also, contrary to your "No" response via email, Adpatec DO extend /
patch windows explorer's right click menu for the CD drive, allowing
you to select "Format" and "Eject", both of which hook back into
Direct CD (2.5d). Try it. That's probably going to turn out to be the
way to solve the problem for me. The only other option is
automatically driving DirectCD's Windows like someone else suggested,
but from past experience that can be unreliable.


>You have cross-posted to the universe and e-mailed me privately. That is
>excessive and probably objectionable to many afflicted with these
>replies.

I CC'd the message to your email in case you missed the followup, this
is default behaviour for me. Sorry that it offended.

As for the other, the whole purpose of cross-posting is to cover the
case where multiple groups basically cover the same topics, and there
isn't just one definitive group on the subject. Some developers only
read the microsoft.* hierarchy. Other CD specific developers would
skip that totally and just read the cdrom groups. I did think this one
through carefully, and apart from the .misc group which was just a
"cover all" inclusion, I don't spot a group on the list which this
topic isn't relevant to. What I did spot is that the cross posting
caught a bunch of people who are also having the same problem, and
have emailed me privately asking me for a copy of any info that I
manage to get on this one. Certainly no other complaints though.



Peter Barton: pbarton@tig.com.au
P.O. Box 364, Bulleen, VIC 3105, Australia
http://www.madmaxmovies.com/ - Mad Max!

i am not sure but...
for eject:
ShellExecute(0, "Eject", "E:\", NULL, NULL, ... )
anyway, just do ShellExecute on CD drive with EJECT verb... if explorer
can do it, let him do it :)

Mikhail

Peter Barton wrote:
> 
> I'm building a kiosk type application, which as part of its operations
> copies files onto CDR discs. The Adaptec DirectCD driver seems to work
> fine as far as making the drive accessable from my software, just like
> reading / writing a hard disk.
> 
> The big problem is ejecting discs, and also formatting discs. DirectCD
> won't let a disc be ejected until it is closed - you can't even eject
> using the eject button on the CD drive. Problem is that there will be
> no way for the user to open the DirectCD Wizard and close the disc
> manually. Is there any way programatically that I can either close the
> disc myself, tell DirectCD to close it, or even just force the disc
> out unclosed? The source code I found will only spit out a closed
> disc, otherwise it fails. I notice that Eject from Windows Explorer
> still works, so I guess they're either forcing it, or there is
> something special happening there that DirectCD knows about.
> 
> This is with DirectCD 2.5 by the way, I'm about to go and buy version
> 3 to see if that helps me at all...
> 
> Peter Barton: pbarton@tig.com.au
> P.O. Box 364, Bulleen, VIC 3105, Australia
> http://www.madmaxmovies.com/ - Mad Max!

Mikhail A wrote:
> 
> i am not sure but...
> for eject:
> ShellExecute(0, "Eject", "E:\", NULL, NULL, ... )
> anyway, just do ShellExecute on CD drive with EJECT verb... if explorer
> can do it, let him do it :)

While the original questioner expressed disdain about the need to
understand UDF for his application, it may be relevant to you. Ejecting
a packet disc is not the equivalent of ejecting a conventional CD-ROM.
Depending on the format, the process may begin with organizing and
writing data from RAM and may include intercepting the command for the
opportunity to finalize the disc or the session.

The shell command may do the job, depending on the way that commands to
the drive are intercepted by the UDF modifications to the filesystem.

Mike

mrichter@cpl.net
http://mrichter.simplenet.com
CD-R http://resource.simplenet.com