Hello, I'm new in the forum, and they are also inexperienced with Linux ... I wanted to try Antix 12 on my old computer, and after seeing him live, I installed a dual boot with XP ... The problem is that now Antix starts while xp no, when I start the computer and I select xp from grub gives me this error:
map (HD0)
Error 11: unrecognized device string
Press any key to continue ....
I do not understand where I went wrong in the installation, since xp is on sda1, Antix is on sda6, swap sda5, when asked where to install grub I left sda.
Can anyone help me, to understand why this happened? I'd like to have both systems, can you?
Thank you and sorry for the imperfect English!
__{{emoticon}}__

can-t-boot-into-windows-t3771.html

antix12-grub-menu-lst-t4022.html

Howdy and Welcome. Happy Trails, Rok

I suppose this will help:

post26972.html#p26972

*********
map (hd0)
map (hd0)
rootnoverify ,0)
chainloader +1
***********
I changed it to just
root (hd0,0)
chainloader +1

and it worked

and welcome

Edit your menu.lst: windows entry to look like this.
Open Antix Control center then System, select Edit Config Files you will see menu.1st
This has always worked for me.
If you have more than one (hd0) it was also detecting your restore partition.

I have to give some command from the terminal type"update grub" after editing? thanks

I modified the menu.lst file as shown in the way of Lagopus and then as indicated by Eino, I read the posts that you have indicated to compare the configuration files, I modified by opening the file with leafpad, coming from the terminal as root (sux), saved and restarted. But nothing xp does not work.

maary79 wrote:I have to give some command from the terminal type"update grub" after editing? thanks

No. This is one of the advantages of Grub. You don't have to do anything extra after editing menu.lst.

maary79 wrote:I modified the menu.lst file as shown in the way of Lagopus and then as indicated by Eino, I read the posts that you have indicated to compare the configuration files, I modified by opening the file with leafpad, coming from the terminal as root (sux), saved and restarted. But nothing xp does not work.

Did you get the same error message? It helps us help you if you report the error messages exactly. It is almost the only information we have to try to figure out what is wrong.

The output of"sudo blkid" might be useful too so we can double check that things are actually where you think they are.

The output of"cat /boot/grub/device.map" would also be good to see.

Hi, Yes, it always gave me the same error.
Output:
sudo blkid
/dev/sda1: UUID="70C84F66C84F29A4 TYPE="ntfs"
/dev/sda5: UUID="6d01e93b-9fac-4bf3-b3f6-38cea572c9a1" TYPE="swap"
/dev/sda6: UUID="57579235-ff30-4161-912c-c6477106ce89" TYPE="ext4"

cat /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-Maxtor_4D040H2_D211YWSE

Thanks.

Post the contents of /boot/grub/menu.lst

File menu.lst:

timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title antiX at sda6, kernel 3.5.0-antix.2-486-smp
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=/dev/sda6 nomce quiet nosplash nouveau.modeset=0 vga=791
initrd /boot/initrd.img-3.5.0-antix.2-486-smp
boot

title Microsoft Windows XP Home Edition at sda1
map (hd0)
map (hd0)
root (hd0,0)
savedefault
makeactive
chainloader +1

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=57579235-ff30-4161-912c-c6477106ce89 ro
# kopt_2_6=root=UUID=57579235-ff30-4161-912c-c6477106ce89 ro nosplash quiet

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,5)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(init-3) 3

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title antiX-12, kernel 3.5.0-antix.2-486-smp
root (hd0,5)
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=UUID=57579235-ff30-4161-912c-c6477106ce89 ro
initrd /boot/initrd.img-3.5.0-antix.2-486-smp

title antiX-12, kernel 3.5.0-antix.2-486-smp (init-3)
root (hd0,5)
kernel /boot/vmlinuz-3.5.0-antix.2-486-smp root=UUID=57579235-ff30-4161-912c-c6477106ce89 ro 3
initrd /boot/initrd.img-3.5.0-antix.2-486-smp

title antiX-12, kernel memtest86+
root (hd0,5)
kernel /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

Thanks.
Mary

I am no good at this, but grub counts hd0,0 as #1, and hd0,1 as #2, and so on, right?
So if you have antix on sda6, it should be hd0,7???

Just asking...
sorry, but I have no idea about the xp problem.

Try changing the M$ lines to
or

rust collector wrote:So if you have antix on sda6, it should be hd0,7???

no rust!
when grub counts (hd0, 0) = sda1
then sda6 = (hd0, 5) __{{emoticon}}__

i would guess the map (hd0) lines are causing the string error. once grub finds a string it doesn't recognize, it stops processing the menu.lst entry. in effect, grub is never getting to your boot entries.

i personally use anti's first option in his post above without any issue.