Androidx86-Installer-for-Windows
Androidx86-Installer-for-Windows copied to clipboard
make mounted UEFI partition to have other drive letter
I just got an issue when installing BlissOS and PrimeOS, Both ended up failed.
When I look at the log file generated, The installer tries to mount UEFI partition to Z: drive letter which is currently used to mount my workplace network drive.
I looked to your source code and found that the drive letter to mount UEFI partition is hardcoded to use Z: drive letter.
I can install it using USB Drive. but, no shop offers <16GB USB Drive in my place.
Here's the generated log:
================Installer Info================
Installer Directory:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: Hewlett-Packard
Model: HP 14 Notebook PC
Product: 22CF
BIOS info:
HPQOEM - 1
F.16
INSYDE Corp. - 10000001
Available GPU(s):
GPU: AMD Radeon(TM) R5 Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: AMD A8-6410 APU with AMD Radeon R5 Graphics
OSVer: Microsoft Windows NT 10.0.18362.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 10/05/2019 08.20.03====
-ISO File: D:\Downloads\blisspie.iso
-TargetDrive: G
-UserData: 23068672
-Setup Directories...
-Folder Created: G:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\7z.exe x "D:\Downloads\blisspie.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oG:\AndroidOS
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\7z.exe e "D:\Downloads\blisspie.iso" "boot\grub\grub.cfg" -oG:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=G:\AndroidOS\data.img count=23068672
-Initialize Data.img
#Launch:C:\Users\Syahriel Ibnu\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "G:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
==============Revert Installation==============
-Cleaning up Bliss Directory ... G:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /D
Error output:
The system cannot find the file specified.
==========================================
Additional hardware info:
RAM: 8GB
HDD: 500GB (13 partitions incl. system, 5 visible from windows)
OS: Windows 10 19H1 64bit, Ubuntu 18.04, Android-x86 6.0 (installed using DVD)
Broken DVD Drive.