Make Install GNUPG/Bootloader Dual Boot Probs

[smartgenes]

On trying to do a 'MAKE INSTALL' using GNUPG I come up with the error message below about permissions. I'm trying to install the prog so that I can use the key given on the Debian site, so I can run ms-sys_2.1.0-1_amd64.deb (and thus restore my Windows in the dual boot set up).
I have no idea how I will use the key once I get the prog working, I'm totally new to Linux.
I got the error "The following signatures could not be verified because the public key is not available" and I think the way to solve this is the installation of GNUPG.
My real problem is the bootloader which doesn't load XP. The XP disc does not allow any entries in the command prompt in Recovery (some problem reading the drive?)
So I'm trying to dload MS-SYS to attempt to modify the bootloader from a Terminal.
Any help appreciated...

make[1]: Entering directory `/home/steve/Techy Downloads/gnupg-1.4.9/cipher'
make[2]: Entering directory `/home/steve/Techy Downloads/gnupg-1.4.9/cipher'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/steve/Techy Downloads/gnupg-1.4.9/cipher'
make[1]: Leaving directory `/home/steve/Techy Downloads/gnupg-1.4.9/cipher'
Making install in tools
make[1]: Entering directory `/home/steve/Techy Downloads/gnupg-1.4.9/tools'
make[2]: Entering directory `/home/steve/Techy Downloads/gnupg-1.4.9/tools'
test -z "/usr/local/bin" || /bin/mkdir -p "/usr/local/bin"
/usr/bin/install -c 'gpgsplit' '/usr/local/bin/gpgsplit'
/usr/bin/install: cannot create regular file `/usr/local/bin/gpgsplit': Permission denied
make[2]: *** [install-binPROGRAMS] Error 1
make[2]: Leaving directory `/home/steve/Techy Downloads/gnupg-1.4.9/tools'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/steve/Techy Downloads/gnupg-1.4.9/tools'
make: *** [install-recursive] Error 1

[valemon]

Hello and welcome to LF!

An easy way to restore MBR is the super grub live cd. I also may be able to help you. Post the output of commands

sudo fdisk -l
sudo cat /boot/grub/menu.lst

also regarding your install issue are you installing with sudo?

[smartgenes]

I'm not even sure what Sudo is... I was following the ReadMe for GnuPG after unpacking:

3) "cd gnupg-x.y.z"

4) "./configure"

5) "make"

6) "make install"

7) You end up with a "gpg" binary in /usr/local/bin.

8.) To avoid swapping out of sensitive data, you can install "gpg"
setuid root. If you don't do so, you may want to add the
option "no-secmem-warning" to ~/.gnupg/gpg.conf

I also discovered in the process that putting spaces in folder names is not go/ /od...

The output below:

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xa617a617

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4102    32949283+   7  HPFS/NTFS
/dev/sda2            4103        9729    45198877+   5  Extended
/dev/sda5            4103        9553    43785126   83  Linux
/dev/sda6            9554        9729     1413688+  82  Linux swap / Solaris
steve@steve-desktop:~$ sudo cat /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### 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=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc

## 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=quiet splash

## 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=(recovery) single
# altoptions=(recovery mode) single

## 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## 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		Ubuntu 9.04, kernel 2.6.28-11-generic
uuid		4143364d-ab25-4bb1-a5b8-0cafaeeb90bc
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc ro quiet splash 
initrd		/boot/initrd.img-2.6.28-11-generic
quiet

title		Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid		4143364d-ab25-4bb1-a5b8-0cafaeeb90bc
kernel		/boot/vmlinuz-2.6.28-11-generic root=UUID=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc ro  single
initrd		/boot/initrd.img-2.6.28-11-generic

title		Ubuntu 9.04, kernel 2.6.27-7-generic
uuid		4143364d-ab25-4bb1-a5b8-0cafaeeb90bc
kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc ro quiet splash 
initrd		/boot/initrd.img-2.6.27-7-generic
quiet

title		Ubuntu 9.04, kernel 2.6.27-7-generic (recovery mode)
uuid		4143364d-ab25-4bb1-a5b8-0cafaeeb90bc
kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=4143364d-ab25-4bb1-a5b8-0cafaeeb90bc ro  single
initrd		/boot/initrd.img-2.6.27-7-generic

title		Ubuntu 9.04, memtest86+
uuid		4143364d-ab25-4bb1-a5b8-0cafaeeb90bc
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title		Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title		Microsoft Windows XP Professional
root		(hd0,0)
savedefault
makeactive
chainloader	+1

Thanks for the quick response!

[valemon]

sudo in front of a command means you get root privileges for that command.

sudo apt-get install build-essential

Run the above to get build-essential package.
For installing apps before typing each command to install type "sudo". "sudo su" gets you root privileges so you don't have to type each time sudo. Just be carefull
Then you should be able to install whatever application you need.

Now regarding your real problem, as I can see, your menu.lst entry for windows is correct, maybe you could tell what error does grub give you?

[smartgenes]

When I do the Sudo command I'm getting a response related to when I was setting up my email with Hotway/Evolution... how do I reset the installer info?

Port 110 is in use │
│ │
│ It looks like xinetd (pid 236 is already using port 110, the standard │
│ port for POP3 servers. Hotway will need to use something else. │
│ Unfortunately, there's no simple way for this configuration script to │
│ set up your inetd to use a different port, so you will need to do that │
│ yourself. │
│ │
│ Alternatively, uninstall any other POP3 servers you may have installed, │
│ and then reconfigure hotway.

The error message from Grub (Grub being the bootloader for both apps?) as I start XP is displayed on a blue screen in a microsecond so I can't read it...

[smartgenes]

Now I get this message on typing the sudo command:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

Sorry if this is something obvious, but Linux is new to me.

[valemon]

The errors you get possibly occur because you have synaptic or update manager running. Wait until they finish or stop em.
Regarding your windows boot problem, I am afraid Linux is not responsible for that blue screen (BSOD )

[smartgenes]

Synaptic Manager is saying a similar thing about another process using it... how to stop it?

[valemon]

Hmm try

sudo killall synaptic && killall aptitude && killall apt-get

[smartgenes]

Killall told me "synaptic: no process killed", attempting "sudo apt-get install build-essential" afterwards brought the same message about port 110 (pid2376) being in use...