Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Image Burning: Buffer Underrun Reason/technique?

2002-01-31 by Steadman Uhlich

Ah yes....but I live in the past (my firewire CDRW is only 10 months "old")....

Wish I had the buffer underun protection...but will defrag my hardrive (I only have one in the laptop) and slow the sucker down from a whopping 8x to 4x...

Thanks to all for advice so far....You too Bob Frost (a good tip description thanks...)

Steadman
  ----- Original Message ----- 
  From: Moreno Polloni 
  To: DigitalBlackandWhiteThePrint@yahoogroups.com 
  Sent: Wednesday, January 30, 2002 3:10 PM
  Subject: Re: [Digital BW] Image Burning: Buffer Underrun Reason/technique?


  > The solutions are various: buying a CD writer with a bigger memory buffer,
  > using a faster hard disk, using a slower write speed, etc, etc,

  Most of the newer CD Burners incorporate some sort of buffer underrun
  protection built into the hardware, making ruined disks a thing of the past.



        Yahoo! Groups Sponsor 
              ADVERTISEMENT
             
       
       

  Please visit the Group Homepage to check the Files, Bookmarks, Polls and other resources as they are often being updated. The page is at:

  http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint

  Please follow these basic guidelines:
  - Include your full name with your message.
  - Include the address of your website, if you have one.
  - As threads develop, trim off excess portions of earlier messages to keep them short.
  - As the topic of a thread changes remember to change the subject header.
  - Good manners are required at all time. No personal attacks or "flames."
  - Complete your Yahoo profile.
  - Before posting a question, search the message archives and the various resources on the homepage. 




  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 



[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.