Fixed COPY ... TO ... crashing

[fromano]

**** DO NOT TRY THIS COMMAND ON FILES YOU DON'T WANT TO LOSE, IT WILL DELETE FILES IN TARGET THAT DOES NOT EXIST IN SOURCE ***

32-bit TCMD on Windows 10 x64

TCC 19.10.43 Windows 10 [Version 6.3.10240]
TCC Build 43 Windows 10 Build 10240

this command:
*copy /A: /B /D /E /F /G /H /J /O:n /S /UF /W /Y /Z /[!Thumbs.db] g:\mp3 TO: n:\mp3 p:\mp3 s:\mp3

g:\ local ntfs disc
n:\ local ntfs disc
p:\ local ntfs disc
s:\ Remote (network) drive

causes tcc to crash (no .gpf):
Log Name: Application
Source: Windows Error Reporting
Date: 2016-02-29 19:55:02
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: FROMANO-ENVY810
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: tcc.exe
P2: 19.10.43.0
P3: 56d3aef7
P4: StackHash_ea6d
P5: 10.0.10240.16683
P6: 56ad9358
P7: c0000374
P8: PCH_4A_FROM_ntdll+0x000690BC
P9:
P10:

 

[rconn]

This is a problem with /O:n (none of the other options are relevant). I will have a fix in the next build.

I cannot perceive of any reason to use /O:n with COPY -- what was your intent?

 

[fromano]

when I copy(backup) whole drives I want the copy to do it in order of their names, sometimes I use /O:-s or /O:s to either copy the biggest/smallest files first

Are you saying this is not right or am I misunderstanding it? Would it have happened with DIR /O:n?

 

[rconn]

Copies are already done in the order of their names (assuming you're using NTFS). And it wouldn't make any difference anyway unless you want to read the names as they're processed (which would only work for very large files or very slow systems).