Very Computer

I've seen this happen again and again when running 7.5.3. During
compilation the resource map of the file being compiled gets screwed up.
What I typically get is a "not enough memory to run" error. Doing a Get
Info on the compiled app shows ridiculous numbers for the app's minimum
and suggested size. Opening up the app in ResEdit or Resorcerer shows that
various resources have erroneous sizes. Trashing and recompiling never
works. The only solution is to restart the Mac. The problem then may not
come back for a few hours or a day or two of compilation. Then it's back
with a vengence.

Going back to 7.5.1 completely cures the problem.

The other problem reports with resource forks and 7.5.3 that I've seen
have all involved people running the Iomega Zip drive extension. That's
not the case on my machine, which has FWB HDT 1.8S on all disks (no mixed
disk drivers either, another commonly rumored source of problems with
7.5.3) I also don't experience problems with any program other than
CodeWarrior (which means I don't suffer from the often reported problem
with Stuffit Expander on 7.5.3).

I reported this problem right after 7.5.3 was released. It has not been
fixed in any of the 1.6 updates. The only solution I've found is to run
7.5.1 when doing program development. Under 7.5.1 CW is 100% stable. Under
7.5.3 I get the resource file problem, and the occasional bomb.

--
Mary Stewart on usenet:
wisdom dragged at mockery's chariot wheels

For a good time, visit http://www.veryComputer.com/

I made a few chaanges to my code (adding some files, changing
appropriate lines) using 1.6.2, and compiled everything successfully;
however, when I went to run the program, I got a
"Cannot run program, resource not found".  The Finder verifies this
(a -192 error when I try to run it).  This is before the de*
can even do anything about it (that it, it doesn't seem to  be a code
error, but a startup problem).  

Taking the made file into ResEdit caused ResEdit to yell about
a corrupted file; it could only recover a handful of the resources in
the file.  Norton verifies this, but does not report anything else
seriously wrong with the drive that this project and program runs on.

I recompiled after removing binaries twice, to two different filenames,
but same result.

This problem just suddenly arose; there have been no changes to my
system folder or the like between the last time the project file
was used and now.  

Can anyone help?  

--
Michael K. Neylon, UM ChE Grad | "Look! Every time I move my arm, it

A!, PatB, F!, MST, ST, DW      |  Look!...$42...$84..." - SGC2C
        http://www.veryComputer.com/~mneylon

 >
 >>I made a few chaanges to my code (adding some files, changing
 >>appropriate lines) using 1.6.2, and compiled everything successfully;
 >>however, when I went to run the program, I got a
 >>"Cannot run program, resource not found".  The Finder verifies this
 >>(a -192 error when I try to run it).  This is before the de*
 >>can even do anything about it (that it, it doesn't seem to  be a code
 >>error, but a startup problem).  
 >
 >Let me guess -- you're running 7.5.3, right?
 >
 >I've seen this happen again and again when running 7.5.3. During
 >compilation the resource map of the file being compiled gets screwed up.
 >What I typically get is a "not enough memory to run" error. Doing a Get
 >Info on the compiled app shows ridiculous numbers for the app's minimum
 >and suggested size. Opening up the app in ResEdit or Resorcerer shows that
 >various resources have erroneous sizes. Trashing and recompiling never
 >works. The only solution is to restart the Mac. The problem then may not
 >come back for a few hours or a day or two of compilation. Then it's back
 >with a vengence.
 >
 >Going back to 7.5.1 completely cures the problem.
 >[SNIP]

I had this exact same problem and updating my hard disk driver cured it. I
was using an older version of Silver Lining. When I updated to the latest
version the problem disappeared.

-Harold

--------------------------------------------------------------
Harold Ekstrom
the ag group, inc.
<ftp://ftp.aggroup.com/>
<http://www.veryComputer.com/;

Quote:>I made a few chaanges to my code (adding some files, changing
>appropriate lines) using 1.6.2, and compiled everything successfully;
>however, when I went to run the program, I got a
>"Cannot run program, resource not found".  The Finder verifies this
>(a -192 error when I try to run it).  This is before the de*
>can even do anything about it (that it, it doesn't seem to  be a code
>error, but a startup problem).  

--
Michael K. Neylon, UM ChE Grad | "Look! Every time I move my arm, it

A!, PatB, F!, MST, ST, DW      |  Look!...$42...$84..." - SGC2C
        http://www.veryComputer.com/~mneylon

I've had exactly this problem from time to time for some time (Even CW8).
When I build a 68k version of my App and then have a look in Resourcerer
at the CODE resources the CODE resource with ID 0 appears to be some
amazing size.

Resourcerer also spits the dummy to some extent, apologising for internal
errors etc.

Deleting the executable file, removing objects, and re-making doesn't seem
to help, but re-starting my Mac before re-making seems to fix the problem,
so presumably the MW linker is trashing something in the system around the
time it's generating the startup code in CODE 0.

I've never been able to reproduce this enough to report a bug, and frankly
I suspected it was some problem with my system.

Peter

You might want to run something like Norton's Disk Doctor on your drives,
zap your PRAM, rebuild your desktop (and a good clean rebuild, like with
TechTool...cause if your desktop is fubar, cmd-opt will keep it fubar).

maybe even consider doing a CLEAN reinstall of your system software
(tho try to leave this as a final possibility).

you also might want to make sure that your disk drivers are working and
up to date.  compatable with SCSI Manager 4.3 (might not directly be
the issue, but can't hurt to  have it anyways), you're careful about
having blind writes on or off (especially if you've upgraded your
processor in some way), etc etc.

just be sure EVERYTHING is up to date and in working order...that's
about the best you can do.

Someone told me that CodeWarrior tends to act like a canary in a mine
shaft.  If you start to see really funky problems while using CodeWarrior
(and they are not a bug with/in CodeWarrior), then it's probably a good
forewarning to you that something is amiss in your system and sooner or
later, it'll manifest itself in other, more painful ways.

--

Family Man               | Business:   none of your business :)
Shareware Author         | WWW:        <http://www.veryComputer.com/~hsoi/>
MacOS Developer/Geek     | "What lasagna? THAT lasagna" - Ajax

NOTE: My email address and WWW URL are new!  Please update your
references.