![]()
[<<]Message[>>] [<<]Author[>>] [<<]Subject [<<]Thread
Number : 3489 Date : 2003-01-08 Author : Yuki Taga Subject : Re: EXTREME alarm Size(KB) : 5
Hi Kan, Wednesday, January 8, 2003, 7:11:18 PM, you wrote: KY> I felt funny typing "Yuku", but I simply repeated your signature KY> line :-) I thought I was talking to a Japanese guy and then, I KY> started to wonder if this guy was from eastern Europe Tokyo. Setagaya-ku, if you know the place. ^_^ KY> At any rate, I'm very much relieved that the loss was of the KY> backup, not the real data --- a big sigh. Me too. (I am cutting a bit below to keep this as trim as possible, so we just cover the main points you've raised.) KY> In this particular instance, the jump is rather significant. The KY> versions 2.82.x was a "dead-end thread" in the XXCOPY evolution. KY> In order to make our next major update, we had to redo a lot of KY> things differently. So, substantial changes were made in the KY> code and we spent almost six months on this version. So, KY> nothing's surprise me except with a lot of disappointments (and KY> embarrassments). No problem. I am a very experienced computer girl, and I should have been more careful with a beta. I should have tested it in a safe environment before turning it loose on real files. It's just that I've grown to trust you guys. But you are human, after all, as we all are. ^^_^^ KY> About the XXCOPY INSTALL KY> XXCOPY may be installed anywhere you like. For example: KY> xxcopy /install:c:\bin\ Yes, I understand. Mine lives in m:\2000 Apps\xxcopy, and of course I have that in my PATH, on both systems. The batches can be run from either OS, and all drives are seen and lettered the same way by both systems. I didn't realize what xxcopy did about renaming when you install a later version. That is good. But for me, I'd still rather give it its own home. Girls don't like clutter. >>Kan, I believe you are saying above that the *only* way this can be >>ambiguous is if the complete source, as specified, does not exist. >>Am I correct? In any case, that was not a problem here. The >>complete source existed, and still exists. Simply rolling back to >>the old version of xxcopy allowed the batch to run perfectly. KY> The ambiguity is inherent to the command line that you create. KY> It is only you who can say it is not ambiguous. Moreover, KY> even you cannot guarantee that the m:\2000ap~1\equis72\ directory KY> really exists at all time. What if a virus wipes out that directory KY> prior to the XXCOPY execution? Or, someone came to your computer KY> and did something. One way or another, the fact remains true KY> that the command line itself does not resolve the ambiguity KY> until the contents of the volume is examined and the presence KY> of the intended directory is verified. That is why we strongly KY> suggest that the trailing backslash is almost "mandatory" and KY> I encourage this every time I have occasion for it. If you KY> browse the technical bulletins, you will find nearly all examples KY> follow this recommendation. There is no advantage in keeping KY> the deliberate command ambiguity when it is easily avoidable KY> (and accidental massive deletion at the destination side KY> due to the missing directory --- regardless of how that may KY> happen). Okay. I will amend my files to include the backslash. It is not a big deal, and I did not realize it was strongly recommended. I can guarantee that the destination directory was there, however. This is a normally disconnected USB, dedicated for backups. No virus, nobody can get at it except me. It was there. I do understand what you are saying, however. There are times when it might not be there for some people, and I should develop good habits that avoid traps. But it was there in this case. This USB drive is like one of my hands. I know it well. ^_^ But I am immediately editing my batch files to include the final backslash. KY> Please swallow it. No problem. KY> Wow, up to this point I thought I was talking to a man. Sorry for KY> my stereotyping. In this business, 95% of our customers are male KY> and I have tendency to assume as such. I usually do not like the KY> wording like "he or she". Not that I don't have respect to female KY> professionals in this field. Melissa in this group is one whose KY> feedback over the years has helped us tremendously. Actually, KY> you are the first "yamato-nadeshiko" that I encountered who can KY> talk the file management subject in great detail. There are others. But I assemble these boxes myself, too, which is surprising to some. Thank you for the compliment. KY> OK, Yuki, I'm convinced that we are dealing with something quite KY> serious here. We are now withdrawing the latest beta test KY> version v.2.83.x from our server until we find out more about KY> this incident. KY> Kan Yabumoto It's a good idea, Kan. Better safe than sorry. You have an excellent product, and I'm happy to use it. I was so shocked last night I'm afraid I wrote without thinking too well. But, back on the older version now and everything is running just like it always ran before -- perfectly. I'll stay tuned to this board very closely now and see how things progress. Best, Yuki mailto:yukitaga@t...
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.