Have you tried burning from another admin account, or even as root? If it works, it's something in your original account's Library folder (~/Library). If it doesn't work as root, then it's something in the system. That's all I have for ya.
I hear the logic there, but the thing is, even if I rename the drive, the other firewire drive will be mounted before the rename, thus it will have the "1" tagged after it. Besides, I can't rename the drive because that negates alot of management tasks that I currently have in place. You would...
The thing is with a login script is that the alias to the drive is created before login, so any subsequent firewire drive would still have the "1" after it (assuming its connected during the boot process).
Does anyone have any idea why Panther is putting an alias to the hard drive in /Volumes? Here's the thing, in Jaguar, the /Volumes folder only contained volumes other than the boot drive. Now, Panther tosses an alias for the boot drive in there.
If I drag the hard drive onto a terminal...