[ros-bugs] [Bug 5176] shell: Copy/Paste failure when multiple files are selected at once.

[ReactOS.Bugzilla at reactos.org]

http://www.reactos.org/bugzilla/show_bug.cgi?id=5176





--- Comment #7 from BrentNewland <brent.newland at gmail.com>  2011-12-28 00:01:13 CET ---
(In reply to comment #5)
> I think I found the other part to this problem, and that it should point to the
> solution:
> 
> On a fresh install of ReactOS trunk, open the Application Manager, go to the
> driver section, and download the AC97 driver. It will ask you to extract to
> C:\Downloads, go ahead and extract it.
> 
> Now, enter c:\downloads with Explorer, highlight the "inf" and "system32"
> folders, right click one, and hit copy or move. Go into the c:\ReactOS folder,
> right click somewhere, and click Paste.
> 
> Looks like they disappeared or weren't copied, right? Look inside the
> c:\ReactOS\inf folder - you'll find the "inf" and "system32" folders inside.
> 
> However, if you rename the folders to "inf2" and "system322", they disappear.
> 
> 
> Faster way to reproduce:
> Open command prompt, run the following commands:
> cd \temp
> mkdir test1
> mkdir test2
> mkdir target
> mkdir test1
> explorer c:\temp\
> 
> Now, highlight "test1" and "test2", right click and cut/copy, enter "target"
> folder, right click and paste. They are now in the "test1" folder.
> 
> And showing the effect is the same for files and folders:
> Open command prompt, run the following commands:
> cd \temp
> echo 1 > test3
> echo 1 > test4
> mkdir target
> mkdir test3
> explorer c:\temp\
> 
> Now, highlight "test3" and "test4", right click and cut/copy, enter "target"
> folder, right click and paste. They are now inside the "test3" folder.
> 


Should be:

cd \temp
mkdir test1
mkdir test2
mkdir target
cd target
mkdir test1
explorer c:\temp\

Basically, it takes the first file/folder in the list of files/folders to be
copied and makes it the target (or it disappears).


-- 
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.