> Chris, I suspect that Mike understood this perfectly well and was asking
> whether Genesis uses the "AmiTCP" binary (and hence you should rename
> AmiTCP.020 to AmiTCP to run the 020 compiled version) or whether it
> chooses the appropriate version for the processor it's running on, and
> hence runs "AmiTCP.020" if it's running on an 020.
>
> Not a totally unreasonable question...
No, just a funny question :)
ie. the reason it's like that:
1) It's shipped like this in the archive. If it's shipped like that, there's a
very very high chance that we designed it to work that way ;)
ie. if you had to 'manually rename it' (since when do you need to do that
anyhow? ;), I would have told you a long time ago.
Yes, you *could* rename amitcp.020 to 'amitcp', but then if you only had an 00
processor, this would cause a crash, of course. However, if you have an 020+,
and it can't find the '.020' version, it would revert to the 'amitcp' kernel.
2) As above, you should never start to 'fiddle' with things, when they are
shipped in a particular way. For instance on the Voyager mailing list, people
rename the Flash plugin stuff....then write to the list asking why the Flash
plugin 'does not work', ahem :)
BTW, they are located in /kernel, not /bin, as I said.
Chris.
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
