Selective Install Hangs

World         Australia | Europe | North America | Singapore
Europe Austria | Birmingham | Budapest | France | Italy | London | Switzerland | TeamOS/2 (Germany)
North America Berkeley | Chattanooga | Minnesota | Nova Scotia | Ontario | Pennsylvania | TeamOS/2
Last update: 6th August, 1995

Symptoms

Machine hangs during initialisation of selective install program.

Hardware

ThinkPad 755Cs

Perhaps other hardware too.

Cause

During initialisation, selective install runs the executeables in \os2\drivers. Why? According to IBM APAR PJ17752 this is done in order to check the existence of certain SCSI adapters &/or devices. It would appear that one of these executeables can cause selective install to stop OS/2 dead under certain (unspecified) circumstances.

Procedure

Notes

I noticed that having successfully run Selective Install once and moving the .EXE's back to their original location I was able to run Selective Install again without problems. Maybe Selective Install was looking for a SCSI adapter that had been previously installed but had since been removed by other means? Perhaps. Who knows? In any case, removing those EXEs temporarily seemed to fix the problem.

I am not sure what implications moving the .EXEs has for the Selective Install process. If you are not attempting to do anything with SCSI devices it probably doesn't matter. If you are, it might be a good idea to shutdown Selective Install, move the EXEs back to their original location then restart Selective Install a second time.


The Warp Pharmacy | News | Hardware | Software | Symptoms | Procedures | References | Commerce | Search | More Help!!! ]