F.A.Q. Questions fréquentes - Revision history

Thebucheron at 13:16, 20 May 2016

2016-05-20T13:16:25Z

Thebucheron at 14:38, 19 May 2016

2016-05-19T14:38:19Z

Thebucheron at 14:33, 19 May 2016

2016-05-19T14:33:46Z

Thebucheron at 14:32, 19 May 2016

2016-05-19T14:32:15Z

Thebucheron at 14:30, 19 May 2016

2016-05-19T14:30:32Z

Beworld at 17:38, 25 February 2016

2016-02-25T17:38:55Z

Beworld at 19:37, 16 February 2016

2016-02-16T19:37:50Z

Beworld: Created page with "''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larg..."

2016-02-16T19:34:50Z

Created page with "''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larg..."

New page

''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''

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 [[Dual-boot MorphOS and MacOS X on a Mac Mini G4]] guide.

''You said that ''Quark'' and other low-level software are compressed in the ''boot.img'' file. Compressed?''

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.

← Older revision		Revision as of 13:16, 20 May 2016
Line 4:		Line 4:
	''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.''		''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~~.	+	Cette requête lors de l'installation de MorphOS est justifiée par la nécessité d'être compatible avec les anciennes versions du firmware HAL/OF (versions qui ne pouvaient lire et démarrer que depuis des partitions "FFS"). Le fichier "boot.img" est donc mis sur une partition "FFS" afin de permettre au firmware d'y avoir accès et de le lancer. La deuxième partition s'explique par le fait qu'il est plus prudent et plus fiable de mettre son système sur une partition "SFS". Les nouvelles versions du firmware HAL/OF peuvent lire les partitions "SFS", et "PFS", ainsi vous pouvez mettre votre "boot.img" et votre système sur la même partition.Une exception notable est l'installation de MorphOS sur les ordinateurs Mac Apple pris en charge. L'Open Firmware de ces machines ne supporte que le démarrage à partir partitions "HFS" ou "HFS"+, donc la création d'une très petite partition pour le fichier "boot.img" est à nouveau obligatoire, comme expliqué dans le guide [[Double-d%C3%A9marrage_MorphOS_et_MacOS_X_sur_un_Mac_Mini_G4]].

← Older revision		Revision as of 14:38, 19 May 2016
Line 14:		Line 14:
	''Vous avez dit que "Quark" propose la mémoire protégée et la mémoire virtuelle, mais il semble que ces caractéristiques ne sont pas activés. ''		''Vous avez dit que "Quark" propose la mémoire protégée et la mémoire virtuelle, mais il semble que ces caractéristiques ne sont pas activés. ''

−	~~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~~.	+	La protection mémoire n'a jamais existé sur AmigaOS, et n'est pas mise en application dans "l'ABox" de MorphOS pour des raisons de compatibilité (la plupart des applications hérités de l'Amiga classique ne se lanceraient pas correctement avec la protection mémoire). En fait, la protection mémoire est utilisable dans la "QBox" et sera disponible pour de futures applications spécialement conçues pour la "QBox", lorsque la migration des pilotes matériels de "l'ABox" vers la "QBox" aura lieu. La mémoire virtuelle a été mise en application dès le commencement du développement de MorphOS, mais son développement est actuellement arrêté, en raison d'une priorité très basse. En effet, MorphOS et ses programmes natifs/Amiga classique a des besoins en RAM très faible en comparaison avec la taille des barettes mémoires désormais disponible.

← Older revision		Revision as of 14:33, 19 May 2016
Line 12:		Line 12:


−	''~~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~~.''	+	''Vous avez dit que "Quark" propose la mémoire protégée et la mémoire virtuelle, mais il semble que ces caractéristiques ne sont pas activés. ''

	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.		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.

← Older revision		Revision as of 14:32, 19 May 2016
Line 9:		Line 9:
	''Vous avez dit que "Quark" et tout autre logiciel bas niveau étaient compressés dans le fichier "boot.img". Compressé ?''		''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.	+	Le fichier "boot.img" est en fait une archive gzip. Le véritable fichier image (bootpegasos2rom.img) est donc à l'intérieur de cette archive. Il est extrait et lancé par le firmware "HAL/OF".

@@ Line 2: / Line 2: @@
-''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''
+''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.
-''You said that ''Quark'' and other low-level software are compressed in the ''boot.img'' file. Compressed?''
+''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.

← Older revision		Revision as of 17:38, 25 February 2016
Line 4:		Line 4:
	''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''		''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''

−	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 [[~~Dual~~-~~boot MorphOS and MacOS X on a 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.

← Older revision		Revision as of 19:37, 16 February 2016
Line 1:		Line 1:
		+	[[Page_principale\|Retour sur la page principale]]
		+
		+
	''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''		''I'm installing MorphOS and the installation script requires that I create and format two partitions: one very small ''FFS'' partition for the ''boot.img'' file, and one larger, bootable, possibly ''SFS'', partition for system files. You said only one is necessary.''