[comp.sys.mac] System 6.0.5 and init cdev

jprice@uclapp.physics.ucla.edu (John Price) (03/21/90)

	I installed system 6.0.5 last night on my Mac+, and I had some 
problems.  I solved them, and in retrospect, I should have forseen them.  
The problems stemmed from (I believe) running init cdev on my hard disk.  
Installer didn't like the fact that Easy Access and Responder were not 
Startup Documents, but Documents.  I think this is due to the way init cdev 
handles startup documents.  This has been talked about before, but I didn't 
listen to most of it :(

	Anyway, I was able to get around this by removing both Easy Access 
and Responder (which I don't use anyway), and replacing them with the new 
copy from the distribution.  Then, Installer worked fine.

	Now, I'm sure that there's a better way...  (here come the flames!)

---------------------------------------------------------------------------
  John Price                   | Internet: price@uclapp.physics.ucla.edu
  5-145 Knudsen Hall           | BITNET:   price@uclaph
  UCLA Dept. of Physics        | DECnet:   uclapp::jprice
  Los Angeles, CA  90024-1547  | YellNet:  213-825-2259
---------------------------------------------------------------------------
             Where there is no solution, there is no problem.

mwilkins@jarthur.Claremont.EDU (Mark Wilkins) (03/22/90)

  Unfortunately, there's no way to make the installer cooperate with init
cdev.  However, that's a feature, not a bug.

  init cdev changes the file types of the files you turn off so that they
aren't opened by init 31 on startup.  Installer won't overwrite a file if
its type is not what it expects, because it must deal with the possibility
that you've just named another file wrongly.  So it asks you to deal with it.

-- Mark Wilkins

ccc_ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) (03/26/90)

It sounds like "init cdev" needs a change in the way it works.

In current versions of the System, there is a flag bit called "no inits"
that you can set, for example with ResEdit 1.2. If the INIT 31 code sees
that this bit is set, it won't try to open the file to execute any INITs
in it (ha ha). It also sets it itself, after opening a file which might
contain INITs, only to find that there aren't any.

I imagine that setting this bit shouldn't upset the Installer.

Lawrence D'Oliveiro
Computer Services Dept, University of Waikato
Hamilton, New Zealand
Mike Murray, Macintosh Marketing Manager, moves to Microsoft.