From: "Jon Harrison" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.3) with ESMTP id 1866214 for ecs-t6x@2rosenthals.com; Thu, 17 Apr 2008 01:26:28 -0400 Received-SPF: none (secmgr-ny.randr: 216.162.174.5 is neither permitted nor denied by domain of seadog.reno.nv.us) client-ip=216.162.174.5; envelope-from=jharrison@seadog.reno.nv.us; helo=pop5.greatbasin.net; Received: from pop5-wpti.greatbasin.net ([216.162.174.5] helo=pop5.greatbasin.net) by secmgr-ny.randr with esmtp (Exim 4.43) id 1JmMdb-00067w-Ew for ecs-t6x@2rosenthals.com; Thu, 17 Apr 2008 01:26:28 -0400 Received: from DP6550.seadog.reno.nv.us (seadog.reno.nv.us [216.82.144.188]) (authenticated bits=0) by pop5.greatbasin.net (8.13.8/8.13.8) with ESMTP id m3H5QGZr011868 for ; Wed, 16 Apr 2008 22:26:17 -0700 Received: from TYAN.seadog.reno.nv.us (TYAN.seadog.reno.nv.us [192.168.1.35]) by DP6550.seadog.reno.nv.us (Weasel v1.72) for ; 16 Apr 2008 22:26:17 -0700 Message-ID: <100-75df0648-26465.055@seadog.reno.nv.us> To: "eCS ThinkPad T60/61 Mailing List" Date: Wed, 16 Apr 2008 22:26:13 -0700 (PDT) Priority: Normal User-Agent: PMMail/3.00 (os/2; U; Warp 4.5; en-US; i386; ver 3.00.00.0935) X-Mailer: PMMail 3.00.00.0935 for OS/2 Warp 4.5 In-Reply-To: <185022.22.00.27.16.04.2008@seadog.reno.nv.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [eCS T60/T61] Installing to TP61 X-Spam-Score: -1.4 (-) X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP On Wed, 16 Apr 2008 22:55:06 -0600, Chuck McKinnis wrote: > >I wonder if the 4 Gb is causing a problem when the CD tries to load into >high memory. I wondered about this. I have 3 Gb of ram in 2 sticks, I believe. I suppose I could check on how to pull one. Also, the drive I purchased is the one that supports FDE, so it has a security chip on it. I don't think this matters, except that it differs from yours. The Hitachi doc's says it is supported by MacOS X, Linux Variations, DOS Variations, Windows Vista, Windows XP SP2 so therefor I would expect that this is not the problem. I suppose it could be driver specific but DFSee (dated Jan '08) has no problem operating the drive. Jon