Path: utzoo!utgpu!watmath!watdragon!rose!sbmueller
From: sbmueller@rose.waterloo.edu (stephler();)
Newsgroups: comp.sys.amiga
Subject: Using BLINK to remove debug hunks from executables
Keywords: BLINK REMOVE DEBUG HUNKS EXECUTABLES
Message-ID: <14917@watdragon.waterloo.edu>
Date: 6 Jul 89 03:49:33 GMT
Sender: daemon@watdragon.waterloo.edu
Distribution: comp
Lines: 15

So yesterday I decided to make some room on my boot disk by running the
executables on it through BLINK with the NODEBUG option.  Very nice
job, I actually saved *8* whole disk blocks, because very few of the
executables actually had any debug hunks to remove.  Those that did
were mostly stock C-A commands.  My question of the day:  is there any
problem applying BLINK to such things as device drivers, libraries,
handlers and printer drivers?  I can't see there being any problem, but
before I do anything I might regret, I thought I'd ask around...  I
guess all of these things are loaded with LoadSeg() and presumably it
throws the debug hunks out when loading anyway, so there should be 
0 difference in what actually gets into memory at load time.  Thanx
for any info...

stephler();
.sig on vacation