<verbatim>
Operating System: Windows XP
Fossil Version: >fossil ver
This is fossil version [9c5322463b] 2010-01-12 14:10:13 UTC
</verbatim>

I recently changed my "\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\AutoRun" REG_SZ registry entry from "" to "cd \" so my command-line prompts (cmd.exe) would start up at the root (as opposed to C:\Documents and Settings\__USER_GOES_HERE__), and this seemed to effect fossil's server detrimentally.  Whenever I would try to connect to the server, the fossil processes spawned by the server processes would crash, citing "ntdll.dll" in the Windows crash error report.

After looking around, I'm finding empty files with names like "fossil_server_P8080__out1.txt" in my root. (C:\)

I'm able to reproduce and fix this anomaly by changing the aforementioned registry entry from "cd \" to "" and back.


This is likely a problem with Windows more so than Fossil.

Fossil server crashes on Windows with custom CMD.exe command-line AutoRun