DISCLAIMER
This FAQ is presented "as is" and the views expressed in it are those of the author and are not necessarily endorsed by The CD-Info Company Please direct any comments, corrections or suggestions to Greg Volk, the FAQ's author.
Note from the publisher (posted on 28 Oct 2000):
Do you currently own a Philips CDD2000 or CDD2600, or a Hewlett-Packard HP420 or HP6020 CD Recorder? If so, you should read this notice about a Class Action Settlement. Thanks to Mike Hoffberg for this link.
Version 1.7 (11/1/96)
Sections:
(Note: If you have contributed something to this FAQ, but do not see your name listed, please mail the current FAQ maintainer with your name, email address, and which question(s) you contributed to.)
While this setup does work quite well for 99% of what I burn, I have run into one underrun problem when I was burning a CD that would have contained 630mb spread over 11,000+ files. The CD did not finish, and I was left with a half written CD, and an underrun error. To remedy this, I dropped down to single speed burning, for this one disc, and it worked just fine. The point I'm trying to make, is that good, fast IDE drives (such as the WD31600A) are good to burn from unless you have a truly massive amount of small files. I still burn stuff at 2x, however when I have more than 7,000 files to burn onto one CD, I drop down to single speed just to be safe.
I imagine that the solution to this would be to go to some sort of SCSI drive, however I do not have the money for this. Another possible solution would be to build an image of all the data that I wished to burn, and then burn it from the image. I lack the extra drive space to do this, so it is not plausible. Yet another solution that might eliminate the 11,000 file underrun problem would be to upgrade my PC to something quicker than a 486-66.
Additionally, Deirdré Straughan 74431.2004@compuserve.com had the following to add:
A: The answer to these questions, and more regarding hard drives for high performance demand audio/visual/data use can be found in the following article by Bertel Schmitt bschmitt@panix.com.
Facts and Myths of AV Tuning
By Bertel Schmitt bschmitt@panix.com
Drive Your Hard drive Harder
used with permissionHard drives have been blamed for just about any ill in the digital audio & video editing world. If frames drop or audio flakes out, the stock answer of any harried tech support person is "it must be your hard drive."
Users on the other hand cant understand why they have just shelled out $$$ for a super fast HD that supposedly shovels 7 MB/sec, and all they can capture is 1.8 Mb/sec (if they are wearing striped socks and the moon-phase is a zero crossing).
The correct answer is a long one. It involves looking at all phases of the capture chain, at bus & CPU saturation, at PCI chipset designs, at bursting, at system stalls, even at memory access. Audio and video is a steady stream, but PCs are not configured to handle streams well. If anything goes wrong at any point of the capture chain, a data stall occurs and frames drop.
Instead of looking at the big picture, blaming the poor hard drive became en vogue. The biggest bugaboo and whipping post is the dreaded thermal recalibration, tcal for short. If someone goes online and says "I captured for 10 seconds and my frames drop," you can be sure that someone answers: "You are the victim of the heinous thermal recalibration. Go out and buy yourself an AV disk."
Some drive manufacturers quickly capitalized on this. "AV Drives" became the gold plated MonsterCables of the digital world. People happily pay $100 more for the same drive, as long as it has "AV" attached to the part number. In a world of eroding margins, "AV" and "thermal recalibration" became a god-sent to struggling drive manufacturers and system integrators. But do AV Drives really perform wonders as advertised? Have they slain the dreaded tcal? To cite Kris Kristofferson: "Its a walking contradiction, partly truth and partly fiction."
First off, some theory
What is thermal recalibration and why do people say such awful things about it? Run your hard drive for a while and touch it. Its hot. A change in temperature leads to expansion or contraction, in a hard drive, it changes the geometry of the platters. Modern hard drives reserve one dedicated servo surface. On startup, the drive reads the servo tracks. After extended usage or after an error condition, the drive recalibrates. Recalibration takes approximately 40ms per surface, depending on the size of your drive and the number of surfaces, a complete recalibration can take somewhere between 0.2 and 1 second. The bigger the drive, the longer the tcal. During the tcal, nothing is being read or written, so unless other precautions are being taken, the data stream is being interrupted. Until recently, improving the performance and capacity of the drive involved adding more platters and raising the rotational speed. Sadly, adding platters or raising the rotational speed means more heat. The main heat generator in a drive is friction between the platters and the air that surrounds them. More platters, more speed, more heat. That, for instance, was the reason why one never saw 9 Gig Seagate Elite or Micropolis 1991 - - for years the mainstay in AV editing circles - - with 7.200 rpm. They rotate at 5.400 rpm, because, as one engineer told me, "if they would spin any faster, they'd probably melt away."By the same token, the best way to keep your hard drive healthy, wealthy, wise and reasonable free of tcals is to blow a lot of air over it. I have a stack of five Barracuda 4s, one as the system drive, four as a striped set. Uncooled, you could cook with them. A 4" inch fan in front and back keeps them at a moderate temperature. The fans also lengthen their lifespan.
The no tcal-drive
A common myth is that current technology AV drives do not recalibrate. That's baloney, unless you are one of the lucky few who could lay their hands on a drive with embedded servo tracks and magnetoresistive (MR) read heads (MRH). This technology, pioneered by IBM in 1991 (who, as usual, didn't exploit it enough - have you heard much about AV drives by IBM?) is now going mainstream. In the second half of the year, Seagate, Fujitsu, HP et al will ship embedded servo MR drives in quantities, instantly obsoleting this article. MR drives will also increase the data density and hence the data thruput by 60% to 80%. At the same rotational speed of 7.200 rpm, one of these drives will deliver approximately 12 MB/sec instead of the current 6.8 MB/sec.That's why these drives will ship as wide or ultra SCSI drives. More on the matter in the WWW under http://www.seagate.com/new/newtop.shtml.
Micropolis claims that their "hybrid servo system combines the best features of both dedicated and embedded servo system designs and completely eliminates the requirement for periodic T-Cal operations." More by pointing your web browser to http://www.microp.com/AVG.html. Micropolis has implemented this technology in their "Gold" series. Note that they are saying: "completely eliminates the requirement for periodic T-Cal operations." They don't say that they have ditched tcal altogether. In a pure embedded servo design, no recalibration is necessary at all. All tracks contain servo information and each head will be brought automatically to the correct position without any interruptions.
The AV drive.
As we have seen, current technology AV drives do have to tcal eventually. They just do it differently than regular drives. A regular drive does periodic maintenance, or it goes into tcal when it sees any (usually correctable) error requiring a re-read. AV-drives try to hide the recalibration. They perform maintenance while the drive is idle, they interrupt maintenance when the drive gets busy, or they do what's called a "posted tcal:" If a recalibration is scheduled and the drive is busy, the drive logic delays (or posts) the recalibration until an idle period is reached. This is the most important feature of AV drives. Its a feature that's shared by most modern high performance SCSI drives, AV or not. A stock ST15150, a.k.a. Seagate Barracuda 4, does posted tcal as a factory default, just like its more expensive brethren with the "AV" suffix.AV tuning
The grizzled backyard mechanic is used to tuning a car. A hard drive can be tuned within limits. Just like a car can (or, until computers took over, could) be tuned for power or economy. Don't expect too much from tuning (10% on a good day). And as with the car, power carries a price.First, a little background. SCSI drives are better and more powerful than their IDE brethren, because they have a little computer and some memory on the drive itself. The controller card writes data into the memory, issues a command to the on-drive computer and then goes about the rest of its business. The computer on the drive does the rest. The computer on the drive is programmable and it can be directed to change its attitude towards data. That's done by setting variables or flags, which are stored in so-called "Mode Pages."
One of the best known mode page setting is the Write Cache Flag. Most SCSI drives have an on-board cache which ranges from 256K up to 1 Meg and more. On some drives, this cache is strictly for reading data, on most newer drives, the cache can buffer reads and writes. Obviously, in a capture situation, a cached write is better, because the computer simply writes into the cache and doesn't have to wait for the drive to complete the write operation. Most drives are shipped with the write cache disabled. That's because in normal life, more than 90% of all drive operations are reads and therefore the whole cache is dedicated to reads. Some drive manufacturers will also claim that disabling the write cache is safer in case of a power failure, but that's a Red Herring. A power failure during a file write is a ticket to disaster, itty-bitty write cache or not.
There are several utilities floating around that allow the enabling of the write cache. One of the best and painless is the SCSI Explorer by Adaptec, which is part of their EZ-SCSI package. Free with their controllers.
The rest of the AV tuning has been done by the hard drive manufacturers themselves or by "Speed Shops", a.k.a. hard drive integrators.
Their basic strategies are:
- Turn off error correction. Error correction takes time.
- Don't let the drive remap bad blocks. Remapping takes time.
- Don't let the drive retry reads or writes. If it doesn't get it the first time around, don't try again. Its just wasting time.
- Setup the drive with one large cache segment instead of several.
- Adjust the prefetch values, so that the drive prefetches as much as possible. Most AV data are contiguous and a prefetch will most likely succeed.
- Optimize the buffer full and buffer empty ratios.
As you can see, half of the "secret tuning recipe" sacrifices speed for data integrity. The theory behind it is that a flipped bit in a video stream will have much less impact on your well-being than a flipped bit in accounting data. That's why "hot" AV drives should only be used for AV, not as a system drive. But even as an AV drive, fiddling with error correction can be an invitation to disaster. If a bit is flipped in video or audio data, you will hardly hear or see it. But if its flipped in a file pointer, the whole file could be burnt toast.
Do-It-Yourself AV Tuning
The tuning of AV drives used to be a specialized chore for professionals. With reason, because one wrong setting in a mode page can send the whole drive to the scrap pile. Peripheral Test Instruments in Lakewood, CO, has put out Dr. SCSI, a fairly safe application (unless you perform unguided brain surgery in your drives mode pages - which you can), that performs AV tuning with a mouse click. The program is available for DOS, Windows and NT and it costs less than the premium of one AV drive alone. Information can be obtained via 303-763-7488 info@scsitools.com or http://scsitools.com .The manual comes complete with in-depth SCSI theory and ample warnings for the unwashed. Highly recommended.
Besides the fan built into the computer's power supply inside the case, I've got a fan inside that moves more air through the case. My case provided a place to mount this, so I just mounted one.The Fujitsu hard drive M2934QAU I have gets hot and the fan I've added helps this.
Note that the fan on the CPU chip doesn't cool the case. It just keeps the CPU chip cooler by moving the heat away from the CPU, avoiding a hot spot on the chip.
In HP's specs listed in the 4020 installation guide for the CD-writer drive, the maximum operating temperature is shown as 35 degrees C, which is 95 degrees F. This means that if the internal temperature inside your computer's case goes above 95 degrees F, proper operation of the 4020i is not guaranteed. It doesn't mean it will always just stop working. It simply means that HP doesn't suggest operation above that temperature.
I measured the difference in temperature between the inside of my computer's case, and the room, with and without the extra fan I installed turned on. With the extra fan turned off, using just the fan built into the power supply, the difference was 22 degrees F. With the fan on, the difference was 8 deg F.
This means that to not exceed HP's operating temperature of 95 I had to keep the room below 73 deg F without my extra fan, or 87 deg F with my extra fan. Quite a difference.
I haven't tried this experiment with a cooler running hard drive, but I know that other large fast scsi's get hot too. If you've got one of these, there's a chance your internal case temperature is exceeding HP's maximum for the CD-writer unless you've got a supplemental fan.
Comparing this to other equipment, it very well could be that the 4020i's 95 degree requirement is stricter than any other devices in your computer. I note that most ICs (like RAM) for consumer application are rated to 40 deg C, or 104 deg F. My Plextor 8X CD reader is rated to 45 deg C or 113 deg F, for example.
Radio Shack sells a thermometer module 277-123 for about $20, but a fan only costs $10 or $15 bucks, so you might save the expense of measuring by just getting the auxiliary fan which is cheaper! Make sure you've got a place to install and connect it!
Version 1.20 firmware seems to be quite solid. I have burnt over 100 CDs with 4020i drives using this firmware and haven't had any problems. Thus when the 1.25 flash upgrade appeared, I was rather reluctant to upgrade. However I'm told that version 1.20 does not do CD-XA discs correctly, and that 1.25 was the answer to this. Hence my reason to upgrade. I ran the flash upgrade, and it claimed to have flashed just fine. Unfortunately when I would try to execute a CD-Info command on the drive, error strings in error dialog boxes would appear. Per HP's tech support instructions I re-downloaded the 1.25 flash upgrade, and flashed the drive again. Once again, it completed successfully. This time however I was able to use the drive. The CD-Info command worked as it should and everything seemed to be ok. When I tried to burn a CD, errors once again became abundant. CDs would not close correctly, usually soft locking Windows 3.11. I called HP once again, and the support rep told me to download the 1.20 firmware and flash back to it. I did this, and was able to write several CDs successfully after doing so. However, about five CDs later I began getting the error "Calibration Area Full" from the drive, just before it would begin writing. I called HP about this, and after questioning me about what brand of CDs I was using (this error occurred on every blank I tried, HP, Kodak, MEI, Verbatim) the tech decided to send me a new drive. Oddly enough, the new drive has version 1.20 firmware on it, not 1.25.
To summarize:
Jim Watson asked HP what version 1.25 changed, and received the following reply:
Firmware 1.25 improves overall compatibility and enhances performance. It also allows disc at once recording and improves access to video CDs and CD+ discs.03.02 Why does HP require a password to download new and previous firmware versions from their web site? Jim Watson watson@kiss.de posted the following on the comp.publish.cdrom.hardware UseNet news group.Any problems with the drive that were advertised by users like Jeff Arnold have been fixed with 1.25.
I emailed the tech support at HP and apparently this upgrade is only for certain situations text follows:Q. Can you please explain why you have password protected the firmware files?A. Not all users need the 1.25 firmware upgrade. The firmware upgrade programs have been password protected because we need to know who is using them and give special instructions. There will probably not be any more than one more upgrade program in the future. I can offer passwords and filename information via Email.
-- HP SureStore Tech Support.
However, Darin Johnson nvisions@worldnet.att.net had the following to say about his NCR SCSI adapter, DAO (commercial FILE2CD), and the 4020i:
Having read that, it is clear the Advansys card is not entirely at fault, and that the problem only occurs with certain combinations of the 4020i and various SCSI boards.
Furthermore, Russell Thamm russell.thamm@dsto.defence.gov.au had the following to say regarding the 1542 and Target Abort errors:
The point is that I had these problems using an Adaptec AHA-1542 interface card. When I had the HP4020i replaced AND upgrade to the 1.25 firmware, the problem has disappeared (I hope). As far as I can tell, the fault was caused by either a dud unit or the 1.20 firmware.
As for using SCSI controllers other than the 1542CF, I'm looking for others who have done this. If you wouldn't mind typing up your experience with other SCSI controllers and sending them to me, I'd be happy to add it to this document, and give credit. Tim Goldstein sent in two things to watch for when purchasing a host adapter for your 4020i drive:
Rick Adams happypcs@oro.net had the following to say about the 2940UW and 4020i combo:
I have an Adaptec 2940 UW ultra wide, which isn't the same as a 2940 regular. Using the 1.25 firmware I was able to get the HP drive to read correctly when connected to the 2940UW, but I had many CD writing lockups and errors so I now use the HP supplied controller and 1.20 until the HP / Adaptec ultrawide / firmware / whatever / issues are resolved!Rick also points out a configuration problem with the 2940 that can cause buffer underruns.
I did get a buffer underrun once, but since I always write CD's from a freshly formatted partition on my hard drive, I had to dig further to discover that Adaptec's default 20 MB/sec ultra wide transfer rate was pushing my Fujitsu 2934QAW drive too fast and causing SCSI bus error retries. The SCSI bus retry procedure is slow enough to cause the buffer to underrun. Setting the maximum synchronous transfer rate that the 2940 uses to talk to my drive down to 10 MB/sec cured that.
Tim Goldstein sent in the following about other devices on the same chain as the 4020i:
You must be careful when placing the CD-Writer on a SCSI bus with other devices. If there is a possibility that one of the other devices will be accessed during a write, (i.e. a hard drive) it could cause a data delay resulting in a buffer underrun.
If you are using the HP supplied controller from Advansys be advised there are at least 2 revisions of the card. The one I first got was positively identified to produce random read errors when reading from the HP CD. This means that if I used the HP drive to read a CD, I occasionally had corrupted data during reading. Didn't matter if the disk was a silver manufactured CD or a CD writer burnt CD. I was sometimes seeing as many as 10 bytes wrong in one whole disk read, to as few as 1 byte wrong in 30 CD reads. Yes this is a tiny error rate, but there should be absolutely no errors of this sort. This was traced down to be the cause of one CD I burnt that had two wrong bytes on it. That is, since the drive read in some wrong bytes, that's what it wound up writing.J. Robert Sims, III contributed the following:The solution to the read error problem was to swap out the HP supplied controller card. The one that caused the read errors had the following chips: two of IS61C256AH-20J, two of ML6509CD, one of Atmel 16FE-17, one of Advansys ASC900, one of IS93C46-3GR. This board was sent back to HP.
The easiest way to identify if you have the better board which HP sent me is to see if it has LS245 chips on it. If so, you're in luck. That board didn't produce the above mentioned readback errors.
The errors described only happen with particular boards that improperly expect extra lines be driven by the card. Either revision of the board with most motherboards do not have the problem; only the specific combination of the old board with a very small set of motherboards will show the error.
The current version of Easy CD that can be found on HP's web site seems to be solid. I have burnt 100+ CDs with this version, and most have been successful. Of those CDs that did not burn correctly, I have concluded that the source of the problem was hardware related.
What is going on, and what can I do about it? According to the Easy CD error list, available at http://surf.adaptec.com/easycd/ecd95err.html, this error means that the maximum amount of data that can be put on the CD has been exceeded. Remove a few files and try it again. The Max CD size is not dependent on the number of files.
About Buffer Underruns
CD writing is a real-time process which must run constantly at the selected recording speed, without interruptions. The CD recorder's buffer is constantly filled with a reserve of data waiting to be written, so that small slowdowns or interruptions in the flow of data from the computer do not interrupt writingA buffer underrun error means that for some reason the flow of data from hard disk to CD recorder was interrupted long enough for the CD recorder's buffer to be emptied, and writing was halted. If this occurs during an actual write operation rather than a test, your recordable disc may be ruined
Possible Causes of Buffer Underruns
Hard DiskHardware
- "Dumb" thermal recalibration.
- Fragmented hard drive.
- Cluster size at 32kb instead of 16kb.
- Not enough space in temporary directory.
Memory Resident Programs
- Slow source devices.
- Source devices that transfer data in bursts.
- Incorrect recorder controller settings.
- Inability of the devices to sync properly.
- Overall system configuration.
- Computer unable to allow fast enough data transfer.
- Old device drivers.
Networks
- Any program that may activate on its own
- Anti-virus software
- Screen savers
- System agents
- Schedulers
- TSR (terminate and stay resident) software
- Networks
- System sounds
- Animated icons
Files to Be Recorded
- Recording across the network (usually too slow to maintain adequate throughput speed).
- Incoming e-mail or faxes.
- Other people accessing your computer.
- Windows 95
- Modify Virtual Memory Settings (see below).
- If you have more than 16 MB of RAM, disable Auto Insert Notification (see below).
- If you have more than 16 MB of RAM, change the hard drive's Typical Role to Network Server (see below).
Other
- Recording many small files.
- Damaged source files (data loss).
- Trying to record files in use by the system or other applications.
- Copying from a CD that is scratched, dirty, or damaged.
- Recorder malfunction.
Checks / Prevention
- Disable or remove everything in the computer EXCEPT the operating system, the recording software, and the drivers for your source devices.
- Defragment your hard drives at least once a week to prevent files from scattered across the hard drive.
- Do not record across a network. Copy the desired files to your local hard drive.
- Log out of any networks if possible, including Windows for Workgroups and/or Microsoft Network.
- For best results use SCSI 2 source devices.
- Disc to disc copying, requires a SCSI 2, fully ASPI- compliant CD-ROM drive. We recommend at least a 4x. Copying audio requires a source CD-ROM drive which supports digital audio extraction.
- Make sure your hard drive does Smart Thermal Recalibration. (that is, that it won't recalibrate if the CPU is being used).
- Record at a slower speed.
- Write an .ISO image to the hard disk first, if you have enough hard drive space
- In any operating system, always using the newest drivers from your SCSI controller card manufacturer.
- Always set audio to write at 1x.
- Keep the CDs, the recorder, and your source CD-ROM drive free.
- Make sure your SCSI controller card is FULLY ASPI-compliant.
- Do not try to copy empty directories, zero byte files, or files that may be in use by the system at the time.
- More than 10,000 very small files should be written to an .ISO image first or recorded at 1x if possible.
- The temporary directory should always have space free at least twice the size of the largest file you are recording.
- The entire computer, from the motherboard bus to the recorder itself, needs to be configured properly for faster recording and highest maximum sync transfer rate.
- Change the DMA transfer rate for the card being used.
- Try increasing the bus clock speed to 8 MHz if the motherboard allows this.
- With DOS 6.22 or below and a source hard disk 1 gigabyte or larger, partitions should be kept smaller than one gigabyte so that hard disk sector size is 16kb instead of 32kb.
- Try a different hard disk and /or gold recordable disc.
Windows 95 Settings
Virtual Memory (if you have more than 16 MB of RAM)Hard Drive Typical Role (if you have more than 16 MB of RAM)
- Right click on My Computer.
- Select the Performance tab.
- Click on the Virtual Memory button.
If you have:
- 8-bit color, select 16MBs for both the minimum and maximum size
- 16-bit color, select 16MBs for both the minimum and maximum size
- 24-bit color, select 32 MBs for both the minimum and maximum size
- 32-bit color, select 32 MBs for both the minimum and maximum size
Turning Off Auto Insert Notification
- Right click on My Computer.
- Select the Performance tab.
- Click on the File System button.
- Choose the Hard Disk tab.
- Change "Typical Role of this machine" to Network Server. This re-prioritizes the hard drive so that it is given priority over other hardware and software functions
Note: You should do this for every CD unit on your SCSI bus, including the CD recorder itself!
- Right-click the My Computer icon on the desktop.
- Select Properties from the menu. The System Properties dialog box opens.
- Click the Device Manager tab.
- Click the plus sign next to the CD-ROM icon until you see the name of your CD drive. Select it.
- Click on the Properties button. The Properties dialog box for your CD drive will open.
- Click on the Settings tab.
- Deselect "Auto insert notification."
- Restart your system as prompted.
The above contribution from Deirdré Straughan is © 1996 Adaptec, Inc., all rights reserved.
Use a different SCSI cable if one is available. Otherwise switch ends of the current calbe so that the connectors are hooked to the other device. Check for third-party memory managers like QEMM or RamDoubler. These can cause problems Windows 3.x and should not be used in Windows 95.
Rick Adams happypcs@oro.net mentioned the following regarding Internal Controller errors:
Just prior to writing a CD, I power down and restart my computer into Windows 95. Naturally I make sure screen savers are off and my 10B2 network card is connected only to a 50 ohm terminator. But what really seems to have gotten rid of the "internal controller error" problem was the procedure of first turning the computer off and on, then not doing any other CD reading or starting any other tasks before writing the CD. It seems something isn't being properly reset unless the power is turned off.Another possible source of "Internal Controller" errors is heat. See 02.04Q for more information about max operating temperatures.
Use the CFGISA program to change the controller's DMA Speed to 3. Also try changing the DMA channel and IRQ. Frequently when a session fails, it will disappear when you add more data to the CD later.
I (gvolk) have also found that sometimes Jeff Arnold's freeware program FINALIZE can help in correctly closing an errored CD.
The c4324hlp.vxd driver is not installed in the \windows\system\iosubsys directory. Get the latest version of the driver. The driver cdr4vsd.vxd from Adaptec is a newer substitute for c4324hlp.vxd.
Drivers, software, and firmware upgrades are available from:
The CD-ROM FAQ can be found at:
More information about the bundled software (Easy CD) can be found at the following web site:
Some users have reported jerky video playback on a CD-R drive.
The MTBF on CD-R units tends to be low, so it may be wise to use a different drive for general use.
Since the drive's original release, HP has released new (non-beta) firmware, and Adaptec Software Products Group has released new (non-beta) software. This has certainly had the effect of silencing many of the critics of the 4020i, but many still remain. Many of these critics are having trouble because they do not have the necessary hardware that is required to write a CD, while others correctly cite existing software/firmware bugs. Having said that, I do believe that the HP SureStore 4020i CDR drive is equally as good as other CDR drives in its price range.
In response to this question, Deirdré Straughan 74431.2004@compuserve.com makes the following point:
Real life on the Internet is that most people come to forums like this one to seek help and/or complain. Not many bother to pop in to say "I just love this recorder!" So you will always see a large number of people beating up the HP (and other recorders) online. But please keep in mind that they are only a percentage of the people who are actually using the recorder -- the contented majority is largely invisible.
I got tired of people pirating my software, so when the program detects that it has been hacked, it randomly writes zeros into the data being written to the blank disc.
The pirates (a group known as X-FORCE) that hacked the protection on my software aren't too bright. They didn't even bother to test the software before distributing it around the net.
I finally got my revenge :-) :-)
To get around the Jitter problem, you can do one of two things.
If you are wanting to use your IDE/EIDE CD-ROM drive for Digital Audio Extraction, check out the following web page: http://www.tardis.ed.ac.uk/~psyche/pc/cdrom/CDDA.html
The following is a list of items that you may want to run through before burning a CD as they may have an impact on CD burning.
| Version Number | Date | Main reason(s) for new version. |
| 1.0 | 5/31/96 | Initial distribution. |
| 1.1 | 6/2/96 | Applied standard Internet FAQ
format. Added information regarding AV hard disk drives, and Ethernet as a data source. |
| 1.2 | 6/6/96 | Added contributions regarding firmware, swapping of left and right audio channels, possible solutions to buffer underruns. |
| 1.3 | 6/17/96 | Added info regarding Digital Audio Extraction, solution to popping noises when using the Goldenhawk DAO software, problems related to Advanced Power Management (APM), closing discs, and "Internal Controller Error" message. Added URL of Easy CD Error Codes. |
| 1.4 | 7/1/96 | Added Rick Adams' contribs regarding
2940 & 4020i combo, and possible
"Internal Controller Error" remedy. Added URL of software for DAE from IDE/EIDE CDRom drives. Added info about heat related problems, added Pre-Burn checklist, corrected Easy CD Error 39-00-00-00 answer, added URL of "Common Easy CD Errors." |
| 1.5 | 9/1/96 | Revised answer to 05.07Q. Added 05.12 Added 04.07 Added 06.11 Added 06.12 Revised answer to 06.05 |
| 1.6 | 10/1/96 | Added Adaptec copyright notice to
contribs section. Updated 04.06 Deleted 04.07 Updated 05.12 Added 05.13 |
| 1.7 | 11/1/96 | Revised 03.01 Answer. Maintainer's (gvolk's) address has changed to gvolk@umr.edu. |
Home | Applications | Bibliography | CD-Lite
History | Industry | Sponsors | Technology
FAQ Copyright 1996 Greg Volk
HTML Copyright 1996 The CD-Info Company
990126