Felix Miata <[EMAIL PROTECTED]> writes: [...]
> > bugged and doesn't report failures, or your floppy has an > > hardware failure that didn't report to the floppy drive during > > bootdisk creation but lead to a misread when you tried to boot > > with it. I would favor the second option. > > Not likely on mine. 8.2 installed just fine, but beta 3, beta 4, RC1, & > RC2 all did the same thing as above with me, except Beta 3 created > several zero byte files on the floppy. No zero byte files on the three > latter, but same error message when attempting boot as above. On all Is the floppy full? What happens when you try to copy the contents to the hd? And when you try to mount it? And when you try to read the files on it? > four 9.0 installs, installation boot was initiated from floppy, > network.img on the first, and hd.img on the latter three. On RC1 I > attempted mkbootdisk & drakfloppy after booting the HD, but got no > improvement. I emailed cooker list about this Thu, 29 Aug 2002 00:29:20 > -0400 & Tue, 03 Sep 2002 03:00:11 -0400 & Thu, 05 Sep 2002 21:32:33 > -0400 and got no replies. When no one answers on this list, it generally means that either: 1- the bug is likely to be invalid (happens when only one person reports something which is unlikely to happen) 2- the bug is considered non important, or we have more important bugs pending 3- the reporter doesn't report enough information 4- the reporter writes 200 lines talking about his life, so no one bothers wasting time to read 5- it would need much investigation from the reporter and we consider it would be a useless effort to try to initiate it 6- we don't have the knowledge to fix it 7- serveral people reported the same problem but the reports are inconsistent with each other 8- a similar problem has recently been fixed and the reporter doesn't clearly specify the version of software with failure (of course, I may have forgotten other situations ;p) In this situation, I'd favor `2', but it's true that the problem also needs investigation from the people involved. Also, a big problem is that floppies are very likely to have hardware failures. Many times with similar bugs we spent time trying to investigate, just to see that it was only due to h/w failure, so most of the times we don't bother. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
