EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Crashed When Monitoring c:\ drive

Posted: 07/15/2010 07:45:10
by Theo Z (Basic support level)
Joined: 05/03/2010
Posts: 26


I have tested the new build for several days and didn't find any problem. Thank you very much once again for fixing the problem.

Posted: 08/23/2010 23:49:19
by Linden ROTH (Basic support level)
Joined: 08/23/2010
Posts: 20

I'm using version v.2.1.28 (July 8, 2010) and am getting similar problems x64 Vista (also x64 Win7)
  FCbFilter  := TCallbackFilter.Create( nil );
  FCbFilter.SerializeCallbacks := true; //bad with default false as well

  FCbFilter.GetDriverStatus( ProductGuid, DriverInstalled, FileVersionHigh, FileVersionLow, nil );

  if not DriverInstalled then
      FCbFilter.InstallDriver( extractfilepath( application.exename ) + 'cbfltfs.sys', //moved local to allow easier testing on multiple machines
                            ProductGuid, RebootNeeded );
      if RebootNeeded then
          showmessage( 'Need to reboot' );

  FCbFilter.AddFilterCallbackRule( '*.*', fltDeleteNotify or fltSetSizesNotify);
  FCbFilter.OnSetAllocationSizeN := SetAllocationSizeN;
  FCbFilter.OnCanFileBeDeletedN := CanFileBeDeletedN;
  FCbFilter.AttachFilter( 30 );

Works fine for a while then hard crash (BLUE SCREEN)... about to change to the Control (synchronous) events and see if that helps

Am I missing any thing here

Posted: 08/24/2010 03:54:59
by Vladimir Cherniga (Team)

The new version will be available in a few day, it contains several bug fixes. At this moment you can try the intermediate version.

About timeout in FCbFilter.AttachFilter( 30 ); It is 30 millisecond period, such small value may lead to skipping of the callbacks. In any case a will recheck the issue with a current version.
Posted: 08/24/2010 04:01:06
by Linden ROTH (Basic support level)
Joined: 08/23/2010
Posts: 20

Thanks for the prompt reply - had noticed the 30 (not 30000) and this has stopped (or so it would seem - with only 3 hours of testing) the BSofD but surely a small time-out on notify events should not cause a system crash - exception or fail


Posted: 08/24/2010 23:14:38
by Linden ROTH (Basic support level)
Joined: 08/23/2010
Posts: 20

The new version works even at 30ms time out (even if I breakpoint) ... the old version (28) worked if time-out was 30000ms (even if breakpoint hit)




Topic viewed 10902 times

Number of guests: 2, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!