Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!gem.mps.ohio-state.edu!uwm.edu!srcsip!gorby!mnkonar
From: mnkonar@gorby.SRC.Honeywell.COM (Murat N. Konar)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ResEdit 1.3d1
Keywords: ResEdit 1.3d1, virus?, Trojan Horse?, Real?
Message-ID: <39357@srcsip.UUCP>
Date: 15 Nov 89 23:04:11 GMT
References: <1989Nov14.204614.18246@polyslo.CalPoly.EDU> <16925@dartvax.Dartmouth.EDU> <36499@apple.Apple.COM>
Sender: news@src.honeywell.COM
Reply-To: mnkonar@gorby.UUCP (Murat N. Konar)
Distribution: na
Organization: Honeywell Systems & Research Center, Camden, MN
Lines: 24

In article <36499@apple.Apple.COM> keith@Apple.COM (Keith Rollin) writes:
[about the theoretically existent ResEdit 1.3d1]
>The differences between 1.2 final and 1.3d1, therefore, are a) 1.2 
>doesn't have the fancy menu editor, and b) 1.2 doesn't have all the 
>bugs that 1.3d1 does. 
>No one that I know has reported any problems with crashed disks or corrupted 
>files when using 1.3d1, but if you're as cautious as I am with your data (and 
>you should be given the Mac's propensity to crash all the time), you'll stick 
>with 1.2. I know that I do. But then, I use Rez to define my menus anyway...


Hypothetically speaking, I have had trouble with ResEdit 1.3d1.  Like MDEF
proc IDs not getting set correctly in the fancy menu picker, and the curious
ability to paste multiple copies of a resource with identical names, types
and ids into a resource file (i.e. I sometimes can get 5 INIT 1234's in 
one file). Weird.  Seems like this multiple copy property of ResEdit 1.3d1 
could concievably cause file corruption, but it hasn't yet. 

Hypothetically, of course.

____________________________________________________________________
Have a day. :^|
Murat N. Konar        Honeywell Systems & Research Center, Camden, MN
mnkonar@SRC.honeywell.com (internet) {umn-cs,ems,bthpyd}!srcsip!mnkonar(UUCP)