Under System 6, DaynaPORT Installer kept asking me to insert ... itself.

[theirongiant]

I had a strange issue tonight trying to install the DaynaPORT SCSI/Link drivers to use with a BlueSCSI + PicoW on a Macintosh SE.

The internal hard drive has System 7.1, but I also have a 6.0.8 volume on the BlueSCSI.

Booting the SE from the 6.0.8 volume, I added the DaynaPORT 7.5.3 installer to the FloppyEMU and mounted it. Every time I ran the installer, it would ask for the DaynaPORT Installer disk. The very disk from which the installer was running.

I tried copying the DaynaPORT installer files to another BlueSCSI volume, and even to the SE's internal hard disk. No dice; it still asked for the DaynaPORT disk. Notably, the installer did not do this when I only copied the AppleTalk v58.0.0 software; it only complained when I tried to copy the SCSI/Link driver.

My eventual workaround was to boot to System 7.1 on the internal hard disk, and install DaynaPORT to the System 6.0.8 volume. It had no trouble installing it then.

Is this some kind of System 6.0.8 quirk, or something funky with the DaynaPORT installer?

Last year, while doing similar things for #Marchintosh, I tried to use the BlueSCSI Wi-Fi on another Mac that already had some previous network driver installed. The network drivers apparently get injected into the System suitcase—this is definitely true for the DaynaPORT, where it becomes .ENET in the DRVR resource—and you're only supposed to have one driver loaded at a time this way.

Is the odd install disk behavior related to the driver injection sequence? If so, how and why?

 

[shirsch]

I think this is a known issue with the DaynaPORT installer. It needs to be mounted from the active desktop.

 

[mikes-macs]

Good thing you figured it out and now it’s documented. There are SO many of these kinds of quirks, it’s tough to remember them all. Especially when you may only need the info every once in a while.