re: ShadowWrite 1.3.3 bug?

[jlee@Bonnie.ICS.UCI.EDU (Joseph)]

In article <2a8hg6INNlog@iraun1.ira.uka.de>:
>Hi folks,
>
>when I load any ORCA/C source file (filetype $B0, auxtype $8) into
>SW 1.3.3 and save it after working with it, I end up with an "untyped"
>source file (filetype $B0, auxtype $0). It seems that SW 1.3.3 doesn't handle
>auxtypes of source files correctly. However, it works fine with Teach files.
>An $50/5445 file has the same filetype/auxtype after saving.
>
>Has anybody else experienced this?
>
>Any comments (Huhu, Andre)?
>
>Stefan Voss
>(voss@ira.uka.de)

I've noticed this bug since SW 1.2. Seems SW either trashes or assumes the
auxfield of a src file so editing it and saving it is bad.  I thought this
would be fixed by now, but it's not. *shrug*.

Since I'm on bugs of SW, I have some other annoying ones.  Whenever I save a
file some memory error or something would occur because when I run another
app from the finder or returning to the finder, I keep getting this dialog
saying 'Unknown error $0202' or something with the same error #. This dialog
pops up twice quitting back to the finder.  Nothing seems to be wrong with
the system i.e. no crashes or hangs, but this dialog is really annoying.

I'm not sure which NDA this bug is in but TMTerm freezes up when SW is running,
either because SW was opened before or SW was just opened.

Joseph
--
jlee@bonnie.ics.uci.edu  | "If builders built buildings the way programmers
                         |  wrote programs, then the first woodpecker that
Creative 'Ware           |  came along would destroy civilization."
         II<>II          |  -- Weinberg's Law