World Australia | Europe | North America | SingaporeLast update: 6th August, 1995
Europe Austria | Birmingham | Budapest | France | Italy | London | Switzerland | TeamOS/2 (Germany)
North America Berkeley | Chattanooga | Minnesota | Nova Scotia | Ontario | Pennsylvania | TeamOS/2
Perhaps other hardware too.
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.
MKDIR \OS2\TMPDRVRS
MOVE \OS2\DRIVERS\*.EXE \OS2\TMPDRVRS
MOVE \OS2\TMPDRVRS\*.EXE \OS2\DRIVERS
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.