At 12:57 17-6-00 +0200, you wrote:
>Richard Schiffelers <[EMAIL PROTECTED]> writes:
>
> > i now trying to get it to install but am getting stuck at the end where it
> > comes to getting the aboot part installed. When it tryes to install aboot
> > it gives a error message and then ask whether it should nevertheless force
> > the install of aboot. If i then afterwards try to boot from the srm
> console
> > is says it can't find a valid bootblock.
>
>Could you first have a look at /tmp/exec.log (switch to console 2 using
>ctrl-alt-f2)
>
>Explaination of what DrakX try to do:
>
>the 2 commands used are swriteboot and abootconf.
>or maybe try doing it yourself and see what happens:
>% chroot /mnt
>% swriteboot /dev/sda1 /boot/bootlx
>or
>% swriteboot -f1 /dev/sda1 /boot/bootlx
>but beware, it may break things on the first partition (see man swriteboot)
>(that's what force install aboot does)
>then
>% abootconf /dev/sda1 1
>
>hope it will help, cu Pixel.
Problem is solved. In the past i only worked with AlphaBIOS and then you
don't need to do anything special with the diskconfiguration. However when
using the srm console you have to use BSD-style disk labels which i didn't
and therefore aboot failed.
Everyone thanx for all the help, system is now up and running.
Richard ([EMAIL PROTECTED])
p.s. Two tips/suggestions for the Mandrake people:
1. The extension cd is being refered to as ... (x86), Should be Alpha (is
only text)
2. As i ran into the BSD-style disk label problem the creation of the label
during the fdisk part, later when the aboot question comes it is already to
late to fix it.