Hello All, Installed newest version 320 build 202 on a dual core intel,XP pro,creating secundary snapshot just fine,archived my primary for refreshing on ext. disk,everything went just fine, but at copy/update primary to archive or archive to primary it just hangs at the moment it has to copy [indexing the files before no problems ], i hear a lot of activity on the ext. disk but FDISR just hangs and no movement for 10 min and so i killed the process with taskmanager. In the activitylog there some messages : Windows error 232 and " error- writing message to pipe,pipe is being closed " . So anybody an opinion about this ? Huub.
I was getting what I thought was a hung during the preparing to copy. Would last 20 minutes, and then continue. Turned out to be AntiExecutable. Disabling it didn't help. Had uninstall it. There may be a similiar conflict. Pete
I would try disconnecting, un-plug and re-plug in you ext HDD. Windows Error 0x000000E8 - 232 The pipe is being closed. ERROR_NO_DATA This is a benign error but could be caused by the ext HDD not seeing the data FD-ISR is preparing to send. hth, ...screamer
Tried another external disk and everything went smooth,guess has to do with faulty disk. BTW other read/write operations to this disk so far no problems,bit puzzled !??
I never had problems with any build of FDISR. On the other hand no build of FDISR improved anything on my computer either. I never see any difference, just another version number and build number. I guess your problem had nothing to do with this build of FDISR, just an accidental coincidence.
Strange thing here i can do regular operations like copying,write and read to this '' faulty disk '' but can't create an FDISR archive on it. Strange
Obviously the disk is formatted as NTFS, FDISR works only on these Filesystems,previously had created snapshots on this disk without problem.
Like I said, "This is a benign error but could be caused by the ext HDD not seeing the data FD-ISR is preparing to send." In this case, compressed data. ...screamer
If you have a spare usb cable lying around try changing the cable to the problematical drive, sometimes it is as simple as that, don't ask me why, I don't understand them, I just work with them
Like i said no problems archiving to another external so compressed data is not likely the problem.Previously used built 173 with no problems to that disk,is there any difference with latest built in terms of compression ? Is this a known item ?
Solved ! Had renamed the .arx file itself [bzw. longer name.arx],i reset to default name,sofar no problems anymore.