A part of the attempt to resolve 'SBIG Device Not Found' Issue the latest version of SBIG Driver Checker 64 application was downloaded from the SBIG Archives page (Diffraction Limited), and 'Update' was used to download and install the latest drivers.

As at 2017-11-23, the latest drivers downloaded were as follows (on 64 bit computer):

Despite the '64' in the name SBIGDriverChecker64.exe is a 32-bit application and can work on a 32-bit computer to install 32-bit SBIG drivers

It was noted that SBIGDriverChecker64 installs latest driver files into the following locations on my 64bit laptop running Windows 7

C:\Windows\system  :   sbigudrv.dll

C:\Windows\System32\drivers\ : sbigu64.sys, sbigfcam.hex,  sbiglcam.hex, sbigpcam.hex, sbigfga.bin

sbigudrv.dll is observed to be the only file contained in the \Windows\system folder on my 64 bit computer

It's unclear how other programs manage to find it. Examining the Windows Registry with Regedit shows just a single reference to SBIGUDrv.dll (see below) which points to a C:\Windows\System32 location for the .dll
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs\  

Value Name: C:\Windows\system32\SBIGUDrv.dll


In trying to find a log file reporting any further information about "SBIG Device not found" errors I came across the following list of all CCDSoft SBIG Camera Errors in "C:\Program Files (x86)\Common Files\System\sberror.h".   .

SBIG Camera Errors

CE_CAMERA_NOT_FOUND         1001  |SBIG driver: Camera not found.|
CE_EXPOSURE_IN_PROGRESS     1002  |SBIG driver: Exposure already in progress.|
CE_NO_EXPOSURE_IN_PROGRESS  1003  |SBIG driver: Exposure not in progress.|
CE_UNKNOWN_COMMAND          1004  |SBIG driver: Bad PC Command.|
CE_BAD_CAMERA_COMMAND       1005  |SBIG driver: Bad camera command.|
CE_BAD_PARAMETER            1006  |SBIG driver: Bad parameter.|
CE_TX_TIMEOUT               1007  |SBIG driver: Transmission timeout.|
CE_RX_TIMEOUT               1008  |SBIG driver: Receive timeout.|
CE_NAK_RECEIVED             1009  |SBIG driver: NAK received.|
CE_CAN_RECEIVED             1010  |SBIG driver: CAN received.|
CE_UNKNOWN_RESPONSE         1011  |SBIG driver: Unknown response.|
CE_BAD_LENGTH               1012  |SBIG driver: Bad length.|
CE_AD_TIMEOUT               1013  |SBIG driver: A/D timeout.|
CE_KBD_ESC                  1014  |SBIG driver: Keyboard Escape.|
CE_CHECKSUM_ERROR           1015  |SBIG driver: Checksum error.|
CE_EEPROM_ERROR             1016  |SBIG driver: EEPROM error.|
CE_SHUTTER_ERROR            1017  |SBIG driver: Shutter error.|
CE_UNKNOWN_CAMERA           1018  |SBIG driver: Unknown camera.|
CE_DRIVER_NOT_FOUND         1019  |SBIG driver: Driver not found.|
CE_DRIVER_NOT_OPEN          1020  |SBIG driver: Driver not open.|
CE_DRIVER_NOT_CLOSED        1021  |SBIG driver: Driver not closed.|
CE_SHARE_ERROR              1022  |SBIG driver: Driver share error.|
CE_TCE_NOT_FOUND            1023  |SBIG driver: TCE not found.|
CE_AO_ERROR                 1024  |SBIG driver: AO error.|
CE_ECP_ERROR                1025  |SBIG driver: ECP error.|
CE_MEMORY_ERROR             1026  |SBIG driver: Memory error.|
CE_DEVICE_NOT_FOUND         1027  |SBIG driver: Device not found.|
CE_DEVICE_NOT_OPEN          1028  |SBIG driver: Device not open.|
CE_DEVICE_NOT_CLOSED        1029  |SBIG driver: Device not closed.|
CE_DEVICE_NOT_IMPLEMENTED   1030  |SBIG driver: Device not implemented.|
CE_DEVICE_DISABLED          1031  |SBIG driver: Device disabled.|
CE_OS_ERROR                 1032  |SBIG driver: Operating system error.|
CE_SOCK_ERROR               1033  |SBIG driver: Socket error.|
CE_SERVER_NOT_FOUND         1034  |SBIG driver: Server not found.|
CE_CFW_ERROR                1035  |SBIG driver: General CFW error.|

CE_CFWE_NONE                1040  |SBIG driver: CFW error none.|
CE_CFWE_BUSY                1041  |SBIG driver: CFW error busy.|
CE_CFWE_BAD_COMMAND         1042  |SBIG driver: CFW error bad command.|
CE_CFWE_CAL_ERROR           1043  |SBIG driver: CFW error calibration error.|
CE_CFWE_MOTOR_TIMEOUT       1043  |SBIG driver: CFW error motor timeout.|
CE_CFWE_BAD_MODEL           1045  |SBIG driver: CFW error bad model.|


Downloaded and installed Sequence Generator Pro today (fully featured 45 day trial).  Principal aim is to gain an independant view & diagnosis of the SBIG Camera Not Found problem that I've been experiencing whilst trying to connect to my SBIG ST-10 camera from a recently reinstalled copy of CCDSoft 5 . However it will also give me an opportunity to understand if the SGP offers me anything of benefit, considering its cost $99 USD versus it features which strongly overlap with the functionality of my own AIS/CCDApp2 observatory control program.

VS2010 Express Edition has been my principal program development environment in the last  6 years or so for developing my CCDApp2 and CCDApp2_AllSky programs for observatory control and for AllSky Image Capture respectively. However I begun to move my program development into more recent Visual Studio products.

VS2015 and 2017 have a lot of new features that I don't need use for regular Windows Forms / Console Programming and their GUI in are both less appealing than VS2010's GUI due to MicroSoft's move towards dumbing down the window bars, dividers, scoll bars etc (It can be hard to pick out the window your're working on and hard to find &  move scroll bars etc). However both offer JIT debugging which is useful and both advertise support for Python Programming.

In practice VS2015 (Vn 14.0.25431.01 Update 3) is found to be highly resource intensive, consuming significant CPU and large amounts of memory. A lot of online blogs and forum postings report this.  None of the 'solutions' I've tried provide an adequate fix to this problem.   (It is noted that VS2015 starts up a side process called 'Microsoft.VsHub.Server.HttpHostx64.exe' which also consumes resources and still runs for some 15 mins after VS2015 is closed).
See https://connect.microsoft.com/VisualStudio/feedback/details/1610160/microsoft-vshub-server-httphostx64-exe

VS2017 (Vn 15.4.4) is altgether a lot lighter installation and consumes far less CPU and memory.
Hence VS2017 will gradually become my main programming environment for VB.Net programs.
[VS2017 was updated to Vn 15.5.0 on 2017-12-06, it's meant to have faster project opening and faster building]

For my Pthyon scripts and programs (e.g SharpCap Interface application) VS2015 will be the programming environment of choice, since python code debugging works in VS2015, but doesn't in VS2017 (I've seen this reported as an VS2017 issue in various online forums)

Some legacy VB.Net programs will remain for the time being in VS2010.

I've tried to install VS2017 on my AllSky Laptop in order to access JIT debugging to solve an annoying runtime error that occurs after several hours or days of operation which stops a particular thread and eventually brings down the whole program. Unfortunately VS2017 refuses to load as the laptop is running Windows XP.

For some time JIT debugging hasn't been working on my main laptop.  Whilst it may not have be a feature in VS2010 Express Edition, it is a feature of VS2015 Community Version and although I had enabled JIT from Tools/Options/Debugging/JIT Debugging, I was not presented with an option to debug the program when one of my VB.Net programs crashed or otherwise failed during testing.

Eventually I came across a solution online which solved the issue
https://stackoverflow.com/questions/32988364/vs-just-in-time-debugging-wont-work

The trick was to go to Windows "\Control Panel\System and Security\Action Center\Change Action Center Setting\Problem Reporting Settings"  and set it to 'Never Check For Solutions".  This may require administrator permissions.

A method of Connection and Control of SharpCap image acqusition program from my own Observatory Control Program (AIS/CCDApp2) has been described previously.  This involves a python script (SharpCap Interface v10.py) that is run from within SharpCap to act as a server/interface application.  Once started the script opens Port 4000 (localhost), and waits/listens for a connection from the CCDApp2 program running on the same machine. After connection is made the server than waits for request messages from CCDApp2's job queue, such as 'take_image_set' request to record a set of Live Stacked Images for a specified Target Object.   Progress during image capture is communicated through 'get_appstate' and 'get_lastresult' requests. 
(Note that since SharpCap 3.0 a special £10 licence is required to access certain feature in SharpCap, including Scripting)

Whilst the Python Scripts can be created and edited in a simple text editor, there is an advantage in being able to create & develop them in a proper source code development package that can colour code text, spot language errors and be able to run the program under debugging conditions. 

Since the Script uses Windows Forms with data fields, labels and buttons etc, there is an extra benefit if the source code development package can also build forms interactively (visually rather than simply in code). However I haven't found a package yet that can develop Forms interactively for use with Python Code.   So I'm left to define my form using code alone.

SharpCap uses a built in scripting language called IronPython (http://ironpython.net/).  IronPython is an implementation of the Python programming language which is tightly integrated with the .NET Framework. I've therefore installed IronPython on my computer (Current Version 2.7.7)

At the present moment I'm using two alternative packages for developing my Python Code:
a) Microsoft Visual Studio 2015 (Community Edition, V14) (including PythonTools)
b) JetBrains PyCharm (Community Edition, 2017.2.4)

Both packages seem have issues for developing and debugging Python code.   I'm see trying to see which one provides the most productive environment to work.  Visual Studio is the environment I've previously worked with whilst developing VB.Net applications

At the moment PyCharm produces the critical error message when attempting to run the Script with debugging.
   "Unable to proceed (sys._current_frames not available in this Python implementation)."
This is apparently a known problem for running PyCharm with IronPython but one that has not been solved yet.
Running Python Code in PyCharm however works ok
(It's understood that the sys._current_frames problem was introduced with IronPython 2.7.6 and 2.7.7 and thus debugging might work ok if using version 2.7.5)

VS 2015 will run the program with debugging, but initially whilst it stopped at Breakpoints, the step-in/over/out operations didn't move through the code in the interactive screen but simply caused the program to run until the next breakpoint.  This was eventually fixed by going to Debug Tab in the Project's Properties (accessed by Right Clicking on the Project in Solution Explorer) and changing the debug Launch Mode from "IronPython (.NET) launcher" to "Standard Python launcher".  'Execute Project in Python Interactive' (accessed from Debug or Tools/Python Tools menus)  is used for running the Script in the development environment. This provides a console window that highlights any runtime errors and warnings.

More recently I've tried moving my SharpCap Interface project into VS2017, but I find that I'm unable to successfully run Python Code with debugging.  This is understood to be an issue with VS2017. 

In both VS2015 and PyCharm running the Script in development environment (outside of SharpCap) is not able to access SharpCap data and methods.   An include file containing dummy classes and objects representing those in SharpCap itself is used to prevent the Script from crashing in the development environment.   This is not ideal, but allows connectivity between the Server Interface and my CCDApp2 program to be tested.  The presence of a flagging file (SimFlag.dat) is used to tell the script if it is in the test (Simulation) environment or the live (SharpCap) environment:

import os.path
if os.path.exists('SimFlag.dat'):
   sim = 1
   from SharpCap_Dummy import SharpCap
else:
   sim = 0

Proper testing requires the Script to be run from within the SharpCap program itself however.   To speed up my workflow I have added a Button (& subroutine) to my Observatory Control Program plus accompanying routine that allow me to quickly copy the Python Script Files from the VS2015 project areas into the particular folder that I use for running Python scripts in SharpCap.

Beside an .htm report file summarising the session, the script also outputs a .log file that contains more detailed information about the session and the communications between CCDApp2 and the SharpCap interface. Both of these can be helpful for understanding any issues or bugs.