[ofw] WinOF RC5 available for testing.

Jeremy Enos jenos at ncsa.uiuc.edu
Tue Jun 5 18:35:35 PDT 2007


I see... guess I jumped in too fast before reading.  I was able to 
'update' the driver to my 614 version again and it cleared the flags.  
However, I still don't see any service set up and Windows Open Fabrics 
isn't present in the add/remove programs list either.  Perhaps that's a 
result of my first slip up, neglecting to uninstall the other drivers 
first.  I don't know what the device manager uninstall context actually 
implies though anyway... I can certainly find files still present in the 
OS from the driver I uninstall if I ever do try that route.  I had hoped 
that this installer would clean up the cruft along the way.  (I haven't 
verified that it doesn't yet)

On another host, I did see the entry in add/remove programs after 
install, but still no opensm service listed in services.  It also failed 
to install the driver properly.  The device manager instance completely 
disappeared, and in the Add Hardware dialogue, I can get information on 
the device basically telling me that it's registry entry has a problem 
again.  Perhaps I need to manually clear the registry entries related to 
OpenIB to get a clean start again?

    Jeremy

Smith, Stan wrote:
> Per Release Notes - remove existing openib-windows installation prior to
> installing WinOF. Otherwise you have entered into a somewhat problematic
> realm; similar installations although Windows sees them as different due
> to differing GUIDs.
>
> The fact that the existing installation was not detected 'is'
> troublesome.
>
> Are you sure your system didn't automatically reboot upon detection of
> an existing openib-windows installation? The existing install notifier
> will timeout and reboot. Coffee break during install?
> The reason I ask is the existing installation was working as of RC2;
> specifically tested against svn.614 & svn.566.
>
>
>
> Jeremy Enos wrote:
>   
>> Just working with the interactive install to start with  (RC5).  I
>> installed on top of a working 614 installation, and after I reboot,
>> the "Infiniband Fabric" system device has a caution flag with this
>> device status:
>> ---------------------------
>> Windows cannot start this hardware device because its configuration
>> information (in the registry) is incomplete or damaged. (Code 19)
>>
>> Click Troubleshoot to start the troubleshooter for this device.
>> ---------------------------
>>
>> Of course, no IPoIB adapters since the fabric device is not working.
>>
>>     Jeremy
>>
>> Smith, Stan wrote:
>>     
>>>  http://www.openfabrics.org/~woody/WinOF_1.0/WinOF_1-0_RC5.zip
>>>
>>>
>>> Changes since WinOF RC3 [RC4 was a flash in the pan]
>>> ----------------------- 
>>>
>>> 1) Folder \Program Files\WinOF is, once again, correctly removed
>>> during uninstall. 
>>>
>>> 2) Mysterious file delete/Installer error resolved.
>>>
>>> 3) OpenSM is installed as a disabled Windows service. A Custom
>>>    install selecting the 'OpenSM_service_enabled' will enable
>>> automatic OpenSM service start. 
>>>
>>> 4) WinOF.x86 will not install on x64, WinOF.x64 will not install on
>>> x86. 
>>>
>>> 5) Uninstall WinOF now uses contents of Add/Remove Programs
>>>    uninstall registry entry, instead of calling ARP.
>>>
>>> 6) Local Area Connections created by IPoIB are correctly uninstalled
>>> for both XP and Win2K3. 
>>>
>>> 7) Updated Release Notes.
>>> _______________________________________________
>>> ofw mailing list
>>> ofw at lists.openfabrics.org
>>> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
>>>       



More information about the ofw mailing list