Subj : RE: Windows 10 To : All From : MICHAEL PURDY Date : Thu Jan 31 2019 19:12:12 Date: Wed, 26 Aug 2015 21:05:17 -0400 From: MICHAEL PURDY To: CRAIG STRUTT Subject: RE: Windows 10 Newsgroups: win.server.program Message-ID: <1440637517.32.1440604218@winserver.com> References: <1440604218.32.1439596304@winserver.com> X-WcMsg-Attr: Rcvd X-Mailer: Wildcat! Interactive Net Server v7.0.454.5 Lines: 72 Craig Short Answer Wildcat is an SSI product and Hector has previously said that he prefers people to contact him directly so ˙he˙ knows about potential problems. I think this is important given that SSI will need to deal with an increasing number of W10 users over the next 12 months. So my recommendation would be to contact him directly. The other option would be to post in the BETA Winserver List that he does read. Long Answer DBGVIEW receives some output from the Windows OS but most comes from output sent to the Debug Stream by third party developers. You can read about the Output Stream here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa363362(v=vs.85).aspx The main thing to keep in mind is that if the developer does not send any debug output to the stream then you will not see anything and consequently DBGVIEW is of little value. A couple of reasons for using the debug stream are to reduce the overhead of sending debug information to STDOUT such as File or the Console and to avoid frightening end users etc. Fault tolerant heap shim This normally means a program has crashed e.g.: 1. It completely died and bailed 2. Its has become unresponsive 3. It exited abnormally on program stop. The most common cause is problems with memory management in the application or incompatibility problems. There are several other causes that need to be investigated by the developer on a case-by-case basis. I encountered a lot when I first moved to Win7. The shim will allow a crash prone application to run, but the associated registry shim entries are often lost especially after reboot. Basically you don˙t want shim errors. Troubleshooting Q. Have you set wcStart.exe and wcMail.exe to Run As Administrator Q. Have you navigated to the Wildcat root folder and Right Clicked on wcStart / wcMail and Run the Troubleshoot Compatibility Option and saved the suggested compatibility settings? This will tell you if W10 considers the Applications are Incompatible! Addition Troubleshooting Information I have a utility called wcdiag.exe that when run at the CLI wcdiag /t will produce a log called wcdiag-trouble.log this along with the DBGVIEW log may / may not be of help to HS/SSI You can download it here: http://wcstatus.mapurdy.com.au/downloads/downloads.wct If you wish to touch base with me again then send me an IM to either: Gtalk: mapurdy.com.au or Skype: mike_purdy. I don˙t login here now as much as I once did. Mike --- Platinum Xpress/Win/WINServer v3.1 * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013) .