FreeDOS - Revision history

Leo: Added operating systems category

2021-12-30T02:24:02Z

Added operating systems category

← Older revision		Revision as of 02:24, 30 December 2021
Line 163:		Line 163:
	Gentoo has a guide outlining how to create a custom FreeDOS environment image		Gentoo has a guide outlining how to create a custom FreeDOS environment image
	* https://wiki.gentoo.org/wiki/BIOS_Update/en		* https://wiki.gentoo.org/wiki/BIOS_Update/en

			[[Category:Operating_Systems]]

Leo: Leo moved page Freedos to FreeDOS: Free DOS name

2020-06-14T23:37:26Z

Leo moved page Freedos to FreeDOS: Free DOS name

← Older revision		Revision as of 23:37, 14 June 2020
(No difference)

Leo at 17:26, 10 August 2017

2017-08-10T17:26:51Z

@@ Line 52: / Line 52: @@
 }}
-=== See Also ===
+=== USB ===
-Gentoo has a guide outlining how to create a custom FreeDOS environment imaage
+## Create the filesystem, use 'mkfs.vfat -F32' for drives larger than 4GB
-* https://wiki.gentoo.org/wiki/BIOS_Update/en
+# mkfs.vfat /dev/sdx1
-== PXE Boot FreeDOS ==
+... for the rest, see https://wiki.gentoo.org/wiki/LiveUSB/Guide#Installing_a_Master_Boot_Record_.28MBR.29
 With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using Syslinux's {{code|memdisk}}.
@@ Line 97: / Line 136: @@
 }}
-=== iPXE Boot ===
+=== iPXE ===
 For more details, see the [[IPXE]] page.
 I was able to boot FreeDOS using the following iPXE embedded script. Note the {{code|imgargs}} values; these are required for a successful boot.
@@ Line 117: / Line 156: @@
 {{Info|1=Boot from HTTP and other protocols|2=The previoius example uses tftp, but you can easily use http as well as any other supported protocols your iPXE ROM was compiled with.}}

Leo: /* iPXE Boot */

2017-08-10T16:58:14Z

iPXE Boot

← Older revision		Revision as of 16:58, 10 August 2017
Line 98:		Line 98:

	=== iPXE Boot ===		=== iPXE Boot ===
	For more details, see the [[~~iPxe~~]] page.		For more details, see the [[IPXE]] page.

	If you do not have a DHCP server set up to do PXE boot (ie, {{code\|next-server}} and {{code\|filename}} isn't set), you could use iPXE instead to boot FreeDOS via network.		If you do not have a DHCP server set up to do PXE boot (ie, {{code\|next-server}} and {{code\|filename}} isn't set), you could use iPXE instead to boot FreeDOS via network.

Leo: /* PXE Boot FreeDOS */

2017-08-10T16:20:39Z

PXE Boot FreeDOS

← Older revision		Revision as of 16:20, 10 August 2017
Line 60:		Line 60:
	== PXE Boot FreeDOS ==		== PXE Boot FreeDOS ==

	With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using {{code\|memdisk}}.		With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using Syslinux's {{code\|memdisk}}.

	Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in the {{code\|pxelinux.cfg}} directory containing:		Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in the {{code\|pxelinux.cfg}} directory containing:
Line 98:		Line 98:

	=== iPXE Boot ===		=== iPXE Boot ===
			For more details, see the [[iPxe]] page.

	If you do not have a DHCP server set up to do PXE boot (ie, {{code\|next-server}} and {{code\|filename}} isn't set), you could use iPXE instead to boot FreeDOS via network.		If you do not have a DHCP server set up to do PXE boot (ie, {{code\|next-server}} and {{code\|filename}} isn't set), you could use iPXE instead to boot FreeDOS via network.

	I was able to boot FreeDOS using the following iPXE embedded script:		I was able to boot FreeDOS using the following iPXE embedded script. Note the {{code\|imgargs}} values; these are required for a successful boot.

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
Line 112:		Line 114:
	imgargs memdisk raw		imgargs memdisk raw
	boot		boot

	}}		}}

	~~The~~ {{~~code~~\|~~imgargs~~}} ~~is important as it won't boot otherwise.~~		{{Info\|1=Boot from HTTP and other protocols\|2=The previoius example uses tftp, but you can easily use http as well as any other supported protocols your iPXE ROM was compiled with.}}

Leo: /* Creating Custom FreeDOS Image */

2017-06-09T19:02:12Z

Creating Custom FreeDOS Image

← Older revision		Revision as of 19:02, 9 June 2017
Line 21:		Line 21:
	# mount fdboot.img freedos		# mount fdboot.img freedos

	## Create an file for the image. Eg. 50 MB		## Create an file for the image. Eg. 10 MB
	# dd if=/dev/~~null~~ of=freedos.img bs=1024 ~~seek~~=~~51200~~		# dd if=/dev/zero of=freedos.img bs=1024 count=10240
			10240+0 records in
			10240+0 records out
			10485760 bytes (10 MB) copied, 0.232655 s, 45.1 MB/s

	## Make the MSDOS filesystem (vfat)		## Make the MSDOS filesystem (vfat)
	# mkfs.msdos freedos.img		# mkfs.msdos freedos.img
			mkfs.vfat 3.0.9 (31 Jan 2010)

	## Load the boot sector to the image		## Load the boot sector to the image, requires nasm
	# ./sys-freedos.pl --disk=freedos.img		# ./sys-freedos.pl --disk=freedos.img
			DOS boot sector for freedos.img will be created by:
			nasm -o /dev/stdout -dISFAT16 ./bootsecs/boot.asm
			Using FAT16. Partn offset 0, CHS *x64x32 Drive 0, (0x0, 0x29),
			SerNo 5C9-916A, Strings ' ', 'FAT16 '.
			Boot sector successfully updated.

	## Mount and copy the FreeDOS system files over		## Mount and copy the FreeDOS system files over

Leo at 22:43, 18 May 2017

2017-05-18T22:43:04Z

← Older revision		Revision as of 22:43, 18 May 2017
Line 1:		Line 1:

			== Configuration ==
			* http://www.freedos.org/kernel/config.txt


	== Creating Custom FreeDOS Image ==		== Creating Custom FreeDOS Image ==

Leo: /* iPXE Boot */ pipes

2017-05-18T22:41:09Z

iPXE Boot: pipes

← Older revision		Revision as of 22:41, 18 May 2017
Line 91:		Line 91:
	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
	:retry_dhcp		:retry_dhcp
	dhcp \|\| goto retry_dhcp		dhcp {{!}}{{!}} goto retry_dhcp

	echo Booting FreeDOS BIOS Update		echo Booting FreeDOS BIOS Update

Leo: /* Creating Custom FreeDOS Image */

2017-05-18T22:22:42Z

Creating Custom FreeDOS Image

← Older revision		Revision as of 22:22, 18 May 2017
Line 39:		Line 39:
	}}		}}


			=== See Also ===

			Gentoo has a guide outlining how to create a custom FreeDOS environment imaage
			* https://wiki.gentoo.org/wiki/BIOS_Update/en

	== PXE Boot FreeDOS ==		== PXE Boot FreeDOS ==

Leo: /* PXE Boot FreeDOS */

2017-05-18T22:20:07Z

PXE Boot FreeDOS

← Older revision		Revision as of 22:20, 18 May 2017
Line 44:		Line 44:
	With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using {{code\|memdisk}}.		With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using {{code\|memdisk}}.

	Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in		Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in the {{code\|pxelinux.cfg}} directory containing:
	the {{code\|pxelinux.cfg}} directory containing:

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=

← Older revision		Revision as of 22:20, 18 May 2017
Line 44:		Line 44:
	With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using {{code\|memdisk}}.		With a custom FreeDOS image created as outlined above, you should be able to PXE boot the image using {{code\|memdisk}}.

	Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in		Assuming that you have all the PXE infrastructure set up (DHCP + TFTP + /tftpboot/pxelinux.cfg), add an entry in the {{code\|pxelinux.cfg}} directory containing:
	the {{code\|pxelinux.cfg}} directory containing:

	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=