Re: Modem Port
Re: Modem Port
- Subject: Re: Modem Port
- From: email@hidden
- Date: Thu, 14 Mar 2002 19:12:29 +0000
Good point about the language issue. I don't think there
is a way around that on Mac OS X. There is no "." driver
names that might be immutable across languages. I'm not
even sure the bsd paths would be immutable. The only
way to do that is to encode the strings to search for in
a resource or XML file, or wherever you internationalize
strings in Mac OS X!!
I was in your boat 6 months ago. I gave up trying to
create one app that runs on both Mac OS X and Mac OS
9/8.6. As I understand it, packages are just folders in
Mac OS 8.6. What I have is a mach-o version in a
package. The package has a non-macho placeholder app
that just tells the user "you ran the wrong app! run foo
instead." Foo is the Classic version of the app. I was
able to create a single Metrowerks Codewarrior project
for this.
I suppose when I give up supporting 8.6 then it might
get easier for me to go the one-app route.
>
I completely agree. The product I am developing uses serial endpoints, so,
>
it was my understanding that it was not possible to write a carbonized
>
version. Thus, I am doing OS 9 first, and in about a week I will be
>
starting the OS X version.
>
>
If you simply rely on the name of the port ( instead of the driver name ),
>
wont you run into trouble on different language version of the OS?
>
If so, this *is* an issue in my case, because eventually there *will* be a
>
french version of my program!
>
>
-Morgan
>
>
on 3/14/02 10:19 AM, email@hidden at email@hidden wrote:
>
>
> Hi,
>
>
>
> Maybe for Morgan it was Mac OS 9 only, but what is the
>
> point of writing software for the Mac OS 9 only these
>
> days?
>
>
>
> Adam
>
>> This is specifically a MacOS 9 discussion. This does not apply to X
>
>> or even classic . I though you were looking for specific info on how
>
>> to "uniquely" identify the Internal modem port.
>
>>
>
>>
>
>> Roger
>
>>
>
>> At 4:28 PM +0000 3/14/02, email@hidden wrote:
>
>>> Hi,
>
>>>
>
>>> I thought leapIn and leapOut wouldn't even be the names
>
>>> in Mac OS X? I think counting on leapIn/leapOut is not
>
>>> very robust.
>
>>>
>
>>> In my software, SoftTTY (TTY for the Mac), I want to
>
>>> ignore any Infrared ports when auto-configuring. What I
>
>>> do is filter serial ports with "irda" or "infrared" in
>
>>> the name (not the "." driver name or bsd path). This is
>
>>> good at eliminating most infrared ports and doesn't
>
>>> exclude any non-infrared ports.
>
>>>
>
>>> Adam
>
>>>
>
>>>
>
>>>> .LeapIn and .LeapOut would get you the internal modem on all
>
>>>> machines which Apple says is capable of running MacOS X (this entry
>
>>>> is only present if the modem is available) , it won't work for
>
>>>> earlier machines such as the first powerbook g3, or the beige g3
>
>>>> tower with 2 serial ports.
>
>>>>
>
>>>> In any event you should always open .aIn and .aOut (just drop in
>
>>>> to Macsbug and type drvr to get the correct case...) since
>
>>>> .LeapIn/.LeapOut is patched into the driver open call and will work
>
>>>> properly on a machine where .aIn really points to the modem.
>
>>>>
>
>>>> Roger
>
>>>>
>
>>>>
>
>>>> At 3:16 PM +0000 3/14/02, Quinn wrote:
>
>>>>> At 18:28 -0800 13/3/02, Morgan Redman wrote:
>
>>>>>> I remember a while back, I got help with how to identify which serial
>
>>>>>> port
>
>>>>>> was actually an IrDA port. ( by identifying the serial port with
>
>>>>>> input/output drivers named ".IrIn" / ".IrOut"
>
>>>>>>
>
>>>>>> Now I need to know how to identify which serial port is the
>
>>>> Internal Modem.
>
>>>>>>
>
>>>>>> the input / output driver name for the Internal Modem on my machine is
>
>>>>>> ".LeapIn" / ".LeapOut"
>
>>>>>> is this constant on all macs?
>
>>>>>
>
>>>>> Testing for these driver names is about as reliable as testing for
>
>>>>> ".IrIn"/".IrOut". We've never documented that this technique will
>
>>>>> work, but it's the best solution I know of.
>
>>>>>
>
>>>>> S+E
>
>>>>> --
>
>>>>> Quinn "The Eskimo!" <http://www.apple.com/developer/>
>
>>>>> Apple Developer Technical Support * Networking, Communications, Hardware
>
>>>>> _______________________________________________
>
>>>>> macnetworkprog mailing list | email@hidden
>
>>>>> Help/Unsubscribe/Archives:
>
>>>>> http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
>>>>> Do not post admin requests to the list. They will be ignored.
>
>>>>
>
>>>>
>
>>>> --
>
>>>> _______________________________________________
>
>>>> macnetworkprog mailing list | email@hidden
>
>>>> Help/Unsubscribe/Archives:
>
>>>> http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
>>>> Do not post admin requests to the list. They will be ignored.
>
>>
>
>>
>
>> --
>
> _______________________________________________
>
> macnetworkprog mailing list | email@hidden
>
> Help/Unsubscribe/Archives:
>
> http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
> Do not post admin requests to the list. They will be ignored.
>
_______________________________________________
>
macnetworkprog mailing list | email@hidden
>
Help/Unsubscribe/Archives:
>
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.