diff --git a/data/eng/Makefile b/data/eng/Makefile index f45bf11a6c..03acba0f90 100644 --- a/data/eng/Makefile +++ b/data/eng/Makefile @@ -295,6 +295,13 @@ MKISOFS_EXTRA:=\ /=distr_data/KolibriOS_icon.ico \ /=distr_data/readme.txt \ Skins/=$(REPOSITORY)/skins/authors.txt \ + Docs/config.txt=docs/CONFIG.TXT \ + Docs/copying.txt=docs/COPYING.TXT \ + Docs/hot_keys.txt=docs/HOT_KEYS.TXT \ + Docs/install.txt=docs/INSTALL.TXT \ + Docs/readme.txt=docs/README.TXT \ + Docs/stack.txt=docs/STACK.TXT \ + Docs/sysfuncs.txt=docs/SYSFUNCS.TXT \ #end of list # Some macro for convenient work. diff --git a/data/eng/docs/CONFIG.TXT b/data/eng/docs/CONFIG.TXT new file mode 100644 index 0000000000..10a5eddba6 --- /dev/null +++ b/data/eng/docs/CONFIG.TXT @@ -0,0 +1,98 @@ +KolibriOS allows some configures for user requirements. This file describes +such settings. +For this it is required to change files on ramdisk. If you boot from floppy, +there is no problem - change files on floppy. If you use floppy image +kolibri.img - either use program which can work with images (for example, +WinImage or DiskExplorer) or make changes from Kolibri and do not forget to +save ramdisk (with the application rdsave). + +1. Desktop background. +a) Replace in the file autorun.dat (it is text file) the parameter for + the program kiv ("\S__background.jpg") the name of file to the full + Kolibri-path to JPEG-, BMP-, GIF- or PNG-image which you like. It will be + new background. background.jpg now can be deleted. +b) Replace in the file autorun.dat "/RD/1/KIV \S__background.jpg" to + "/rd/1/PIC4" (spaces are ignored by the loader program). You can delete + BACKGROUND.JPG. New background will be nice texture. + For programmers: you can change texture and color, for this in file + pic4.asm from distributive sources change: + * to change texture: value of variable usearray (string 585) + from ptarray to any of ptarray2,ptarray3, ..., ptarray9. + * to change color: in procedure check_parameters find string with + the appropriate comment (string 127) and add to 0x40000 1 or 2. + After changes recompile pic4, by request pack with kpack (in + distributive is so), inject to ramdisk. +c) Two previous points sets background for a long time (until next + reinstall). It is possible also after Kolibri boot to set background + until next reboot in programs kiv, iconedit, pic4, tinyfrac. + +2. Configure system menu. + Data for system menu are placed in text file menu.dat. It can be edited + in any editor keeping format. If you use Kolibri TINYPAD, you + must disable option "optimal fill on saving". + +3. Configure autorun. + The list of programs, loading when system boots, is read out from + text file autorun.dat. It can be changed in any editor keeping format. + For example, you can add as first item start of application startmus + (delay 1, without arguments) to hear distinctive melody each time at + booting. + For programmers: you can change melody, for this edit file startmus.asm + from distributive sources: there you can choose melody from three existing + or add your own - format of melody is explained in documentation on + subfunction 55 of function 55. + +4. Icons list. + The list of desktop icons is kept in text file icons.dat, but to + change the list it is recommended to use icon manager icon (which can + be run from desktop context menu). Images for icons are kept in file + iconstrp.gif, which must be edited by external graphics editor. + +5. Skin. + The skin can be viewed and changed dynamically with the application + desktop; after you choose most likely for you skin, you can make it + permanent by replace file default.skn, from which system loads skin at + booting. Standard skin is included to ramdisk, some alternative skins can + be found in distributive in the folder Skins. You can also create your own + skin, for detailed comments look at distributive sources. + +6. Sound. + Driver sound.obj, which is located on ramdisk by default, is intended for + south bridges Intel ICH, ICH0, ICH2, ICH3, ICH4, ICH5, ICH6, ICH7 and + NVidia NForce, NForce 2, NForce 3, NForce 4. If you have SB16-compatible + sound card, remove sound.obj and rename sb16.obj from the folder 'drivers' + to sound.obj. If you have controller sis7012, rename sis.obj from root + folder in distributive to sound.obj and copy it to floppy or image to + the folder 'drivers' (replacing old). The driver fm801.obj can be useful + for ForceMedia FM801 controller, the driver vt8235.obj - for VIA chipsets, + the driver emu10k1x.obj - for EMU10K1X audioprocessor, all are intended to + similar with previous case use: copy it to the folder 'drivers' as + 'sound.obj', replacing the old file. + +7. Bus Disconnect. + The application KBD (Kolibri Bus Disconnect) allows to disconnect processor + bus in order to decrease its temperature, a side effect is noise in AC97 + codecs. The application can be loaded automatically at system boot, to do + this add to autorun (file autorun.dat, see 3) a line of the form +"/RD/1/KBD BOOT 20 # Enable Bus Disconnect for AMD K7 processors". + +8. Network settings. + Initial network configuration is read at boot from the ini file + /rd/1/network/zeroconf.ini. You can set automatic detection with DHCP + ("type=zeroconf") or fixed IP addresses ("type=static"). + +9. Configuration of videomode for ATI videocards. + The driver for ATI can set required screen resolution with refresh rate + at system startup, if they are supported. The list of supported modes + can be obtained with the utility VMODE, it allows also manual mode setting. + To set the mode at startup one must pass to the loader ATIKMS, described + in AUTORUN.DAT, the argument -mxx, e.g. + +/RD/1/DRIVERS/ATIKMS -m1024x768x60 -1 + + Pay attention that the format of autorun.dat does not allow spaces in + command line, so there must be no other arguments. + Also one can disable ability to change videomodes and all linked actions + at startup by passing the argument -n. The driver will still support + hardware cursor. To fully disable the driver, one can simply delete + the line with ATIKMS from autorun.dat. diff --git a/data/eng/docs/INSTALL.TXT b/data/eng/docs/INSTALL.TXT new file mode 100644 index 0000000000..58f40b6de3 --- /dev/null +++ b/data/eng/docs/INSTALL.TXT @@ -0,0 +1,109 @@ +Minimal system requirements for Kolibri 0.7.x.0: +* CPU: Pentium, AMD 5x86 or Cyrix 5x86 without MMX with frequency 100 MHz +* RAM: 8 Mb +* Videocard: supporting VGA (640*480*16 mode) or Vesa +* Keyboard: AT +* Mouse: COM or PS/2 + +The system can boot from any of following devices: +- Floppy 3.5 +- IDE HDD LBA +- CD/DVD +- USB Flash + +I. Install to floppy. + 1) Insert clean floppy without bad sectors to drive. + 2) Write to it kolibri.img image with any available methods: + a) (if you have already loaded Kolibri by any method) run the program + rdsave and select the variant corresponding to floppy + b) (for DOS and Windows) run subjoined install.bat + c) with program WinImage or its analogue (e.g. DiskExplorer) + d) (for Linux) set "executable" attribute to subjoined script install.sh + and run it +Now you can boot from floppy (keep it in drive, reboot, set in BIOS option +of floppy booting). + +II. Install to hard disk. +There exists several loaders from hard disk. All are oriented on DOS and +Windows users. Also standard Linux-loader GRUB can be used. All methods work +with file kolibri.img. If you already have old version of Kolibri installed, +simply replace kolibri.img to new. If you have booted from LiveCD, which +does not contain the file kolibri.img, Kolibri can create it independently, +to do this, run the program rdsave, enter the file name for saving and select +the corresponding variant. Of course, in this case Kolibri must be able to +write to file system of selected partitions, currently this means that +only FAT volumes are ok. +1) Most of all features has the loader mtldr (author - Diamond) - works with + DOS/Win95/98/NT/2k/XP/Vista, supports FAT32 and NTFS, has installator, can + be installed to any folder on disk. + To install, simply run file HD_load\mtldr_install.exe and select image file. + Apropos, by this way you can install several images. There is also + variant of install by hand - for those who want to know what installator + does: directions in HD_load\mtldr +2) There is also the loader MeOSLoad (author - Trans, expanded by Mario79) - + works with DOS/Win95/98, supports FAT32, it is placed with the instruction + to the folder HD_load\MeOSLoad. +3) Moreover, there exist a program which allow load Kolibri directly from + Windows 95/98/Me (of course, unloading it) - 9x2klbr (author - Diamond), + supports FAT32 and NTFS. +4) Usage of the loader GRUB. The way of using file 'memdisk' to load Kolibri + has been described by derPENGUIN on english forum + (http://meos32.7.forumer.com/viewtopic.php?t=110). + The suggested method (described by Alver) is based on that description + and was checked on grub-0.97-19mdv2007.0. + 1. Kolibri can write only on FAT filesystem, so if image file is placed not + to FAT volume, the system can not save settings. Therefore if you have + FAT32 partition, place 'kolibri.img' there. + 2. This method requires the file 'memdisk' from the package 'syslinux' + (http://syslinux.zytor.com). You may install the whole package or only + extract the mentioned file. Only the file 'memdisk' is needed. (After + package install it will be in '/usr/lib/syslinux'). + 3. Place the file 'memdisk' to the folder 'boot' or to the partition used + for Kolibri. + 4. Add to the configuration file 'menu.lst' ('grub.conf') lines as follow: + + title KolibriOS + kernel (hd[Hard disk number],[partition number])[path]/memdisk + initrd (hd[Hard disk number],[partition number])[path]/kolibri.img + + (Remember that numeration of partitions in GRUB starts from 0.) + Example: + title KolibriOS + kernel (hd0,0)/boot/memdisk + initrd (hd0,3)/kolibri/kolibri.img + + The initial variant was: + + label KolibriOS + root (hd[Hard disk number],[partition number]) + kernel [path]/memdisk + initrd [path]/kolibri.img + + Here 'memdisk' and 'kolibri.img' must be placed on the same partition. + + Example: + label KolibriOS + root (hd0,0) + kernel /boot/memdisk + initrd /boot/kolibri.img + This example is the variant described on english forum, with install to + Linux boot partition (of course, without FAT partition). + +5) The previous method could not work as is in GRUB2 (tested by Apocalypse_dn), + the commands "linux16" and "initrd16" should be used instead of "kernel" + and "initrd" (suggested by vkos). + +III. Install to USB-Flash-drive. +The special loader for FAT32-volumes has been written, it and its installer +to flash drive can be found in the folder HD_load\USB_Boot. +For not-FAT32 drives you may use article placed in the folder +HD_load\USB_Boot_old. + +IV. Install to CD and DVD. +There exists special LiveCD-version of Kolibri, which contains +in addition to standard things some "heavy" (in Kolibri standards) programs: +the ported emulator DosBox, games "Fixed Rate Pig" and "sokoban". +You can also create bootable CD or DVD on the base of kolibri.img, adding +anything what you want, in the mode of floppy emulation. +The appropriate actions are determined by used CD/DVD write program +(focus on words such as "boot floppy emulation").