hi guys , i have a toshiba A20 sattelite laptop
with a dvd-rom cd-rw burner that over the last two weeks no longer seems to want to burn anything ontoa cdrw properly
im not totally computer savy but i also dont want to fork out 120 Aust for them just to have a look at it

it seems to be burning perfectly onto regular cd's just not rw's anymore

im using nero 6 and it seems to be fine
the music data shows as being on the cd but it just wont play
and when it does its stops and starts like it really jittery
and play with alot of cracking and hissing on my stanton cd decks which are mp3 compatble players , i have tried verbatim rw's tdk and a few others
and the same result all the time
the dvd rom cd burner is a SD-R2412 toshiba dvd rom version
if anyone could help me i would appreciate it emmensly:confused:

thanks

Why are you using rw's to write to...why not just -r's or +r's. "Skipping" (jumping or sticking) will happen for many reasons but as a rule of thumb try turning off all running programs when you burn. I.E. screensaver, Firewall < usually the worst. On the cracking and hissing, mp3 is a poor format to play loud, so to get the best results make sure the "source" copy is good - if the source copy has hissing on it then so will the copy. There are prog's out there which will reduce this problem but im afraid I dont have any links to them. Try your search engine. Last "the music data shows as being on the cd but it just wont play" < Make sure your player will read RW's ....sounds silly I know but a lot of stand alone players will not. Good luck.
Found this also...it may help you. " The problem is the version of a DLL file used by Nero 7 for decoding mp3 files when it burns them, called "mp3PRO.dll". It is located in C:\Program Files\Common Files\Ahead\Audio Plugins. For some reason, on SOME computers (maybe a hardware conflict) the version of this file with Nero 7 is problematic and produces gaps in the data.

The solution is to obtain an older version from a Nero 6 installation and replace the newer version. Watch out though, there are several version of the DLL file which cause this problem, there are some sites looking into this if you check "