#IGETTER SLOW MAC OS X#
#IGETTER SLOW UPDATE#
#IGETTER SLOW ARCHIVE#
#IGETTER SLOW DOWNLOAD#

'That's enough! I decided that the user can just run Classic without Apple Menu Options.' Booted Classic into Extensions Manager enabled 'Apple Menu Options' - Classic wouldn?t boot. Disabled Apple Menu Options - Classic booted fine. Meanwhile, MacFixIt reader Don Seher reports that, in his case, the Apple Menu Options extension was causing problems: However, after successfully starting Classic with extensions off, I restarted Classic with my usual set of extensions no troubles at all.' 'I also couldn't get Classic to start after installing the 10.3.9 updater on my G4 400 (Sonnet 1Ghz upgrade).

However, some readers now report that simply starting Classic with Extensions off once is enough to eliminate subsequent startup problems. One of our previously suggested workarounds was to temporarily turn off all extensions (by holding down the Shift key while Classic is starting up), then isolate any potentially problematic extensions by restarting Classic with limited sets enabled.

#IGETTER SLOW MAC OS X#

Problems starting Classic (cont.) We previously noted that some users are having problems launching the Classic environment after updating to Mac OS X 10.3.9. Reinstalling Flash player/plugin doesn't solve the problem either.'įor some readers, however, re-installing Flash does provide resolution. The file just downloads but will not play even though Safari plugins show the Flash plugin is registered. One reader writes: 'I too am having flash problems.

#IGETTER SLOW DOWNLOAD#

You can still specify the download location by holding down the option key while control-clicking a link.įlash problems Readers continue to note problems with Macromedia Flash content in Safari 1.3. Note that the 'Integrate with Internet browsers (Watch for URL clicks)' option works well with Safari v1.3.'įile saving changes As noted by a number of readers, Safari 1.3 changes the default option from save as to save to download folder. 'We're working on a fix of this problem and will release a new version as soon as possible. Now, the developers of iGetter report that an updated, Mac OS X 10.3.9-compliant release is on the way: To avoid crashing of Safari v1.3 you must uncheck 'Add Contextual menu support for Internet browsers' option at iGetter preferences, Integration panel. IGetter fix coming We previously reported that the iGetter 2.2 Input Manager Bundle is incompatible with the new release of Safari (1.3, included with Mac OS X 10.3.9), causing crashes.

#IGETTER SLOW UPDATE#

The commands I suggested above reproduce the exact steps taken by JavaStartup to update the JSA, with the advantage of avoiding a reboot and not requiring any downloads.'

#IGETTER SLOW ARCHIVE#

This startup item rebuilds the Java Shared Archive on the first reboot after the upgrade, and then deletes itself. 'The reason why Java 1.4.2 Update 2 and Security Update 2005-002 can be used to fix the Java issue is that they include the JavaStartup startup item.

cd /System/Library/Frameworks/amework/Versions/1.4.2/Libraries/.

The Terminal commands are as follows (press the 'Return' key after each line): Now, MacFixIt reader Camillo Lugaresi offers a workaround that can be executed through the Terminal (located in Applications/Utilities), and replicates the fixing mechanism utilized by previous workarounds. After our initial coverage and posting of some successful workarounds, Apple acknowledged the issue with a Knowledge Base article that offers some limited fixes, including those published here. Terminal fix for Java issues Since the release of Mac OS X 10.3.9, we've been covering significant issues with Java - both in Safari and in Java applications - caused by the update.

Igetter slow