typing up and down the following commands as the link tells me to do

[SOLVED] error: symbol 'grub_term_highlight_color" not found. grub rescue>

always coming back to grub rescue> the same procedure as every time,

Code:

error: symbol 'grub_term_highlight_color' not found

then

Code:

entering rescue mode....

Code:

'grub rescue> 'dpkg-reconfigure grub-pc' for effect'

Code:

>set
>set prefix=(hd0,1) /boot/grub
>set root=(hd0,1)
>set insmod normal
>normal
>insmod linux
>linux /vmlinuz root=/dev/hd0,1 ro
>initrd /initrd.img
>boot

and looping back to
grub rescue>

even trying

Code:

fschk -y /dev/hd0,1

gives me no reply at all. The first repair-kit is on an usb-drive formatted in FAT32 to repair grub. Entering the BIOS it is flashing from the usb-drive.
Before all that I tried without success to execute the commands above with
sda for SATA-hdd.
And not even

Code:

'fdisk -l'

seems to work. Think I am done with uefi. :-(

---------- Post updated at 11:42 PM ---------- Previous update was at 09:54 PM ----------

Starting now in efi mode the mobo tells me startup.nsh, wow, backslashes all over the place. This shell must be nuts.
This link gets me some help
https://packages.debian.org/wheezy/grub-efi-amd64
allthough I am at the very beginning of this.

Code:

 EFI Shell version 2.31 [5.8]
    Current running mode 1.1.2
    Device mapping table
      fs0  : Harddisk - Alias hd5a65535a1   blk0
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)/HD(1,...,0x800,0xF3800)
      blk0 : Harddisk - Alias hd5a65535a1   fs0
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)/HD(1,GPT,...,0x800,0xF3800)
      blk1 : Harddisk - Alias (null)
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)/HD(2,GPT,...,0xF4000,0xBA43800)
      blk2 : Harddisk - Alias (null)
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)/HD(3,GPT,...)
      blk3 : Harddisk - Alias (null)
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)/HD(4,GPT,...)
      blk4 : BlockDevice - Alias (null)
             PciRoot(0x0)/Pci(0x13,0x0)/Sata(0x0,0x0)
      blk5 : BlockDevice - Alias (null)
             PciRoot(0x0)/Pci(0x1C,0x1)/PCI(0x0,0x0)

    Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
    Shell>

Code:

fdisk -l is not recognized as an internal or external command, operable program or batch file. Invalid file system mapping on hd16c0b

...great.

while trying to unpack the rescue-kit on my usb-device, at the laptop there it says after typing

Code:

root@rechenknecht2:/media/usb0/save# mount -o loop -t iso9660 grub-efi-amd64_1.99-27+deb7u2_amd64.deb /media/usb0/save
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

where the directory named /save is containing the debian-file. So there is a conflict at the basic, where the usb-drive with this very specific debian-packet is on an usb-drive that is formatted in FAT32 to fullfill the requirements of UEFI but working in the wrong place.
Any hints for this nutshell of microsoft? Setting the SATA to another plug? Thanks in advance.

quote:

"This represents only the beginning of the uses and benefits of EFI shell commands and scripts. Not only can EFI be used similarly to a MS-DOS device driver, its capabilities also remove the hassle of modifying the OS. Disk utility vendors can use EFI to craft powerful tools like platform-independent disk partitioning. Another of EFI's benefits is that the same device drivers can be used by many EFI-compliant platforms, thus providing a good return on investment. EFI allows users to create device drivers to access hardware directly without having to go through the OS, making the process both simpler and faster."

from
https://software.intel.com/en-us/art...-and-scripting

getting tired......to be simpler and faster, way beyond my expectations.