Difference between revisions of "F.A.Q. Questions fréquentes"
From MorphOS Library
Thebucheron (talk | contribs) |
|||
| Line 2: | Line 2: | ||
| − | '' | + | ''J'installe MorphOS et le script d'installation exige que je crée et formate deux partitions : une très petite partition en "FFS" pour le fichier "boot.img", et une plus grande, amorçable, et de préférence en "SFS", pour le système. Vous aviez dit qu'une seule partition était nécessaire.'' |
This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only ''FFS'' partitions. So the ''boot.img'' was put in a ''FFS'' partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a ''SFS'' partition, due to its higher reliability. New versions of the HAL/OF can read ''SFS'' partitions, and ''PFS'' partitions as well, so you can put everything on a single reliable partition. A notable exception is the installation of MorphOS on a supported Apple Mac machine. The Open Firmware of these machines only supports booting from ''HFS'' or ''HFS+'' partitions, therefore the creation of a very small partition for the ''boot.img'' file is again mandatory, as explained in the [[Double-d%C3%A9marrage_MorphOS_et_MacOS_X_sur_un_Mac_Mini_G4]] guide. | This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only ''FFS'' partitions. So the ''boot.img'' was put in a ''FFS'' partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a ''SFS'' partition, due to its higher reliability. New versions of the HAL/OF can read ''SFS'' partitions, and ''PFS'' partitions as well, so you can put everything on a single reliable partition. A notable exception is the installation of MorphOS on a supported Apple Mac machine. The Open Firmware of these machines only supports booting from ''HFS'' or ''HFS+'' partitions, therefore the creation of a very small partition for the ''boot.img'' file is again mandatory, as explained in the [[Double-d%C3%A9marrage_MorphOS_et_MacOS_X_sur_un_Mac_Mini_G4]] guide. | ||
| − | '' | + | ''Vous avez dit que "Quark" et tout autre logiciel bas niveau étaient compressés dans le fichier "boot.img". Compressé ?'' |
The ''boot.img'' file is a gzip archive, the real image file (e.g. ''bootpegasos2rom.img'') is inside and is extracted and run by the HAL/OF. | The ''boot.img'' file is a gzip archive, the real image file (e.g. ''bootpegasos2rom.img'') is inside and is extracted and run by the HAL/OF. | ||
Revision as of 16:30, 19 May 2016
J'installe MorphOS et le script d'installation exige que je crée et formate deux partitions : une très petite partition en "FFS" pour le fichier "boot.img", et une plus grande, amorçable, et de préférence en "SFS", pour le système. Vous aviez dit qu'une seule partition était nécessaire.
This behaviour of MorphOS installation procedure is justified by the necessity to be compatible with the past. Old versions of the HAL/OF were able to manage only FFS partitions. So the boot.img was put in a FFS partition to let the HAL/OF be able to run it. On the other hand, it was/is better to put system files on a SFS partition, due to its higher reliability. New versions of the HAL/OF can read SFS partitions, and PFS partitions as well, so you can put everything on a single reliable partition. A notable exception is the installation of MorphOS on a supported Apple Mac machine. The Open Firmware of these machines only supports booting from HFS or HFS+ partitions, therefore the creation of a very small partition for the boot.img file is again mandatory, as explained in the Double-démarrage_MorphOS_et_MacOS_X_sur_un_Mac_Mini_G4 guide.
Vous avez dit que "Quark" et tout autre logiciel bas niveau étaient compressés dans le fichier "boot.img". Compressé ?
The boot.img file is a gzip archive, the real image file (e.g. bootpegasos2rom.img) is inside and is extracted and run by the HAL/OF.
You said that in earlier versions of this article that Quark supports memory protection and virtual memory, but it seems these features are not active.
Memory protection did not exist in the AmigaOS, and is not implemented within the ABox of MorphOS for compatibility reasons (almost all the legacy applications would not be able to run correctly with memory protection). On the other hand, memory protection is usable within the QBox and might be available for future applications especially designed for QBox in case a migration of hardware drivers from ABox to QBox will take place. Virtual memory was implemented in the beginning of MorphOS development, but its upgrade is currently halted, due to very low priority. In fact, the maximal RAM requirements of MorphOS and native/legacy programs are very small in comparison with the usual RAM sizes currently available.