On 14-Apr-00, Chris Wiles wrote:
> ie. if you had to 'manually rename it' (since when do you need to do that
> anyhow? ;),
With most programs that come with cpu specific versions.
> I would have told you a long time ago.
Maybe. You have actually not yet achieved outstanding fame for telling
people what they need to know. That's a common and widely recognised
failing of people who understand a piece of software 100% and have difficulty
putting them selves in the place of people who are struggling to try
to come to grips with it.
> Yes, you *could* rename amitcp.020 to 'amitcp',
> but then if you only had
> an 00 processor, this would cause a crash, of course.
I would expect anyone trying to use the NetConnect suite on a 68000
would have difficulty telling the difference between a crash-freeze and
normal operation anyway. If a 68000 owner changed amitcp.020 to
amitcp, they would deserve a crash.
> 2) As above, you should never start to 'fiddle' with things,
> when they are shipped in a particular way.
Does that apply also to people 'fiddling' with downloading a new
Voyager or MD-II instead of using it as 'shipped in a particular way'?
The only limitation needed on fiddling is that people need to be able
to undo their fiddling if it causes something to break, and that the
fiddling should have some rational reason and purpose.
I've certainly fiddled with everything in Genesis/AmiTCP for which
there was no documentation supplied. One of my best sources of
information about using Genesis/AmiTCP has been c.s.a.networking,
and shame of shames, Holger Kruse. That seems like going to the
BeOS shop for help with Linux, or vice versa.
Regards
--
Irony? We don't get much of that around here.
<tsb>
Support *Open Directory Project* No Banners, No junk-just information.
*ODP *is built by volunteers and owned by the community .
*-------> http://dmoz.org <*-----------Check it out
<sb>
*Patrick Ford Auckland, New Zealand*
*/#fidonet#/ 3:772/235.3 #/icq#/ 51642681*
<tsb>
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
