Okay Bill. This version started up okay (did not bomb. I found that if I use my old 642 station (Oak Bay, Victoria) that the sun will always be up if I don't change the time in the FITS header which is UT. Image was taken remotely at J54 (Canary Islands). So Fits header time was Oct. 15/09 22:17:18 UT. For some reason Charon believed the sun was up and that the image was taken here (642). Dark there but not here ;-). Changed header time to 03:17:18 UT (-7 hours)(DST) to reflect 642 Lat and Long. This made it dark here.
Anyway, things sort of worked.

The new station dat file had station J54 listed, which also helped.

Thanks for the help and input.

Chris. Spratt
Victoria, BC

--- In guide-user@yahoogroups.com, Bill J Gray <pluto@...> wrote:
>
> Hi Chris,
>
> I think the first step will be to figure out what that
> error message is. I've updated
>
> http://home.gwi.net/~pluto/charon.zip
>
> accordingly. The major change is that if it bombs out,
> it asks you to 'hit any key' before closing the window.
> So you'll be able to actually see the message.
>
> Also, be aware that the file 'charon.log' contains
> some details about what's going on. If you can e-mail
> that to me, it would probably at least let me see how
> far Charon is getting before crashing.
>
> A minor, but maybe significant, change in the new
> version is that if setting the video mode fails, it tries
> using the VESA mode for your video card. That _might_
> enable success. I'm not counting on it, though; it's
> more likely that the update will simply enable us to see
> where the problem(s) lie.
>
> -- Bill
>