Brian, Plextor wouldn't need to teach everyone to use their CD burning software if they provided this upgrade material in a more acceptable format! <SMILE>
-- Carol [EMAIL PROTECTED] -----Original Message----- From: Brian Borowski [mailto:[EMAIL PROTECTED] Sent: 23 August 2004 16:37 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Upgrade process, manual and other docs on ptr1 website, ETC... Your disagreement with me, is slightly different. I don't believe Plextor has the responsibility to teach everyone how to use their cd burning software. You believe they should make this process easier; which is somewhat different. I agree with you on that one. They could, for example, like MS and others do, make CDs available for users to obtain, if requested. They could make the PTR1 capable of upgrading from a file on the compact flash card if this is possible, ETC. Brian Borowski On Mon, 23 Aug 2004, Carol Pearson wrote: > I'm sorry, I don't quite agree here. > > It may not be directly a Plextor issue but it's unreasonable, surely, > to expect everyone to have CD burning software and, even if they have > the software and use it in a limited capacity, they still may not > understand (as I did not) about images. > > I know of no other programme where updates are issued in this format. > > I hope Plextor are listening! > > > -- > Carol > [EMAIL PROTECTED] > > > > -----Original Message----- > From: Brian Borowski [mailto:[EMAIL PROTECTED] > Sent: 23 August 2004 15:43 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Upgrade process, manual and other docs on ptr1 website, > ETC... > > > The upgrade process isn't complicated; just read the documentation on > the web site and follow the directions. If users don't know how to > burn an image with their particular sort of cd burning software; then > this is really not a Plextor issue, but a use of software issue. The > problem is, > there are numerous brands of cd burning software, and Plextor (I can't > imagine this to be the case) cannnot be responsible for teaching people > how to do this; this list can help with such issues. Personally, I > like: $ cdrecord dev=0,0 speed=16 -data PTR1VERUP200ENG.iso but it's all > up to the user. > > As for the documentation; maybe the manual isn't just the thing for > everyone, but if one actually reads it, or searches for the sections > relevant to what you're trying to do; it has all the information in > it; I had no questions about the use of the machine after reading the > whole thing. That's not to say refreshing of my memory wasn't needed, > because > > there was so much information there, but you learn how to do some > basic things with the machine, and when you've mastered that, learn > the more complicated things through the use of the manual, this list, > and experimentation. There is documentation on the ptr1 site, about > the new > > features in V2, and how to upgrade; I followed those instructions and > it > > happened... > > There may be an issue with some stray RF on the case of the PTR1, but > this isn't unusual in the case of almost all devices that have a power > supply, > especially if the case of that equipment isn't grounded through a > separate > line (the safety ground) which I believe all computers have. The PTR1's > > power supply has a two-conductor cord and uses a switching power > supply (down to 10V DC 2.5A) and has to be well isolated for safety > reasons. The fact that the computer is grounded and the PTR1 is not, > might well mean that when a user makes a connection between the two > devices, there could > > be a small low voltage difference between them. This is a common > problem and I've experienced it many times with a wide variety of > equipment. > > As for the audio hum when recording. My solution is to either: > * Reverse the plug, > > * Try a different mic, or if the input setup is more sophisticated > different connecting cords, > > * My favorite: wind a few turns of the cord from the input device > through a ferrite bead (toroid or tube). > Success with the above three suggestions varies depending upon numerous > external conditions, use, ETC. > > Brian Borowski > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004 > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.742 / Virus Database: 495 - Release Date: 19/08/2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
