[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 4751 Date : 2003-06-04 Author : Pat Hyde Subject : Re: XXcopy cmds? Size(KB) : 5
Hi Kan, First things first. I was not, repeat, not attempting to place any blame on your program or programming skills. What I was saying was, " The blame lay with me, no one else." Reason why I thought that maybe XXcopy had caused my problem. I will attempt to explain. I have a recollection of attempting to use the Clone command. Used in the batch file below. I used the clone command instead of the switch sequence. @Echo off XXcopy C:\ E:\ /r/i/c/h/k/e/y/d/onC:\My.Log if not errorlevel 1 goto :eof if errorlevel 100 if not errorlevel 101 goto :eof echo An error occoured backing up the C:\drive echo Opening C:\My.Log for review start notepad c:\my.log pause :eof cls As I said I have a vague recollection that when I did this a message appeared stating something to the effect that D:\ drive would be written to? Perhaps I am wrong. But again, No blame on you. I press the button to accept. If I have this wrong then I offer full and total apologies. My system set-up as follows. Main Drive is C:\ Boot to Windows Slave Drive is E:\ Image of C:\ D:\ CDRW\DVD Samsung SM-332B A:\ Floppy Drive. Once again no blame apportioned to XXcopy or it's authors. It is a first class tool. The only problem is that it is so powerful that a lot of care is required. My advice to anyone. Be very careful, read messages presented carefully before pressing foot to floor. Will I continue to use XXcopy. Guaranteed 1000% would not be without it, or the information received from the Forum. So much info can be gained. If I have ruffled your feathers Kan you have an unreserved apology. Hope that this puts things into a better perspective. Corrections to anything I have said will be gratefully received. Kan/ Gary if you are tuned in? Regards Pat ----- Original Message ----- From: Kan Yabumoto To: xxcopy@yahoogroups.com Sent: Wednesday, June 04, 2003 10:24 AM Subject: Re: [xxcopy] XXcopy cmds? Pat wrote: >Hi again to all, >Advice and guidance required. > >I have been using XXcopy for a few weeks only. I have also, I thing, >inadvertantly wiped the firmware from my CDRW\DVD player, requiring >a vivit to the Service Centre. >I say I think. >the command I have been using I believe to be safe and should not >have caused any harm anywhere. Howevere, a little knowledge is >dangerous in the wrong hands, as I have found to my cost. >The command. XXcopy C:\ E:\ /r/i/c/h/k/e/y/d >I had been using this command previously in Xcopy for quite some >time. > >To add justa little flavour to all of this, I tried, ( and this is >where I think the problem occoured ) the XXcopy Clone command. > >I have an weird feeling that it all went belly up then. >Anyone got any ideas on the subject?? >Not put off by this exoerience, Learn by mistakes. Pat: While I have sympathy to anyone whose equipment starts malfunction, I am not ready to accept responsibility to your problem unless some concrete evidence is presented. Here's the list of possible culprits in the order of probability in my opinion. 1. CDRW hardware manufacturing/component defect 2. CDRW firmware defect (bug) 3. Bug in packet-writing software 4. OS (probably inside kernel32.dll, if at all) 5. XXCopy's defect (bug). My reasoning is based on the fact that XXCOPY's actions are strictly at the high level Win32 file I/O operations. XXCOPY does not even know how to read or write (i.e., to manipulate the device in an intimate way) to a CDRW/DVD. It requires a device driver which knows the device characteristics that interacts with the device. XXCOPY avoids accessing even sectors and tracks on the hard disk to be on the safe side. Therefore, even if certain sequence that XXCOPY performs consistently (and repeatably) destroys the firmware, what XXCOPY does is within the bounds of what is allowed by the system and the fault must be in the lower-level software components that were supplied by the respective vendor. My educated guess is some component failure is probably the direct cause ---- of course, a good circuit design should prevent such a catastrophic device failure even if some components fail. This is my opinion which may be naturally regarded as self-serving statement. I would like to hear from anyone who knows computers in both hardware and software. Anyway, as the author of the XXCopy program, I will assure you that the chance of my program being the direct cause of your equipment failure is less than one in 1 million. So, what then? I suggest after you get the drive back (probably, the best remedy for you is to get your device replaced rather than just a re-programming of the firmware). If you have a different unit (even if it is the same model), it will be extremely unlikely that using the XXCOPY /CLONE operations will ever produce the same failure again. On the other hand, if you just reprogram the firmware, using XCOPY (not XXCOPY) may result in a similar failure --- if it was caused by a component failure, I would not be surprised if the same thing happens unless the real cause (say, failed or marginal components or poor solder joints) is identified and removed. If you make a copy what I wrote here and present it to the CDRW/DVD manufacturer's engineer, he will probably agree with my assessment of this matter. Kan Yabumoto Yahoo! Groups Sponsor Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed]
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.