Unwanted delete of entire folder using Win2K

[Guest]

I use one machine strictly for scanning. I set up the machine for that single
purpose and made it as quick as possible by reformatting the drive (NTFS),
reinstalling Win 2000, a Viewer (Irfanview) and the scanning software
(Epson). There is no other software. Win2K is fully current. The installation
is a full installation (no customization) but is otherwise super "vanilla." I
have never even tweaked the registry. There is no virus software and no
external shares. I handoff images to the network through a one-way out
connection.

I scan images to a c:\temp directory. When finished, I transfer all images
to a network directory. Here's the problem: if I do a Cut-Paste (CTRL+X) of
all the images, the ENTIRE c:\TEMP directory is deleted. Not just the images.
The first few times it happened, I thought I was going crazy.

In one way, the failure is fully predictable. If I cut all images, the
entire directory is deleted every time. However, if I cut only some of the
images, the temp directory (and remaining images) may or may not disappear.

And, yes, the directory is definitely deleted.

The only way I can work with the machine is to use a cumbersome four-step
process: I first copy the files (CTRL+C) to the network directory, then
"soft-delete" images to the Recycle Bin. Next, I empty the recycle bin which
then asks for confirmation (the 4th step.)

Has anyone ever encountered this problem before? Or, more importantly, does
anyone know a repair?

 

[Lanwench [MVP - Exchange]]

In

I use one machine strictly for scanning. I set up the machine for
that single purpose and made it as quick as possible by reformatting
the drive (NTFS), reinstalling Win 2000, a Viewer (Irfanview) and the
scanning software (Epson). There is no other software. Win2K is fully
current. The installation is a full installation (no customization)
but is otherwise super "vanilla." I have never even tweaked the
registry. There is no virus software and no external shares. I
handoff images to the network through a one-way out connection.

I scan images to a c:\temp directory. When finished, I transfer all
images to a network directory. Here's the problem: if I do a
Cut-Paste (CTRL+X) of all the images, the ENTIRE c:\TEMP directory is
deleted. Not just the images. The first few times it happened, I
thought I was going crazy.

In one way, the failure is fully predictable. If I cut all images, the
entire directory is deleted every time. However, if I cut only some
of the images, the temp directory (and remaining images) may or may
not disappear.

And, yes, the directory is definitely deleted.

The only way I can work with the machine is to use a cumbersome
four-step process: I first copy the files (CTRL+C) to the network
directory, then "soft-delete" images to the Recycle Bin. Next, I
empty the recycle bin which then asks for confirmation (the 4th step.)

Has anyone ever encountered this problem before? Or, more
importantly, does anyone know a repair?

In Windows Explorer, click the folders button so you have a two-paned
window. On the left, select C:\TEMP. On the right, you will see the contents
of C:\TEMP. Highlight/select them, then do CTRL+X. It should *not* touch the
folder itself - only the contents therein.

 

[Guest]

In

In Windows Explorer, click the folders button so you have a two-paned
window. On the left, select C:\TEMP. On the right, you will see the contents
of C:\TEMP. Highlight/select them, then do CTRL+X. It should *not* touch the
folder itself - only the contents therein.

Thanks for your prompt reply. I'm apologize, for not having been completely
clear. I am not a beginner. I fully understand how to delete files. I have
been doing CTRL+X-CTRL+V since transitioning from DOS into the very first
version of Windows. I will often create and delete hundreds, even thousands,
of image files per week. I think I mentioned that a CTRL+X on *part* of the
stack sometimes removes the entire directory. To be clearer, I will mention
that when CTRL+X mis-fires, it removes everything, including the "temp"
directory, the entire file stack, and all sub-directories. Unlike a normal
"hard delete," (SHIFT+DELETE) no confirmation dialog box ever appears.

Let's say that "temp" is the name of the parent directory that appears on
the left side of the Explorer pane. Pretend that within "temp" is a group of
150 images plus one or more sub-directories. These appear in the right pane.
IF I select all of the image files (which only appear in the right pane, of
course), but NOT the sub-directories, and do a CTRL+X-CTRL+V (into a target
directory), all of the image files disappear, all of the sub-directories
disappear, and the "temp" directory disappears.

As mentioned, some of the time, but on a more unpredictable basis, I may
select to cut and paste 50 of 150 images. CTRL+X-CTRL+V sometimes works okay,
but sometimes kills all files, all-subdirectories, and the "temp" parent.
Again, no fanfare; no confirmatory dialog box. Re-booting has no effect.

Even my rent-a-geek is baffled. Short of attempting another complete system
rebuild from scratch, any other suggestions?

Thanks.

 

[Sid Knee]

Have you tried:

- CTRL-A to select all the files (or mouse-drag a rectangle around all
the files)
- right-click and drag them to the network destination directory
- chose "move here" from the menu that appears when you release the
right mouse button.

(I'm assuming you have a mouse connected. Given the way you are
currently doing it, you may not).

 

[Guest]

- CTRL-A to select all the files (or mouse-drag a rectangle around all
the files)
- right-click and drag them to the network destination directory
- chose "move here" from the menu that appears when you release the
right mouse button.

Thanks. That way works okay, but, as you know, CTRL+X-CTRL+V is dramatically
faster when picking a hodepodge of files from here and there. And, then all
of a sudden, the entire stack is gone.

Thanks.

 

[Pegasus \(MVP\)]

I use one machine strictly for scanning. I set up the machine for that single
purpose and made it as quick as possible by reformatting the drive (NTFS),
reinstalling Win 2000, a Viewer (Irfanview) and the scanning software
(Epson). There is no other software. Win2K is fully current. The installation
is a full installation (no customization) but is otherwise super "vanilla." I
have never even tweaked the registry. There is no virus software and no
external shares. I handoff images to the network through a one-way out
connection.

I scan images to a c:\temp directory. When finished, I transfer all images
to a network directory. Here's the problem: if I do a Cut-Paste (CTRL+X) of
all the images, the ENTIRE c:\TEMP directory is deleted. Not just the images.
The first few times it happened, I thought I was going crazy.

In one way, the failure is fully predictable. If I cut all images, the
entire directory is deleted every time. However, if I cut only some of the
images, the temp directory (and remaining images) may or may not disappear.

And, yes, the directory is definitely deleted.

The only way I can work with the machine is to use a cumbersome four-step
process: I first copy the files (CTRL+C) to the network directory, then
"soft-delete" images to the Recycle Bin. Next, I empty the recycle bin which
then asks for confirmation (the 4th step.)

Has anyone ever encountered this problem before? Or, more importantly, does
anyone know a repair?

The behaviour you observe is by design. If you Ctrl+X a whole folder
then it will be moved to the destination area.

Since you appear to perform this action routinely, why don't you
automate it by using a batch file. Start off by using a dedicated
folder instead of c:\temp, then run this batch file via a shortcut
on the desktop:

@echo off
xcopy /s c:\Pics\*.jpg "s:\SomeFolder\"
if ErrorLevel 0 del /s /q c:\Pics\*.jpg
pause

You will find that all jpg files will be moved and that
the directory structure of c:\Pics will be maintained.

 

[Sid Knee]

Thanks. That way works okay, but, as you know, CTRL+X-CTRL+V is dramatically
faster

..... but less safe as you dramatically discovered Sorry, couldn't
resist. And yes, I agree that keyboard shortcuts can be much faster than
the mouse for the adept.

I read your other response. One thing I didn't notice .... how exactly
do you select the files (in the right explorer pane) that you want to
copy. Obviously, if you want them all, CTRL-A is the way to go but what
about the case where you want say 50% of them?

 

[Sid Knee]

The behaviour you observe is by design. If you Ctrl+X a whole folder
then it will be moved to the destination area.

that wasn't my understanding of what he said. As I saw it he wasn't
CTRL-X'ing the folder just all (or some) of the files *within* the
folder. Yet the folder was getting deleted anyway along with the files.

 

[Lanwench [MVP - Exchange]]

In coxrail <[email protected]> typed:

Thanks for your prompt reply. I'm apologize, for not having been
completely clear. I am not a beginner. I fully understand how to
delete files. I have been doing CTRL+X-CTRL+V since transitioning
from DOS into the very first version of Windows. I will often create
and delete hundreds, even thousands, of image files per week. I think
I mentioned that a CTRL+X on *part* of the stack sometimes removes
the entire directory. To be clearer, I will mention that when CTRL+X
mis-fires, it removes everything, including the "temp" directory, the
entire file stack, and all sub-directories. Unlike a normal "hard
delete," (SHIFT+DELETE) no confirmation dialog box ever appears.

Let's say that "temp" is the name of the parent directory that
appears on the left side of the Explorer pane. Pretend that within
"temp" is a group of 150 images plus one or more sub-directories.
These appear in the right pane. IF I select all of the image files
(which only appear in the right pane, of course), but NOT the
sub-directories, and do a CTRL+X-CTRL+V (into a target directory),
all of the image files disappear, all of the sub-directories
disappear, and the "temp" directory disappears.

As mentioned, some of the time, but on a more unpredictable basis, I
may select to cut and paste 50 of 150 images. CTRL+X-CTRL+V sometimes
works okay, but sometimes kills all files, all-subdirectories, and
the "temp" parent. Again, no fanfare; no confirmatory dialog box.
Re-booting has no effect.

Even my rent-a-geek is baffled. Short of attempting another complete
system rebuild from scratch, any other suggestions?

Very odd....I can't reproduce this here at all (just tried it; only about 20
files/subfolders, though) and it didn't delete the parent folder when I
pasted the clipboard contents into a new folder elsewhere.

I do like the recommendation to script this with a batch file, however -
since you do this regularly.

 

[Guest]

Start off by using a dedicated

folder instead of c:\temp, then run this batch file via a shortcut
on the desktop:

Thanks for the suggestion.

Truth is, I already use a batch file similar to this to move images into 62
static directories based on parts of file names.

In this particular circumstance, I am looking for a way to fix a failed
Window component that works perfectly on every other of my machines.

Maybe I'm missing something, but I can only imagine four fixes:

1) Copy EXPLORER.EXE and all related components from another functional
installation of Win2K. (Does anyone know ALL components that might affect the
functionality of Explorer.exe?)

2) Registry tweaks.

3) Wipe the drive back to bare metal, reinstall Win2K, and hope for the best.

4) Wipe the drive back to bare metal, install XPPro, and hope for the best.

What specifically has me baffled is how this very same installation of Win2K
worked perfectly on this very same computer under FAT and now fails under
NTFS.

Thanks again.

 

[Guest]

Very odd....I can't reproduce this here at all (just tried it; only about 20

files/subfolders, though) and it didn't delete the parent folder when I
pasted the clipboard contents into a new folder elsewhere.

I seriously doubt that this problem is reproducible. I have never
encountered the problem in 20 years of using Windows. As stated elsewhere,
the problem appeared when I wiped the hard drive, converted from FAT to NTFS,
and re-installed Win2K. (Same CDs; same hard drive.)

I do like the recommendation to script this with a batch file, however -
since you do this regularly.

As I indicate in another reply, I appreciate all the workaround suggestions,
but I am actually seeking a fix to one of the core sub-parts of the Windows
OS. Fixing seems to be looking more and more like an impossibility.

But thanks for taking your time to try. It may be, quite literally, one of
those bizarre cases of a single bit being corrupted during installation,
never to repeat itself again.