InitShellApp: Application not started from Shell
This is for sas2flash.efi and lsi_util.efi ( SAS cards)
-rw-r--r-- 1 d d 952768 Sep 5 2019 Shell64U.efi
-rw-rw-r-- 1 d d 771136 Dec 15 16:12 Shell_Full.efi
-r--r--r-- 1 d d 922272 Mar 13 2021 shellx64.efi
I don't know if the permissions matter on fat32,,
it does run and behave normally (shellx64,Shell_Full)
the last is what is in 0.13.2,,,, doesn't work
Shell_Full does work (renamed of course),
the LSI programs behave just as in linux
I have not run the 1st, so I can't say anything about it (shell64U)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, the shell included in 0.13.2 (the current release of refind)
When executing sas2flash.efi (a flashing utility for lsi SAS cards)
(lsi, now broadcom, make an industry standard "serial attached scsi " series of cards)
says
InitShellApp: Application not started from Shell
(I would not expect sas2flash.efi to start from refind, they are cli programs)
I was worried that the permissions on Shell_Full would stop it from executing,
it does (execute normally, renamed of course so it shows up in refind)
shell_full also executes those programs normally (sas2flash,, lsi_util)
sorry, sometimes I write too compressed
Oh, mb is a b360m-a 8th gen intel,,,, ami bios, bios updated to current, only 2-3 yr old
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That was enlightening,,, vers BTW doesn't work, nor vers -s
Just today I realized the mb has a builtin shell
AMI, , spec 2.70 ,, rev 5.13
-
0.13.2 shell,,,,,2.2
Full shell,,,,,,1.0
64U shell,,,,,2.204
-
So I guess those efi programs want a version 1 shell, they are a bit older
(2015,,,,?2009?,,, the older program, lsi_util, is EXTREMELY useful and powerful)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
updated my post. The command is ver.
Yes, it does appear they want a version 1 shell but it's difficult to say what about a version 1 Shell they are looking for since most commands should work from any Shell.
InitShellApp: Application not started from Shell
This is for sas2flash.efi and lsi_util.efi ( SAS cards)
-rw-r--r-- 1 d d 952768 Sep 5 2019 Shell64U.efi
-rw-rw-r-- 1 d d 771136 Dec 15 16:12 Shell_Full.efi
-r--r--r-- 1 d d 922272 Mar 13 2021 shellx64.efi
I don't know if the permissions matter on fat32,,
it does run and behave normally (shellx64,Shell_Full)
the last is what is in 0.13.2,,,, doesn't work
Shell_Full does work (renamed of course),
the LSI programs behave just as in linux
I have not run the 1st, so I can't say anything about it (shell64U)
It is unclear what you are talking about. Can you rephrase, using longer sentences and less pronouns?
Where are sas2flash.efi and lsi_util.efi from?
Is the problem that they cannot be run directly from rEFInd?
Or is the problem that they cannot be executed using the shell that is included in rEFInd?
"it does run and behave normally (shellx64,Shell_Full)"
What is "it"?
"the last is what is in 0.13.2,,,, doesn't work"
What is "last"?
What computer are you using? What version of EFI or UEFI does it have?
OK, the shell included in 0.13.2 (the current release of refind)
When executing sas2flash.efi (a flashing utility for lsi SAS cards)
(lsi, now broadcom, make an industry standard "serial attached scsi " series of cards)
says
InitShellApp: Application not started from Shell
(I would not expect sas2flash.efi to start from refind, they are cli programs)
I was worried that the permissions on Shell_Full would stop it from executing,
it does (execute normally, renamed of course so it shows up in refind)
shell_full also executes those programs normally (sas2flash,, lsi_util)
sorry, sometimes I write too compressed
Oh, mb is a b360m-a 8th gen intel,,,, ami bios, bios updated to current, only 2-3 yr old
rEFInd can start cli tools such as gptsync and gdisk so it might be able to do the same for sas2flash.
rEFInd doesn't have a method to add arbitrary tools but it should allow adding them as a main loader using the menuentry command in the conf file.
For each shell, get the results of the following commands:
verver -sLast edit: joevt 2021-12-19
That was enlightening,,, vers BTW doesn't work, nor vers -s
Just today I realized the mb has a builtin shell
AMI, , spec 2.70 ,, rev 5.13
-
0.13.2 shell,,,,,2.2
Full shell,,,,,,1.0
64U shell,,,,,2.204
-
So I guess those efi programs want a version 1 shell, they are a bit older
(2015,,,,?2009?,,, the older program, lsi_util, is EXTREMELY useful and powerful)
updated my post. The command is
ver.Yes, it does appear they want a version 1 shell but it's difficult to say what about a version 1 Shell they are looking for since most commands should work from any Shell.
The version 1 EFI Shell is available at https://github.com/tianocore/edk2/blob/UDK2018/EdkShellBinPkg/FullShell/X64/Shell_Full.efi
The version 2 UEFI Shell is available at
https://github.com/tianocore/edk2/blob/UDK2018/ShellBinPkg/UefiShell/X64/Shell.efi
OpenCore has their own Shell called OpenShell based on the version 2 UEFI Shell.