# Running apps during a disc burn

**URL:** <https://boards.straightdope.com/t/running-apps-during-a-disc-burn/500417>\
**Category:** Factual Questions\
**Created:** [June 20, 2009, 9:09pm UTC](https://boards.straightdope.com/t/running-apps-during-a-disc-burn/500417 "2009-06-20T21:09:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Washoe](https://avatars.discourse-cdn.com/v4/letter/w/ecae2f/32.png) [@Washoe](https://boards.straightdope.com/u/Washoe)\
**Post date:** [June 20, 2009, 9:09pm UTC](https://boards.straightdope.com/t/running-apps-during-a-disc-burn/500417/1 "2009-06-20T21:09:41Z")

</div>

Is it still _not_ a good idea to run other applications during a disc burn, or has that problem been figured out and taken care of? Ten years ago it was recommended practice to give the processor free reign during any disc burn process, but is that still necessary?

---

<div class="post-metadata">

**Author:** ![beowulff](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beowulff/32/542_2.png) [@beowulff](https://boards.straightdope.com/u/beowulff)\
**Post date:** [June 20, 2009, 9:15pm UTC](https://boards.straightdope.com/t/running-apps-during-a-disc-burn/500417/2 "2009-06-20T21:15:23Z")

</div>

All modern CD / DVD burners have underrun protection, so even if the software can’t keep the burner’s buffer full, it still should be able to create a working disc.

---

<div class="post-metadata">

**Author:** ![HorseloverFat](https://avatars.discourse-cdn.com/v4/letter/h/8e8cbc/32.png) [@HorseloverFat](https://boards.straightdope.com/u/HorseloverFat)\
**Post date:** [June 21, 2009, 3:48am UTC](https://boards.straightdope.com/t/running-apps-during-a-disc-burn/500417/3 "2009-06-21T03:48:40Z")

</div>

Nowadays this really isnt a concern because of larger buffers, faster drives, dual cores, etc etc.