Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Set up the Minolta 2300DL printer on OS X Install
Start by downloading the SDK from Zenographics site (you will need to register with them to download the SDK). The file you're interested in is called SDKColor.dmg. I had some trouble downloading this file with Safari on 10.2 (it supposedly works in 10.3), but it worked fine in Mozilla.

Read the rest of the hint for the how-to...
read more (328 words)   Post a comment  •  Comments (22)  
  • Currently 2.40 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[38,096 views]  View Printable Version
Install dual-boot OpenBSD 3.5 / OS X on early Macs Install
After a dozen re-installations of OpenBSD 3.5 on my old iMac, I finally figured out how to make it boot into the finished installation. The problem was that I had created a 15GB partition that was not completely contained within the upper 8GB of the hard drive (no kidding ... couldn't fit that 15GB into an 8GB space -- who would have thought??), and the 333MHz iMacs cannot boot anything past that 8GB mark.

I thought it would work because I had sub-partitioned that 15GB under the OpenBSD installer so that the first OpenBSD partition was well within that limit, but it didn't work. The trick is that the entire partition as seen by Disk Utility on OS X must reside in that 8GB playground. What I had to do was create two "Free Space" partitions as placeholders in OS X, the first of which fit entirely into the 8GB limit, and a second which was as big as I liked into the lower part of the drive. Then under OpenBSD, I further partitioned that first placeholder into the / and swap partitions, and the second placedholder into the /usr, /tmp and /home partitions.

The last catch was that I could not get it to boot off the hard drive by copying the file ofwboot to the first HFS partition as described in the documentation, so I left the OpenBSD installation CD in the drive and used the Open Firmware command boot cd:,ofwboot /bsd to get it all going.
  Post a comment  •  Comments (2)  
  • Currently 2.17 / 5
  You rated: 4 / 5 (6 votes cast)
 
[8,406 views]  View Printable Version
Skip a disk swap during installation Install
A typical installation of 10.3 requires me to change discs during the middle of the install. One day while messing around with partitions, I noticed my Firewire DVD drive is visible in Disk Utility ... and during the install my external drive popped open when the second disc was needed.

So, in a nutshell ... I know if you have the LaCie Porsche designed external DVD-RW, you can put the second disc in it before you start, and then install OS X without interruption. This probably works with other external drives as well...
  Post a comment  •  Comments (3)  
  • Currently 1.80 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[6,258 views]  View Printable Version
Extract the Apple Remote Desktop 2.0 client installer Install
Apple Remote Desktop 2.0, just now shipping, is significantly slicker and more powerful than earlier versions, but with great power comes inconvenient installation issues: the admin requires that clients be updated to 2.0 as well, which can be done remotely from the admin console. However, Apple hasn't yet provided a downloadable ARD 2 client installer -- and if you're planning to install the client on a machine image or other locale, it would be nice to have one...

The contextual menu "Show Package Contents" comes to the rescue, as usual. The actual "Remote Desktop Client200.mpkg" client installer lives inside the Remote Desktop application package at /Contents -> Resources -> Installers; just control-click on the application and Show Package Contents, then navigate to the folder and option-drag the client installer to the desktop.
  Post a comment  •  Comments (7)  
  • Currently 2.00 / 5
  You rated: 3 / 5 (7 votes cast)
 
[9,723 views]  View Printable Version
Force installation of Java 1.4.2 Install
Installing Java 1.4.2 would not work, and complained that I needed to install Java 1.4.1 first. Well, I had installed 1.4.1 and I tried a bunch of the solutions floating around (re-installing Apple's java.pkg, and several on this site) and nothing worked.

This is the trick that helped me install Java 1.4.2 with no errors from software update. I searched for and wide for this information so I thought I'd share it; it's adapted from a versiontracker comment.

Apple's Solution to 1.4.2 update over 1.4.1 problem ... AppleCare's advice is to find the directory QuickTimeJavaUpdate.pkg in /Library/Receipts/ and delete it. Java 1.4.2 will now update. It worked for me on two computers that suffered from this bug.
  Post a comment  •  Comments (8)  
  • Currently 2.33 / 5
  You rated: 3 / 5 (6 votes cast)
 
[12,674 views]  View Printable Version
A real workaround for the 8GB limit on older Macs Install
I've worked out a work-around for the 8GB limit for system volumes on older Macintoshes. I'm writing this on a Beige G3 with a 27G system partition, and I'm confident that it won't be rendered unbootable by system updates or disk activity (the reason for the 8GB limit in the first place). Most of the credit goes to Ryan Remple and his XPostFacto tool for installing OS X on older, unsupported Macs -- the 'trick' relies on using XPF's 'Helper Disk' feature. I haven't tried it, but I think it should also work on Macintoshes that are affected by the 8GB limitation but wouldn't otherwise need XPostFacto.

XPostFacto's Helper Disk was designed to make it possible to boot older Macs from Firewire drives; it works by making a minimal copy of the System files (technically: a bootloader, the kernel, and some extensions) to a disk partition your Mac could normally boot from -- this is the helper disk -- but pointing this minimal system at the (otherwise unsupported) 'real' system volume. The minimal system includes the OS X disk drivers, so once it's been started off the helper disk, it can fully use any disk OS X supports to finish starting up -- including the parts of drives over 8GB. This might sound familiar to Linux users -- it's the same idea as the /boot partition Linux distributions use to get around the 1024 cylinder limit on older PCs.

There's one major snag: The OS X installer enforces the 8GB limitation, so you can't normally install OS X to a large partition. This can be worked around by backing up a supported install, repartitioning, and restoring to the new large partition. It's a pain, but it works. The biggest problem is finding somewhere to put the backed-up system while repartitioning.

[robg adds: Please read the entire hint, including the issues section at the end, before you decide to try this with your older Mac. There are some constraints that you'll want to consider before you dive into this project.]
read more (694 words)   Post a comment  •  Comments (4)  
  • Currently 1.60 / 5
  You rated: 2 / 5 (5 votes cast)
 
[12,691 views]  View Printable Version
Make the Dane-Elec Combo card reader work in 10.3 Install
If anybody is having problems getting their Dane - Elec Compact Flash/Smart Media combo card reader to be recognised in Panther, it's because it needs the drivers from the manufacturer of the chipset of the reader itself, not the ones bundled in the box. The drivers can be found here on SCM's website.
  Post a comment  •  Comments (0)  
  • Currently 1.40 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[6,609 views]  View Printable Version
Auto create users during installation Install
Ever have to set up a lab of computers, and then had to manually add users to each system using the Setup Assistant? Want to bypass that? Well, here's how. On each computer, create a file in /var/db named .InstallerConfiguration. It should be in this form:
<?xml version="1.0" encoding="UTF-8"?>
<!-- Next two lines should be one with a space between... -->
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
 "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>Users</key>
 <array>
  <dict>
   <!-- This is optional. If it's not set, they aren't admin --!>
   <key>admin</key>
   <true/>     <!--can be false for a regular user. --!>
   <key>fullName</key>
   <!--Any name, is the "Full Name" in the Accounts field. --!>
   <string>Steve Jobs</string>
   <key>password</key>
   <string>set_user_password</string>
   <key>shortName</key>
   <string>steve</string>
   <!--Path to the user's image. This is optional. --!>
   <key>picturePath</key>
   <string>/Library/User Pictures/Fun/Orange.tif</string>
   <key>uid</key> <!-- User's UID. This is optional.--!>
  </dict>
 </array>
</dict>
</plist>
Each user is one <dict> entry, so you can do multiple users with one file. After creating the file, just run the normal OS X installer. When it reaches the Setup Assistant stage, it should just see and read from the .InstallerConfiguration file instead of asking for the user setup information.

I think that 10.3 deletes the file after it's done being used, but I'm not sure if 10.2 does. Either way, be careful to delete this file if you use this method of creating users...
  Post a comment  •  Comments (3)  
  • Currently 1.60 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (5 votes cast)
 
[6,079 views]  View Printable Version
Create a new 'safety' user prior to upgrades Install
In view of the hassles I dealt with relative to this previous problem, I strongly suggest that, before any new upgrade, you create a new, uncustomized user account, possibly with admin privileges, especially if you run a system with only one account (this means you, laptop users). This way, if you have problems after the upgrade:

If you log in with the uncustomized account, and everything works, then you know it's not a system problem. You can then (a) ssh to the same system (via ssh localhost) but log in as yourself, and see if you can connect; if you can, this proves that the basic unix functionality of your account is OK; (b) if you can't ssh over, at least you can sudo over to your account, and maybe move some of your customization files out of the way (say $HOME -> Library -> Preferences -> loginwindow.plist or your dotfiles, if you've customized them); and (c) the fact that you can log in to an uncustomized account means that most likely the system upgrade went OK, and one of your customizations (startup apps, preference files, etc) is potentially a culprit. Even if you don't know what you're looking for, you can at least get a knowledgeable friend in the same room with the system to check things out.

If you do see the same problems with the uncustomized account as with your own account, then you know that the problem's with the system upgrade, and maybe you should restore your backup, try upgrading in a different way, verify/repair disk/permissions, or perhaps a wipe and reinstall (and run hardware diagnostics while you're at it).

This bit me hard during the Panther upgrade (which is working great for me now, though). Since the bulk of the customizations to a system will be in an individual user's home directory (per the UNIX model), an uncustomized account will help identify problems you discover during an upgrade a lot faster, hopefully in a matter of hours rather than days. You can always remove the account after the upgrade if you're worried about it being a security issue.

I recommend this for anyone upgrading Mac OS X, from a 10.n to a 10.n+1 release (or even 10.n.m to 10.n.m+1 release, if you're paranoid enough).

  Post a comment  •  Comments (5)  
  • Currently 1.67 / 5
  You rated: 1 / 5 (6 votes cast)
 
[6,775 views]  View Printable Version
Steps for installing an unsupported printer Install
I was looking for an install guide for printers on OS X 10.3, I found a guide by Clint Morgan describing installation of the foo2zjs driver. First I had some problems following his steps so I want to describe what helped me installing my Minolta Magicolor 2300DL printer.
  1. Apple Developer Tools (Jaguar) or Xcode (Panther) - Apple's Developer Site for more information. Can be found on the software-restore-cd

  2. gettext-0.13.0 - required by glib. If you get an error (as I did) that you dont have a C# compiler, use following: ./configure --disable-csharp

  3. pkg-config-0.15 - required by glib

  4. glib-2.2.3 - required by ghostscript

  5. ghostscript-7.07 - required by foo2zjs. jpeg library required: decompress, rename folder to "jpeg" and copy to top folder of ghostscript

  6. ghostscript-font-6.0 - required by ghostscript. NOTE: The fonts are distributed as a separate package and are NOT included with ghostscript itself. Copy files to /usr -> [local/ -> ] share -> ghostscript -> fonts

  7. wget-1.9 - required by foo2zjs. This utility is required by the foo2zjs build process at the time of this writing. It is also used by another foo2zjs utility (getweb) to download ICM color profiles.

  8. foomatic-filters-3.0.0 - required by foo2zjs. Use following command for installation:
    sudo make install CUPS=/usr/libexec/cups CUPS_FILTERS=/usr/libexec/cups/filter
    
  9. foo2zjs.
Setting up the printer works with the CUPS web interface, URL is http://localhost:631. For more information, see foo2zjs.rkkda.com/ ... or download foo2zjs.tar.gz from them, and read INSTALL.osx in foo2zjs package.

[robg adds: I haven't tested this one.]
  Post a comment  •  Comments (8)  
  • Currently 2.67 / 5
  You rated: 3 / 5 (3 votes cast)
 
[15,697 views]  View Printable Version