Did you try Erwin Waterlander's WCD? http://waterlan.home.xs4all.nl/

Every. Single. Day. Sometimes also Notepad2 for quick edits. But Emacs is my bread and butter.

Also this: C:\...\conf> echo %@replace[;,^n,%PATH] C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0 C:\bin\ATI Technologies\ATI.ACE\Core-Static C:\bin\Tools C:\bin64\JPSoft\TCMD

[...] If LocalDateTimeToUTCFileTime can fail, the second one should be preferred. Â* Â* Juanma

On Mon, Oct 18, 2010 at 08:06, Jay Sage <> wrote: But did you run it as Administrator? It's not a failure (though it is not nice). Uninstalling TCMD12 just unregistered the isLicense DLL. Â* Â* Juanma

On Mon, Oct 18, 2010 at 04:36, Jay Sage <> wrote: It did work for me on Win7 x64. How does it fail for you? Â* Â* Juanma

On Sun, Oct 17, 2010 at 14:41, Joe Caverly <> wrote: It's been discussed before. You must go to your TCMD11 directory and run regsvr32 isLicense40.dll If you're on Vista or later, you must do this from a CMD running as administrator. Â* Â* Juanma

Same here: Windows 7 64-bit, TCMD12x64, no plugins. TCC crashes upon start. Â* Â* Juanma

Yes, definitely! Juanma

On Tue, Feb 2, 2010 at 04:12, vefatica <> wrote: There's a difference, I think: programs launched from TCC get App Paths added to the start of their PATH, while CMD does not do that (though Explorer does). Juanma

I'll do that, thanks for the suggestion. I also remember him saying that, but "tasklist /L" seems to work as expected on 64-bit Windows 7.

With all due respect, that's why I wrote that it is not impossible at all for TCMD to be involved; I said nothing about it being the cause, on the contrary, I said that I think it is just triggering the bug. I'm glad we agree.

No, sorry, it's not absolutely impossible.

There's no need for a hardware bug. Even if what crashes is a driver (I suppose so, yes), some user-mode code could be calling a system-level API in an unusual (but correct) way that invokes a low used code path. There's a difference between saying "the user code cannot bring the system down"...

I cannot know whether TCMD is triggering a Windows bug; likely. But what I've reported is my direct experience. Perhaps you can figure it out and work around it, as you've done for many other Windows bugs.