Cool Mac Gear• iPod Video • iPod nano • iPod 1G-2G • iPod 3G • iPod 4G • iPod Mini • PowerBook-iBook • Garageband |
One of the major differences between OS X and the Classic Mac OS is how these operating systems respectively handle multitasking. Mac users have actually had multitasking since System 6 "Multifinder" back in the 80s, which simply means that one or more application(s) can be processing data in the background while you continue to work with another application in the foreground, that you can keep two or several applications open simultaneously, and can switch among open applications at will. However, the Classic Mac OS has cooperative multitasking, in which individual applications request and yield use of the processor cooperatively, but priority is given to the frontmost application, so the applications running in the background tend to slow to a crawl, which is still a lot better than nomultitasking at all by a long shot, but not ideal. Mac OS X, on the other hand, features protected multitasking, in which the operating system constantly monitors and allocates processor power to the various running applications as needed, balancing and sharing supply and demand, so to speak. This is a much more efficient method of handling multiple applications, then one of the most dramatic advantages of Mac OS X over the legacy Mac OS. Happily, when you run non-carbon legacy applications in the Classic environment under OS X, they benefit from preemptive multitasking as well, since Classic Mode runs as an application thread in OS X, and while they will still rely on cooperative multitasking when in Classic mode, a crash will not bring the entire system down. Preemptive multitasking gets addictive pretty quickly, and it is a great feeling to be able to send an application performing a process into the background knowing that it will run and more than a snail's pace. OS X Mail Eudora Mailbox Cleaner 1.0 Utility For Importing Mailboxes Into Mail.app RE: ViaVoice X mic issues Fans of this OS X Odyssey series will be happy to learn that Odyssey now has its very own domain page here on Applelinks, where you can find the entire series archived for reference.
You can check it out at:
From David Chilstrom Regarding "manifold reports of bugginess in the Mail app", as reported in "OS X Odyssey 31", I've been using it since the Public beta with nary a word lost. Mind you, Mail was no poster child for application stability in the earlier days of OS X, but I haven't had a single Mail crash since running it under OS X.1 in constant daily use. In search of evidence for Mail issues beyond my own fortunate experience, I searched that ultimate site of "manifold reports of bugginess", Macintouch, for OS X Mail issues and came up with surprisingly little. I'd be curious to know where I can read these "reports" to clue in on the agonies to which I am so blissfully unaware. Indeed, as Mail is standard on every OS X installation, and at least tried by most users, I'm rather amazed not to see a litany of complaints about it. Mail uses (as does Eudora) the widely used mbox format to store mail. Rather than storing all messages in a central database or creating individual files for each message, the mbox file format stores all messages for any particular folder in a single text file. Mail messages are stored in your home folder->Library->Mail->Mailboxes. OmniWeb will open the package for each folder and read the enclosed mbox file or you can control click on any of your mailboxes and see the files listed below:
Info.plist
For packing a lot of power in a clean and simple interface, Mail is pretty hard to beat. David Chilstrom
Hi David;
There have been reports of Mail bugginess and at least one obout data loss posted in this column, although I can't recall off the top of my head which editions. I've also seen them elsewhere on forums, but didn't record links. In fairness, I think most of these gripes were aimed at the early versions of Mail. It's got to be better than Outlook Express and Entourage. ;-)
Your report is encouraging. My son has used Mail exclusively since the final release of OS X came out, and likes it a lot.
For me, the non-backward compatibility with OS 9 makes Mail a non-starter, at least for the foreseeable future.
However I must check out whether it's possible to convert Mail mbox mailbox files to Eudora mailboxes and vice-versa by changing the File Type and Creator Code info using ResEdit. This workd for some non-Eudora mbox files. Just drag a mailbox to ResEdit and when the window opens, select "Get Info For --" from the File Menu. That will bring up a dialog box with the File Type and Creator Codes, which you can switch from whatever they are to Eudora's TEXT and CSOm codes respectively. If this works, as it does with, say, mailboxes from the Green email client, it should convert a Mail mailbox into a Eudora mailbox (or vice-versa)
Charles Eudora Mailbox Cleaner 1.0 Utility For Importing Mailboxes Into Mail.app While we're talking about the Mail app., Andreas Amann notes that:
The result is Eudora Mailbox Cleaner, a simple drag'n'drop application which prepares Eudora mailboxes for proper importing into Mail.app. So far, the following functionality has been implemented: All of these features have only been tested importing mailboxes from Eudora 5.1 (OS X, b18) to Mail.app in OS X 10.1.2. Your mileage may vary for different versions... The program has not been optimized for speed, but since you'll only have to import your mail once that should not pose too much of a problem (it cleaned up my several 1,000 messages - just over 10MB in size - nicely in about 5 minutes).
Tips:
System requirements:
For more information, visit:
From David Ulrich Charles, That's great. But then you have the further addendum in which someone who appears to be seeking a job at IBM points the finger at the Mac again saying it was *some* configurations -- which may be true -- but says that there is nothing in ViaVoice to disable analog mic input in ViaVoice to which I say, "No, no, no!" If that is true, how is it then that with my analog mic setup (that **I open ViaVoice with Apple's Speech Recognition**) can been seen pulsing away mic activity away in the Speakble items interface as ViaVoice Setup leaps up to tell me that I have no microphone at all. There is not even the briefest pause as it waits for a response or searches for a mic. Immediately it leaps forward saying no mic at all, when I've been using Macs speakable items all day -- even to open ViaVoice setup! I'm suspicious. Dave
Hi Dave;
Just trying to cover all the possible angles evenhandedly. I suspect that the difficulties with analog sound support are in both ViaVoice and the Mac OS.
Charles
Note: Letters to Moore's Mailbag may or may not be published at the editor's discretion. Correspondents' email addresses will NOT be published unless the correspondent specifically requests publication. Letters may be edited for length and/or context. Opinions expressed in postings to Moore's MailBag are those of the respective correspondents and not necessarily shared or endorsed by the Editor and/or Applelinks management. If you would prefer that your message not appear in Moore's Mailbag, we would still like to hear from you. Just clearly mark your message "NOT FOR PUBLICATION," and it will not be published. CM
Page: 1 - 2 - 3 - 4 - 5
|
Cool Mac Gear• iPod 1G-2G • iPod 3G • iPod 4G • iPod Mini • PowerBook-iBook • Keyboard Skins • Garageband
| ||||||
|
| ||||||||
