Good morning,

I've done a complete install of Myst IV on my MacBook Pro, but when I click on it, I got nothing at all. The icon jumps a few time and then nothing.

I've looked for logs or information but I don't find anything useful.

In any case, here's the log if it can help. I'm not too sure what's going wrong since the install is pretty straight forward.

(Aug 12, 2008 7:02:37 PM), Install, com.installshield.product.service.product.PureJavaProductServiceImpl$DiskSpaceCheck, wrn, Checking required disk space requires file service native support.
(Aug 12, 2008 7:02:52 PM), Install, com.installshield.product.actions.Files, wrn, Cannot set file attributes: operation is not supported by the current file service implementation.
(Aug 12, 2008 7:02:53 PM), Install, com.installshield.product.actions.Files, wrn, Cannot set file times: operation is not supported by the current file service implementation.


Thanks a lot,

Nico

You're using an Intel Mac, which means, to the best of my knowledge, that Myst IV won't run. It has to run through the Rosetta emulation program that Apple wrote, since Myst IV was designed for PowerPC Macs. It's just so graphics intensive, I wouldn't place bets on it running on an Intel Mac.

Besides, I don't even know if it will run on OS X Leopard. It runs on OS X 10.4.11, 10.2.x and 10.3.x, but I don't know about OS X 10.5.4.

You're in luck Nico, there's a fix:
http://forums.ubi.com/eve/forums/a/tpc/f/580100736/m/8741024374

I installed Myst 4 on my macbook (OS 10.5.5).

When it did not start up, I found the fix wishstik posted above and it did indeed work.

(For convenience sake this is the workaround:

"After you have installed both disks, and with the second disk still in the Mac...
Double click Myst4 icon (nothing happens)
Go to File -->Choose "Get Info" and open the bottom arrow and set all users to Read/Write
Open Terminal (if you don't know where it is, go to HD and search for "Terminal")
Type: cd_ (that's "cd" followed by a space, no quotes)
Drag the Myst4 icon into the Terminal window, which will give you the path to the app
Press return.
Type the magic line: chmod a+x Myst4
Press return, quit Terminal.
Double click on Myst4 icon" )

I was able to play just fine and was making good progress on Spire when Myst IV stopped working.

I got this error message:

"You cannot open the application Myst 4 because it is not supported on this architecture"

I tried the fix above, several times. Did not work.

I uninstalled - after saving the Saved folder on my desktop - and reinstalled and once again went to Terminal to type in the above fix.

It still did not work. Nothing. However, I did not get the unsupported architecture error message.

Two things to note:

1. The game stopped working after connecting an external hard drive to my macbook for a brief time.

2. Although I followed the Terminal instructions to the letter, what happens now is that after typing in the chmod part of the fix it says "no such file or directory". When I open Myst4 in a Finder window, it clearly shows there is such a file and directory. (This entry on Terminal starts with -bash. Does this mean anything to anyone?)

Any help would be greatly, greatly appreciated. I was so enjoying the game.

Lemme think... The things I'd look out for are 1. Trying to pass chmod on the alias to Myst 4, 2. making sure the chmod command is being passed on the Myst4 executable inside the Myst 4 applicaiton, and 3. a Bourne Shell (aka BASH) that doesn't have access to the chmod command.

Try this; if you're dragging the alias for Myst 4 into the terminal, navigate to the Myst 4 application itself in the Applications folder and drag it into the terminal instead at the specified step. To get out of the bash shell, type "exit" at the prompt before passing and cd or chmod commands. If this closes the window or eliminates the text prompt with the message [Process Completed], close the window and press cmd+shift+N and type "tcsh" into the prompt. Once you're in tcsh, pass the chmod command with the parameters listed and try running Myst IV. Make sure it's using Rosetta, as I know for fact that Revelation is not a universal application!

This message has been edited. Last edited by: JacaByte,

I have tried it and i get this message:

''levi-rauffs-macbook-pro:~ levi$ exit cd /Applications/Myst4/myst4.app/myst4 chmod a+x Myst4
logout
-bash: exit: cd: numeric argument required''

Oh, no... the Mac is becoming as Geeky as Windows...

Even if you had parsed that command correctly (I assume you were trying to pass multiple commands in one line; commands are separated by a semi-colon, so your line should have been "exit; cd /Applications/Myst4/myst4.app/myst4; chmod a+x Myst4") I don't think that would have worked correctly; you were still inside of the BASH shell. Pass the exit command on its own line, and if that exits you out of the BASH shell (which I think it will) press cmd+shift+N and type "tcsh", which is normally the default shell used by the Terminal but somehow you've changed it. I know for certain that tcsh has the appropriate /bin and /sbin commands available, so you may have more luck using this shell.

When the window for the tcsh shell comes up, type "cd /Applications/Myst4/myst4.app/myst4" (or do what you did before to get that application path) and press enter. Then type "chmod a+x Myst4". If that gives you a file not found error, type "cd .." and press the up key twice (so you should get "chmod a+x Myst4" in the prompt again) and press enter. Now try to launch Myst IV again. If that does work, then I suspect that the Myst IV application has been meddled with beyond repair, in which case you'll need start from scratch with a reinstall of Myst IV.

@wstrohm: Say what? The Mac has always been more geeky than Windows, ever since college students started using AppleScript to empty their trash bins in OS 7. And guess what? We're proud of it.

quote:

The Mac has always been more geeky than Windows, ever since college students started using AppleScript to empty their trash bins in OS 7. And guess what? We're proud of it.

Yeah, that has to be a LOT easier than "Shift-Cmd-Delete."

This message has been edited. Last edited by: wstrohm,

(That emoticon is so appropriate it's not even funny. It's hilarious.)

I'll see your key command, and raise you a script that makes a new text document in the window you currently have open. It's so useful you'll wonder where it is when you switch computers. Beat that with a key combo!

quote:

I'll see your key command, and raise you a script that makes a new text document in the window you currently have open.

As opposed to opening TextEdit?

quote:

Originally posted by wstrohm:

quote:

I'll see your key command, and raise you a script that makes a new text document in the window you currently have open.

As opposed to opening TextEdit?

As opposed to opening TextEdit, opening the Save dialog, hunting down the folder you were in and saving the file. (Let's try "Mac OS HD/Users/Max/Library/Application Support/EV Nova/TCTC/Pilot log.txt". Phew! Finally got there.) Believe me, when all you need is a blank text document, this is a real time saver.

A "new text document" is automatically opened when TextEdit is opened. I don't follow you at all. A "new text document" is blank. It has to be written in before it is saved, so why would I want to go to "Mac OS HD/Users/Max/Library/Application Support/EV Nova/TCTC/Pilot log.txt" for a blank text document?

No, that's where you want to put the darn text document. Have you used Text Edit when it opens a fresh document on start? That document is new; it doesn't belong anywhere until you save it somewhere, and navigating someplace that's buried underneath 10 folders and subfolders takes a while.

"Spotlight" simplifies navigation sufficiently for my purposes. All I need to know is the name of a folder to open it in one click; and if I need to save something, I don't need to write an Applescript to do it efficiently. BTW, I think this conversation is not appropriate for this thread... PM me if you want to continue.

Aw, just when it was heating up nicely . . .

Well, yeah, heating up nicely may be good in some instances, but here it's off-topic and not appropriate for this thread, as wstrohm points out. Actually, he beat me to it...but only by a bit!