Re: Linux, ISOFS, multi-extent files: what's the status?

2010-01-19 Thread Thomas Schmitt
Hi, Giulio Orsero wrote: Isn't the read-ahead thing solved with padding? ie mkisofs adds 150k by default since some time, and when burning I've always used 1MB of padding (ie cdrecord's padsize=512s), just to be safe. I could not reproduce the bug with anything else but CD TAO tracks. Never

Re: Linux, ISOFS, multi-extent files: what's the status?

2010-01-19 Thread Joerg Schilling
Thomas Schmitt scdbac...@gmx.net wrote: I could not reproduce the bug with anything else but CD TAO tracks. Never with CD SAO, never with DVD. The reason for the TAO problem is known: Two non-data sectors at the end of the announced track size. A simple remedy is not to read the last two

Re: Linux, ISOFS, multi-extent files: what's the status?

2010-01-19 Thread Thomas Schmitt
Hi, Joerg Schilling wrote: There are known writers that write up to 15 run out sectors in TAO mode. Then a cautious program should approach the last 15 sectors separately and be ready to tolerate failure. This would still not hamper read performance with the main part of the image. Have a

Daha sağlıklı hava ister misiniz?

2010-01-19 Thread Havatemizlemesistemleri.com
Yeni Sayfa 2 ANA SAYFA HAKKIMIZDA TEKNİK SERVİS İNSAN KAYNAKLARI HABERLER