[7728] in Release_7.7_team
Re: quick-statalib5
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Thu Feb 16 12:44:51 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: <1329403571.28227.3.camel@QUICKSTATION-11-4.MIT.EDU>
Date: Thu, 16 Feb 2012 12:44:48 -0500
Cc: Joyce Gomes <jogomes@MIT.EDU>, release-team@MIT.EDU, acis-team@MIT.EDU
Message-Id: <17544222-9B77-413B-81F3-02AD430A0683@mit.edu>
To: Thomas Smith <tjsmith@MIT.EDU>
Content-Transfer-Encoding: 8bit
Hi Tommy,
Any time this afternoon or tomorrow morning after 10am would be fine.
-Jon
On Feb 16, 2012, at 9:46 AM, Thomas Smith wrote:
> Hi Jon,
>
> Good news.
> Thanks for the assistance.
> Let me know when will be good for you to go to Stata and I will come by
> and pick up the vostro machine.
>
> Best regards,
> Tommy
>
>
>
>
>
> On Thu, 2012-02-16 at 09:38 -0500, Joyce Gomes wrote:
>> ________________________________________
>> From: Jonathan Reed [jdreed@MIT.EDU]
>> Sent: Wednesday, February 15, 2012 4:32 PM
>> To: Jonathan D Reed
>> Cc: release-team@mit.edu
>> Subject: Re: quick-statalib5
>>
>> 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
>>
>
