pa1743@sdcc13.ucsd.edu (Jethro Bodean) (02/23/90)
I booted up and some of my inits had turned into documents and didn't install themselves. Any thoughts - I've never heard of this - is it not something to be alarmed of - other than having to simply find my original inits again??? Help? Any news on this?? -tk pa1743%sdcc13@ucsd.edu
rcoahk@chudich.co.rmit.oz (Alvaro Hui Kau) (02/23/90)
From article <7696@sdcc6.ucsd.edu>, by pa1743@sdcc13.ucsd.edu (Jethro Bodean): > > I booted up and some of my inits had turned into documents > and didn't install themselves. Any thoughts - I've never heard of > this - is it not something to be alarmed of - other than having to > simply find my original inits again??? Help? > Any news on this?? Did you have INIT cdev in your system folder?? if you have, go to the control panel, select init cdev and turn all the init on! Or you can use a utility like desktop to change the type of your inits to INIT. (INIT must be in capital letter!) Hope this help. akkh@mullian.ee.mu.oz.au.
rc3h+@andrew.cmu.edu (Ross Ward Comer) (02/23/90)
pa1743@sdcc13.ucsd.edu (Jethro Bodean) writes: > I booted up and some of my inits had turned into documents > and didn't install themselves. Any thoughts - I've never heard of > this - is it not something to be alarmed of - other than having to > simply find my original inits again??? Help? > Any news on this?? > -tk > pa1743%sdcc13@ucsd.edu The problem is actually a feature of a program called "init cdev". This cdev lets you control which inits are run on startup. Unfortunately, it controls the inits by changing their type from init to a plain document. The way around this is to fire up "init cdev" and highlight those inits (which will be unhighlighted). There are other programs with similar features (Aask comes to mind, among others) which may also be causing this problem. The fix is the same. ross rc3h@andrew.cmu.edu
herbw@midas.WR.TEK.COM (Herb Weiner) (02/24/90)
INIT CDEV and related utilities disable INITs (and cdevs and rdevs) by changing their type. This causes the INITs to loose their ICONs and display as generic documents. I would like to suggest that all INIT (cdev/rdev) authors include an extra ICON in their INIT. This extra ICON would be the same as the normal ICON with an X through it. Then, when INIT CDEV (or other utility) disables the INIT, the ICON would change to an ICON with an X through it, rather than changing to a generic document ICON. For INIT CDEV, the correct file types are: Enabled type: Disabled type: INIT xNIT cdev xdev RDEV xDEV Can anyone confirm whether other utilities use the same file type to disable INITs? If not, the BNDL and FREF resources would have to handle multiple disable types. If you agree that this is a good idea, please help by: 1. Supplying type information for relatives of INIT CDEV. 2. Forwarding this suggestion to INIT authors and other Bulletin Boards. Herb Weiner (herbw@midas.WR.TEK.COM) AppleLink D0521
ebert@arisia.Xerox.COM (Robert Ebert) (02/24/90)
In article <1928@wrgate.WR.TEK.COM> herbw@midas.WR.TEK.COM (Herb Weiner) writes: >INIT CDEV and related utilities disable INITs (and cdevs and rdevs) by >changing their type. This causes the INITs to loose their ICONs and >display as generic documents. > >I would like to suggest that all INIT (cdev/rdev) authors include an >extra ICON in their INIT. This extra ICON would be the same as the >normal ICON with an X through it. Of course, the correct way to do it would be for the init handler authors (or other interested bodies) to write the code that adds the new icons to the desktop for the new file types, and make it part of the init handling hack. That way writers of other hacks wouldn't be burdened with having to create their own icons for such a specialized case. It is a neat idea, though. --Bob
wiseman@tellab5.tellabs.com (Jeff Wiseman) (02/27/90)
In article <7696@sdcc6.ucsd.edu> pa1743@sdcc13.ucsd.edu (Jethro Bodean) writes: > > I booted up and some of my inits had turned into documents Do you happen to have an "Init turn-er off-er" such as init cdev or Aask? That can produce this effect. Hope this helps. -- Jeff Wiseman: ....uunet!tellab5!wiseman OR wiseman@TELLABS.COM
lsr@Apple.COM (Larry Rosenstein) (02/27/90)
In article <6653@arisia.Xerox.COM> ebert@arisia.Xerox.COM (Robert Ebert) writes: > In article <1928@wrgate.WR.TEK.COM> herbw@midas.WR.TEK.COM (Herb Weiner) writes: > >INIT CDEV and related utilities disable INITs (and cdevs and rdevs) by > >changing their type. This causes the INITs to loose their ICONs and > >display as generic documents. > > Of course, the correct way to do it would be for the init handler authors > (or other interested bodies) to write the code that adds the new icons Actually, it isn't necessary to change the type of the INIT file. There is a file attribute that indicates whether the file contains INITs. Clearing that bit is enough to ensure that the INIT isn't loaded at boot time. Larry Rosenstein, Apple Computer, Inc. Object Specialist Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr AppleLink: Rosenstein1
Leo.Bores@f14.n114.z1.fidonet.org (Leo Bores) (02/27/90)
In an article of <22 Feb 90 18:51:53 GMT>, pa1743@sdcc13.ucsd.edu (Jethro
Bodean) writes:
JB> I booted up and some of my inits had turned into documents
JB>and didn't install themselves. Any thoughts - I've never heard of
JB>this - is it not something to be alarmed of - other than having to
JB>simply find my original inits again??? Help?
JB> Any news on this??
Try starting up your system again with the option and "clover-leaf" keys held
down. You will be asked if you wish to rebuild the desktop. Click "OK". THis
will remove any comments that you may have placed in certain application "info"
windows but may also solve your problem. Do you have AASK running?
Leo Bores
--
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!14!Leo.Bores
Internet: Leo.Bores@f14.n114.z1.fidonet.orgphaedrus@milton.acs.washington.edu (The Wanderer) (02/27/90)
In article <6913@internal.Apple.COM> lsr@Apple.COM (Larry Rosenstein) writes: >Actually, it isn't necessary to change the type of the INIT file. There >is a file attribute that indicates whether the file contains INITs. >Clearing that bit is enough to ensure that the INIT isn't loaded at boot >time. Really? Which attribute is that? I don't see it in any of the file- attribute-changers I have. There's an "Inited" attribute, but it doesn't have anything to do with whether there's INITs in the file; that attribute just means that the Finder's had a chance to look at the file and position it in a window and/or add its BNDL info to the Desktop. At least, all my documents I've checked had the Inited bit set (and I certainly hope they don't all have INITs in them... that must be some virus... :) ), and clearing the Inited bit in a few of my INITs didn't stop them from loading. Anyway, could you point me to the documentation of this? I'll probably be writing a few INITs shortly, and it would be very nice if they loaded... :) >Larry Rosenstein, Apple Computer, Inc. >Object Specialist > >Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr >AppleLink: Rosenstein1 -- Internet: phaedrus@u.washington.edu (University of Washington, Seattle) The views expressed here are not those of this station or its management. "If you can keep your head while those about you are losing theirs, consider an exciting career as a guillotine operator!"
russotto@eng.umd.edu (Matthew T. Russotto) (02/27/90)
In article <2152@milton.acs.washington.edu> phaedrus@milton.acs.washington.edu (The Wanderer) writes: >In article <6913@internal.Apple.COM> lsr@Apple.COM (Larry Rosenstein) writes: > >>Actually, it isn't necessary to change the type of the INIT file. There >>is a file attribute that indicates whether the file contains INITs. >>Clearing that bit is enough to ensure that the INIT isn't loaded at boot >>time. > > Really? Which attribute is that? I don't see it in any of the file- >attribute-changers I have. Neither 'shared' nor 'invisible' INITs will be loaded. -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu ][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?
lsr@Apple.COM (Larry Rosenstein) (02/28/90)
In article <2152@milton.acs.washington.edu> phaedrus@milton.acs.washington.edu (The Wanderer) writes: > Really? Which attribute is that? I don't see it in any of the file- > attribute-changers I have. There's an "Inited" attribute, but it doesn't ResEdit 1.2 has a bit labeled "No Inits". I'm not sure which bit this represents in the file attributes. Larry Rosenstein, Apple Computer, Inc. Object Specialist Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr AppleLink: Rosenstein1
wiseman@tellab5.tellabs.com (Jeff Wiseman) (02/28/90)
In article <6653@arisia.Xerox.COM> bebert.osbunorth@xerox.com (Bob Ebert) writes: >In article <1928@wrgate.WR.TEK.COM> herbw@midas.WR.TEK.COM (Herb Weiner) writes: >>INIT CDEV and related utilities disable INITs (and cdevs and rdevs) by >>changing their type. This causes the INITs to loose their ICONs and >>display as generic documents. >> [stuff deleted] > >Of course, the correct way to do it would be for the init handler authors >(or other interested bodies) to write the code that adds the new icons >to the desktop for the new file types, and make it part of the init Oooohh neat! And maybe it could somehow be worked into the startup display in the same way! Since I normally use only about 4 or 5 of the 20 inits in my system folder, I could get'em ALL to show up with Iconwrap or something. (Course then, someone might have to write an Icon-page-wrap type init :-) -- Jeff Wiseman: ....uunet!tellab5!wiseman OR wiseman@TELLABS.COM