Read/Write. Freeze
JOhn Meyer/Symantec Volunteer
> Configuration Information:
> Version: 3.5.1
> Operating system: System 7.x
> Formatting: --Other--
>
> Using NU 3.5.1 on my Mac 1400. When I use install disk and try
> "custom de-install" I see check boxes and all the options greyed out.
> How can I de-install?
Hi Robert:
To uninstall, probably the easiest way is to do as follows:
Drag the Norton's Folder to the trash. Go to the "SYSTEM
FOLDER:EXTENSIONS" and drag Crashguard to the trash. Go to the
"SYSTEM FOLDER"CONTROL PANELS" and drag Filesaver to the trash.
Finally go to the "SYSTEM FOLDER:PREFERENCES" and drah the Norton
PReferences to the trash. Then empty the trash.
Hope this helps.
John Meyer/Symantec Volunteer
> Configuration Information:
> Version: 3.5.1
> Operating system: System 7.x
> Formatting: --Other--
>
> When I attempt to open read/write protected zip disks, my systems
> freezes with a dialogue box from Crash Guard saying applicaiton is
> corrupted. Is this a comflcit with NU 3.5.1? All other non
> read-write protected zip disks work fine. Thanks
Hi Robert:
More than likely you have a software conflict. Make sure that you
are running the latest version of your IOMEGA software. There have
been a number of released versions lately -three this year, including
one a week ago.
I have been running Zip disks with NUM 3.5.x and have had no problems
with freezes or crashes. You may also have an extension conflict
that needs to be isolated and resolved. Here is some information on
basic INIT conflict troubleshooting:
It's probable that CrashGuard is conflicting with another extension
or control panel (an INIT conflict). Symantec has had no reports of
general incompatibilities with just the System software.
Try isolating CrashGuard so that it's the only extension that loads.
To do this, use the Apple Extension Manager (or another manager) to
go to a Base OS8 INIT set. Then add CrashGuard to the set, restart
and see if you can reproduce the error. If that works OK, then
another INIT is involved and you'll need to use the Extension Manager
to start re-enabling INITs and restarting to see when the problem
reoccurs.
You can also try moving the CrashGuard extension out of the Extension
folder and placing it loose in the System folder. That will cause it
to load last and may help with restart problems. Or you can add
spaces to the front of the extension's name while it's in the
Extension folder and this will cause it to load sooner and that may
help as well.
There is one known conflict that it worth mentioning: SoftwareFPU:
If you have a 68k application that you are running on a PPC that
requires SoftwareFPU, you will need to disable Norton CrashGuard
prior to running the 68k application.
NOTE: If you're having trouble booting up at all, you can bypass any
INIT issues by holding the Shift key during bootup to turn off all
extensions. Then pull CrashGuard out of the Extension folder
temporarily, in order to restart successfully with all inits enabled,
to use Extension Manager.
You may also be able to bypass the startup sequence by holding the
Space key during bootup. That should call up Extension Manager
before your INITs even load.
General information on how to solve an INIT conflict:
Solving an INIT conflict is a process of elimination. People often
use the word INIT to describe both extensions (INITs) and control
panels (Cdevs). Disable all but the one INIT or Cdev that is giving
you problems and see if the problem persists. If you don't know what
INIT is causing the problem, just pick one to start with. Disable
the INITs by placing them on the desktop (or into a TEMP folder that
you create on the desktop) and restarting or use an extension manager
to turn them off as you need to.
If the problem doesn't repeat itself with just one INIT loading, add
another. Finally you will add the one that causes the problem to be
reproduced. To see if the problem is related to the loading order of
the INIT, rename it to change how it loads. For example change
"After Dark" to "zzAfterDark." Changing the loading order of
conflicting INITs will almost always solve the conflict. A startup
manager such as Extensions Manager or Now Startup Manager can make
this process easier. You can also speed up the process by moving
groups of INITs back to the appropriate folder (Extension or Control
Panels) at one time. If you add 3 or 4 and the problem doesn't
persist, it wasn't caused by any of those.
INITs load in this order:
Extensions (alphabetically)
Control Panels (alphabetically)
Stuff loose in the system folder (you guessed it, alphabetically)
Within any of the folders listed above, special characters can cause
load order changes as well. A ~ added in front of a file's name
will cause it to load last or late and a 'space' added in front of a
file's name causes it to load first or early.
So...to make an extension load after a control panel, place it loose
in the system folder. To make a control panel load first, put 3
spaces in front of it's name and put it in the Extensions folder.
Then, make an alias of the renamed control panel and put the alias in
the Control Panels folder so you can access it the same way you
always did. If you have a start up manager, chances are that it
makes provisions for reordering you INITs.
If reordering your INITs doesn't work, try reinstalling the INIT(s)
that are at the heart of the problem.
Please let me know if I can help further with this issue.