Multi Commander > Support and Feedback
Crash upon opening Multicommander
AlanJB:
Hi Susan.
Glad that you got it sorted and that I was of some help :)
I am technically a Newbie on this forum, although I have 45+ years programming under my belt. Not C++, sadly, and I am very new to MC. But loving it so far :D
I totally get where Mathias is going with MC, and I am very impressed (BTW, I'm not easily impressed with most software I come across). For a one-man, part-time effort this is OUTSTANDING work!
I think Mathias has got his config TOTALLY right and it makes end-user (i.e., amateur) debugging SO much easier when config data is saved in well-formatted .xml files with sensible tag names! More developers should take a leaf out of his book, IMHO.
( Disclaimer: I do not know, nor have I any financial or otherwise arrangement with Mathias: he is Swedish, I am English and I have never left the UK: I simply know good software when I see it ;) )
Alan
Susan G:
--- Quote from: AlanJB on May 03, 2016, 00:08:51 ---Hi Susan.
Glad that you got it sorted and that I was of some help :)
I am technically a Newbie on this forum, although I have 45+ years programming under my belt. Not C++, sadly, and I am very new to MC. But loving it so far :D
I totally get where Mathias is going with MC, and I am very impressed (BTW, I'm not easily impressed with most software I come across). For a one-man, part-time effort this is OUTSTANDING work!
I think Mathias has got his config TOTALLY right and it makes end-user (i.e., amateur) debugging SO much easier when config data is saved in well-formatted .xml files with sensible tag names! More developers should take a leaf out of his book, IMHO.
( Disclaimer: I do not know, nor have I any financial or otherwise arrangement with Mathias: he is Swedish, I am English and I have never left the UK: I simply know good software when I see it ;) )
Alan
--- End quote ---
Hi Alan-
I agree. It's a wonderful program and I felt lost without it for a couple of days!
Thanks again-
-Susan
Susan G:
Hi-
I continue to get crashes with v6.2 build 2147 64 bit edition related to MCAudioTools.dll. My error reporting is set to Auto send crash report, Crash dump with maximum information (20+ MB). I do use the "Length Total" column.
Is there any other information I should provide? The last time it happened immediately upon saving a Word doc. The time before that I didn't actively do anything, but one of the apps I run might have been writing an autosave backup file at the time.
Thanks-
-Susan
Mathias (Author):
When MC send a crash report it give you a Crash ID.. you got that it ? So find what crash is yours..
Susan G:
Is this what you need?
Report Id: 609e053d-1f95-46fe-bb10-b93e9bf7432a
Thanks-
-Susan
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version