Found the issue w/System601 & AppleTalk installing itself

["AMart79196@gmail.com" <AMart79196@gmail.com>]

I did a bunch of installs and watched each file go in.
I narrowed the problem down to when I installed the driver for
LASERWRITER.  In the installer, its listed as Printers: Laserwriter.
Its NOT listed as Network: Laserwriter or Printer: ATalk laserwriter.
So, I figured it was time to read the script and since I couldn't do
it in GS/OS, (anyone know a program that I could have viewed this
file??) I decided to go over to the trusty WinBlows computer (this one
I am typing on now) and open up a SHK of Disk1 "Install" of the Sys601
disks.  CiderPress will allow me to view inside the archive.  Once
inside, I looked for Scripts.
I opened up the script for LASERWRITER.....please reference it below---
SORRY for the long post due to the C/P of the script....whos paying
for the bandwidth anyway?!?!

So, this is the normal file that causes this NAG screen and all the
unnecessary appleShare/appletalk files to load.  I see no reason for
these files to EVER load unless the user wants them to be loaded.  I
only believe, UNLESS I AM TERRIBLY MISTAKEN, that only the standard
files (i think they are printer, modem, directconnect, and the printer
that you chose to install, and in this case would be laser) for any
printer driver from the scripts get loaded when you choose
"Printer:Laserwriter" from the installer.

Well, I would be bold to get into separating the scripts, seeing if
these files are loaded via any network scripts and it so, just edit
this script just for what it was originally intended for...again,
unless i am totally mistaken...meaning...you need all of these non-
sense appletalk files to take up space and be loaded when you are only
trying to load a driver for a printer.--a DIRECTconnect printer..

Can anyone tell me, before I start making a big project out of all of
this, if it is totally necessary that those other files get loaded to
MAKE the Laserwriter run??  If not, then I truly believe that whom
ever compiled the script (Apple) or someone else screwed up. If they
didn't screw up, then I am truly sorry that I wasted my time trying to
track down why this happens...but at least I will have learned
something today!  Thanks guys..

below is two scripts...the one immediately below is the one found on
the install disk of system601 which causes appletalk and its
components to load when trying to just load the laserwriter driver
into gs/os.  The script below that is my proposed fix...unless, again,
you MUST have these files loaded into your gs/os in order for a
laserwriter to work.

----------------------------------------first script which is on
sys601 install disk-------------------------------------
SCRIPT

V2.00

RR2

Printer: LaserWriter
The script RPrinter: LaserWriterS installs the files necessary for you
to use a LaserWriter printer.  The selected disk must be a startup
disk.\\
:SystemTools2~*

~:::Workspace:::
4




System:System.Setup:ATPatch
~:::Workspace:::
4




System:System.Setup:ATROM
~:::Workspace:::
4




System:System.Setup:ATSetup
~:::Workspace:::
4




System:System.Setup:ATStart
~:::Workspace:::
4




System:System.Setup:PFILoad
~:::Workspace:::
4




System:System.Setup:SPLoad
~:::Workspace:::
4




System:Drivers:ATP3.SPLoad
~:::Workspace:::
4




System:Drivers:ATP2.ATPatch
~:::Workspace:::
4




System:Drivers:ATP4.PFILoad
~:::Workspace:::
3




System:CDevs:ATLWriter
~:::Workspace:::
4




System:Drivers:ATP5.ATStart
~:::Workspace:::
2



System:Drivers:ATalk
System:Drivers:ATalk
~:::Workspace:::
2



System:Drivers:SCC.Manager
System:Drivers:SCC.Manager
~:::Workspace:::
2



System:Drivers:ATP1.ATROM
System:Drivers:ATP1.ATROM
~:::Workspace:::
2



System:Drivers:ATP2.ATRAM
System:Drivers:ATP2.ATRAM
~:::Workspace:::
2



System:System.Setup:ATResponder
System:System.Setup:ATResponder
~:::Workspace:::
2



System:System.Setup:ATInit
System:System.Setup:ATInit
~:::Workspace:::
1



System:Drivers:LaserWriter
System:Drivers:LaserWriter
~:::Workspace:::
1



System:Drivers:IWEM
System:Drivers:IWEM
~:::Workspace:::
1



System:Drivers:AppleTalk
System:Drivers:AppleTalk
~:::Workspace:::
1



System:CDevs:NetPrinter
System:CDevs:NetPrinter

-------------------------------------------------------------------------------------------------
end of C/P----------------------------

Now below is my proposed version of what I think it should be.


--------------------------
SCRIPT

V2.00

RR2

Printer: LaserWriter
The script RPrinter: LaserWriterS installs the files necessary for you
to use a LaserWriter printer.  The selected disk must be a startup
disk.\\

:SystemTools1~*

~:::Workspace:::
1



System:Drivers:Laserwriter
System:Drivers:Laserwriter
~:::Workspace:::
1



System:Drivers:Printer
System:Drivers:Printer
~:::Workspace:::
1



System:Drivers:Modem
System:Drivers:Modem
~:::Workspace:::
1



System:CDevs:DirectConnect
System:CDevs:DirectConnect
~~

--------------------------------------------------end of my proposed
script--------------------------------------------

If anyone wants to test this out with their Laserwriter, and, if in
fact the Laserwriter really doesn't need those extra files, I will
make a script and compile everything into the install disk, shrink it
up, and send it off to anyone that wants to test.---again, only if the
laserwriter will work without all those extra files.

I do know that when you install on a HD, some appletalk files will be
installed and maybe some of the ones that are present in this script,
But I know for sure not all (check the scripts to see what does get
installed).  Now, I know this for SURE, that when you do that top
option in the installer from the list, not the easy update, but the
list that it will NOT install the SCC.Manager file which is the file
responsible for the AppleTalk nag screen at boot-up.

Debunking the AppleTalk weirdness.........hopefully I didn't just
completely make a huge mistake here....and if I did, oh well, I will
still have learned something new...