Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Child-Like Robot
« on: December 05, 2008, 01:57:43 AM »

I tried opening the ToB Mac Tutu Core Files with a completely different program, for some reason the ones opened with UnRarX and Stuffit Expander were screwing up, I ended up using a program called 'The Unarchiver'.... although if you open any other mod files with it the computer can't read the files as executable.

Not entirely sure why... but it's working now, so all is good! Thanks for your help guys!

good tip, glad it's working
Posted by: MrHell
« on: December 04, 2008, 08:04:48 AM »

I tried opening the ToB Mac Tutu Core Files with a completely different program, for some reason the ones opened with UnRarX and Stuffit Expander were screwing up, I ended up using a program called 'The Unarchiver'.... although if you open any other mod files with it the computer can't read the files as executable.

Not entirely sure why... but it's working now, so all is good! Thanks for your help guys!
Posted by: unreserved_Steve
« on: December 03, 2008, 02:33:11 PM »

You could try changing the access permissions.  Run Terminal (it's in Applications/Utilities) and type:
    chmod  -R  777  drag-and-drop-your-BG-folder-here
and press Return.
Posted by: MrHell
« on: December 02, 2008, 02:13:23 AM »

Still no luck... I must be missing something,

I've tried repairing disk permissions, repairing the disk and even tried reinstalling the operating system... I reinstalled tutu every time I tried a new solution, I'm positive this is something to do with the permissions though, the installation was working 4 months ago... what could have changed now?

Thanks so much for your help, It's really appreciated.
Posted by: Child-Like Robot
« on: December 01, 2008, 09:43:40 PM »

Hmm I can can't click 'repair disk', only 'repair disk permissions'... maybe I can try starting up from the MacOSX installation disk?

Yes.  if you have an external drive, you might consider keeping another install of os x on it as  boot drive in case you need it (I've needed mine enough times to know how helpful it is).

You should probably do this (at the very least) periodically to make sure you're in good graces with your computer.  sometimes these problems hide for a while (like this one, i had no other problems with any other function of my computer). 
Posted by: MrHell
« on: December 01, 2008, 09:40:17 PM »

Hmm I can can't click 'repair disk', only 'repair disk permissions'... maybe I can try starting up from the MacOSX installation disk?
Posted by: Child-Like Robot
« on: December 01, 2008, 10:19:06 AM »

I've got the same problem... but I'm not sure what a disk catalouge is? how did you fix it?

Run your disk repair utility.  In OS X: Disk Utility > Repair Disk did the trick.  This should be basically the same on other OS's.  Also make sure Tutu has access to plenty of RAM, as it uses a ridiculous amount (and I ran into trouble later on because I wasn't giving it enough).

Your disk catalog is the invisible software header of the disk which records the basic information about every file on the disk and where it is physically located.  If your header is screwed up, then your computer doesn't know where to look for the resources that a program is asking for.  In this case, it wasn't quite that severe, and seems to be a problem activated by one of the weidu installs, weirdly enough.  It just prevented bg from have write access to the resources. 
Posted by: MrHell
« on: December 01, 2008, 02:05:03 AM »

I've got the same problem... but I'm not sure what a disk catalouge is? how did you fix it?
Posted by: Child-Like Robot
« on: November 21, 2008, 08:35:11 PM »

It appears to be fixed.  It was a problem with my disk catalog, now repaired seems to work fine. 

I had no problems with the disk, but I guess it was preventing the app from writing at all.
Posted by: Child-Like Robot
« on: November 21, 2008, 07:05:36 PM »

I can't help with this one.  An assertion error comes from the game engine itself.  Could be an issue with the Mac port.

Based on the error message and your description of when it occurs, it sounds like the engine is trying to record the state of the store (e.g., what items and what quantity of them are in stock) after your having left it.

agreed.  It definitely has nothing to do with Tutu (crashing in clean ToB also upon exiting the bag of holding) so I'm not really sure what the problem is.  It was working fine a week ago... maybe something odd with my drive. 

If I can get it working I'll at least post about the problem, in case anyone else ever runs into it.  Thanks anyway.
Posted by: Macready
« on: November 21, 2008, 06:59:48 PM »

I can't help with this one.  An assertion error comes from the game engine itself.  Could be an issue with the Mac port.

Based on the error message and your description of when it occurs, it sounds like the engine is trying to record the state of the store (e.g., what items and what quantity of them are in stock) after your having left it.
Posted by: Child-Like Robot
« on: November 20, 2008, 07:08:25 PM »

I'm getting a crash to desktop on a clean EasyTutu install (OS X):

Code: [Select]
An assertion failed in CStore.cpp at line 394
Programmer says: _INN2616 failed to write file.

INN 2616 is Candlekeep Inn (so this is right at the beginning of the game).  It occurs upon leaving the inn (clicking "Done" to exit the .STO) Tried a lot of different settings and reinstalled twice.  Also tried unraring EasyTutu using different expanders—same error every time. 

I'm not that confident that this is even a tutu error.  I have another set of SoA disks I can try installing from that I will dig out and see if that helps.  In the meantime, wondering if anyone else has had this problem.  A similar bug was  noted here <http://forums.pocketplane.net/index.php?topic=25572.0;wap2> with no apparent resolution.

Any guesses?