I've made God Knows how many support tickets out to Andy & Co. asking them to look into this. And while I appreciate Andy's taking time out to answer my dilemma via personal e-mail, I met the proverbial brick wall many times over.
In these fora, I've appealed to fellow Mac users only to hear crickets. I've put BTT and other Windows-using Mods in the mortifyingly awkward position of addressing a Mac-centric issue with which they cannot assist me.
I have now deleted the only working G-Force version I have in hopes that this issue would by some 11th hour and 59th minute miracle be wrought. Evidently I was wrong. Short of a complete Lion reinstall (and I don't think my machine can go past OSX10.8 without *major* hiccups), there is no way I can get any SS products to work anymore. I've noticed, though, that my system Installer Icon has mysteriously vanished, yet I can still isntall things...but not any of this company's material.
Why?
Save for the final observation in the paragraph above this one, I'm asking for a cogently articulated reason why everything else in aforesaid paragraph is the case right now. I feel as if a dozen years and change of faithful, albeit ancillary participation in this program's development has been overwhelmed by the incessant, strident demands for instant personal gratification from the Windows users amongst SS clientelle.
I earnestly await some kind of response in any form and thank in advance anyone who can steer me in a direction that will make me Much happier than I am right now.
I remain steadfast in the hope that SoundSpectrum is not the culprit here, but rather anything that can point to the fact that all MacOSX iterations past Lion basically suck left nut.
No One Has Addressed My Missing BOM File Issue.
Moderators: BTT, andy55, b.dwall, juxtiphi
-
JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
No One Has Addressed My Missing BOM File Issue.
"God is syntax."
JayPro, I think Frank addressed this via ticket, but allow me to step in...
We're overloaded here with TODOs to the point where trying to get compatibility with the 3rd party package software you use just isn't possible. As Frank said, if anything you should write the authors of that software. After all, if all versions of OS X are happy with our .dmg then it's kinda messed up that they're not compatible with it.
If it matters, when we switch to XCode 4 in a few months (one of a hundred things that take priority over this issue), we'll be redoing our .dmg build process (although I can't guarantee that it'll be compatibile with that 3rd party software).
Anyway, so let's please not riddle the airwaves with an issue that is *their* incompatibility. If it means that much to you, stop using their software and use OS X's built-in installer like 99.9% of the rest of the OS X world.
We're overloaded here with TODOs to the point where trying to get compatibility with the 3rd party package software you use just isn't possible. As Frank said, if anything you should write the authors of that software. After all, if all versions of OS X are happy with our .dmg then it's kinda messed up that they're not compatible with it.
If it matters, when we switch to XCode 4 in a few months (one of a hundred things that take priority over this issue), we'll be redoing our .dmg build process (although I can't guarantee that it'll be compatibile with that 3rd party software).
Anyway, so let's please not riddle the airwaves with an issue that is *their* incompatibility. If it means that much to you, stop using their software and use OS X's built-in installer like 99.9% of the rest of the OS X world.