View Single Post
  #9  
Old 24-04-2012, 05:49 PM
gregbradley's Avatar
gregbradley
Registered User

gregbradley is offline
 
Join Date: Feb 2006
Location: Sydney
Posts: 18,185
Quote:
Originally Posted by cventer View Post
Did you post on Software Bisque forum ?

I would make sure you run it in administrator mode.

Also delete and reinstall FLI drivers again in admin mode after CCDSOFT daily build is installed.

ie treat it like a fresh instal off ccdsoft first

then instal fli ccdsoft drivers.

Then run ccdsoft with admin rights and see if that helps. You cant be
only person in world running FLI cam with latest ccdsoft build
Yes I posted it in SB but only another forum member replied and he said check USB port in device manager and set it differently to STi. I think he is confused as device manager does not give numbers to usb ports. It does to com ports.

Reinstalling the drivers may work. I am using XP so no rights as administrator required.

Quote:
Originally Posted by Tandum View Post
Is/was the FLI an ascom camera? The latest ccdsoft install may have broken the hack to get ascom going.
or
The ccdsoft that came with the Sti does not include the optional ccdsoft camera plugin.
The camera plugin is still in the camera plug in folder and does not seem to change with the later version.

Not sure if FLI is an ascom camera. It comes with its own installer and driver installation software.

I like the idea of reinstalling the drivers for the FLI. I remember a fix for Vista issues was often to copy the version of the FLI driver in one part of CCDsoft and copy it in another.

Greg.
Reply With Quote