Aladdin Systems, Inc. - Spring Cleaning FAQ

Q: Why does Spring Cleaning freeze or give an error while scanning my hard drive in a particular module?

There are a few possibilities for what can cause this situation. The two primary reasons are usually memory allocation problems or corrupt files. Spring Cleaning 1.0 needs a contiguous block of Ram (uninterrupted piece) to sort all of the files to be listed. If it can't find a large enough block, you could freeze or get an error message. Usually allocating more Ram to Spring Cleaning would help this problem. The 1.0.1 update should eliminate this issue because the memory management was refined so it can use alternate methods of sorting files if needed. Make sure version 1.0.1 is being used before worrying about the other possibilities.

A corrupt file or font can cause a freeze or error during the scanning process. Try running Norton Utilities, MacTools, or some other disk repair program that can detect corruption. If you don't have one of these programs then Apple's Disk First Aid (provided with your system software) will at least perform simple repairs.

If those programs do not find any problems and you still suspect a corruption, you can try to manually eliminate the possible corrupt files. If you are running Prefs Cleaner or Font Remover, you would use a process of elimination to try and determine which files/fonts might be corrupted. Try removing half of the files/fonts from their folder and place them in a temporary folder. Run the module again and see if you get the same error. If you do not (if you do, go to the next paragraph), then one of the files/fonts that you removed is most likely corrupt. Add them back in small groups and run the module each time until it freezes again. One of the files you just added is probably corrupt.

If you still froze or received an error after removing half of the files/fonts, then its possible that the corrupt item is part of the remaining ones. Try removing more files/fonts in groups until you are able to run the module without problems. When you are successful, the corrupt item was probably in the last group of items removed.

There may also be a simple INIT (extensions and control panels) conflict occurring. Try booting with your INITs off (by restarting the Mac and holding the shift key down until you see "Extensions Off" (System 7.6 says Extension Disabled) message under the Welcome to Macintosh dialog). Then run Spring Cleaning to see if the situation improves.

It is also highly advisable to run some type of virus scan since infections can cause random errors. (Disinfectant 3.6, a freeware product, can be downloaded from many sites on the Internet)

Q: Why can't I scroll through the items listed in the Actions Window?

You are most likely running one of the original series Power Macs (6100 family, 7100 or 8100) with System Software version 7.5 or 7.5.1. It seems that the combination of Spring Cleaning, these particular machines, and these versions of the System Software contribute to the problem. We have a few temporary workarounds and two solutions. You should be able to use the arrow keys on their keyboard to scroll through the list. Some users have also been able to turn on Balloon Help and then scroll. It seems that the problem is isolated to System 7.5 and 7.5.1 so if you update your System Software to 7.5.3 or higher, the problem will most likely disappear. This problem is fixed in the Spring Cleaning 1.0.1 update, so updating is obviously the best solution.

Q: Why are all of the Action Buttons grayed out when I get to the first window of MacUninstaller?

Don't forget that MacUninstaller requires a TWO step process while the other modules are a single step. The first window of MacUninstaller is where you select the application to be removed by placing a red check mark in the lefthand column next to the application's name. Once you select at least one application, only the "Scan" button will become active. Spring Cleaning will then scan for the files associated with the chosen application(s) and return a list of items. You can then select files and the normal Action Buttons will become active.

Q: I trimmed the fat from Virex and now it doesn't work. Why?

There is a problem in Spring Cleaning 1.0 with trimming Virex. The 1.0.1 update fixes the situation by not listing Virex as a possibility to trim.

Q: I trimmed ClarisWorks and now when I launch it, I get an error message saying that it may have been damaged and asks if I want to continue. Why?

ClarisWorks checks its internal code when launching and can tell that the fat code has been eliminated. It assumes that something has damaged the program (ie. virus, system corruption) and presents this dialog box. The program has not been damaged and will run fine if you continue. You will, however, continue to see the error message every time you run ClarisWorks. We suggest that you reinstall the program and not trim it.

Q: How does Spring Cleaning decide what is orphaned?

Spring Cleaning first builds a list of all the applications on your hard drive, and then does the same for all of the files. It then compares their Creator codes to try and match files to the applications. If it can't match a file with an application, it lists it as orphaned. You may have some files listed that Spring Cleaning 'suspects' are orphans but really are not. Sometimes a file may have a blank Creator code or one that is just a bunch of question marks. Spring Cleaning can't match these files with an application so it lists them as orphans. You may also have some files that are included with a particular program that uses them, but weren't 'created' by that application (ie a third party grammar module that is bundled with a company's word processor, but was created by a totally different company). These files might be listed as orphans even though a particular program uses them. They just weren't created by the parent application so Spring Cleaning considers them to be orphaned when they aren't. You should carefully evaluate the files listed in the Action Window to make sure they don't belong to a program before you delete them.

Q: Why won't SC find all of my applications in MacUninstaller?

The application probably has a small problem in that the Bundle (bndl) bit is set incorrectly. This causes the application to not be listed in the desktop database properly. Since Spring Cleaning is using the desktop database to locate applications, an item not listed properly will not show up in the first window. Try running Norton Utilities, MacTools, or some other disk repair program that can detect Bundle (bndl) bit problems. They should find and might repair the problem. You should then rebuild your desktop by rebooting your computer while holding down the command (aka Apple) and option keys. When you see the message "Are you sure you want to rebuild the desktop file on the disk XXXX?" click OK. The applications should now be included in the desktop database allowing Spring Cleaning to 'see' them.

Q: Why, when it looks like Spring Cleaning slimmed an application, does it show up as unslimmed the next time I run App Slimmer?

Spring Cleaning currently looks at the full code for a program and checks to see what portion is PowerPC and what is non-PowerPC. If it sees too much of one kind it will list it. However, it does not yet take into account whether the code is protected 'resource' code and cannot be deleted. If it is protected code that Spring Cleaning can't remove, then it will show up again next time you scan.

This issue is fixed in version 1.0.1 :)

Q: Can MacUninstaller tell the difference between files created by different versions of the same program?

This depends on whether the Type & Creators for the files are different. MacUninstaller uses the Type and Creator codes to match files with their parent applications. Some developers change the file Type and Creator with each release and some do not. If you perform a "Get Info" on a file and it provides a version number in the Kind field (ie. ClarisWorks 4 document rather than just ClarisWorks document) then Spring Cleaning might differentiate between versions. As always, caution is the best approach.

Q: How do I eliminate an item from Spring Cleaning's memory?

Unfortunately, there is currently no way to remove a single item from Spring Cleaning's Memory File in version 1.0 or 1.0.1. You would have to remove the current Memory File for the items to reappear in the lists. If you want to keep the Memory File because of the other items you've entered, you can move the Memory File out of the Spring Cleaning folder, perform the actions on the files, then replace the Memory File when finished. This would allow you to perform an action on an item in the Memory file without permanently losing the list of other files added to Spring Cleaning's memory. This will change in version 2.0.

Q: When is version 2.0 coming out?

We are working very hard on designing and developing Spring Cleaning 2.0. There are many variables involved in the software development process that prevent us from setting a specific release date. Registered users of version 1.0 will receive a FREE upgrade to version 2.0 so make sure to send in the registration card :) In addition, you can also subscribe to our electronic mailing list to be notified of updates to our products. Simply visit our Web Page and click on the 'Join Our Mailing Lists' button on the left side.

Products | Support | Company Info | Site Map | Home

Downloads | Updates | Products | Register
Developers | Ask Aladdin

Copyright 1997, 1998 Aladdin Systems, Inc. Questions? Send us a note.
Modified 3/12/98 FxD Webworks

		Q: Why does Spring Cleaning freeze or give an error while scanning my hard drive in a particular module? There are a few possibilities for what can cause this situation. The two primary reasons are usually memory allocation problems or corrupt files. Spring Cleaning 1.0 needs a contiguous block of Ram (uninterrupted piece) to sort all of the files to be listed. If it can't find a large enough block, you could freeze or get an error message. Usually allocating more Ram to Spring Cleaning would help this problem. The 1.0.1 update should eliminate this issue because the memory management was refined so it can use alternate methods of sorting files if needed. Make sure version 1.0.1 is being used before worrying about the other possibilities. A corrupt file or font can cause a freeze or error during the scanning process. Try running Norton Utilities, MacTools, or some other disk repair program that can detect corruption. If you don't have one of these programs then Apple's Disk First Aid (provided with your system software) will at least perform simple repairs. If those programs do not find any problems and you still suspect a corruption, you can try to manually eliminate the possible corrupt files. If you are running Prefs Cleaner or Font Remover, you would use a process of elimination to try and determine which files/fonts might be corrupted. Try removing half of the files/fonts from their folder and place them in a temporary folder. Run the module again and see if you get the same error. If you do not (if you do, go to the next paragraph), then one of the files/fonts that you removed is most likely corrupt. Add them back in small groups and run the module each time until it freezes again. One of the files you just added is probably corrupt. If you still froze or received an error after removing half of the files/fonts, then its possible that the corrupt item is part of the remaining ones. Try removing more files/fonts in groups until you are able to run the module without problems. When you are successful, the corrupt item was probably in the last group of items removed. There may also be a simple INIT (extensions and control panels) conflict occurring. Try booting with your INITs off (by restarting the Mac and holding the shift key down until you see "Extensions Off" (System 7.6 says Extension Disabled) message under the Welcome to Macintosh dialog). Then run Spring Cleaning to see if the situation improves. It is also highly advisable to run some type of virus scan since infections can cause random errors. (Disinfectant 3.6, a freeware product, can be downloaded from many sites on the Internet) Q: Why can't I scroll through the items listed in the Actions Window? You are most likely running one of the original series Power Macs (6100 family, 7100 or 8100) with System Software version 7.5 or 7.5.1. It seems that the combination of Spring Cleaning, these particular machines, and these versions of the System Software contribute to the problem. We have a few temporary workarounds and two solutions. You should be able to use the arrow keys on their keyboard to scroll through the list. Some users have also been able to turn on Balloon Help and then scroll. It seems that the problem is isolated to System 7.5 and 7.5.1 so if you update your System Software to 7.5.3 or higher, the problem will most likely disappear. This problem is fixed in the Spring Cleaning 1.0.1 update, so updating is obviously the best solution. Q: Why are all of the Action Buttons grayed out when I get to the first window of MacUninstaller? Don't forget that MacUninstaller requires a TWO step process while the other modules are a single step. The first window of MacUninstaller is where you select the application to be removed by placing a red check mark in the lefthand column next to the application's name. Once you select at least one application, only the "Scan" button will become active. Spring Cleaning will then scan for the files associated with the chosen application(s) and return a list of items. You can then select files and the normal Action Buttons will become active. Q: I trimmed the fat from Virex and now it doesn't work. Why? There is a problem in Spring Cleaning 1.0 with trimming Virex. The 1.0.1 update fixes the situation by not listing Virex as a possibility to trim. Q: I trimmed ClarisWorks and now when I launch it, I get an error message saying that it may have been damaged and asks if I want to continue. Why? ClarisWorks checks its internal code when launching and can tell that the fat code has been eliminated. It assumes that something has damaged the program (ie. virus, system corruption) and presents this dialog box. The program has not been damaged and will run fine if you continue. You will, however, continue to see the error message every time you run ClarisWorks. We suggest that you reinstall the program and not trim it. Q: How does Spring Cleaning decide what is orphaned? Spring Cleaning first builds a list of all the applications on your hard drive, and then does the same for all of the files. It then compares their Creator codes to try and match files to the applications. If it can't match a file with an application, it lists it as orphaned. You may have some files listed that Spring Cleaning 'suspects' are orphans but really are not. Sometimes a file may have a blank Creator code or one that is just a bunch of question marks. Spring Cleaning can't match these files with an application so it lists them as orphans. You may also have some files that are included with a particular program that uses them, but weren't 'created' by that application (ie a third party grammar module that is bundled with a company's word processor, but was created by a totally different company). These files might be listed as orphans even though a particular program uses them. They just weren't created by the parent application so Spring Cleaning considers them to be orphaned when they aren't. You should carefully evaluate the files listed in the Action Window to make sure they don't belong to a program before you delete them. Q: Why won't SC find all of my applications in MacUninstaller? The application probably has a small problem in that the Bundle (bndl) bit is set incorrectly. This causes the application to not be listed in the desktop database properly. Since Spring Cleaning is using the desktop database to locate applications, an item not listed properly will not show up in the first window. Try running Norton Utilities, MacTools, or some other disk repair program that can detect Bundle (bndl) bit problems. They should find and might repair the problem. You should then rebuild your desktop by rebooting your computer while holding down the command (aka Apple) and option keys. When you see the message "Are you sure you want to rebuild the desktop file on the disk XXXX?" click OK. The applications should now be included in the desktop database allowing Spring Cleaning to 'see' them. Q: Why, when it looks like Spring Cleaning slimmed an application, does it show up as unslimmed the next time I run App Slimmer? Spring Cleaning currently looks at the full code for a program and checks to see what portion is PowerPC and what is non-PowerPC. If it sees too much of one kind it will list it. However, it does not yet take into account whether the code is protected 'resource' code and cannot be deleted. If it is protected code that Spring Cleaning can't remove, then it will show up again next time you scan. This issue is fixed in version 1.0.1 :) Q: Can MacUninstaller tell the difference between files created by different versions of the same program? This depends on whether the Type & Creators for the files are different. MacUninstaller uses the Type and Creator codes to match files with their parent applications. Some developers change the file Type and Creator with each release and some do not. If you perform a "Get Info" on a file and it provides a version number in the Kind field (ie. ClarisWorks 4 document rather than just ClarisWorks document) then Spring Cleaning might differentiate between versions. As always, caution is the best approach. Q: How do I eliminate an item from Spring Cleaning's memory? Unfortunately, there is currently no way to remove a single item from Spring Cleaning's Memory File in version 1.0 or 1.0.1. You would have to remove the current Memory File for the items to reappear in the lists. If you want to keep the Memory File because of the other items you've entered, you can move the Memory File out of the Spring Cleaning folder, perform the actions on the files, then replace the Memory File when finished. This would allow you to perform an action on an item in the Memory file without permanently losing the list of other files added to Spring Cleaning's memory. This will change in version 2.0. Q: When is version 2.0 coming out? We are working very hard on designing and developing Spring Cleaning 2.0. There are many variables involved in the software development process that prevent us from setting a specific release date. Registered users of version 1.0 will receive a FREE upgrade to version 2.0 so make sure to send in the registration card :) In addition, you can also subscribe to our electronic mailing list to be notified of updates to our products. Simply visit our Web Page and click on the 'Join Our Mailing Lists' button on the left side.

		Products \| Support \| Company Info \| Site Map \| Home Downloads \| Updates \| Products \| Register Developers \| Ask Aladdin

		Copyright 1997, 1998 Aladdin Systems, Inc. Questions? Send us a note. Modified 3/12/98 FxD Webworks