• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Modem access from Classic
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Modem access from Classic


  • Subject: Re: Modem access from Classic
  • From: "Jonathan 'Wolf' Rentzsch" <email@hidden>
  • Date: Wed, 4 Sep 2002 22:14:31 -0500

Jens Bauer, email@hidden, wrote:
>Now... What do you want to do with the modem ?

I'd like to enable an old application that will never be ported to Mac OS
X use my TiBook's internal modem. This app happens to be MacAuthorize, a
credit card authorization and capturing dialup client.

>If you want to dial, I'll recommend using Open Transport.

Just dialing isn't enough -- I need a full-blown modem connection.

>I do not know how to do it using AppleEvents.

That I do know:

tell application "Internet Connect" to connect current configuration

>But let me hear the rest of the story, and also let me know which
>compiler environment you plan to use.

Actually, I have this running now, but I'm not thrilled with the setup
because of Classic->Native loopback networking bugs.

I wrote a stub 68 DRVR which is loaded by a PPC FBA (both written in
CodeWarrior). This combo hijacks .AIn and .AOut and registers a new
CommToolbox resource pointing to .A[In|Out]. This FBA connects via OT TCP
to a Mach-O daemon (written using PBX). The daemon serves as a bridge
between Classic and /dev/cu.modem. ASCII art:

68 DRVR <-> PPC FBA <-> OT <-> Sockets <-> Mach-O Daemon <-> /dev/cu.modem

Issues I've run into:

o Sometimes daemon can't listen to the port. I forget the exact error
(should have written it down) but once daemon can't listen to the port
once, it can never again until restarting X.

o Attempting to connect to Native via loopback address (127.0.0.1) fails.
(Yes Quinn, I saw the technote on this!)

o If I'm out of AirPort range and don't jack my TiBook into the network
(that is, there are no active network devices), Classic can't connect to
Native.

o Classic can't talk to native unless I give Native a static IP address.
Classic OT hangs in OTConnect (T_CONNECT is never received).

o I suppose if the network setup changes while the bridge connection is
open, I'll have to handle that and attempt a mid-transfer reconnect. Ick.

o Surprised most Comm clients on 9 poll SerGetBuf() instead of how I used
to do it, a single async PBRead(). But this isn't Apple's fault... (grin)

This is on 10.1.5 -- maybe 10.2 helps out, haven't tried it yet. I really
wish I could share memory between a Classic app and a Native app, that
would allow me to bypass OT and its bugs.

If I can't get a handle on this, I'll be forced to switch the bridge
communication technology to (shudder) AppleEvents. I'm not liking
stuffing and unstuffing handles thousands of time a second just to move a
emulate a connection.

Apple folks: I have tech incidents to burn, if that helps...

.......................................................
Jonathan 'Wolf' Rentzsch jon at redshed dot net
Red Shed Software http://redshed.net (847) 584-7465
PGP: B2AF 1A09 F881 EBDE C9D6 C4D2 C04F A3C0 3EC5 D5F2

"better" necessarily means "different"
_______________________________________________
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.

  • Prev by Date: Re: Modem access from Classic
  • Next by Date: OT vs. socket calls on 10.2
  • Previous by thread: Re: Modem access from Classic
  • Next by thread: OT vs. socket calls on 10.2
  • Index(es):
    • Date
    • Thread