The DbgView does indeed give this single line of output
[2536] Subclass done
The Problem Details screen gives this lot of info:
Problem signature:
Problem Event Name: APPCRASH
Application Name: sailwave.exe
Application Version: 2.9.4.0
Application Timestamp: 5133e49f
Fault Module Name: StackHash_384d
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c000041d
Exception Offset: 73054f0d
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 384d
Additional Information 2: 384d3b36de92e2b3da1c2d0e63c180b8
Additional Information 3: 982b
Additional Information 4: 982b2c6b39fa42bcf78d7b426fdc5a0c
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This made me think of having a look in the Windows Event Viewer and it contained the following:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: sailwave.exe
P2: 2.9.4.0
P3: 5133e49f
P4: StackHash_384d
P5: 0.0.0.0
P6: 00000000
P7: c000041d
P8: 73054f0d
P9:
P10:
Attached files:
These files may be available here:
C:\Users\satkinson\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_sailwave.exe_80a635bfb1d0aa8e5f479a09e961641bc72b53b_1fe7314a
Analysis symbol:
Rechecking for solution: 0
Report Id: df22e8c1-8704-11e2-9591-c5370cc1e641
Report Status: 0
The directory mentioned contains the below in a file called Report.wer
Version=1
EventType=APPCRASH
EventTime=130071201778892177
ReportType=2
Consent=1
ReportIdentifier=df22e8c2-8704-11e2-9591-c5370cc1e641
IntegratorReportIdentifier=df22e8c1-8704-11e2-9591-c5370cc1e641
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=sailwave.exe
Sig[1].Name=Application Version
Sig[1].Value=2.9.4.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5133e49f
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_384d
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=73054f0d
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=384d
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=384d3b36de92e2b3da1c2d0e63c180b8
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=982b
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=982b2c6b39fa42bcf78d7b426fdc5a0c
UI[2]=C:\Program Files (x86)\Sailwave\sailwave.exe
UI[3]=Sailing Scoring Software has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Sailwave\sailwave.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[5]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[6]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[7]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[8]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[9]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[10]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[11]=C:\Windows\syswow64\GDI32.dll
LoadedModule[12]=C:\Windows\syswow64\USER32.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\syswow64\comdlg32.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[18]=C:\Windows\system32\MAPI32.dll
LoadedModule[19]=C:\Windows\syswow64\ole32.dll
LoadedModule[20]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[21]=C:\Windows\system32\oledlg.dll
LoadedModule[22]=C:\Windows\syswow64\WININET.dll
LoadedModule[23]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[24]=C:\Windows\syswow64\iertutil.dll
LoadedModule[25]=C:\Windows\syswow64\urlmon.dll
LoadedModule[26]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[27]=C:\Windows\system32\IMM32.DLL
LoadedModule[28]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[29]=C:\Windows\system32\uxtheme.dll
LoadedModule[30]=C:\Program Files (x86)\TeamViewer\Version7\tv_w32.dll
LoadedModule[31]=C:\Windows\system32\CRTDLL.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL
LoadedModule[34]=C:\Windows\system32\Secur32.dll
LoadedModule[35]=C:\Windows\system32\profapi.dll
LoadedModule[36]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[37]=C:\Windows\syswow64\NSI.dll
LoadedModule[38]=C:\Windows\system32\dnsapi.DLL
LoadedModule[39]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[40]=C:\Windows\system32\WINNSI.DLL
LoadedModule[41]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[42]=C:\Windows\system32\RASAPI32.dll
LoadedModule[43]=C:\Windows\system32\rasman.dll
LoadedModule[44]=C:\Windows\system32\rtutils.dll
LoadedModule[45]=C:\Windows\system32\sensapi.dll
LoadedModule[46]=C:\Windows\system32\mswsock.dll
LoadedModule[47]=C:\Windows\System32\wshtcpip.dll
LoadedModule[48]=C:\Windows\System32\wship6.dll
LoadedModule[49]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[50]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[51]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[52]=C:\Windows\system32\rasadhlp.dll
LoadedModule[53]=C:\Windows\System32\fwpuclnt.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Sailing Scoring Software
AppPath=C:\Program Files (x86)\Sailwave\sailwave.exe
And this list of DLLs got me to thinking; I make use of a desktop sharing app called TeamViewer, and it occurred to me that it adds an icon to the top of each application window to allow quick sharing of that application. I disabled it for sailwave, and then I can start sailwave without it crashing. I guess its attempt to attach itself to the Sailwave window during startup must be causing some issue. I can live without TeamViewer for sharing specific applications so it’s not a big deal.
Thanks for the quick responses and help. It really highlights the usefulness of a support community like this.
Onwards to running last years club results against the new RYA NHC to see what (if any) difference there is, before suggesting to the members that it may be worth moving to … 
Steve
···
Jon Eskdale
Sailwave
03333 443377
07976 709777
On 6 March 2013 22:16, Steve Atkinson Steve.Atkinson@windswept.org.uk wrote:
Had a bit of an unproductive evening trying your suggestions and other things
I’ve tried a complete uninstall, and reboot, and removed all references to sailwave left in regedit, then another reboot and a clean install of 2.9.4
It still exhibits the same behaviour 
Then I tried the rename of sailwave.exe, and still no joy.
I also tried installing it into c:/sailwave incase the brackets in C:\Program Files (x86)\Sailwave were causing any issues.
Out of interest I then did a plain uninstall of 2.9.4 and straightaway installed 2.8.5 with the defaults, and it works without any issues, minus the NHC stuff.
Just on the off chance I uninstalled 2.8.5 and reinstalled 2.9.4 but it is back to being unable to start, so it does appear to be something confined to the new beta versions
Is there any sort of additional logging that can be turned on or crash reports that should be generated to help diagnose the problem?
Regarding the Mac install
I can’t remember the exact details of what I did, but I know I have Xquartz and WineBottler installed
http://xquartz.macosforge.org/landing/ http://winebottler.kronenberg.org/
I think all I did after installing them was to just run the sw2_9_4.exe installer and it just worked.
The only quirk is that double clicking on a .blw file doesn’t work, you have to start Sailwave and then File -> Open and browse to the file to open it.
If I remember any more of the details I’ll let you know
Steve
On 6 March 2013 10:09, Jon Eskdale jon@sailwave.com wrote:
Hi Steve,
The NewVersion message is because 2.9.4 is a Beta and the version check says that the one you are running is not the current latest version - which is true but perhaps it should be a bit more intelligent, you can turn off the check for new version when you are running a beta version if you want to stop the message appearing.
StoppedWorking
This is a strange one but as you were running a previous version before it might be something to do with the Manifest file that Colin supplied with some versions. I’ve found that it works best without this file and had a similar problem with on 64 bit machine. Using Windows explorer goto the C:\Program Files (x86)\Sailwave directory and make sure there is no sailwave.manifest file present.
If this does not work it may be because somewhere windows has cached this info. Try renaming the file Sailwave.exe to Sailwave2.exe and then double click to run it. I know it sounds strange but I’ve seen this work just by changing its name to not be Sailwave. If someone knows where it is storing this / how to fix it please let us know as I spent half an hour looking the other day and failed!!
Many thanks for the feedback on the success in running 2.9.4 and the NHC code on the Mac. The missing Exit is very strange although I guess Alt-F4 would work as a get around?
I’m sure if you could spend the time to Write up the “how you installed it on the Mac” with which versions and best place to download the Wine from etc it would be greatly appreciated by many users and if you like we could put it on the Sailwave site.
Jon
Jon Eskdale
Sailwave
03333 443377
07976 709777
On 6 March 2013 08:54, Steve Atkinson Steve.Atkinson@windswept.org.uk wrote:
Having some issues with the new 2.9.4 Beta, (and the same problem
happend with 2.9.3)
It’s crashing out at startup (screen shots attached), both when
started from the start menu and when double clicking on a blw file
When double clicking on a file, it seems to sort of display the table
of data, but then crashes before it resizes the control to the full
area of the window
This is running on Windows 7 64 bit. There’s nothing particularly odd
about the machine, other than having My Documents (and Pictures, Music
etc) configured on a separate drive
I though I had seen something on the mailing list on a means to run
sailwave with some extra loggin/debug turned on to try and see what
the issue is, but I can’t seem to find those messages
This machine was running an older previously. Unfortunately, I cant
remember what version, probably one that was released back around
August/September last season
Any ideas what I can try to do to get things working?
Having said that the new beta runs fine on my Mac Air under Wine to
process results using the new RYA NHC, apart from there appearing to
be no Exit option on the File menu
Thanks
Steve