At 3:42 AM +0900 7/25/01, [EMAIL PROTECTED] wrote:
>At the moment I'm switching between OS 9 and OSX via 'STARTUP
>DISK'->'RESTART' due to the fact none of the drivers for 3rd party
>USB periphs (like my ISDN TA modem, the hell I'm going back to 56k)
>have been updated yet, which in turn means I'm generating copious
>quantities of files with dual creators for those apps I use which
>have been ported to OSX. Double clicking them under OSX, causes OS9
>'in emulation' to kick in which then goes into a never ending cycle
>of restart->crash, restart->crash, restart->crash, as it tries to
>load an external HD which is another of those
>3rd-party-not-yet-updated jobs. In short I'm having to manually
>update the OSX finder to use the OSX version app not the OS9
>.<nervous tick='serious'> _And_it's_starting_to_wear_me_down_
></nervous>
>
>I've been over the docs at ADC believing system('some_CFfunction')
>would be the path to take but I'm unable to make sense of how I can
>apply raw carbon code to get perl to do what I want.
>
>anyone got any pointers?
Robin -- I think you know more about this stuff than I do, but I've
been doing all my work under OS X since the Public Beta came out, and
I just wanted to mention something in case this is what you're
frustrated with.
Over several months, my reliance on Classic applications and non-OS
X-updated utilities/device drivers/etc has gradually diminished - yay!
But the consistent reminder that it's not all there yet is what
happens when I double-click docs: if there's a Classic version of an
application (in the Classic environment's boot disk at least), then
double-clicking that app's doc icons will cause the Classic version
of the app to attempt to launch, even if the OS X version of the app
is already running.
So even though OS X BBEdit and I start with coffee and end with
candles, because I keep a Classic version of BBEdit handy, if I
double-click a BBE doc, Classic BBE tries to launch, fails, and my
work routine momentarily stumbles while I remember why I'm clicking
out of error messages instead of looking at my document.
So I've quit double-clicking doc icons, and now instead drag them to
the OS X or Classic app icon on the Dock (which will cause the app to
launch if it isn't already running). Or, of course opening via the
Open/Recent menu commands, etc...
So if this related to what you've been trying to hack around, then a)
you're not alone! and b) maybe for the time being use an interface
other than double-clicking?
Anyway, my sympathies. And, since this appears to be a generalized
behavior under OS X/Classic, if someone does have ideas regarding
system('some_CFfunction') or similar, it might help to get back our
full GUI in several ways, not just your pesky peripherals.
1;
--
- Bruce
__bruce_van_allen__santa_cruz_ca__
