Quote:
Originally Posted by DiapDealer
Actually, loading the Sigil exe in Dependency Walker when Diskeeper is installed should be enough. If Diskeeper being installed keeps Sigil from launching altogether, then Dependency Walker should prominently display a big, fat red error rather quickly.
EDIT: it's as easy as File->Open, and browse to the Sigil exe. Profiling is a little more in-depth, but since Sigil won't launch, that's not really an option anyway.
|
I reloaded Diskeeper 16 and Sigil now works. My theory as to the different result between today and yesterday is accepting a feature of how Diskeeper would like to use DRAM.
Dependency Walker, however, does not come back clean on Sigil. In any event, Sigil appears to be working just fine, despite the DW alert. I can't attach the DW text file because it exceeds the 20mb limit set for attachments. If there is an e-mail address off-board I can use to send it, just PM me. Or I guess I can split it and send 2 pieces--let me know.
Thanks