Re: Problems with Stuffit 8
On Thursday, October 2, 2003, at 07:10 PM, Larry Pohl wrote: I'm not sure this is Peter's problem but this is from the Aladdin site: Well, I'm b-a-a-ck! It would be nice if the problem was this simple. It was far more serious. Here is what happened, and I am about to send off a report to (1) MacFixit and (2) Aladdin. The steps I took were as follows - 1. Paid for, and downloaded the Stuffit Deluxe update, tasking advantage of the current low upgrade price for registered users. 2. Saw (but ignored - mea culpa) the little notice following installation that in order for the software to work properly it would be necessary to log out and log back in, Instead, I thought I'd just launch it to see if there were any significant interface changes - I'm a bit impatient that way. I had no intention of using it for anything, but I couldn't see how a quick explore could do any harm. While looking though the preferences, disaster struck. The screen went dim, and the machine went into kernel panic: a desperately unpleasant sight. 3. Rebooted the computer, but the boot process would not proceed beyond the apple icon in the middle of the screen. It did not even get as far as the little spinning icon. Eventually the apple icon was replaced by a No Entry icon (a circle with a diagonal bar). This was new. 4. Bad. Very Bad. Try some tools. Disk Warrior fixed a problem with the Volume Wrapper, but otherwise found no serious problems. Didn't help. Booted from MacOS X Disk and ran Disk First Aid. No problems reported. Repaired permissions. Many repairs were made, but it still didn't help. 5. No option but a clean install of MacOS X (with archive, of course). Clean install worked fine, upgraded back to 10.2.8 (with which I had had none of the many reported problems). 6. Only problem now is, no .sit files will open. Do I have another go at installing Stuffit 8, but behave myself this time? Maybe it was just a very unhappy coincidence. Bit between the teeth, and off we go. This time, no mucking around, no exploring, just install and reboot the damn thing. 7. Back to step 3. 8. Repeat Steps 4 and 5. I have now uninstalled Stuffit Deluxe 8 (of course, that entailed relaunching the Stuffit Deluxe 8 installer and re-entering the installation code, by now a very scary exercise, just so I could get to the Uninstall option) and gone back to SD 7. 9. So far, everything seems OK. I have currently gone back only as far as MacOS X 10.2.6, but I'm not prepared to give SD8 a third chance until I can get some assurances from Aladdin that this will not happen again. I have been delighted with the way MacOS X has, for me at least, upheld its reputation as an OS which does not crash. Aladdin seem to have found a way through. This would have to be the most unpleasant software upgrade I have ever experienced. It has not done my nerves (nor, I suspect, my System) one bit of good. Time for a Bex and a bit of a lie down... -- Peter Hinchliffe Apwin Computer ServicesFileMaker Pro Solutions Developer Perth, Western Australia Phone (618) 9332 6482Fax (618) 9332 0913 Mac because I prefer it -- Windows because I have to.
Re: Problems with Stuffit 8
On 03/10/03 11:45 PM, Peter Hinchliffe [EMAIL PROTECTED] wrote: On Thursday, October 2, 2003, at 07:10 PM, Larry Pohl wrote: I'm not sure this is Peter's problem but this is from the Aladdin site: Well, I'm b-a-a-ck! It would be nice if the problem was this simple. It was far more serious. Here is what happened, and I am about to send off a report to (1) MacFixit and (2) Aladdin. The steps I took were as follows - 1. Paid for, and downloaded the Stuffit Deluxe update, tasking advantage of the current low upgrade price for registered users. 2. Saw (but ignored - mea culpa) the little notice following installation that in order for the software to work properly it would be necessary to log out and log back in, Instead, I thought I'd just launch it to see if there were any significant interface changes - I'm a bit impatient that way. I had no intention of using it for anything, but I couldn't see how a quick explore could do any harm. While looking though the preferences, disaster struck. The screen went dim, and the machine went into kernel panic: a desperately unpleasant sight. 3. Rebooted the computer, but the boot process would not proceed beyond the apple icon in the middle of the screen. It did not even get as far as the little spinning icon. Eventually the apple icon was replaced by a No Entry icon (a circle with a diagonal bar). This was new. 4. Bad. Very Bad. Try some tools. Disk Warrior fixed a problem with the Volume Wrapper, but otherwise found no serious problems. Didn't help. Booted from MacOS X Disk and ran Disk First Aid. No problems reported. Repaired permissions. Many repairs were made, but it still didn't help. 5. No option but a clean install of MacOS X (with archive, of course). Clean install worked fine, upgraded back to 10.2.8 (with which I had had none of the many reported problems). 6. Only problem now is, no .sit files will open. Do I have another go at installing Stuffit 8, but behave myself this time? Maybe it was just a very unhappy coincidence. Bit between the teeth, and off we go. This time, no mucking around, no exploring, just install and reboot the damn thing. 7. Back to step 3. 8. Repeat Steps 4 and 5. I have now uninstalled Stuffit Deluxe 8 (of course, that entailed relaunching the Stuffit Deluxe 8 installer and re-entering the installation code, by now a very scary exercise, just so I could get to the Uninstall option) and gone back to SD 7. 9. So far, everything seems OK. I have currently gone back only as far as MacOS X 10.2.6, but I'm not prepared to give SD8 a third chance until I can get some assurances from Aladdin that this will not happen again. I have been delighted with the way MacOS X has, for me at least, upheld its reputation as an OS which does not crash. Aladdin seem to have found a way through. This would have to be the most unpleasant software upgrade I have ever experienced. It has not done my nerves (nor, I suspect, my System) one bit of good. Time for a Bex and a bit of a lie down... There's an interesting comment (critique) by one of the Unsanity haxie people about how Aladdin implemented the AVR function in SD 8 and its potential for causing problems. http://www.unsanity.org/archives/000253.php As an aside, the update is working fine for me.
Problems with Stuffit 8
Hi Everyone, I have just gotten of the phone from Peter Hinchliffe, who is having a Major problems with Stuffit Deluxe 8. He has had to reinstall everything twice. He asked me to issue this caution to everyone who is thinking of install v8. - Matt -- 0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0--0 Matt Healey[EMAIL PROTECTED]
Re: Problems with Stuffit 8
On 03/10/03 9:43 AM, Matthew Healey [EMAIL PROTECTED] wrote: Hi Everyone, I have just gotten of the phone from Peter Hinchliffe, who is having a Major problems with Stuffit Deluxe 8. He has had to reinstall everything twice. He asked me to issue this caution to everyone who is thinking of install v8. - Matt Hi I'm not sure this is Peter's problem but this is from the Aladdin site: Friday, 3 October 2003 StuffIt Deluxe for Mac Q: I have a .sit file containing an application, installer, or script that I expanded with Stuffit Deluxe or Standard 8.0. When I try the launch the application nothing happens. Why is this? A: At the request of Apple, Aladdin made a change to how Stuffit Deluxe and Standard behaved in the above situation. Previously, Stuffit products under Mac OS X explicitly set the execution bit to be on on expanded files regardless of whether or not the file was actually a program. This was done as a workaround to a limitation of the .sit file format which didn't allow for Unix based permissions. While this workaround was for the most part working well, Aladdin was informed by Apple that it would cause serious trouble for users with future versions of the Mac OS. The result of this is that this execution bit is no longer getting set on most files (Classic Applications, and single-file--as opposed to bundled--applications with a Type and Creator set will be launchable when expanded by StuffIt 8.0 products), which means OS X applications compressed into the .sit file format, and expanded with a Stuffit 8.0 Mac product, will not launch. While this in many ways is an inconvenience, the best thing we can say is that we have been told by Apple that it is in the best interest of our Macintosh users that we do this. To work around this change, here is our advice to our users: 1. We have created a drag-and-drop applet that you can download to use that will perform the above command for you. You can download it from: ftp://forJS:[EMAIL PROTECTED]/support/JS/FixPermissionsOnPackages .sitx 2. If you are familiar with the Terminal, you can manually go to the 'Terminal' program and modify the permissions to the file by navigating to the directory the application is in (via the 'cd' command) and typing the following: chmod -R 755 applicationname.app For Developers, as a short term fix feel free to link to this FAQ and/or the applet listed above. The best long term solution is to use the .sitx format, which is designed for OS X and takes full account of Unix based file permissions while remaining compatible with StuffIt 7.x or newer. Any users who have 10.2 or later, or who downloaded the security update that Apple put out some time ago will have a copy of Stuffit Expander 7.0 or later which can handle .sitx files. Finally, Aladdin plans to release an update for the Stuffit Deluxe and Standard 8 products that allows users some form of relief to this issue. What form that relief will take and when this update will be released is not yet specified.
