I need some help dual booting STABLE & CURRENT. I have two SCSI disks
with:
STABLE taking the entire first disk (works fine)
CURRENT taking the first 1/3 of the second disk and
backup data taking the remaining 2/3 of the second disk.
I have installed CURRENT (at least 8 times) but I cannot get it
On Sat, Nov 01, 2003 at 01:26:10PM -0800, Steve Wingate wrote:
> STABLE taking the entire first disk (works fine)
> CURRENT taking the first 1/3 of the second disk and
> backup data taking the remaining 2/3 of the second disk.
>
> I have installed CURRENT (at least 8 times) but I cannot get it to
On Sat, 1 Nov 2003, Steve Wingate wrote:
> I need some help dual booting STABLE & CURRENT. I have two SCSI disks
> with:
> STABLE taking the entire first disk (works fine)
> CURRENT taking the first 1/3 of the second disk and
> backup data taking the remaining 2/3 of the second disk.
>
> I have
>
> Try to install booteasy from STABLE, only from STABLE, to both
> harddisk. don't install booteasy when install CURRENT
> or try to recover boot easy from STABLE on the second hardisk as
> described in the handbook
> it works for me
>
> sham khalil
I have tried this and it still doesn't boot t
On Sat, 1 Nov 2003, Steve Wingate wrote:
> I need some help dual booting STABLE & CURRENT. I have two SCSI disks
> with:
> STABLE taking the entire first disk (works fine)
> CURRENT taking the first 1/3 of the second disk and
> backup data taking the remaining 2/3 of the second disk.
>
> I have in
> "Nothing happens" probably means "its beeping but I can't hear it" :)
>
> If that happens, its because boot0 and the BIOS can't figure out how to
> reach the partition, generally because the geometry is wrong. Try zeroing
> off the front end of the disk, partitioning it with DOS FDISK, then put
On Sat, 1 Nov 2003, Steve Wingate wrote:
> > "Nothing happens" probably means "its beeping but I can't hear it" :)
> >
> > If that happens, its because boot0 and the BIOS can't figure out how to
> > reach the partition, generally because the geometry is wrong. Try zeroing
> > off the front end of
> > I don't like the sound of that. I'll just stick with STABLE until 5.x is
> > really ready.
>
> -STABLE will have the same problem since its in boot0 and the BIOS, not
> the OS on the partition its trying to boot.
Actually STABLE will have no problems as it's been running on this box for
over a
Sat, Nov 01, 2003 at 20:38:36, s.wingate (Steve Wingate) wrote about "Re: Dualbooting
STABLE & CURRENT":
> >> I don't like the sound of that. I'll just stick with STABLE until 5.x is
> >> really ready.
>> -STABLE will have the same problem since
