I've just learned that the code for Win2000 has been locked down. George
was just able to get something in before it locked but he wasn't able to
talk with anyone about it. So, I guess, we have to live with his choice of
using the key 3F000000h followed by a pointer to a text leaf that contains
the 1284 ID.
Again this shouldn't effect the printers that specify the PWG ID as the
Command_Set_Specifier_ID, just those that use the NCITS ID.
Personally, my preference would have been to put the text leaf pointer after
the LUN key, sigh.
From: Gregory LeClair [mailto:firstname.lastname@example.org]
Sent: Thursday, March 04, 1999 4:09 PM
To: John Nels Fuller; '1394 PWG'
Subject: RE: P1394> 1284 ID
Could you give me a concrete idea of what will work for the
One idea would be to put the Device ID off the root as a text
leaf following the Vendor_ID (See cfgrom04.pdf, P. 13, Sec. 5.2.4.)
Another idea, as you mentioned, would be to put the Device ID in the
Unit Directory. Is the LUN Key the most appropriate (and possibly
(See cfgrom04.pdf, P. 15, Sec. 5.2.7.)
Please advise. Thanks,
From: John Nels Fuller [SMTP:jfuller@MICROSOFT.com]
Sent: Wednesday, March 03, 1999 5:50 PM
To: '1394 PWG'
Subject: P1394> 1284 ID
We have some problems with the way proposed to include a 1284 ID in the PWG
profile. Actually, not so much with the PWG profile as with the interim
solution we will be shipping with Win2000 (this uses the command set
specifier 00609Eh and command set 0104D8h).
We really want that 1284 ID to be in a plain vanilla text leaf instead of a
private format string. And we really want it in the unit directory, because
Win2000 isn't going to know about feature directories, etc.
Again, this is just for our interim solution. In future releases we will be
happy to look in the feature directory; but we still think that the format
should be that of a standard text leaf.
John Nels Fuller
Program Manager, Windows 2000
One Microsoft Way
Redmond, WA 98052-6399
Voice: (425) 703-3863
Fax: (425) 93 MSFAX