Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All the programs I used in XP and Vista tranferred to W7 without any problem. Backward compatibility is Windows main strengths and the main reason why corporations stick to it. Can you imagine them using Macs where support was dropped after just a few years, where upgrading to new Os meant upgrading the software such as CS4 which means the total cost of ownership is even higher than Windows.

lol

You are forgetting that they are not being "forced" to upgrade. Leopard was working fine in their business model this morning, why would it not be working correctly this afternoon or even late next week?

If they are using CS3 over CS4, they have a reason, whether it is financial or feature related, that is their decision -- this has nothing to do with SL and is Adobe's issue.

What made me chuckle was "Backward compatibility is Windows main strengths ...".

What!? EVERY SINGLE RELEASE of windows has come with a more-than-lengthy list of incompatible software and hardware.

Where have you been for the past 15 years?
 
All the programs I used in XP and Vista tranferred to W7 without any problem. Backward compatibility is Windows main strengths and the main reason why corporations stick to it. Can you imagine them using Macs where support was dropped after just a few years, where upgrading to new Os meant upgrading the software such as CS4 which means the total cost of ownership is even higher than Windows.

If you look at most LARGE companies (1,000 + employees), they rarely jump to the newest version of Windows because of compatibility issues (and cost of changing due to various levels of hardware throughout the company). My company has 3,000+ employees and we never went to Vista because of compatibility issues with billing software, proprietary software, etc. Most large companies do NOT jump to the newest versions of Office, either (which may be a shock to you).
 
lol

You are forgetting that they are not being "forced" to upgrade. Leopard was working fine in their business model this morning, why would it not be working correctly this afternoon or even late next week?

If they are using CS3 over CS4, they have a reason, whether it is financial or feature related, that is their decision -- this has nothing to do with SL and is Adobe's issue.

What made me chuckle was "Backward compatibility is Windows main strengths ...".

What!? EVERY SINGLE RELEASE of windows has come with a more-than-lengthy list of incompatible software and hardware.

Where have you been for the past 15 years?
What you say is true right up until they need new hardware, then they have no choice but to run the latest OS as Apple doesn't offer a way to go back.

Windows backwards compatibility is also MSs largest weakness. In that they have to support all those APIs that should have been long removed.
 
Your statement seems to only be true in Apples case. Everyone here complained about Vista and drivers and laid the blame on MS, yet with Snow Leopard it is all of a sudden the hardware makers fault. Did Apple change the driver model for all those that are running the 32bit kernel? If not there is no real reason why Leopard drivers shouldn't work with Snow Leopard when running a 32bit kernel.

How can you make a blanket statement of "Everyone here complained about Vista and drivers and laid the blame on MS, yet with Snow Leopard it is all of a sudden the hardware makers fault" on me when I never excused the laziness of hardware companies when it came to Windows Vista? Windows Vista was API stable for over a year. For one whole year hardware developers hard the opportunity to write their drivers - sorry, I'm not going to excuse it. I'm also not going to excuse the fact that Microsoft provided many driver API's in stable form before Windows Vista was released.

Apple made it known that at 10A380 that the kernel was API stable, by 10A402 the whole operating system was API/ABI stable which was released 10 July, 2009. They've had a month and a half to finalise and do some final testing, 11 June 2009 was when the kernel was marked API/ABI stable - closed to two months. Sorry, I'm not going to cut the hardware vendors slack just as I am not going to cut software vendors slack. They have the opportunity to test their product, they had the opportunity to hire more people if the work load was too much as to carry on new product development and maintenance for existing products so that they work with a new operating system being released.

Things have changed in the kernel - there are vendors out there who use nasty hacks, work arounds and bugs that are only exposed under certain conditions. The kernel has changed; that is the reality - you can either accept it or keep flooding the forum with your laundry list of complaints.
 
Why is it Parallels' (or Adobe's or HP's or....) problem that a minor OS update from Apple is incompatible with the previous version?

:confused: You agree that it's Apple's fault?

...and when the OS vendor updates the OS, it's the OS vendor's responsibility to not break things for no reason. (Some OS changes, such as driver framework shifts, will cause breakage - but that is done because the improvement is considered worth the pain.)

Much of the Windows 7 Beta/RC testing was automatic - installation and program and system errors were uploaded to Microsoft. With a large base, statistical methods were used to recognize and prioritize problems.

It's HP's fault that Apple shipped software that broke the printer?

HAHA! You are so far out in left field (and yes the "left" pun was intended, from your tag line), you're almost trolling.

This _IS_ the model of software companies.

Are you a developer or have you ever used a programming language? What happens when a new version of a development language is released? Do you even know?

They deprecate features and functionality in the language which BREAKS thousands upon thousands of applications instantly when it is released. This happens every week with at least one language somewhere. Add up the number of mainstream development languages along with the number of scripting languages to the number of development frameworks in use and you'll get the idea of the amount of change that is happening each week.

Common sense here. Geesh...

It _IS_ the responsibility of the software developer to be tracking the progress and life-cycle of the development language, to ensure they are compatible with all future updates and the direction the language is going.

This _IS_ what is happening here.

Wouldn't it be nice, if I could write an application and then blame Ubuntu or CentOS or FreeBSD when their new version breaks my software. Yeah, I could only imagine the dumb looks I would get from customers... I spend a minimum 10% of my time refactoring code to ensure it works with current and future language and OS changes...

The only debate really, is how much time should Apple have given developers to work these issues out.

Don't forget this is also the company who developed Rosetta and supported multiple processor / instruction sets in a single release... who ported an entire mainstream OS to that new architecture with relatively minimal negative impact. I would guess they kind of know what they are doing, just a guess though.
 
How can you make a blanket statement of "Everyone here complained about Vista and drivers and laid the blame on MS, yet with Snow Leopard it is all of a sudden the hardware makers fault" on me when I never excused the laziness of hardware companies when it came to Windows Vista? Windows Vista was API stable for over a year. For one whole year hardware developers hard the opportunity to write their drivers - sorry, I'm not going to excuse it. I'm also not going to excuse the fact that Microsoft provided many driver API's in stable form before Windows Vista was released.

Apple made it known that at 10A380 that the kernel was API stable, by 10A402 the whole operating system was API/ABI stable which was released 10 July, 2009. They've had a month and a half to finalise and do some final testing, 11 June 2009 was when the kernel was marked API/ABI stable - closed to two months. Sorry, I'm not going to cut the hardware vendors slack just as I am not going to cut software vendors slack. They have the opportunity to test their product, they had the opportunity to hire more people if the work load was too much as to carry on new product development and maintenance for existing products so that they work with a new operating system being released.

Things have changed in the kernel - there are vendors out there who use nasty hacks, work arounds and bugs that are only exposed under certain conditions. The kernel has changed; that is the reality - you can either accept it or keep flooding the forum with your laundry list of complaints.
I am sorry for making it seem like it was only you.

I will point out the time frame difference though. In MSs case there was a year before consumer release whereas Apple only had a couple months. That is far less time for good testing of all the hardware that could potentially ever be plugged in to a Mac. Not saying that is a good excuse, just pointing that out. What I find odd is in the case of hardware, if the driver arch is the same then why is hardware not working? I understand software and API usage bringing incompatibilities.
 
FileMaker Pro 10

Has anyone tried FileMaker Pro 10 with SL. FileMaker Pro claims that there is an issue with opening existing databases. See below a statement from their Web site:


For example:
Create a basic database
Create the following AppleScript in Script Editor (substitute the application name and filepath to anything suitable)

tell application “FileMaker”
open file “Drive:filename.fp7”
end tell
Run the AppleScript
Result: On Mac OS X v10.6, the FileMaker application launches if it was closed, but the file does not open. Script Editor displays the following AppleScript error:
“FileMaker got an error: Unable to coerce the data to the desired type.


WORKAROUND:
For example:
tell application “FileMaker”
open “Drive:filename.fp7”
end tell
 
10.6 -

Comments on the new joy.

10.5.8 all patches upgraded to 10.6.0
All went smoothly - ~1.25 hours to upgrade. ~55mins to timemachine the upgrade (46Gb of changed data compared to the TM from last night).

Few errors:
Quicksilver - installed B56a7 to resolve (no surprise, install latest and things work)
GuitarPro 5 - simple reinstall, same image - works
TuxGuitar - have to replace the swt.jar file to a 64bit version (no surprise - 10.6 is 64 bit - good forum update already) Safari

One break:
Safari 4.0.3 cannot be reinstalled. It was acting strange (slow, not opening pages, etc) so I thought, just reinstall it. But no luck as Safari requires Mac OS X 10.5.8 or newer.
Yes, that's right, its just a Mac program that is broken... sigh. :eek:

Clean install will prob 'fix' this - but so will safari 4.0.4 or os x 10.6.1 :D

Same rules always apply - if you're worried about things not working after the upgrade - don't upgrade on day 1. And remember the blue screens - they don't happen here. :apple:
 
Comments on the new joy.

10.5.8 all patches upgraded to 10.6.0
All went smoothly - ~1.25 hours to upgrade. ~55mins to timemachine the upgrade (46Gb of changed data compared to the TM from last night).

Few errors:
Quicksilver - installed B56a7 to resolve (no surprise, install latest and things work)
GuitarPro 5 - simple reinstall, same image - works
TuxGuitar - have to replace the swt.jar file to a 64bit version (no surprise - 10.6 is 64 bit - good forum update already) Safari

One break:
Safari 4.0.3 cannot be reinstalled. It was acting strange (slow, not opening pages, etc) so I thought, just reinstall it. But no luck as Safari requires Mac OS X 10.5.8 or newer.
Yes, that's right, its just a Mac program that is broken... sigh. :eek:

Clean install will prob 'fix' this - but so will safari 4.0.4 or os x 10.6.1 :D

Same rules always apply - if you're worried about things not working after the upgrade - don't upgrade on day 1. And remember the blue screens - they don't happen here. :apple:

Never do an upgrade - clean install, clean install, clean install, clean install!
 
One of the big ones I've heard floating around is that AT&T USB Cards are a no go. Specifically the USB 881B, I'll test that myself and find out. But that really kills me updating the laptops.

On the desktop side I have a lot of pro apps I'm worried about but most have been confirmed to work by now.

Things I still have questions about on the consumer side...
  • last.fm or iScrobbler
  • Drobo and Drobo Dashboard
  • NetNewsWire

Drobo and Drobo Dashboard work just fine.
 
yazsoft Sharetool 1.28 works but it will crash over and over and then all of a sudden start working :(
 
Any one tried of VisualHub works? I would hate to lose such simple and awesome converter.

It barfed when I tried to convert an FLV, but then it sometimes did that in 10.5 so I am not sure it's a specific 10.6 issue. Since VH is no longer supported by the author, I've moved to MPEG Streamclip and that has worked fine in 10.6 so far.
 
Fools Rush in Where Angels Fear to Tread

Will be waiting for 10.6.1, or at least .3 as I did with Leopard, when printing was sorted...

Don't understand why apple release stuff with so many unfixed problems?

I guess it's just like Microsoft, you don't really know what's wrong until the unwashed masses get a hold of it. Then patch and patch and patch...:eek:

At least you quick adapters will help .1 or .2 pave the way for me to upgrade... Thanks! :cool:
 
CS4 Uninstall and Reinstall?

I was over on the Adobe forums and they're suggesting that before installing SL, you uninstall Adobe Photoshop Elements 6 and then reinstall after installing SL. Anyone know if this is the case with CS4? I also have CS4 Web Premium.
 
One of the big ones I've heard floating around is that AT&T USB Cards are a no go. Specifically the USB 881B, I'll test that myself and find out. But that really kills me updating the laptops.

That sounds awful. Just knowing how long it took for those companies to make a (shoddy) application (all of them) to even get those things working on the Mac OS in the first place makes me scared for what the future holds for them in SL.
 
Will be waiting for 10.6.1, or at least .3 as I did with Leopard, when printing was sorted...

Don't understand why apple release stuff with so many unfixed problems?

I guess it's just like Microsoft, you don't really know what's wrong until the unwashed masses get a hold of it. Then patch and patch and patch...:eek:

At least you quick adapters will help .1 or .2 pave the way for me to upgrade... Thanks! :cool:

It doesn't really fall under Apple to provide third party support. The developer preview has been out long enough for those who cared enough to update their apps accordingly. Otherwise, it's just a matter of time.
 
Hey guys,

Can someone with a iSCSI NAS please check if globalSAN iSCSI Initiator works with Snow Leopard? I highly depend on it for my Time Machine backups and data storage.

If it doesn't, or if it can't be confirmed, does anyone know of an iSCSI Initiator that's been confirmed to work with Snow Leopard? Or better yet, does Snow Leopard have native support for iSCSI but it hasn't been announced as a "feature" ?

If it helps, I have a 2.8 iMac from '08.

Cheers,
-robodude666
 
MP Navigator EX

I have a Canon CanoScan 5600F. I have to launch something called "Solution Menu" and then when I choose "Scan / Import photos of documents" it starts up a program called MP Navigator EX. I can't find anything about it's compatibility with SL. It's not listed in the Wikidot list.


SOLVED!

I found the answer on Canon's website below - it lists all compatible consumer scanners with SL: http://www.usa.canon.com/consumer/c...ortDetailTabAct&fcategoryid=235&modelid=17142
 
It doesn't really fall under Apple to provide third party support. The developer preview has been out long enough for those who cared enough to update their apps accordingly. Otherwise, it's just a matter of time.

Yes, very true madog... Those who cared enough!

Look how long it took M$ to put out Intel based apps... BIG developers will do it when they feel like it, not when Apple change their system, in time all will, but they won't jump when Apple tell them...:( (i wish)
 
On another note, if anyone is itching to see support articles for SL, Australia's site has them:

http://www.apple.com/au/support/snowleopard/

Curious about having some of Apple's own apps be incompatible with SL. If you are worried about incompatibilities I would suggest that you wait a couple of months until 10.6.1 appears and/or some of the vendors affected come out with patches.

I usually use these OS upgrades to erase the hard drive completely then re-install each application as I needed it. I tend gather a lot of utilities that I no longer use and these OS updates tend to "clear the deck" as they say.

Fortunately I use Fusion instead of Parallels, so that won't give me any issues.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.