Phoenix answers all our phone-home BIOS questions
And by the way, PhoenixNet is dead
As promised, Phoenix has answered all the questions we sent them about the controversial PhoenixNet BIOS. Now we know why it took so long to get our answers: the scheme was dying quietly as we corresponded.
1. Does the PhoenixNet installation software alert the user to the Net feature and give them a chance to decline to install it? (We understand that the user can disable the service in CMOS setup; but if an option is not present during installation, then the connection, when available, will likely be made without the user's knowledge since only a fraction of users will go into setup before using their machine.)
"When a PhoenixNet-Enabled PC running Windows 98 or ME is initially booted up, the BIOS causes a small application, called the Permission Application, to be enabled. The BIOS performs no other functions related to the PhoenixNet Delivery System after this occurs. The Permission Application presents a display screen than asks the user, following the Windows registration process, whether the user wishes to receive PhoenixNet services. If the user decides not to accept the PhoenixNet offer, an icon is placed on the PC's desktop, so the user can accept the offer later and enroll on the PhoenixNet web site. No other PhoenixNet application is installed if a user declines the offer, and the Permission Application will not launch again, unless the operating system is removed and reinstalled. In that case, the process described above occurs."
2. Are there any versions of PhoenixNet-enabled BIOS which do not offer the option to disable it in CMOS setup? If not, is Phoenix prepared to guarantee that there won't be any in future?
"PhoenixNet was designed to use a Permission Screen approach to give users an easy way to enroll or not in the PhoenixNet service. This feature eliminated any need for a user to go into BIOS setup to disable or decline these services. In some cases, motherboard companies went further and added a switch to the BIOS setup that allowed a PC system builder to disable PhoenixNet capabilities entirely. If the PC was shipped with the switch in the default position, the Permission Screen was displayed and the process explained in answer no. 1 took place. However, if a system builder disabled the option, the process never started. In short, the PC was not PhoenixNet-Enabled.
Because of a change in the PhoenixNet business model mentioned in our response to question 6, motherboard companies discontinued adding PhoenixNet Solutions Delivery clients to their products in the first quarter of this year. The shipments of the product that remain in the channel are from earlier production that will not be resumed." [our emphasis]
3. Certain PhoenixNet installed files, PTLSEQ.DAT; PTLSEQ.MET; and PTLSEQ.RCL, appear to contain some configuration and hardware information related to the individual PC its running on. What data about the PC is sent to Phoenix during the Net connection? Is it recorded? If so, what is it used for and by whom can it be accessed?
4. What data about the PC *can be* sent to the mobo manufacturer during the Net connection? In other words, how flexible is this feature? Could a manufacturer track the aggregate use of their mobos with this feature? Could they track individual use?
5. Is it possible to identify a particular mobo with any feature currently included in, or planned for, the Net service?
"If a user enrolls in the PhoenixNet service, the PC is identified to the service to indicate that the machine is enrolled, and to maintain a record of services that the user has chosen from our Web site. This practice is analogous to the placement of 'cookies' by various web services."
6. We assume that the purpose of PhoenixNet is to attract ad revenues for Phoenix and possibly mobo manufacturers by driving consumers toward commercial products and services which you or the manufacturers have been paid to promote. Correct us if we're wrong.
"Obviously, the success of any free Internet service depends on advertising and similar revenue sources. The weaknesses in this business model have become apparent recently and have been responsible for the termination of many free Web services. Phoenix has concluded that this business model no longer represents a viable approach to delivering services to its users, and the product is being phased out."
There was some confusion in our previous report. The company has clarified its position:
"We hope this clarification and our enclosed answers provide the information necessary to put any concerns to rest over PhoenixNet."
Has it? Hit the e-mail link at the top of the page and let me know what you think. I'll forward your comments to Phoenix. ®
Sponsored: Protecting mobile certificates