
                        DOCUMENTATION OF THE CT2

                     February 2000 - Rodolphe Czuba


PLEASE, BEFORE YOU DECIDE TO PRINT ON PAPER THIS FILE, ASK YOU IF YOU COULD 
NOT AVOID THAT ! READ THIS FILE ON THE SCREEN IN NORMAL CT2 MODE !
REDUCE THE PAPER CONSUMPTION OF THE PLANET !
THINK ABOUT OUR PLANET FOR THE NEXT GENERATIONS OF PEOPLE (your children) 
AND THE ANIMALS WHO NEED FORESTS, EVEN IF YOU THINK YOU DON'T NEED !


IMPORTANT                                                                   
Don't ask assistance from us if you don't read this !                                                                   

                                                                   
-------------------
Material overview :
-------------------

  The CT2 offers two modes: NORMAL and TURBO. The NORMAL mode permits
to keep a Falcon 100% as origin, except that the DSP IRQ is not wired (see 
below). 

The small following chart gives features (in MHz) of the 2 modes.

              NORMAL          TURBO

CPU             16              50
BUS             16              50
FPU      	32              50
DSP             32              50
Fast-RAM        no              50
VIDEL (Int)     32              50
VIDEL (Ext)     32              32    (with hardware fitting last manual)


  The CT2 contains what is called 'the DMA' modification destined
to CUBASE AUDIO. This last works perfectly in  TURBO mode !

  The TURBO mode is possible in VGA resolution, but also in  RVB and MONO ST
(SM12x/144) thanks to the attendance of a 32 MHz clock on the EXT entrance of
VIDEL, the SETUP being in charge of commuting the VIDEL on this External clock
after having detected a RVB screen or SM124.  It is possible to DISABLE this
  External clock from the SETUP if you  are in TURBO and with a small software
in the AUTO directory if you are in NORMAL mode (EXCLKOFF.PRG).

 Two things differentiate a Falcon from an another with a CT 2 in 
 NORMAL mode :
 
 - the interruption coming from the DSP is not wired and can block a program
   using it. To use this rare kind of software you need to put a patch 
   (DSP_IRQ.PRG) in the AUTO directory (behind your debugger if you use one!).
   In this mode, do not forget to remove wait-states on the DSP in the F7 set up.
 
 - the coprocessor is 32-bit wired (16-bit on basic Falcon) and it run up to
   32 MHz (instead 16 MHz on basic Falcon) -> about 15 % better.


-------------------
Software overview :
-------------------

  On the CENTurbo II, it is possible to start several ways:

  - NORMAL mode.
  - TURBO mode under TOS 7.0x
  - TURBO mode under TOS 4.0x
  
   (x means 1,2 or 4 according to your TOS)

  
*** NORMAL mode ***

  In this mode, you keep an original boring slow Falcon...  


*** TURBO mode under TOS 7.0x ***

  It is the standart CT2 TURBO mode. You have to use it if you want to boost 
  your Falcon !

  This is a TOS 4 (don't be afraid by the number 7 !) that was modified to 
correct some errors of the original TOS, install the FAST-RAM and propose 
some options via the set up. The available options in the SETUP are taken 
in account in the launching of this one.

  With this boot, the FAST-Ram is declared to the system, the TOS is copied in
Fast-Ram, the keyboard reset works ( as well cold or warm boot ).

  The boot is made with the internal driver (Cecile) or external (if it works
in turbo!). The boot looks first for a bootable hard drive  in the order
declared under the setup. Then, 2 cases are available  with Cecile or external.

  With the internal Cecile, the boot looks on the partition started for a
possible CECILE.SYS that contains some complementary information (boot
partition, energy economy mode, speed...) and start the system. If there is not
  started partition, the boot is made on the value in the setup (that can take
time!).

  In the case of an external driver that works and reachable by the system
(beware of big capacitie SCSI disks ), the boot partition is validated by this
driver and the boot will be made on it.

  with this mode, you can really start on the partition of your choice with
the original desktop.

  It is necessary to possess a graphic accelerator (NVDI, MAGIC,...) to run the
system. Modifications brought to the TOS 4.0x to make a TOS 7.0x  don't go
until the integration of all graphic routines without the utilization of the
Blitter. YOU NEED NVDI (2.5, 4.11 or 5.x) or MAGIC to use FAST-RAM !


*** TURBO mode under TOS 4.0x  ***

  This mode is dummy and only for testing some curious softwares !
  Don't use it for regular use of the Falcon (or you were stupid to buy a 
  CT2 !) : there is no FAST-RAM, even if the ram test sequence indicates a 
  'dummy' not physical FAST-RAM that is coming in reality from ST-ram !
  In this mode the speed is very slow if compared with the TOS 7 (FAST-Ram)!
    
  In this mode the setup is available but doesn't permit to select the options
that are available in the TOS 7.0x. The only available option is the choice 
of the TOS 4.0x launching.

  Under TOS 4.0x, THERE IS NO ACCESS TO THE FAST-Ram and the reset blocks the
machine because the TOS can't start in Turbo : it is necessary to make a hard
reset (push the button) to start again the machine.

 Note that TOS 4 mode allows you to use the Falcon without the NVDI or MAGIC 
 (so , WITH the BLITTER ON) because there is no Physical FAST-RAM. In this 
 manner you have time to find a NVDI or MAGIC... 


 
---------------------------------
Software installation of the CT2
---------------------------------


  Configuration of the CT2
  ------------------------

  In the beginning you MUST BE in NORMAL mode.
  The following step is OBLIGATORY before switching in Turbo.

   - Execute CBOOT.APP, reset the NVRAM (right icon) except if you got the CRC
    message mistake, reset the various options and validate when leaving.
    NOTE: think to select your country for keyboard and desktop and to make 
    a back-up boot on a disk.

    The SETUP.TXT file suplly informations complete on the configuration.

    
  External software
  -----------------

  * AUTO directory

  If you use XBOOT, it is necessary to configure it with only the FastLoad bit
(see FILEINFO.CPX) because it uses the blitter.

  Activate your graphic accelerator for the TOS 7 mode (NVDI for example).
During the progress of the file AUTO, the only graphic exit is the text that is
transferred from the ROM to the Chip-Ram, therefore that works with the
Blitter, fortunately.

  Here the order to respect. All programms are not allowed to run together:
this is only a list...

 - XBOOT
 - MENU
 - MAGXBOOT
 - SETENV
 - METADOS
 - EXTENDOS
 - DRVIN (replaces Fpatch2)
 - SCC
 - RSVX
 - STING
 - FDI_INIT
 - JPEGD
 - NVDI
 - CKBD
 - SPEEDOGDOS
 - WDIALOG
 - CENTSCREEN
 - SLECTRIC
 - UISIII
 - FREEDOM
 - LETEMFLY
 - DESKPIC
 - FALCT2_8 (formerly FALCON8)
 - NOSYSTEM
 - RDEBUG
 - CENTINEL
 - DSP_IRQ
 - MINT


  * CPX

  It is necessary to put FGENERAL.CPX INEVITABLY in the CPX directory and
DISABLE the BLITTER (and save the configuration). It is recommended to 
validate it resident thanks to CONFIG.CPX.

  FILEINFO.CPX is an utility permitting to adjust 3 bits of program
configurations and accessories: FastLoad, TT-Ram (Mem) and TT-Ram (Prg). The
FastLoad bit prevents the system to erase all the memory to every launching of
the software, that can take time with 32 Mo of Fast-Ram (1 to 2 seconds). The
TT-Ram bit (PRG) loads the program in Fast-Ram, attention to the software audio
and video (by example : CUBASE AUDIO will not output sounds if the PRG bit 
is set ! But you should set the MEM bit). The TT-Ram bit (MEM) fact that the 
program will make this allowances memory in Fast-Ram, same remark for the 
program.


  * ACCESSORIES

  Install XCONTROL.ACC, otherwise the FGENERAL.CPX will never be activated.

  Install CBOOT if you want to reset material options without needing to go
back by the CT2's setup. These options are active after validation of CBOOT.


  * CECILE
  
  Keep in mind that CECILE was developed especially for the high speed of 
  the CT2 and that we cannot warranty the other drivers to run perfectly in 
  TURBO mode ! So, it is strongly recommended to use CECILE by selecting 
  'CECILE' in the F10 menu of the CT2.
  Cecile is compatible with CUBASE and MAGIC (by example...).
  
  Our experience showed us that AHDI, ICD and SCSITOOLS (HUSHI) are be 
  avoid if you don't want to loose a partition on your HDD !
  The case of HDDriver is different : some version are running and other 
  versions are not running in some conditions.
  The versions before the 7.60 are to be avoid because the 7.60 was the 
  official version for the Milan (the 25 MHz 040 gives the same problems 
  than the 50 MHz 030 of the CT2 : the internal routs are too speed and the 
  HD accesses timings are too short/quick !!
  Keep in mind that this means a bad writing could occur and crash, by 
  example, the directory and/or FAT of a partition of your Hard Disk ! 
   
  The better solution is to install CECILE on the boot partition of your HD 
  and to use the internal CECILE on the FLASH when in turbo mode.
  Launch CC-TOOLS.APP in the CECILE folder to install CECILE.
  If you have booted in normal mode with an other driver than CECILE, you 
  should launch CECILE.PRG before launching CC-TOOLS.
  Don't be afraid by the fact there is no more files in the window of your 
  partition : press ESC to update the system ! It is caused by the launch of 
  CECILE out of the AUTO folder.
  
  At this step you have to know that there is 3 speed steps into the 
  CECILE.SYS driver. By default, the speed is 1. These 3 speeds are 
  different timings to access the slowest (old) to the fastest (modern) hard 
  drives. This speed selection is only for IDE HD. It has no matter with 
  SCSI HD (timings are done by the SCSI controller (53C80)).
  
  When the installation of the driver is done, reboot the computer in normal 
  mode : the HD must boot.
  
  In TURBO mode, you will have to carefully try the higher speeds (2 & 3).
  Firstly, try only the read accesses (not dangerous !).
  To try the write accesses, use a configuration without X-boot or all other 
  programs that write when booting up to the desktop...
  In the desktop launch the CC-TOOLS test, and finally, transfert a big ZIP 
  file (about 1 MB) from a partition to an other and check the zip 
  destination. If there is at least one error, your HD has problem to read 
  and/or write at the speed you have selected. Go down back.
  With all modern and fast HD (QUANTUM FIREBALL by exemple) the speed can be 
  used at 3 in read and write to have the best data rate performances... 
  Remember to always reboot after a change of the speed into CECILE.SYS or 
  your tests are dummy.
    
  There is too an IDE hardware setting in the F7 menu of the CT2.
  This one is to add hardware wait states on IDE transferts.
  It is set by default, but you have to remove it if the HD is modern and/or 
  you successed in the previous test in speed 3.
  
  In the all cases, you can try all combinations if there is no write on the 
  HD.
   

-------------------
PATCHS for SOFTWARE
-------------------

We kindly furnish some patchs for software that had problems to run with CT2 
(especially because of the speed with the FAST-Ram).

You should read the documentation in the 'PATCHS' folder.
It is a necessity, by example, for CUBASE AUDIO 2.04/2.06 and MAGIC 5 or 6.
Be carefull : when Cubase is patched, it is impossible to run it in NORMAL 
mode : keep a copy of the folder with a sightly different name to use both in 
Normal and Turbo mode (but you should not need to run something in 
Normal mode !).

                                                               
--------------------------------
SCSI transferts / AUDIO  setting
--------------------------------

When the Turbo mode is running you have to check the SCSI transferts.
It is the same procedure than with IDE HD.
Firstly use CC-TOOLS to test.
After, check a copied big ZIPped file (at least 5 MBytes) from the IDE to
the SCSI in 640*480 TRUE COLOR mode (important to respect this
configuration : CENTscreen is already installed !).
If there is no error, you can think that the SCSI is OK.

If not, be sure that the SCSI chain is correctly set :
Do you know the RULE for SCSI ?
You MUST put a terminator on the LAST PHYSICAL peripheral of the chain.
All the other peripherals MUST NOT have terminator !
There is only one way to be sure of that : open the box and check the 
terminator strap/setting on the electronical boards or behind the 
peripherals like CD-ROM.

Follow this point seriously because a major part of 
the vendors don't know the SCSI rules and install SCSI material inside 
case/box without to remove the original terminator on the peripheral.
If there is more than the chain's end terminator, the data transferts could 
be altered even if they were good in normal mode several months ago !

The AUDIO quality has to be listen : check for crackles with official good 
software (not demos or stupid mod players that may badly programmed !).

If you have problems with SCSI and/or AUDIO, you have now to modify a 
hardware setting ON the CT2 :

There is 4 squared pads before the CPU of the CT2 just between 2 small 14 
pins chips. The 2 left pads are connected together by a very small track.
You have to cut this track and put a solder jumper on the two right pads.
You have now a new SDMA timing and have to do again all the SCSI and AUDIO 
tests.

Note that this modification and the add of a HE14 connector on the left 
forward corner of the CT2 to light a panel led, are the only ones that 
cannot cancel the warranty.

If the problem stills to be, please contact Rodolphe Czuba : rczuba@free.fr or visit
www.czuba-tech.com   

   
-------------
Compatibility
-------------

  The list of software tested here is not exhaustive. If a software is not
present, it is sufficient to know some rules to know if it will be capable to
work under the aforementioned modes.

  First of all It is necessary to  distinguish software that function on all
TOS (and therefore on all Atari) and those specific to the Falcon.

  In the first case, the most work if they respect the elementary rules of
programming (using only system functions!).

  We can also distinguish software functioning on the TT, because they are
almost-guaranteed to work under TOS 7.0x.

  In case of doubts, it only needs to know if it runs normally on TT or Falcon
before going farther.

  As for software functioning on Falcon, the main problem will come from the
few of consideration of the system. Some software audio not having already
foreseen to function on something else than a basis Falcon (without turbo),
there won't be a miracle on an as fast board as the CT2. The second big
problem, is the management of the FAST-Ram. If  no distinction is made, we can
be in  front of a screen in Fast-Ram that won't be seen, or AUDIO buffers
giving the same problem than the graphic routines of the TOS with the Blitter.
You're driving to a system crash...

  Be careful not to abuse the passage of all the programs in Fast-Ram. May be
they are already well configured !

  The last point it is the acceleration of the CPU in relation to the DSP that
can bring problems to software conceived on a too much tighten timing (Basis
Falcon).



---------------------------------
FAQ - Frequently Asking Questions 
---------------------------------

    Here are some questions that you can put yourselves (especially if you 
didn't read the DOC! ). Let's recall that the reading of the documentation is 
INDISPENSABLE ...It will make you win a lot of times and will prevent you from 
putting your configuration upside down. (And especially that permits us to do 
not still answer to the same questions!) 

--------------------------------------------------------------------------------
Q1. My computer does'nt boot in normal mode (black screen) and crash when I come 
    out of the setup in TURBO mode.

A1.Vous have a hardware problem on your machine :
- the ROM case is not in its support or is fitted badly. 
- the CT2 is badly fitted...

--------------------------------------------------------------------------------
Q2. I don't have icons and text in XBOOT.

A2.WARNING , XBOOT is installed in FASTRAM whereas he doesn't know how to 
manage it. Don't leave XBOOT, don't save anything and REBOOT. 
To use again XBOOT, you must remove him bits of FAST RAM, with the help of the 
CPX FileInfo for example. 

--------------------------------------------------------------------------------
Q3.With an IDE hard disk boot, the computer crashes during the file auto init 
or before arriving to the desktop. 

A3.The ATA speed controlled  in ccile doesn't fit to this hard drive. To 
modify this speed, use " ATA " options of CECILE. The speed 3 only works with 
the most modern Disks. Try speed 1 for an old hard drive. Use the option Wait 
State even in the SETUP to slow down the access to the IDE port. You still have 
again 3 speed settings avalaible. 
Most of the time, a too fast or too slow speed provokes problems. Look for the 
speed that corresponds to your disk. 

--------------------------------------------------------------------------------
Q4. I don't have icons/ or scrambled icons  on the desktop. It even happens to 
crash while scrolling a menu. 

A4. The blitter is active and try to use the FAST RAM what it cannot MAKE. You 
must disable the blitter to remedy this problem. Use FGENERAL and select " 
BUFFER YES ". 

--------------------------------------------------------------------------------
Q5. I can't disable the blitter, it reactivates itself.

A5. The CPX SI (SYSTEM INFO) reactivates the blitter systematically. Suppress 
this CPX. 

--------------------------------------------------------------------------------
Q6.Magic doesn't start.

A6.You need to patch it.

--------------------------------------------------------------------------------
Q7.Magic stops on a white screen. 

A7. It seems to be a current bug of MAGIC. Make a hot RESET 
(CONTROL-ALTERNATE-DELETE on the keyboard).

--------------------------------------------------------------------------------
Q8.Calamus crashes in 256 colors with FALCON8.PRG enable. 

A8.Vous must use FALCT2_8.PRG instead of FALCON8.PRG.

--------------------------------------------------------------------------------
Q9.Cubase crashes (format error). 

A9.Vous must replace the MROS of Cubase by our patched version. 

--------------------------------------------------------------------------------
Q10.Anyplayer or Quincy or a software using the DSP stay frozen.

A10.Vous must have the DSP-IRQ.PRG program in the AUTO file.

--------------------------------------------------------------------------------
Q11. A software using the coprocessor crashes in FAST RAM. Besides 
calculations to the coprocessor are wrong (Pentium syndrome ). 

A11.Contact us...

--------------------------------------------------------------------------------
Q12. I boot on my  external SCSI hard drive instead of my internal IDE.

A12. Your IDE disk doesn't have started partition whereas the SCSI has a 
started partition. It is therefore this last one that will boot. 

--------------------------------------------------------------------------------
Q13. My Quantum MAVERICK hard drive  is seen during the ID test , but a crash  
occurs just after.

A13.This hard drive doesn't know how to transmit its parameters to CECILE. 
In the F10-CECILE menu  of the setup choose CHS for the " mode-IDE-master " 
instead of AUTO.

--------------------------------------------------------------------------------
Q14. From the moment I passed from a CT1 to the CT2, my FALCON crashes 
inopportunely in normal AND in turbo mode.

A14. Check that the resistance of 1.2K present on the network P12 (1 cm behind 
the CPU of the motherboard) and that was indispensable on CT1 has been 
withdrawn to upgrade to the CT2.

--------------------------------------------------------------------------------
Q15.From the moment I made a keyboard adapter, my FALCON reboots inopportunely 
or my keyboard is crazy during the boot or I have a black screen during the boot
 When I disconnect the keyboard, the boot is normally. 

A15. Look carefully the adapter, the cable is probably too long. 

--------------------------------------------------------------------------------
Q16. In turbo mode, the IDE disk doesn't boot in external boot or in T.OS 4 or 
under MagiC. 

A16a The IDE disk doesn't work with routines of the TOS or those of MagiC. It 
is necessary to change hard drive. While waiting, it is necessary to remove the 
boot on the IDE and to put one on the external SCSI. In this case, the boot on 
an external driver will find, without crashing, the driver and will continue the 
boot on the selected drive. 

A16b. Check that the external driver works correctly in turbo mode with 
this IDE disk. To make the test, it is necessary to start with internal Ccile 
and to launch the driver once under the desktop. You just need to use your 
machine to see if everything works fine, especially the IDE. 

--------------------------------------------------------------------------------
Q17. The boot with the internal Ccile doesn't work anymore after having put a 
CECILE.SYS on the boot partition.

A17. Check in normal mode if the ATA settings are correct.

----------------------------------------------------------------------
Q18. What is the AUTO folder correct order?

R18. Here the order to respect. All programms are not allowed to run together:
this is only a list...

 - XBOOT
 - MENU
 - MAGXBOOT
 - SETENV
 - METADOS ou BETADOS (recommended)
 - EXTENDOS
 - DRVIN (replaces Fpatch2)
 - SCC
 - RSVX
 - STING
 - FDI_INIT
 - JPEGD
 - NVDI
 - CKBD
 - SPEEDOGDOS
 - WDIALOG
 - CENTSCREEN
 - SLECTRIC
 - UISIII
 - FREEDOM
 - LETEMFLY
 - DESKPIC
 - FALCT2_8 (formerly FALCON8)
 - NOSYSTEM
 - RDEBUG
 - CENTINEL
 - DSP_IRQ
 - MINT
 
  If a software is not here, you must try to locate it at the same level
than an equivalent. For example: STICK take STING's place...

----------------------------------------------------------------------
Q19. After a Flash updating, the next boot crash and the Flash mean
to be unchanged.

R19. You must use the reset button for validate the new Flash.

----------------------------------------------------------------------
Q20. After the cold start, the screen stay black in normal mode or an
error occurs when quit the setup in turbo mode.

R20. It is possible that the SDMA is not clocked! Check the solder of
the #12 wire and the resistor on the track cutted at the left of SDMA.

----------------------------------------------------------------------
Q21. When launching Magic 5, the resolution change don't run correctly
(scrambe screen) with CENTscreen 3 on.

R21. CENTscreen 3 is not compatible with Magic 5. Remove it. Magic 6 run
perfectly with CENTscreen.

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