[7725] in Release_7.7_team
Re: quick-statalib5
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Feb 15 16:32:40 2012
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <FE5A354B-F503-420E-BFBB-B98D66EFD8FB@mit.edu>
Date: Wed, 15 Feb 2012 16:32:37 -0500
Cc: release-team@MIT.EDU
Message-Id: <CA1A4CD2-AE0B-4E0E-9897-FBDB3E5828D2@mit.edu>
To: Jonathan Reed <jdreed@MIT.EDU>
Content-Transfer-Encoding: 8bit
OK, I have fixed the Vostro re-installation problem, and re-installed the machine (as quick-statallib5). It can be re-deployed to Stata. I suspect any other Stata problems can be solved by re-installation (people are still screwing with the machines, because they're public, but that's a different problem). Any network issues that occur in Stata now are definitely location-specific, because it works just fine in E17.
The change to the installer still needs to be deployed,I'm hoping to do that later this week.
I can go over with Tommy or whoever picks up the Vostro (I don't have the special screwdriver to re-secure it) and make sure it comes up.
-Jon
On Feb 14, 2012, at 4:18 PM, Jonathan Reed wrote:
> OK, I took a look at this today, and the install is failing for the same reason that the upgrades were failing, because of the stupid Realtek firmware issues. (The installer tries to look for firmware, doesn't find it, and then decides it should remove and reinsert the module anyway, causing the device to lose its network configuration.) We solved this for the upgrade by doing horrible things, I'm not sure what the right answer is here. (I'm not sure how this ever worked, actually). I'll play around with things and see what our options are.
>
> -Jon
