Phoenix OS/4 - Revision history

Martini at 22:06, 17 July 2017

2017-07-17T22:06:46Z

← Older revision		Revision as of 00:06, 18 July 2017
Line 2:		Line 2:

	--[[User:Dbanet\|Dbanet]] ([[User talk:Dbanet\|talk]]) 18:52, 18 February 2014 (CET)		--[[User:Dbanet\|Dbanet]] ([[User talk:Dbanet\|talk]]) 18:52, 18 February 2014 (CET)

			[[Category:Redirects]]

Dbanet: Replaced content with "The content of this page [http://www.os2world.com/wiki/index.php/Phoenix_OS/4 was moved to the OS/2 World Wiki] as that's the most popular and active one. --~~~~"

2014-02-18T17:52:23Z

Replaced content with "The content of this page [http://www.os2world.com/wiki/index.php/Phoenix_OS/4 was moved to the OS/2 World Wiki] as that's the most popular and active one. --~~~~"

Show changes

Dbanet: /* Installation instructions */

2014-02-18T16:25:15Z

Installation instructions

← Older revision		Revision as of 18:25, 18 February 2014
Line 44:		Line 44:
	\|RESTART\|\|Indicates, that the file to be loaded is an another kernel bootloader, rather than a kernel file.		\|RESTART\|\|Indicates, that the file to be loaded is an another kernel bootloader, rather than a kernel file.
	\|-		\|-
	\|LOGSIZE\|\|Defines the size of the log buffer (which [[#Getting_the_log \| you can get]] reading special device files) in KiB (0 < value < All memory-~~16k~~).		\|LOGSIZE\|\|Defines the size of the log buffer (which [[#Getting_the_log \| you can get]] reading special device files) in KiB (0 < value < All memory - 16MiB).
	\|-		\|-
	\|PRELOAD\|\|Use the files preload function (a must for OS4APIC to work properly, also speeds up the loading process).		\|PRELOAD\|\|Use the files preload function (a must for OS4APIC to work properly, also speeds up the loading process).

Dbanet at 16:24, 18 February 2014

2014-02-18T16:24:30Z

← Older revision		Revision as of 18:24, 18 February 2014
Line 42:		Line 42:
	The possible options are:		The possible options are:
	{\| class="wikitable"		{\| class="wikitable"
	\|RESTART\|\|Indicates, that the file to be loaded is an another kernel bootloader, rather than a kernel file		\|RESTART\|\|Indicates, that the file to be loaded is an another kernel bootloader, rather than a kernel file.
	\|-		\|-
	\|LOGSIZE\|\|~~???~~		\|LOGSIZE\|\|Defines the size of the log buffer (which [[#Getting_the_log \| you can get]] reading special device files) in KiB (0 < value < All memory-16k).
	\|-		\|-
	\|PRELOAD\|\|Use the files preload function (a must for OS4APIC to work properly, also speeds up the loading process)		\|PRELOAD\|\|Use the files preload function (a must for OS4APIC to work properly, also speeds up the loading process).
	\|-		\|-
	\|LOADSYM\|\|~~Try to find and load~~ the *.~~SYM files (useful for debugging)~~		\|LOADSYM\|\|Load the symbol file for <tt>OS2BOOT</tt>.
	\|-		\|-
	\|CFGEXT\|\| Specifies an extension for the <tt>CONFIG.ext</tt> file to be loaded instead of the CONFIG.SYS file, where <tt>ext</tt>		\|CFGEXT\|\| Specifies an extension for the <tt>CONFIG.ext</tt> file to be loaded instead of the CONFIG.SYS file, where <tt>ext</tt>
Line 119:		Line 119:
	What is the purpose of the <tt>SCREEN03.SYS</tt> driver?		What is the purpose of the <tt>SCREEN03.SYS</tt> driver?
	\|a=		\|a=
	The <tt>SCREEN03.SYS</tt> was written to enable Panorama VESA BIOS Extension Video Driver to set the proper Write-Combine flags for the LFB (the linear frame buffer)'''without''' <tt>ACPI.PSD</tt>.		The <tt>SCREEN03.SYS</tt> was written to enable Panorama VESA BIOS Extension Video Driver to set the proper Write-Combine flags for the LFB (the linear frame buffer) '''without''' <tt>ACPI.PSD</tt>.

	Now the Phoenix team provides the full alternative to the OS2KRNL + ACPI.PSD + PANOGRADD stack of technologies:		Now the Phoenix team provides the full alternative to the OS2KRNL + ACPI.PSD + PANOGRADD stack of technologies:

Dbanet: /* Frequently asked questions */

2014-02-18T15:51:43Z

Frequently asked questions

← Older revision		Revision as of 17:51, 18 February 2014
Line 119:		Line 119:
	What is the purpose of the <tt>SCREEN03.SYS</tt> driver?		What is the purpose of the <tt>SCREEN03.SYS</tt> driver?
	\|a=		\|a=
	The <tt>SCREEN03.SYS</tt> was written to enable Panorama VESA BIOS Extension Video Driver to set the proper ~~<del>MTRR</del>~~ flags '''without''' <tt>ACPI.PSD</tt>.		The <tt>SCREEN03.SYS</tt> was written to enable Panorama VESA BIOS Extension Video Driver to set the proper Write-Combine flags for the LFB (the linear frame buffer)'''without''' <tt>ACPI.PSD</tt>.

	Now the Phoenix team provides the full alternative to the OS2KRNL + ACPI.PSD + PANOGRADD stack of technologies:		Now the Phoenix team provides the full alternative to the OS2KRNL + ACPI.PSD + PANOGRADD stack of technologies:

Dbanet: /* Frequently asked questions */

2014-02-17T21:21:42Z

Frequently asked questions

@@ Line 87: / Line 87: @@
 ==Frequently asked questions==
-{{netfaq
+{{netfaq|q=
-|q=I'm getting a "<tr>VIRTUALADDRESSLIMIT is not bullshit</tr>" error message while booting. What's wrong?
+I'm getting a <tt>SYS1195: The statement "VIRTUALADDRESSLIMIT" on line *** of the CONFIG.SYS file is not recognized.  Line *** is ignored.
 |a=
 Somewhere in SVN3xxx the VIRTUALADDRESSLIMIT tuning feature was broken. Now the VAL is fixed and set to 2048.
@@ Line 95: / Line 96: @@
 Unfortunately, there is no information whether Phoenix will fix this issue and make the VAL changeable again, or not.
 }}

Dbanet: /* Installation instructions */

2014-02-17T21:17:46Z

Installation instructions

← Older revision		Revision as of 23:17, 17 February 2014
Line 2:		Line 2:

	==Installation instructions==		==Installation instructions==
	~~THIS IS A DRAFT. DON'T USE THIS INSTRUCTION -- IT IS INCOMPLETE.<br />~~

	From now, we assume that you [[#Getting_the_binary_distributions \| downloaded the latest OS/4 kernel distribution]] zip file, and it is named like this:<br />		From now, we assume that you [[#Getting_the_binary_distributions \| downloaded the latest OS/4 kernel distribution]] zip file, and it is named like this:<br />
	<tt>os2krnlSVNxxxx_unoff.zip</tt>, where <tt>xxxx</tt> is the SVN revision of the downloaded release.		<tt>os2krnlSVNxxxx_unoff.zip</tt>, where <tt>xxxx</tt> is the SVN revision of the downloaded release.

Dbanet: /* Installation instructions */

2014-02-16T12:57:53Z

Installation instructions

← Older revision		Revision as of 14:57, 16 February 2014
Line 71:		Line 71:

	There are also some configuration statements you can use in the <tt>config</tt> section in the Phoenix bootloader configuration file, but those are usually only useful for debugging and troubleshooting purposes. See the example OS2LDR.INI file in the OS/4 kernel distribution package.<br />		There are also some configuration statements you can use in the <tt>config</tt> section in the Phoenix bootloader configuration file, but those are usually only useful for debugging and troubleshooting purposes. See the example OS2LDR.INI file in the OS/4 kernel distribution package.<br />
	~~<br />~~
	----		----
	~~<br />~~
	This is a basic installation process, but remember, that there is also a new <tt>CLOCK03B.SYS</tt>, which supersedes original <tt>TIMER0.SYS</tt> and <tt>CLOCK01.SYS</tt> drivers. It is recommend to install this driver:		This is a basic installation process, but remember, that there is also a new <tt>CLOCK03B.SYS</tt>, which supersedes original <tt>TIMER0.SYS</tt> and <tt>CLOCK01.SYS</tt> drivers. It is recommend to install this driver:
	* <tt>unzip os4krnl_current.zip CLOCK03B.SYS -d \OS2\BOOT</tt>		* <tt>unzip os4krnl_current.zip CLOCK03B.SYS -d \OS2\BOOT</tt>
Line 81:		Line 81:
	* <tt>unzip os4krnl_current.zip SCREEN03.SYS -d \OS2\BOOT</tt>		* <tt>unzip os4krnl_current.zip SCREEN03.SYS -d \OS2\BOOT</tt>
	You don't need to modify <tt>CONFIG.SYS</tt>, too.<br />		You don't need to modify <tt>CONFIG.SYS</tt>, too.<br />
	~~<br />~~
	----		----
	~~<br />~~
	Okay, everything is set up. Now reboot your system!<br />		Okay, everything is set up. Now reboot your system!<br />
	You should notice the kernel selection menu with two options, where you can select to load either the original IBM kernel, or the Phoenix one. Although you may fail to boot up with the Phoenix kernel due to a bug in it, there is no doubt you will be able to fall back to the original kernel and boot your system with it (if you were able to do this before :)).		You should notice the kernel selection menu with two options, where you can select to load either the original IBM kernel, or the Phoenix one. Although you may fail to boot up with the Phoenix kernel due to a bug in it, there is no doubt you will be able to fall back to the original kernel and boot your system with it (if you were able to do this before :)).

Dbanet: /* Installation instructions */

2014-02-16T12:56:58Z

Installation instructions

← Older revision		Revision as of 14:56, 16 February 2014
Line 3:		Line 3:
	==Installation instructions==		==Installation instructions==
	THIS IS A DRAFT. DON'T USE THIS INSTRUCTION -- IT IS INCOMPLETE.<br />		THIS IS A DRAFT. DON'T USE THIS INSTRUCTION -- IT IS INCOMPLETE.<br />
	~~<br />~~
	From now, we assume that you [[#Getting_the_binary_distributions \| downloaded the latest OS/4 kernel distribution]] zip file, and it is named like this:<br />		From now, we assume that you [[#Getting_the_binary_distributions \| downloaded the latest OS/4 kernel distribution]] zip file, and it is named like this:<br />
	<tt>os2krnlSVNxxxx_unoff.zip</tt>, where <tt>xxxx</tt> is the SVN revision of the downloaded release.		<tt>os2krnlSVNxxxx_unoff.zip</tt>, where <tt>xxxx</tt> is the SVN revision of the downloaded release.
	To unify the following installation instruction, it is assumed, that the downloaded distribution file's name is <tt>os4krnl_current.zip</tt>. Please, rename the downloaded file to <tt>os4krnl_current.zip</tt> using your favorite filemanager or the CMD.EXE's <tt>ren</tt> command like this: <tt>ren os2krnlSVNxxxx_unoff.zip os4krnl_current.zip</tt>.		To unify the following installation instruction, it is assumed, that the downloaded distribution file's name is <tt>os4krnl_current.zip</tt>. Please, rename the downloaded file to <tt>os4krnl_current.zip</tt> using your favorite filemanager or the CMD.EXE's <tt>ren</tt> command like this: <tt>ren os2krnlSVNxxxx_unoff.zip os4krnl_current.zip</tt>.
	Also, you will need the <tt>unzip</tt> utility, [http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=unzip&stype=all&sort=type_name&dir=%2Fpub%2Fos2%2Futil%2Farchiver which you can find on hobbes].<br />		Also, you will need the <tt>unzip</tt> utility, [http://hobbes.nmsu.edu/h-search.php?sh=1&button=Search&key=unzip&stype=all&sort=type_name&dir=%2Fpub%2Fos2%2Futil%2Farchiver which you can find on hobbes].<br />
	~~<br />~~
	Okay, so everything is set up properly -- let's begin!<br />		Okay, so everything is set up properly -- let's begin!<br />
	~~<br />~~
	The OS/4 distribution package includes a powerful kernel loader, which features '''loading OS/4 and OS/2 kernels''', '''kernel selection menu''', '''custom CONFIG.SYS files''' for each kernel, '''CONFIG.SYS editor''' which may be invoked right before the kernel loads (available on OS/4 kernels only; although the modified version of the config is not put back on the disk, the feature is fairly useful in crash recovering), '''chainloading another kernel bootloaders''' and '''preloading files in the memory''' (better boot time).<br />		The OS/4 distribution package includes a powerful kernel loader, which features '''loading OS/4 and OS/2 kernels''', '''kernel selection menu''', '''custom CONFIG.SYS files''' for each kernel, '''CONFIG.SYS editor''' which may be invoked right before the kernel loads (available on OS/4 kernels only; although the modified version of the config is not put back on the disk, the feature is fairly useful in crash recovering), '''chainloading another kernel bootloaders''' and '''preloading files in the memory''' (better boot time).<br />
	~~<br />~~
	So, the first thing to do, is to install the OS/4 kernel bootloader, because the original one is unable to load the OS/4 kernel.		So, the first thing to do, is to install the OS/4 kernel bootloader, because the original one is unable to load the OS/4 kernel.
	If you use a recent version of ACPI, original kernel, or both (you have eCS), then it is highly recommended to keep the original bootloader:		If you use a recent version of ACPI, original kernel, or both (you have eCS), then it is highly recommended to keep the original bootloader:
Line 18:		Line 18:
	* rename <tt>OS2LDR</tt> to <tt>OS2LDR.IBM</tt>: <tt>ren \OS2LDR OS2LDR.IBM</tt>		* rename <tt>OS2LDR</tt> to <tt>OS2LDR.IBM</tt>: <tt>ren \OS2LDR OS2LDR.IBM</tt>
	* extract OS2LDR from the OS/4 package to the root of the boot drive: <tt>unzip os4krnl_current.zip OS2LDR -d \</tt>		* extract OS2LDR from the OS/4 package to the root of the boot drive: <tt>unzip os4krnl_current.zip OS2LDR -d \</tt>
	~~<br />~~
	Then extract the Phoenix OS/4 kernel to the root of the boot drive (the file is named OS4KRNL for the debug version and OS4KRNLR for the release version):		Then extract the Phoenix OS/4 kernel to the root of the boot drive (the file is named OS4KRNL for the debug version and OS4KRNLR for the release version):
	* we will use the release version, so do <tt>unzip os4krnl_current.zip OS4KRNLR -d \</tt>.		* we will use the release version, so do <tt>unzip os4krnl_current.zip OS4KRNLR -d \</tt>.
	~~<br />~~
	OS/4 ships also with an updated <tt>DOSCALL1.DLL</tt> library, which works fine with both kernels (highly recommended):		OS/4 ships also with an updated <tt>DOSCALL1.DLL</tt> library, which works fine with both kernels (highly recommended):
	* download [http://hobbes.nmsu.edu/h-search.php?key=lxlite&pushbutton=Search the lxlite package] from hobbes		* download [http://hobbes.nmsu.edu/h-search.php?key=lxlite&pushbutton=Search the lxlite package] from hobbes
Line 28:		Line 28:
	* rename it for a backup: <tt>ren \OS2\DLL\DOSCALL1.DLL DOSCALL1.IBM</tt>		* rename it for a backup: <tt>ren \OS2\DLL\DOSCALL1.DLL DOSCALL1.IBM</tt>
	* and then extract the Phoenix version: <tt>unzip os4krnl_current DOSCALL1.DLL -d \OS2\DLL</tt>		* and then extract the Phoenix version: <tt>unzip os4krnl_current DOSCALL1.DLL -d \OS2\DLL</tt>
	~~<br />~~
	Then you need to configure the OS/4 kernel bootloader to be able to load the original, and the Phoenix kernel. The configuration file's name is OS2LDR.INI. An example configuration file is present in the distribution package, and contains a comment for each line.<br />		Then you need to configure the OS/4 kernel bootloader to be able to load the original, and the Phoenix kernel. The configuration file's name is OS2LDR.INI. An example configuration file is present in the distribution package, and contains a comment for each line.<br />
	Create an empty OS2LDR.INI file in the root of the bootdrive and then put this in it using a text editor (or whatever you want):		Create an empty OS2LDR.INI file in the root of the bootdrive and then put this in it using a text editor (or whatever you want):
Line 65:		Line 65:

	Although the original kernel may be loaded by the OS/4 kernel bootloader '''directly''', the most stable configuration is to use original bootloader to load the original kernel.<br />		Although the original kernel may be loaded by the OS/4 kernel bootloader '''directly''', the most stable configuration is to use original bootloader to load the original kernel.<br />
	~~<br />~~
	Notice, that the original bootloader (OS2LDR.IBM) is able to load the only kernel file, named OS2KRNL, and you have to keep the original kernel with that name to have the ability to load it with the original bootloader.<br />		Notice, that the original bootloader (OS2LDR.IBM) is able to load the only kernel file, named OS2KRNL, and you have to keep the original kernel with that name to have the ability to load it with the original bootloader.<br />
	~~<br />~~
	Also notice, that although you have the ability to chainload kernel bootloaders with custom name using the Phoenix bootloader, the '''first''' loaded kernel bootloader is always named OS2LDR.<br />		Also notice, that although you have the ability to chainload kernel bootloaders with custom name using the Phoenix bootloader, the '''first''' loaded kernel bootloader is always named OS2LDR.<br />
	~~<br />~~
	There are also some configuration statements you can use in the <tt>config</tt> section in the Phoenix bootloader configuration file, but those are usually only useful for debugging and troubleshooting purposes. See the example OS2LDR.INI file in the OS/4 kernel distribution package.<br />		There are also some configuration statements you can use in the <tt>config</tt> section in the Phoenix bootloader configuration file, but those are usually only useful for debugging and troubleshooting purposes. See the example OS2LDR.INI file in the OS/4 kernel distribution package.<br />
	<br />		<br />
Line 77:		Line 77:
	* <tt>unzip os4krnl_current.zip CLOCK03B.SYS -d \OS2\BOOT</tt>		* <tt>unzip os4krnl_current.zip CLOCK03B.SYS -d \OS2\BOOT</tt>
	You don't need to modify <tt>CONFIG.SYS</tt><br />		You don't need to modify <tt>CONFIG.SYS</tt><br />
	~~<br />~~
	'''Attention!''' Since SVN revision '''4166''', it is '''mandatory''' to install the new <tt>SCREEN03.SYS</tt>, otherwise kernel won't boot:		'''Attention!''' Since SVN revision '''4166''', it is '''mandatory''' to install the new <tt>SCREEN03.SYS</tt>, otherwise kernel won't boot:
	* <tt>unzip os4krnl_current.zip SCREEN03.SYS -d \OS2\BOOT</tt>		* <tt>unzip os4krnl_current.zip SCREEN03.SYS -d \OS2\BOOT</tt>

Dbanet: /* Getting the binary distributions */

2014-02-16T12:54:57Z

Getting the binary distributions

← Older revision		Revision as of 14:54, 16 February 2014
Line 119:		Line 119:

	The latest kernel distribution should reside on [http://www.gus.biysk.ru/os4/ the gus.biysk.ru server in the /os4 directory].<br />		The latest kernel distribution should reside on [http://www.gus.biysk.ru/os4/ the gus.biysk.ru server in the /os4 directory].<br />
	You should find there a ~~<tr>~~ZIP~~</tr>~~ file in the root, starting with ~~<tr>~~os2krnlSVN~~</tr>~~.		You should find there a '''ZIP''' file in the root, starting with '''os2krnlSVN'''.

	Also [http://www.os2world.com/forum/index.php/topic,324.msg2674.html#msg2674 the first post on the OS2World thread about OS/4] should contain the direct link to the release.		Also [http://www.os2world.com/forum/index.php/topic,324.msg2674.html#msg2674 the first post on the OS2World thread about OS/4] should contain the direct link to the release.