Joe Mize Feb 13, 2000
> .... and one minor change in Ax.0 handling,--
> it's the same as the 30 January version. (More on that one minor change
> below.)
> SAx.0 USAGE:
>
> A warning: display of Ax.0 data using lines such as
>
> A1_PATH=14.3;e:\Usnosa10
>
> in GUIDE.DAT, and display of Ax.0 (or SAx.0) using the "Get A1.0/A2.0
> Data" function in Extras, are two very different things, independent of
> one another.
>
> The first only works with A1.0 and A2.0; you cannot get it to understand
> an SAx.0 disk. When used with Ax.0, though, it will display data from
> that catalog whenever your limiting magnitude is (in the above case) fainter
> than 14.3. The data just "appears", with no extraction step needed. You
> can use a full path specifier, as in the above case.
>
> The second method, the "Get A1.0/A2.0 Data" function, used to be the
> _only_ method, and it's the one Joe Mize should use, because it's the
> only one that will let him get data from SAx.0. It's intended to extract a
> small chunk of SAx.0 or Ax.0 data from a CD-ROM for display in Guide.
>
> I agree with Denis Boucher; Guide is probably trying to get the data
> from the wrong drive. To check this, edit the file STARTUP.MAR and look
> for this line:
>
> 63 real CD e
>
> Change the 'e' to match the actual letter of the hard drive. Because
> it's CD-ROM oriented, it does expect that you'll be just giving a letter;
>
> 63 real CD e:\Usnosa10
>
> won't work.
>
> You have a lot of company in running into this problem. After sending out
> plenty of e-mails describing it, I've done what I should have done in the
> first place, and made it possible to select the drive from inside the
> "Get A1.0/A2.0" dialog box. That's the "one small change" I mentioned in
> the first paragraph.
>