Activity for G4L
-
G4L released /g4l ISO images/Readme-g4l-0.68
-
-
-
Harold Hallikainen posted a comment on discussion Help
I've used G4L for MANY years to do a monthly bare metal backup of the drive in a Windows machine. Before running it, I run: SDelete -c -z c: to zero out free space. Harold https://w6iwi.org -- Not sent from an iPhone.
-
Michael Setzer II posted a comment on discussion Help
Recall a very long time ago, Did an install of Fedora Core 3, (current version is 41) on an 80G drive that had had windos 95 I believe. Did an image and it created a 24G image. Then run the clean on disk, and redid image and it was only just over 2G. So clearing out the unused sectors makes a huge difference. You can also try the NTFSCLONE option. It only backs up used data on NTFS partition, but is faster than doing a bit level copy. Only issue is that it only has the partition, so restoring woudl...
-
Blackstone modified a comment on discussion Help
Downloaded iso for v67, and on it was the '.exe' version of lblank7 - put the entire 'other' directory on my WIN10 laptop, ran lblank7.exe as admin and it zeroed-out the drive's unallocated space (awesome). It's a 300Gb HD w/58Gb data Imaging it BEFORE zeroing gave me a 'compressed' lzop file 240Gb AFTER zeroing re-imaged it gave me lzop file 46Gb... BIG difference was due to the drive had WIN7 on it taking up 276Gb (plus 'erased' crap) of the 300Gb drive, then installed WIN10 over it (total wipe...
-
Downloaded iso for v67, and on it was the '.exe' version of lblank7 - put the entire 'other' directory on my WIN10 laptop, ran lblank7.exe as admin and it zeroed-out the drive's unallocated space (awesome). It's a 300Gb HD w/58Gb data ~ imaging it BEFORE zeroing gave me a 'compressed' file 240Gb AFTER zeroing re-imaged it gave me file 46Gb... BIG difference was due to the drive had WIN7 on it taking up 276Gb (plus 'erased' crap) of the 300Gb drive, then installed WIN10 over it (total wipe - saved...
-
The exe program sould work from command prompt. Probable best to open it with admin access, since some space might be used by reserved. Not on what encryption option might have. But if trying to mount the partition results in it being flagged as read-only, something must be going on.
-
OK - so, we're talking about a single OS laptop running Win10, not linux, so no grub... My WIN10 sez bitlocker is OFF... can I just run lblank7 that is in the cd of my g4l (copy it to another usb that WIN10 can see) while in windows via it's command prompt? There's lblank7 and lblank7_64 - neither one has '.exe' after it... there's a 'blank6.exe' on it...
-
OK - so, we're talking about a single OS laptop running Win10, not linux, so no grub... My WIN10 sez bitlocker is OFF... can I just run lblank7.exe that is in the cd or usb of g4l (copy it to another usb that WIN10 can see) while in windows via it's command prompt? There's lblank7 and lblank7_64 - guess use lblank7_64.exe?
-
Could the partition be encrypted or have bitlocker?? If so, that would be an issue. The is a standalone simple c program lblank7.exe that is in the cd or usb of g4l. It just creates a number of files that blanks space until disk is full, and then it erases them. Would have to open a command window and run the program to clear all unused space. Have seen some messages that found they had bitlocker on systems, and didn't know it. Some would have problems with the grub menu booting with bitlocker s...
-
is there a way to get windows cipher.exe to just write the zero's and not the full: once with a series of 0's (zero) once with a series of 255's once with a series of random numbers just want the deleted files space 'emptied', not overwritten to prevent recovery... sfdisk -l /dev/sda shows: sda1 is EFI system, sda2 is microsoft reserved, sda3 is microsoft basic data, and sda4 is windows recovery environment ntfsck /dev/sda3 says command not found fsck -f /dev/sda3 - not willing to use this - seems...
-
The zero tool should work fine, but it appear the partition is being mounted as read-only for some reason? Could be it wasn't closed properly, or has some kind of special setting. What does sfdisk -l /dev/sda show for it and other partitions. Could see fsck -f /dev/sda3 shows or ntfsck /dev/sda3 Would also be interest in how big the partition is? If not to large, it might not save much space. Don't have a system handy with windows 10 or 11 with UEFI setup. Also, not 0.67 is out, and already working...
-
trying to use G4L's utility zerotool on my win10 partition sda3 w/UEFI boot using g4l v0.66a and booted as UEFI w/no problem - trying to use its zerotool and it comes up with: Progress /bin/g4l: line 132: 0bits: Read-only file system ncftpstatus: OK ...but nothing happens :-\ does the zerotool not work on my win10 partition?
-
Relesed 0.67 - Using Fedora 40 as base
-
-
-
-
-
Christopher Baker posted a comment on discussion Open Discussion
Brilliant! Just tried it out, and yup 'Zero Tool' under Utilities. How did I not see that? I probably mistakenly got it into my head that it was some kind of pre-OS-installation partition clearing tool... Shows that even with OS's & SSD's TRIM function and firmwares, abandoned data still lives on these drives like the rotating spindle drives do. Ah, at least our posts might inform some googlers out there to the use & benefits of the menu option? Thanks Mike!
-
Is under the Utility option for zeroing out the space. Generally can zero out various partition types. Saw the same thing long ago. Had done a clean install of Fedora Core 4 on an 80G disk, and made an image and it was much larger than I expected. Think it was like 24G. Then cleared the unused sectors, and redid the image, and it was like 2.8G. The raw mode does copy all raw sectors, so if they contain random data it takes up space to compress them. If they have been filled with 0's the compression...
-
I recently imaged an 128GB NVMe drive. It was a project where I did a number of partition deletes & installs of windows versions (Embedded 7 through 8.1) along with copying a 10gb game to it, over and over. Doing an raw-mode whole-drive image was resulting in a compressed image over 50GB, even though the 119GB NTFS partition contained only 26GB uncompressed data, via ntfsbackup. Finding that a silly wasteful size, I thought about it for a while, and surmised that the raw read was preserving all the...
-
I recently imaged an 128GB NVMe drive. It was a project where I did a number of partition deletes & installs of windows versions (Embedded 7 through 8.1) along with copying a 10gb game to it, over and over. Doing an raw-mode whole-drive image was resulting in an image over 50GB, even though the 119GB NTFS partition contained only 26GB uncompressed data, via ntfsbackup. Finding that a silly wasteful size, I thought about it for a while, and surmised that the raw read was preserving all the bits of...
-
-
-
First screen shows a read error on the kernel load, so that would mean something went wrong with the writing of the image? Are you burning it to a CD or to a USB? So first thing I could try would to be to copy to another media and see if it will boot without that read error. Is your system 32 bit or 64 bit? Think it must be 64 bit, since kernels moved to 64bit when Fedora stopped releasing 32 bit version. I still build the iso version that uses syslinux that hasn't been updated in a long long time....
-
Will Jackson posted a comment on discussion Help
Thanks for creating this software, it's been most useful. However and unfortunately none of the releases after v0.61 get beyond the splash screen. I'm using Ubuntu 22.04. None of the options worked, tried bz6x6 800x600, no video, bz5x18.5 vga=788 etc. I did get an out attached. Thanks.
-
The difference in kernel size between bz6x7.8 and the added 6.7.9 is just about 93K of the 12M total size in difference. So not much there, and the lsblk was a small addition to ramdisk.lzma size. Just need to see what lines were change in config file, and add them to the bz6x8 .config. Generally keep the latest stable kernel, and the rc kernel, but 6.8 just went to released status. Usually wait for next rc to come out before changing default. Glad it works.
-
Puiu Saptezecisisase posted a comment on ticket #61
I tried alpha31 and it worked! (at least for backing up, haven't tried restoring but I see no reason why it shouldn't work) Found lsblk too, hope it didn't bloat the iso too much because it's useful having it. Thank you!
-
went ahead and make a new 31alpha and new g4lefi that have that added.
-
Made a new alpha30 and new g4lefi.img had added the eMMC set to y, and had hoped the make oldconfig would have set any required options, but it appears it didn't. So, set the MMC-y, and then make oldconfig prompted for a number of other things. Also, added lsblk which just required the program since all linked libraries were already thers. Need to download new files. ftp://setzco.dyndns.org/g4l-v0.66alpha30-fc39.iso ftp://setzco..dyndns.org/g4lefi-0.66.img The differences between .config is 2872,2873d2871...
-
I tried the alpha you built and it didn't see the eMMC storage. Here's the output of lsmod taken from a working debian install: Module Size Used by intel_rapl_msr 20480 0 intel_rapl_common 32768 1 intel_rapl_msr x86_pkg_temp_thermal 20480 0 intel_powerclamp 20480 0 coretemp 20480 0 crc32_pclmul 16384 0 binfmt_misc 24576 1 ghash_clmulni_intel 16384 0 sha512_ssse3 49152 0 sha512_generic 16384 1 sha512_ssse3 sha256_ssse3 32768 0 mmc_block 57344 0 sha1_ssse3 32768 0 nls_ascii 16384 1 nls_cp437 20480...
-
ftp://setzco.dyndns.org/g4l-v0.66alpha29-fc39.iso ftp://setzco..dyndns.org/g4lefi-0.66.img Have updated bz6x7.9 kernel to add option CONFIG_PHY_INTEL_LGM_EMMC=y and rebuilt that kernel. Looked thru menuconfig, but couldn't find option in make menuconfig, so just activated it in .config Did make, and updated the above files, so both the syslinux iso and the grub4dos image files. Don't have the EMMC so having tested. Currently in Nevada taking care of mom from hospital, so remotely accessing machines...
-
eMMC support
-
Uploaded Version 0.65 Fedora 38
-
-
-
-
-
I've created updated bz6x4.15 and bz6x5.2 kernels that have it enabled. Have built a new version 0.65 as 8th so far that includes this. Send me an email to mikes@guam.net and I can send you ftp link, or can send files. The syslinux version iso, or usb efi/non-efi image or development source. Or if you just want kernel(s) files. Was just changing option in .config file and rebuilding the kernels. Added about 18K to to kernel size. Usually add new ethernet kernels, but it was in a different section....
-
On 8 Sep 2023 at 8:49, Mikhail wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "Mikhail" mtatarin@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] vmxnet3 ethernet driver support Date sent: Fri, 08 Sep 2023 08:49:07 -0000 Hi, Could you please create a new topic: vmxnet3 driver support The question is how to add vmxnet3 support to g4l? Any plans to add vmxnet3 support in next future g4l releases?...
-
Mikhail posted a comment on discussion Help
Hi, Could you please create a new topic: vmxnet3 driver support The question is how to add vmxnet3 support to g4l? Any plans to add vmxnet3 support in next future g4l releases? Thank you. BR, Mikhail.
-
Uploaded Version 0.64 working on 0.65
-
-
-
-
-
On 18 Jun 2023 at 23:13, KenUnix wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "KenUnix" kenmartin@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Imageing from 931.52 SSD to 931.51 SSD possible? Date sent: Sun, 18 Jun 2023 23:13:16 -0000 Michael, Thanks for the reply. I thought I had good quality SSD's Western Digital Green 1.tb then to discover some are 931.51 and some are 931.52! Clonezilla...
-
KenUnix posted a comment on discussion Help
Michael, Thanks for the reply. I thought I had good quality SSD's Western Digital Green 1.tb then to discover some are 931.51 and some are 931.52! Clonezilla had the -r flag set and kept running until it was 99% done then said it was having write errors. And the clone was aborted. Tried with two different drives. So I got a Samsung 2tb SSD and cloned the laptop to it. As a test I attempted to clone the Samsung 2tb that had 1tb on it back to the laptop with the 1tb drive and clonezilla said the destination...
-
On 18 Jun 2023 at 18:39, KenUnix wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "KenUnix" kenmartin@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Imageing from 931.52 SSD to 931.51 SSD possible? Date sent: Sun, 18 Jun 2023 18:39:04 -0000 I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones of them so I purchased two more WD Green 1TB SSD's. However those have a size...
-
I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones of them so I purchased two more WD Green 1TB SSD's. However those have a size of 931.51GB !! Clonezilla won't do it. The difference if .02GB. Will G4L do it? Thanks. Forgot to mention I am running Ubuntu 22.04.
-
I have two laptops with WD Green 931.52GB SSD's. I wanted to make clones of them so I purchased two more WD Green 1TB SSD's. However those have a size of 931.51GB !! Clonezilla won't do it. The difference if .02GB. Will G4L do it? Thanks.
-
On 7 Jun 2023 at 15:25, Russell Hanneken wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "Russell Hanneken" russellhanneken@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Re: Can't boot 0.63 Date sent: Wed, 07 Jun 2023 15:25:28 -0000 Apparently the current version of Pop!_OS uses systemd-boot rather than grub. https://superuser.com/questions/1583591/systemd-permanently-add-boot-loader-options-popos...
-
Russell Hanneken posted a comment on discussion Help
Apparently the current version of Pop!_OS uses systemd-boot rather than grub.
-
I'm using Pop!_OS 22.04 LTS, which is a distribution downstream from Ubuntu. Thanks for the workaround; I'll see if I can use it! Anyway, stay safe.
-
On 6 Jun 2023 at 22:26, Russell Hanneken wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "Russell Hanneken" russellhanneken@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Can't boot 0.63 Date sent: Tue, 06 Jun 2023 22:26:29 -0000 I just realized that my laptop has something called coreboot. From the GitHub page: coreboot is a Free Software project aimed at replacing the proprietary firmware...
-
On 6 Jun 2023 at 22:26, Russell Hanneken wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "Russell Hanneken" russellhanneken@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Can't boot 0.63 Date sent: Tue, 06 Jun 2023 22:26:29 -0000 I just realized that my laptop has something called coreboot. From the GitHub page: coreboot is a Free Software project aimed at replacing the proprietary firmware...
-
I just realized that my laptop has something called coreboot. From the GitHub page: coreboot is a Free Software project aimed at replacing the proprietary firmware (BIOS/UEFI) found in most computers. I'm guessing this is not supported?
-
For the img file, I used the dd command that was in the documentation. For the iso, I used Popsicle. I can mount and see the USB drive with the iso image on it. I don't know if it makes a difference, but this is the laptop I have, and this is the firmware that it runs.
-
On 6 Jun 2023 at 20:54, Russell Hanneken wrote: To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net From: "Russell Hanneken" russellhanneken@users.sourceforge.net Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sourceforge.net Subject: [g4l:discussion] Can't boot 0.63 Date sent: Tue, 06 Jun 2023 20:54:35 -0000 I'm attempting to boot Ghost for Linux 0.63 on my System76 Gazelle laptop, and each time I try I just get this message: SecureBoot is disabled. Booting from 'SanDisk...
-
I'm attempting to boot Ghost for Linux 0.63 on my System76 Gazelle laptop, and each time I try I just get this message: SecureBoot is disabled. Booting from 'SanDisk Cruzer Glide' failed; verify it contains a 64-bit UEFI OS. Press any key to continue booting... "SanDisk Cruzer Glide" is the name of the 32GB USB flash drive I"m using. When I press a key, I just get sent back to my laptop's menu for selecting a disk to boot from. I've tried burning both images on the USB stick, with the same results....
-
Has 6.3.5 as default kernel and updated files. Also has memtest86+ 6.20 latest grub4dos with legacy and UEFI support. Doesn't support secure boot So must turn off secure boot before booting.
-
Uploaded version 0.63
-
-
-
-
Update: Was posting to the grub4dos list about image info, and the author had made a custom version for me to test that resolved the issue with the acer predator so it correctly displays the image and the text with my latest test version. Not sure if it was just an issue with the Predators UEFI setup, or was something in the UEFI for some systems.
-
Have been test the newer grub4dos legacy and UEFI boot options, and in virtual box and dell machine they worked fine. Did recently find on an Acer Predator notebook with the background image, the menu options got messed up completely. But without image works fine. I've also gotten the new memtest 6.10 to work on syslinux version and both grub4dos versions. Doesn't work if secure boot, unless one make addition to secure boot setting. Also note on the Acer Predator if boot option is other than AHCI...
-
Uploaded version 0.62 and working on 0.63
-
Forgot to add readme file to the ISO Zip before uploading. Just added Readme for 0.62 to files directory. G4L version 0.62 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 50331648 Jan 1 03:57 g4l-v0.62.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....
-
-
The https://sourceforge.net/projects/g4l/files/g4l%20ISO%20images/g4l-v0.62-Release-ISOs.zip/download Is a zip file that contains two files. Archive: g4l-v0.62-Release-ISOs.zip Length Date Time Name --------- ---------- ----- ---- 67108864 01-01-2023 04:04 g4lefi-0.62.iso 50331648 01-01-2023 20:39 g4l-v0.62.iso --------- ------- 117440512 2 files The g4l-v0.62.iso uses syslinux to boot and is created as a hybrid version, so one can use an ISO burning program to write it to a CD or one can copy it...
-
Roger Davis posted a comment on discussion Open Discussion
There are two versions on the same download. To use G4L on a CD to backup drive to drive, bit for bit, which one do I want? I"m almost certain it's G4L V062, 50.3MB , but I need to be SURE. Please advise...
-
-
-
Uploaded 0.61 release
-
-
-
-
A couple questions. 1. How are you trying to boot it? The g4lefi.iso is not a normal iso that is meant to be burned to a cd. It is generally copied directly to a flash with grub4dos being the boot loader. 2. Have you checked BIOS settings. I recently had a linux system that had the onboard battery die, and the BIOS reset back to default. Replace battery, but machine would not boot from hard disk. Turned out there was a strange BIOS setting that was defaulted to boot using Windows EFI, and for whatever...
-
The first one I would expect, since the G4L efi image does not have an Official EFI signature since that is a very expensive process as I understand it. One would have to make a signature file and manually install it in each machine to allow for secure boot to work? Don't understand what the issue is with the second? Should display the EFI grub4dos menu listing that is a basic 800x600 screen..
-
greyhairweenie posted a comment on discussion Open Discussion
On new Dell G15 Ryzen Edition using efi iso, get "DEFAULT_B00T_DEVICE HAS BEEN BLOCKED BY THE CURRENT SECURITY POLICY" in a blue popup, with secure boot enabled. With secure boot disabled, it flashes a text line too fast to catch and drops to a blank screen with blinking cursor. Not a critical problem, I have other means of imaging the drive.
-
Kevin Eisinger posted a comment on discussion Help
Michael, Where should I post requests for new features in G4L? I would like to request that G4L add a screen when backup is complete indicating it completed successfully. We would have to click OK to acknowledge that screen and to go back to previous screen. Hopefully this is not difficult to add. When G4L encounters hard drive errors it goes back to the previous screen, thus if you were not watching the entire backup process you may not realize that the process did not complete successfully. Thanks,...
-
Had to look. It is under the Utilities options.
-
Michael, I am backing up a windows 10 system. It has 4 partitions, EIF partition, MS reserved, NTFS, MS windows recovery. Windows 10 is working with no problems so the errors should be in unused sections (hopefully). I did boot using an old Ubuntu 17 flash drive and started running badblocks and it found errors. Thus, it looks like hard drive issues. You mention ddrescue, is this an option on G4L? If so where can I find it. Thanks, Kevin Eisinger
-
I've done similar on Linux. Used lzop to extract the compressed data image to a file that is the original size of partition. Then used the linux loop mount option? Would have to look up the process since it has been a long time. But generally just restoring to a spare disk is faster.
-
G4L primarily uses dd for most of the backup processes. Unfortunately, dd does not handle hard errors within disks/partitions. There are options to use ddrescue, which does have a number of methods to attempt to copy the readable data, and does try to recopy the bad areas a number of times before leaving those blocks as what it was able to get. May or may not make a useful image. You didn't mention what file systems are on disk. If it is windows, you might be able to use ntfsclone option to backup...
-
I have successfully accessed files from the G4L image file. The backup have been from a Windows 7 system and a Windows 10 system. I have accessed these from a Windows 7 and Windows 10 system. I create backup with the default lzop compression, thus I had to uncompress the image prior to mounting to it. As mentioned previously you will need enough hard drive space for the original size of the hard drive that was backed up. Also if your image file is on a network this will take a lot of time to uncompress....
-
I am trying to backup hard drives and I am getting Errors and G4L returns back to LOCAL USE screen. I have two test systems that have the same computers and I am getting errors with both of them. G4L V 0.60, I have tried A: bz5x14.11, D: bz5x15.rc5. G4L V 0.57, I have tried D: bz5x6.15, A: bz4x19.128. I get the same errors on all of these. Computer: 3U MS-98K9 Motherboard MSI MS-98K9 BIOS American Megatrends inc V2.9b4, 4/9/2021 Hard Drive Samsung SSD870 I have tried using a 2TB HD and a 4TB hard...
-
Agree that it isn't an easy process and it is probable more work than restoring to a spare disk. Recall I once needed a file from a smaller partition I had imaged, and didn't have a spare disk at time were I was, so tried it. Probable more just to see if it would work, and it did. So. Definitely agree that quickest option would be to just restore to a spare disk, and then search it. On issue that might be of concern. If doing this on same system with original disk, the bllkids on disk would be identicle...
-
That complex "exception" is actually a multi-step restoration of the image to a state in which files can be extracted.
-
That is probable mostly correct with one complex exception. It is possible to first uncompress the image file to the raw state. Then you can mount that file as a loop process. Have done it a few times, but uncompressed size is size of the original disk/partition so needs lots of space. The loop mounting process is also something I'd have to look up, since it depends if it is a partition or disk image, and OS might make difference. Usually easier to just restore to an external disk. So, mostly Not...
-
No. It's an image backup, and you have to restore the image somewhere to see and pull files from it.
-
Sam posted a comment on discussion Help
Just like it says. If I make a G4L backup can I see individual files in it? Can I pull a file from the backup? Thanks!
-
Did you note or can you check what was showing in cat /proc/partitions If it has something I can identify, could have it show a message to users that they might need to disable raid to be able to backup partitions? Second. Do you know what raid controller it is showing? Might be that the controller for some machines is included, but this one isn't, or it might be that the raid controller in hardware or software removes the standard drive devices if it sees them as raid? There is also a line that...
-
Isaac posted a comment on discussion Help
Michael, Thank you for your response. Disabling RAID did, although other Dell machines work well with RAID enabled. Thank you! On Mon, Dec 20, 2021 at 1:50 PM Michael Setzer II msetzerii@users.sourceforge.net wrote: A couple things come to mind, but need more info. First, what type of drive is it? Regular hard disk or some other type? Second, on the OS, how does it report the drive as being. Third, might the drive require special firmware files. I don't include a lot of firmware files, just ones...
-
A couple things come to mind, but need more info. First, what type of drive is it? Regular hard disk or some other type? Second, on the OS, how does it report the drive as being. Third, might the drive require special firmware files. I don't include a lot of firmware files, just ones that users have mentioned. It might be some modual in the kernel build that isn't included at this point. Generally, they to add most, but occasionally it lists things that are set to default n to add. After booting...
-
Dear Michael, thank you for the latest Version. Finally I was able to use it in UEFI boot. However I do have an issue with Dell Latitude 7400. It boots well using USB with g4L V60, but when I attempt to back up the hard drive, I can only see the USB drive itself under SDA and a small recovery partition as SDA1 but the actual drive I am trying to back up is not shown. I tried other machines - no problem! May i ask you to provide some insight and point me to the right direction. Thanks
-
Hope that is a good sign, since usually if people have issues they let you know, but if it works don't do anything. Have started working on next version already. Upgraded 5 of my systems to Fedora 34, and upgraded the build to use the Fedora 34. In first two builds, I had missed copying on of the libraries, and the tests crashed since it was of course one of the critical libraries. But have now got 6 builds with 0.61, all seems good. Did find a few libraries I had that were not actually used by any...
-
