In article <[EMAIL PROTECTED]>, DeMoN LaG <n@a> wrote:
> If he is unable to run Netscape 4.x and Mozilla/Netscape 6 concurrently > because he uses a Mac, I consider that a flaw in how the Mac handles > it's running processes. Not a flaw in Mozilla. Haven't we discussed this before? * Mac OS does not prevent running two apps with the same creator code at the same time. * Mozilla and Netscape Communicator 4.x can be run at the same time. * Mozilla and Netscape 6.2 can't be run at the same time. This is not due to Mac OS. The second instance itself refuses to run if it finds another version already running. This has been implemented in order to avoid cache corruption. * Netscape 6.2 and Netscape Communicator 4.x can be run at the same if Netscape Communicator 4.x is launched first * If Netscape 6.2 is already running, Netscape Communicator 4.x can't be launched. This happens because Netscape Communicator 4.x thinks it would cause profile corruption, even though that wouldn't be the case. * Netscape 6.2 and Netscape Communicator 4.x can coexist on the same hard disk. It does not affect the ability of either app to run. However, the behavior of file associations becomes unreliable. This can be worked around by using drag&drop for opening files (instead of double-clicking). * The file association problem can be fixed by hiding Netscape Communicator away on a disk image. If Netscape Communicator 4.x is ever needed again (eg. for testing a web site against its bugs), the disk image can be mounted quite swiftly. Case closed? -- Henri Sivonen [EMAIL PROTECTED] http://www.clinet.fi/~henris/
