>I was told apps running under Classic (9.2.x) were able to place calls
>on the hardware just the same as Jaguar.  I assume the API's are smart 
>enough
>in "Classic" and "Jaguar" to know if the other is doing something that 
>would cause problems.

My understanding of the processes is that the Kernel is the ONLY thing 
that actually talks to the hardware. This is fairly normal for secure 
OS's.

So apps running in Jaguar talk to device interfaces, that talk to the 
kernel, that talks to hardware.

Apps running in Classic talk to the Classic environment, which fools the 
app into thinking it is talking to the hardware. Then the Classic 
environment, which is really just an application running in Jaguar talks 
to device interfaces, which talk to the kernal, which talks to the 
hardware.

OS 9 (ie: NOT running in Classic), can talk directly to the hardware if 
it desires.

>Under OS 9.x.x my schedules used to run flawlessly.
>Under Classic/Jaguar the connection is too slow to connect and first 
>account times out.
>The call is still made, its just slower.  Why?  This is what I am waiting 
>on Apple to answer.

This just seems like a bottle neck in getting the response passed back up 
the chain. Remember, now to dial the modem, the modem connects, passes 
that info to the Kernel, which passes it to the modem device interface, 
which passes it to the Classic Environment application, which converts it 
into the appropriate hardware response and passes it to Emailer. Lots and 
LOTS of passing around, which all adds to a delay, and the possibility of 
something going wrong in the chain.

This time out is not unique to Emailer. Other internet applications 
running in Classic experience the same problem, so it is a failure 
somewhere in Classic to Jaguar. I think if enough people report the issue 
to Apple they may work on a fix.

-chris
<http://www.mythtech.net>

___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]>  or  <[EMAIL PROTECTED]>

Reply via email to