Sean Armstrong wrote:
> With all due respect, If you had read my earlier emails on this subject you
> would have seen that I have installed every Linux distribution out there and
> was even able to install the Mandrake 7.02 dist. on another computer. The so
> called bug is not 'my' mistake, but the mistake of Mandrake. They have had
> this problem with 7.0 since the Oxygen release, and even though many people
> complained of the problem to Mandrake they refused to fix the BUG!!! This is
> a corporate problem with Mandrake and they need to pull their respective
> heads out of their self righteous arses before they rush a BETA product to
> market under the guise of a final product. I probably would not be so
> irritated if they had a fix for the BUG, but they don't and like others, you
> have failed to give any helpful information on fixing the problem. Good Day
> and Good Luck.
> SA
Heehee, RH reliable? I have found Mandrake demanding on HW, but just because
new code exposes problems that always existed in certain hardware is no reason
to act like you had three containers of caffeinated peppermints in two minutes.
For example Some Seagate IDE and Most WD IDE have data problems under any form
of UDMA with 586 and 686 code. The reflection of signals causing the problem
always existed, but only the timing requirements of the "optimized" code makes
it apparent. That's a hardware problem. Returning to 386 code may make it
transparent but it doesn't make it go away.
I have always found RH distros to have their rough edges and a healthy share of
bugs. The situation here is different. Mandrake demands pretty good hardware,
just as Enoch or Stampede does.
But you did say yours worked in 6.1. I was and am very happy with 6.1.
I upgrade to 7.0-2 only on machines where I need some specific feature, and
most of those are covered by the GOLD Pack anyway... Still using 6.1.
And lessee--I have a DLINK card which has Ethernet and modem on it which works
fine in Win 3.1 and not at all in later versions. It was built for a Win95
Beta and in the final they changed the addressing method for PCMCIA cards.
The fact is, op systems progress while hardware already bought doesn't change.
It is natural to expect some obsolescent devices to stop working.
Moreover, I did not hear from you that you retested this drive with the
previously working 6.0 or 6.1. Hardware doesn't last forever, and the
positioning mechanisms of CDs are very precise and subject to wear.
So I think just a little cooling of jets is in order. I know you may have
differing experience, but mine has been that when I have a problem, more than
90% of the time, the problem has its hands on my keyboard<g>. Verify that your
drive still works with your old software before going ballisitc on Mandrake for
recompiling with optimized code. Verify that MD5 Sum worked, and most of all,
burn slowly with a media you know your old drive will read reliably. You
assume it is Mandrake 7.0 when it may be
1. Your aging drive (I have thrown away SIX that would not read parts of CDs
this year, FreeBSD, SuSE, Windows, etc could not be installed using them)
2. A bad DL or burn
3. Media that your old CD won't read reliably.
4. Media that your burner won't do reliably
5. The wrong burn speed (some older drives do not reliably read quickly
burned CDs)
Of course, if you want to dismiss all those possibilities and run to another
distro, that is your choice.
Civileme
