how to get rid of virus

I have no problem with my fonts using OS 10.5, they are all available just as the were with 10.4.

Then you must not be using any fonts which conflict with those installed by OS X. Which means you wouldn't in Snow Leopard, either.

I know that it wasn't very ethical of Apple to change their system fonts,

They've actually conflicted all the way back to when Apple first introduced their version of Helvetica before OS 9. It didn't matter then though since Apple wasn't using their version in any application design. You just threw it out and used your Type 1 versions.

they advised me that it was up to Quark and other application makers to make the changes.

Piffle! Apple created the problem by giving their fonts the same internal names. When they created the new .dfont versions for OS X, that was the time to give them proper non conflicting names. Just what the heck is Adobe, Quark, or any other vendor supposed to do about it? The conflicting internal font names is the problem, not any application.

Here's the issue. A press/prepress shop has hundreds, likely thousands of documents built over the years using Type 1 versions of Helvetica. You can't just let them use the Apple versions since the leading, baseline shift, kerning and other metrics are different. All of your carefully placed type (like on zillions of Nutrition Facts boxes on food product packaging) will move. You have to use the font you originally built the document with to maintain type position. It's either that, or spend literally thousands of hours rebuilding them to use Apple's fonts, which are NOT PostScript fonts. Guess what every shop does? They ditch the Apple supplied fonts so they can use the ones the documents were built with.

Nothing like passing the buck to say it's up to Quark and others to "fix" it. Sheesh!

Kurt, I recall when 10.6 was introduced I bought the upgrade and loaded it. I immediately was not able to use most of Helvetica Neue fonts, Helvetica Light and ITC Garamond light and some others. About 1/2 of the Helvetica Neue and all the ITC Garamond fonts were grayed out in Quark and CS2.

Oh, I don't doubt that at all. Snow Leopard is basically an entire rewrite of the OS to 64 bit. As part of that, it was no longer possible to patch the old type engine. So a "from scratch" rewrite was required. There was a lot wrong with all types of fonts at the start. It took until 10.6.3 for Snow Leopard to really become useful for desktop publishing. 10.6.4 cleaned up the last of the more obnoxious type bugs. There are still a couple of obscure ones, but for the most part, the growing pains of SL are behind us.

I tried your suggestion, but other problems arose, don't remember just what, but I think it was something to do with not being to see certain things in the Apple Helvetica.

In order to use your Type 1 fonts, but still get back to the Apple versions, it takes a bit of monkeying around to set up your system to switch between them easily. It's not all that hard, but more than most folks are comfortable doing since you have to relocate "required" fonts out of the System folder.

At the time Quark was working on the re running of text built with the earlier OS, that was eventually fixed and I found out about it on the Quark discussion forum. They never did anything about the font conflicts that I reported. Quark sent me to Apple and Apple sent me back to Quark. I wasn't knowledgeable to argue with either so i just went back to OS 10.5.

Yes, that was a rather long battle of finger pointing. Quark blamed Apple, Apple said Quark needed to fix the problem with the strange leading issue with many Type 1 fonts. Well, how could it be Quark's fault when what changed was the OS, and not XPress? Everything worked just fine in 10.5.x and earlier. Then with the 10.6.3 update, the leading issue basically disappeared. From other reports I read, Apple and Quark were working together rather tightly to find the issue. In the end, Apple fixed it.

At first, I ran Snow Leopard on a separate partition with all of my apps installed, strictly as a test bed. There was so much that needed to be fixed at first that I continued doing all of my real work in Leopard and just kept an eye on the progress in Snow Leopard. That, and slowly upgrading software to be SL compatible. At 10.6.3, I finally switched over and have been working in SL completely since then.

Why would I want to go back to the Apple versions, is it important that I do?

It's not important at all, just aesthetics. The only reason to have the Apple versions on the drive is so the Apple supplied apps which use Helvetica display as intended. Because of the differences in metrics, using a Type 1 version of Helvetica will cause the text in those Apple apps which use Helvetica to display oddly. Type off center in a column, too wide, etc. Doesn't hurt a thing, just looks. The only trouble you could create would be to have no version of Helvetica active. Then the apps which need them may display very badly, or not launch at all.

I tossed all of Apple's Helvetica fonts from my system and have Type 1 fonts in their place, within the /Library/Fonts/ folder. I also use almost none of the apps where Apple incorporated their versions of Helvetica into the design, so it makes no visible difference to me.

Why can't I just stay with the Type 1 fonts?
To replace my most used fonts would cost about $2,000.00.

You can stay with them if you like. As mentioned, it's just a display issue with the Apple supplied apps to use a different version. I have to have the Type 1 versions active for the numerous documents built over the years which depend on them for correct spacing and such. So the Apple versions of Helvetica will never be on my Macs if I can help it. I do have Apple's version set aside and can activate them if I want to, I've just never had any real need to do so.

I would be willing to try again if you can again give me step by step instructions, unless it requires going back to the Apple versions.

It's all in my article, Font Management in OS X, but the kind of short version for Snow Leopard is:

1) In the /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/
ATS.framework/Versions/A/Resources/ProtectedFonts/ folder, copy these fonts to another location:

Helvetica.dfont
HelveticaNeue.ttc
HelveticaLight.ttf

Then delete them (the originals, not the copies you just made).

2) In the /System/Library/Fonts/ folder, delete the same three fonts. Restart the Mac.

3) Apple's versions of Helvetica which conflict with Type 1 versions are now out of the way. Create a set in your font manager for your Type 1 versions, and a separate set for the Apple versions you set aside in another folder. If you're using Font Book, make sure to use a Library Set so they don't get copied into your user account Fonts folder, or the /Library/Fonts/ folder, whichever is the one chosen in Font Book's preferences.

4) Now you can just choose which Helvetica fonts to activate with your font manager. Not both at once of course, or you're just creating the conflict again. Whichever set you want on, turn the other one off.

One problem that I may have is if it didn't work and I wanted to restore my 10.5 from my backup drive.

Then make a complete backup first so you can get back to it.

If I do a reverse backup from my backup drive it would bring back a lot of archived data which no longer resides on my main HD.

Then make a fresh backup of the drive to an empty partition as it is right now before installing Snow Leopard. Then if things don't go as you hope, just boot to that Leopard backup and copy it back with Carbon Copy Cloner. You'll be right back where you were.

If I do a reverse backup from my backup drive it would bring back a lot of archived data which no longer resides on my main HD.

Then your backup is greatly out of date if you don't want old info in it coming back. Hence the suggestion to create a new backup of your main drive as it is now before installing SL.

Almost impossible to tell what the archived documents are without matching item by item.

You shouldn't need to know that. Earlier versions of CCC couldn't clone a drive the way SuperDuper! does by adding or removing files during an update to the clone to have it always match the source. Depending on how you set the options, it does now. Has been able to for a while.

I may receive some form of compensation, financial or otherwise, from my recommendation or link.