<$BlogRSDURL$>
Apple Mac OS X FAQ
Monday, September 22, 2003
 
NetBoot and Network Install images can be created with DVD source discs when using Mac OS X 10.2.4 or later.
NetBoot and Network Install images can be created with DVD source discs when using Mac OS X 10.2.4 or later. If you are creating an image on a client computer, be sure to copy the updated version of Network Image Utility from the server to the client computer.

When imaging DVD discs, Network Image Utility asks if you want to continue the imaging process with a second disk. Click Cancel when prompted for the second disk.

Important: If you click Continue when asked about the second disk, you must force quit Network Image Utility by pressing Command-Option-Escape. After a force quit, the imaging process is not complete. You should start over with a new image.
 
Common Unix Printing Services (CUPS)
In Mac OS 10.2, the Common Unix Printing Services (CUPS), has a web browser interface with some very interesting features.

You can see it by using the URL
 
There was a little-known secret she always recommends to users PRIOR to attempting to zap their PRAM.
There was a little-known secret she always recommends to users PRIOR to attempting to zap their PRAM.

What is this magical technique? Resetting the Open Firmware. It's kind of like zapping the PRAM but different. To do it, shut down your Mac, then press Command-Option-O-F as you start it back up. You can release the keys when you see a white screen that says "Welcome to Open Firmware." At the Open Firmware prompt, type "reset-all" (without the quotation marks, of course) and then press Return or Enter.

To exit Open Firmware, type "bye" or "mac-boot" (no quotes).

While doing some research on this technique, I found an Apple Tech Note with another Open Firmware command that could come in handy someday. If you type "eject cd" (no quotes; followed by Return or Enter) at the Open Firmware prompt, your Mac will often spit out a recalcitrant CD that won't come outany other way.
 
Sharing an iTunes library between multiple users on the same machine.
Sharing an iTunes library between multiple users on the same machine.

I'm encoding my entire CD collection so that my wife and I can fully utilize our iPod. However, with multiple users in OSX, iTunes naturally will create a separate library for each user. Not great when we're both adding new files regularly and need access to the most current roster of available MP3s. It's pretty simple use of aliases to solve the problem:
Logged in as either user, move the iTunes folder from the Documents folder into the Shared user folder.
Delete the same Documents/iTunes folder from each individual user.
Create an alias of this iTunes folder on Shared (remove the word 'alias').
Copy that back to each user's Documents folder so each user has an alias to the Shared/iTunes folder.
Your MP3 files should also be placed in the Shared folder. When you move them, you'll also need to "reset" the index of files in iTunes. Since you've set up everyone to work off ONE library, though, you only need to do it once.
 
If you want to join a non-Apple encrypted wireless network from a computer with an AirPort card
If you want to join a non-Apple encrypted wireless network from a computer with an AirPort card, you must use one of two different styles for password entry; and it must be the one chosen by the network administrator. They are:
1. ASCII password
If you were given a password that may be plain language, containing characters from the full range of ASCII, use the double quotation mark (") before and after the password. These are case-sensitive, and they are five characters long for 40-bit encrypted networks or 13 characters long for 128-bit encrypted networks.

Example of 40-bit: "pw123"
Example of 128-bit: "password12345"

2. Hexadecimal password
If you were given a password that uses only the hexadecimal range of characters (which are: abcdef0123456789), put a dollar sign ($) before the password. These passwords are 10 characters long for 40-bit encrypted networks or 26 characters long for 128-bit encrypted networks. In a hexadecimal password, the dollar sign is called the Hex Escape. It notifies the software that the characters that follow it should be treated as a hexadecimal number. Other possible hex escapes are "0x" and "0X" (zero-x, and the "x" may be upper or lower case).

Example of 40-bit: $1234abcdef
Example of 128-bit: $12345678901234567890abcdef
 
To get iChat AV to work behind firewalls and some broadand routers you need to do one of the following:
To get iChat AV to work behind firewalls and some broadand routers you need to do one of the following:

1. Put the desired computer in a dmz and allow all traffic.

or

2. Open the following ports and do some port forwarding.

UDP port 188 For Voice over IP
UDP port 332 (Have not figured out why yet)
UDP port 5060 For Voice over IP
UDP port 5298 For Rendezvous (Necessary for iChat AV)
UDP port 5678 For Remote Replication Agent Connection (Have not figured out why yet)
UDP ports in this range: 16384 to 16403 (Necessary for iChat AV)
 
Here is an explanation and outline on how to backup the netinfo database
A few of you have asked me to outline this.. So here you go

Here is an explanation and outline on how to backup the netinfo
database. this should not only include user work stations but servers
as well.

THIS IS ONLY FOR THE LOCAL NETINFO DB. IF YOU HAVE A SHARED DOMAIN, REPEAT FOR IT AS WELL

1. launch terminal
2. at the prompt, type the following (all on one line, preserving all
spaces as indicated; case is important in terminal, so make sure you
copy case correctly);

cd /private/var/db/netinfo
sudo cp -R local.nidb local.nidb.backup

3. when you are prompted for a password, type your normal account
password (you must be an admin user, or course).

the cp command copies the database local.nidb to a new file in the same
directory called local.nidb.backup; since the database is actually a
directory of files, the -R option tells cp to copy the directory and
all files within it. the sudo command-which asked for your
password-provides you with the temporary root access needed to be able
to write a new file to that directory.

when making multiple backups and you don't back up to a new,
differently named, copy each time, make sure you delete the previous
backup copy before backing up again; you can do so using the following
command in terminal:

sudo rm -R /var/db/netinfo/local.nidb.backup

to restore the backup netinfo database you have to boot in as single
user mode.

1. hold down command+S key during startup

2. at the localhost# prompt. use fsck to enure that your drives are in
good shape:

/sbin/fsck -y

if you received a message that your file system was modified, run fsck
again, as many times as is necessary to get the message that your disk
is OK.

3. to mount the boot disk so that you can access the files on it, type
the following (note the space between uw and /):

/sbin/mount -uw /

4. type the following commands:

cd /var/db/netinfo
mv local.nidb local.nidb.deleted
rm /private/var/db/ .AppleSetupDone
reboot

the first command changes the name of the corrupt netinfo database to
local.nidb.deleted (so that OS X won't use it when you reboot). you
could have deleted it using a different command in terminal, but by
renaming it you'll still have a copy in case it turns out the problem
wasn't a corrupted netinfo database. the second command deletes a file
the operating system uses to keep track of whether or not you ran the
initial account setup process. once you delete that file. mac OS X
thinks that you need to set up your initial account again, and will
launch the setup assistant the next time you book into OS X.

5. when your computer roboots, the setup assistant will ask you to set
up a "first" user account. Be sure to provide the exact same short
username you used for your original admin account (the one you
generally use that has administrator privileges). this will cause mac
OS X to match your "new" account up with your existing user folder and
all corresponding permissions. you may also need to go into the users
pane of system preferences and re-create any other users you previously
created. again be sure to use the exact same short usernames the
original accounts used.
 
Wouldn't it be great to clean off a server and get back to an original state within a couple of minutes?
Wouldn't it be great to clean off a server and get back to an original state within a couple of minutes? Wouldn't it also be great if you didn't have to run all of those HUGE updates again that take so much time? I utilized this and was up and running again in a matter of 5 minutes with servers running 10.2.6.

Reboot a server and hold down Command-S.
You will boot to the Command Line Interface (CLI).
Type the following. Each line should be followed by the hitting the Enter key so that the commands execute.

mount -uw /
rm /var/db/.AppleSetupDone
rm -r /var/db/netinfo/
rm -r /var/db/authserver/ (if you were using Password Server)
rm -r /Users/*
reboot

You'll be run through the Setup Assistant and Open Directory Assistant as if it were a clean install. Note, you'll lose any user data so only use all the steps on a test system you don't care about.
 
PDF workflow button is hidden by default
"The PDF workflow button is hidden by default. The button is enabled
if the system detects the existence of either the /Library/PDF/Services or the ~/Library/PDF Services directory."

I *never* managed to make the button appear if the folder does existonly in the global /Library/ folder. However, once I created it in ~/Library/, it worked perfectly, and elements added in any of the "PDF Services" folders appear in the menu.

Otherwise, it is a really nifty feature. Too bad Apple does not make any emphasis of it.
And a nice trick : you can also add folders on AFP servers, then the volumes will be automatically mounted if they were not :-)
 
Booting into Open Firmware
Booting into Open Firmware (command-option-o-f),
then at the prompt,
type "reset-nvram", hit Enter,
then again at the prompt,
type
"reset-all", and hit Enter again.
(no quotes surrounding the commands).
 
Update on occasional damage to files when quitting FileMaker Server 5.5 on Mac OS X or Mac OS X Server
Update on occasional damage to files when quitting FileMaker Server 5.5
on Mac OS X or Mac OS X Server

PROBLEM DESCRIPTION: Intermittently, some customers using FileMaker Server
on Mac OS X or Mac OS X Server may see this entry in their FM Server log:

"File "filename.fp5" close error: database may be damaged; try opening it
in FileMaker Pro. (10001) "

We believe that an error may occur during a compression process that is run
when files are closed. In this case, the files may compete for cache space
to do their compression work.

This error occurs intermittently because it depends on several factors: how
much free space in each file needs to be compressed [e.g., many record
deletions intermingled with additions], how much cache space is available,
and how quickly the computer can process the compression.

RECOVERY AND PREVENTION: If you see this, you must first open all files with
FileMaker Pro before they can be hosted by FileMaker Server again.

To prevent this error occurring, please close one file at a time before
quitting FileMaker Server.

At this time, FileMaker has not received reports of data-loss in this
specific situation. Other reports of data loss appear to be unrelated to
this issue.

NEXT STEPS: We are currently testing a fix for the above problem and intend
to begin an external testing program in the next few weeks. If you have
experienced this problem and are interested in taking part in an external
testing program, or if you suspect that you have encountered this issue,
please report it via http://www.filemaker.com/company/product_problems.html

FURTHER INFORMATION:

Please see the updated TechInfo Knowledge Base article at
http://www.filemaker.com/ti/108428.html
 
Macs to network via Firewire
Hello all. The question has come up about the ability for Macs to network via Firewire.
Things to know:

Q. Is it possible?
A. Yes

Q. What do I need?
A. Minimally 10.2.6, Firewire ports, Understanding of IP.

Q. What are the limitations.
A. Firewire can only go 14 feet without a repeater. The further you go can cause speed degradation. 6 Physical layer device connections 400 Mb/sec. Transfer rate (50 MB/sec.) Maximum 63 device connections.

Q. What are my other options.
A. A firewire repeater and a firewire hub.

Powered by Blogger