Re: Sophisticated(!) copying in DOS



"RJB" <notpublic@xxxxxxx> wrote in message
news:qLMne.18654$Ib.6973@xxxxxxxxxxx
> Dude. Check the hostility.
>
> I have confirmed in damn near every thread that I AM running from the
> command prompt.
>
> I didn't understand your "explicit" so I asked for clarification.
>
> My ONLY problem is with the /EXCLUDE switch. So it makes sense to me to
> focus on that. It is not a tangent. It IS the problem.
>
> Since the paths are correct when the switch is not in there, I am
> presuming the paths are STILL correct when it is. I can copy between
> directories till my toes curl, what I can't do is exclude a list of files.
> Which is all I want to do.
>
> My comment "I don't know where it is" - I have the batch file. It is on my
> desktop. When it runs, I don't know what IT considers its "explicit"
> location. If I move it to any directory, I get the same result - nothing.
>
> I have done everything everybody has suggested. I have done my best to
> explain what the results were, and if I tried modifying others'
> suggestions, I have tried to explain that.
>
> But thanks, for the first time in decades, I actually feel like I'm a
> moron.
>

I'm sorry if you are frustrated. I'm sorry if I appear hostile. I'm not
hostile, just frustrated, as you are. Not knowing how something works
doesn't make you a moron. I have spent hours crafting scripts to copy files
to CDRW for backups. It can be very frustrating getting it working as
expected. The key is to figure out exctly what you want to do then create a
very simple test situation. Once the test situation is working then apply it
to the original problem.

It appears you don't understand that Windows XP is not built on DOS. When a
program runs it has it's own unique environment. Because of this scripts
(batch files) often work differently than they did in earlier versions of
Windows. If you run a file from your desktop it won't have any idea where
the exclude file is located. From all the posts it sounds like this is your
problem. Usually it is simplest to have the script and any associated files
in the source directory. Make a shortcut on your desktop to run the script.

I suggest you create two temporary directories on a local drive. Keep it
very simple. e.g. C:\TEMP1 and C:\TEMP2.

Copy the files to TEMP1.

Create the exclude file in TEMP1. Call it EXCLUDE.TXT.

Start a cmd prompt and navigate to TEMP1 so that the prompt in the cmd
window looks like this C:\TEMP1>.

Type "XCOPY C:*.* C:\TEMP2\ /EXCLUDE;EXCLUDE.TXT". Without the quotations
and trailing period.

Keep it very simple, maybe one line in EXCLUDE.TXT that only excludes one
file. Make sure to keep the batch file and the exclude file in the source
directory. See if that works. If it doesn't work report back. There is some
other problem. If it does then you have to figure out how to apply this to
your situation.

It appears you don't understand that Windows XP is not built on DOS. I say
this because DOS and earlier versions of Windows used .bat files. Win2K and
XP use .cmd files usually called scripts. For compatibilty XP will run .bat
files the same as .cmd files. It really doesn't matter what you call them,
they should work. When a program runs it has it's own unique environment.
Because of this scripts often work differently than they did in earlier
versions of Windows. If you run a file from your desktop it won't have any
idea where the exclude file is located. From all the posts it sounds like
this is your problem. Usually it is simplest to have the script and any
associated files in the source directory. Make a shortcut to the batch file
on your desktop to run the script.

Kerry

> "Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m> wrote in message
> news:e2m2jw7ZFHA.3144@xxxxxxxxxxxxxxxxxxxxxxx
>> "RJB" <notpublic@xxxxxxx> wrote in message
>> news:BdKne.8224$zb.4292@xxxxxxxxxxx
>>>> read everyone's posts and try following directions. Once it's working
>>>> you can build from there.
>>>
>>> Um, I appreciate the advice, but I HAVE been trying to follow
>>> directions. In fact, I will go one step further, and say that I HAVE
>>> followed directions.
>>>
>>
>> Then why haven't you tried it from a cmd prompt, while in the source
>> directory, with the exclude file in the source directory, with no path
>> names in the command line other than the destination directory? This will
>> help to diagnose if it is a path related problem. I suggested this and
>> your response was:
>>
>> What do you mean "make sure [I am] explicitly in the directory"? I am
>> running the batch file FROM the destination laptop...
>>
>> Then you went off on a tangent about the /EXCLUDE parameter.
>>
>> I then posted again repeating the instructions and you said you don't
>> know where the file is. If you don't know where it is how do you copy it
>> in the first place? If it is a network share then just map a drive to
>> that share. You seem unable or unwilling to understand and follow
>> directions. I'm not trying to put you down. Diagnosing a problem by
>> newsgroup is frustrating at the best of times. When you keep repeating
>> that you are following directions when you clearly aren't it is even more
>> frustrating.
>>
>> Kerry
>>
>>
>
>


.



Relevant Pages

  • Re: GUI and Rapid Application Development?
    ... Most simple applications that I dealt with did not need the use of API ... I imagine Perl is faster, ... my Perl scripts are more compact ... Chirag> in Windows that could run on Windows 98 through 2003. ...
    (comp.os.linux.misc)
  • Re: Change the way users log on and off MODULE MISSING???
    ... After I ran those commands or scripts I ... do you think it was the security programs install/uninstall that caused ... and uninstall my Business Contact Manager just doesn't work! ... > If you receive the following error or similar, then reinstall Windows Script ...
    (microsoft.public.windowsxp.security_admin)
  • Re: How to Create a TCP/IP PrinterPort on a MS Cluster 2k3 via Scr
    ... thus the creation of the port on the node. ... Download the Windows Server 2003 resource kit and add prnadmin.dll to the ... Do you actually think I would post these scripts if it didnt work? ... In your response include the commands you used. ...
    (microsoft.public.windows.server.clustering)
  • RE: Login scripts not executing
    ... We are using windows 2003 in bothe the forests. ... We are not using Group Policy for logon scripts, ... controller and given the path in the user properties-profiles-logon scripts. ...
    (microsoft.public.win2000.active_directory)
  • itools 0.16.5 released
    ... meta-package for easier development and deployment: ... all scripts have been renamed to have ... "igettext-extract.py" works now with Windows Python files. ... And backwards compatibility fixes for the forum. ...
    (comp.lang.python.announce)