thanks, Ritchie, for all your help! i appreciate it very much! =)
Ritchie said:
what
Are you absolutely sure about that? If you create a folder called "_test", then
is that the only folder copied (assuming it becomes the 'first')?
tried the "_test" test and it disproved my hypothesis so i just started
messing with a variety of stuff... during my tinkerings, i came across the
real problem.
i noticed that the xcopy operation was erroring out with 'Insufficient
Memory' at a certain point - it was caused by a file with a maximum-length
filename: "030926 UtilitiesForms copied out before attempting to move all
common functions into frmDataEntry - saved in case external versions of
these functions are needed agai.vb" (you can see that as i was typing it,
the final 'n' got cut off!) not sure if it's just the filename causing the
problem or the combined file/path name since the path is a bit lengthy
too... ("c:\documents and settings\kris\my documents\visual studio
projects\drs\drs client\safety\")
either way, i worked around the problem by simply renaming the file to
something shorter, but i would prefer a more 'robust' solution - i.e. a copy
command that doesn't care what my files are named! (i prefer _my_
preferences to dictate how _the OS_ works, not the other way around! (i
swear i can hear the mocking laughter of Mac evangelists even as i write
this...)) admittedly, it's pretty rare that i write a file with the
maximum-length name, but it _does_ happen...
any thoughts? is this a known bug? something fixed in a SP? (this machine
is only SP2 for reasons only my sys admin could explain...)
or maybe it's really out of memory?! it only has 256 megs, after all! ;-)
"The ampersand (&) separates multiple commands on one command line". In
ohterwords, all the commands joined by an & are treated as one block of
code...
SETLOCAL basically creates a copy of the current environment and then that copy
becomes the current environment. When the script ends or an ENDLOCAL command
is encountered, the current environment is discarded and the previous
restored.
i c - thanks! i don't really see the advantage of joining the first two
commands on one line in this case, but now at least i know what it does.
and as for 'environments' - sadly, i don't even know exactly what that is...
(my best guess is that it's a 'set' of env. variables that you can address
by name.) i don't use either of these things on a daily basis (or even
command line in general) but it's helpful to know what these things are when
i do run across them!
BTW, the /S switch is redundant because of the /E switch. Run 'xcopy/?' for
a list of switches and their descriptions.
yeah i ran it with '/?' - that's where i came up with all these crazy flags!
=)
i wasn't real clear on /S vs. /E, but with your input + re-reading the help
text several times i think i've got it now. (i know it seems easy, but the
part that confused me was where they say in the help "Same as /S /E." - i
figured "if the example does it this way, it must be sensible to do it that
way."... wrong!)
thanks again! =)