Can't "find" other computer (running 10.4.11) connected via Firewire

Question

I have a new MacBook Pro running OS 10.6.3 and tried to connect it via Firewire to our Mac Mini running OS 10.4.11, but it isn't working. I used to make a firewire network between the Mini and our PB G4 (both were running OS 10.4.11) all the time to transfer files back and forth. Now with the MacBook Pro running Snow Leopard, I cannot get the MB Pro to "recognize" or "find" the Mini. The Mini is able to "mount" chosen volumes from the MacBook Pro, so it seems to work in that direction. (Although I have an issue with the Mini's permissions but that's a different issue.)
What I did:
Two computers connected via FireWire cord.
On the MB Pro (10.6.3), I went to System Preferences -> Network, clicked the padlock icon, entered my password, clicked the + button, from the pop-up menu, chose "FireWire" then clicked "Create."
Then I'm supposed to repeat those steps on the Mini, but OS 10.4.11 doesn't have the same set up. As I remember it, though, I went to the Mini's System Preferences, Network, Network Port Configurations FireWire is check marked "on" and at the top of the list. I go to a finder window sidebar, look at "network" area and find the MacBook Pro and click connect, and follow the instructions.
Mini connects and "sees" the MB Pro.
MB Pro is set up, but doesn't "see" the Mini.
What do I do?
Please note, the MB Pro has only Firewire 800, not 400, so I have an Adapter which plugs into the Firewire 800 port on the MB Pro, then plugs into the Firewire 400 cord, which is connected to the Mini. Could this be an issue or factor? Seems it wouldn't be since the Mini is able to "find" the MB Pro.

Answer 1

What am I missing?
As far as I know, the installing software still checks the "Library > Receipts" folder to read a history of which package updates have been installed rather than searching to see if the actual app is installed. Have you deleted the receipt ".pkg" files equal to or newer than the one you currently wish to install. However, remember this approach assumes that any "patches" applied in the ordinary upgrade process will not create a conflict within the embedded QT structure when reinstalling an older version--which may or may not be true here. (I.e., QT is no longer an independent application or software package but rather an integrated part of the operating system.) The safest approach is to re-install an older version of the entire OS and upgrade the system as it was meant to be updated to the level at which you wish to operate.