View Single Post
  #18   Report Post  
Posted to sci.electronics.repair
mike[_12_] mike[_12_] is offline
external usenet poster
 
Posts: 129
Default DVD burner screwed by 2nd burner added to system



wrote:

Then I tried to burn one with the LG burner and it made a coaster(you
can see on the disc where it stopped burning about a third of the way
through.


the 'puter's an older P4 system with Ex-Pee on it - anyone got any
ideas?


ASPI layer driver trouble?


That looks like a good direction to look into some, thanks for the
link. At the moment I'm able to use the burner though it still
refuses to properly see dvd-r's that have video files on them - it
classifies them as dvd-r's with 0 bytes of capacity, yet it'll read a
dvd-r that has music files on it; and, it's buned 5 videos so far it
just can't read them when it's done, nor can it play them (though they
work ok in a dvd player).

I think to establish whether the prob lies with the drive, or the
software, I'll try putting it in another xp system and see what
happens there, rather than reload any app or aspi; also dragging my
feet on doing a firmware update, since they usually have dire warnings
that you may kill your piece of equipment...



http://www.afterdawn.com/guides/archive/aspisetup.cfm

Are both optical drives on the same cable, and if so, are both set for CS (Cable Select)? What if you reverse the positions of the two drives?


Not any more, now I've got the LG on the secondary channel by itself
and put the Lite-On in another machine.
but for now I'm trying to get caught up on achiiving a bunch of video
files, if the drive will continue to work.

I might try uninstalling both drives in the Device Manager and uninstall any third party UDMA driver software. Back in the Windows 98 days, when VIA was coming out with a new driver package every few weeks, one version of their UDMA driver would make file copying really slow, and I mean slower than floppy I/O, if both disk drives were on the same cable.


One other symptom it shows when burning something in Nero is that the
speed for verifying the data after burning took a major hit, where as
it used to verify at speeds from3X up to about 8X, I had to quit
having it verify because it dropped down to 300 or so Kbits /sec. -
( it would record at its usual speed, though.

Thanks for the pointers,
Mike