This must have something to do with your installation; I am running XP Media on
two of our
machines here and Guide8 (latest update) is working perfectly in all regards.  I
just
checked at various levels, including 8-11 and the NEXT works fine from one
object to
another and does indeed toggle from one catalog to another.  Are you indicating
that you
have NOT updated Guide in some time?  If so, I would install the current
version....quick
and easy and nothing changes except stuff that needs to.

Dr. Clay
_____
Arkansas Sky Observatories
MPC H45 - Petit Jean Mountain South
MPC H41 - Petit Jean Mountain
MPC H43 - Conway West
http://www.arksky.org/

----- Original Message -----
From: "JoeMize" <jmize@...>
To: <guide-user@yahoogroups.com>
Sent: Monday, November 09, 2009 11:49 AM
Subject: Re: [guide-user] Guide8 Problem


> How interesting, I just discovered this abend only occurs when the Level-10
> is set at 1deg.  Level-9 at 2deg or Level-11 at 30mins Guide8 works
> fine...joe  :)
>
>
> "May You Go Among The Imperishable Stars"
> Joe Mize  www.cav-sfo.com
> Chiefland Astronomy Village, Fla.
>
> ----- Original Message -----
> From: "JoeMize" <jmize@...>
> To: "Guide" <guide-user@yahoogroups.com>
> Sent: Monday, November 09, 2009 11:39 AM
> Subject: [guide-user] Guide8 Problem
>
>
>> Bill, I've just started having my "First Ever" problem with Guide.  I'm
>> using Guide8 on a WinXP Media Laptop.  I've used Guide since Guide4, I've
>> not Updated Guide8 since 04-26-2003.  Wow, has Guide8 been out since
>> 02-2002?
>>
>> When I Right Click a star for More Info I receive the requested
>> information
>> and I'm able to click the Next button as many times as I want.  But when I
>> try another Right Click somewhere else the following abend is received.
>> From then on I always receive the abend until I reBOOT my machine and I'm
>> allowed 'one' Right Click again.
>>
>> I have no problem on my WinXP Pro desktop machine.  Any help will be
>> appreciated.  Thkx...joe  :)
>>
>> ===
>> GUIDE6 MFC Application
>> GUIDE6 MFC Application has encountered a problem and needs to close.
>>
>> === More Information
>> AppName: guide8.exe  AppVer: 1.0.0.1  ModName: guide8.exe
>> ModVerL 1.0.0.1  Offset: 0002595c
>>
>> === Detailed Information
>> <?xml version="1.0" encoding="UTF-16"?>
>> <DATABASE>
>> <EXE NAME="guide8.exe" FILTER="GRABMI_FILTER_PRIVACY">
>>    <MATCHING_FILE NAME="get_dss.exe" SIZE="41984" CHECKSUM="0x30F033D8"
>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>> PRODUCT_VERSION="1,
>> 0, 0, 1" FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>> VERFILEDATELO="0x0"
>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="03/23/2003 01:51:34"
>> UPTO_LINK_DATE="03/23/2003 01:51:34" VER_LANGUAGE="English (United States)
>> [0x409]" />
>>    <MATCHING_FILE NAME="GSC22.EXE" SIZE="12288" CHECKSUM="0xABD40E65"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>> LINK_DATE="03/16/2003 21:39:49" UPTO_LINK_DATE="03/16/2003 21:39:49" />
>>    <MATCHING_FILE NAME="guide8.exe" SIZE="887296" CHECKSUM="0x4E5F72D"
>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>> PRODUCT_VERSION="1.0.001" FILE_DESCRIPTION="GUIDE6 MFC Application"
>> COMPANY_NAME="" PRODUCT_NAME="GUIDE6" FILE_VERSION="1.0.001"
>> ORIGINAL_FILENAME="GUIDE6.EXE" INTERNAL_NAME="GUIDE6" LEGAL_COPYRIGHT=""
>> VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001"
>> VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>> LINKER_VERSION="0x0"
>> UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1"
>> LINK_DATE="04/16/2003 20:20:17" UPTO_LINK_DATE="04/16/2003 20:20:17"
>> VER_LANGUAGE="English (United States) [0x409]" />
>>    <MATCHING_FILE NAME="gzip386.exe" SIZE="91648" CHECKSUM="0xCCB4F368"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>> LINK_DATE="12/02/1997 17:52:51" UPTO_LINK_DATE="12/02/1997 17:52:51" />
>>    <MATCHING_FILE NAME="hdecomp.exe" SIZE="60928" CHECKSUM="0x6C96D7E"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>> LINK_DATE="06/10/2001 16:45:13" UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>    <MATCHING_FILE NAME="lunar.dll" SIZE="152064" CHECKSUM="0x1897D200"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>> LINK_DATE="10/29/2001 16:00:24" UPTO_LINK_DATE="10/29/2001 16:00:24" />
>>    <MATCHING_FILE NAME="ASTEROID\ADDCOMET.EXE" SIZE="35436"
>> CHECKSUM="0xEAABD2D1" />
>>    <MATCHING_FILE NAME="IMAGES\HDECOMP.EXE" SIZE="60928"
>> CHECKSUM="0x6C96D7E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>> LINKER_VERSION="0x0" LINK_DATE="06/10/2001 16:45:13"
>> UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>    <MATCHING_FILE NAME="PGL\GPU.EXE" SIZE="86402" CHECKSUM="0xDCCAE214"
>> MODULE_TYPE="DOS" />
>>    <MATCHING_FILE NAME="PGL\PGL2PS.EXE" SIZE="32952" CHECKSUM="0xD43F23C9"
>> />
>>    <MATCHING_FILE NAME="REALSKY\A10_EXTR.EXE" SIZE="31170"
>> CHECKSUM="0x1F5C1F32" />
>>    <MATCHING_FILE NAME="REALSKY\GETIMAGE.EXE" SIZE="92782"
>> CHECKSUM="0xDADD08AE" MODULE_TYPE="DOS" />
>>    <MATCHING_FILE NAME="REALSKY\GET_DSS.EXE" SIZE="40448"
>> CHECKSUM="0x85C650D0" BIN_FILE_VERSION="1.0.0.1"
>> BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1"
>> FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>> VERFILEDATELO="0x0"
>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="11/04/2001 01:38:59"
>> UPTO_LINK_DATE="11/04/2001 01:38:59" VER_LANGUAGE="English (United States)
>> [0x409]" />
>>    <MATCHING_FILE NAME="UTILS\GSC22.EXE" SIZE="9728" CHECKSUM="0xD6C2A57C"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>> LINK_DATE="11/05/2001 21:09:57" UPTO_LINK_DATE="11/05/2001 21:09:57" />
>>    <MATCHING_FILE NAME="UTILS\GZIP386.EXE" SIZE="91648"
>> CHECKSUM="0xCCB4F368" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>> LINKER_VERSION="0x0" LINK_DATE="12/02/1997 17:52:51"
>> UPTO_LINK_DATE="12/02/1997 17:52:51" />
>> </EXE>
>> <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
>>    <MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x2D998938"
>> BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781"
>> PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API
>> Client
>> DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
>> Windows®
>> Operating System" FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)"
>> ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="©
>> Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
>> VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
>> MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001"
>> UPTO_BIN_FILE_VERSION="5.1.2600.5781"
>> UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58"
>> UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United States)
>> [0x409]" />
>> </EXE>
>> </DATABASE>
>>
>>
>> "May You Go Among The Imperishable Stars"
>> Joe Mize  www.cav-sfo.com
>> Chiefland Astronomy Village, Fla.
>>
>>
>>
>>
>> ------------------------------------
>>
>> To unsubscribe from this group, send an empty email to:
>> guide-user-unsubscribe@...! Groups Links
>>
>>
>>
>>
>
>
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>
>

Yup, Dr.Clay, the only time I updated Guide8 after its 02-2002 install was
way back in 04-2003.  I've seen no reason to do so until now.  Maybe it's
time if this bothers me with my new OTA's FOV.  Thkx for checking...joe  :)


"May You Go Among The Imperishable Stars"
Joe Mize  www.cav-sfo.com
Chiefland Astronomy Village, Fla.

----- Original Message -----
From: "P. Clay Sherrod" <drclay@...>
To: <guide-user@yahoogroups.com>
Sent: Monday, November 09, 2009 1:04 PM
Subject: Re: [guide-user] Guide8 Problem


> This must have something to do with your installation; I am running XP
> Media on two of our
> machines here and Guide8 (latest update) is working perfectly in all
> regards.  I just
> checked at various levels, including 8-11 and the NEXT works fine from one
> object to
> another and does indeed toggle from one catalog to another.  Are you
> indicating that you
> have NOT updated Guide in some time?  If so, I would install the current
> version....quick
> and easy and nothing changes except stuff that needs to.
>
> Dr. Clay
> _____
> Arkansas Sky Observatories
> MPC H45 - Petit Jean Mountain South
> MPC H41 - Petit Jean Mountain
> MPC H43 - Conway West
> http://www.arksky.org/
>
> ----- Original Message -----
> From: "JoeMize" <jmize@...>
> To: <guide-user@yahoogroups.com>
> Sent: Monday, November 09, 2009 11:49 AM
> Subject: Re: [guide-user] Guide8 Problem
>
>
>> How interesting, I just discovered this abend only occurs when the
>> Level-10
>> is set at 1deg.  Level-9 at 2deg or Level-11 at 30mins Guide8 works
>> fine...joe  :)
>>
>>
>> "May You Go Among The Imperishable Stars"
>> Joe Mize  www.cav-sfo.com
>> Chiefland Astronomy Village, Fla.
>>
>> ----- Original Message -----
>> From: "JoeMize" <jmize@...>
>> To: "Guide" <guide-user@yahoogroups.com>
>> Sent: Monday, November 09, 2009 11:39 AM
>> Subject: [guide-user] Guide8 Problem
>>
>>
>>> Bill, I've just started having my "First Ever" problem with Guide.  I'm
>>> using Guide8 on a WinXP Media Laptop.  I've used Guide since Guide4,
>>> I've
>>> not Updated Guide8 since 04-26-2003.  Wow, has Guide8 been out since
>>> 02-2002?
>>>
>>> When I Right Click a star for More Info I receive the requested
>>> information
>>> and I'm able to click the Next button as many times as I want.  But when
>>> I
>>> try another Right Click somewhere else the following abend is received.
>>> From then on I always receive the abend until I reBOOT my machine and
>>> I'm
>>> allowed 'one' Right Click again.
>>>
>>> I have no problem on my WinXP Pro desktop machine.  Any help will be
>>> appreciated.  Thkx...joe  :)
>>>
>>> ===
>>> GUIDE6 MFC Application
>>> GUIDE6 MFC Application has encountered a problem and needs to close.
>>>
>>> === More Information
>>> AppName: guide8.exe  AppVer: 1.0.0.1  ModName: guide8.exe
>>> ModVerL 1.0.0.1  Offset: 0002595c
>>>
>>> === Detailed Information
>>> <?xml version="1.0" encoding="UTF-16"?>
>>> <DATABASE>
>>> <EXE NAME="guide8.exe" FILTER="GRABMI_FILTER_PRIVACY">
>>>    <MATCHING_FILE NAME="get_dss.exe" SIZE="41984" CHECKSUM="0x30F033D8"
>>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>>> PRODUCT_VERSION="1,
>>> 0, 0, 1" FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>>> VERFILEDATELO="0x0"
>>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="03/23/2003 01:51:34"
>>> UPTO_LINK_DATE="03/23/2003 01:51:34" VER_LANGUAGE="English (United
>>> States)
>>> [0x409]" />
>>>    <MATCHING_FILE NAME="GSC22.EXE" SIZE="12288" CHECKSUM="0xABD40E65"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>> LINK_DATE="03/16/2003 21:39:49" UPTO_LINK_DATE="03/16/2003 21:39:49" />
>>>    <MATCHING_FILE NAME="guide8.exe" SIZE="887296" CHECKSUM="0x4E5F72D"
>>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>>> PRODUCT_VERSION="1.0.001" FILE_DESCRIPTION="GUIDE6 MFC Application"
>>> COMPANY_NAME="" PRODUCT_NAME="GUIDE6" FILE_VERSION="1.0.001"
>>> ORIGINAL_FILENAME="GUIDE6.EXE" INTERNAL_NAME="GUIDE6" LEGAL_COPYRIGHT=""
>>> VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001"
>>> VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>> LINKER_VERSION="0x0"
>>> UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1"
>>> LINK_DATE="04/16/2003 20:20:17" UPTO_LINK_DATE="04/16/2003 20:20:17"
>>> VER_LANGUAGE="English (United States) [0x409]" />
>>>    <MATCHING_FILE NAME="gzip386.exe" SIZE="91648" CHECKSUM="0xCCB4F368"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>> LINK_DATE="12/02/1997 17:52:51" UPTO_LINK_DATE="12/02/1997 17:52:51" />
>>>    <MATCHING_FILE NAME="hdecomp.exe" SIZE="60928" CHECKSUM="0x6C96D7E"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>> LINK_DATE="06/10/2001 16:45:13" UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>>    <MATCHING_FILE NAME="lunar.dll" SIZE="152064" CHECKSUM="0x1897D200"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>> LINK_DATE="10/29/2001 16:00:24" UPTO_LINK_DATE="10/29/2001 16:00:24" />
>>>    <MATCHING_FILE NAME="ASTEROID\ADDCOMET.EXE" SIZE="35436"
>>> CHECKSUM="0xEAABD2D1" />
>>>    <MATCHING_FILE NAME="IMAGES\HDECOMP.EXE" SIZE="60928"
>>> CHECKSUM="0x6C96D7E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>> LINKER_VERSION="0x0" LINK_DATE="06/10/2001 16:45:13"
>>> UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>>    <MATCHING_FILE NAME="PGL\GPU.EXE" SIZE="86402" CHECKSUM="0xDCCAE214"
>>> MODULE_TYPE="DOS" />
>>>    <MATCHING_FILE NAME="PGL\PGL2PS.EXE" SIZE="32952"
>>> CHECKSUM="0xD43F23C9"
>>> />
>>>    <MATCHING_FILE NAME="REALSKY\A10_EXTR.EXE" SIZE="31170"
>>> CHECKSUM="0x1F5C1F32" />
>>>    <MATCHING_FILE NAME="REALSKY\GETIMAGE.EXE" SIZE="92782"
>>> CHECKSUM="0xDADD08AE" MODULE_TYPE="DOS" />
>>>    <MATCHING_FILE NAME="REALSKY\GET_DSS.EXE" SIZE="40448"
>>> CHECKSUM="0x85C650D0" BIN_FILE_VERSION="1.0.0.1"
>>> BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1"
>>> FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>>> VERFILEDATELO="0x0"
>>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="11/04/2001 01:38:59"
>>> UPTO_LINK_DATE="11/04/2001 01:38:59" VER_LANGUAGE="English (United
>>> States)
>>> [0x409]" />
>>>    <MATCHING_FILE NAME="UTILS\GSC22.EXE" SIZE="9728"
>>> CHECKSUM="0xD6C2A57C"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>> LINK_DATE="11/05/2001 21:09:57" UPTO_LINK_DATE="11/05/2001 21:09:57" />
>>>    <MATCHING_FILE NAME="UTILS\GZIP386.EXE" SIZE="91648"
>>> CHECKSUM="0xCCB4F368" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>> LINKER_VERSION="0x0" LINK_DATE="12/02/1997 17:52:51"
>>> UPTO_LINK_DATE="12/02/1997 17:52:51" />
>>> </EXE>
>>> <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
>>>    <MATCHING_FILE NAME="kernel32.dll" SIZE="989696"
>>> CHECKSUM="0x2D998938"
>>> BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781"
>>> PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API
>>> Client
>>> DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
>>> Windows®
>>> Operating System" FILE_VERSION="5.1.2600.5781
>>> (xpsp_sp3_gdr.090321-1317)"
>>> ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="©
>>> Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
>>> VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001"
>>> UPTO_BIN_FILE_VERSION="5.1.2600.5781"
>>> UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58"
>>> UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United
>>> States)
>>> [0x409]" />
>>> </EXE>
>>> </DATABASE>
>>>
>>>
>>> "May You Go Among The Imperishable Stars"
>>> Joe Mize  www.cav-sfo.com
>>> Chiefland Astronomy Village, Fla.
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> To unsubscribe from this group, send an empty email to:
>>> guide-user-unsubscribe@...! Groups Links
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> ------------------------------------
>>
>> To unsubscribe from this group, send an empty email to:
>> guide-user-unsubscribe@...! Groups Links
>>
>>
>>
>>
>>
>
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>

I too always wait for excuses to make changes....sounds like this might be a
good time!

Dr. Clay
_____
Arkansas Sky Observatories
MPC H45 - Petit Jean Mountain South
MPC H41 - Petit Jean Mountain
MPC H43 - Conway West
http://www.arksky.org/

----- Original Message -----
From: "JoeMize" <jmize@...>
To: <guide-user@yahoogroups.com>
Sent: Monday, November 09, 2009 12:44 PM
Subject: Re: [guide-user] Guide8 Problem


> Yup, Dr.Clay, the only time I updated Guide8 after its 02-2002 install was
> way back in 04-2003.  I've seen no reason to do so until now.  Maybe it's
> time if this bothers me with my new OTA's FOV.  Thkx for checking...joe  :)
>
>
> "May You Go Among The Imperishable Stars"
> Joe Mize  www.cav-sfo.com
> Chiefland Astronomy Village, Fla.
>
> ----- Original Message -----
> From: "P. Clay Sherrod" <drclay@...>
> To: <guide-user@yahoogroups.com>
> Sent: Monday, November 09, 2009 1:04 PM
> Subject: Re: [guide-user] Guide8 Problem
>
>
>> This must have something to do with your installation; I am running XP
>> Media on two of our
>> machines here and Guide8 (latest update) is working perfectly in all
>> regards.  I just
>> checked at various levels, including 8-11 and the NEXT works fine from one
>> object to
>> another and does indeed toggle from one catalog to another.  Are you
>> indicating that you
>> have NOT updated Guide in some time?  If so, I would install the current
>> version....quick
>> and easy and nothing changes except stuff that needs to.
>>
>> Dr. Clay
>> _____
>> Arkansas Sky Observatories
>> MPC H45 - Petit Jean Mountain South
>> MPC H41 - Petit Jean Mountain
>> MPC H43 - Conway West
>> http://www.arksky.org/
>>
>> ----- Original Message -----
>> From: "JoeMize" <jmize@...>
>> To: <guide-user@yahoogroups.com>
>> Sent: Monday, November 09, 2009 11:49 AM
>> Subject: Re: [guide-user] Guide8 Problem
>>
>>
>>> How interesting, I just discovered this abend only occurs when the
>>> Level-10
>>> is set at 1deg.  Level-9 at 2deg or Level-11 at 30mins Guide8 works
>>> fine...joe  :)
>>>
>>>
>>> "May You Go Among The Imperishable Stars"
>>> Joe Mize  www.cav-sfo.com
>>> Chiefland Astronomy Village, Fla.
>>>
>>> ----- Original Message -----
>>> From: "JoeMize" <jmize@...>
>>> To: "Guide" <guide-user@yahoogroups.com>
>>> Sent: Monday, November 09, 2009 11:39 AM
>>> Subject: [guide-user] Guide8 Problem
>>>
>>>
>>>> Bill, I've just started having my "First Ever" problem with Guide.  I'm
>>>> using Guide8 on a WinXP Media Laptop.  I've used Guide since Guide4,
>>>> I've
>>>> not Updated Guide8 since 04-26-2003.  Wow, has Guide8 been out since
>>>> 02-2002?
>>>>
>>>> When I Right Click a star for More Info I receive the requested
>>>> information
>>>> and I'm able to click the Next button as many times as I want.  But when
>>>> I
>>>> try another Right Click somewhere else the following abend is received.
>>>> From then on I always receive the abend until I reBOOT my machine and
>>>> I'm
>>>> allowed 'one' Right Click again.
>>>>
>>>> I have no problem on my WinXP Pro desktop machine.  Any help will be
>>>> appreciated.  Thkx...joe  :)
>>>>
>>>> ===
>>>> GUIDE6 MFC Application
>>>> GUIDE6 MFC Application has encountered a problem and needs to close.
>>>>
>>>> === More Information
>>>> AppName: guide8.exe  AppVer: 1.0.0.1  ModName: guide8.exe
>>>> ModVerL 1.0.0.1  Offset: 0002595c
>>>>
>>>> === Detailed Information
>>>> <?xml version="1.0" encoding="UTF-16"?>
>>>> <DATABASE>
>>>> <EXE NAME="guide8.exe" FILTER="GRABMI_FILTER_PRIVACY">
>>>>    <MATCHING_FILE NAME="get_dss.exe" SIZE="41984" CHECKSUM="0x30F033D8"
>>>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>>>> PRODUCT_VERSION="1,
>>>> 0, 0, 1" FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>>>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>>>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>>>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>>>> VERFILEDATELO="0x0"
>>>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>>>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="03/23/2003 01:51:34"
>>>> UPTO_LINK_DATE="03/23/2003 01:51:34" VER_LANGUAGE="English (United
>>>> States)
>>>> [0x409]" />
>>>>    <MATCHING_FILE NAME="GSC22.EXE" SIZE="12288" CHECKSUM="0xABD40E65"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>>> LINK_DATE="03/16/2003 21:39:49" UPTO_LINK_DATE="03/16/2003 21:39:49" />
>>>>    <MATCHING_FILE NAME="guide8.exe" SIZE="887296" CHECKSUM="0x4E5F72D"
>>>> BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1"
>>>> PRODUCT_VERSION="1.0.001" FILE_DESCRIPTION="GUIDE6 MFC Application"
>>>> COMPANY_NAME="" PRODUCT_NAME="GUIDE6" FILE_VERSION="1.0.001"
>>>> ORIGINAL_FILENAME="GUIDE6.EXE" INTERNAL_NAME="GUIDE6" LEGAL_COPYRIGHT=""
>>>> VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10001"
>>>> VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>>> LINKER_VERSION="0x0"
>>>> UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1"
>>>> LINK_DATE="04/16/2003 20:20:17" UPTO_LINK_DATE="04/16/2003 20:20:17"
>>>> VER_LANGUAGE="English (United States) [0x409]" />
>>>>    <MATCHING_FILE NAME="gzip386.exe" SIZE="91648" CHECKSUM="0xCCB4F368"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>>> LINK_DATE="12/02/1997 17:52:51" UPTO_LINK_DATE="12/02/1997 17:52:51" />
>>>>    <MATCHING_FILE NAME="hdecomp.exe" SIZE="60928" CHECKSUM="0x6C96D7E"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>>> LINK_DATE="06/10/2001 16:45:13" UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>>>    <MATCHING_FILE NAME="lunar.dll" SIZE="152064" CHECKSUM="0x1897D200"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>>> LINK_DATE="10/29/2001 16:00:24" UPTO_LINK_DATE="10/29/2001 16:00:24" />
>>>>    <MATCHING_FILE NAME="ASTEROID\ADDCOMET.EXE" SIZE="35436"
>>>> CHECKSUM="0xEAABD2D1" />
>>>>    <MATCHING_FILE NAME="IMAGES\HDECOMP.EXE" SIZE="60928"
>>>> CHECKSUM="0x6C96D7E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>>> LINKER_VERSION="0x0" LINK_DATE="06/10/2001 16:45:13"
>>>> UPTO_LINK_DATE="06/10/2001 16:45:13" />
>>>>    <MATCHING_FILE NAME="PGL\GPU.EXE" SIZE="86402" CHECKSUM="0xDCCAE214"
>>>> MODULE_TYPE="DOS" />
>>>>    <MATCHING_FILE NAME="PGL\PGL2PS.EXE" SIZE="32952"
>>>> CHECKSUM="0xD43F23C9"
>>>> />
>>>>    <MATCHING_FILE NAME="REALSKY\A10_EXTR.EXE" SIZE="31170"
>>>> CHECKSUM="0x1F5C1F32" />
>>>>    <MATCHING_FILE NAME="REALSKY\GETIMAGE.EXE" SIZE="92782"
>>>> CHECKSUM="0xDADD08AE" MODULE_TYPE="DOS" />
>>>>    <MATCHING_FILE NAME="REALSKY\GET_DSS.EXE" SIZE="40448"
>>>> CHECKSUM="0x85C650D0" BIN_FILE_VERSION="1.0.0.1"
>>>> BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1"
>>>> FILE_DESCRIPTION="getimg22 MFC Application" COMPANY_NAME=""
>>>> PRODUCT_NAME="getimg22 Application" FILE_VERSION="1, 0, 0, 1"
>>>> ORIGINAL_FILENAME="getimg22.EXE" INTERNAL_NAME="getimg22"
>>>> LEGAL_COPYRIGHT="Copyright (C) 1998" VERFILEDATEHI="0x0"
>>>> VERFILEDATELO="0x0"
>>>> VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>>> LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1"
>>>> UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="11/04/2001 01:38:59"
>>>> UPTO_LINK_DATE="11/04/2001 01:38:59" VER_LANGUAGE="English (United
>>>> States)
>>>> [0x409]" />
>>>>    <MATCHING_FILE NAME="UTILS\GSC22.EXE" SIZE="9728"
>>>> CHECKSUM="0xD6C2A57C"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0"
>>>> LINK_DATE="11/05/2001 21:09:57" UPTO_LINK_DATE="11/05/2001 21:09:57" />
>>>>    <MATCHING_FILE NAME="UTILS\GZIP386.EXE" SIZE="91648"
>>>> CHECKSUM="0xCCB4F368" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0"
>>>> LINKER_VERSION="0x0" LINK_DATE="12/02/1997 17:52:51"
>>>> UPTO_LINK_DATE="12/02/1997 17:52:51" />
>>>> </EXE>
>>>> <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
>>>>    <MATCHING_FILE NAME="kernel32.dll" SIZE="989696"
>>>> CHECKSUM="0x2D998938"
>>>> BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781"
>>>> PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API
>>>> Client
>>>> DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft®
>>>> Windows®
>>>> Operating System" FILE_VERSION="5.1.2600.5781
>>>> (xpsp_sp3_gdr.090321-1317)"
>>>> ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="©
>>>> Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0"
>>>> VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2"
>>>> MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001"
>>>> UPTO_BIN_FILE_VERSION="5.1.2600.5781"
>>>> UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58"
>>>> UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="English (United
>>>> States)
>>>> [0x409]" />
>>>> </EXE>
>>>> </DATABASE>
>>>>
>>>>
>>>> "May You Go Among The Imperishable Stars"
>>>> Joe Mize  www.cav-sfo.com
>>>> Chiefland Astronomy Village, Fla.
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------
>>>>
>>>> To unsubscribe from this group, send an empty email to:
>>>> guide-user-unsubscribe@...! Groups Links
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> To unsubscribe from this group, send an empty email to:
>>> guide-user-unsubscribe@...! Groups Links
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> ------------------------------------
>>
>> To unsubscribe from this group, send an empty email to:
>> guide-user-unsubscribe@...! Groups Links
>>
>>
>>
>>
>
>
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>
>

Hi Joe,

     I'd strongly recommend getting the current version.  Many
bugs have been fixed since then,  and many improvements made
in how the program works.  I can't say that I specifically
recall this particular bug.  But I do know that when somebody
describes a random bug and tells me they've not updated for
years,  getting the current version almost always fixes it.

-- Bill

Will do Bill.  Thkx...joe  :)


"May You Go Among The Imperishable Stars"
Joe Mize  www.cav-sfo.com
Chiefland Astronomy Village, Fla.

----- Original Message -----
From: "Bill J Gray" <pluto@...>
To: <guide-user@yahoogroups.com>
Sent: Monday, November 09, 2009 3:41 PM
Subject: Re: [guide-user] Guide8 Problem


> Hi Joe,
>
>    I'd strongly recommend getting the current version.  Many
> bugs have been fixed since then,  and many improvements made
> in how the program works.  I can't say that I specifically
> recall this particular bug.  But I do know that when somebody
> describes a random bug and tells me they've not updated for
> years,  getting the current version almost always fixes it.
>
> -- Bill
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>

Thanks. That got TOFFSET working for me.

However, Guide snapped out of the time problem on Sunday on its own and has been
working fine since then.  It was only since Friday that I noticed the problem.

--- In guide-user@yahoogroups.com, "P. Clay Sherrod" <drclay@...> wrote:
>
> It appears that you have a space between the "=" sign and the -1.
> You can also go into Guide.txt and manually change the TOFFSET to the value
that you wish,
> but always remember to SAVE the file once done.

Hi All,

Another vote for : "Please do NOT discontinue support for Charon."

I have completely automated Charon for tracking and general plate solving.  My
own custom observatory control program shells to Charon using a keyboard buffer
utility.  It then exports the Charons result to file which is interrogated by my
application and used for tracking.  Its also used as part of an automated
asteroid hunting system.  The image is also presented in Guide - nice.  This
setup has been working great for about 2 years.

No other application is available that fits my requirements as well as Charon. 
Long Live Charon.

Cheers
Peter - MPC:E18




--- In guide-user@yahoogroups.com, "P. Clay Sherrod" <drclay@...> wrote:
>
> Please do NOT discontinue support for Charon.
>
> Dr. Clay
> _____
> Arkansas Sky Observatories
> MPC H45 - Petit Jean Mountain South
> MPC H41 - Petit Jean Mountain
> MPC H43 - Conway West
> http://www.arksky.org/
>
> ----- Original Message -----
> From: "Bill J Gray" <pluto@...>
> To: <guide-user@yahoogroups.com>
> Sent: Friday, November 06, 2009 9:50 AM
> Subject: Re: [guide-user] Charon
>
>
> > Hi Chris,
> >
> >    "...For some reason Charon believed the sun was up and that the
> > image was taken here (642)."
> >
> >    If that's what it says in Charon's settings menu,  then that's the MPC
> > code the program will use.  Unfortunately,  it can't get the MPC code from
> > the FITS header.  (Not in any reliable or standard way,  that is.  I'm sure
> > the MPC code is sometimes stored in FITS headers,  but I'd be gobsmacked
> > if any two programs stored them in the same way.  Setting it through Charon
> > is more reliable.)
> >
> >    I'm pleased to hear from some folks using the program.  Although I've
> > done very little except maintenance on it for some years,  I was tempted to
> > make a major change when John Greaves pointed out this paper to me:
> >
> > http://arxiv.org/abs/0910.2233
> >
> >    The program described in the article loads up an image and
> > automatically figures out where that image is in the sky,  given
> > a pretty rough estimate of the image scale.  I'd considered some
> > similar tricks long ago,  but didn't think it would run very
> > quickly.  Seems it's actually quite fast,  and I can see several
> > ways in which it could be both simplified and sped up.  The result
> > would be that Charon could be much more reliable and the need for
> > user control would mostly go away:  the program could run in an
> > almost totally automated fashion.  But it would be a _big_ project;
> > I doubt I'll do it any time soon!
> >
> > -- Bill
> >
> >
> >
> > ------------------------------------
> >
> > To unsubscribe from this group, send an empty email to:
> > guide-user-unsubscribe@...! Groups Links
> >
> >
> >
> >
> >
>

Hi Peter,  all,

     "...Another vote for : 'Please do NOT discontinue support for Charon.'"

     No worries;  I had,  and have,  no intention of doing so.

     There are definitely not many people using Charon.  (Though since this
thread began,  I've heard from many I didn't know about.)  But Charon
has been very easy to maintain.  Over the past few years,  all I've had
to do is to fix a bug or two and add support for a catalog or two,  and
answer a few questions about it.

-- Bill

...and we appreciate the continued support.  Small numbers do no necessarily
translate
into small accomplishments via Charon.

(Furthermore, we know you live very deep in the Maine woods and can find you
eventually if
you ever stop supporting it....[grin])

Dr. Clay
_____
Arkansas Sky Observatories
MPC H45 - Petit Jean Mountain South
MPC H41 - Petit Jean Mountain
MPC H43 - Conway West
http://www.arksky.org/

----- Original Message -----
From: "Bill J Gray" <pluto@...>
To: <guide-user@yahoogroups.com>
Sent: Monday, November 16, 2009 9:06 AM
Subject: Re: [guide-user] Re: Charon


> Hi Peter,  all,
>
>    "...Another vote for : 'Please do NOT discontinue support for Charon.'"
>
>    No worries;  I had,  and have,  no intention of doing so.
>
>    There are definitely not many people using Charon.  (Though since this
> thread began,  I've heard from many I didn't know about.)  But Charon
> has been very easy to maintain.  Over the past few years,  all I've had
> to do is to fix a bug or two and add support for a catalog or two,  and
> answer a few questions about it.
>
> -- Bill
>
>
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>
>

Bill,

I too am appreciative of your continued support of Charon. I may mess it up from
time to time but you have always been there to help me straighten it out,
Thanks!

--- In guide-user@yahoogroups.com, "P. Clay Sherrod" <drclay@...> wrote:
>
> ...and we appreciate the continued support.  Small numbers do no necessarily
translate
> into small accomplishments via Charon.
>
> (Furthermore, we know you live very deep in the Maine woods and can find you
eventually if
> you ever stop supporting it....[grin])
>
> Dr. Clay
> _____
> Arkansas Sky Observatories
> MPC H45 - Petit Jean Mountain South
> MPC H41 - Petit Jean Mountain
> MPC H43 - Conway West
> http://www.arksky.org/

Clear, Dark Skies!

Dave Birmingham

Birmingham Astronomical Observatory
Harvard MPC H53
Thompsonville, IL
37° 56' 28.7" N / -088° 46' 18.5" W
ele. 516 ft/ 157 m
12" LX200GPS s/n 05008
ASO SuperCharge # 243-2012
Main Imager SBIG ST-402ME-C1

When you right-click on a quasar, it gives you the redshift value.

Is there a chart somewhere, or an "easy" calculation to find out the approximate
light year distance?

For instance, Einstein's Cross, Q 2237+0305, it says a redshift value of 1.695.
How many millions (or billions) of light years is that?

Thanks!
Scott Kranz

Anybody have an updated ccds.nam file with the meade dsi's, orion starshoots and
atik's and others???????

Don

Hello Don

> Anybody have an updated ccds.nam file with the meade dsi's, orion starshoots
and
> atik's and others???????

mine is from 12.03.2009 with dsi and orion starshoots included but no atik:

Meade Deep Sky Imager            ICX054AL     9.6      7.5   510   492  146

Orion StarShoot (SSDSCI-I)       ICX259AK     6.5      5.25  752   582  133
Orion StarShoot (SSDSCI-II)      ICX429AKL    8.6      8.3   752   582  134

If you have the data of these cameras (pixel size and number of pixels) you can
include them by yourself. The "how to" is included at the bottom of the file.
But
don't forget to tell Bill of these new cameras so that he can include them in
the
next update.

Clear skies
Bernd

Bernd Brinkmann

Sternwarte Herne, MPC code A18
Herne, Germany

e-mail: info@...
http://www.sternwarte-herne.de

Hi Don,

     As Bernd indicated,  most of the cameras you mention are
included with the current software,  which I'd recommend getting
anyway just due to various bug fixes and improvements:

http://www.projectpluto.com/update8.htm

     That gets you everything but the Atik cameras.  A bit of searching
on their Web site got me some data,  but not all (I find camera
manufacturers are sometimes astonishingly bad about telling you the
dimensions of their CCD chips... something you'd expect most people
to want to know.)  But some Googling got me the rest of the sizes.
If you download

http://www.projectpluto.com/ccds.zip

     (about 21 KBytes) and unZIP it in your Guide folder,  you'll
have eight Atik cameras listed in the CCD Frame dialog.  (The
data for them is also shown below.)

-- Bill

Camera name                 CCD chip    pix size (um)  width height
Atik 16                     ICX429AL     8.6      8.3   752   582
Atik 16ic                   ICX424AL     7.4      7.4   660   494
Atik 16ic-s                 ICX415AL     8.3      8.3   783   582
Atik 16HR                   ICX285AL     6.45     6.45 1392  1040
Atik 314E                   ICX205AL     4.65     4.65 1392  1040
Atik 314L/L+                ICX285AL     6.45     6.45 1392  1040
Atik 4000/4000LE            KAI04022     7.4      7.4  2048  2048
Atik 11000                  KAI11002     9        9    4032  2688

Hi Scott,

     That question sounded vaguely familiar.  I dug through old e-mails
and found that I'd answered it for somebody back in 2005.  So I'll
recycle my answer.

     The only additional comment I'd make is that the Hubble Constant,
and therefore the age of the universe,  is now known to within about
one percent (as opposed to the five percent error in 2005).  The
improvement is mostly due to WMAP measurements.  To me,  it's pretty
amazing that we can know how old the universe is to that level of precision.

-- Bill

---------------------------------

     (Pause to do some on-line research... I'm not all that knowledgeable
about cosmology;  does that mean I'm not a cosmopolitan kind of guy?)

     Unfortunately,  Guide can't tell you that.  I ought to add in some code
to enable it to compute new numbers using those found in a catalog... but
at present,  it can just take the redshift and spit that out at you.
However,  there's another way to do it,  as follows.

     I eventually found some formulae (more on that below) which,  with a
modest bit of effort,  could be turned into the following table.  You can
interpolate within the table as needed.  For example,  an object with
z=.4 is receding from us at about one-third of the speed of light,  and
is about 1400 million parsecs or 4.5 billion light-years away. (Please
ignore the meaningless precision!  If the Hubble Constant really is
known to within about one part in twenty,  then these distances should
also be good to within one part in twenty.)

     z   vel        distance
      (% of c)   Mpc     Mlightyears
    0.1  9.5    401     1308
    0.2 18.0    761     2482
    0.3 25.7   1083     3530
    0.4 32.4   1369     4464
    0.5 38.5   1624     5294
    0.6 43.8   1850     6031
    0.7 48.6   2051     6687
    0.8 52.8   2230     7272
    0.9 56.6   2390     7793
    1.0 60.0   2533     8259
    1.5 72.4   3057     9967
    2.0 80.0   3377    11012
    3.0 88.2   3725    12145
    4.0 92.3   3897    12706
    5.0 94.6   3994    13021
    6.0 96.0   4053    13214
    7.0 96.9   4092    13341
    8.0 97.6   4119    13429
    9.0 98.0   4138    13492
   10.0 98.4   4153    13539

     Anyway.  My on-line research turned up a relationship between the velocity
v of the galaxy and its redshift z:

1 + z = sqrt( (1+v/c) / (1-v/c))

     which,  after a bit of algebra,  can be solved for v:

k = (z+1)^2
v = c (k-1) / (k+1)

     Then you can solve for the distance to the object using Hubble's Law:

D = v / H

     where D = distance in megaparsecs,  v = velocity in km/second,  and
H = Hubble's constant,  currently thought by at least some to be about
71+/-3.5 km/sec/Mpc.

-- Bill

Is there a way to update the variables listed in Guide8 to include the latest
79th Name-List of Variable Stars?

Chris. Spratt
Victoria, BC

ahhh thank you!  Exactly what I was looking for!



-scott


----- Original Message -----
From: "Bill J Gray" <pluto@...>
To: guide-user@yahoogroups.com
Sent: Monday, November 23, 2009 9:14:13 AM GMT -06:00 US/Canada Central
Subject: Re: [guide-user] quasar distances

 




Hi Scott,

That question sounded vaguely familiar. I dug through old e-mails
and found that I'd answered it for somebody back in 2005. So I'll
recycle my answer.

The only additional comment I'd make is that the Hubble Constant,
and therefore the age of the universe, is now known to within about
one percent (as opposed to the five percent error in 2005). The
improvement is mostly due to WMAP measurements. To me, it's pretty
amazing that we can know how old the universe is to that level of precision.

-- Bill

---------------------------------

(Pause to do some on-line research... I'm not all that knowledgeable
about cosmology; does that mean I'm not a cosmopolitan kind of guy?)

Unfortunately, Guide can't tell you that. I ought to add in some code
to enable it to compute new numbers using those found in a catalog... but
at present, it can just take the redshift and spit that out at you.
However, there's another way to do it, as follows.

I eventually found some formulae (more on that below) which, with a
modest bit of effort, could be turned into the following table. You can
interpolate within the table as needed. For example, an object with
z=.4 is receding from us at about one-third of the speed of light, and
is about 1400 million parsecs or 4.5 billion light-years away. (Please
ignore the meaningless precision! If the Hubble Constant really is
known to within about one part in twenty, then these distances should
also be good to within one part in twenty.)

z vel distance
(% of c) Mpc Mlightyears
0.1 9.5 401 1308
0.2 18.0 761 2482
0.3 25.7 1083 3530
0.4 32.4 1369 4464
0.5 38.5 1624 5294
0.6 43.8 1850 6031
0.7 48.6 2051 6687
0.8 52.8 2230 7272
0.9 56.6 2390 7793
1.0 60.0 2533 8259
1.5 72.4 3057 9967
2.0 80.0 3377 11012
3.0 88.2 3725 12145
4.0 92.3 3897 12706
5.0 94.6 3994 13021
6.0 96.0 4053 13214
7.0 96.9 4092 13341
8.0 97.6 4119 13429
9.0 98.0 4138 13492
10.0 98.4 4153 13539

Anyway. My on-line research turned up a relationship between the velocity
v of the galaxy and its redshift z:

1 + z = sqrt( (1+v/c) / (1-v/c))

which, after a bit of algebra, can be solved for v:

k = (z+1)^2
v = c (k-1) / (k+1)

Then you can solve for the distance to the object using Hubble's Law:

D = v / H

where D = distance in megaparsecs, v = velocity in km/second, and
H = Hubble's constant, currently thought by at least some to be about
71+/-3.5 km/sec/Mpc.

-- Bill




[Non-text portions of this message have been removed]

Thanks all,

Bill, at one time I took hours to collect all the cameras I could find
and add them(even if they matched another camera) and
then an update(i believe) overwrote the ccds.nam file I had worked on
and I didnt want to go through the effort again if there was someone who
added them all already

Thanks,
Don


Bill J Gray wrote:
>
>
> Hi Don,
>
> As Bernd indicated, most of the cameras you mention are
> included with the current software, which I'd recommend getting
> anyway just due to various bug fixes and improvements:
>
> http://www.projectpluto.com/update8.htm
> <http://www.projectpluto.com/update8.htm>
>
> That gets you everything but the Atik cameras. A bit of searching
> on their Web site got me some data, but not all (I find camera
> manufacturers are sometimes astonishingly bad about telling you the
> dimensions of their CCD chips... something you'd expect most people
> to want to know.) But some Googling got me the rest of the sizes.
> If you download
>
> http://www.projectpluto.com/ccds.zip
> <http://www.projectpluto.com/ccds.zip>
>
> (about 21 KBytes) and unZIP it in your Guide folder, you'll
> have eight Atik cameras listed in the CCD Frame dialog. (The
> data for them is also shown below.)
>
> -- Bill
>
> Camera name CCD chip pix size (um) width height
> Atik 16 ICX429AL 8.6 8.3 752 582
> Atik 16ic ICX424AL 7.4 7.4 660 494
> Atik 16ic-s ICX415AL 8.3 8.3 783 582
> Atik 16HR ICX285AL 6.45 6.45 1392 1040
> Atik 314E ICX205AL 4.65 4.65 1392 1040
> Atik 314L/L+ ICX285AL 6.45 6.45 1392 1040
> Atik 4000/4000LE KAI04022 7.4 7.4 2048 2048
> Atik 11000 KAI11002 9 9 4032 2688
>
>


[Non-text portions of this message have been removed]

C Spratt wondered :-

"Is there a way to update the variables listed in Guide8 to include the latest
79th Name-List of Variable Stars?"

The 79th Name List is completely subsumed within the latest iii.dat, and has
been for some time now, from the GCVS website or the B/GCVS version of it
(called something like gcvs.... something.dat).

Cheers

John

Wanna play with CoRoT stuff?  Well, it used to be a bit tedious, needing the
download of fits files from esoteric data servers, files best viewed in the java
app topcat or such, but now you can more or less play directly.

This came out recently

http://cdsarc.u-strasbg.fr/viz-bin/Cat?J/A%2bA/506/519

the data for a recent paper.  It's the N3 data release.  They've classified all
the exoplanet fields' variable stars, and they've even decided they're all
variable and invented new variability types at times.  ie as far as corot is
concerned, all the exoplanet field stars turned out to be variable at the
millimag or less capabilities corot has.

I dunno.  Sounds a bit iffy to me, but there are certainly real variables in
there.

Anyway, there's also a log file at vizier

http://cdsarc.u-strasbg.fr/viz-bin/Cat?B/corot

which is a bit out of date, as there are now data for around 39000 objects, but
a lot of the stuff is there (30,000 as of the mid 2009 corot update release,
it's the October short run data that's missing I think, which can be found at
the laeff and nasa servers for the truly keen).

That's the N2 data delivery, is the b/corot vizier logfile stuff.

I glued them all together a few weeks back to make a usable whole.  Because N2
is lagging at vizier compared to the direct data servers the file has stars with
no coords that won't be plotted, but otherwise it's there, and they can be glued
in when b/corot is updated.

To make access even easier, why not use Guide 8, I bethought.

The combined data and tdf can be found here

http://wikisend.com/download/571642/corot.tdf

you'll need cookies enabled, download the nigh on four megabytes of it and copy
to the Guide directory and (re)run Guide.

I didn't take all the N3 data columns, just the first guesses re variability
type and probability thereof, not the third or second.  The automated
identification system's first guess is wrong a lot of the time anyway, so no
need worrying about the more wrong guesses.  It's a look and see thing more than
anything.  I mean, when they class a star as M0 V and the first and most
probable classification picked is that of a BE variable star, you know one of
those data are going to be wrong.

Now, purple circles ring the corot stars involved for fields of one degree or
less, adjustable via right click and display.

Basic info is stuff like spectral type, main probable variability type (you'll
need to find the N3 paper, via the above N3 vizier readme to find a table of all
those, although most are standard acronyms seen before, or guessable acronyms
like "ecl" for eclipser, there's an astroph version linked via ADSABS) and the
probability of that variability type being valid.  There's the first (of three
in the full catalogue) probable period, amplitude thereof, and "fit" for said,
on a scale of 0 to 1, with 1 bestest, the 'fit' being an estimate of how the
model lightcurve based on the variability type assumption and the probable
period actually fits the true data.

The above tdf has coords within it so you can goto RA one of those to start off,
the field will be obvious once you get there (only small bits of sky involved
with CoRoT).

But goto tdf -> corot -> then entering a corot ID number works too.

In more info the red CoRoT link takes you to the above b/corot default short
entry for the object, and at the far right of that is the PLOT link for getting
to look at the lightcurve via a VizieR interface, which is adjustable, but a
little buggy at the moment (always defaults to red mag, even when it's the
monochromatic whiteflux being looked at and not the chromatic red, green and
blue fluxes).

If you click on the TS link you can download the fits file and examine corot HJD
versus flux in FV or Topcat or probably VOPlot or such, google for said if that
keen.

Fits files aren't small, and the chromatic ones can be quite big.

As an example let us play with CoRoT 102708916 which is one of the objects typed
as an eclipser with 100% certainty.

More Info has a link that launches this page in your web browser if clicked

http://vizier.u-strasbg.fr/viz-bin/VizieR?-source=B/corot/exo&CoRoT=102708916

Click the green background plot link at the endmost column to get this

http://cdsarc.u-strasbg.fr/viz-bin/vizExec/Vgraph?B/corot/102708916;ftp://ftp.ia\
s.u-psud.fr/corotpub/N2-1.0/2007/02/03/EN2_STAR_CHR_0102708916_20070203T130553_2\
0070402T070126.fits&

(url has wordwrapped, be careful with it)

and use inputs in X cuts and Y cuts and the axes values to zoom in and out, for
example :-

http://cdsarc.u-strasbg.fr/viz-bin/vizExec/Vgraph?cat=B%2Fcorot%2F.%2F102708916%\
3Bftp%3A%2F%2Fftp.ias.u-psud.fr%2Fcorotpub%2FN2-1.0%2F2007%2F02%2F03%2FEN2_STAR_\
CHR_0102708916_20070203T130553_20070402T070126.fits&LIST_Band=Red%3BGreen%3BBlue\
&Band=Red&P=0&-x0=2598&-x1=2606&--bitmap=600x600&-y0=100000&-y1=140000

wordwrapped again

Now, counts isn't very informative, so to get an uncalibrated rough instrumental
differential magnitude we'll reckon maximum for this object in the last zoom
link is 134000 counts, and we'll use that as the "normaliser", just for messing
around.

Then differential mag from that point is -2.5 x log10(counts/134000)

Deepest minimum reads off the axis something like 107000 so that's about 0.24
mags fainter.  And this is a relatively high amplitude CoRoT object, you'll find
plenty of stuff at around the millimag level.  But look at the detail on the
curve for that amplitude, and the tightness of it.  Bottom right is "data as a
table" link, so you can click on that look at the data, save it, shove it in a
spreadsheet, convert to differential mags or just leave it in fluxes, and make
up your own graphs.

Notice this randomly chosen object is not only an eclipsing binary, it's an
eccentric eclipsing binary, as evidenced by the secondary minimum not being
halfway between the two primary minima.

And if you're thinking you've seen just as nice a plot before, well, this isn't
a _phaseplot_, this is the continuous sequential raw observation time series!

Plot it up in a spreadsheet and you could do a good estimate of the period just
by reading off the minima here.

Lots of stars to play with and look at and see how CoRoT data really is. 
Whether the exoplanet stuff is included in there I know not, I dunno if any
transit have been found in the exo fields, or how many.

Cheers

John

Below is the tdf that'll let folk use the AAVSO VSX data as a Guide 8 file.

Beware wordwrap on the url.

Basically, you go here :-

ftp://cdsarc.u-strasbg.fr/pub/cats/B/vsx/

you downloads vsx.dat.gz, expands it if needs be into the Guide directory
(extract it like a zip file if it remains compressed after download and _ensure_
it's called vsx.dat and only that), and cut and paste the below tdf into a text
editor and save it as vsx.tdf in the Guide directory.

Said above b/vsx file is ostensibly updated somewhat regularly on the old
automatics like.

Pink labelled pink xes for fields of 2 degrees or less (adustable via right
click -> display).

Cheers

John

file vsx.dat
title VSX
RA H  42  9
units0 -2
de d  52  9
text  9  30
~b  9  30 %s\n\n
~b 40 0 0 Variable\n
~b 40 0 1 Suspect\n
~b 40 0 2 Nonvariable\n
~b 62  30 Type  %s\n
~r 42   9 \nRA  [2000]  %R\n
~r 52   9 Dec[2000]  %D\n\n
~b 94  11 Max mag %s\n
~b109 0   Min mag %[110,11]\n
~b109 0 ( Amplitude %[110,11]\n
~r125  13 \nEpoch HJD %s
~b139  20 \nPeriod %s days
~b 45   1 \n\n
~r  1   7 ^Online
Data//xhttp://www.aavso.org/vsx/index.php?view=detail.top&oid=%s^\n

epoch 2000
sort 1
type sCb4abfe;x16
label spaces
goto spaces
goto case
field 0.00 20.00
shown 0
end

Now, this is a bit newer.  Around early November data started being made
available from the NASA MAST server

http://archive.stsci.edu/kepler/data_search/search.php

and you'd to play around with that, and something called ST-DADS used by MAST,
to select and "order" fits files which could then be downloaded via anonymous
ftp, either via an ftp client or possibly via a browser (I didn't check that
though).

Some of this could be automated via direct HTTP GET, but about a week ago they
added an on the fly web lightcurve plotter, so quicklooks can be done without
dealing with ftp or fits files unless you want to.

Initially a few weeks back I obtained data for about 6500 of the public objects,
since then more public objects have been released, giving a total of 7500
according to the mast server, although noises made by press releases quote 8500
for some reason.  This stuff only spans about nine and a half days, and looks to
be the commissioning stuff, and most certainly appears to have had all the
interesting stuff kept back.  Not just lightcurves.  For instance, it is claimed
it is no use for looking for planetary transits within it as they are variable
stars, or variable lightcurves at least.  This implies all the variable stars
have been released.  Ain't so, there has to be a bunch of periodic variable
stars that haven't been released, both new discoveries and also definitely many
known variable stars in the field quite coincidentally have no public data for
them.

Whatever, if you want to look at it, Guide will let you.

I took fields of relevant data and attached a TDF to it.  This data the Kepler
people call "browse quality data".   Mostly to cover themselves I surmise, but
it does allow folk to have a butcher's hook.  Note that no formal use of the
lightcurve data in any publication or website or maillist is permitted until mid
January next year, as firmly stated on the MAST pages help etc.

The tdf for this one is at

http://wikisend.com/download/205410/kepler.tdf

and can be downloaded into the Guide 8 directory.

Purple circles can be right clicked on for more info, and a link followed to get
to a page of Kepler lightcurve data which I can't give an example of here coz it
ain't mid Jan 2010 yet.

Try the object for this coord 18 40 08.16 +43 34 34.4 to find the field.

Once you get to the webbrowser webpage "mark" the object via the tickbox.  If
there's another entry, in yellow with an @ symbol, that's "proprietary" so you
ain't allowed to play with that, it isn't public yet.  Just the other stuff.

There are two topmost buttons.  Submit marked data for retrieval from STDADS
will eventually get you to something that'll let you order a fits file of the
lightcurve data downloadable via ftp client, and viewable in topcat etc, if tick
boxes and proper route followed, and all very pedantic and bothersome, so I
mention it only for the truly keen, who are on their own re figuring it out
(you've gotta wanna).

The "Plot marked spectra" actually generates a lightcurve, a "time series"
spectrum.  Not a spectrum spectrum.  So if you mark it and tick that you get a
graph, the lightcurve or electrons per cadence (kind of like a flux) over
seconds of time (total duration about nine and a half days).

The above coord object turned out to be an IRAS source and looks and is
apparently spectrum K2 according to some catalogues, so it might be an LPV.

Dunno, the "variability" in Kepler rarely looks like that in CoRoT, but I think
that's because the lightcurve data is at an earlier stage of processing in the
newer satellite mission.

Anyhow, if you wish to look at Kepler lightcurves quick and easy, Guide will do
it for you, just go to the Kepler fields and with the above TDF, right click,
More Info, click the red KEPLER Link, look in opened browser window, tick the
tick box (ie mark the lighcurve), and Plot Marked Spectra, and get a graph which
has some adjustable options, and a HELP link too I just notice.

As more data is released the above tdf can be expanded by just adding data to
from the MAST data search, though likely it'd be best to start off with a new
set of objects.

It'll give an idea of what Kepler is spitting out and how it looks though
without having to learn how to use fits files, run java apps, or download from
ftp sites.  And all just simply from scanning around in Guide, with no input
forms to wrestle with.

Cheers

John

I would like to ask a question, I use Guide Version 8 in my windows XP but know
just tried to install it in my new HP computer with Windows 7 (64 bit) and it
would not install. do I need to download a new driver for Windows 7.... Thanks
from Texas

So far,  the only issue with Windows 7 (that I know of!) is one
that also caused some trouble for some people in Vista:  the 'setup'
program fails.  The fix for this is described (and a revised 'setup'
provided) at

http://www.projectpluto.com/setup.htm

     If anyone else runs into Win7 issues,  please let me know.

-- Bill

Bill,

The same tool bar button problem seen on Vista is on W7. Turn off the
Themes off in icon properties and all will work fine.

Denis

Bill J Gray wrote:
>     So far,  the only issue with Windows 7 (that I know of!) is one
> that also caused some trouble for some people in Vista:  the 'setup'
> program fails.  The fix for this is described (and a revised 'setup'
> provided) at
>
> http://www.projectpluto.com/setup.htm
>
>     If anyone else runs into Win7 issues,  please let me know.
>
> -- Bill
>
>
> ------------------------------------
>
> To unsubscribe from this group, send an empty email to:
> guide-user-unsubscribe@...! Groups Links
>
>
>
>

Thanks Bill on the new setup for Windows 7, I did what you said and everything
is OK... Once I started the Guide 8 program I did have to press ENTER to redraw
the screen. It came right up....Thanks again....

--- In guide-user@yahoogroups.com, Bill J Gray <pluto@...> wrote:
>
>     So far,  the only issue with Windows 7 (that I know of!) is one
> that also caused some trouble for some people in Vista:  the 'setup'
> program fails.  The fix for this is described (and a revised 'setup'
> provided) at
>
> http://www.projectpluto.com/setup.htm
>
>     If anyone else runs into Win7 issues,  please let me know.
>
> -- Bill
>

"...Once I started the Guide 8 program I did have to press ENTER
to redraw the screen."

     Wups!  I see the 'setup.htm' page says that this is an unresolved
issue.  I've revised that text to read:

    "...A couple of users are reporting that when Guide starts up,  it
doesn't show a chart.  Then you hit Enter,  or zoom in or out,  or do
anything else that would normally cause the chart to be redrawn,  and
you're back on track.  The currently-posted version of Guide has a fix
for this;  you can click here for the current version."

     ...which then links to http://www.projectpluto.com/update8.htm .
Thanks for mentioning this.

-- Bill

Hi Bill,

If I turn proper motion off with "ALT-J 11" as you say in your
update, how do I recover it?  It would be ineresting to watch
binaries, and Jupiter's satellites revolve in orbit, but because all
my work is with BCE eclipses I don't want to risk losing the feature.

Larry



Laren Dart
http://ldart.got.net



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 091126-1, 11/26/2009
Tested on: 11/26/2009 2:57:57 PM
avast! - copyright (c) 1988-2009 ALWIL Software.
http://www.avast.com

Alt J entries are usually toggles, so if alt J 11 turns something off, alt J 11
turns it back on, and the reverse.

Try it and see.

Cheers

John

Hi John

Thanks for the quick response.  I thought that was the case, but I
have forty years of research notes on this computer, and I'm paranoid
about trying anything I'm not absolutely sure about.  I do have a
good external BU drive, but still...   :-)

Larry

At 03:36 PM 11/26/2009, you wrote:

>Alt J entries are usually toggles, so if alt J 11 turns something
>off, alt J 11 turns it back on, and the reverse.
>
>Try it and see.
>
>Cheers
>
>John


Laren Dart
http://ldart.got.net



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 091126-1, 11/26/2009
Tested on: 11/26/2009 11:34:51 PM
avast! - copyright (c) 1988-2009 ALWIL Software.
http://www.avast.com