Powerbook G3 Series Modem Resource

The Most Important Thing to Remember, From Apple:

• Your existing modem was originally shipped with the latest firmware available, however, 56K modems are still in their infancy and will be undergoing changes over the next several months. The Apple Modem Updater installs the latest Rockwell firmware, based on version 2.2.

Resources:

• MacInTouch-has been covering the issue well. If you read this page much later, check MacInTouch's excellent search engine.
• MacFixIt-has also been covering the issue.
• Apple TIL Article-describes how to reset the modem using any comm program like Clarisworks or Zterm.
• Apple TIL Article-describes how to get the fastest connection from 56Kbps modems.
• Apple TIL Article-Modem Updater 1.2.1 (v.90 update) read me file.
• Apple TIL Article-tells how to check if you've properly installed the update.
• Two Apple Modem Updates-one updates your G3 Series modem to V.90 and one fixes a sleep energy problem.
• VersionTracker's USR-Specific modem script.

What we recommend:

• If you are getting reliable connections at around 44,000 with any configuration of settings or updates, do not mess with your configuration .to try to get any faster a connection. The highest possibly set by the FCC is 53,000 anyway. Generally...if it isn't broke..don't fix it.
• If you are having unreliable connections with your *un-updated* modem try several providers, phone lines in different areas, and all the scripts and settings currently on your computer. Try everything because once you install the update, there's no going back.
• Everything you've tried is hopeless: then go for the V.90 update. Be sure to read the directions very carefully remembering to install and select the proper modem script as well.
• If this gives you bad connections again, try the same things: different areas, different phone lines, differen't settings. If your provider uses U.S.Robotics modems exclusively, you can try the USR-specific modem script.
• If you are still having problems, read every word on this page. If after doing all this you are getting unreliable connections with your G3 Series modem, you can only keep trying until Apple releases another update.

What You Can Do to Help:

• You can submit your negative or positive experience, noting your Powerbook G3 Series model, and what modifications to your modem config you've done. Thanks!

New v.90 Standard?

Apple just amazes me. They pulled the current desktop v.90 modems from the BTO options on their website, along with removing it from the service parts list. The Powerbook BTO pages still list a "K56flex internal modem" as available as an option. MacInTouch says this:

Following the disappearance of the Power Mac G3 internal modem from the Apple Store and from Apple's service parts list, a MacInTouch reader says that Apple is preparing a new modem for December release. The new version apparently introduces "a new V.90 firmware standard", which is supposed to bring better compatibility between customer and service provider modems. (Some other readers have reported disastrous results after installing a recent Apple modem software update, which is not reversable, as far as we know.)

This does not directly affect Powerbook Users. We've gotten our updates. So as far as Powerbook users should be concerned: k56flex is available at the Apple Store. One of the two modem updates discussed endlessly a few weeks ago upgrades these modems to v.90. Perhaps another updater will be released by Apple for the PB modems at the same time as the Powermac gets the "new V.90 firmware standard," to bring the Powerbooks to the latest and greatest.

I've never owned the internal modem for the G3 Series. So you readers that do need to keep me well informed because I can't do testing of my own. The internal modem for the G3 Series has been nothing but trouble for some readers. Check the modem page for all the info I've gathered so far. Stay Tuned for more.

Modem Script

VersionTracker has posted a modem script for the Powerbook G3 Series, which only works well if your provider uses U.S. Robotics V.90 modems. VersionTracker's description:

PBG3 V.90 script - use if the 'Modem Updater 1.2.1' won't give V.90 connections anymoremodem script for PowerBook G3 series, your ISP must have V.90 USR modems for it to work.

Lots more on this tomorrow....

I got my WS I 292/14 at the end of August, and it has been a beautiful
and speedy workhorse, with absolutely no problems. With the original
internal modem, I was getting connection speeds of 40-44,000 - after the
Apple modem upgrade, I routinely connect at 49,333, and downloads are
noticeably faster, with absolutely no problems connecting, or hangups.
I'm reluctant to try a future modem upgrade because this one has been so
flawless!

BTW, I upgraded to Mac OS 8.5 last night, with NO glitches, whatsoever,
but I'm keeping my "old" System Folder for the next few days, just in
case. (Using the "System Merge" function of Conflict Catcher 8 was
fantastic - by far the easiest "clean install" I've ever done, well
worth the cost of the software!) I'll wait to upgrade my desktop
6500/250 for another week, ... just in case ...! So far, 8.5 is MUCH
faster, VERY feature-filled, and absolutely stable, both on the internet
and with applications including Photoshop, Quark, and MS Office.

(1) USR modems at the provider end continued...
I was just thinking about the script VersionTracker uploaded, and looking at
their description again reminded me of one caveat. They say the script is
only for use with USR modems on the provider end. This could be a potential
problem if the provider uses a mixture of modems. Hopefully those that do
use USR modems use *only* USR modems to answer with. Unfortunately, I don't
have an easy way to test the consequences if the user dials in and gets a
different modem.


(2) A reminder to help minimize problems after running the update
As one of the readers who wrote into Macintouch suggests, it is important
for the user to copy the new modem script named "PowerBook G3 Internal 56K"
into the "Modem Scripts" folder (in the Extensions folder), and to *select*
the new script. It makes a difference.

 - Many users don't read the instructions. ;)


(3) Another possible solution for the hardy?
Macintouch added a couple of tweaks the user can do to their script to force
either a V.90 or K56flex connection:

[from a reader] ... the codes to switch the V.90 modems from
                    V.90 to K56 and vice-versa:
                                  +ms=56,0 Forces k56flex
                                  +ms=12,0 Forces v.90
                    You can also add a minimum/maximum connect
                    speed specifier at the end, such as:
                                  +ms=56,0,34000,48000
                    which would specify a force to K56flex,
                    with a minimum connect speed of 34k and
                    a maximum of 48k.

I doubt I'll test them, but some people may have fun with it.


(4) Talkin' about V.90

One problem stems from the fact that there has been more than one flavor of
V.90 so far, and there are possibly going to be more before everybody shares
a single standard. (And I know for one that the V.90 my provider offers is
not the current "Standard".)

Not to be Apple's apologist, but they do inform the user somewhat in the
ReadMe file that accompanies the modem updater (1.2.1)

>From Apple:

> Your existing modem was originally shipped with the latest firmware
> available, however, 56K modems are still in their infancy and will be
> be undergoing changes over the next several months.
> The Apple Modem Updater installs the latest Rockwell firmware, based
> on version 2.2.

And they add the following:

> If you experience a problem with the Apple Modem Updater, shut down your
> computer for 40 seconds to reset the modem. Restarting the computer will
> not reset the modem. Then begin the modem firmware upgrade process again.
>
> If V.90 connection reliability issues still exist after updating the
> modem, reselect the V.34 modem script.
>
> Future Modem Software
>
> New firmware updates, modem scripts, and modem drivers may be released
> for 56K modems until the technology stabilizes.   For more information
> on V.90 modem upgrade information, see Apple's support web site:
> http://www.apple.com/support

I churned out my first report and follow-up comment so quickly, (in the
midst of a hectic 75-hour work week), I see that I left out lots of info.
Despite the number of words.

One thing I wish to add to the scenario I was painting the other day is that
some service providers in some cases use a variety of modem types on their
end of the phone line. Simply stated, some of the equipment might be brand
new, while other lines do their best with older modems the provider isn't
yet ready to devote to charity. If it is done well, the equipment will be
set up so a given phone number will always answer using the same protocol
whenever the user dials in. These modems can use different chipsets or
different protocols, though. So an unfavorable set-up can mean that the user
is actually hitting on different "conditions" each time s/he dials in. It
can be somewhat like Russian Log-in Roulette at times.

Therefore, the user can experience a variety of different connections. And
this can be frustrating. One time a user may get in fine at 56K only to
discover that the next time they are disconnected after a minute. Or, for
example, the user might connect at 33.6K. This definitely adds to the
confusion as the user is unable in such a situation to receive consistent
results, or to find traceable patterns.

The powerbook modem with the recent upgrade was working well most of the
time.  But then my service provider decided to upgrade their k56 modems to
V.90 and now it sucks.  I get dropped connections, dns problems after
connection, , authentication problems, server not responding messages etc.

This is all very frustrating and someone has to do something!!

Thanks to your site i added the following to the mdoem script line in
freeppp and am making the modem connect using K56flex instead of v.90 and it
is working.

AT&FW2l3 +ms=56,0,34000,44000

     I picked up my 'book 2 weeks ago. Love. Coolest piece of
     hardware next to the hammer.* I've tried Apple's Modem Updater
     1.2.1. I get the message "Sorry, this updater software is
     older than the currently installed software." THe installer
     recognizes the modem, but no update. Has anyone else
     experienced this? I see that others have been able to update
     and achieve decent speedsócould there be yet another chapter
     in this modem mayhem?
         Granted, I connect at 43,000 bps, but I know for a fact
     that my phone lines allow my desktop USR Sportster 56k to
     connect at 49,333 bps reliably. What app do I use to alter the
     script to force v.90? And please upload more success stories
     regarding the new 'books (233 mhz) and their modem updates.

My PB G3 250's modem plain out doesn't connect at anything faster than
12,400 kbs!!!!!!  My ISP uses Flex protocol, so does the GV internal.  I
called Apple and they picked it up the next day and sent it to New York
for diagnostics.  It came back in 3 days:  "Nothing Wrong with Modem."
Odd, so I tried my old Motorola Lifestyle 28.8 modem and connect
reliably all day long on the same phone line.  Then I took the Powerbook
into an Apple authorized repair shop, and they told me "nothing wrong
with the modem."  I was furious and demanded they "SHOW" me there was
nothing wrong; i.e. log onto their ISP with their phone line but MY
powerbook.  They logged in at the trusty 12,400 kbs rate.....

What can I do to make Apple fix this?  The authorized repair shop says I
can't do anything because the diagnostic tool doesn't show any errors,
but of course they couldn't make the modem work right.

Continuing Modem Problems

Many readers have reported that they are still having problems after the modem update. One reader says:

• 1) Drops connections on a regular basis,
• 2) Won't connect at reasonable speeds (33k+) on a regular basis, or
• 3) Can't detect a dial-tone, even when the connected line works?

My modem progressed from functioning both pre- and post-upgrade, to doing each of the above and now it simply will not detect a dial-tone. I hate the idea of sending the 'Book back to Apple... Anyone else had this problem and discovered a solution?

If any reader out there can help, please share.

I experienced phenomenon #1 (pre- and post-update) and have found a solution
that worked for three (many?) individual 300/14 G3 Series PowerBooks the
past couple of days.

First, my analysis after working on the 300/14s is that this is not a
hardware problem.

The problem as I see it involves the internet provider and the equipment
(modems) the provider uses to respond to the user dialing in.

A friend phoned me earlier in a worried state because he couldn't maintain a
connection for more than 60-90 seconds using the internal modem in his
spanking new 300/14.

I kept him on the line while I repeated his actions on a 300/14 I have here,
(setting it up for a friend; I've got a 292/14).

Sure enough, I couldn't stay on-line for more than 60-90 seconds. I could
not download my email, and was lucky to connect to a single web page before
losing the connection. (Symptom: Navigator sits in limbo for 20-30 seconds
trying to go to the second page, and then the dialog pops up informing the
user that TCP/IP has been disconnected. The connection seems to be lost
early in the process, though). Note, I was logging into the same provider
("provider 1") using my own account.

I proceeded to walk through several quick experiments that included:

(1) Logged into my second provider ("provider 2") for reference. This
provider only supports speeds up to 33.6K. The connection worked without a
flaw, and I stayed on-line for about ten minutes downloading email and
surfing a few web pages. Even went to the PowerBook Zone and read my friend
the above article. (Mistake - this only worried him more).

(2) Tried logging into provider 1 again using a different phone number. Same
result as earlier, i.e. dropped connection after a minute or so.

(3) Tried tweaking the modem scrip slightly to see what happened. Same
result as earlier.

(4) I went through my mailbox to find a letter from "provider 1" I
remembered glancing at a few weeks back. This confirmed that they had added
a third phone line in September, although it said nothing about using
different modems or protocols.

(5) Logged in using the newest phone number. Got a solid connection at 46K
((aside: I've yet to meet anyone who can achieve a true 56K with any 56K
modem, even with a pristine line.))
Downloaded mail, surfed a dozen or so pages, and even downloaded the V34
(33.6K) script Apple earlier released for the iMac (for the next test, if
required). Case solved, (at least for my friend and me). After maintaining a
solid connection for 20 minutes (while my friend and I discussed other
things for the last 10 minutes or so), I was willing to offer my conclusion
to his problem.

It goes like this:

The provider in this case has been using (cheap) US Robotics modems in the
past that only support 56Kx2 (ex-2) modem chips, i.e. US Robotics modems. No
V90, no 56K Flex (despite the fact most people I know have flex modems, not
x2).
[Note: The x2 modem ordeal was prior knowledge. I got burned 8 months ago
when I bought a TDK 56K Flex modem card, the most popular one in the
country, and could only manage 33.6 connections with the same provider,
specifically because of their preference for cheap x2 modems).

It appears that this provider is using different modems for the new phone
number. (Possibly thanks to the popularity of the iMac, which should share
the same problem. In fact, the next test I would have done would have been
to try using the iMac V34 script.)

*The short answer*

I believe the problem you and others are experiencing is simply related to
the service your provider is offering.


*What to do?*

Contact your provider and see if they can't offer a different phone number
(= different modem connection) that supports V.90 and 56K Flex. Many
providers do have this available for the asking. I've experienced this when
travelling and using local providers as part of my "global roaming" contract
with my provider in Tokyo. Real example? Well, I went to Toronto in
September and suddenly could only log-on using the Toronto phone number I
was originally given at 14.4K. Until I phoned and the local provider gave me
a "good" phone number, that is. Then I was cruising along with connections
between 44K and 48K.

For testing, you could always "borrow" the identity of a friend who you know
has a stable connection. If you're from the "Show Me" state, that is. ;-)

Or, if 33.6K satisfies you, use a V34 script.


*What I haven't covered*

I wasn't explicit, but you may have concluded from my convoluted explanation
that connections up to 33.6 should work, but you can't expect higher
connection speeds if your provider is set-up the way I suspect. Thus, I have
implicitly answered number 2 above, (from your article).

The one problem you raise that I cannot explain with physical evidence is
number 3, the failure to detect a dial-tone. However, I suspect it is more
an internal problem where PPP (TCP/IP? OT?) gets confused after several
failed attempts to connect without quitting or restarting. Just a hunch.


*One more unsolicited conclusion*

Form my limited-yet-hands-on experience, I don't believe there is a hardware
problem behind this. Hopefully you can confirm this quickly and put other
users at ease.

Note from Doug: The reader who submitted this quickly followed up with these next few comments:


I didn't mention this in my first wordy discussion of the "modem problem",
but it might make WSII users feel better to hear that WSI owners who are
signed up with a service provider as I described (56Kx2 only or V.90-56Kx2)
also cannot manage a connection over 33.6K when using the original 56K Flex
modem in WSI (233/250/292).

Before updating, WSI users should get a 33.6K connection, (under good line
conditions), but nothing higher.

WSI users who run the update may continue to get 33.6K connections, or may
even start to experience the same problems as WSII users. This is because
the update changes the modem from a dedicated 56K Flex modem into a 56K Flex
- V.90 modem like the one in the WSII. The modem then tries to negotiate a
V.90 connection, but defaults to 56K Flex if a V.90 connection cannot be
mmade.

Recapping, I believe the disconnect problem occurs when (a) the provider's
modems support only 56Kx2 (or V.90-56Kx2) for connections over 33.6K.

I am experiencing exactly the same problem with my modem.

I just downloaded the ARA 3.0.1 Updater  from the apple tech support
online.

I read in the text for this updater at the support site that this update
is supposed to fix a problem the ARA. Just after the sleep mode, the ARA
cannot get back online.
I wonder if this problem is related.

I will try this updater and report back.


I have  had considerable trouble with connecting to my home base system from a
remote location.

I thought the problem was the Apple Modem update -- turned out to be the ARA
3.0.1 update (downgrade??)

Lost connections left and right both to AOL and to my SOHO modem server
(OneWorldCombo) which did not happen with my old 540c using ARA 2.1 

Anyways, AppleTech here in Canada suggested turning off Virtual Memory and
setting the options in ARA 3.0.1 to ARAP and not using "Automatic" 


Has worked fine since end of Sept. 27 (touch wood)

Perhaps some people are experiencing this problem - please pass it on if this
info helps others - I sure appreciate others giving me a helping hand

Written/Edited/Published by Doug B. Landry
Logo by Jon Iverson
Apple, Mac, Macintosh, Mac OS,The Apple Store, and Powerbook are trademarks of Apple Computer, Inc.
©1998 Doug B. Landry. All rights reserved. All or part may not be reproduced or distributed without written permission.