Could have been - but they both worked together ( fastcopy etc) with Pinnacle, and after installing a retail version of Nero as the drives worked with their own version of the software, and failed at the Lead-in stage that was, to me, indicative of a failure to properly execute the write process I could read old CD and DVD's from them both OK ( simultaneously at that) - just not write to either with the OEM version that was supplied with the other, or if both were powered at the same times.
No problem with the media CD or DVD, RW or R, + or - And - as it all worked once I chucked the OEM Nero - that's what I blame. And - yes Jumpers and CS conflict as well as extra IDE 'Raid' connections on the MB can cause real fun - such as drives not being properly recognised on the Raid connections until they had had a partition created on them elsewhere Thanks for the thoughts and extra information JimB. ----- Original Message ----- From: "Rick Glazier" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 16, 2005 1:39 PM Subject: Re: DVD integration and new DVD burner software > I glossed over (or forgot) that section of the symptoms... > > That sounds more like a problem with "jumpers"... An odd one > I'll admit, but I have seen some VERY odd things happen when > jumpers were wrong on various random drives. I have seen even > ODDER things happen with Cable Select, but that is in the archives... > (I did not get around to making my cables shorter yet, and things > are still working great with "only" using jumpers...) > > I commonly have three or four IDE readers and/or burners hooked > up, (there are always two burners of some type), (and as many > as three IDE HDs), and never had CD/DVD drives conflict in that way... > Older IDE hard drives, (lets say ones under 1G) sometimes refused to > "play nicely together" due to a certain vagueness (or implementation) of > the older IDE specs... > > As far as the failure in the lead-in... I have not had any errors of any kind > for quite some time, > (except for a random bad media -- might be a failure rate of 5%, and > seems to be fairly consistent regardless of what drives I use), > but IIRC, the lead-in might only get burned poorly when "building" a > TOC using the PMA area. PMA areas were thought to be a "weak link" > by some experts... It was "such a problem" at one time, the "workaround" > was to change the style of the burn. (I think the answer was to always use > DAO.) I also believe, (at least in my case), it was due to some > incompatibility > with my drive and the (cheap) disks I was using. (I think it would give sense > errors, but it has been a very long time...) > > In any event, we are beating a dead horse since I doubt if you > want to go and see if you can reproduce the problem. <grin> > > Rick Glazier > > From: "James Button" > > But - would that have got around the problems that it would only work with > > the correct drive powered up - > > With both powered up it tended to hang, or just fail during lead-in > > creation. > > I suspect that there were minor differences ( bits chopped out or changed > > to limit functionality) in the 'OEM' dlls when compared > > with the 'Retail' version - but I couldn't be bothered to delve that deeply > > into the problem > > -- > ---------------------------------------- > WIN-HOME Archives: http://PEACH.EASE.LSOFT.COM/archives/WIN-HOME.html > Contact the List Owner about problems: [EMAIL PROTECTED] > Unofficial Win-Home List Members Profiles Page > http://winhome.wavijo.com/ > > -- ---------------------------------------- WIN-HOME Archives: http://PEACH.EASE.LSOFT.COM/archives/WIN-HOME.html Contact the List Owner about problems: [EMAIL PROTECTED] Unofficial Win-Home List Members Profiles Page http://winhome.wavijo.com/
