Welcome to the MacNN Forums.

ambush · Nov 9, 2003, 03:14 PM

I can't play, as soon as I enter a game, it AUTO QUITS.

I'm on Panth. Dled latest patch.

I wanna play?
I took almost 5 hours to reinstall os9 on a comp, install d2/lod, patch, xfer via network to osx comp, and wait, I enter a game and it does not work?

Thanks!

ambush · Nov 9, 2003, 03:23 PM

I'd like to add that I bought every single Blizzard game for the mac. I even bought Starcraft two times (scratched first CD).

But since OS X became standard, I can't say I'm satisfied with their job

- Speed for OSX ((WC3 lags like there's no tomorrow, on DECENT hardware, D2 is unplayable on OSX and playable on OS9 on the SAME comp)

- Support for OSX (**NO** OSX installer, OS9 is dead, and I can't install my game w/o OS9????)

- Bugs. It auto quits.

What I did:

Install D2 + LOD from old CDs.
Run on OS9, dl patch.
Xfer to osx comp.
DL file labeled "OSX Patch" in the FTP d2mac directory
moved files to d2 dir
launched d2carbon
it autodled 1.10 *again*
patches
re-runs
auto quits whenever I enter a game, making the game unplayable.

roders · Nov 9, 2003, 06:14 PM

Diablo 2 actually plays slightly slower with the 1.10 pathc under OSX than it does with 1.09d patch for OSX,and thats on my 1.8Ghz G5!

theory · Nov 9, 2003, 06:26 PM

I think blizzard made a new patch ( a mac only one straight after 1.10 ) that fixed that problem. Download it and see what happens

roders · Nov 9, 2003, 06:37 PM

Yeah 1.10b solves the quit on startup when playing in software mode.

sideus · Nov 9, 2003, 07:24 PM

Panther + D2 1.10 = Awesome game play! At least for me. Warcraft III is also much better under Panther.

ambush · Nov 9, 2003, 07:47 PM

I downloaded the 110b updater,

says there's nothing to upgrade: error 0.

What do I do.

Horsepoo!!! · Nov 9, 2003, 08:23 PM

Originally posted by sideus:
Panther + D2 1.10 = Awesome game play! At least for me. Warcraft III is also much better under Panther.

That's because you never finished Act 5 Normal.

benb · Nov 9, 2003, 08:35 PM

Originally posted by ambush:
I downloaded the 110b updater,

says there's nothing to upgrade: error 0.

What do I do.

Personally, I would complain some more.

Other people would suggest Google, or some other web search.

Switched2Mac · Nov 9, 2003, 08:41 PM

OS 9 is like a Windows user still wanting to use Windows 3.1

OS 9 is dead. Deal with it and move on.

I love Total Annihilation on the PC but the Mac version only runs under OS 9. Too bad. Oh, well.

When my iMac arrived in July, I opened the box and was EXCITED! My first Mac.

And the first thing I did was grab the OS9 Install Disc from the package and snap it in half.

Love live Mac and OS X!

ambush · Nov 9, 2003, 08:53 PM

Well I logged on Bnet, so I *automatically* have the latest version, which explains why I can't install 110b. I already have it.

And it still crashes.

sideus · Nov 9, 2003, 09:15 PM

Originally posted by Horsepoo!!!:
That's because you never finished Act 5 Normal.

Mohammed Atef · Nov 9, 2003, 09:35 PM

Originally posted by sideus:

meh. I thought it was hilarious.

mac freak · Nov 9, 2003, 10:19 PM

OT:
Mohammed, that's some location.

a2daj · Nov 10, 2003, 12:22 AM

Did you download the Diablo II OS X patch or the LoD OS X patch? They're two separate patches and installing the incorrect one might cause the crashing behavior you're describing.

The LoD patch is actually smaller than the original one. For OS X you need to not only download the correct pach files but you need to download and install both the 1.10 and 1.10b patch. Upgrading the OS 9 version of Diablo II will not affect the OS X version as far as the patches go. Since you've already got the 1.10b patch installed it's possible it's the wrong version.

It's also possible that the installation is corrupt.

a2daj · Nov 10, 2003, 12:29 AM

Originally posted by roders:
Diablo 2 actually plays slightly slower with the 1.10 pathc under OSX than it does with 1.09d patch for OSX,and thats on my 1.8Ghz G5!

Are you talking about OpenGL rendering or software rendering? OpenGL rendering is significantly better with 1.10. But I still use software rendering because it's still more consistent in terms of framerates, particularly when there are a lot of things on screen.

roders · Nov 10, 2003, 01:17 AM

This is running in OpenGL mode, but on a stock/standard speck G5, it's not slow, just not quite as smooth as the 1.9d patch (which I know is suppossed to be the opposite of what happened to every one else) it's all very strange!

ambush · Nov 10, 2003, 05:47 AM

Originally posted by a2daj:
Did you download the Diablo II OS X patch or the LoD OS X patch? They're two separate patches and installing the incorrect one might cause the crashing behavior you're describing.

The LoD patch is actually smaller than the original one. For OS X you need to not only download the correct pach files but you need to download and install both the 1.10 and 1.10b patch. Upgrading the OS 9 version of Diablo II will not affect the OS X version as far as the patches go. Since you've already got the 1.10b patch installed it's possible it's the wrong version.

It's also possible that the installation is corrupt.

Well, I'd expect it to work perfectly, since I downloaded the patch on BattleNet!

Maybe Bnet gave me the wrong patch? That'd be odd.

a2daj · Nov 10, 2003, 10:32 AM

Originally posted by ambush:
Well, I'd expect it to work perfectly, since I downloaded the patch on BattleNet!

Maybe Bnet gave me the wrong patch? That'd be odd.

Battle.net doesn't autoupdate the OS X version unless you already have an earlier OS X version installed. You said you did a clean install of Diablo II, thus you would have had to grab an OS X update off of Blizzard's site. When you downloaded the OS X patch which patch did you download? The patch for Original Diablo II or Expansion Diablo II? The Battle.net autoupdate app may look at the app you already have and update based on that, not the files you have installed. I'd expect it not to work perfectly if you installed the wrong patch. The correct patch for the expansion pack has LOD in the archive name.