See the release notes under unattended install/uninstall. stan. ________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Enos Sent: Friday, June 01, 2007 4:55 PM To: [email protected] Subject: Re: [ofw] WinOF 1.0 [RC3] available for test. Unless I've missed it, I've only seen mention of a GUI interactive mode of install. Is there a command line mode? thx- Jeremy Erez Cohen wrote: Stan, my comments below starting with [Erez Cohen]. Best regards, Erez Cohen Field Application Development Manager Mellanox Technologies Ltd. Tel : + 972 - 4 - 9097200 ext 378 Cell : + 972 - 54 - 5468801 Fax : + 972 - 4 - 9593245 www.mellanox.com -----Original Message----- From: Smith, Stan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 29, 2007 8:52 PM To: Erez Cohen; [email protected] Subject: RE: [ofw] WinOF 1.0 [RC3] available for test. <snip...> Erez Cohen wrote: Stan, I think we are getting very close for a release. Most of the issues I've sent where addressed nicely. Few minor issues (tested on Win2K3, 32bit and XP 64bit): 1. During uninstall on Win2K3 32 bit machine I got the enclosed error message. After reboot the HW devices where gone but the WinOF package (as seen in the add remove programs window) was there. I run a second uninstall, this time it worked just fine. If there is an uninstall error, should never be the case, the installer aborts. The last thing the installer does on a successful uninstall is to delete the WinOF directory. More problematic is the why of the error. Was the OpenSM_service features selected? [Erez Cohen] - I'm not sure, I think it did not. Curious - seems there is a race condition. The VBS statement @ line #69 checks for the existence of the file to delete. If line #69 is True, then line #70 deletes the file; Line #70 failed in your case?? Only thing I can imagine is a race condition between control points deleting the same file. This is a mystery as I have never witnessed the behavior. Will investigate further....RC4 here we come. 2. WinOF dir still remains after uninstall on the Win2K3 32bit machines. It was gone on the XP 64bit. Was the feature OpenSM_service selected? [Erez Cohen] - No. Was this an uninstall using RC2 or RC3? RC2 had this problem, which was fixed and verified on 32-bit XP for RC3. I'll see if I can reproduce the failure. Upon re-reading your comment, I realized 32bit Win2K, I do not have a 32bit Win2K3 available for test. Seems really odd the x64 Win2K3 works while the 32bit variant fails on folder removal? Will investigate further. [Erez Cohen] - All installs and uninstalls where with RC3. 3. When choosing typical installation, OSM as service is installed in the "Disable" mode. This prevent it to be started with net start command: I:\>net start opensm System error 1058 has occurred. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. I recommend installing the service in the manual mode. Be careful of what you ask for. Your previous suggestion stated installed and 'disabled' :-) A simple tour thru My Computer->Manage->Services->InfiniBand Subnet Management enables the service. Or if you like a command line approach: 'sc config openSM start= "auto" ; sc openSM start'. The sc.exe interface does not support a start type of 'manual', although the GUI interface does? 'disabled' is the closest to what you requested. [Erez Cohen] - Agree. Will try to be more accurate next time ;) 4. In custom installation there is a component called OSM as service (or something similar to that). What it actually does is setting the SM to auto and start it. If not chosen, the SM will be installed but not started (see 1 above). I think a more appropriate name for this component/feature is "Enable OpenSM" as it will be installed even if not chosen. Possibly not the best nomenclature; will make the feature more descriptive of what it actually does. Can you live with 'OpenSM_service_enabled'? [Erez Cohen] - Yes. 5. Uninstall from the start menu pops the "Add Remove Program" window rather then start the uninstall process. I reverted back to the Add/Remove Programs as msiexec.exe did an incomplete uninstall where ARP did a complete uninstall. Specifically, msiexec.exe left WinOF in the system search path (IS script function was not called). Additionally, msiexec left an incomplete ARP entry for WinOF. When this incomplete WinOF ARP entry was invoked it failed. 6. In add remove windows, there is no information in at "click here for support information" in XP 64 bit. Beats me as to why InstallShield-12 has decided not to produce the support information? The info is in the .ism file, for some reason IS has decided not to put to ARP? Will investigate. Stan. Best regards, Erez Cohen Field Application Development Manager Mellanox Technologies Ltd. Tel : + 972 - 4 - 9097200 ext 378 Cell : + 972 - 54 - 5468801 Fax : + 972 - 4 - 9593245 www.mellanox.com _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
_______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
