« September 2005 | Main | December 2005 »

Thank you for calling Haus Interactive...

...this call may be monitored for quality assurance.

What do you need to have clear digital recordings of your phone calls? One shareware program and one electronic device.

(1) SHAREWARE PROGRAM: Audio Hijack Pro

(2) ELECTRONIC DEVICE: Radio Shack Recorder Control

1a: plug phone line into Recorder Control
1b: plug telephone line of Recorder Control and (mono) mini jack into the proper ports on your computer

2a: Go to System Preferences/Sound/Input and click on the audio input you plugged the mini jack into
2b: Turn up the audio gain

3a: Open Audio Hijack and create a new Audio source (both input and output, see illustration)
3b: Click "Effects" and create a "double gain" effect for sound clarity (see illustration)
3c: Click on "Input" again and click "Hijack", then "Record" to begin recording your phone call
3d: When you're done click "Record" again to stop. You will find your audio files (named by date and time) on your computer: /HD/Users/yourusername/Music/Audio Hijack/


Before setting forth to record calls, it is always a good idea to brief yourself on the legality of it. You can start with this quick guide to phone recording law.

Posted by Aaron R. Deutsch on October 13, 2005 | Comments (0)

OS 10.4 (might have) killed my modem

September 20, 2005
10.4 Tiger modem, an oddessey.
Finally saw this through and thought I'd post my (only loosely edited) experience in full in the off chance that it may help someone who is not as far along this same path.

My girlfriend and I have a PowerMac G4/AGP with internal CD-RW that was running 10.3.9 but wanted to upgrade to Tiger (on DVD) for Spotlight, fax log, other improvements.

We pulled the HD into another PowerMac G4 and installed using it's DVD drive, then moved HD back to AGP. Spotlight indexed everything and we were running fine *until we tried to fax*. Discovered the modem was completely dead. No more faxing and no dial-up connection for when her wifi blinks out either.

The internal modem worked fine on my Dual 1Ghz Quicksilver running the same version of OS - but it's 10 miles away in Brooklyn. Not going to help our Manhattan problem computer.

June 1, 2005 was the timestamp on the last successful fax from the AGP.

- PowerMac G4/AGP
- 640MB RAM
- 250GB internal ATA HD with PCI ATA controller card
- OS 10.4.2 with all the security updates and such
- OWC Mercury Extreme 1Ghz CPU upgrade

Modem Information:
Modem Model: Spring
Interface Type: Serial
Modulation: V.90
Hardware Version: 3.0F
Driver: com.apple.driver.AppleSCCSerial (v1.3.0)

- Application Enhancer and WindowShade
- Microsoft Optical Desktop 5.1 for wireless Mouse and Keyboard

- Buffalo PCI wireless card being used with the Apple Airport software (but equipment not turned on when trying modem)

- no DVD drive (only CD-RW) so no booting to 10.4 installer
- no extra HD to backup data onto and archive to revert to old system, etc.
- Microsoft keboard and mouse so no zapping PRAM, etc.

- checked cable connections
- made sure phone line worked
- made sure phone line did not have voicemail
- tried another phone cord
- made sure network settings were correct (didn't change from 10.3.9)
The Network section of System Preferences is set to:
Modem: Apple Internal 56k Modem (v.90) (per the factory settings)
* enable error correction...
* wait for dial tone before dialing
* tone
* sound on

Console reported:
Jul 22 22:45:40 BlueMonday pppd[3914]: Connect script failed
Jul 22 22:47:01 BlueMonday pppd[3919]: Connect script failed
Jul 22 22:47:55 BlueMonday pppd[3928]: Failed to open /dev/cu.modem:
Resource busy
Jul 22 22:47:56 BlueMonday pppd[3929]: Failed to open /dev/cu.modem:
Resource busy
Jul 22 22:49:16 BlueMonday pppd[3930]: Connect script failed

- created new user account and tried again:
Jul 23 10:13:07 BlueMonday pppd[4699]: Connect script failed
- updated to 10.4.1. Did not fix problem.
- 10.4.2 rumored to have a fix. waited. Installed. Did not fix problem.

August 23. 2005:
Scored a D-Link USB modem on eBay and tried that.
System preferences recognized it right away as "Atlas Modem Board". I input the correct login/phone number and gave it a whirl. Connecting...Disconnecting..."A modem error occurred. Please verify your settings and try again."

Console reported this:
Aug 26 23:01:52 BlueMonday pppd[1576]: Connect script failed
Aug 26 23:05:08 BlueMonday pppd[1583]: Connect script failed

...tried this modem on my laptop and tower the other day and it did not work so I'm wondering if I might have gotten a dud...

...Tried this from MacFixit:
"My modem works fine on Tiger. (I asked what mac model/modem he was using-Mike)
I do know that there was an issue on Panther that caused my Mac to freeze when trying to connect via the modem. I solved this problem by deleting /var/log/ppp.log. To access this from the Finder, select the Go menu > Go to folder and enter in /var/log/ then press return. Find ppp.log, move it to the trash (you'll be asked for your administrator password) and empty the trash. After that, try connecting again.

Also found a hint on macfixit.com:
- Go into TCP/IP under SysPrefs/Network/Modem and click "configure IVp6" and click "off". Still no dice.

Also on macfixit was this thread:

they (as well as accelerateyourmac.com; http://www.xlr8yourmac.com/OSX/tiger_modem_reports.html) suggested:

The 10.4.x InternalUSBModem.kext extension is messed up. It sometimes leaves the modem in a state where the system can't communicate with it. That's OK because the 10.3.9 one works, this is why going back to 10.3.9 let's you use the modem. If you did an archive & install you should just need to do something like this in the terminal:

cd /Previous\ Systems.localized/Previous\ System\ 1/System/Library/Extensions/

cd IOSerialFamily.kext/Contents/PlugIns/

sudo kextload InternalUSBModem.kext


"My situation has a twist similar to Matt Powell in that I already recycled the disk space of my System Archive, thus I have no local copy of a previous IOSerialFamily.kext.

So I Finder>Go>Connect to Server... to my daughter's Mac on the family ethernet then drag and drop /System/Library/Extensions/IOSerialFamily.kext from her 10.3.5 system into /Previous Systems/ on my Mac. This gets me IOSerialFamily.kext version 6.0; 10.4.1 has version 8.0

Now I follow Jethro77's advice.

cd /Previous\ Systems.localized/IOSerialFamily.kext/Contents/PlugIns

sudo kextload InternalUSBModem.kext

Where I have a departure from the standard experience:

Notification: "System Extension cannot be used"
Terminal Output:
kextload: extension /Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext is not authentic (check ownership and permissions)

I retry with -t option to get diagnostic info from kextload:

Terminal Output:
kernel extension InternalUSBModem.kext has problems:
Authentication failures
"File owner/permissions are incorrect" = (
"/Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext"
"/Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext/Contents/Info.plist"
"/Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext/Contents"
"/Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext/Contents/MacOS/InternalUSBModem"
"/Previous Systems.localized/IOSerialFamily.kext/Contents/PlugIns/InternalUSBModem.kext/Contents/MacOS"

Try changing permissions:

sudo chown -R root InternalUSBModem.kext
sudo chgrp -R wheel InternalUSBModem.kext

Then reloading the kext:

sudo kextload -t InternalUSBModem.kext

Terminal Output:
kextload: extension InternalUSBModem.kext appears to be valid
kextload: InternalUSBModem.kext loaded successfully"


"THANK YOU!!! I'd actually had the idea of using the old modem driver, but tried dragging and dropping the entire IOSerialFamily.kext bundle from the GUI, which does not work. The terminal method worked instantly...now I can use Tiger...yeah!

but then there is a problem with faxing:

UPDATE: If I use the old kernel extension from 10.3.9, my dial-up connection works. I have to do a restart, then issue the "sudo kextload InternalUSBModem.kext" in the Terminal. The dial-up connection will work until I restart, or until I try to use the modem to fax.

If I attempt to fax after substituting the old 10.3.9 kernel extension, then I get a message in the Console telling me that "kextd crashed", and the fax software fails. If I try to fax using the 10.4.1 kernel extention, I get a message telling me the device is busy, cannot open the communications port, etc., same as others have reported."

September 10, 2005:
- Order replacement internal modem (again on eBay)
- Modem stopped showing up in System Profiler after loading in the 10.3.9 IOSerialFamily.kext files per a macfixit forum posting. Prepare to revert to 350Mhz CPU if this doesn't work...

September 11, 2005:
- Ordered a fresh 250GB HD from newegg. The plan: do a fresh install of 10.3 and test modem functionality.

PROBLEMS HAVE ALSO BEEN REPORTED WITH (From accelerateyourmac.com and early Apple bulletin boards http://discussions.info.apple.com/webx?128@897.nhkcad0TShM.0@.68af5e7c):
- iBook 700Mhz
- PowerMac MDD 1Ghz
- PowerMac G4/AGP
- eMac
- iMac Mini
- PowerBook G4
- PowerBook 12"

10.4.2 ONLY FIXED THE ISSUE FOR A FEW USERS (From apple discussion: http://discussions.info.apple.com/webx?128@897.nhkcad0TShM.0@.68af5e7c)
- PowerBook Ti
- Dual 1Ghz PowerMac G4
- PowerMac MDD

APPLE BEING OBNOXIOUS AND LOCKING THREADS "Reason: Please start a new topic about your technical issue":

- http://discussions.info.apple.com/webx?128@897.nhkcad0TShM.0@.68af5e7c

(original post deleted: http://discussions.info.apple.com/webx?128@897.nhkcad0TShM.1@.68adbc89)

September 18:
- Received new HD. Installed 10.3.2 on new HD and upgraded to 10.3.9 -- still no modem functionality.

September 20:
- installed new modem with 10.3.2 HD. Dial up functional!!!
- swapped HDs for the one with 10.4.2 + security updates. Modem still working.


(but the analog output sound a little more "harsh" than before... instantly concerned about longevity of new modem)

New modem appears in 10.3 and 10.4 as:

Modem Information:

Modem Model: Spring
Interface Type: Serial
Modulation: V.90
Hardware Version: 3.0F
Firmware Version: APPLE VERSION 0001, 4/7/1999
Driver: com.apple.driver.AppleSCCSerial (v1.3.0)
Country: 22 (United States, Canada, Guam, Hong Kong, India, Latin America, Philippines, Thailand)

So I don't know what this means - seems like a pretty wild coincidence that the modem just so happened to die at the precise time as the Tiger upgrade (and with so many other people experiencing trouble).

Does the OS control voltage in any way? Could 10.4.2 have actually fried the modem?

This was an especially weird repair for me as I'm no electrician and I really felt like I was blindly throwing money at this, but much more relieved to have 100% functioinality back vs. anger over wasted time.

For those who might have a PowerMac G4 tower (vs the laptops) you can find replacement modems on eBay for $10-$15 which is a lot cheaper than your local Apple repair store and certainly worth a try. It seems like the problem on the 'boards is being narrowed down to a particular model of modem so you may actually have a *working* modem that just doesn't work with OS 10.4 in which case buying a new modem would still be a resonable fix for you.


Posted by Aaron R. Deutsch on October 9, 2005 | Comments (0)