This message is from the T13 list server.
Gary, There are BOZOS out there running around pushing bogus information on how to detect and address DCO and HPA. All the Law Enforcement agencies are going bonkers and it is becoming an annoying issue. There are people claiming endusers are using DCO to hide content from detection, yet there is only a "Freeze Lock" and not a "Set Lock". Thus everyone here know that if a BIOS issues a "Freeze Lock", you pull the drive out of the system, or place it on an HBA where the BIOS can not invoke the "Freeze Lock". Issue the DCO Identify and all the capacity issues are restored. Now the only way to commit such a lock out is to first issue a DCO and then pound down "SET_MAX_PASSWORD". This would foil the DCO Identify or would it? Since the DCO Freeze Lock would not survive transistions in the power. Now if the DCO de-stroked the device, and the "SET_MAX_PASSWORD" was based on the de-stroked capacity, in order to preserve the order of operations the DCO Freeze Lock must survive. Now all of this throws a monkey wrench into PARTIES, unless the above is wrong. It will make BEER upset to because the DCO lock effectively break BEER access. If BEER can not be found then EDDS is also effectively broken. So Curtis, all the fun associated with EDD'S BEER PARTIES is smashed if the DCO hides the BEER. GAWD, I have been around you way to long, Curtis! Cheers, Andre Hedrick LAD Storage Consulting Group On Wed, 2 Oct 2002, Gary Laatsch wrote: > This message is from the T13 list server. > > > Curtis, > > I would say yes to that. I think at minimum it needs to be investigated and it >sounds from both my experience and what Andre is saying rev 2 is in order. > > gkl > > -----Original Message----- > From: Curtis Stevens [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, October 02, 2002 10:05 AM > To: T13 (E-mail) > Subject: RE: [t13] Update of 1367D - PARTIES > > > This message is from the T13 list server. > > > Gary > > I am not aware of any updates to PARTIES. The options are and > addendum, or a rev 2. It has been a while, so rev 2 may be in order. This > looks to me like the addition of one section. Would you like me to put > together a project request? > > ----------------------- > Curtis E. Stevens > Pacific Digital Corp. > 2052 Alton Parkway > Irvine, CA 92606 > > Phone (949) 477-5713 > Fax (949) 252-9397 > > E-Mail: [EMAIL PROTECTED] > WEB: www.PacificDigital.com > > Never take life seriously... after all, nobody ever gets out alive! > > > -----Original Message----- > From: Gary Laatsch [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 01, 2002 2:42 PM > To: Andre Hedrick > Cc: T13 (E-mail) > Subject: RE: [t13] Update of 1367D - PARTIES > > > This message is from the T13 list server. > > > Andre, > > I think it might be cosidered if it falls within the scope of that > document. I would need to study that more. I know both DCO and 48-bit > stuff is ATAPI-6ish and the 1367D is ATAPI-4ish, so we should probably > address them both somewhere anyway. There are just some anomilies with HPA > that would be nice to address in somekind of document before we get to many > differnent ways of doing things out there. If we can kill 2 birds with 1 > stone (is it still PC to use that phrase) it would be better. > > gkl > > -----Original Message----- > From: Andre Hedrick [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 01, 2002 12:03 PM > To: Gary Laatsch > Cc: T13 (E-mail) > Subject: Re: [t13] Update of 1367D - PARTIES > > > > > Does it deal with the combination of DCO + HPA additionally? > > Andre Hedrick > LAD Storage Consulting Group > > On Tue, 1 Oct 2002, Gary Laatsch wrote: > > > This message is from the T13 list server. > > > > > > Folks, > > > > I was looking at document 1367D which is the PARTIES document and it > doesn't deal with support of the 48-bit HPA stuff. Is there an updated > document that I haven't found yet or did I just sign up to do something > which will be brought up during new business in Vegas? > > > > Gary Laatsch > > Principal Engineer > > Mass Storage > > Phoenix Technologies Ltd. > > Office: 949-790-2107 > > Fax: 949-790-2001 > > [EMAIL PROTECTED] > > > > "Working code is good code, good code is not always working code...." > > - Craig Llewellyn (my first firmware manager) circa 1978 > > > > > > >
