• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why does ejecting cdrom take so much resources?

Red Squirrel

Red Squirrel

No Lifer
When nero is done any burning process, it will always eject the cdrom, but this process locks up the whole machine for a few seconds. It's always done this, on any machine I've used nero on, or any copy software that auto ejects the cdrom drive. Is there a reason it takes up so much resources? As far as I know it should be more mechanicly involved then anything, even at the hardware level it should not be more then a few commands sent to the drive.
 
It's because inside the machine while you're not looking, it incinerates your disc, then uses its hidden reserves of materials to manufacture from basic elements a whole new disc. Considering this, a few seconds is pretty short!
 
I've noticed this as well. It does it when it starts a burn too. This has been since I started using Nero many years ago, and through several computer upgrades.
 
It's a Windows thing, I can type 'eject /dev/cdrom' and have my disc eject or be inserted without anything else being affected.
 
I can type 'eject /dev/cdrom' and have my disc eject or be inserted without anything else being affected.
Click to expand...
But does that command actually mount/unmount the disc or is it simply telling the tray to open/close?
 
But does that command actually mount/unmount the disc or is it simply telling the tray to open/close?
Click to expand...

Yes, if necessary it will umount the device. On Linux if the device is mounted the tray is locked so the drive would ignore the eject command anyway.
 
The only version of Windows I have seen to not have this problem is Windows XP Pro x64 Edition. When you insert/eject a disc in it, there is absolutely no delay or slowdown. In all other versions of windows, this problem still exists.(Not sure about Vista)
 
I have more issues when I load a disk. While it detects the disk the system freezes for a few seconds. And if it has issues with the disk it might freeze the system. I sometimes use a paperclip to force it open, which releases the system at least most of the time and gives an error and asks to reinsert the disk.

It is probably I/O related. Isn't DMA supposed to prevent this though by not locking the CPU for I/O, or is that finally done with SATA and NCQ. Does this still happen with SATA optical drives?
 
It is probably I/O related. Isn't DMA supposed to prevent this though by not locking the CPU for I/O, or is that finally done with SATA and NCQ. Does this still happen with SATA optical drives?
Click to expand...

Well DMA uses less CPU time for data transfer than PIO, but the real problem is that the polling process blocks when it tries to read the disc and in the Windows case that process is explorer so it seems like the system locks.
 
Hmm so guess it's windows lack of proper multithreading for this process, or at least, bad cpu management. Since yeah CDs in general are slow in windows, when loading/ejecting.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top