|
|
|
Error Burning with External DVD-Writer and USB2 (SCSI command aborted)
|
|
|
camstuf
Suspended permanently
|
1. February 2005 @ 01:10 |
Link to this message
|
|
This thread is so long, what is the main problem/solution?
To use with my emachines laptop(OS: XP),
I just bought an external DVD burner and alcohol 120% will not see a blank disc;
Nero seems ok to copy a burnt DVD.
As far as VOB/TS files: still testing.
Emachines: T2865/AMD Athlon? XP 2800+ Processor (2.083 GHz)
NVIDIA® nForce?2/160 GB HDD/512 MB DDR (PC 2700)
DVD +/- RW Drive CD-ROM Drive; 3.5" 1.44MB FDD;
8-in-1 Media Reader/ This message has been edited since posting. Last time this message was edited on 1. February 2005 @ 01:11
|
|
Advertisement
|
 |
|
|
|
nklz
Newbie
|
1. February 2005 @ 02:11 |
Link to this message
|
|
I think the problem lies somewhere between usb drivers for controlling the burner through USB and simply not-too-great chipsets.
Actually the main problem is, that it isn´t really possible to pinpoint the problem excactly, and hence the solution isn´t right around the corner either.
I´m using an USB enclosure, because then I can put my computer in the kitchen, put an usb and monitor cable through the wall, and thereby eliminate the noise from my box completely.
|
|
laddyboy
AfterDawn Addict
|
1. February 2005 @ 04:21 |
Link to this message
|
|
When I'm using a laptop I need both an external burner and an external hard drive. The internal burners for laptops are expensive, slow, and fragile.
|
|
desof
Newbie
|
1. February 2005 @ 06:53 |
Link to this message
|
|
Hi All,
I think we have to be caution on each statement that is in this threat.
It is very easy NOT to associate apple to apple.
It would be interesting to gather the information provided and verify they are all related to the same issue.
To be honest, it is quite difficult to find a common denominator as the posts aren't that precise.
One person talks about an issue, then another one brings up a slightly differnt one.
You think it is all related, but the truth is it can be totally different.
I know people are frustrated as I was and it might explain the reason why.
The main problem seen was: SCSI command aborted with External USB2 DVD-writer.
From a previous post, I explained that I encountered this issue with external Plextor burner.
For the people who have internal DVD burner, is the problem related to "SCSI command aborted", YES OR NO?
If not, it is not the proper threat to use.
Is yes, what type of internal dvd burner (SCSI / IDE)?
What is interesting to know is: (trying to put a template so we can easily compare)
Do you get the SCSI command aborted error message?
is there additional error message displayed?
OS type?
Service pack?
DVD burner model?
Firmware version?
Internal/external model?
(it should be external as per the title of this post)
Type and model of enclosure?
Is your DVD-writer the only device connected to USB port?
Confirm that you're using USB2.0 (not USB1.)?
Do you have latest driver/patch for your OS/DVD burner?
Driver version?
DVD-writer software and version that you use?
Has the burning process ever worked fine?
Has the problem recently occurred?
(what change since the last time it used to work?)
Is it an intermittent issue?
Rate of occurrence?
Have you tried different DVD writer software?
Have you tried different brands for your blank DVDs?
which model/type do you use?
Have you tried different writing speed capabilities?
Is there specific settings enabled/disabled? (such as DVD compatibility).
Have you tried to change to different USB port?
Have you tried to change USB cable?
Have you tried different USB enclosure?
Have you tried to use different protocol such as Firewire / IDE?
What solved the problem in your case?
In my case, I simply connected the DVDburner to IDE bus as internal device and problem was gone.
No other change was made.
Yeah, my job is providing customer support for VOIP products that my company sells.
So I have good background about debugging issues.
desof
|
|
ccampbell
Senior Member
|
1. February 2005 @ 08:24 |
Link to this message
|
Hi Tubtyke,
You make valid points.
But first off, you need to know that 'SCSI Command Errors' have been around since the beging in 1992 when Recorders first came out. Hence the reason the error still says 'SCSI' when most recorders are now IDE. When recorders first came out, they were all IDE, now 99.9% of them are IDE, yet the MMC command set has not changed the erroor message. :-)
And those who have Internal drives, and get this same error message, are running into different problems, and mostly stem from old IDE Drivers, DMA settings, Driver conflicts, and even old versions of Recording softwares that may have a bug.
As for pointing our fingers at Hardware, we do so because from our testing and debugging efforts we have not been able to find a solution. We did create a patch, that does help some users. But we did not change any commands, simply allowed our software to ignore the first few times the error message comes up and to reissue the command in the hopes of a communication eventually becomes estabilished. It will still eventually time out and generate the error message if no communication is established, so it's not a fix. But this lends credence to the fact it is more likely to be a hardware error. Plus, this occurs to other Recording Software programs, not just Nero, or CD Clone, or Roxio, etc. One may work for a while where another failed, but eventually has the same issue. Users have Tried clean systems, so that rules out driver conflicts. And all the Recording software programs and recorders follow the MMC Command set, so we are all using the same commands, though maybe implementing them just slightly differently.
But can we truly say with 100% surity that it's hardware. No, we can not. But we do suspect it is based on these results, and many others posted on this forum. We can say that it's 90% likely to be hardware related, and still a 10% chance of it being software.
But from a software side, we have run out of options to try and resolve this. So the ball needs to be picked up by the hardware end now and see where they can run with it.
Regards,
Craig
Nero Inc
USA
|
|
Judgeless
Newbie
|
3. February 2005 @ 05:09 |
Link to this message
|
|
The SCSI errors exist because the apps that interface with CD/DVD burners use an ASPI (Advanced SCSI Programming Interface) to burn media. Results like (SCSI_ABORTED) or (SCSI ERR) means that something failed. The next few lines in the log will tell you what happen. Example (SCSI_HASTAT_REQUEST_SENSE_FAILD) and (SCSI_TASTATUS_CHKCOND). The lines after the (SCSI_ABORTED) or (SCSI ERR) can help explain the problem. With my config I found that the reason I received the (SCSI_HASTAT_REQUEST_SENSE_FAILD) error was because it was not supported by the ALI M5621 chip set. The error went away when I used Firewire, IDE or a different USB 2.0 controller. The reason I received the (SCSI_TASTATUS_CHKCOND) error was because my DVD burner did not support the old media I was trying to use. I tried the same media and drive on IDE and Firewire and still received the error. Different media worked fine.
Sean
|
|
tubetyke
Newbie
|
3. February 2005 @ 08:20 |
Link to this message
|
Judgeless: Thanx for the detailed info. However, in many cases reported here, myself included--nothing changed. My burner (Sony DRU-500A) was burning fine, mostly DVD-R.
I was using DVD Shrink & Decrytper and no problems until shortly after I installed SP2, updated DVD Shrink and later updated Nero.
What you describe seems like a problem that would have existed all along with incompatible drivers, etc.
Many of us on this thread were burning fine and suddenly started having these errors and aborted burn sessions--that is what is so puzzling.
Many users on this thread have external burners (mine is internal) and there are many different brands of burners as well as a variety of OS. It seems from this evidence, one could deduce what the problem is, but thus far it has eluded us.
Some with external burner enclosures reported progress after changing the enclosure, or switching from USB to FireWire.
Craig from Nero has graciously given us his time and knowledge, but he thinks the evidence points to a hardware problem, rather than software.
I don't agree with him, since there are so many brands of hardware all coming down with the same problem. I think it must lie in the software, or the drivers and that some sort of updating has triggered a change that made burners that worked, turn into burners that did not. I suspect MicroSoft, but that's an easy target.
Always happy to hear other points of view. I am not a techie, by any means.
Thanks to you and all the rest for the input on this vexing problem.
Tubetyke
|
|
jrkn
Junior Member
|
4. February 2005 @ 05:16 |
Link to this message
|
|
i've got a retail external burner, a BTC 1108UI.
dvd+r goes okay but i can't burn -r becouse then i get the error. However, i've got a win XP install with SP1 intergrated, but i don't have SP2 installed.
I think the main problem are the USB drivers in windows, becouse i'd read a reply from someone who said it did work in linux but not in windows.
|
|
Judgeless
Newbie
|
4. February 2005 @ 11:34 |
Link to this message
|
Quote:
dvd+r goes okay but i can't burn -r becouse then i get the error
What is the error after the (SCSI_ABORTED) or (SCSI ERR)?
If it?s a (SCSI_TASTATUS_CHKCOND) it could mean that the media you?re burning is not supported by your drive. That error will occur with or with out USB and in Windows or Linux.
Sean
|
|
dkmedia
Newbie
|
5. February 2005 @ 05:03 |
Link to this message
|
I too have been having this problem and have been banging my had against the wall because of it. I am seriously considering building a cheap desktop just to make things easier. I started having this problem when I replaced my burner (it died on me) and enclosure (it seemed a bit flaky). the onyl way I have found to burn -r with any degree of success is by using NTI CD and DVD maker 7, and this only works about 65% of the time. Like others, I dont seem to have any trouble with +r media. I have winxp sp2 with all the patches, the latest shrink and decrypter. I started to notice these problems because my shrink/decrypter was very slow using the external drive (has anyone else had this? maybe it is related?) So anwyays I tried gear dvd (that one works, but goes mega slow, probably .5x if I had to guess, but seems like it will work for me 100% of the time) I tried CloneDVD (that didnt even come close to working) and of course Nero deson't hack it anymore. NTI has worked for me, but sometimes it decides to give me a buffer underrun error. I dont think that should be a problem since I have 512mb, a generous swap file and my hdd buffer is 16mb (I know the burner only has 2mb, but that should be enough). I would really like a chance to try roxio, but there is no demo and I don't feel like spending $70 on something that won't work. If NTI keeps working until my demo expires, then I will probably stick with that. I can also safely say that this would not happen under linux unless if its a media error, but moving to linux may be unreasonable (and its a pain to rip under it). I can't really move to linux because I need hpotoshop, flash and vb6. Anyways, I guess thats enough rambling, I hope someone figures this out!
-Rodolfo
www.dkmedia.net
|
|
jrkn
Junior Member
|
5. February 2005 @ 09:09 |
Link to this message
|
Quote:
dvd+r goes okay but i can't burn -r becouse then i get the error
What is the error after the (SCSI_ABORTED) or (SCSI ERR)?
If it?s a (SCSI_TASTATUS_CHKCOND) it could mean that the media you?re burning is not supported by your drive. That error will occur with or with out USB and in Windows or Linux.
i only get the SCSI_ABORTED message, and can burn dvd-r at usb1.1, but it takes ages...
|
|
shaowniq
Newbie
|
7. February 2005 @ 00:32 |
Link to this message
|
hi,
i've notebook with i855G chipset, ICH4 with USB2 onboard controller, have connected LG LGSA-4163B DVDRW with external Canyon enclosure (ALI chipset). First problem was SCSI Command Aborted, i fixed it with Nero 6.6.0.1 and patched mmc.dll file, then i get the Reset Occured error. I fixed it through disabling Buffer underrun protection. I tested only two medias, certified for 8X writing, all was ok, DVDs are readable and everything is ok. I fixed writing with Nero, i'm happy, but my question is: how can I fix this with CLONEDVD3 or Elby DloneDVD 2.X ? Please help me. And thanx for mmc.dll, it makes miracles :-)
|
|
fgjoao
Newbie
|
7. February 2005 @ 18:09 |
Link to this message
|
I have used Nero for 3 years and had no problems with my Pentium 4 Desktop (Internal LG DVD Burner). Recently I bought a Toshiba Satellite Notebook and a External Case (ViPower USB 2.0) for my DVD Burner and guess what: Nero doesn't work anymore. I've tried everything suggested in this forum and nothing worked (disabling IMAPI Services, Disabling High Compatibility Mode in Nero, ETC.). Yesterday, I downloaded and installed CopyToDVD 3.0.45 DEMO and everything is working fine now. Maybe it's because CopyToDVD uses the Patin-Couffin Drivers...
As you can see, I´m always burning...
|
|
fgjoao
Newbie
|
7. February 2005 @ 18:13 |
Link to this message
|
|
Oh, and I have tested both softwares (Nero and CopyToDVD) with various media types and brand": Princo (DVD-R), LG (DVD-R), TDK (DVD+R), Maxell (DVD-RAM) and Master-G (DVD+RW)...
As you can see, I´m always burning...
|
|
tubetyke
Newbie
|
7. February 2005 @ 18:49 |
Link to this message
|
Just an addendum to my problems--first a recap--I'm using 3.06G P4 CPU, w/ 1 G RAM and Sony DRU-500a internal burner--OS is XP Pro w/ SP2 and latest version of Nero.
My media is Sony DVD-R--so I don't think it is the media in my case.
Again my eror is: "Device error, Sense code (30C08)
DVD Error 199688"
I am able to burn to DVD-R, if I use Decrypter to make an ISO file first. Can't use DVD Shrink anymore.
Many of you are using external burners, but are getting the same error code as myself.
Looks like the hardware-software blame game continues, w/ neither side stepping up to the plate. I'd be willing to blame Windows, but some here have reporter different OS. Vexing and puzzling to say the least.
Many thanx to all who have contributed and are active in the search for a cure. One day!
Best wishes to all--Tubetyke
|
|
ONuetron
Newbie
|
8. February 2005 @ 21:07 |
Link to this message
|
I was drawn to this thread as I googled the errors I was having:
SCSI_TASTATUS_CHKCOND
SCSI Comman aborted.
7 hours later I figured it out.
The latest Nvidia driver conflicts with the Aspi layer.
I simply did a rollback on the Nvidia driver to the settings it came with from my installation disk and bam, all working perfectly.
This will not be the same for everyone but I guarantee it is not hardware but in fact a software conflict somewhere.
I was happily burning away for months before I started getting these errors so it can`t be put down to any one event which was so frustrating. Not only would Nero not work but ANY burning software!
Anyway it sorted my computer so give it a try.
Cheers
|
|
jrkn
Junior Member
|
9. February 2005 @ 09:48 |
Link to this message
|
|
do you have a Nforce chipset?
i've got a intel chipset, i think it's the usb support within the drivers wich is crappy.
|
|
nklz
Newbie
|
9. February 2005 @ 10:08 |
Link to this message
|
|
ONuetron: that doesnt sound all that farfetched. Could you be more specific, as to what kind of Nvidia drivers are giving you problems, and what kind of hardware you have (nforce chipset or geforce graphics).
Only thing is, I have an ATI based card, but the driver has proven to conflict with other programs, so the fact that my enclosure is working all of a sudden, could be because I am using upgraded graphic drivers - who knows.
This message has been edited since posting. Last time this message was edited on 9. February 2005 @ 11:13
|
|
ONuetron
Newbie
|
9. February 2005 @ 11:11 |
Link to this message
|
|
I have a gforce graphics set and the nvidia drivers causing me problems were version 66.93 from here:
h**p://www.nvidia.com/object/winxp_2k_66.93
driver conflict for sure.
|
|
FrankLdw
Newbie
|
14. February 2005 @ 03:55 |
Link to this message
|
I did have this problem too with my SWEEX external USB2.0 case with a Plextor PX-716A/TLA0203 or PX-712A-model in it.
The error did always show up when the drive tried to write the first block on the disc. In a few cases the recording did start correctly. In this case the writingprocedure would finnish without further errors.
The error occured randomly with Nero 6, Roxio Creator Classic 7, Pinnacle Instant Copy 8 etc.
When I didn't use a RW-type of disc they ended as toast in case the error showed up.
I also have a Freecom Classic external USB-2 Writer (With a NEC-ND2500 in it). With this hardware I
didn't have any problems in the past months and I decieded to place the Plextor PX-716A in the Freecom-housing and the NEC ND2500 in the SWEEX housing.
The Plextor works fine for days now and the NEC-drive
seems to function well in the SWEEX-housing (but I've
not tested the NEC much times yet).
So, I think the combination USB to IDE-converter <-> DVD-Rewriter is the problem and NOT the software-configuration of your PC.
If anything changes I will report that on this forum.
Regards,
Frank
The Netherlands
|
Moderator
|
14. February 2005 @ 10:38 |
Link to this message
|
|
good grief, ive only read the last page so far and already we have disagreement as to whether it's hardware or software. i did notice the fingers pointing at nvidia drivers. my old pc (whence i first got into dvd burning) had nvidia, and had no end of problems with burning. In my case AND I STRESS ONLY IN MY CASE, my problems were solved by decent media. I ditched the old pc as it was actually faulty, maybe it gave up in end cus i bashed it after having so much grief with it :)
bought a new pc (old pc had been rebuilt from scratch cupl of times btw prior to going in bin). installed EXACTLY same burning software, O/S etc as best as can be exact on different pc. Went from crappy usb2 pc card in crappy pc to non-nvidia pc. BUT i think my main problem was duff media, went from crap bulkpaq, to verbatim. However i still think underruns (yes you can have underruns even on burnproof drives) coupled with crappy media was MY cause of problems as a lot of my films did actually work ok.
i did it again, i missed the obvious - forgot to say i was using my dr700a in a usb2 enclosure on old p3 500 pc. Now that same sony is internal to my new pc (but tested it fine in said enclosure on a fast P4 machine). However the usb enc. is still in use wih a
n LG cd burner, it does nearly ALL the ripping for all my movies. Guess what all the rips are fine on this , as are the burns on the sony.
Phew im out of breath
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***This message has been edited since posting. Last time this message was edited on 14. February 2005 @ 11:15
|
Moderator
|
15. February 2005 @ 22:49 |
Link to this message
|
I've got as far as page 16 (my poor eyes). Don't think i've noticed anyone in this sorry tale using Nero 6.6.0.0 (i do). (i've had no probs with my usb enclosures, whether used with dvd burner, dvd reader, or my hard drive (can only use one enclosure at once as they're all Master's)..
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***
|
|
fgjoao
Newbie
|
16. February 2005 @ 05:28 |
Link to this message
|
I had problems with Nero 6.6.0.6 DEMO. I don't think this is a software issue; maybe the ASPI layer is the problem with USB 2.0 and DVD Burners; I came to this conclusion after using CopyToDVD (uses Patin-Couffin driver / layer) and getting no more errors. It's good to say that I've disabled Windows XP IMAPI Services and I always close all resident software and unplug all other USB devices before burning...
As you can see, I´m always burning...
|
Moderator
|
16. February 2005 @ 05:33 |
Link to this message
|
|
Sure, not implying that 6.6.0.0 is exempt. I use Mandrake Linux a fair bit at work, but don't use it at home anymore, i've seen a few threads saying Linux isn't affected but i haven't got the patience with Linux half the time. I much prefer my Solaris/Veritas anyday. Anyway, I don't have any problems myself (yet) but am closely following this thread as it seems a helluva few peepl are, and am intrigued as to what the outcome will be.
Rich
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***
|
|
Advertisement
|
|
|
|
ypelchat
Newbie
|
16. February 2005 @ 09:49 |
Link to this message
|
|
Hello;
I have the exact same problem as LeeM2. I recently bought two new GSA-4163B burners, and put them in an external USB2 enclosure. Both my machines also have GSA-4081B burners installed internally, and they were burning DVD's just fine, until i plugged the newly purchased USB2 burners to the computers. After that, I was unable to burn -R anymore, regardless of the brand and speed used. My 4081B and 4163B would burn -R coasters, one after another. In fact, my 4081B are useless now, and the 4163B will only burn +R media. Something must be wrong with the USB2 drivers that installed when I plugged the new USB2 4163B. I get constant ATAPI errors, and most burn fail on or before reaching the 20% mark. The +R media burning is working just fine on the 4163B, but not on the 4081B. I tried many type of -R, and all failed. Slowing the speed did not help either. I have come to believe that plugging a USB2 DVD burner my computers caused WIndows driver error. The same USB2 enclosure work flawlessly with a HD.
|
|
