Otherware/Otherware_1_SB_Development.iso/amiga/system/sphinx.lzh/SPHINX2.5y/Docs/Setup.doc

Text File | 1992-01-10 | 7.0 KB | 159 lines

                  Sphinx.doc v2.5b
         ⌐ 1991, Nicolas Dade. All Rights Reserved
 permission is hereby granted for non-commercial duplication and distribution
          doc file for the SPHINX: AmigaDOS device
 last revised: June 20th, 1991


NOTE: this recipe is for a typical machine, which has not been over config-
ured by its user. if this is not the case, either you made your machine the
mess it is yourself, and can reinterpret these instructions, or someone else
did it for you, in which case you are just going to have to find that person
and beg.

to update SPHINX from version 2.4 or 2.4b to version 2.5b:

1  copy the new Sphinx-Handler to L:
2  copy the new SPHINXConfig editor to where ever you are keeping it
3  load the v2.4 configuration file into SPHINXConfigv2.5b, edit the new
   fields, and save it, thereby creating a v2.5 configuration file.
end

NOTE: if you then wish to try out the new SPHINX, but have given it a name
of a SPHINX that has already been mounted into the machine, you will have to
follow the instructions for restarting SPHINX, below.


to set up SPHINX on your machine if you don't already have SPHINX set up:

1  copy Sphinx-Handler to L:
2  create a configuration file using SPHINXConfig by starting SPHINXConfig
   running, editing what you want to change, and then pressing [Save v2.5]
   (see SPHINXConfig.doc for more).
3  either
  3.1 using a text editor add to your MountList (devs:MountList) an entry
      for SPHINX. (see Section II)
   or
  3.1 using a CLI append the file MountList.SPHINX to your MountList
   or
  3.1 just copy the file MountList.SPHINX to devs: and in part 4 add
      the text
      Mount SPHINX: from devs:MountList.SPHINX
4  edit your startup-sequence or user-startup, using a text editor, adding
   to it
   Mount SPHINX:
   (try to put this next to where you mount NEWCON:)
5  either
  5.1 copy the file SShell.info to where you keep your Shell's icon, either by
      dragging the icon with WorkBench or copying SShell.info with some other
      program.
  5.2 select this icon and chose Info from Workbench's menu
  5.3 under DEFAULT TOOL, type in the shell you wish to pair up with this icon
      (if you wish to have different shells available, make one SShell icon
       for each shell)
      If you are not sure what shell you are using or what it is named, first
      look at what your current shell icon is using, and use the same.
  5.4 If you like, edit the tooltype WINDOW so that the window comes up with
      the title and position you desire (NOTE: even if the current window
      position & size are not possible, it is all right--SPHINX will realize
      this and adjust)
   or
  5.1 duplicate your Shell's icon (Shell.info)
      (you may need to use a CLI, WorkBench1.3 will not copy an icon if it
       can't find a corresponding file, but if you dislike CLIs, try using
       WorkBench first)
  5.2 select this duplicate's icon, and chose Info from Workbench's menu
  5.3 either there is a TOOL TYPE called WINDOW, in which case
    5.3.1 replace `NEWCON:' or `CON:' or whatever window handler you are
      using with `SPHINX:'
      or
    5.3.1 click on [ADD], then type in:
      WINDOW=SPHINX:0/0/1000/1000/MySphinxShellWindow
      or similar (change the window's position, size and title at your
      whim)
end


if you want to try sphinx out right away (without rebooting):

1  if you haven't set SPHINX up, follow the instructions above for setting
    SPHINX up.
2  open a CLI or Shell that does NOT use SPHINX: and type
    Mount SPHINX:
   (or `Mount SPHINX: from devs:MountList.SPHINX' if you just copied the file)
3  either
  3.1 double-click on the SPHINX shell icon you created
      if everything goes well, a window should open and print out SPHINX's
      startup message (because this is the first SPHINX window), then the
      shell's startup message, and then a prompt.
   or
  3.1 type `newshell SPHINX:0/0/1000/1000/NewSphinxShellWindow'
end


if while SPHINX is starting up it detects a condition that will keep it from
running on your system (i.e. a lack of memory, can't open window, can't find a
usable font, etc...) then it will show you an alert. There is nothing
harmfull about this alert; just use the alert code (the four letter string)
and look it up in the SPHINX alert table in Section I. If you can correct the
error (the chart contains suggestions about this), then do so and then try
starting SPHINX again, as described below.

NOTE: the startup code in SPHINX has been modified so that if a startup is
not successfull, it can be tried again and again until it is, without
restarting the handler. However opening the window and the fonts is NOT
part of the startup code; if this fails and you want to try it again, you
should restart SPHINX.

to restart SPHINX on a machine that already has a SPHINX of that name mounted:

open a CLI and type first
 assign SPHINX: remove
,then
 mount SPHINX:
,substituting for `SPHINX:' whatever name you have given this SPHINX, and
then start SPHINX running using whatever program with which you are paring
it (this is what you do when you double-click on the SPHINX shell icon).


If you have a program that currently uses CON or NEWCON and you would like to
try it with SPHINX, there are two possibilities.
   if the program lets you choose who handles its window, like the shell
   did (see above), then just change the `CON' or `NEWCON' to `SPHINX' (just
   as you did with the shell).
or
   if the program is "hard coded" to use CON or NEWCON, then the device name
   probably appears some place in the program. Using a file editor (like
   DiskX or FedUP), (and, for those of you who use PowerPacker, a
   decompressed version) search for the string `CON:' or `NEWCON:', and
   replace those characters with, say, `SPX:' or `SPHINX:' (or anything with
   the appropriate number of characters. Then make a configuration file and a
   mountlist entry for the SPHINX, mount the SPHINX, and start the modified
   version of the program running. If the program isn't using CON/NEWCON's
   more complex commands, everything should be fine.


If you want more than one SPHINX (because you want windows with different
configurations), chose a device name that hasn't been used yet, and repeat
the steps for setting SPHINX up from scratch with it, replacing everywhere
there is the string `SPHINX' your new name.
The new SPHINX can still used the same handler, L:Sphinx-Handler, but will
need a new name, mountlist entry, configuration file, and `Mount NAME:' in
the startup sequence (and, if you are using this new one for a shell, a new
icon).

There is no need to have a SPHINX called `SPHINX', it is just the suggested
name.

I suggest that you use either the cursor shape or the window border colors
or input text color to differentiate differently configured SPHINXs.
The differently configured SPHINX will load its own copy of Sphinx-Handler,
which, once it is started, will discover the first copy, delete most of
itself, and start using the code of the first copy of Sphinx-Handler. This
way differently configured SPHINXs don't cost very much in terms of memory
(about 500 bytes of local code & data,+the stack and the memory used by the
window).