Trying to Install maciNTosh (Windows NT) on My Pismo

[CC_333]

I got it partitioned and the bootloader up and running. I choose "Run a program" and type "cd:\ppc\setupldr" and setup starts, but all "other" options seem to result in an error that references a line 913 in a .c file (I don't recall the path).

Why is this? Is the burned copy of NT 4 Workstation I downloaded today defective somehow?

c

 

[adespoton]

Which build of NT4 did you download? I presume you got a PPC build, but there were a number of builds, some of which were VERY hardware-constrained.

 

[CC_333]

I just got whatever was on WinWorldPC, because I thought that all the early releases had all supported architectures on one disk. Perhaps I was mistaken? I'll look around for other copies that might be more proper for this purpose (I have a commercially-made NT 4 Workstation CD that came with a copy of Visual Basic, but it's in storage somewhere).

In the meantime, I'm trying to get also Mac OS and Mac OS X installed (I'm going to try triple booting NT, NewWorld Mac OS 7.6, and Mac OS X, which probably has never been done successfully before), but I can't seem to get anything to see the two HFS partitions I created in the NT bootloader (in addition to the NT partition, there's one for Mac OS 7/8/9, and one for Mac OS X). The Mac OS X installer DVD sees them, and Disk Utility lets me format them, but the installer won't install to either of them because it says they aren't bootable. Mac OS 9 doesn't see them at all, so that's a no-go as well.

What am I doing wrong?

c

 

[adespoton]

Do you have a driver partition on the same volume as those partitions? The boot manager needs to be able to write which boot path is blessed to the driver partition.
I suspect there may also be an issue of booting off of HFS AND booting off of HFS+. I haven't got around to following in your footsteps yet though -- possibly over Christmas I'll get around to trying to boot my G4 Mini into Snow Leopard PPC AND Mac OS 7.5.3 AND NT4.... I'm hoping that some of these hurdles will have been overcome by then

 

[CC_333]

Do you have a driver partition on the same volume as those partitions? The boot manager needs to be able to write which boot path is blessed to the driver partition.

I thought the NT bootloader was supposed to create that automatically?

In, for instance, Mac OS 9, can I simply update the disk drivers via Drive Setup like normal without trashing all the NT stuff? Or is there a special procedure I need to follow?

I suspect there may also be an issue of booting off of HFS AND booting off of HFS+.

I patched my CHRP 7.6 installation for HFS+, from which it seems to boot quite happily, so I'm formatting everything HFS+ for simplicity.

c

 

[joevt]

In, for instance, Mac OS 9, can I simply update the disk drivers via Drive Setup like normal without trashing all the NT stuff? Or is there a special procedure I need to follow?

The hard drive should have the Mac OS 9 drivers when it's first formatted so that there's sufficient room to keep them all.
I suppose one could try moving partitions to make room for the drivers (just needs 1824 blocks for all of them).
Try iPartition.app 3.3.1 in Mac OS X 10.4?

Use my dumpvols.sh script in Mac OS X to gather more info
https://gist.github.com/joevt/a99e3af71343d8242e0078ab4af39b6c

pdisk -l /dev/disk21

Partition map (with 512 byte blocks) on '/dev/disk21'
 #:                type name               length   base      ( size )
 1: Apple_partition_map                        63 @ 1        
 2:      Apple_Driver43*Macintosh              56 @ 64       
 3:      Apple_Driver43*Macintosh              56 @ 120      
 4:    Apple_Driver_ATA*Macintosh              56 @ 176      
 5:    Apple_Driver_ATA*Macintosh              56 @ 232      
 6:      Apple_FWDriver Macintosh             512 @ 288      
 7:  Apple_Driver_IOKit Macintosh             512 @ 800      
 8:       Apple_Patches Patch Partition       512 @ 1312     
 9:           Apple_HFS MacOS9.1          2097152 @ 1824      (  1.0G)
10:           Apple_HFS MacOS9.2          2097152 @ 2098976   (  1.0G)
11:           Apple_HFS MacOS9.2.2        2097152 @ 4196128   (  1.0G)
12:          Apple_Free                    262144 @ 6293280   (128.0M)
13:           Apple_HFS System7.5.3       1835008 @ 6555424   (896.0M)
14:           Apple_HFS System7.5.5        409600 @ 8390432   (200.0M)
15:           Apple_HFS System7.6.1        614400 @ 8800032   (300.0M)
16:           Apple_HFS MacOS8.0           614400 @ 9414432   (300.0M)
17:           Apple_HFS MacOS8.1           614400 @ 10028832  (300.0M)
18:           Apple_HFS MacOS8.5           614400 @ 10643232  (300.0M)
19:           Apple_HFS MacOS8.5.1         614400 @ 11257632  (300.0M)
20:           Apple_HFS MacOS8.6           614400 @ 11872032  (300.0M)
21:          Apple_Free                  14773192 @ 12486432  (  7.0G)
22:           Apple_HFS Jaguar           16778400 @ 27259624  (  8.0G)
23:          Apple_Free                       160 @ 44038024 
24:           Apple_HFS Panther          31457280 @ 44038184  ( 15.0G)
25:           Apple_HFS Tiger            62914560 @ 75495464  ( 30.0G)
26:          Apple_Free                    267616 @ 138410024 (130.7M)
27:           Apple_HFS Misc8            95764008 @ 138677640 ( 45.7G)

 

[CC_333]

I gave up for now, because I couldn't get anything to work.

So for now, I'm setting it up as stock with the original 9.0.4 (I learned that apparently, when Apple updated the firmware, they broke compatibility with a couple features when running 9.0.4 or below: brightness control, and clamshell mode.

I wonder what resources those features are part of, and if the equivalents from 9.1 and up can be transplanted onto 9.0.x to restore it to full functionality?

c

 

[adespoton]

Ah; and hence your questions regarding ROMs. General rule is: you need a ROM version that matches or is later than the one that came with the OS version. Unfortunately, as things progressed, some features got stripped from later ROMs.

It'd be really great if we could eventually get to the point where we could break out all the ROM components so that people could build their own custom ROM containing the hardware features and OS features needed -- but we're nowhere near there right now (although I think we're getting further at understanding how the components interact with the OS and hardware, and how you can load new components in/patch old components out).