Subversion Repositories Kolibri OS


Blame | Last modification | View Log | Download | RSS feed

  1. KolibriOS allows some configures for user requirements. This file describes
  2. such settings.
  3. For this it is required to change files on ramdisk. If you boot from floppy,
  4. there is no problem - change files on floppy. If you use floppy image
  5. kolibri.img - either use program which can work with images (for example,
  6. WinImage or DiskExplorer) or make changes from Kolibri and do not forget to
  7. save ramdisk (with the application rdsave).
  9. 1. Desktop background.
  10. a) Replace in the file autorun.dat (it is text file) the parameter for
  11.    the program kiv ("\S__background.jpg") the name of file to the full
  12.    Kolibri-path to JPEG-, BMP-, GIF- or PNG-image which you like. It will be
  13.    new background. background.jpg now can be deleted.
  14. b) Replace in the file autorun.dat "/RD/1/KIV \S__background.jpg" to
  15.    "/rd/1/PIC4" (spaces are ignored by the loader program). You can delete
  16.    BACKGROUND.JPG. New background will be nice texture.
  17.    For programmers: you can change texture and color, for this in file
  18.    pic4.asm from distributive sources change:
  19.    * to change texture: value of variable usearray (string 585)
  20.      from ptarray to any of ptarray2,ptarray3, ..., ptarray9.
  21.    * to change color: in procedure check_parameters find string with
  22.      the appropriate comment (string 127) and add to 0x40000 1 or 2.
  23.    After changes recompile pic4, by request pack with kpack (in
  24.    distributive is so), inject to ramdisk.
  25. c) Two previous points sets background for a long time (until next
  26.    reinstall). It is possible also after Kolibri boot to set background
  27.    until next reboot in programs kiv, iconedit, pic4, tinyfrac.
  29. 2. Configure system menu.
  30.    Data for system menu are placed in text file menu.dat. It can be edited
  31.    in any editor keeping format. If you use Kolibri TINYPAD, you
  32.    must disable option "optimal fill on saving".
  34. 3. Configure autorun.
  35.    The list of programs, loading when system boots, is read out from
  36.    text file autorun.dat. It can be changed in any editor keeping format.
  37.    For example, you can add as first item start of application startmus
  38.    (delay 1, without arguments) to hear distinctive melody each time at
  39.    booting.
  40.    For programmers: you can change melody, for this edit file startmus.asm
  41.    from distributive sources: there you can choose melody from three existing
  42.    or add your own - format of melody is explained in documentation on
  43.    subfunction 55 of function 55.
  45. 4. Icons list.
  46.    The list of desktop icons is kept in text file icons.dat, but to
  47.    change the list it is recommended to use icon manager icon (which can
  48.    be run from desktop context menu). Images for icons are kept in file
  49.    iconstrp.gif, which must be edited by external graphics editor.
  51. 5. Skin.
  52.    The skin can be viewed and changed dynamically with the application
  53.    desktop; after you choose most likely for you skin, you can make it
  54.    permanent by replace file default.skn, from which system loads skin at
  55.    booting. Standard skin is included to ramdisk, some alternative skins can
  56.    be found in distributive in the folder Skins. You can also create your own
  57.    skin, for detailed comments look at distributive sources.
  59. 6. Sound.
  60.    Driver sound.obj, which is located on ramdisk by default, is intended for
  61.    south bridges Intel ICH, ICH0, ICH2, ICH3, ICH4, ICH5, ICH6, ICH7 and
  62.    NVidia NForce, NForce 2, NForce 3, NForce 4. If you have SB16-compatible
  63.    sound card, remove sound.obj and rename sb16.obj from the folder 'drivers'
  64.    to sound.obj. If you have controller sis7012, rename sis.obj from root
  65.    folder in distributive to sound.obj and copy it to floppy or image to
  66.    the folder 'drivers' (replacing old). The driver fm801.obj can be useful
  67.    for ForceMedia FM801 controller, the driver vt8235.obj - for VIA chipsets,
  68.    the driver emu10k1x.obj - for EMU10K1X audioprocessor, all are intended to
  69.    similar with previous case use: copy it to the folder 'drivers' as
  70.    'sound.obj', replacing the old file.
  72. 7. Bus Disconnect.
  73.    The application KBD (Kolibri Bus Disconnect) allows to disconnect processor
  74.    bus in order to decrease its temperature, a side effect is noise in AC97
  75.    codecs. The application can be loaded automatically at system boot, to do
  76.    this add to autorun (file autorun.dat, see 3) a line of the form
  77. "/RD/1/KBD             BOOT       20    # Enable Bus Disconnect for AMD K7 processors".
  79. 8. Network settings.
  80.    Initial network configuration is read at boot from the ini file
  81.    /rd/1/network/zeroconf.ini. You can set automatic detection with DHCP
  82.    ("type=zeroconf") or fixed IP addresses ("type=static").
  84. 9. Configuration of videomode for ATI videocards.
  85.    The driver for ATI can set required screen resolution with refresh rate
  86.    at system startup, if they are supported. The list of supported modes
  87.    can be obtained with the utility VMODE, it allows also manual mode setting.
  88.    To set the mode at startup one must pass to the loader ATIKMS, described
  89.    in AUTORUN.DAT, the argument -m<width>x<height>x<refresh>, e.g.
  91. /RD/1/DRIVERS/ATIKMS -m1024x768x60 -1
  93.    Pay attention that the format of autorun.dat does not allow spaces in
  94.    command line, so there must be no other arguments.
  95.    Also one can disable ability to change videomodes and all linked actions
  96.    at startup by passing the argument -n. The driver will still support
  97.    hardware cursor. To fully disable the driver, one can simply delete
  98.    the line with ATIKMS from autorun.dat.