Input manager & trackpad
Hi all!
I've got an idea for a new project, but I'm not sure how well the mac architecture would support it.
Where can I find a good introduction to making/using input managers as well as some info on their intended use and limitations. Can I make an input manager to change the way the trackpad can be used?
Should I be using input managers to give custom trackpad behavior, or is there some other way of doing it that I'm not aware of?
Thanks for sending me off in the right direction,
~Jordan
I have the impression that the trackpad can be customized via a driver. One is
http://www.ragingmenace.com/software/sidetrack/
The references I have seen for input manager seem to relate to text input.
There is a developer forum here:
http://discussions.apple.com/forum.jspa?forumID=727
Similar Messages
-
I can't open safari. I tried Mac HD to library...it does not show a input manager, only methods and there are no files associated with it. This just started this
morning. Firefox works.Hi,
There are two libraries. One is System one is your User account.
InputManagers folder is in the system library.
Open a Finder window. Select MacintoshHD in the Sidebar on the left. Now open the Library folder. The Input Managers folder is in there.
I think you are looking in your "users folder" which you can access in the same Finder window by selecting your user account (it has a small house icon).
I saw your post here. https://discussions.apple.com/message/15025894#15025894
If you think you have the Community Toolbar installed you need to check these folders.
/Library/Application Support/ Move the Conduit file to the Trash.
/Library/Application Support/ Move all of these files to the Trash: SIMBL/Plugins/CT2285220.bundle
/Library/InputManagers/ Move CTLoader to the Trash.
/Library/Receipts/ Move ctloader.pkg to the Trash.
/Library/ScriptingAdditions/ Move any Conduit / CTLoader related files in that folder to the Trash.
/Users/<User name>/Library/Application Support/ Move Conduit to the Trash.
Carolyn :-) -
Input Manager & Script Additions
Carolyn suggested I check add-ons. However I cannot locate an Input Manager folder anywhere. I can find one script additions folder at macHD/system/library. I'm experiencing the same problems as everyone else following a recent update. Emptying the Input Manager folder has worked for some. Where do I locate this and the Script Additions folders?
HI Mark,
Open a Finder window. Select MacintoshHD in the Sidebar on the left. Then on the right open the Library folder then the Input Managers folder / Application Support folder and the ScriptingAdditions folder.
I'm experiencing the same problems as everyone else following a recent update
If Safari is crashing, If Safari has just crashed, press the Report button on the CrashReporter dialog box to view the crash information.
Now copy/paste the entire contents of the Crash Reporter window into your reply here. If the crash report dialog does not appear or the crash is hard to reproduce, crash logs can be retrieved from the ~/Library/Logs/CrashReporter> folder.
Understanding paths.
The ~ (Tilde) character represents your Home Folder. So if someone suggest you follow a path in your Home Folder / Library to find a particular file or folder, the path is:
~/Library
If it's the system folder the path is:
/Library (no Tilde)
Carolyn -
Rouge input devices (trackpad & Magic mouse)
I've been banging my head for days. I can't seem to find out why my wireless magic mouse & the new trackpad, seem to select any thing that would take a click to open, when I just pass over. I rarely have to click on anything, as they select it anyway, without me clicking. I have to be VERY careful as I often find my self on pages I DID NOT want. Even worse... I've unknowingly DELETEED items, as I may have passed over a delete command and the mouse or trackpack selects. It it like at rouge MOUSEOVER, or HOVER CLICK. Can't fix it. anyone know about this or can fix. It's got to be a setting, but I can't find it.
thanks...DonThanks for the info, howerver may consider, but it seems to be a setting of some type as both the magic mouse & trackpad continue to accept as you pass over a link of some sort. lost a couple emails, today as the tackpad cursor passed over couple line as I clicked delete for something else. I've been into Mac for only about a year, so don't dare touch "Terminal" or anything of that sork, as I don't know what I' doing. (I'd had similar problems like this with PC,s over the years, but wasable to fix glitches, corruptions, etc. Mac....well Idon't know. Service call might be expensive.
Still looking for an answer about my "runaway rouge, mouse & trackpad
Thanks.....Don -
Retina MacBook Pro Trackpad in Windows 8
Hello, and apologies if this has been answered anywhere, I've been digging for hours and to no avail.
I just recently picked up the new Retina MacBook Pro, and I'm having issues with the trackpad in boot camped Windows 8. For reference, the trackpad worked fine in Windows 7, and I used the same Windows Support drivers that Boot Camp downloaded for both Windows 7 and Windows 8.
The issue manifests itself as such:
Windows receives no input from Trackpad at all
2 "Touchpads" appear in Device Manager in Windows 8
Both touchpads have yellow yield sign indicating on further inspection "driver installed improperly"
So far I've tried the following:
Uninstall and re-scan for devices
Reinstall by running repair with boot camp utility
Older versions of the driver in boot camp
Running the individual boot camp driver directly (results in "you need to run 64 bit version of DPInst.exe"
Extracting boot camp driver archive, replacing DPInst.exe with a 64 bit version, running DPInst.exe as well as re-archiving and running the driver
Checking online for additional drivers, including Microsoft's auto-check functionality
Each of these methods have resulted in the same thing, 2 touchpads appearing with "incorrectly installed drivers." I'm at a total loss, if anyone has had any success conquering this issue, or if you've simply been able to use your Trackpad on your RMBP, please share your steps!
Cheers.To make the trackpad work. You need to install trackpad++
(http://www.techspot.com/downloads/4967-trackpad-control-module.html), it will enable the trackpad driver on boot camp. After you install the trackpad++, trackpad++ will complain something. ingnore it. You should be able to enable trackpad. And you can now even uninstall the trackpad++, the trackpad will sill work.
brightness, what graphics card are you using? It might be due to the auto adjusting brightness running there. You can go to your power options, edit the one you are using (Change plan settings >> Change advanced power settings) and look for Batteries >> Enable adaptive brightness and disable the one you are using. After that, the scrollbar for adjusting brightness in power options should work again.
bluetooth connection is incredibly unreliable/intermittent when in Windows (I run Windows 7 64-bit and Boot Camp 4.0, and got both devices connected without any trouble via Bluetooth).
https://discussions.apple.com/thread/4079148
After much testing, I have found the cause of lagging/jumpiness on the Bluetooth Magic Mouse and Magic TrackPad in Boot Camp. Hopefully this will help others:
The drivers for the Broadcom 802.11n Wireless Adapter have a setting called "Bluetooth Collaboration" that is Disabled by default. Enabling this option removes the problem instantly. My Magic Trackpad now works flawlessly, even if I stand 6 metres from the machine. It now works just as well as under Mac OS. The setting can be found under:
Control Panel > Device Manager > Network Adapters > Broadcom 802.11n Network Adapter (right click and choose "Properties".
Under the "Advanced" tab, highlight the setting named "Bluetooth Collaboration", then change it to Enable. Then click OK.
I narrowed the problem down to the wireless card by disabling ALL startup services and processes for Windows, then re-enabling one by one.
As soon as I enabled the Windows Wireless Service, the problem came back.
Similarly, disabling the Wireless Card inside the Network and Sharing Center (or Device Manager) removes the problem.
This led me to believe it must be a driver issue with the wireless card, since the problem didn't occur with the Magic TrackPad under Mac OS, or on my mother's Windows 7 64-bit computer.
So when I went into the Driver Properties to check for an update, I found this setting about Bluetooth Collaboration.
All Apple notebooks use the Broadcom card (and have done for years), so this driver is installed for almost anybody using Boot Camp on an Apple notebook. I'd assume this problem would affect anybody using Boot Camp + wifi + a Bluetooth device.
Wireless Connection problem using windows in a Mac. -
No Inputs in xserver(unable to access /etc/rc.conf to change startup)
Hello everyone,
I've installed arch on an older notebook and of all the steps I could miss, I forgot to add hal to the daemons array in /etc/rc.conf so now when arch boots up it goes directly into xserver(kde) without any input hotplugging resulting in no input from trackpad/keyboard, as well as external mouse and keyboard.
I've tried editing /etc/rc.conf when using the arch boot cd but I get "permission denied" when trying to mount /dev/sda1,2,3,4 etc. Is there any way I can interrupt the boot process so that I can remove "kdm" from the daemons array? Or to somehow stop arch from booting into xserver? I'm somewhat new to the linux environment but I try my best to follow all and any tutorials/advice and you guys seem to have the most detailed tutorials of all the distros - way to go!
Thanks for the help
Last edited by geometro (2010-06-08 01:30:06)You need to set a different runlevel in the Grub entry. Once you have selected the entry in the boot menu, you can edit it by pressing key e. Add "3" (without to quotes) to the end of the kernel line and then Esc to exit. Then you can try to boot by pressing b.
Runlevel 3 didnt work(still booted into xserver), but I looked up into runlevels(didnt know about them before) so I tried runlevel 1 and it worked! :P Thanks for the help!!
"Runlevel 1 is usually for very basic commands. This is the equivalent to "safe mode" used by Windows. This level is usually only used to asses repairs or maintenance to the system. This is a single-user mode and does not allow other users to login to the machine."
edit: typo
Last edited by geometro (2010-06-08 05:07:58) -
Mail - Subject line automatically deletes with text input
Another 'annoying' intermittent issue with 10.5.1 upgrade.
When I begin a new mail message, the subject line automatically deletes and highlights what would be the affected number of characters when I begin typing the subject. Once I input 4 characters, the line is deleted. It occurs 75% of the time.
Anyone else having the same issues, or have a possible fix?would you happen to have a plug in or input manager such as rapidowrite or text expander or some other sort of app installed with Mail and AB by any chance? (if you have rapidowrite, i believe there is a new version that is more compatible with leopard, recently released.)
if so, then i would suggest you quit mail, then uninstall/get rid of these, drag them to the desktop, launch mail again and see if that clears the issue.
you can find these plug-ins in homefolder/library/mail/bundles and in homefolder/library/address book plug-ins
hope this helps -
Safari 3.1 Install - Breaks Mail, Update Manager, Help, Safari
I downloaded and installed Safari 3.1. Afterwords, all apps that use webkit appear to be broken. They attempt to start and crash.
I have backed out all input manager files per the instructions that have been posted elsewhere.
I have re-applied the 10.4.11 combo update.
I removed the Audio Hijack APE file per Mac Fix It
Etc... Multiple times...
Still no mail, no Safari, no help, no update manager. The Webkit version of Safari works...Fixed!! I tried verify permissions and verify hard drive in disk utility. I do have a key error that causes the drive verify to stop.
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Keys out of order
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
Disk Utility stopped verifying “Macintosh HD” because the following error was encountered:
The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
But, never mind that. for now..
From the forums I found this...
"This issue is resolved, thanks karelsf. To run Software Update through terminal, open Applications > Utilities > Terminal, then type:
sudo softwareupdate -i -a
Enter your password at the prompt. You'll probably be asked to restart when it's done, which you'll have to do manually. This probably worked because the new Safari update also installed a new WebKit framework, which was the problem in the first place.
Thanks!
Mateja"
Thank the above wonderful folks for sharing!!
Might not work for everybody, but worked for me, just need to figure out the hard drive error... -
I need to create a new user in 9i (Windows 2000). I tried connecting as system/manager but I keep getting invalid name/password. I can connect as scott/tiger, scott/tiger does not have the necessary priviledges.
Help please.
Thanks
JordiThe 9i database creation wizard, called by the 9i installer, now prompts for sys and system passwords. It doesn't allow you to input manager for system or change_on_install for sys. These will be your passwords only if you use the CREATE DATABASE command, or you change the passwords after creating the database with the wizard.
If you did the install, you should have written down the passwords. If you didn't do it, ask the person who did. If no one knows the password, your best bet is to recreate the database.
Best! -
Hi friends,
Please tell me about how to create a batch input from beginning to end.
How can I achieve the entry of the data?
sm35 or shdb is used to record the transaction steps?
One says sm35, the other says shdb?
Step by step?
Thanks in advance.Hi,
BDC option
ABAP Runtime Environment (BC-ABA)
Batch Data Communication option.
BDC options define the processing mode for a batch input session.
Examples of modes used for processing sessions are:
Display all records.
Display for error dialogs only.
Process session in the background.
Process session on the screen.
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
Transfer data from an external system into an R/3 System as it is installed.
Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
The Data Transfer Workbench
Purpose
The Data Transfer Workbench supports the automatic transfer of data into the R/3 System.
The Workbench is particularly useful for large amounts of data. It guarantees that data is transferred efficiently and ensures that data in the R/3 System is consistent.
Features
The Data Transfer Workbench provides the following functions:
Integration of standard data transfer programs
Registration and integration of your own data transfer programs
Various techniques to load data into R/3.
The data is read from a transfer file in SAP format and loaded into the R/3 System using one of the techniques below:
Administration and organization of data transfer projects
Tools for analyzing the required SAP structures
BAPI interface
Batch input
Direct input
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
Data transfer from other, external systems
Generation of data transfer programs
Generation of function modules that can be used as an interface to the R/3 System
Initial Data Transfer
Prerequisites
Before you start the initial data transfer, you should have answered the following questions:
Which business objects are to be transferred?
The objects to be transferred depend on the business applications you are using. If you are using sales and distribution processing, for example, you should transfer the material master records as well as the sales master records .
How should the business objects be transferred?
Various techniques are available to load the data into the R/3.
Process Flow
The process of transferring data can be divided into the steps:
1. Preparing the data transfer
Analyzing and Cleaning Legacy Data
Analyzing SAP Structures
Developing Programs, Function Modules and BAPIs
Creating a Program or FM for Data Extraction
Creating a Mapping Program
Registering Programs, Function Modules and BAPIs
1. Executing the data transfer
Organizing the Transfer in Projects
Executing Data Transfer Runs, monitoring (CCMS) and processing (log)
Checking transferred objects in R/3 using a function module or report (task type AUD).
The graphic below describes the steps involved in transferring the data:
ThThe The Data Transfer Workbench is an integrated project management for all the required steps involved in transferring data to your R/3 System.
You need to use programs or function modules for the various steps. SAP provides a range of BAPIs for loading data into R/3.
You could also carry out all the steps, except for loading the data via BAPIs, without using the Data Transfer Workbench.
In the first step you extract the existing data from a source system into a file and clean it there, if necessary.
To load data into R/3 you need a transfer file in an appropriate SAP format.
Using a mapping program you have to map the extracted data to the structures of the transfer file.
To load the data into the R/3 System one of the Techniques is used depending on the type of business object . I f more than one of these techniques is provided for a particular object type, you should read the documentation to find out what the different uses are .
Once you have created a project, you can start a run. The tasks of the run definition are processed in order.
After the data has been successfully loaded into the R/3 System, it can be checked here.
Result
You have transferred the data into the relevant R/3 application and checked it here.
Data Transfer
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
Transfer data from an external system into an R/3 System as it is installed.
Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
Data transfer from other, external systems
Generation of data transfer programs
Generation of function modules that can be used as an interface to the R/3 System
Data Transfer Methods
You can use the following methods to transfer data:
Direct input: With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with the help of the screens. This means that direct input has considerable performance advantages.
CALL TRANSACTION: Data consistency check with the help of screen logic.
Batch input with batch input sessions : Data consistency check with the help of screen logic.
Difference between Batch Input and CALL TRANSACTION
If the direct input cannot be used for your task, this makes creating a data transfer program easier since the underlying transactions ensure that the data consistency checks are executed.
In the case of an error during the data transfer (if data records are inconsistent, for example), you can restart the transfer at the point in the program where the error occurred.
Batch input methods
With the batch input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a "batch input session". The session records the actions that are required to transfer data into the system using normal SAP transactions.
When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System  Services  Batch input), or have the session run in the background processing system.
CALL TRANSACTION methods
In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data does not have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program.
The information in Choosing Data Transfer Methods will help you decide which is the best data transfer method.
Data Transfer: Overview of Batch Input
Prerequisites
Before beginning the initial data transfer, you should answer the following questions:
Which business objects are to be transferred?
The business objects to be transferred depend on the business applications that you will be using. If you are using sales and distribution processing, for example, you must transfer the material masters as well as the sales documents from your legacy system.
How are the business objects to be transferred?
The data can be transferred either manually or automatically, using an SAP data transfer program or using your own transfer program.
Process flow
During the initial data transfer, data from the external system is converted into a sequential data transfer file and then transferred into the R/3 System using an SAP data transfer program. The data transfer file is the prerequisite for successfully transferring data as it contains the data in a converted format that is suitable for the R/3 System.
1. Check to see if an SAP data transfer program (direct input, batch input or CALL TRANSACTION) exists for this data using the Data Transfer Workbench. Refer to the notes for this transfer program.
If no SAP data transfer program exists, proceed as follows:
2. Determine the SAP transactions that a user would use to enter data records.
3. Record these transactions using the batch input recorder. Ensure that you have filled all of the relevant fields with data.
4. Use this data to generate a data transfer program.
5. Display the Data Transfer Workbench and create your own data transfer object.
6. Now follow the steps for transferring data using the Data Transfer Workbench.
The Transaction Recorder
Use
You can use the transaction recorder to record a series of transactions and their screens.
Features
You can use the recording to create
Data transfer programs that use batch input or CALL TRANSACTION
Batch input sessions
Test data
Function modules.
The recording can be executed several times. The screens are run in exactly the same way as they were run during the recording.
You can edit recordings that you have already made using an editor.
Activities
1. To display the batch input initial screen, choose System  Services  Batch input Edit.
2. Choose Recording. The system now displays the initial screen of the batch input recorder.
3. Make a recording of the relevant transactions.
4. Generate one or several of the objects named above.
Special features
F1 -, F4 - and self-programmed F1 - and F4 help ( PROCESS ON HELP-REQUEST , PROCESS ON VALUE-REQUEST ) are not recorded. The same applies to all commands in the System and Help menus.
Error and warning dialogs are not recorded. This means that only the OK code field and the field contents that lead to successful further processing in the current screen.
" COMMIT WORK " in a transaction flow indicates the successful end of the transaction as regards batch input. The recording also ends successfully.
" LEAVE TO TRANSACTION " in the course of a transaction indicates that it is not suitable for batch input. The recording is terminated.
In ScreenPainter screens, movements in the scrollbar are not recorded. Use the function keys F21-F24 for positioning.
Recording Transactions
The recording forms the basis of generating data transfer programs, sessions, test data and function modules.
Procedure
1. Display the initial screen of the batch input recorder.
2. Assign a name to your recording.
3. Choose Create.
4. On the subsequent dialog box, enter the transaction code that you want to record and choose Continue.
The system displays this transaction.
5. Execute the transaction in the usual way.
6. When you have finished processing the transaction, the system displays an overview of the transaction and your input.
Choose Get transaction if no errors occurred while the transaction was being recorded.
If you do not want to keep the last recording that you made, go to the next step.
7. Choose Next transac. If you want to record an additional transaction. Then continue from point 4.
8. Save your recording when you have finished.
Recording
Once you have recorded the transaction, you can process it again later.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and choose Execute.
4. Choose one of the following processing modes:
A : Display all screens.
E : Display errors only. In the case of an error, the system displays the screen on which the error occurred. Once this error has been corrected, the system continues to process the recording until the next error occurs.
N : No display. The recording is not processed visibly.
5. Choose the update mode:
A : Asynchronous update
S : Synchronous update
L : Local update
6. You begin to process the recording when you choose Enter to exit the dialog box. When the recording is complete, the system displays a log that lists the name of the transaction, the system field SY-SUBRC and the system messages that were output.
Using the Recording Editor
The recording editor contains functions that you can use to edit your recordings.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and choose Change.
4. The following functions are available on the overview that the system displays:
Delete transaction from the recording: This deletes the selected transaction.
Add a new transaction to the recording: The transaction is added at the end of the recording.
Editing: You can edit the current recording.
If you choose Editing, proceed as follows:
5. The system displays an editor where you can add and delete individual lines. You can also change the contents of these lines.
6. If these editor functions are insufficient for your requirements, you can choose Export to download the recording onto your presentation host and use a PC editor to edit it there.
7. Choose Import to import this file back into the R/3 System. Ensure that the file is still in the correct format.
8. Choose Check to ensure that the edited version of the recording is still syntactically correct.
9. Save your changes to the recording when you have finished editing it.
Generating Batch Input Sessions From the Recording
The data from the recording is transferred into batch input sessions that you can process for test purposes using the usual mechanisms.
Prerequisites
Before you can generate a batch input session, you must record the transactions through which the data is to enter the R/3 System. You use the batch input recorder to do this.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and then choose Generate session.
4. Enter a session name, a user with whose authorizations the session is to be processed, the identification whether the session is to be deleted once it has been processed and the processing date.
5. Choose Continue to exit the dialog box.
You have generated a batch input session that uses the same data for the input fields that you entered when you created the recording. You can now process this as usual.
Generating Data Transfer Programs
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and choose Create program.
4. On the following screen, specify a program name.
5. You can also choose how the maintained field contents of the recorded screens are to be filled:
Transfer the values that were used during the recording. If you require a flexible data transfer, you must modify this program.
Set the parameters of the input values to be maintained and import these values from a data file. To set the parameters, the system creates a data structure and imports the data records from an external file into this data structure. The program assumes that the external file has been adapted to this data structure.
6. If you have decided to set parameters for the input values to be maintained, it is useful if you create a test file when you generate the program. To do this, flag the checkbox and enter a name for the test file. For more information, see creating a test file.
7. Choose Continue.
8. The system displays the attribute screen of the program editor. Choose the relevant attributes here and save the program.
Result
You have now generated a data transfer program that you can use to import data into the R/3 System. The program can execute the data transfer using batch input or CALL TRANSACTION .
Generating Function Modules
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and choose Create function module.
4. On the subsequent dialog box, enter a function module name, a function group and a short text for the function module. Exit the dialog box by choosing Continue.
The system automatically creates the function module.
Result
You have now generated a function module that you can use as an interface for your R/3 System. As well as information relevant for the data transfer, the function module's import interface has a parameter for each input field of the transaction recorded.
Using Function Modules
Prerequisites
The function module was generated from a recording made using the batch input recorder.
Procedure
1. Cal the function module.
2. Supply the generic interface of the function module:
CTU : Flag whether the data is to be transferred using batch input method CALL TRANSACTION USING . The system generates a batch input session if this flag is not set.
MODE : Processing mode:
A Display all
E Display only errors
N No display
UPDATE : Update mode:
S Synchronous
A Asynchronous
L Local update
GROUP : (If CTU is already specified): Name of the batch input session to be generated
USER : (If CTU is already specified): User with whose authorizations the session is to be processed
KEEP : Specifies whether this session is to be deleted once it has been processed
HOLDDATE : Specifies the earliest processing date for the error session
NODATA : Defines the NODATA character
3. Supply the function module's special interface.
For each input field that was filled when you recorded the transactions, the system creates an import parameter. The recorded value is used as the default value for this import parameter.
Creating Test Files
To test the data transfer program that you have created, you can create a data record in a sequential file. This data record contains all the field contents from the recording that are relevant to the data transfer in the format required by the data transfer program. It is therefore useful if you align the format of your conversion program data file with the format of the test file.
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1. Display the initial screen of the batch input recorder (Transaction SHDB).
2. Choose Overview.
The system displays an overview of all recordings.
3. Position the cursor on the relevant recording and choose Create test data.
4. Enter a test file and exit the dialog box by choosing Continue.
You have now created a test file.
If the test file you have specified already exists, the system appends the new data record.
If you do not specify the path, the system archives the test file in the working directory of the current application server.
Executing the Data Transfer
Purpose
You generally use the Data Transfer Workbench to execute the data transfer. The following section describes how you transfer data directly using the batch input method.
Prerequisites
You require a data transfer program. This may be an SAP data transfer program, or you can create your own program.
Process flow
1. Provide the data to be imported in a data file. Ensure that the data is in the correct format.
2. If you are using a generated data transfer program, you can choose a data transfer method.
If you are only dealing with one data record, you can import this directly using a generated function module.
3. Execute the data transfer program.
4. Analyze the program and correct any errors that occur.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Selecting a Data Transfer Method
When you transfer data in ABAP, you have three options to submit the data for the data transfer. Only the first two methods can be recommended without reservation. The third method, by way of CALL DIALOG, is outmoded. CALL DIALOG is less comfortable than the other methods. You should use it only if you must.
Use the CALL TRANSACTION USING statement
Summary: With CALL TRANSACTION USING, the system processes the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.
Your program prepares the data and then calls the corresponding transaction that is then processed immediately.
The most important features of CALL TRANSACTION USING are:
o Synchronous processing
o Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
o You can update the database both synchronously and asynchronously
The program specifies the update type
o Separate LUW (logical units of work) for the transaction
The system executes a database commit immediately before and after the CALL TRANSACTION USING statement
o No batch input processing log
Create a session on the batch input queue.
Summary: Offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging.
Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.
Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function module calls from the ABAP program.
The most important aspects of the session interface are:
o Asynchronous processing
o Transfers data for multiple transactions
o Synchronous database update
During processing, no transaction is started until the previous transaction has been written to the database.
o A batch input processing log is generated for each session
o Sessions cannot be generated in parallel
The batch input program must not open a session until it has closed the preceding session.
Use the CALL DIALOG statement
Summary: Not recommended if you can enter data by way of sessions or CALL TRANSACTION USING.
Your program prepares data for a sequence of dialog screens, and calls a dialog module for immediate processing.
The most important aspects of the CALL DIALOG interface are:
o Synchronous processing
o Transfers data for a sequence of dialog screens
o No separate database update for the dialog
A database update occurs only when the calling program executes a commit operation.
o Shares LUW with calling program
o No batch input processing log is generated
Executing Data Transfer Programs
Procedure
If you are using an SAP data transfer program, follow the procedure specified in the program documentation.
If you are using a generated data transfer program, proceed as follows:
1. Start the data transfer program.
2. Decide which batch input method you want to use for the data transfer.
a) CALL TRANSACTION USING:
You must specify the:
Processing mode: You use this parameter to specify whether processing should take place in the background or in dialog mode.
Possible values are:
A Display all
E Display only errors
N No display
Update mode: This parameter determines how the data is to be updated:
Possible values are:
S Synchronous
A Asynchronous
L Local update
Error session: Here you have the option to specify a session name for a batch input session in which data is to be written in the case of an error. You can use this to identify incorrect data records after the batch input program has run and to import the records into the R/3 System once you have corrected them.
If you are creating an error session, you must also specify:
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
b) Generate session:
Session name: Specify a name for the batch input session to be generated.
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
3. Specify a character that is to be used as the NODATA character.
4. Specify the path of the data file from which the data is to be imported into the R/3 System.
5. Execute the program.
6. If you have generated a session, or if errors occurred in CALL sTRANSACTION USING mode, you must now edit the generated sessions. You can find information on this in BC - System services in batch input sessions.
Batch Input Authorizations
You do not need special authorization - other than the ABAP run time authorization (authorization object S_PROGRAM - to run a program that creates batch input. Any user can create batch input sessions.
Starting processing for a session once it is in the queue is another matter, however. You can find more information on this in batch input sessions.
Creating a Session with BDC_OPEN_GROUP
Use the BDC_OPEN_GROUP function module to create a new session. Once you have created a session, then you can insert batch input data into it with BDC_INSERT.
You cannot re-open a session that already exists and has been closed. If you call BDC_OPEN_GROUP with the name of an existing session, then an additional session with the same name is created.
A batch input program may have only one session open at a time. Before opening a session, make sure that any sessions that the program closes any sessions that it previously had opened.
BDC_OPEN_GROUP takes the following EXPORTING parameters:
CLIENT
Client in which the session is to be processed.
Default: If you don't provide a value for this parameter, the default is the client under which the batch input program runs when the session is created.
GROUP
Name of the session that is to be created. May be up to 12 characters long.
Default: None. You must specify a session name.
HOLDDATE
Lock date. The session is locked and may not be processed until after the date that you specify. Only a system administrator with the LOCK authorization for the authorization object Batch Input Authorizations can unlock and run a session before this date.
Format: YYYYMMDD (8 digits).
Default: No lock date, session can be processed immediately. A lock date is optional.
KEEP
Retain session after successful processing. Set this option to the value X to have a session kept after it has been successfully processed. A session that is kept remains in the input/output queue until an administrator deletes it.
Sessions that contain errors in transactions are kept even if KEEP is not set.
Default: If not set, then sessions that are successfully processed are deleted. Only the batch input log is kept.
USER
Authorizations user for background processing. This is the user name that is used for checking authorizations if a session is started in background processing. The user must be authorized for all of the transactions and functions that are to be executed in a session. Otherwise, transactions will be terminated with "no authorization" errors.
The user can be of type dialog or background. Dialog users are normal interactive users in the R/3 System. Background users are user master records that are specially defined for providing authorizations for background processing jobs.
Adding Data to a Session: BDC_INSERT
Use the BDC_INSERT function module to add a transaction to a batch input session. You specify the transaction that is to be started in the call to BDC_INSERT. You must provide a BDCDATA structure that contains all of the data required to process the transaction completely.
BDC_INSERT takes the following parameters:
TCODE
The code of the transaction that is to be run.
POST_LOCAL
Parameter to update data locally. If POST_LOCAL = X, data will be updated locally.
(refer to the keyword documentation of SET UPDATE TASK LOCAL for more information)
DYNPROTAB
The BDCDATA structure that contains the data that is to be processed by the transaction.
DYNPROTAB is a table parameter in the function module.
Closing a Session: BDC_CLOSE_GROUP
Use the BDC_CLOSE_GROUP function module to close a session after you have inserted all of your batch input data into it. Once a session is closed, it can be processed.
Function Module BDC_CLOSE_GROUP
Exception parameters
Parameter Function
NOT_OPEN Client
QUEUE_ERROR Internal use
BDC_CLOSE_GROUP needs no parameters. It automatically closes the session that is currently open in your program.
You must close a session before you can open another session from the same program.
You cannot re-open a session once it has been closed. A new call to BDC_OPEN_GROUP with the same session name creates a new session with the same name.
Processing Batch Input Sessions
When you create a batch input session, it remains in the batch input queue until it is explicitly started. Session processing can be started in two ways:
An on-line user can start the session using the batch input menu options. (To access the batch input options, choose System  Services  Batch Input.)
You can submit the background job RSBDCSUB to start a session in background processing. If several sessions have the same name, RSBDCSUB starts them all.
Its possible to coordinate the generation and execution of a session in the background processing system.
You can, for example, schedule both the batch input program and RSBDCSUB in the background. If you designate the batch input job as the predecessor for RSBDCSUB, then RSBDCSUB will be started automatically when the batch input job successfully completes.
Alternatively, you can schedule both the batch input program and RSBDCSUB as job steps in a single background job. In this case, however, RSBDCSUB is started even if the batch input program should terminate abnormally.
For detailed information about processing batch input sessions, see Managing Batch Input Sessions in the System Services guide.
Frequent Data Transfer Errors
The most frequent errors include:
The BDCDATA structure contains screens in incorrect sequence.
The BDCDATA structure assigns a value to a field that does not exist on the current screen.
The BDCDATA structure contains a field that exceeds the specified length.
General guidelines
You should be aware of the following guidelines when you create sessions and call transactions or dialogs:
You must provide data for all required fields on a screen.
You can only specify the initial data for a screen. The system does not accept input as a response to a warning or an error message.
If there is more than one possible screen sequence for a transaction or dialog, your program specifies the screen sequence for the transaction. You must transfer all screens that the dialog user sees to the selected screen sequence. This applies even if the screen itself is not used to input data.
Direct Input
To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data. In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not process screens. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or Transaction BMV0.
Examples for direct input programs are:
Program Application
RFBIBL00 FI
RMDATIND MM
RVAFSS00 SD
RAALTD11 AM
RKEVEXT0 CO-PA
Pls reward points.
Regards,
Ameet -
MacBook Pro: I have no control of my trackpad, it's jumping all over the place ???
Pointer began moving around on it's own. I have no control over it and it makes my MBP useless. I haven't added anything new, help??
Check to be sure it is clean.
Look hard at your MacBook. Is the battery bulging? This puts pressure underneath the trackpad, and can cause it to malfunction.
Do you have a mouse plugged in as well? The mac will combine inputs from trackpad and mouse, so an additional mouse may make the cursor go all over the place. -
Why does Safari crashes when opening a new tab?
Here is the crash report.
Process: Safari [11775]
Path: /Applications/Safari.app/Contents/MacOS/Safari
Identifier: com.apple.Safari
Version: 5.0.5 (6533.21.1)
Build Info: WebBrowser-75332101~1
Code Type: X86-64 (Native)
Parent Process: launchd [10718]
Date/Time: 2011-05-24 13:49:18.593 -0400
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6
Interval Since Last Report: 41077 sec
Per-App Interval Since Last Report: 183839 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID: 9013D0E0-C713-45B2-A1CE-26151410B11F
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 11
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff832482e2 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x00007fff8324d92d pthread_mutex_lock + 469
2 com.apple.QuartzCore 0x00007fff88c874a8 CAViewDraw + 47
3 com.apple.Safari 0x000000010009f29a 0x100000000 + 651930
4 com.apple.AppKit 0x00007fff85148c49 -[NSView _drawRect:clip:] + 3390
5 com.apple.AppKit 0x00007fff851478bc -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1325
6 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
7 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
8 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
9 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
10 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
11 com.apple.AppKit 0x00007fff85147c26 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2199
12 com.apple.AppKit 0x00007fff85145f8e -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 767
13 com.apple.AppKit 0x00007fff85146e5a -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4555
14 com.apple.AppKit 0x00007fff85146e5a -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 4555
15 com.apple.AppKit 0x00007fff85145ab0 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 254
16 com.apple.AppKit 0x00007fff85142362 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2683
17 com.apple.AppKit 0x00007fff850bbb9a -[NSView displayIfNeeded] + 969
18 com.apple.Safari 0x000000010003415c 0x100000000 + 213340
19 com.apple.AppKit 0x00007fff850b6a46 _handleWindowNeedsDisplay + 678
20 com.apple.CoreFoundation 0x00007fff81f2eb37 __CFRunLoopDoObservers + 519
21 com.apple.CoreFoundation 0x00007fff81f0a464 __CFRunLoopRun + 468
22 com.apple.CoreFoundation 0x00007fff81f09dbf CFRunLoopRunSpecific + 575
23 com.apple.HIToolbox 0x00007fff82b037ee RunCurrentEventLoopInMode + 333
24 com.apple.HIToolbox 0x00007fff82b03551 ReceiveNextEventCommon + 148
25 com.apple.HIToolbox 0x00007fff82b034ac BlockUntilNextEventMatchingListInMode + 59
26 com.apple.AppKit 0x00007fff8508be64 _DPSNextEvent + 718
27 com.apple.AppKit 0x00007fff8508b7a9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
28 com.apple.Safari 0x0000000100015ff6 0x100000000 + 90102
29 com.apple.AppKit 0x00007fff8505148b -[NSApplication run] + 395
30 com.apple.AppKit 0x00007fff8504a1a8 NSApplicationMain + 364
31 com.apple.Safari 0x0000000100009f18 0x100000000 + 40728
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff8326112a kevent + 10
1 libSystem.B.dylib 0x00007fff83262ffd _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff83262cd4 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff832627fe _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff83262128 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff83261fc5 start_wqthread + 13
Thread 2: WebCore: IconDatabase
0 libSystem.B.dylib 0x00007fff83282f8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff83286da1 _pthread_cond_wait + 1286
2 com.apple.WebCore 0x00007fff85e8e0f9 WebCore::IconDatabase::syncThreadMainLoop() + 249
3 com.apple.WebCore 0x00007fff85e8a1fc WebCore::IconDatabase::iconDatabaseSyncThread() + 172
4 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
5 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 3: Safari: CertRevocationChecker
0 libSystem.B.dylib 0x00007fff8324829a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff8324890d mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff81f0a932 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff81f09dbf CFRunLoopRunSpecific + 575
4 com.apple.Safari 0x000000010002f5c5 0x100000000 + 193989
5 com.apple.Safari 0x000000010002f555 0x100000000 + 193877
6 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 4:
0 libSystem.B.dylib 0x00007fff8324829a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff8324890d mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff81f0a932 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff81f09dbf CFRunLoopRunSpecific + 575
4 com.apple.Foundation 0x00007fff87168f5f +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 297
5 com.apple.Foundation 0x00007fff870e9f29 __NSThread__main__ + 1429
6 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 5: Safari: SafeBrowsingManager
0 libSystem.B.dylib 0x00007fff8324829a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff8324890d mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff81f0a932 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff81f09dbf CFRunLoopRunSpecific + 575
4 com.apple.Safari 0x000000010002f5c5 0x100000000 + 193989
5 com.apple.Safari 0x000000010002f555 0x100000000 + 193877
6 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 6: com.apple.CFSocket.private
0 libSystem.B.dylib 0x00007fff8328be52 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x00007fff81f2c498 __CFSocketManager + 824
2 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
3 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 7: WebCore: LocalStorage
0 libSystem.B.dylib 0x00007fff83282f8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff83286da1 _pthread_cond_wait + 1286
2 com.apple.JavaScriptCore 0x00007fff8742ba40 ***::ThreadCondition::timedWait(***::Mutex&, double) + 64
3 com.apple.WebCore 0x00007fff861defb1 WebCore::LocalStorageThread::threadEntryPoint() + 193
4 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
5 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 8: Safari: SnapshotStore
0 libSystem.B.dylib 0x00007fff83282f8a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff83286da1 _pthread_cond_wait + 1286
2 com.apple.JavaScriptCore 0x00007fff8742ba40 ***::ThreadCondition::timedWait(***::Mutex&, double) + 64
3 com.apple.Safari 0x00000001001be5bd 0x100000000 + 1828285
4 com.apple.Safari 0x00000001000470a7 0x100000000 + 290983
5 com.apple.Safari 0x0000000100046f25 0x100000000 + 290597
6 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 9:
0 libSystem.B.dylib 0x00007fff8324829a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff8324890d mach_msg + 59
2 com.apple.QuartzCore 0x00007fff88c803a6 CA::Render::Server::server_thread(void*) + 177
3 com.apple.QuartzCore 0x00007fff88c802e6 thread_fun + 34
4 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
5 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 10:
0 libSystem.B.dylib 0x00007fff83261f4a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff8326235c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff83261fc5 start_wqthread + 13
Thread 11 Crashed:
0 com.apple.GeForceGLDriver 0x0000000200012ce0 gldAttachDrawable + 2528
1 com.apple.GeForceGLDriver 0x00000002000d6787 gldUpdateDispatch + 14359
2 com.apple.GeForceGLDriver 0x00000002000d7016 gldFinish + 646
3 com.apple.opengl 0x00007fff85a8c24d CGLFlushDrawable + 67
4 com.apple.QuartzCore 0x00007fff88c8831b view_draw(_CAView*, double, CVTimeStamp const*, bool) + 2980
5 com.apple.QuartzCore 0x00007fff88c87720 view_display_link(double, CVTimeStamp const*, void*) + 64
6 com.apple.QuartzCore 0x00007fff88c87667 link_callback + 219
7 com.apple.CoreVideo 0x00007fff815b10ab CVDisplayLink::performIO(CVTimeStamp*) + 431
8 com.apple.CoreVideo 0x00007fff815b0310 CVDisplayLink::runIOThread() + 754
9 com.apple.CoreVideo 0x00007fff815affe3 startIOThread(void*) + 139
10 libSystem.B.dylib 0x00007fff832814f6 _pthread_start + 331
11 libSystem.B.dylib 0x00007fff832813a9 thread_start + 13
Thread 11 crashed with X86 Thread State (64-bit):
rax: 0x00000000070496f4 rbx: 0x0000000000000002 rcx: 0x00007fff8324829a rdx: 0x00000000e00002c2
rdi: 0x00000000e00002c2 rsi: 0x00007fff705905c0 rbp: 0x0000000107dcd8f0 rsp: 0x0000000107dcd8f0
r8: 0x00000000000083c3 r9: 0x0000000000000000 r10: 0x00000000000010bc r11: 0x0000000000000206
r12: 0x0000000107dd1000 r13: 0x0000000102f4c000 r14: 0x0000000000000000 r15: 0x0000000107dcd920
rip: 0x0000000200012ce0 rfl: 0x0000000000010296 cr2: 0x0000000000000000
Binary Images:
0x100000000 - 0x1006afff7 com.apple.Safari 5.0.5 (6533.21.1) <B81D1199-542C-D929-A1CA-A139EA6262C1> /Applications/Safari.app/Contents/MacOS/Safari
0x100f80000 - 0x100f81fff +com.presenta.iGetterBundle 2.8.5 (2.8.5) <B1379AAB-5499-F07D-C498-E6D4C714B789> /Users/amandaoneill/Library/Internet Plug-Ins/iGetterBundle.plugin/Contents/MacOS/iGetterBundle
0x100f84000 - 0x100f88fff +com.presenta.iGetterSafariBundle 2.8.5 (2.8.5) <83AA0108-1E06-4987-259A-CAA7D9E090CF> /Users/amandaoneill/Library/Internet Plug-Ins/iGetterBundle.plugin/Contents/Resources/iGetterSafariBundle.bundle/Con tents/MacOS/iGetterSafariBundle
0x100fb1000 - 0x100fb1fff com.apple.JavaPluginCocoa 13.4.0 (13.4.0) <00AF9559-29EA-5E25-42CF-BE2447F9EBC5> /System/Library/Frameworks/JavaVM.framework/Versions/A/JavaPluginCocoa.bundle/C ontents/MacOS/JavaPluginCocoa
0x100fb5000 - 0x100fbaff7 JavaLaunching ??? (???) <E859D1E8-3E9D-5432-DCFA-684A9B1EDD2C> /System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunch ing
0x107cf3000 - 0x107d19fff GLRendererFloat ??? (???) <0AF0FF0D-6FD6-B5FA-9991-C8F58E8F1DD4> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x108120000 - 0x1082b1fef GLEngine ??? (???) <7B2CD458-D828-6A44-C918-C194838974D5> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x1082e2000 - 0x108705fef libclh.dylib 3.1.1 C (3.1.1) <0774DA8C-734E-2639-0F37-CCB20D17CDBD> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/libclh.dylib
0x11a01b000 - 0x11a1d0fff libCMaps.A.dylib 545.0.0 (compatibility 64.0.0) <63054685-73A1-615F-464C-05A4C5F0043D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCMaps.A.dylib
0x200000000 - 0x200787fff com.apple.GeForceGLDriver 1.6.26 (6.2.6) <D469864E-34A6-37EE-A01D-7C2AF0223D35> /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDrive r
0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <472D950D-70F8-B810-A959-9184C2AA6C74> /usr/lib/dyld
0x7fff80003000 - 0x7fff8000eff7 com.apple.HelpData 2.0.5 (34.1.1) <24DC6CD3-02B7-9332-FF6D-F0C545857B55> /System/Library/PrivateFrameworks/HelpData.framework/Versions/A/HelpData
0x7fff8000f000 - 0x7fff80025fef libbsm.0.dylib ??? (???) <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib
0x7fff80026000 - 0x7fff80067ff7 com.apple.CoreMedia 0.484.20 (484.20) <42F3B74A-F886-33A0-40EE-8399B12BD32A> /System/Library/PrivateFrameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff8021d000 - 0x7fff80265ff7 libvDSP.dylib 268.0.1 (compatibility 1.0.0) <170DE04F-89AB-E295-0880-D69CAFBD7979> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x7fff80266000 - 0x7fff803e4ff7 com.apple.WebKit 6533.21 (6533.21.1) <E954BB9E-51DC-9B68-5312-E1507329A9B3> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff803e5000 - 0x7fff80418fff libTrueTypeScaler.dylib ??? (???) <6EFBF3B7-E4D5-E6AE-5A7D-22F37E288737> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib
0x7fff80419000 - 0x7fff804a8fff com.apple.PDFKit 2.5.1 (2.5.1) <7B8A187A-F0BB-44E7-FBD4-9E1C5F9D5E85> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
0x7fff804f9000 - 0x7fff804fcfff com.apple.help 1.3.1 (41) <54B79BA2-B71B-268E-8752-5C8EE00E49E4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x7fff80547000 - 0x7fff8056ffff com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff80669000 - 0x7fff80d6606f com.apple.CoreGraphics 1.545.0 (???) <F0A5F62D-4C66-5B1F-4F13-322932915901> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff80d67000 - 0x7fff80de9fff com.apple.QuickLookUIFramework 2.3 (327.6) <9093682A-0E2D-7D27-5F22-C96FD00AE970> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.f ramework/Versions/A/QuickLookUI
0x7fff80dea000 - 0x7fff80eacfef libFontParser.dylib ??? (???) <363E2A8A-CEFE-9A74-E677-C240B27A4FC6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x7fff80ebc000 - 0x7fff80effff7 libRIP.A.dylib 545.0.0 (compatibility 64.0.0) <2C596A24-8B86-79D6-1A8E-5E8FFB6A1558> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fff80f00000 - 0x7fff80f20ff7 com.apple.DirectoryService.Framework 3.6 (621.11) <AD76C757-6701-BDB5-631E-1CB77D669586> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x7fff80f21000 - 0x7fff80f9efef com.apple.backup.framework 1.2.2 (1.2.2) <13A0D34C-28B7-2140-ECC9-B08D10CD4AB5> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x7fff80fc7000 - 0x7fff8107cfe7 com.apple.ink.framework 1.3.3 (107) <FFC46EE0-3544-A459-2AB9-94778A75E3D4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x7fff8107d000 - 0x7fff81081ff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x7fff810a6000 - 0x7fff810e3fff com.apple.LDAPFramework 2.0 (120.1) <16383FF5-0537-6298-73C9-473AEC9C149C> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x7fff8112f000 - 0x7fff8113bfff libbz2.1.0.dylib 1.0.5 (compatibility 1.0.0) <6FB0A8F4-72A1-D28F-E801-DE2C7498AFB9> /usr/lib/libbz2.1.0.dylib
0x7fff8113c000 - 0x7fff81155fff com.apple.CFOpenDirectory 10.6 (10.6) <CCF79716-7CC6-2520-C6EB-A4F56AD0A207> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff81156000 - 0x7fff81161ff7 com.apple.speech.recognition.framework 3.11.1 (3.11.1) <F0DDF27E-DB55-07CE-E548-C62095BE8167> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x7fff81162000 - 0x7fff81162ff7 com.apple.Cocoa 6.6 (???) <68B0BE46-6E24-C96F-B341-054CF9E8F3B6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff81163000 - 0x7fff8119efff com.apple.AE 496.4 (496.4) <CBEDB6A1-FD85-F842-4EB8-CC289FAE0F24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff8119f000 - 0x7fff811f1ff7 com.apple.HIServices 1.8.2 (???) <7C91D07D-FA20-0882-632F-0CAE4FAC2B79> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x7fff811f2000 - 0x7fff81235fef libtidy.A.dylib ??? (???) <2F4273D3-418B-668C-F488-7E659D3A8C23> /usr/lib/libtidy.A.dylib
0x7fff81253000 - 0x7fff8126eff7 com.apple.openscripting 1.3.1 (???) <FD46A0FE-AC79-3EF7-AB4F-396D376DDE71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x7fff812d6000 - 0x7fff813effef libGLProgrammability.dylib ??? (???) <C4BB281B-629D-08ED-2991-3D51671B0B02> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
0x7fff813f0000 - 0x7fff814a6fff libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <F206BE6D-8777-AE6C-B367-7BEA76C14241> /usr/lib/libobjc.A.dylib
0x7fff814a7000 - 0x7fff814b8fff SyndicationUI ??? (???) <62A4BC15-72EA-0CC1-046A-52E576E8D751> /System/Library/PrivateFrameworks/SyndicationUI.framework/Versions/A/Syndicatio nUI
0x7fff814b9000 - 0x7fff8151bfe7 com.apple.datadetectorscore 2.0 (80.7) <34592AFF-B1B8-2277-B013-70193E4E1691> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff81563000 - 0x7fff815adff7 com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff815ae000 - 0x7fff815d3ff7 com.apple.CoreVideo 1.6.2 (45.6) <E138C8E7-3CB6-55A9-0A2C-B73FE63EA288> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x7fff815d4000 - 0x7fff816bafef com.apple.DesktopServices 1.5.10 (1.5.10) <B7E00D85-F971-D85B-0217-482E15E9E924> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x7fff816bb000 - 0x7fff816bbff7 com.apple.Carbon 150 (152) <1E95560E-7036-A7FB-66FA-8ABA150343D6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff818bb000 - 0x7fff819e3ff7 com.apple.MediaToolbox 0.484.20 (484.20) <628A7245-7ADE-AD47-3368-CF8EDCA6CC1C> /System/Library/PrivateFrameworks/MediaToolbox.framework/Versions/A/MediaToolbo x
0x7fff819e4000 - 0x7fff819eaff7 com.apple.CommerceCore 1.0 (9) <4C66D962-91B5-F25C-A6FF-DFD5F924A0DD> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x7fff819eb000 - 0x7fff81af5ff7 com.apple.MeshKitIO 1.1 (49.2) <F296E151-80AE-7764-B969-C2050DF26BFE> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshK itIO.framework/Versions/A/MeshKitIO
0x7fff81af6000 - 0x7fff81d38fe7 com.apple.AddressBook.framework 5.0.4 (883) <3C634319-4B5B-592B-2D3A-A16336F93AA0> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x7fff81d4f000 - 0x7fff81d50fff com.apple.MonitorPanelFramework 1.3.0 (1.3.0) <5062DACE-FCE7-8E41-F5F6-58821778629C> /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPane l
0x7fff81d51000 - 0x7fff81e86ff7 com.apple.audio.toolbox.AudioToolbox 1.6.6 (1.6.6) <AFAB42A2-A3A8-83D8-D583-613625706690> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x7fff81e87000 - 0x7fff81e8bff7 libCGXType.A.dylib 545.0.0 (compatibility 64.0.0) <49E6AF5D-AF9B-67CF-A6B8-C79F6BA8A627> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x7fff81e8c000 - 0x7fff81e8dff7 com.apple.TrustEvaluationAgent 1.1 (1) <74800EE8-C14C-18C9-C208-20BBDB982D40> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x7fff81ebe000 - 0x7fff82035fe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff82036000 - 0x7fff8221aff7 libType1Scaler.dylib ??? (???) <A2207818-4828-41AD-0F6D-87A07F238388> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libType1Scaler.dylib
0x7fff8231e000 - 0x7fff8235ffef com.apple.QD 3.36 (???) <5DC41E81-32C9-65B2-5528-B33E934D5BB4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x7fff82360000 - 0x7fff82391fff libGLImage.dylib ??? (???) <6925991A-9B1B-B9FA-645A-807F9BCC3DE7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x7fff82392000 - 0x7fff8244bfff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib
0x7fff8244c000 - 0x7fff8247bff7 com.apple.quartzfilters 1.6.0 (1.6.0) <9CECB4FC-1CCF-B8A2-B935-5888B21CBEEF> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters .framework/Versions/A/QuartzFilters
0x7fff82492000 - 0x7fff824a8fff com.apple.ImageCapture 6.0.2 (6.0.2) <06E4103B-9BE4-7EAD-B532-89FC5EB06ED4> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x7fff824a9000 - 0x7fff8257bfe7 com.apple.CFNetwork 454.11.12 (454.11.12) <B1C9008A-4A5D-609D-5D10-C93DAD6FFB4C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x7fff8257c000 - 0x7fff82582ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff82588000 - 0x7fff825d4fff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib
0x7fff825d5000 - 0x7fff825d5ff7 com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <DA9BFF01-40DF-EBD5-ABB7-787DAF2D77CF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x7fff825d6000 - 0x7fff82636fe7 com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff82637000 - 0x7fff82638ff7 com.apple.audio.units.AudioUnit 1.6.6 (1.6.6) <BE4E577D-87EC-8FD0-5341-AE99CE4ADC99> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x7fff82639000 - 0x7fff826b5ff7 com.apple.ISSupport 1.9.4 (52) <93A57F16-3BD5-25AD-5CFF-00007A141129> /System/Library/PrivateFrameworks/ISSupport.framework/Versions/A/ISSupport
0x7fff826b6000 - 0x7fff82920fef com.apple.QuartzComposer 4.2 ({156.28}) <7586E7BD-D3BD-0EAC-5AC9-0BFA3679017C> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzCompose r.framework/Versions/A/QuartzComposer
0x7fff82921000 - 0x7fff82923fff libRadiance.dylib ??? (???) <73257486-8E94-E758-1A5A-5B521F27EE12> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x7fff82924000 - 0x7fff8296bfff com.apple.QuickLookFramework 2.3 (327.6) <11DFB135-24A6-C0BC-5B97-ECE352A4B488> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook
0x7fff82a42000 - 0x7fff82abffef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
0x7fff82ac0000 - 0x7fff82ad4ff7 com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <621B7415-A0B9-07A7-F313-36BEEDD7B132> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x7fff82ad5000 - 0x7fff82dd3fff com.apple.HIToolbox 1.6.5 (???) <AD1C18F6-51CB-7E39-35DD-F16B1EB978A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x7fff82ddc000 - 0x7fff82ef3fef libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <1B27AFDD-DF87-2009-170E-C129E1572E8B> /usr/lib/libxml2.2.dylib
0x7fff82f10000 - 0x7fff83244fff com.apple.CoreServices.CarbonCore 861.34 (861.34) <B5680539-CB31-6C6D-C0AD-606D4D46E7F5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff83245000 - 0x7fff83246fff liblangid.dylib ??? (???) <EA4D1607-2BD5-2EE2-2A3B-632EEE5A444D> /usr/lib/liblangid.dylib
0x7fff83247000 - 0x7fff83408fff libSystem.B.dylib 125.2.10 (compatibility 1.0.0) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
0x7fff83409000 - 0x7fff83434ff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib
0x7fff83435000 - 0x7fff8346efef libcups.2.dylib 2.8.0 (compatibility 2.0.0) <F8E0672F-C0B4-B161-E50D-A1405D14F21C> /usr/lib/libcups.2.dylib
0x7fff8346f000 - 0x7fff834befef libTIFF.dylib ??? (???) <F0F7F0B7-7253-F88F-9E2D-FA3770143758> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x7fff83620000 - 0x7fff836c0fff com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff836c1000 - 0x7fff836faff7 com.apple.MeshKit 1.1 (49.2) <3795F201-4A5F-3D40-57E0-87AD6B714239> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/MeshKit
0x7fff83707000 - 0x7fff837a1ff7 com.apple.ApplicationServices.ATS 275.15.1 (???) <55B528A6-0C88-6CB8-152B-A34A440FACFE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x7fff837e1000 - 0x7fff83825fe7 com.apple.ImageCaptureCore 1.0.4 (1.0.4) <F4ED3329-1A86-EB10-CFC2-999D8699B5E6> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCo re
0x7fff83826000 - 0x7fff838a5fe7 com.apple.audio.CoreAudio 3.2.6 (3.2.6) <1DD64A62-0DE4-223F-F781-B272FECF80F0> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x7fff838a6000 - 0x7fff838edff7 com.apple.coreui 2 (114) <D7645B59-0431-6283-7322-957D944DAB21> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x7fff838f7000 - 0x7fff83d3afef libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <0CC61C98-FF51-67B3-F3D8-C5E430C201A9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x7fff83d3b000 - 0x7fff83d78ff7 libFontRegistry.dylib ??? (???) <8C69F685-3507-1B8F-51AD-6183D5E88979> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x7fff83d79000 - 0x7fff83d88fff com.apple.NetFS 3.2.2 (3.2.2) <7CCBD70E-BF31-A7A7-DB98-230687773145> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff83d89000 - 0x7fff83d9eff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <DC999B32-BF41-94C8-0583-27D9AB463E8B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x7fff83d9f000 - 0x7fff845a9fe7 libBLAS.dylib 219.0.0 (compatibility 1.0.0) <FC941ECB-71D0-FAE3-DCBF-C5A619E594B8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x7fff845aa000 - 0x7fff849d5fef com.apple.RawCamera.bundle 3.6.4 (561) <C4AB0054-B2C8-246E-0F17-98F4BD5BE94C> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x7fff849d6000 - 0x7fff84a62fef SecurityFoundation ??? (???) <D844BB57-386A-0A43-249E-9BE035C2AB53> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x7fff84a71000 - 0x7fff84a71ff7 com.apple.ApplicationServices 38 (38) <10A0B9E9-4988-03D4-FC56-DDE231A02C63> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x7fff84a72000 - 0x7fff84be1fe7 com.apple.QTKit 7.6.6 (1756.15) <B35EDB1D-FCB0-1D40-629E-6ACB56D57C68> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x7fff84c48000 - 0x7fff84c82fff libssl.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <C7153747-50E3-32DA-426F-CC4C505D1D6C> /usr/lib/libssl.0.9.8.dylib
0x7fff84c83000 - 0x7fff84e3bfef com.apple.ImageIO.framework 3.0.4 (3.0.4) <EFB373AE-FE02-40C4-ABDC-09D61AFD25EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x7fff84e3c000 - 0x7fff84e50fff libGL.dylib ??? (???) <0FA671EB-6FA0-BA97-C00A-C42247C22B26> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x7fff84f2e000 - 0x7fff84fbefff com.apple.SearchKit 1.3.0 (1.3.0) <4175DC31-1506-228A-08FD-C704AC9DF642> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff84fbf000 - 0x7fff84fbfff7 com.apple.quartzframework 1.5 (1.5) <5BFE5998-26D9-0AF1-1522-55C78E41F778> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x7fff84fc0000 - 0x7fff84fc0ff7 com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff84fc1000 - 0x7fff85006fff com.apple.CoreMediaIOServices 134.0 (1160) <BA22EA4A-4572-749A-4FE0-1323E0B6F6F3> /System/Library/PrivateFrameworks/CoreMediaIOServices.framework/Versions/A/Core MediaIOServices
0x7fff85013000 - 0x7fff85024fff com.apple.DSObjCWrappers.Framework 10.6 (134) <3C08225D-517E-2822-6152-F6EB13A4ADF9> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x7fff85048000 - 0x7fff85a3efff com.apple.AppKit 6.6.7 (1038.35) <9F4DF818-9DB9-98DA-490C-EF29EA757A97> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff85a3f000 - 0x7fff85a88fef libGLU.dylib ??? (???) <0FCD57C5-D7AA-F2DD-D2EC-C1C8B931F65C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x7fff85a89000 - 0x7fff85a98fff com.apple.opengl 1.6.12 (1.6.12) <29482652-1E44-1C47-428F-1209AA65336D> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x7fff85a99000 - 0x7fff85ab6ff7 libPng.dylib ??? (???) <0C232C1E-49C8-F7A9-9634-DF2BDA1AB722> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x7fff85abf000 - 0x7fff85ac1fff com.apple.print.framework.Print 6.1 (237.1) <CA8564FB-B366-7413-B12E-9892DA3C6157> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x7fff85ac2000 - 0x7fff85ae5fff com.apple.opencl 12.3.6 (12.3.6) <42FA5783-EB80-1168-4015-B8C68F55842F> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff85ae6000 - 0x7fff85becfe7 com.apple.PubSub 1.0.5 (65.21) <1F9B7C84-375D-036F-790A-02BBE7BCE445> /System/Library/Frameworks/PubSub.framework/Versions/A/PubSub
0x7fff85bed000 - 0x7fff85caefef com.apple.ColorSync 4.6.6 (4.6.6) <EC6C8119-23F6-A96E-47A3-5CD31E462AE3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x7fff85caf000 - 0x7fff85cb2ff7 libCoreVMClient.dylib ??? (???) <00C97B96-8D3B-45EB-F503-DB49712DC42D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
0x7fff85d8c000 - 0x7fff85d91ff7 com.apple.CommonPanels 1.2.4 (91) <4D84803B-BD06-D80E-15AE-EFBE43F93605> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x7fff85df2000 - 0x7fff85df9fff com.apple.OpenDirectory 10.6 (10.6) <4200CFB0-DBA1-62B8-7C7C-91446D89551F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x7fff85e52000 - 0x7fff85e87fef com.apple.framework.Apple80211 6.2.4 (624.2) <B2CB69CE-A4F5-D70F-03DE-CF985D5558A2> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x7fff85e88000 - 0x7fff86b03fef com.apple.WebCore 6533.21 (6533.21.1) <A7433C61-B507-BDB0-9CA8-1A3A2A699B2F> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.frame work/Versions/A/WebCore
0x7fff86b34000 - 0x7fff86b45ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <FB5EE53A-0534-0FFA-B2ED-486609433717> /usr/lib/libz.1.dylib
0x7fff86b7b000 - 0x7fff86c9cfe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <48AEAFE1-21F4-B3C8-4199-35AD5E8D0613> /usr/lib/libcrypto.0.9.8.dylib
0x7fff86cb6000 - 0x7fff86cccfe7 com.apple.MultitouchSupport.framework 207.10 (207.10) <1828C264-A54A-7FDD-FE1B-49DDE3F50779> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x7fff86ccd000 - 0x7fff86daafff com.apple.vImage 4.1 (4.1) <C3F44AA9-6F71-0684-2686-D3BBC903F020> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x7fff86dab000 - 0x7fff86e68fff com.apple.CoreServices.OSServices 359 (359) <8F509D8D-4C94-9A1C-3A87-5B775D9F6075> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff86e69000 - 0x7fff87027fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <2C6ECACF-CD56-1714-6F63-CB6F5EE7A1E2> /usr/lib/libicucore.A.dylib
0x7fff87028000 - 0x7fff870d8fff edu.mit.Kerberos 6.5.11 (6.5.11) <085D80F5-C9DC-E252-C21B-03295E660C91> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x7fff870d9000 - 0x7fff8735cfe7 com.apple.Foundation 6.6.6 (751.53) <476E617B-B59B-53DE-991D-98C1993BCBCE> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8738d000 - 0x7fff8738dff7 com.apple.vecLib 3.6 (vecLib 3.6) <08D3D45D-908B-B86A-00BA-0F978D2702A7> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x7fff8738e000 - 0x7fff8738eff7 com.apple.Accelerate 1.6 (Accelerate 1.6) <2BB7D669-4B40-6A52-ADBD-DA4DB3BC0B1B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x7fff8738f000 - 0x7fff873f7fff com.apple.MeshKitRuntime 1.1 (49.2) <1F4C9AB5-9D3F-F91D-DB91-B78610562ECC> /System/Library/PrivateFrameworks/MeshKit.framework/Versions/A/Frameworks/MeshK itRuntime.framework/Versions/A/MeshKitRuntime
0x7fff873f8000 - 0x7fff87419fff libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <6993F348-428F-C97E-7A84-7BD2EDC46A62> /usr/lib/libresolv.9.dylib
0x7fff8741a000 - 0x7fff8760afef com.apple.JavaScriptCore 6533.20 (6533.20.20) <0AA8B101-C02C-0858-84BC-4E4D397E0231> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x7fff8760b000 - 0x7fff8763bfef com.apple.shortcut 1.1 (1.1) <A99C9D8E-290B-B1E4-FEA5-CC5F2FB9C18D> /System/Library/PrivateFrameworks/Shortcut.framework/Versions/A/Shortcut
0x7fff8763c000 - 0x7fff87685ff7 com.apple.securityinterface 4.0.1 (40418) <E2DC796D-84EC-48F5-34A9-DF614573BE74> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
0x7fff87686000 - 0x7fff8768cff7 IOSurface ??? (???) <04EDCEDE-E36F-15F8-DC67-E61E149D2C9A> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x7fff87841000 - 0x7fff87853fe7 libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <76B83C8D-8EFE-4467-0F75-275648AFED97> /usr/lib/libsasl2.2.dylib
0x7fff87854000 - 0x7fff87863fff libxar.1.dylib ??? (???) <CBAF862A-3C77-6446-56C2-9C4461631AAF> /usr/lib/libxar.1.dylib
0x7fff87ba8000 - 0x7fff87badfff libGFXShared.dylib ??? (???) <878C429B-44D4-875C-1A35-4FD8C6152695> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x7fff87c79000 - 0x7fff87db7fff com.apple.CoreData 102.1 (251) <32233D4D-00B7-CE14-C881-6BF19FD05A03> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x7fff87db8000 - 0x7fff87ddefe7 libJPEG.dylib ??? (???) <AD42F658-7C32-EEE5-8341-A8EE6476BF46> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x7fff87ddf000 - 0x7fff87e2eff7 com.apple.DirectoryService.PasswordServerFramework 6.1 (6.1) <01B370FB-D524-F660-3826-E85B7F0D85CD> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
0x7fff87e2f000 - 0x7fff88333fe7 com.apple.VideoToolbox 0.484.20 (484.20) <8B6B82D2-350B-E9D3-5433-51453CDA65B4> /System/Library/PrivateFrameworks/VideoToolbox.framework/Versions/A/VideoToolbo x
0x7fff883a7000 - 0x7fff883b0ff7 com.apple.DisplayServicesFW 2.3.0 (283) <3D05929C-AB17-B8A4-DC81-87C27C59E664> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayS ervices
0x7fff8843e000 - 0x7fff88449fff com.apple.CrashReporterSupport 10.6.7 (258) <BB0B9A08-6CEC-0500-5BD1-C18E1465E406> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
0x7fff8844a000 - 0x7fff884bbff7 com.apple.AppleVAFramework 4.10.23 (4.10.23) <3304268B-A93D-9F79-09C0-AA9081406352> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x7fff8850d000 - 0x7fff88513fff libCGXCoreImage.A.dylib 545.0.0 (compatibility 64.0.0) <C863C133-EA3E-5403-FC44-FDC9F236DC98> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
0x7fff88514000 - 0x7fff88592ff7 com.apple.CoreText 3.151.8 (???) <5DCD6BD9-63FB-767E-5993-5AEBE890145B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x7fff88593000 - 0x7fff885ffff7 com.apple.CorePDF 1.3 (1.3) <6770FFB0-DEA0-61E0-3520-4B95CCF5D1CF> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF
0x7fff88600000 - 0x7fff8860dfe7 libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <45B5B514-7CEB-38A9-F34A-1D96F010EC42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x7fff8860e000 - 0x7fff8864ffff com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff88650000 - 0x7fff886bafe7 libvMisc.dylib 268.0.1 (compatibility 1.0.0) <75A8D840-4ACE-6560-0889-2AFB6BE08E59> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x7fff886bb000 - 0x7fff886c6fff com.apple.corelocation 12.1 (12.1) <7B5164FD-F5FD-6837-1DA3-6E18582CEDF3> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation
0x7fff886c7000 - 0x7fff886caff7 com.apple.securityhi 4.0 (36638) <38935851-09E4-DDAB-DB1D-30ADC39F7ED0> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x7fff886cb000 - 0x7fff88953fef com.apple.security 6.1.2 (55002) <015C9A08-3D07-9462-8E91-DB1924349621> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff88954000 - 0x7fff88962ff7 libkxld.dylib ??? (???) <4016E9E6-0645-5384-A697-2775B5228113> /usr/lib/system/libkxld.dylib
0x7fff88a19000 - 0x7fff88a6eff7 com.apple.framework.familycontrols 2.0.2 (2020) <F09541B6-5E28-1C01-C1AE-F6A2508670C7> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x7fff88ad0000 - 0x7fff88ad5fff libGIF.dylib ??? (???) <1B9DCB7F-CD1D-B23F-8AC6-5292B94A4D0E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x7fff88ba7000 - 0x7fff88c2cff7 com.apple.print.framework.PrintCore 6.3 (312.7) <CDFE82DD-D811-A091-179F-6E76069B432D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x7fff88c2d000 - 0x7fff88fcafe7 com.apple.QuartzCore 1.6.3 (227.36) <6FD8E129-135E-2F89-E9F0-A3CD0C6FCEF1> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7fff88fcb000 - 0x7fff89206fef com.apple.imageKit 2.0.3 (1.0) <5D18C246-303A-6580-9DC9-79BE79467C95> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.fram ework/Versions/A/ImageKit
0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f6
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.36.9)
Bluetooth: Version 2.4.0f1, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545025B9SA02, 232.89 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26100000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0x06300000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06610000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x06500000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24600000Hi,
I agree with Andyb.
/Users/amandaoneill/Library/Internet Plug-Ins/iGetterBundle.plugin/Contents/MacOS/iGetterBundle
If you do want to remove it:
Easiest way to remove igetter is re-download igetter (if you deleted the disk image) and drag to applications, you simply run "uninstall iGetter" , it will remove the input manager /plugin etc.
If that doesn't help note that Thread 11 crashed & imo it could be your graphic card, but then I blame everything on my GC
Good luck
Mia -
Why can't I scroll / Multi-touch with my new Magic Mouse?
I just got my first magic mouse and paired it with my 2008 model white macbook. It works as a mouse, but none of the multi-touch functionality is working. Here's the details
- I updated to lion recently, and i want to take advantage of the gesture technology. but my macbook is *PRE MULTI-TOUCH* so the track pad does none of those cool tricks. I thought that using the magic mouse I could use all those nifty features....
- I read on another forum that people were having trouble with USB OverdriveX, which I've used for a while. I removed the software with AppCleaner, which is supposed to clean out the plists and everything, and I restarted, but nothing's changed.
- I downloaded MagicPrefs, and although it shows me the magic mouse details screen, messing with the settings doesn't change anything, i still can't even scroll. Also i set the menu icon to show me the remaining battery life of my device, and instead of that it is grayed out. Does this mean it doesn't recognize my mouse?
- Finally, and this is what's most frustrating me: Everywhere I look I see the magic mouse preferance pane and it looks NOTHING like mine. I don't have a 'magic mouse' preference pane in my system preferences, and when i click on 'mouse' all i get is this:
I haven't come across anyone else with this problem, and I get the feeling that this might once again be a failure of my aging machine. But every other element of mac software is running, and the mouse recognizes movement, left click, and right click. Any advice would be helpful, thanks!I can't be sure it hasn't gotten mucked up with all those other steps you took, but here's what I know.
The Magic Mouse has some gestures, yes, but not all those found in a multi-touch trackpad. You can get a Magic Trackpad for that if you really want it all to work just the same.
However, to fix your issue, try uninstalling third-party mouse drivers (such as Logitech or Microsoft), USB Overdrive, BetterTouchTool, Jitouch, and/or drivers for other input-managing devices. Not getting the Magic Mouse preferences is usually the result of some third-party driver getting in the way. AppCleaner is a good way to do this, but you might want to search google for instructions specific to whatever drivers you may have installed and now want to remove.
Once you think you've got them all cleaned out, open bluetooth preferences and remove your Magic Mouse. Now re-add it and see if you get the Magic Mouse preferences screens that you've been seeing online.
Hopefully this has fixed it.
If so, I will add that I have greatly expanded my Magic Mouse capabilities with Better Touch Tool and never had the kinds of issues you're having now. If you do get the Magic Mouse set up correctly, do not fear to install Better Touch Tool after the fact. I know from experience it will not cause such havoc! -
The Application Installer quit unexpectedly error when reinstalling Safari
My Safari no longer functions as it was removed from my Powerbook and I no longer have the installation disk. I am attempting to manually install Safari3.2.3Ti.dmg. The installation stops and I receive "The Application Installer quit unexpectedly". I've tried the disk first aid and searched countless blogs but I am at a loss now. Please help - thank you in advance - Gary
Here is the most recent Report:
Date/Time: 2011-06-28 10:23:20.457 -1000
OS Version: 10.4.11 (Build 8S165)
Report Version: 4
Command: Installer
Path: /Applications/Utilities/Installer.app/Contents/MacOS/Installer
Parent: WindowServer [57]
Version: 2.1.9 (104)
Build Version: 36
Project Name: Installer
Source Version: 1040000
PID: 372
Thread: Unknown
Link (dyld) error:
Symbol not found:__ZN3JSC6JSCell14toThisJSStringEPNS_9ExecStateE
Referencedfrom:/System/Library/Frameworks/WebKit.framework/Versions/A/Framework s/WebCore.framework/Versions/A/WebCore
Expected in:/System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCor e
/System/Library/Frameworks/WebKit.framework/WebKit
Model: PowerBook5,6, BootROM 4.9.1f3, 1 processors, PowerPCG4 (1.2), 1.5 GHz, 512 MB
Graphics: ATI Mobility Radeon 9700, ATY,RV360M11, AGP, 64 MB
Memory Module: SODIMM0/J25LOWER, 512 MB, DDR SDRAM,PC2700U-25330
AirPort: AirPort Extreme, 405.1 (3.90.34.0.p18)
Modem: Jump, V.92, Version 1.0
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incomingserial ports
Network Service: AirPort, AirPort, en1
Network Service: Built-in Ethernet, PPP (PPPoE), ppp0
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
Parallel ATA Device: MATSHITACD-RW CW-8123
Parallel ATA Device: FUJITSU MHT2080AH, 74.53 GB
USB Device: Bluetooth USB Host Controller, Apple, Inc., Upto 12 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard/Trackpad, AppleComputer, Up to 12 Mb/sec, 500 mANot clear to me why you want to replace an out of date version of Safari with another out of date version?
If your Safari keeps crashing, or if you are updating Safari (or just have) and it is misbehaving:
N.B. Never delete Safari, never run it under Rosetta, don't use proxy settings, and don't change the application's name or move it from the top level of the Applications Folder to a sub-folder.
(If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall. Alternatively you can download Safari directly:
Safari 4.1.3 for Tiger can be downloaded here:
http://support.apple.com/kb/DL1069
Safari 5.0.5 for Leopard (and Snow Leopard) can be downloaded from here:
http://support.apple.com/kb/DL1070
Make sure you download the correct version for your system.
Also, observe the recommended procedure for installing software: repair permissions and close all applications, install, then repair permissions again.)
Input Managers and other plug-ins from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If Safari is crashing, the very [i]first[/i] thing to do is clear out your InputManagers folders (both in your own Library and in the top-level Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 used Safari 3.0.4 which was not a beta and which was updated to v.3.1.2, and now Tiger uses Safari 4.1.3 and Leopard uses Safari 5.0.5, as does Snow Leopard albeit a different version. If these latest versions of Safari are not the fastest browser you have ever used, then something is wrong!
(Trying to revert to a previous version of Safari can have repercussions, as previous versions of Safari used a completely different webkit on which other applications like iChat, Mail, Dashboard Widgets etc also rely, but if you really want to do this post back for instructions on the safe way to do so.)
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Add-ons that have been frequently mentioned here, among others, for causing such problems are Piclens, Saft, AcidSearch and Pithhelmet, and the dreaded CT Toolbar. If you have them, trash them and go the developer's sites to see if new versions are available for the latest version of Safari on your current operating system.
You must also ensure that you have downloaded and installed all the correct version for your Mac of Security Updates. These require a restart and a permission repair.
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
Hard Disk/Library/InputManagers
Home/Library/InputManagers
especially prior to system updates and updates to Safari (they can always be added back one-by-one later).
Lastly, the Safari updates require a restart of your Mac, and sometimes even a double restart is required. -
SIMBL v0.8.2 breaks Safari 4.x
I am posting this topic to help anyone having problems with Safari 4.x who may not be aware of having the SIMBL Input Manager installed on their computer.
There are several problems with Safari 4, including v4.0.2, that are directly attributable to the current version of SIMBL, 0.8.2. It is an Input Manager / plugin enabler for Cocoa apps that is used by a variety of applications. In my case it was installed with PithHelmet and Safari Tidy.
The problem I noticed was what I called a 'dead gutter zone' in the last 154 pixels on the right side of every web page, no matter what the size. If my cursor was within that area I could not click on any link or scroll using my trackpad. Several other problems attributable to this version of SIMBL also exist, as can be verified by searching for 'SIMBL' within the Safari for Mac discussion area.
The simple solution: Remove the SIMBL Input Manager files found at:
/Library/Application Support/SIMBL/
Then restart you Mac system.
There are other remnants of SIMBL as well, depending upon the application that installed it. Do a search for 'SIMBL' on your Mac to find all its instances, then trash them and restart.
I have written directly to the developer about this problem. If he provides a solution, it will be posted at:
http://culater.net/software/SIMBL/SIMBL.phpThe final solution to this problem is in the hands of the developer of SIMBL.
Maybe you are looking for
-
New Task changes date to 12/31/2031
When entering a new task on my Palm Desktop software (Ver 4.2 installed with Sprint Treo 755p), the software automatically puts the "due date" as 12/31/2031, even when the it's checked as "no due date". Is there a fix? Quite annoying. thx for the h
-
Multiple passes (groups) on same query data
I need to run a report which has two sets of results, one for the current month, one for year to date. This would be easy with subreports, but unfortunately it's a very complex report which has a number of subreports already. I'm using CR10 and SQL S
-
Update backend table from WebDynpro?
Hi, I need to create entries in the backend table HRUS_D2. I found that the FM used for this table is RH_UPDATE_SUBST_LIST_SERVER. I want to write a Java WebDynpro application display all the fields on the webpage which represents above table and up
-
Errors in a Russian translation
In advance I apologise for colloquial - technical English at me much better. And not to think out new rules of English language, has taken advantage of the machine translator. The Russian translation contains following errors: --------------- File iT
-
How do I delete/hide app purchase on the iPad?
Subject is the question/problem.