G4L version 0.60 has some major changes in build, but operation is mostly the same.
Build Issue This Zip contains 2 ISO files
First is similar to the previous ISO files uses syslinux and can be written to CD or Flash
55574528 Oct 13 06:52 g4l-v0.60.iso
Second is a new setup using grub4dos as boot loader and can be written to Flash.
Has both the standard USB option and supports UEFI boot as well.
67108864 Oct 13 06:53 g4lefi-0.60.iso
For most, it should just be writting either version to an usb flash.
All versions will wipe out the contents of flash, so needs to be a flash with nothing
on it. With Linux one can use dd to copy it, or a iso burner.
With Windows I've tested rufus with the g4lefi-0.60.iso file.
With linux after copying to flash should run parted -l
The g4lefi file is an about 64M iso, so only uses that space. parted -l will make
the rest of the flash available for use. But not later reburning would erase that.
The rufus seems to resolve that as well, so using the reset of flash could be done.
Afterwards upgrades could be down by just copying new kernel files and ramdisk.lzma to flash,
and updating grub.conf files?? But need to work that out.
If interested in changes.
Changes involving both. The kernels have been reduced to just 2 versions with various options.
The older versions had 5 kernels, but haven't had issues that gave purpose to having so many.
So, Have the latest stable version an laster release candidate at time of release.
Only the syslinux version has the HDT option included, have not figured if it can be added
to the grub4dos versions at all??
The memtest86+ is only available on the syslinux version and regular grub4dos boot. It does
not work with the UEFI setup.
Have also changed the boot options to use the 800x600 as default resolution on syslinux
and grub4dos regular boot, but both has an vga=ask option that allows for other selections.
The UEFI ignores any attempts to change relsolution, and uses whatever UEFI process passes.
Seems to be the highest resolution supported.
All versions use the exact same kernel files and ramdisk.lzma files. So changes to add EFI
support are in the kernels only and the boot loaders.
Had an user that got 140 new machines that no longer supported regular booting, and only
supported the UEFI, so pushed the need to get the EFI support.
Had added EFI options to kernel long ago, but it never booted??
With a lot of work, figured it out. It actually was booting in UEFI mode, but was getting
no video output?? Found I coul telnet into systems, and it worked.
Eventually, discovered that UEFI boot doesn't support the VGA standard video, and requires
framebuffers and fbcon... Had to add about 100 lines to the kernel .config build file to
get that support. Increased kernel size by about 400K.
Had it working with grub4dos as regular boot loader and grub2 as UEFI boot loader, but later
opted to use grub4dos for both. Seems to work for me. Have a few downloads of test versions,
but heard nothing back, so assume it worked, since usually, if it doesn't one hears back.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
G4L version 0.60 has some major changes in build, but operation is mostly the same.
Build Issue This Zip contains 2 ISO files
First is similar to the previous ISO files uses syslinux and can be written to CD or Flash
55574528 Oct 13 06:52 g4l-v0.60.iso
Second is a new setup using grub4dos as boot loader and can be written to Flash.
Has both the standard USB option and supports UEFI boot as well.
67108864 Oct 13 06:53 g4lefi-0.60.iso
For most, it should just be writting either version to an usb flash.
All versions will wipe out the contents of flash, so needs to be a flash with nothing
on it. With Linux one can use dd to copy it, or a iso burner.
With Windows I've tested rufus with the g4lefi-0.60.iso file.
With linux after copying to flash should run parted -l
The g4lefi file is an about 64M iso, so only uses that space. parted -l will make
the rest of the flash available for use. But not later reburning would erase that.
The rufus seems to resolve that as well, so using the reset of flash could be done.
Afterwards upgrades could be down by just copying new kernel files and ramdisk.lzma to flash,
and updating grub.conf files?? But need to work that out.
If interested in changes.
Changes involving both. The kernels have been reduced to just 2 versions with various options.
The older versions had 5 kernels, but haven't had issues that gave purpose to having so many.
So, Have the latest stable version an laster release candidate at time of release.
Only the syslinux version has the HDT option included, have not figured if it can be added
to the grub4dos versions at all??
The memtest86+ is only available on the syslinux version and regular grub4dos boot. It does
not work with the UEFI setup.
Have also changed the boot options to use the 800x600 as default resolution on syslinux
and grub4dos regular boot, but both has an vga=ask option that allows for other selections.
The UEFI ignores any attempts to change relsolution, and uses whatever UEFI process passes.
Seems to be the highest resolution supported.
All versions use the exact same kernel files and ramdisk.lzma files. So changes to add EFI
support are in the kernels only and the boot loaders.
Had an user that got 140 new machines that no longer supported regular booting, and only
supported the UEFI, so pushed the need to get the EFI support.
Had added EFI options to kernel long ago, but it never booted??
With a lot of work, figured it out. It actually was booting in UEFI mode, but was getting
no video output?? Found I coul telnet into systems, and it worked.
Eventually, discovered that UEFI boot doesn't support the VGA standard video, and requires
framebuffers and fbcon... Had to add about 100 lines to the kernel .config build file to
get that support. Increased kernel size by about 400K.
Had it working with grub4dos as regular boot loader and grub2 as UEFI boot loader, but later
opted to use grub4dos for both. Seems to work for me. Have a few downloads of test versions,
but heard nothing back, so assume it worked, since usually, if it doesn't one hears back.