Author Topic: Tacit/Kelly...  (Read 1979 times)

Offline Dreambird

  • TS Addict
  • *****
  • Posts: 5191
  • Meet The New Boss
    • View Profile
Tacit/Kelly...
« on: October 25, 2003, 06:10:49 PM »
I have OS9.1 on my Pismo that was originally installed from a full install OS9.1 CD... I never went the 9.0.4>9.1 downloadable upgrade route. Now I find that if I try to do a clean system install I choose the option "Perform Clean Install"... it starts up fine and goes for a time and then declares "Big System Morsels cannot be initialized. Installation will not continue." End of story... I cannot do a clean system on this machine, nor could I when I tried it on the Lombard which had OS8.6 on it. I finally just ran OS9.1 right over top of OS8.6 on that one... luckily it took OK.

What's up with that?...  huh.gif
It never happened with the OS8.6 CD...

 thanx.gif
******
On permanent walk-about... ;)
MacBook Pro Retina, mid-2012, SSD 500GB, 16GB RAM, High Sierra 10.13.6, iPad Air 2, iOS 11.4.1

Offline bobw

  • TS Addict
  • *****
  • Posts: 611
    • View Profile
    • http://

Offline Dreambird

  • TS Addict
  • *****
  • Posts: 5191
  • Meet The New Boss
    • View Profile
Tacit/Kelly...
« Reply #2 on: October 25, 2003, 10:15:35 PM »
Thanks for the links bobw... they do shed a little light on what might be happening, but I'm not sure if they apply to me or not...

They specify OS9.0 to OS9.0.4 in one article and the OS9.1 to OS9.2.2 downloadable upgrades in the other. Also I have no trouble installing OS9.1 from my CD on a clean HD or over another OS like I did with OS8.6 on the Lombard to upgrade it.

That all goes off w/o a hitch, it's just when I try to install a clean system folder... so that it would leave me with a previous system folder to merge with a new one.

I don't know if it makes any difference but the error I get is that Big System Morsels can't be "initialized", not a problem reading it.

No external devices attached when doing this... both machines have more RAM installed Kingston 256mb in the Pismo and Transcend 128mb in the Lombard along with the original 64mb Apple.

It seems to me the thing is hanging up on something to do with what's already installed on the HD and not giving me that clean system folder... if I'm making any sense...  wacko.gif
******
On permanent walk-about... ;)
MacBook Pro Retina, mid-2012, SSD 500GB, 16GB RAM, High Sierra 10.13.6, iPad Air 2, iOS 11.4.1

Offline kelly

  • TS Addict
  • *****
  • Posts: 17035
    • View Profile
    • http://
Tacit/Kelly...
« Reply #3 on: October 26, 2003, 07:13:44 AM »
Sure you're making sense. smile.gif

Don't know what it is.

Disk not dirty or scratched?

No Anti-Virus or Security setup running?

I once got around a problem like this by dragging the Installer to the Hard Drive.

It's an Application itself. I gave it more Memory. smile.gif
kelly
Veteran SuperUser

Offline Dreambird

  • TS Addict
  • *****
  • Posts: 5191
  • Meet The New Boss
    • View Profile
Tacit/Kelly...
« Reply #4 on: October 26, 2003, 05:37:55 PM »
Well, glad I make sense, even if in a weird sort of way! smile.gif

I generally boot from the system CD to do these things, so no... there shouldn't be any AV or security programs running... CD looks fine, clean... no scratches, just the usual little fine lines that most have. In any case it doesn't seem to interfere with a complete install... just if I want only a clean system folder.

One of the articles suggests dragging the Big System Morsel from the CD to the root level of the HD... I haven't tried that yet.

There's two what look like installers on the CD "Mac OS Install" (that one has a memory one could change I suppose if it were on the HD) and another one called "Install Mac OS9.1" which appears to be only a document.
******
On permanent walk-about... ;)
MacBook Pro Retina, mid-2012, SSD 500GB, 16GB RAM, High Sierra 10.13.6, iPad Air 2, iOS 11.4.1

Offline tacit

  • TS Addict
  • *****
  • Posts: 1628
    • View Profile
    • http://www.xeromag.com/
Tacit/Kelly...
« Reply #5 on: October 26, 2003, 10:00:03 PM »
I had this problem once; the solution was to zap the PRAM.

This problem may indicate corrupt or unreadable information in PRAM. Zapping the PRAM rewrites this information with default values. In particular, it seems that this error may occur if the information regarding the status of AppleTalk can't be determined fromthe PRAM by the installer.
A whole lot about me: www.xeromag.com/franklin.html

Offline Dreambird

  • TS Addict
  • *****
  • Posts: 5191
  • Meet The New Boss
    • View Profile
Tacit/Kelly...
« Reply #6 on: October 27, 2003, 01:10:15 AM »
Thank-you... Tacit!  biggrin.gif

I zapped the PRAM and installed a clean system folder, no problem...  thumbup.gif  notworthy.gif
******
On permanent walk-about... ;)
MacBook Pro Retina, mid-2012, SSD 500GB, 16GB RAM, High Sierra 10.13.6, iPad Air 2, iOS 11.4.1