On Thu, Oct 25, 2012 at 11:19 AM, Валерий Бицоев <valne...@gmail.com> wrote: > Binaries in EdkShellBinPkg works pretty good, but, unfortunately, i need to > build Shell, because i want to change some things.
I think it might be easier to change code in the newer UEFI shell. > 2012/10/25 Jordan Justen <jljus...@gmail.com> >> On Thu, Oct 25, 2012 at 6:53 AM, Валерий Бицоев <valne...@gmail.com> >> wrote: >> > I am trying to build with GCC44 and run any version of EFI Shell with >> > edk2. When I build ShellPkg and tried to run it, i got ASSERT() at >> > this point: >> > >> > // >> > // Retrieve the pointer to the UEFI HII String Protocol >> > // >> > Status = gBS->LocateProtocol (&gEfiHiiStringProtocolGuid, NULL, >> > (VOID **) &gHiiString); >> > ASSERT_EFI_ERROR (Status); >> >> I believe this is what happens when you try to run the UEFI Shell on >> an older (EFI, not UEFI) system. I think Andrew Fish might have previously mentioned that it was possible to run the new shell on older systems by first loading the HiiDatabase.efi and DevicePathDxe.efi drivers on the system first. To do this, first build MdeModulePkg for your architecture. Then locate HiiDatabase.efi and DevicePathDxe.efi under the build directory. Then load the two drivers in the old EFI shell on your system: > load HiiDatabase.efi > load DevicePathDxe.efi Then run the new Shell.efi. Can you give this a try? If this is not workable for you, maybe Andrew or I could test the current GccShellPkg to see if it working. -Jordan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
