Thanks Bill. I have had a successful reinstall which has been marred by rapid modem timeout after about a minute. This does not happen on my XP drive, so it is not the ISP. I saw an error message flash by which I did not catch, and 'apt-get update' cannot stat any of the source addresses so I cannot dist-upgrade or fix dependency errors. It looks like a misconfiguration but I can't find the source (pppconfig?).
Any ideas? Adam Bogacki P.O. Box 38, Earlwood, NSW 2206, Australia [EMAIL PROTECTED] [current ISP] [EMAIL PROTECTED] [forwarding] -----Original Message----- From: Bill Taylor [mailto:[EMAIL PROTECTED]] Sent: Friday, 22 March 2002 11:34 AM To: Adam Bogacki Subject: Re: [SLUG] Potato 2.2r4 re-install problem Hi Adam, how have you gone with the install problem? I have done much the same with the same problems occurring. I further complicated the issue though, by using a new 40G drive, with the intent of using it as hda when I had it all setup. my partition structure is hdb1 / boot.......rh hdb2 / boot.......deb hdb3 windboot ..(250m) hdb4 extended hdb5--16 have rh on the odd numbers, debian on the even. adjacent partitions have the same name. the box is 6 months old, duron 900 , now with 60 G I was getting the same messages with the boot disk generation, finally fixed when I went out and bought a box of new disks. Because windoze writes it's boot to MBR I installed it first, so I could let lilo overwrite it when I installed rh 7.2 , (which I have installed so many times can do it in 15 minutes) then debian . there seems to be a problem with starting from the second drive, I'm starting everything with floppies at this stage. The hdb MBR should now be empty, or have a dead lilo in it, as I have changed the rh lilo back to hdb1, (/boot (rh)), and the deb lilo is in hdb2 /boot (deb) the plan is to use GAG, although someone on slug mentioned grub can do it. (can't tell you where, it's on my hda , but it was in answer to a question I asked, Jeff put me onto GAG in the same posting) I pulled the power lead from hda to do this, so I'm not up to the point where I 'm worrying about booting yet, but to save problems with renaming of drives if I swap them I may leave that alone, and put the boot loader on the hda MBR. basically, I let each install do it's own thing, then edited rh which I am most familiar with . Your problem seems to be the boot disk , because you have to be able to get in to edit. new disks worked for me. cheers Bill -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
