xplorer2 (Not Responding)

[mcrosman]

Hi,

I do not know if it is a bug of xplorer2. But I have noticed that when I try to copy some files and folders to a formated CDR-W disc if the CDR-W disc has some problem during the copy xplorer2 freezes and the message "Not Responding" appears at the xplorer2's title bar. To solve this problem I have to reset the system.

It would be nice if after some time trying to access a CDR-W disc (that seems to have a problem)  that xplorer2 did not freezed but showed a message informing that the CDR-W has a problem and that cannot be accessed.

Is it a bug of xplorer2 or a bug of Windows XP ?

Marcelo.

[dft1]

I noticed a similar problem trying to copy files from a USB hard drive. Once the drive hit an error, X2's robust copy window would hang forever. I tried killing the x2 process, but got "Access denied". Must be a low level XP process that is hanging. If I pulled the USB plug, then the X2 process would terminate.

[nikos]

i believe these errors are system-wide. I didn't ever have a problem with USB sticks but cdrws etc are notoriously unstable and i'd bet that explorer would also stall with them from time to time

especially so those with "direct cd"
i recommend using proper cd burner software to copy files there

[mcrosman]

Concerning the problem I have mentioned about xplorer2 freezing when it tries to access or copy files to a CDR-W disc that seems to have problem I woul like to mention that I use InCD 4.3.11.1 and Nero 6.6.0.6.

It seems that CDR-W discs are not stable. Sometimes it is necessary to erase and reformat them.

Marcelo.

[robwg]

I work with floppies a lot and get this quite often when there's a problem with  a disk.  It just doesn't seem to want to give up trying to read/write and say "Disk error" but keeps churning away at the drive. I normally C-A-Del at this point but when I have left it going, it does eventually stop and give an error message. I've had the same thing with Zip disks on a USB port as well.

In this situation explorer does seem to behave the same way, although Windows doesn't give it the Not Responding tag as quickly as it does with xplorer2.

Only the Command Prompt handles it better, giving up after a short time.