[IMPORTANT] Boot loader for next release.

[Hamza]

Great Idea , an All-In-One Script !

[fanthom]

@Falcony
great job! if there will be no issues with your Win7/Vista bat file then we should be able to switch to G4D + LILO (or normal Grub) + PLOP.
nice gfxmenu would be necessary (could be shared between G4D and Grub).

@brokenman
please let me know when you check this bat against Win7 successfully. I can take implementation of G4D on my shoulders as i have done some work in this subject before.

[Falcony]

@fantom,

there is some issues with path checks

and with detecting drive:

this is code also have to be checked

Code: Select all

%BCDEDIT% /create /d "FIDOSlax Linux" /application bootsector |  %SED% s/^.*{/{/ | %SED% s/}.*$/}/ >%TEMP%\grub4dos.id
for /f %%A in (%TEMP%\grub4dos.id) do set guid=%%A

[brokenman]

No joy on win7 for me. It gave errors about not being able to find the drive. I was at work so i will run it some boxes at home and reproduce, then post the errors.
Using 'start grub2win7.bat gave strange error.
Using './grub2win7.bat ' started the file, but that is when the errors occured.

[att]

May I make a suggestion? Since we already have Plop boot loader integrated, I thought it would be a nice extra to also integrate a FreeDOS boot option.
One FreeDOS is already being used in the Linux distro GRML, that is where I got it from (www.grml.org), it only needs "memdisk" (20.068 bytes) and a DOS image called "balder10.imz (or img)" which is the size of a floppy disk (1.4 MB).

The changes in boot/slax.cfg are as follows:

Code: Select all

LABEL FREEDOS
MENU LABEL Run Free DOS
KERNEL /boot/dos2/memdisk
APPEND initrd=/boot/dos2/balder10.img


TEXT HELP
                                          More about currently selected:

                                          Boot a FREEDOS with USB and Ramdisk A:
                                          
ENDTEXT 

I use it all the time for Norton Ghost - DOS mode or for some firmware updates that only work under DOS, etc.

[82issa]

Even if they don't implement. I will implement for my personal homebrew porteus.

[brokenman]

I thought it would be a nice extra to also integrate a FreeDOS boot option.
What would the advantage be for justifying this extra 1.4Mb?

[fanthom]

@att
Porteus (as a live cd) provides linux OS and not FREE DOS.
i dont think many people uses DOS nowadays so i would drop this feature request.
Anyway it would be nice to have it in our HOWTO's section: Porteus integrated with FREE DOS boot option.

please post instruction how to create porteus live cd + Free Dos over there.

[att]

fanthom: I thought my instructions were understandable and clear?
So, let me rephrase it again, how I did it:
a) get GRML ISO from http://www.grml.org, any version will do, for example: grml64_2010.04.iso
b) from the /boot/addons directory of the ISO, get the following files:
allinone.img 1.474.560 bytes
balder10.imz 911.929 bytes
memdisk 20.304 bytes

c) copy the files to your SLAX, sorry, PORTEUS distribution, anywhere you want but preferably in the /boot directory,
better yet, make a directory called DOS2 there, so you have /boot/DOS2 on your Porteus drive

Optional: decompress the balder10.imz -> you get a "balder10.img" -> add any DOS programs there that you need for your DOS boot disk. (I use Windows, sorry, I mean WINE, and TotalCommander for this task)

d) change the boot loader of Porteus by adding another section in /boot/slax.cfg:

Code: Select all

LABEL FREEDOS
MENU LABEL Run Free DOS
KERNEL /boot/dos2/memdisk
APPEND initrd=/boot/dos2/balder10.img

TEXT HELP
                                          More about currently selected:

                                          Boot a FREEDOS with USB and Ramdisk A:
                                          
ENDTEXT 

Having FreeDOS is very useful when it comes to running (maintenance) programs that only work with DOS, for example:
* old Norton Ghost 11.5,
* Firmware updates for your Harddisk, CDRom, VGA-Card, etc.

Sometimes, booting DOS over PXE is very convenient, for example, when you have to do 100 Firmware DOS updates on 100 computers and you do not want to run to every computer with a floppy disk and boot from that disk.
In this case, you can modify the PXE default section in Porteus or Slax:

Change /boot/pxelinux.cfg in your Porteus installation so it looks like this: (This is just an EXAMPLE:)

Code: Select all

PROMPT 1

LABEL linux
MENU LABEL Run linux over PXE
KERNEL /vmlinuz
IPAPPEND 1
APPEND vga=769 initrd=/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=xconf;startx

LABEL memtest86
MENU LABEL Run Memtest utility
KERNEL /mt86p

LABEL dos
MENU LABEL Run FreeDOS
KERNEL /dos2/memdisk
APPEND initrd=/dos2/balder10.imz

LABEL dos2
MENU LABEL Run FreeDOS modded
KERNEL /dos2/memdisk
APPEND initrd=/dos2/balder10.img
 

Explanation: "Prompt 1" means you can actually type something in on the PXE-booted machine, and thus select what you want to load over PXE. In this example "dos", "dos2", "memtest86" and "linux" are your options. "plop" over PXE might be another useful option - your mileage may vary.
In this example, if you type in "dos2" and press return, a FreeDOS bootdisk will be loaded over PXE. Very useful for doing lots of firmware updates on lots of machines.

[Ahau]

@att - thanks for putting these isntructions together! When I have time, I'll prep this for posting to the main site. I'll post a draft to the HOWTO section of the forum for your review and approval, and credit you as the author, if this works for you.

[att]

Sorry, I mistyped something :

Change /boot/pxelinux.cfg in your Porteus installation so it looks like this: (This is just an EXAMPLE:)

I meant to say: Change /boot/pxelinux.cfg/default (!!) ; that is the actual filename which contains all the PXE boot options.

Yours
ATT