Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!amdahl!uunet!peregrine!zardoz!dhw68k!bytebug
From: bytebug@dhw68k.cts.com (Roger L. Long)
Newsgroups: comp.sys.mac
Subject: Re: 6.0 What works - what doesn't?
Message-ID: <10528@dhw68k.cts.com>
Date: 14 Aug 88 14:09:38 GMT
References: <7988@cup.portal.com> <4962@watdcsu.waterloo.edu>
Organization: Wolfskill residence; Anaheim, CA (USA)
Lines: 29

In article <4962@watdcsu.waterloo.edu> Richard Crispin writes:
|I have not had a crash that I can attribute for sure to System 6.0. I use
|Word 3.01 & Excel 1.5 without a problem. Initally I had trouble but once I
|removed MacroMaker everything was ok again. I think MacroMaker is a piece
|of very unstable code and should never be used.

It seems that everyone is an expert these days.  People are more than willing
to proclaim to the public that FOO is full of bugs, or that their hard disk
was wiped out after they used FOO, or that FOO crashed their machine, so it
must contain one of those dreaded viruses.

Come on people!  Comments like this aren't helpful at all.  Just because you
have trouble using something doesn't mean that its "a piece of very unstable
code and should never be used."   For all you know, MacroMaker is quite solid
having run for the past year inside Apple as someone's personal hack, and is
only now being released to the public.

If you want to be helpful, go into a little more detail, such as:

	I have a Mac II with 5MB of memory and running standard System 6.0
	software with no extra INITs or DAs.  I also have a 40MB internal
	Apple winchester.  When I tried to run Word 3.01 and Excel 1.5 on my
	system, I initially had some problems, but I noticed that if I removed
	MacroMaker, that the problems went away.  Has anyone else had problems
	that went away when you removed MacroMaker?

-- 
	Roger L. Long
	dhw68k!bytebug