Highlighted
Rob383
1 Copper

EMCopy: ok but then "not a valid Win32 application ??"

Jump to solution

Greetings,

After downloading emcopy64 v14.7 and reviewing the documentation and comments on the internet, I used it successfully this afternoon to update-clone the data contents of one source data directory against an existing corresponding backup data directory.  I used it successfully for two such pairs of data directories  (F to M and G to N).  In each case I first ran the script against a test folder on the corresponding directories.  A test run on a third pair of directories worked as well.  The runs were made in the CMD window on a Win7 64bit Dell computer.

But when I tried to run the script again, even repeating the same test script I had successfully run earlier, I received a pop-up error message each time that "emcopy64.exe is not a valid Win32 application".  So it was working okay, but now is blocked from running.

The following illustrates the test script I was using:

           c:\emcopy>emcopy64.exe "g:\test-1" "n:\test-1" /s /de /c /r:5 /w:3 /th 4 /purge /log+:"c:\emcopy\log_file_1.txt"

                   

Would windows have some sort of test protocol that periodically tests applications that are being run, or would something in the running of EMCopy trigger a problem that flags the application as invalid?  I tried changing the name of the exe but that didn't help and closing/opening the CMD box didn't help.

Any thoughts on this situation?  Thanks.

Labels (1)
Tags (3)
0 Kudos
1 Solution

Accepted Solutions
Rob383
1 Copper

Re: EMCopy: ok but then "not a valid Win32 application ??"

Jump to solution

Shortly after posting the above question I realized how to address part of the issue.  Rather than use the 64bit version of EMCopy, I instead used the 32 bit version which was also included as part of the CifsTools_7.1.72.1.zip package.  Supposedly the 32 bit version is needed because the program is executed in the DOS-like CMD box.

Two considerations puzzle me however:

a) The fact that the 64-bit version did work fine for several large data transfer runs, and then was flagged as unacceptable for anything further.  I guess that was just some sort of delayed trigger-switch effect resulting from monitoring within the Win7 operating system.

b) What puzzles me more is why there is a Win7 64bit version of EMCopy if the only context in which EMCopy can be executed is within the context of a DOS-like CMD box which will not accept the 64-bit version???

Anyway, I guess the latter is just a curiosity question now because the 32 bit version of EMCopy provides the necessary functionality regardless of the fact that my overall operating system is Win7 64-bit.

Cheers

0 Kudos
1 Reply
Rob383
1 Copper

Re: EMCopy: ok but then "not a valid Win32 application ??"

Jump to solution

Shortly after posting the above question I realized how to address part of the issue.  Rather than use the 64bit version of EMCopy, I instead used the 32 bit version which was also included as part of the CifsTools_7.1.72.1.zip package.  Supposedly the 32 bit version is needed because the program is executed in the DOS-like CMD box.

Two considerations puzzle me however:

a) The fact that the 64-bit version did work fine for several large data transfer runs, and then was flagged as unacceptable for anything further.  I guess that was just some sort of delayed trigger-switch effect resulting from monitoring within the Win7 operating system.

b) What puzzles me more is why there is a Win7 64bit version of EMCopy if the only context in which EMCopy can be executed is within the context of a DOS-like CMD box which will not accept the 64-bit version???

Anyway, I guess the latter is just a curiosity question now because the 32 bit version of EMCopy provides the necessary functionality regardless of the fact that my overall operating system is Win7 64-bit.

Cheers

0 Kudos