🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.mac
Article #3657

Re: INITPicker, etc. (was Re: INITs clear screen)

#3657
From: Arie Covrigaru
Date: Mon, 28 Aug 1989 16:58
92 lines
4996 bytes
cs.umich.edu> <13363@well.UUCP>
Sender:
Reply-To: arie@zip.eecs.umich.edu.UUCP (Arie Covrigaru)
Followup-To:
Distribution: na
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Keywords: Inits


In article <13363@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:
>>1. Since it doesn't change the type of those files that are disabled, the
>>   control panel will still show a cdev that was actually not loaded.
>>
>       Personally this is a MUCH better method of implementing support for
>Init Management than the file type changing for a couple of reasons. 1) I get
>to keep my Icons on the desktop, 2) I can change values in the cdev's BEFORE I
>reboot and then have to change and reboot AGAIN, and 3) less chance of things
>breaking in the future when Apple changes the rules.
>

I had no intention of starting an argument here but I believe that the net
is for people to give their opinions about products that we use (or try to
use).

But to the point: Personally, I find it disturbing to have so many icons
in the Control Panel when some of them are not loaded.  Now of course I
could remove them from the System Folder but then what is the point of having
something like INITPicker in the first place?  Some CDEVs won't even let you
change the settings if their INIT is not loaded.  It is true that breaking
the rules can cause problems in future systems and I am not saying that
the way init cdev 2.0 is doing it is the best way, it is just that as it is
the end result is that I don't get those icons in the Control Panel and I like
it this way.

>>2. Compare to the init manager "init cdve 2.0" it takes much more time to
>>   load at startup.
>>
>       This is only true if you have it AutoScan on load.  If you turn this
>preference off, than it is FASTER than InitCdev since it DOES NOT scan the
>system folder AT ALL.
>
As far as I understood, if the system is not scanned at start up then I
won't get an updated list of all the INITs/CDEVs I actually have in the
system Folder when I open INITPicker.  If this isn't true,  please correct me.

>>Having those two disadvantages, the only advantage over the free "init cdev 2.
0
>>is that it can control the order in which INITs/CDEVs are loaded.
>       You also forgot that you have a number of preferences that can be
>changed about the operation of the product (which init cdev does not) and even
>more importantly, you have support!  If you should find any problems with the
>product, or have questions/comments/suggestions, MicroSeeds has a phone number
>where you can call and get this support (the author is also on the net so you
>can send him mail directly).
>
Yes, you do have support for INITPicker if you need it, I won't argue with
that.  For me this is not a consideration when choosing such a utility. Its

>(I am not trying to put down Init cdev, as it have used it in the past and find
>it to be an EXCELLENT product - I simply want to pseudo-flame this previous
>poster for his comments and to correct errors.)
>
>> This doesn't seem to be a good enough reason to charge money for such a
>>utility when a comparable free utility exists.
>>
>       Then don't buy it!  No one is forcing you to buy InitPicker or any
>of the other commercial products.  If you like AppleDraw better than MacDraw,
>don't buy MacDraw, etc.  I have seen people charge for products MUCH LESSS
>useful and supported than INITPicker....
>
Indeed, I returned the product immediately (thanks to the great policy of
MacConnection and the companies that participate in the money back
grantee program).  This doesn't stop me from passing my experience to
other interested parties, as long as it is sincere and with no hidden
intentions.

>>
>       I should also comment that as Scott pointed out previously version 2.0
>of INITPicker has some REALLY nice new features such as sets and 'crash guard'
>and other things on the way...
>
The fact that I tried INITPicker in the first place when I have init cdev 2.0
is because I think that init cdev 2.0 doesn't have all the features I would
like to see in such a tool.  I hope that INITPicker 2.0 will indeed be good
enough and I will probably try it again.

>Disclaimer: I am friends with the author of INITPicker (and Inix, AASK, etc.)
>and have used all of these products at some point as well as helped testing
>them during development.
>
Disclaimer: I have no connection with any of the companies mentioned above
by myself or by Leonard Rosenthol.
Technical Details
Message-ID: <269@zip.eecs.umich.edu>
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!itivax!umich!zip.eecs.umich.edu!arie
References: <1989Aug21.113301.4620@aucs.uucp> <17474@ut-emx.UUCP> <13721@bloom-b

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!itivax!umich!zip.eecs.umich.edu!arie
From: arie@zip.eecs.umich.edu (Arie Covrigaru)
Newsgroups: comp.sys.mac
Subject: Re: INITPicker, etc. (was Re: INITs clear screen)
Message-ID: <269@zip.eecs.umich.edu>
Date: 28 Aug 89 16:58:07 GMT
References: <1989Aug21.113301.4620@aucs.uucp> <17474@ut-emx.UUCP> <13721@bloom-b
Sender: arie@zippy.eecs.umich.edu
Lines: 92