Login with username and password (forgot your password?)

Wow! I've been using FARR for years and never knew this. Figured the slowness just had something to do with FARR's search method (i.e. not caching an index). But this change made a big difference.

Hard to believe, but FARR may be even MORE useful now.

ADDED: When you copy or paste a clip, Echo would always update the clip's timestamp, so that the clip would move to the top of the list when sorted by date. This is now optional: Preferences -> Pasting clips -> UpdateClipTimeStamp. This setting is still True by default, so that Echo's behavior does not change unless you modify this setting. (Thanks, Easye!)

Thanks very much! The new feature works great. Now I'll get the chance to try it out on a daily basis.

I've been a long time user of Ditto myself. I really like a lot of what you have done with this app.

Is there a setting anywhere to have the clip time NOT be updated on pasting? I've searched through the settings and couldn't find one that did this (but I may have missed it).

Ditto had a setting in the General tab called "Update Clip Time On Paste". I would always uncheck that myself when installing Ditto.

This is helpful for me when I do a lot of clipping in one app, then switch to another app and want to paste these various clips. When using Ethervane Echo, I will paste one of the clips, it then automatically goes up to the top and I then have to go searching back down the list to see where the next one was.

Thanks. Keep up the good work.

 . Just tried it, and for me it caused the same issue. Again, the program runs and checks all the installed software. But when I exit DcUpdater. I get a message that it has stopped working. The problem details are as follows:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   DcUppdater.exe
  Application Version:   1.0.0.0
  Application Timestamp:   00000000
  Fault Module Name:   KERNELBASE.dll
  Fault Module Version:   6.1.7100.0
  Fault Module Timestamp:   49eea60f
  Exception Code:   0eedfade
  Exception Offset:   0000b4f4
  OS Version:   6.1.7100.2.0.0.256.1
  Locale ID:   1033
  Additional Information 1:   84b3
  Additional Information 2:   84b3678162dd6817be25351f87fdbaf6
  Additional Information 3:   45f5
  Additional Information 4:   45f5d7257a5e5af74d9ee127e8d651ce

I wish I could track down what is causing the issue on my side. However, I haven't found anything. It does seem that Windows 7 has some odd issues like this. I recently had another beta application (Evernote) that wouldn't even install on Windows 7. On those forums half the people were able to get it to install correctly and the other half couldn't even get the install to do anything. The developers have not found a solution for that yet.

If there's anything to run on my side that might help you find a pointer to the issue, let me know and I'll be glad to help.

I've been having the same issue - DcUpdater crashes multiple times per day.

Not sure if this will help, but I used ProcDump from Sysinternals to get a dump file when it crashed. I'm not familiar with Windows debugging too much, but was able to get the following summary report of the dump file. If I can provide you with any other info on this let me know.

FYI I am running the latest version of the most excellent FARR . These crashes are happening when FARR automatically runs DcUpdater as well as when I manually run it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Eric\Documents\My Dropbox\Apps - portable\wscc\DcUppdater_121709_125306PM.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7100 MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Thu Dec 17 12:53:07.000 2009 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 17:31:01.000
................................................................
........
eax=0012faf4 ebx=00000057 ecx=00000007 edx=00000000 esi=01991194 edi=00000000
eip=75c8b4f4 esp=0012faf4 ebp=0012fb44 iopl=0         nv up ei pl nz ac po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000212
KERNELBASE!RaiseException+0x58:
75c8b4f4 c9              leave
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for guard32.dll -
*** WARNING: Unable to verify checksum for focus.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for focus.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for PATROLPRO.DLL -
*** WARNING: Unable to verify checksum for DropboxExt.3.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for DropboxExt.3.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for SugarSyncShellExt.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for libcurl.dll -
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for slc.dll -
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP:
+5f4d952f043fda44
00000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00001778

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  DcUppdater.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 004f15ba to 75c8b4f4

STACK_TEXT: 
0012fb44 004f15ba 0eedfade 00000001 00000007 KERNELBASE!RaiseException+0x58
WARNING: Stack unwind information not available. Following frames may be wrong.
0012fb9c 0054022d 0012fd68 00540283 0012fc78 DcUppdater!Nxclassesinitialization$qqrv+0x1a88a
0012fc78 0054f1c3 0199a4e4 01991194 005405c8 DcUppdater!Nxclassesinitialization$qqrv+0x694fd
0012fcd4 7628c6c2 000d1512 00000082 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x78493
0012fd00 76286101 00380b29 000d1512 00000082 user32!InternalCallWinProc+0x23
0012fd78 7628502c 00000000 00380b29 000d1512 user32!UserCallWinProcCheckWow+0xe0
0012fdd4 7627c628 00a54338 00000082 00000000 user32!DispatchClientMessage+0xda
0012fe04 77ac817e 0012fe1c 00000018 0012fe40 user32!__fnNCDESTROY+0x26
0012fe30 7627c661 0054052d 000f14a6 0012fe60 ntdll!KiUserCallbackDispatcher+0x2e
0012fe34 0054052d 000f14a6 0012fe60 0054054d user32!NtUserDestroyWindow+0xc
0012fe50 00529854 00000000 00527594 0012fe80 DcUppdater!Nxclassesinitialization$qqrv+0x697fd
0012fe74 0040340a 01973d01 0012feb8 005675a3 DcUppdater!Nxclassesinitialization$qqrv+0x52b24
0012fea8 00403254 01971e20 01972200 0012ff78 DcUppdater!UnStopAppWindowFromAppearingOnTaskbar$qqrv+0x1512
0012fedc 004e60b9 004013d8 004ebae0 005254a0 DcUppdater!UnStopAppWindowFromAppearingOnTaskbar$qqrv+0x135c
0012ff0c 0056fa2b 00000000 005b1034 00000000 DcUppdater!Nxclassesinitialization$qqrv+0xf389
0012ff34 0056fa7a 005e6af0 00000001 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x98cfb
0012ff58 0056e4ec 00000000 00000000 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x98d4a
0012ff6c 0056fc50 00000000 0012ffc4 0056827c DcUppdater!Nxclassesinitialization$qqrv+0x977bc
0012ff88 765c10dc 7ffd9000 0012ffd4 77ae1e9e DcUppdater!Nxclassesinitialization$qqrv+0x98f20
0012ff94 77ae1e9e 7ffd9000 727e97d8 00000000 kernel32!BaseThreadInitThunk+0xe
0012ffd4 77ae1e71 00401758 7ffd9000 00000000 ntdll!__RtlUserThreadStart+0x70
0012ffec 00000000 00401758 7ffd9000 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP:
DcUppdater!Nxclassesinitialization$qqrv+1a88a
004f15ba 33c0            xor     eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  DcUppdater!Nxclassesinitialization$qqrv+1a88a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: DcUppdater

IMAGE_NAME:  DcUppdater.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  46c97c4c

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_DcUppdater.exe!Nxclassesinitialization$qqrv

BUCKET_ID:  APPLICATION_FAULT_STATUS_BREAKPOINT_DcUppdater!Nxclassesinitialization$qqrv+1a88a

WATSON_STAGEONE_URL:  http://watson.microsoft.c...3/00000000.htm?Retriage=1

Followup: MachineOwner
---------