Damaged Boot of a Dual OS System

0

Dear and expert friends!

First of all, I want to wish you all a very happy new year. That day I sat in front of my dual boot operating system (Linux and Win XP) which has served me extremely well since Mike Walsh helped me set it up in 2019 and was greeted by a strange message that was NOT NORMAL at all. my laptop; this is what I saw and what I did:

GRUB4DOS 0.4.4 20-06-2009, Memory: 639K / 986M, End of menu: 0x48EB8

[ Minimal BASH-like line editing is supported. For the first word, TAB

  lists possible command completions. Anywhere else TAB lists the possible

  completions of a device/filename. ESC at any time exits. ]

grub> (‘grub>’ is followed by a blinking cursor)

=================================================== ==========================

NB The possible commands via the “TAB” key are:

background blocklist boot cat cdrom chainloader checkrange

checktime clear cmp color commandline configfile dd debug default

displaymem embed errnum errorcheck fallback find foreground fstest

geometry stop help hiddenflag hide initrd install is64bit kernel

lock ls makeactive map md5crypt module modulenounzip contour

pager partnew parttype password pause pxe quit read restart

root rootnoverify savedefault serial setkey setup setvbe splashimage

terminal terminfo testvbe tpm display uuid vbeprobe write

grub> (‘grub>’ is followed by a blinking cursor)

=================================================== ==========================

NB I tried “grub> help” and I saw a list in two columns giving

examples of how all of the above commands should be executed. Some

the examples were truncated and therefore incomplete. Here are 4 examples

showing the lines (having the same length) of truncation:

partienew [–active] PART TYPE START [LE

     setup [–prefix=DIR] [–stage2=STAGE2_

     terminal [–dumb] [–no-echo] [–no-ed

     write [–offset=SKIP] ADDR_OR_FILE INT

and some commands had no example: boot

clear

displaymem

is64bit

lock

md5crypt

to restart

I pressed “ESC” to exit and a box with the following displayed:

find /menu.lst, /boot/grub/menu.lst, /grub/menu.lst

command line

to restart

stop

with these instructions under the box:

Use the up and down arrow keys to highlight an entry.

Press ENTER or ‘b’ to start. Press ‘e’ to edit commands

before starting, or ‘c’ for a command line.

At this point I selected “halt” and got:

Start stop

followed by the blinking cursor several lines below the command

Text “Stop start”. I pressed ENTER again, but nothing happened and

I had to manually shut down my laptop to force it to shut down.

And now I am the sad owner of a HP-Mini Dual OS Laptop (XenialPuppy 7.5

& Win XP) which apparently has a broken / damaged boot process. Your

expert help is definitely needed and I would be very grateful to

agree with you with step-by-step instructions on how to proceed to remedy the

the embarrassing situation I find myself in now. I am writing to you

thanks to the ACER laptop (Windows 7 OS) of a friend of the local public

library because the HP-Mini is not functional.

Hoping someone can help sort it out!

Stone in thailand


Source link

Share.

Comments are closed.