                ___  _ _                        _____ ___   ___ 
               / _ \| | | ___  __ _ _ __ ___   |  ___/ _ \ / _ \ 
              | |_| | | |/ _ \/ _` | '__/ _ \  | |_ | |_| | | | |
              |  _  | | |  __/ (_| | | | (_) | |  _||  _  | |_| |
              |_| |_|_|_|\___|\__, |_|  \___/  |_|  |_| |_|\__\_\
                              |___/ 



   What is Allegro?

      See readme.txt.


   Where can I get it?

      From any SimTel mirror, in the directory gnu/djgpp/v2tk/, or from the 
      Allegro homepage, http://www.talula.demon.co.uk/allegro/.


   How do I use it?

      See allegro.txt.


   What is DJGPP?

      An MSDOS port of the GNU C/C++ compiler, by DJ Delorie and friends. 
      Great stuff...


   Where can I get it?

      From any SimTel mirror, in the directory gnu/djgpp/, or from DJ's 
      site, http://www.delorie.com/djgpp/.


   How do I use it?

      See the readme.1st file that comes with djgpp. Most of the problems 
      that people have with Allegro are due to them not installing djgpp 
      correctly, so please do be sure to read this!


   I'm confused by the installation instructions in readme.txt. What is this 
   make.exe program I'm supposed to run?

      Make is part of the standard djgpp distribution, in v2gnu/mak*b.zip 
      (whatever the latest version number is). You should get this from 
      wherever you got djgpp.


   Make doesn't work properly.

      Are you sure that you have installed djgpp correctly? Check the 
      instructions in the djgpp readme.1st file, and in particular confirm 
      that you have set the DJGPP environment variable and added the 
      djgpp\bin directory to your path.


   My djgpp installation is fine, but make still doesn't work properly.

      Are you sure that you are using the GNU make program, and not some 
      other version like the Borland one? If in doubt, run "make -v" and 
      check that the GNU copyright message is displayed.


   When I run make, it asks me for some parameters. What do I type?

      You shouldn't be running make from the Win95 explorer! Bring up a DOS 
      box, change to your Allegro directory, and type "make" at the command 
      prompt.


   When I run make, it says "makefile has modification time in the future".

      Are you sure that your system time and date are set correctly?


   When I run make, it says "virtual memory exhausted".

      As the error message suggests, you need to provide more memory for the 
      compiler to use. The go32-v2 program will tell you how much is 
      currently available. If you are running under DOS, try to free up more 
      disk space for use as a swapfile. When using win95, increase the DPMI 
      memory limit in the properties for your DOS session to 65535 (you'll 
      have to type this in by hand, because the pull down list doesn't go 
      above 16384).


   When I run make, it says "reloc refers to symbol 'bss' which is not being 
   output".

      This seems to be a problem with the replacement linker from the 
      RSXNTDJ package. Either go back to using the standard djgpp linker, or 
      remove the "-s" flag from the Allegro makefile. If anyone knows why 
      this happens, and how I can avoid it, I'd like to know about it!


   Even though I included allegro.h, when I try to compile a program using 
   Allegro, I get lots of errors like:
   C:\TEMP\ccdaaaaa(.text+0x9):x.c: undefined reference to `allegro_init'
   C:\TEMP\ccdaaaaa(.text+0xe):x.c: undefined reference to `install_keyboard'

      You haven't read the docs, have you? :-) You need to link your program 
      with the library file, liballeg.a. First, make sure you have installed 
      everything properly (running make should do this for you). Second, if 
      you are compiling from the command prompt or with a makefile, add 
      -lalleg to the end of your gcc command line, or if you are using 
      Rhide, go to the Options/Libraries menu, type 'alleg' into the first 
      empty field, and make sure the box next to it is checked.


   I'm trying to compile the grabber, but it doesn't work!

      The grabber needs to be linked with the code in datedit.c. But you 
      shouldn't have to worry about doing this by hand: just run "make" and 
      that will build everything for you.


   I give up: I can't compile this! Please can you send me a precompiled 
   version?

      No, sorry. For starters, liballeg.a is about 450k, but you'd probably 
      also want  various utilities like the grabber, sound setup, etc. And 
      what about all the example programs? If I included compiled versions 
      of everything, a binary distribution would be over 7 megs: way too big 
      to be practical! More seriously though, there just isn't any reason 
      why you can't build it yourself. A compiler is a deterministic 
      process: given a particular input file and command line, it will 
      always produce the same output. If this isn't working, you either have 
      the wrong input files (ie. your copy of Allegro is broken in some 
      way), or the wrong command line (it is hard to see how that could 
      happen, since all you have to do is type "make"...) or your compiler 
      is broken, ie. you didn't install djgpp properly. You need to find and 
      fix the problem, not just sweep it under the carpet by getting someone 
      else to compile Allegro for you...


   Can I use Allegro with my Microsoft/Watcom/Borland compiler?

      Nope.


   Can I use Allegro to write programs for Linux or DirectX?

      Yes. It has been ported to run under win32 using DirectX, and to the 
      Linux X-Windows system. See the Allegro homepage for links to these 
      versions, and the latest information about any other porting projects.


   Does Allegro work under Windows NT?

      Your mileage may vary. Some people have reported problems, while 
      others say that it works fine. I don't have access to NT myself, so 
      there is nothing I can do about it either way, and to be honest I 
      don't care very much :-) If you want to run DOS programs, use DOS!


   Does Allegro work under OpenDOS?

      Yes, but with some caveats. If you are using the OpenDOS version of 
      EMM386, you must disable their DPMI implementation (specify DPMI=OFF 
      on the EMM386.EXE device line in your config.sys). You should also 
      make sure the PIC=OFF flag is set, but this is the default so it won't 
      be a problem unless you have specifically enabled it.


   What is this "Allegro WIP" that I see people talking about?

      WIP stands for "work in progress", and refers to any changes that are 
      more recent than the last official release. WIP versions of the 
      library can be obtained as patches from the Allegro website, and are 
      usually quite stable, although obviously not so well tested as a final 
      release version.


   I got the WIP patch, but I can't apply it.

      Do you have a copy of patch.exe? If not, go and get it from the same 
      place that you downloaded the rest of djgpp: this tool is a standard 
      part of the compiler distribution. If you do have the patch program 
      but it isn't working properly, make sure that you are installing the 
      patch over the top of an unmodified copy of whatever Allegro version 
      it is intended to update (this will usually be the most recent 
      official release from before the WIP was made, but check the text file 
      that comes with the WIP to be sure). Also, if you are using long 
      filenames under win95 it is important to be consistent, ie. if you 
      have set the LFN environment variable you must be sure to use a 
      LFN-aware unzip program, or if you use an unzipper that truncates the 
      filenames you must clear the LFN variable as well.


   How can I extend the 256k limit on Mode-X video memory? I have two megs 
   in my card.

      You can't. The limit is imposed by the VGA hardware, not by Allegro. 
      To access more than 256k of video memory you need to use an SVGA mode, 
      which means either switching to a higher resolution or getting a copy 
      of the SciTech Display Doctor, which provides several low resolution
      SVGA modes.


   How can I display several different images at the same time? When I show 
   the second one it messes up the palette for the first.

      That is how the video hardware works: there can only be one palette in 
      use at any given moment. Either convert your images so that they all 
      use the same palette (see the Allegro homepage for some utilities that 
      can help with this...) or switch to a truecolor graphics mode.


   My colors always come out wrong. And how can I make a greyscale palette 
   with 256 different shades?

      The VGA hardware only uses 6 bits for each color component, which 
      means the red, green, and blue values in the palette structure range 
      from 0 to 63, not all the way up to 255. That gives you a potential 
      2^18 = 262144 different colors, or 64 shades of grey. If you need more 
      than this you could try using VESA function 0x4F08 to select an 8 bit 
      wide DAC, but Allegro doesn't support this directly and I don't know 
      how reliable it will be across different hardware.


   How can I make parts of my sprite transparent in truecolor modes? I don't 
   understand what the docs mean by "bright pink"...

      In your favourite paint program, get hold of the RGB sliders and drag 
      the red and blue ones up as far as they go (usually to 255, but this 
      will depend on what units your software uses), and the green one right 
      down to zero. The result is a special shade of Magic Pink, or as some 
      people prefer to call it, magenta.


   The textout() function doesn't work after I use any of the GUI routines!

      One of the GUI objects has changed the text_mode() setting while it 
      was drawing itself. Call text_mode() again to select whatever 
      background color you want to use.


   I can't get the 3D polygon functions to work!

      Remember that the vertex positions are stored in fixed point format, 
      so you must use the itofix() macro or shift your coordinates 16 bits 
      to the left.


   I can't get the rotate_sprite() function to work!

      Remember that the angle of rotation is stored in fixed point format, 
      so you must use the itofix() macro or shift your coordinates 16 bits 
      to the left. For example, rotate_sprite(bmp, spr, x, y, itofix(32)) 
      will rotate the graphic by 45 degrees.


   Should I use regular bitmaps, RLE sprites, or compiled sprites?

      It depends on exactly what you are doing. If your images are totally 
      opaque, there is no advantage to using an RLE sprite, and it will 
      probably be faster to use a regular bitmap with the blit() function. 
      If your graphics contain masked areas, an RLE sprite will almost 
      always be both smaller and faster than the draw_sprite() function. 
      Compiled sprites are in general quite a bit faster than both the 
      others for masked images, and slightly faster for opaque graphics, but 
      this is far more variable. They are at their best with small sprites, 
      on older machines and in mode-X, and may actually be slower than 
      blit() when using SVGA modes on a pentium (the large size of a 
      compiled sprite is very bad for the cache performance).


   How can I make my game run at the same speed on any computer?

      You need to make sure the game logic gets updated at a regular rate, 
      but skip the screen refresh every now and then if the computer is too 
      slow to keep up. This can be done by installing a timer handler that 
      will increment a global variable at your game logic speed, eg:

      volatile int speed_counter = 0;

      void increment_speed_counter()
      {
         speed_counter++;
      }

      END_OF_FUNCTION(increment_speed_counter);

      void play_the_game()
      {
         LOCK_VARIABLE(speed_counter);
         LOCK_FUNCTION(increment_speed_counter);

         install_int_ex(increment_speed_counter, BPS_TO_TIMER(60));

         while (!game_over) {
            while (speed_counter > 0) {
               update_game_logic();
               speed_counter--;
            }

            update_display();
         }
      }


   How can I take a screenshot of my Allegro program?

      Add a call to save_bitmap() somewhere in your code. See the 
      save_bitmap() documentation for a discussion of one common pitfall 
      when doing this, and some example code.


   How can I generate a random number?

      Call srandom(time(NULL)) at the beginning of your program, and then 
      use random()%limit to obtain a pseudo-random number between 0 and 
      limit-1.


   Why not use some sort of dynamic linking system for the graphics and 
   sound drivers?

      The VBE/AF interface already provides this for the video drivers: see 
      the FreeBE/AF project on http://www.talula.demon.co.uk/freebe/. For 
      more general things like the sound, VESA, and mode-X routines, this 
      would be very difficult to do because the drivers depend on a lot of 
      helper functions from the core lib. The djgpp DXE format is nowhere 
      near flexible enough to support this, and I don't want to make Allegro 
      dependent on any other dynamic linking packages.


   Why not make a "lite" version of Allegro? I don't need any of the sound, 
   maths, or GUI routines...

      There is no need. The linker will only include the parts of the 
      library that you actually use, so if you don't call any of, say, the 
      texture mapping or FLIC playing functions, they will be left out of 
      your executable. This doesn't work perfectly because a lot of the 
      Allegro code uses tables of function pointers that cause some 
      unnecessary routines to be linked in, so the majority of the graphics 
      functions will be included in every executable, but I have tried to 
      keep this to a minimum. See allegro.txt for information about more 
      precise ways to remove some of the graphics and sound drivers.


   Will you ever add support for 3D accelerator hardware?

      No. I think this sort of hardware support would be most useful as part 
      of a proper 3D API, which Allegro is not, and will never be. If you 
      want to do some work on this, the MESA library (a free implementation 
      of OpenGL) is IMHO the place to start.


   Why not add a MOD playing function?

      Several very good ones already exist, for instance the JGMOD package. 
      See the links on the Allegro website.


   Why not add networking support?

      That would be a lot of work, and I don't have time to do it myself. 
      There are several networking packages currently in development or 
      floating around on the net, though, and in my opinion this sort of 
      code is more useful as an external library than it would be as part of 
      Allegro.


   Why can't Allegro read GIF files?

      Unisys has a patent on the LZW compression algorithm that is used by 
      the GIF format. I want everything in Allegro to be freely usable 
      without any restrictions whatsoever, which means I can't include any 
      code that is subject to licensing or the payment of royalties.


   Does Allegro work with the SB-Live soundcard?

      Apparently not. Hopefully someone will soon write a driver to fix this 
      problem, but if you are getting really impatient, lend me your 
      PC+soundcard and I will do it myself.


   Why doesn't it work with my video card?

      Try using a FreeBE/AF driver (http://www.talula.demon.co.uk/freebe/), 
      or the commercial SciTech Display Doctor (http://www.scitechsoft.com). 
      If it still doesn't work, post a description of your problem to the 
      Allegro mailing list, along with a copy of the output from running the 
      afinfo and vesainfo programs.


   My program crashes all the time. Could this be a bug in Allegro?

      Perhaps. Try to isolate the smallest fragment of code that is able to 
      reproduce the problem, and I'll have a look at it. If you can send me 
      a 10 line program, I will fix it. 100 lines, and I can probably fix 
      it. 1000 lines, and I don't have a chance :-)


   Can I use Allegro in my <whatever> commercial application?

      Sure. See the giftware terms in readme.txt. I don't mind what you do 
      with it, and there are no problems with commercial usage.


   When will <foobar> be finished? I can't wait...

      Whenever it is done! A little encouragement is always welcome, but I 
      don't have any completion deadlines and I'm not going to make one up 
      for you :-) As soon as it is finished, it will be released.


   Where can I get some fonts to use with Allegro?

      The grabber can import directly from GRX or BIOS format .fnt files, or 
      you can draw them onto a .pcx image using any paint program. See the 
      Allegro website for a utility (ttf2pcx) that will convert Windows 
      TrueType fonts into this .pcx format.


   Where can I find a set of instrument samples for the DIGMID driver?

      See the Allegro homepage for some links. You can use Gravis patches 
      (.pat format), or SoundFont 2.0 (.sf2) files, but the latter must be 
      converted into a patches.dat file with the pat2dat utility.


   How can I convert the documentation into Windows Help format?

      You need to download the makertf conversion utility 
      (ftp://ftp.coast.net/Coast/win3/winhelp/mkrtf104.zip), and the Windows 
      Help compiler (ftp://ftp.microsoft.com/Softlib/MSLFILES/HC505.EXE). 
      Make a temporary directory, copy the allegro.txi file from the 
      allegro/docs dir, and run the commands "makertf --no-warn allegro.txi 
      -o allegro.rtf -J allegro.hpj" followed by "hcp allegro.hpj". The 
      second command will give a lot of warnings, but they can safely be 
      ignored.


   How can I print out the documentation?

      The allegro.rtf file can be read directly into Microsoft Word and 
      printed from there, but you should right-click and update the table of 
      contents and index fields to fill them with the correct data first. 
      Alternatively you can install the TeX package and use the tex and 
      dvips programs to convert allegro.txi into Postscript format.


   Where can I find example source code and add-on packages?

      Check the Allegro homepage, http://www.talula.demon.co.uk/allegro/.
      If you have anything to add to this, please send me the URL!


   Why is it considered good coding practice to define PI as a constant, 
   rather than just using the value 3.141592 in my code?

      It simplifies the maintenance of your program, in case the value of PI 
      ever needs to be changed. Also it will make your program more portable 
      to other compilers that use different values of PI.


   I'm still confused. Where can I get help?

      See http://www.talula.demon.co.uk/allegro/maillist.html.



