10.2 Info/Pictures/Movies

[Buggy]

I have posted this before... But I need to add to Duke's assertion that apple should not expect us to pay for OS10.2

OSX 10.0 claimed that it networked with legacy systems such as windows NT. It only half does... only for carbon apps.

OSX10.1 claimed that it improved its networking and claimed again that it networks with legacy systems.... It still doesn't

It has been a year and OSX in any version does not network with NT, even though you can restart the very same machine on the very same network into OS9 and it will work seemlessly.

If they charge for this upgrade... there are going to be some VERY pissed off IT managers. Especially in print houses where they have custom software that is still classic and set up for NT. The print industry that gave birth to Apple has been ignored by apple in the video generation.

this is my 2 cents...

not my $99 upgrade.

 

[Taft]

Hmmm...

Originally posted by Buggy
OSX 10.0 claimed that it networked with legacy systems such as windows NT. It only half does... only for carbon apps.

OSX10.1 claimed that it improved its networking and claimed again that it networks with legacy systems.... It still doesn't

It has been a year and OSX in any version does not network with NT, even though you can restart the very same machine on the very same network into OS9 and it will work seemlessly.

I agree that you shouldn't have to pay for the upgrade, but I've never had any problem connecting to Windows machines.

Have you ever tried Samba? As in Finder->Go->Connect To Server
then enter smb:\\WindowsServer\sharename

Or are you complaining that OS X won't see windows shares by default? Or that authentication against NT machines doesn't work. Could you clarify?

Matthew

 

[4409723]

What?

My friend has NT and we can network fine, i'm not sure what the problem is.

Apple tech support have an article about connecting to smb go take a look


My Monthly Post

 

[Decimal Dave]

OS X hates NT appleshare

This is something that could seriously slow the migration to OS X at my company. All of our Appleshare servers are NT-based, and the OS X finder crashes when accessing any one of them. Using SMB is not an option because it introduces security problems due to the way our network is configured.

 

[Buggy]

You can network through Samba. It is not very "mac" like but it works just fine.

It is with classic that the problems occur.

You can not AFP log onto a NT server without the crashing. It will stay there for a bit but after working throught the files it will crash the finder.

Plus in no way should you try and open a file from within a classic app or save to a NT disk from a classic app. Crashes OS9.

Samba shares doe not crash but you can not see a samba share through a classic apps menus (eg save, open or link)

The linking is one of the most crucial problems. Since pagemaker and Quarks Express are file linking documens and are both classic then anyone who works with either of these programs can not use OSX because you can not link through Classic in Samba.

InDesign works fine. I have been experimenting with it and as soon as I get Photoshop then I won't have to worry about AFP. .. We right now can't afford to buy all new licences or Photoshop, Illustrator and inDesign for the whole work site!!!!

Your friends that are Networking with NT may only be sharing a couple of machines. We have well over 300 on our server. From all reports the problems increase as the number of computers increase.

Also if they are not doing any Linking through classic then they won't experiance the same problems.

Or if they are just file sharing then they most likely will not experiance the problems.

Apple has acknowledge that there is a problem, but they have not explained when and or if it wil be fixed..... only that they are aware of it.

Seriously check out Apple.com - discussions - OSX - networking and the web - "Finder crash when browsing on NT"

If you or any of your friends can solve this problem then post the answer!!!!
There have been very sklled users trying to solve this for over a year. No solution just temp fixes.