HackinDROM App testing (not website)

[CaseySJ]

@Inqnuam,

A couple of issues with v1.3.3 in Catalina:

• The screen "stuttering" problem (as in video posted yesterday) occurs when mouse is in the bottom part of Create EFI section.
• Bluetooth RSSI signal monitoring function causes mouse to freeze every 2-3 seconds. The freeze lasts about 1 second then mouse can move again. If we quit HackinDROM, then Bluetooth icon in menu bar changes to squiggly line which means Bluetooth is not available.
  • I am okay to disable this function in Catalina if the solution is not simple.

 

[Inqnuam]

About 2hours im working on a file which name should be "alldisks.plist"

So I was working on a another file

 

[Inqnuam]

@RandC
Everything is correct about the EFI side
I was able to load (simulate) your EFI disks list inside the app based on your aldisks.plist:

dont pay attention to disk Vendor names types and all, they are from my system

I'll come back to you later

 

[Inqnuam]

@RandC
Please try Special Version 10 below
I've added buttons:
Yoda will print text into Terminal (you need to open the binary of the app) and also sends some commands to the app!
Try: Will try to change the window to Settings (for test)
Reset all: to reset all configs..
Close: to close the app

 

[RandC]

@Inqnuam Well that version seems to not loop and presents mount opportunity. Here is the text from terminal. Please note that while it was running I hit the rescan button so things are repeated. Didn't see any special buttons.

rand@Hackintosh MacOS % ./HackinDROM


asked for +1 VolumeName subscriptMissingKey(path: AllDisksAndPartitions[1].Partitions[1], key: "VolumeName", bestMatch: nil)


asked for +1 VolumeName subscriptMissingKey(path: AllDisksAndPartitions[2].Partitions[1], key: "VolumeName", bestMatch: nil)


asked for +1 VolumeName subscriptMissingKey(path: AllDisksAndPartitions[1].Partitions[1], key: "VolumeName", bestMatch: nil)


asked for +1 VolumeName subscriptMissingKey(path: AllDisksAndPartitions[2].Partitions[1], key: "VolumeName", bestMatch: nil)

I've enclose screen shots of the mount panel. Cannot make it larger so took picture, scrolled, and took second picture.

I then hit Mount next to the first disk (boot disk) and it asked for my userid and password and had the userid filled in. I'm running at a non-admintrative user so when I typed my password, it just presented the dialog again. I then changed to an administrative userid and password and that then brought up another dialog that said I had to enter my administrative user and password. Once I did that the EFI partition mounted.

Hope this is enough info. If you need anything else, let know. Thanks so much for you hard work!

Thanks

Rand

 

[RandC]

@Inqnuam Just a few additional comments. In the disk list, the second Sabrent described as OS is a Windows boot disk. The OWC Mercury Electra is a Linux (Unbuntu) boot disk (won't boot through OC though, although I've not tried with 0.6.8). Have to boot from BIOS. The two Hard Drives appear to be correctly described.

 

[Inqnuam]

Didn't see any special buttons.

In this Special Version 10, special buttons are added just below the “Loading EFI” when it enters in loop

soo this is cool! Looks like it is working as excepted
I think the issue was juste about a thread execution
will try to optimize tasks in future versions
You can keep using SV10, it will update automatically when a new one is available

 

[Inqnuam]

@Inqnuam Just a few additional comments. In the disk list, the second Sabrent described as OS is a Windows boot disk. The OWC Mercury Electra is a Linux (Unbuntu) boot disk (won't boot through OC though, although I've not tried with 0.6.8). Have to boot from BIOS. The two Hard Drives appear to be correctly described.

Unfortunately there’s no way to know exactly what OS is installed
There’s no partitions names for theses 2 EFIs, so the method is to check the partition type if it is Microsoft file system then you’ll see “Windows + emoji” the emoji is for = I’m not exactly sur it is Windows!
When the apps detects as Windows and it is sure then you’ll see your partition name or just “Windows”

If it is Linux type file system then you’ll see “Linux + emoji”

Limitations yes, but I think it is better than juste “NO NAME” or empty

in realty EFI partitions volume name by default is “EFI”
HackinDROM renames theses “EFI” s to more identifiable name*
In addition it tries to find a partition that can be affiliated to that EFI
It is simple when it is a simple USB installation stick
But then it is about APFS format then we can have “unlimited” partitions,
HackinDROM tries to find a partition name which is “human friendly”: no empty partition name or just “VM” or multiple time “VM”
But all this is done when it is possible
When nothing is possible then a random name is given to make it different one from others

* HackinDROM’s renaming method is
EFI
-
First 3 letters of that drives Vendor/Model name
-
Last 3 letters/numbers of that drive’s serial number

Sooo for your “Windows + emoji” partition, simply because that partition is probably ms-dos type and not Linux's most used ext4 ext3 etc.

« OS » is the name of one of that disks partition which is affiliated to that EFI

 

[RandC]

Unfortunately there’s no way to know exactly what OS is installed
There’s no partitions names for theses 2 EFIs, so the method is to check the partition type if it is Microsoft file system then you’ll see “Windows + emoji” the emoji is for = I’m not exactly sur it is Windows!
When the apps detects as Windows and it is sure then you’ll see your partition name or just “Windows”

If it is Linux type file system then you’ll see “Linux + emoji”

Limitations yes, but I think it is better than juste “NO NAME” or empty

in realty EFI partitions volume name by default is “EFI”
HackinDROM renames theses “EFI” s to more identifiable name*
In addition it tries to find a partition that can be affiliated to that EFI
It is simple when it is a simple USB installation stick
But then it is about APFS format then we can have “unlimited” partitions,
HackinDROM tries to find a partition name which is “human friendly”: no empty partition name or just “VM” or multiple time “VM”
But all this is done when it is possible
When nothing is possible then a random name is given to make it different one from others

Thanks for the explanation. Guess I didn't see the buttons before the load completed. Ignore the Ubuntu Linux comments. I discovered (using HackinDROM to mount the EFI partitions) and somehow the Linux disk had an OC EFI and the Windows backup disk had the Ubuntu EFI. So moved the ubuntu EFI to the correct place and deleted the EFI on the Windows Backup disk (which is not a bootable Windows drive...discovered the hard way when I was building the machine and using the machine early on that having two Windows bootable drives is very bad for Windows ).

Thanks

Rand

 

[Inqnuam]

The screen "stuttering" problem (as in video posted yesterday) occurs when mouse is in the bottom part of Create EFI section.

Is this stuttering when you hover on boot args?

Bluetooth RSSI signal monitoring function causes mouse to freeze every 2-3 seconds. The freeze lasts about 1 second then mouse can move again. If we quit HackinDROM, then Bluetooth icon in menu bar changes to squiggly line which means Bluetooth is not available.

• I am okay to disable this function in Catalina if the solution is not simple.

actually this is also present in Big Sur too
But Big Sur threads management is better so only the app freezes
But this is easy to fix, just do not execute monitoring on the main thread (same as UI)
In next version!