Burn CD - Error 2122 - Please Help!

Question

Updated drivers for CDROM, Graphics card, etc. all this evening. No luck. I get an error out right after it checks the files to be burned - Unknown Error 2122, and it ejects the blank CD.
Stats below...thanks for any advice.
Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
NVIDIA AWRDACPI
iTunes 6.0.3.5
CD Driver 2.0.4.3
CD Driver DLL 2.0.3.2
LowerFilters: Pfc (2.5.0.204),
UpperFilters: GEARAspiWDM (2.0.4.3),
Video Driver: RADEON X800 Series \RADEON X800 Series
IDE\DiskMaxtor6B120M0_________________________BANC19J0, Bus Type ATA, Bus Address [2,0]
IDE\DiskMaxtor6Y080L0_________________________YAR41BW0, Bus Type ATA, Bus Address [2,0]
IDE\CdRomAOPENDUW1608/ARR_______________________A110___, Bus Type ATA, Bus Address [0,0]
If you have multiple drives on the same IDE or SCSI bus, these drives may interfere with each other.
Some computers need an update to the ATA or IDE bus driver, or Intel chipset. If iTunes has problems recognizing CDs or hanging or crashing while importing or burning CDs, check the support site for the manufacturer of your computer or motherboard.
Current user is administrator.
D: AOPEN DUW1608/ARR, Rev A110
Media in drive is blank.
Get drive speed succeeded.
The drive CDRW speeds are: 0.
The drive DVDR speeds are: 0.
The drive DVDRW speeds are: 0.
The last failed audio CD burn had error code 2122(0x0000084a). It happened on drive D: AOPEN DUW1608/ARR on CDR media at speed 0X.

Answer 1

Many of us have posted and experimented and tried everything mentioned here all to no avail in regards to the 2122 error code. And don't let anyone tell you it's YOUR problem--it's not the AOpen drive that's bad-it's that iTunes is NOT working with or doesn't recognize the AOpen burners.... I've gotten a few replies from Apple people and they even say the same thing....
personally I think it's really SAD AND STUPID that this big company can come up with all sorts of new products, pods, nanos etc and yet can't come back and fix the programs for the people that already bought their original products!!!!
HOW HARD can it be to fix a little thing like this??? I don't honestly know -I am not a programmer--but if this many people have complained, wouldn't it be nice if someone would just ADRESS THE PROBLEM??? And then so many of us wouldn't be sitting here fuming, hoping each time they come out with a new upgrade that MAYBE this time it'll work---rather than to be disappointed over and over again and see the same fricking 2122 error....Don't you think fixing something first would be nice instead of just making more newer faster smaller things??