A sig 11 usually indicates a hardware error, memory going bad, processor
failing/overheating. I'm not inclined to believe it's your drive, unless
you were using virtual memory at the time. If you are doing any over
clocking, try getting rid of that first, and running w/o the case closed.
If that doesn't give you any joy, try swapping out simms/dimms if you can.
It may help to isolate the error.
Also as another note, (You may be following this already but) the kernel
needs to be installed bellow cyln 1024, which means that you need the
partition that holds /boot to exist entirely bellow this limit to make
sure that you will not have problems. I don't think this would cause your
problem, but I thought I should warn you for future reference.
Good Luck
On Sun, 21 Nov 1999, Craig Christensen wrote:
> After I created my partitions and clickin on "OK" I got a blue window
> saying:
>
> install abnormally -- recieved signal 11
> sending termination signals...done
> sending kill signals...done
> unmounting filesystems... /mnt/sourceTab>/<alt-tab> between elements | <F12>
> next screen /dev/pts/proc
> you may safely reboot your system.
>
> Any clues?
>
> Craig Christensen
> [EMAIL PROTECTED]
>
>
>
--
Justin Oelgoetz
Email: [EMAIL PROTECTED]
Web: http://www.chemistry.ohio-state.edu/~joelgoet/
PGP: http://www.chemistry.ohio-state.edu/~joelgoet/pgp.txt
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
