No this is my grub.cfg:
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set=root e23402e9-d6df-4c19-867c-2b1f623a9206
if loadfont /boot/grub/unicode.pf2 ; then
set gfxmode=auto
set gfxpayload=keep
insmod gfxterm
insmod video
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set=root e23402e9-d6df-4c19-867c-2b1f623a9206
insmod png
if background_image /boot/grub/beyond-the-clouds.png ; then
set color_normal=white/black
set color_highlight=yellow/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
set timeout=5
menuentry "Microcore-3.8" {
insmod ext2
set root=(hd0,1)
linux /boot/bzImage tce=LABEL=microOS/mc-ext restore=LABEL=microOS/mc-hm noswap kmap=uk TZ=GMT acpi_enforce_resources=lax waitusb=10 quiet --
initrd /boot/microcore.gz
}
The key seems to be that with the earlier version of grub2 TC interrupts with a text-only error report which does not interfere with my grub splash screen whereas with ver 1.99 it interrupts with a text + graphics error report - and it is this that switches off my splash screen. It is v. annoying but as I say I could return to 1.98 although I only have one system with this version now. TC has 1.99 in its repository.