Bart Silverstrim writes: > Um...because it took an adapter that generically had worked, but after > modifying it didn't?
It was referenced by an OS that generically worked, but then did not after the modification of the adapter. Note that it has not been established that any particularity of the adapter firmware is at the root of this problem. The meaning and cause of the messages and behavior I'm seeing remain unknown. > I have an old 68k mac laying here...think I can install > AmigaDOS on it? I don't believe so, but it has been a long time. > I and others on the list have suggested numerous times things like > self-contained Live-CD's of Linux/FreeBSD, or USB-bootable versions, > or talking to the actual developers instead of a USER MAILING LIST > (Not DEVELOPER), or swapping the controller out and get matching > drives to test against, or even paying someone to fix it with your > hardware to test on, or just going back to windows so you can ignore > the problem in the first place ... The one thing you have not done is explain the meaning of the messages I've seen. > As far as this list is concerned, it's not gonna happen. I'm not optimistic, but one never knows. > I've seen Linux report errors with drives that NT didn't. So? > Aren't you the same person that said MS changed features specifically > at your request, but you didn't remember what they were? Yes. > If so, you never did answer me on how you could have forgotten what > that feature was. It was quite some time ago. Much water has passed beneath the bridge. > ...how long has it taken you to realize that HP/Compaq > routinely do odd proprietary crap to their hardware? I've known it for years, but my evaluation of the pros and cons continues to evolve. > you didn't know what the Apple IIe is? Yes, I did. > You couldn't figure out why someone would suggest testing a problem on > another bit of identical hardware to isolate if it was a hardware > problem or a software problem? Someone might suggest that in order to seem knowledgeable, rather than admit that he has no clue as to the source of the problem. > How long have you been a sysadmin? Overall I have a fair number of years of experience in that capacity. Currently I only administer my own systems. > Get the multithousand dollar support contract with them, run exactly > what they tell you to run, and you'll be happy with the support they > would give. I don't think they'd approve of FreeBSD. > how long have you been doing this, anyway? A couple of decades. > I heard a similar type of argument from a five year old. Small children have a way of getting straight to the point that their elders might sometimes do well to emulate. > I've had several machines where distro X wouldn't work but Distro Y > did. But by your logic, this isn't possible, right? I haven't tried any other distributions. I don't know the source of the boot problem, so it's hard to say. > You're right. You're getting much farther by insulting people and > being obstinate when given suggestions. Apply that same logic consistently, and you'll see the source of my frustration. > What a dichotomy to your insults of FreeBSD developers. Dichotomy? > You mean, it could be buggy or have problems that are "ignored", but it > still "works" anyway and gets the MS stamp? Yes. > But, how could this be? The certification tests are not exhaustive. -- Anthony _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
