Diving Log 6 won't connect to Cobalt 2 - maybe due to unsigned driver

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Messages
1
Reaction score
0
Location
San Francisco bay area
# of dives
200 - 499
I had to recently reinstall Diving Log 6 on laptop (windows 10) after overhaul to fix a drive failure. Now the Cobalt 2 can't be accessed. I can/have been able to update the Cobalt 2 with latest firmware (Cobalt shows up in device manager through USB after enabling on Cobalt 2). I tried to manually install cobalt drivers that were provided by Support at Diving Log and the install couldn't complete - error msg that the inf file did not contain signature information. There is a bare minimum signature item in the install area so I can only guess that the driver install expects something more extensive.
 
I think this has to be a question for Diving Log- the Cobalt 2 just appears as a USB mass storage device, and it looks as if that part is working. I don't know what Windows is looking for in order to install the Diving Log drivers, but maybe that has changed since they prepared them for the Cobalt. It may be some kind of security setting?

Good luck,

-Ron
 

Back
Top Bottom