Wellsite Information Transfer Standard Markup Language
NEWS from 2002 |
| 1 November 2002 | XML in Drilling, 5th/6th November in Stavanger. Agenda | |
| 8 October 2002 | POSC Meetings in London on October 15/16 and Houston 20th November The theme of the meetings is "E&P Knowledge, Information and Data: Documents, Data Stores and Catalogues" and addresses issues and challenges in use and management of value-added information. The plenary session in London on October 15 includes presentations from ChevronTexaco, ExxonMobil, Flare Consultants, IBM, Landmark Graphics, Norwegian Petroleum Directorate, Paras Consulting, POSC, Schlumberger and Statoil. The October 16 agenda features two seminar sessions: WITSML and E&P Products and Services Nomenclature and Classification. |
|
| 18 September 2002 |
|
|
| 18 July 2002 | The WITSML sponsors and participating companies are pleased to welcome Shell to the WITSML advisory board. The first task facing the newly expanded board is the transitioning of future development and maintenance of the standard to POSC for ensuring long-term sustainability and broader industry take-up." | |
| 15 January 2002 | API v1.1.0a Prototype Refresh | |
| 14 January 2002 | Updated BP contact information | |
| 4 January 2002 | Information on problems with VB6 on Windows 2000 (see below) |
v1.1.0 Update Information for Windows 2000 problems with VB6 |
The "refresh" of the prototype API (version 1.1.0A) is mostly ready, but we're waiting to resolve one remaining issue with Microsoft...
Some testers have reported a problem when running the WMLI DLL setup on Windows 2000 systems, in which the message "Setup cannot continue because some system files are out of date.." is repeatedly issued, even after
restarting the system.
We have been able to reproduce the problem on a test system at NPSi.
It is caused by an apparent incompatibility between the VB6 Package and Deployment Wizard (PDW) - which we use to generate the setup files - and Windows 2000.
The problem is that the VB6 PDW assumes that it is OK to upgrade "system files", so it includes them in the setup file that it creates.
However, Windows 2000 does not allow application setups to upgrade system files (only Service Packs can). So...the setup gets in a loop, thinking that it has upgraded the system file, only to then discover that the old version is still there, because W2K restored it.
> The problem is only surfacing now that systems creating the setup files are at later SP levels (ours are at SP2) than the target W2K systems (now typically at SP1).
This is a known problem described in Microsoft Knowledge Base article Q274764, but the "resolutions" offered there aren't really practical.
We've opened an incident with Microsoft to see if there is a real solution.
David Thom
Director - Systems Technologies
NPSi Houston
|
Site maintained by POSC. Contact: masters@posc.org Phone: +1 713 267 5111 |