EP1212676A2 - Installation a distance de systemes d'exploitation informatiques - Google Patents

Installation a distance de systemes d'exploitation informatiques

Info

Publication number
EP1212676A2
EP1212676A2 EP00957720A EP00957720A EP1212676A2 EP 1212676 A2 EP1212676 A2 EP 1212676A2 EP 00957720 A EP00957720 A EP 00957720A EP 00957720 A EP00957720 A EP 00957720A EP 1212676 A2 EP1212676 A2 EP 1212676A2
Authority
EP
European Patent Office
Prior art keywords
computer
installation
routine
operating system
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP00957720A
Other languages
German (de)
English (en)
Inventor
Stephen Blair Glaxo SmithKline KINLAW
Andrew David Glaxo SmithKline PATTERSON
Daniel James Glaxo SmithKline PLATT
Thomas Dwayne Glaxo SmithKline POWELL
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Glaxo Group Ltd
Original Assignee
Glaxo Group Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Glaxo Group Ltd filed Critical Glaxo Group Ltd
Publication of EP1212676A2 publication Critical patent/EP1212676A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation

Definitions

  • the present invention relates to the remote installation of computer operating systems for networked computers.
  • Such networks may be in the form of a local area network (LAN) where computer workstations in a single physical location, for example a building, are connected to each other and to a computer acting as a network server.
  • the network server typically controls security access to the network and regulates resource sharing.
  • a method of installing a computer operating system comprising the steps of running an installation routine on a computer in which the installation routine accepts user inputs defining a delivery location and is operative to detect the computer type, connect the computer to an operating system installation source held on a remote computer, retrieve a copy of a master installation script held on the remote computer, and modify the copied master installation script in dependence on a number of variables associated with the delivery location and the computer type to create a dedicated installation script, and subsequently installing automatically the computer operating system using the dedicated installation script.
  • the installation routine is operative to retrieve additional software associated with the computer type from the remote computer and subsequently install the software using the dedicated installation script.
  • the installation routine is operative to detect hardware components of the computer, to retrieve additional software associated with the hardware components to supplement the computer operating system from the remote computer and subsequently install the software using the dedicated installation script.
  • the installation routine is operative to detect the computer type and the hardware components of the computer by evaluating the computer's BIOS settings.
  • the installation routine evaluates the computer's BIOS settings by comparing the computer's BIOS settings with known BIOS settings.
  • the storage device may hold a database containing the known BIOS settings, each of which BIOS settings being associated with one or more hardware variables, whereby the hardware variables may be used to modify the master installation script.
  • the hardware variables may be used to modify the master installation script to thereby install additional software for undetectable hardware components known to be present in computers having a certain type or hardware component.
  • the hardware variables may be used to modify the master installation script to thereby change programmable settings of the computer or hardware component.
  • an operating system can be installed and configured elsewhere, such as at the equipment supplier's premises or at a centralised IT/support centre, the installation possibly being performed in a different language to that required by the end user and possibly without a network connection to the LAN and server where the computer workstation is to be used. It is furthermore desirable that a computer installed and configured at a first location for use at a second location will be configured exactly the same as a computer installed and configured at a third location for use at the second location.
  • the present invention provides an installation procedure in which the installation and configuration of each workstation is standardised and repeatable.
  • the present invention also provides an installation procedure in which the installation process is essentially automated, thereby reducing the amount of time an installer must spend at each machine to provide a machine ready to be used upon delivery.
  • the present invention provides an installation method and system where a computer operating system can be installed and configured at a first location for use at a second location, where the second location need not necessarily be on the same LAN or WAN as the first location.
  • the present invention provides an installation procedure which is adaptive, selecting the additional software needed to support non-standard configurations without prompting the user.
  • the installation routine is operative to retrieve the computer operating system from the remote computer along with any additional software and subsequently disconnect the computer from the remote computer, wherein the computer is then re-booted and the computer operating system installed using the dedicated installation script.
  • the installation routine may also accept user inputs defining a build location corresponding to the location of the remote computer where the operating system installation source is held.
  • the data connection to the remote computer may be made via the internet.
  • the storage device is a computer disk.
  • it may be any computer readable media capable of storing the aforementioned instructions.
  • a system for installing a computer operating system comprising: a computer; a network to which the computer may be connected; a remote computer connected to the network which holds an operating system installation source, additional software and a master installation script file; and, a storage device which holds a set of computer executable instructions and a number of files for performing an installation routine in accordance with the first aspect of the present invention when n i on the computer.
  • a program storage device readable by a machine and encoding a program of instructions and a number of files for executing the method of the first aspect of the present invention.
  • the machine is a general purpose computer.
  • the installation routine may be initiated by running a computer program held on a storage device.
  • the storage device is a computer disk which is inserted into a drive of the compute.
  • the computer may connect to the remote computer by the iternet.
  • the additional software may be located on a different source to that of the remote computer.
  • Figure 1 is a schematic of a typical computer hardware arrangement used in the remote installation of a computer operating system in accordance with the present invention
  • Figure 2 is a flow chart which outlines a typical installation routine according to the present invention
  • Figure 3 is a flow chart expanding upon a particular step of the installation routine illustrated in Figure 2;
  • Figure 4 is an expanded schematic of the hardware arrangement shown in Figure 1 including an end-use network where a workstation is to be used;
  • Figure 5 is a flow chart of a more specific example of an installation routine according to the present invention.
  • Figure 6 is a flow chart expanding upon a particular step of the installation routine illustrated in Figure 5.
  • a typical arrangement of the computer hardware used in the remote installation of a computer operating system in accordance with the present invention is shown in Figure 1.
  • a network 10 connects a network server 12 and a network data store 14 to a network interface device 16.
  • the network interface device 16 is connected to a computer workstation 18 with a random access disk memory 20.
  • the disk memory 20 does not contain a computer operating system.
  • a 32 inch disk or other suitable storage device 22 is used to boot the computer workstation 18.
  • an installation program held on the computer storage device 22 is run on the computer workstation 18.
  • the installer when running an installation routine controlled by the software the installer is prompted to idenrf ⁇ die particular network interface device 16 and to input a !juild location code, a delivery location code and a unique identifier for the computer workstation 18. Subsequently, the installation routine detects the computer type of the computer workstation 18 and its additional hardware components. By using the data input by the installer, the installation routine is able to connect the computer workstation 18 to the network 10 via the network interface device 16.
  • the installation routine then automatically installs an appropriate computer operating system from a remote computer operating system .nstallation source held in the network data store 14 onto the disk memory 20 of the computer workstation 18.
  • the installation routine is adapted to configure the computer operating system in dependence on the delivery location code and detected computer type and hardware components.
  • the build location code refers to where the build process is to be carried out, whilst the delivery location code refers to where the built computer workstation is to be located.
  • the installer is prompted to input a build location code '.a d a delivery location code in step 100.
  • An environment database in a look-up table stored on the installation disk is then interrogated with the build location code and the delivery location code (step 102) to obtain build location specific variables and delivery location specific variables which are stored by the computer workstation in step 104.
  • the installer is also prompted to enter a unique identifier for the computer workstation (step 106).
  • the installation routine then scans the computer workstation's BIOS settings in step 107 to determine the computer type (including manufacturer and model) and hardware components, such as PCI devices, installed in the computer workstation.
  • the detected computer type and hardware components are cross referenced with a further look-up table held on the installation disk to determine computer workstation variables in step 107a.
  • the installation routine uses the build location specific vrriables the installation routine connects the computer workstation to the network in step 108 and accesses an installation account on the server.
  • a master installation script held with the computer operating system installation source on the network data store is copied onto the disk memory of the computer workstation in step 110.
  • the copy of the installation script is then modified in dependence on the build location specific variables, on the delivery location specific variables and on the computer workstation variables (step 112) to create a dedicated installation script.
  • the computer operating system is then installed and configured using the computer operating system installation source setup routine with the dedicated installation script in step 114.
  • the installation and configuration step 114 of Figure 2 is expanded upon in the flow chart of Figure 3.
  • the computer operating system installation source is copied from the network data store onto the disk memory (such as a hard disk) of the computer workstation in step 200.
  • Additional software required by the detected computer type or detected hardware components, as defined by the computer workstation variables, is copied from the network data store in step 201.
  • the setup routine then disconnects from the network and reboots the computer workstation in step 202.
  • the setup routine installs the computer operating system using the dedicated installation script (step 204).
  • the additional software is then installed to supplement the computer operating system in step 205.
  • the computer operating system is then configured in dependence upon the dedicated installation script in step 206.
  • the setup routine also cleans up the disk memory of the computer workstation by deleting any unnecessary files in step 210.
  • the setup routine ends once the computer workstation has a complete computer operating system ready for use at the delivery location.
  • the schematic of Figure 4 includes the computer hardware arrangement of Figure 1 in addition to a network 30 and a network server 32 to which the computer workstation 18 is intended to be connected.
  • the network 10 may be a part of the same LAN as the network 30, it may be a part of the same WAN as the network 30 connected by a telecommunications system, or there may be no network connection to the network 30. If there is a connection between the network 10 and the network 30 that the computer workstation 18 is intended to be used upon, then the installation routine registers the computer workstation 18 by its unique identifier with the network 30 and network server 32 where the computer workstation 18 is to be used.
  • the network 10 is an Ethernet network, with network servers 12, 32 operating under Microsoft Windows NT Server operating system V.4 and the computer operating system installation source is Microsoft Windows NT workstation.
  • the computer storage device 22 is an MS-DOS formatted disk holding an MS-DOS v.6.22 operating system kernel and files necessary to boot the computer workstation 18, the installation routine, the environment database and TCP/IP network drivers for each selectable network interface device 16.
  • the computer workstation 18 is a Hewlett-Packard Vectra XM/4 5/166 Personal Computer with 32MB of random access memory.
  • the disk memory 20 of the computer workstation is a 1.2GB hard disk drive.
  • the network interface device 16 is a 3COM Etherlink 2 3C503/16 Ethernet network card installed in the computer workstation 18.
  • the operating system kernel on the computer storage device 22 takes control of the boot routine and prompts the user to select the network ' iterface device 16 used from a list of supported network interface devices using the MS-DOS v.6.22 start-up menu facility in step 300.
  • the TCP/IP network drivers corresponding to a network interface device selected from the list are copied to default file names (step 302) so that the installation routine may access any of the supported network interface devices without knowledge of the specific type.
  • the boot routine then runs the installation routine in step 304.
  • the installation routine accepts an input of a build location code (step 305) and a delivery location code (step 306).
  • the build location code and delivery location code are cross-referenced with a list of allowable locations in respective steps 307, 308 and if the locations are not on the list, a list of the allowable locations is displayed in respective steps 309, 310 and the installer is prompted to re-enter the code in respective steps 305, 306. If six incor .ct attempts at entering an allowable location are made the installation routine ends and reports an error in respective steps 309a and 310a. After a valid build location code and a valid delivery location code are entered, the installation routine accepts an input of a unique identifier for the computer workstation (step 311) to be later used as its DNS address. The installation routine interrogates the environment database with the build location code and the delivery location code in step 312 to obtain build location specific variables and delivery location -pecific variables. The variables relate to environment and network specific settings for the two locations, as can be seen from Table 1.
  • the build location specific variables "server” and "share” define the server and network data store holding the computer operating system installation source. If, for example, the build location UK is entered, the computer operating system installation source would be installed from ID4 on the UK ID4 server.
  • the installation routine accesses the computer workstation's BIOS (Basic Input Output System) in step 312a which holds data on the computer workstation's hardware (manufacturer, model, memory, hard disk capacity, Advanced Power Management support and settings and other hardware components such as MPEG, USB, Firewire, parallel and serial interfaces).
  • BIOS Basic Input Output System
  • An example of data held in a computer workstation's BIOS is shown below: F000::0000 26 89 45 1C 8B C6 03 C3 83 CO 48 26 89 45 1A 32 &.E H&.E.2
  • the installation routine cross-references the contents of the computer workstation's BIOS with a BIOS settings table held on the installation disk in step 312b.
  • the BIOS settings table stores the BIOS codes that will be found in the BIOS of each computer workstation from a particular manufacturer, such as the "Hewlett-Packard" identifier in the above example.
  • a subset of entries are stored in the table for each manufacturer identifying the BIOS codes that will be found in each particular computer workstation model supplied by that manufacturer, such as "HP.Kayak.PC. Workstation XA 6/266" in the above example.
  • a unique workstation type code is stored in the table. By cross-referencing the contents of the BIOS with entries in the table, a unique workstation type code is determined.
  • the BIOS also holds data on other hardware components attached to the computer workstation's bus such as PCI cards and USB devices.
  • PCI cards and USB devices.
  • An example of data held on PCI components by a computer workstation's BIOS is shown below:
  • PCI bus 00 device 04 function 00 Header Type 'non-bridge' ( ulti-func)
  • the BIOS settings table also holds entries for each supported component, cross-referencing each component with a unique component code. Each entry in the computer workstation's BIOS is cross-referenced with the entries in the BIOS settings table to determine unique component codes.
  • the installation routine logs the computer workstation onto the network in step 313.
  • the IP address for the computer is obtained from the server using DHCP (dynamic host configuration protocol) and the unique identifier is used as the DNS address.
  • a computer disk format utility is run to format the disk memory 20 of the computer workstation 18.
  • a master installation script stored on the network data store with the computer operating system software source is copied onto the disk memory (step 314).
  • the installation routine modifies the copied script in dependence on the build location specific variables and on the delivery location specific variables (step 315) to create a dedicated installation script.
  • the script fields shown in bold are edited by inserting the delivery location specific variables, the field names corresponding to the column headings of Table 1.
  • the unique identifier is entered as the ComputerName.
  • An entry in the dedicated installation script is made containing the workstation type code and each component code. These are later used during unattended installation to obtain and install additional operating system components necessary to best support the workstation type and installed components.
  • the computer operating system installation source is then copied from the network data store onto the disk memory (such as a hard disk) of the computer workstation.
  • the computer workstation variables are used to select additional software required by the detected computer type or detected hardware components, which are copied from the network data store.
  • the installation routine then proceeds in step 316 to accept inputs relating to the selection of additional software to be installed.
  • additional software may include drivers to access other network protocols, office application suites and e-mail client software.
  • the installation routine ends by running the Windows NT set-up routine held with the computer operating system source on the network store.
  • the Windows NT set-up routine is run in step 317 in an ur ttended installation mode using the dedicated installation script 'o provide answers to questions usually asked during a manual set-up.
  • the set-up routine proceeds substantially as has been described with reference to Figure 3.
  • the dedicated installation script then runs the installation routines for the additional software.
  • the additional software may also include software supplied by computer manufacturers tailored specifically for computer workstation types such as power management software, help files and maintenance software for the particular computer workstation model.
  • Step 206 of Figure 3 is expanded upon in the flow chart of Figure 6.
  • the routine reconnects the computer workstation to the network 10 using the newly installed computer operating system (step 412) and an attempt is made (step 414) to connect to the network where the computer workstation is intended to be used. If this is successful, the unique identifier for the computer is registered as the computer workstation's DNS address with the Windows NT network domain and server that the computer workstation is intended to be used upon in step 416.
  • the computer workstation then disconnects from the network 1 , (step 418) and is ready for use upon delivery to the locationor where it is intended to be used. If the attempt is not successful, the installation fails.
  • a connection to the network where the computer workstation is intended to be used is not possible.
  • a remote build site code relating to the outside organisation's own network is used for the build location code (REM in Table 1).
  • the location specific variables relating to the remote build site code are used for both the build location specific variables and the delivery location specific variables.
  • the delivery location code entered is stored for later use.
  • the configuration of the computer operating system is updated in dependence on the stored delivery location code.
  • the unique identifier of the computer workstation is then registered with the Windows NT network domain and server that the computer workstation is inter/Jed to be used upon at the delivery location according to the previously described steps 414 to 418 of Figure 6.
  • the computer workstation's network interface device type is inputted by the installer, it is possible with new PCI type devices to automatically detect the network interface device from the BIOS in the same way as for other hardware components.
  • BIOS software itself may oe out of date and may not support Year 2000 issues. As the BIOS software version is stored in the BIOS, this could be detected and the BIOS software updated or patched as a result.
  • the installation routine can be set to identify these conflicts, due to knowledge of what standard hardware components a computer workstation of a certain type will have and/or detection of hardware components from the BIOS, and resolve them.
  • the installation routine can be pre-set with the knowledge that certain computer workstation types have modems by default and the operating system and additional software should be installed and configured to cater for this by including software for access to the internet, email, remote access etc.
  • the additional software will be located with the operating system source on the remote computer, it may alternatively be located on a different source, on the same network or possibly accessible via the internet or an intranet.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé d'installation d'un système d'exploitation informatique à partir d'un réseau vers un ordinateur et de configuration de l'ordinateur destiné à être utilisé dans le réseau ou dans un autre réseau. Un programme d'installation est exécuté lequel accepte une entrée d'un emplacement de constitution et d'un emplacement de remise, il interroge une base de données d'environnement à l'aide de l'emplacement de constitution et de l'emplacement de remise pour obtenir une ou plusieurs variables spécifiques à la constitution et une ou plusieurs variables spécifiques à la remise. Le programme d'installation détermine également le type d'ordinateur et les composants matériels installés, il accède au réseau à l'aide des variables spécifiques à la constitution, et il copie un script d'installation maître à partir d'une source d'installation de système d'exploitation stockée dans le réseau. De plus, le programme d'installation modifie le script d'installation copié selon les variables spécifiques à la constitution, les variables spécifiques à la remise, le type d'ordinateur et les composants matériels détectés pour créer un script d'installation spécialisé. Le système d'exploitation informatique est ensuite installé automatiquement à l'aide du script d'installation spécialisé. Le processus d'installation peut également comprendre l'étape d'enregistrement de l'ordinateur dans le réseau dans lequel il est destiné à être utilisé de manière qu'il soit prêt à être utilisé immédiatement au niveau de l'emplacement de remise.
EP00957720A 1999-08-27 2000-08-23 Installation a distance de systemes d'exploitation informatiques Withdrawn EP1212676A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US38448599A 1999-08-27 1999-08-27
US384485 1999-08-27
PCT/US2000/023159 WO2001016701A2 (fr) 1999-08-27 2000-08-23 Installation a distance de systemes d'exploitation informatiques

Publications (1)

Publication Number Publication Date
EP1212676A2 true EP1212676A2 (fr) 2002-06-12

Family

ID=23517488

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00957720A Withdrawn EP1212676A2 (fr) 1999-08-27 2000-08-23 Installation a distance de systemes d'exploitation informatiques

Country Status (4)

Country Link
EP (1) EP1212676A2 (fr)
JP (1) JP2003508845A (fr)
AU (1) AU6930000A (fr)
WO (1) WO2001016701A2 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1244010B1 (fr) * 2001-03-20 2007-04-25 Sap Ag Procédé et article de manufacture pour l'assignation de services à des rôles afin de lancer des services d'application dans un système basé sur des rôles
US6901590B2 (en) * 2003-03-03 2005-05-31 Computer Associates Think, Inc. System and method for single transparent deployment flow
US7814126B2 (en) 2003-06-25 2010-10-12 Microsoft Corporation Using task sequences to manage devices
US7290258B2 (en) * 2003-06-25 2007-10-30 Microsoft Corporation Managing multiple devices on which operating systems can be automatically deployed
US8086659B2 (en) 2003-06-25 2011-12-27 Microsoft Corporation Task sequence interface
WO2005116826A1 (fr) * 2004-05-24 2005-12-08 Ian Carel Van Reenen Gestion de systeme informatique
US20080162604A1 (en) * 2005-03-01 2008-07-03 Serge Soulet System and Method For Migrating a Platform, User Data, and Applications From at Least One Server to at Least One Computer
KR100725394B1 (ko) * 2005-07-08 2007-06-07 삼성전자주식회사 복수의 운영체계에서 특정 운영체계를 선택적으로 설치하는컴퓨터 시스템 및 방법
US8522234B2 (en) 2007-02-05 2013-08-27 Microsoft Corporation Tailoring an operating system to a computer system
CN101398762A (zh) * 2007-09-29 2009-04-01 联想(北京)有限公司 一种在计算机上自动安装操作系统的方法和装置
US9361082B2 (en) 2012-09-06 2016-06-07 Welch Allyn, Inc. Central monitoring station warm spare
US10001981B2 (en) 2016-05-26 2018-06-19 At&T Intellectual Property I, L.P. Autonomous server installation

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5142680A (en) * 1989-04-26 1992-08-25 Sun Microsystems, Inc. Method for loading an operating system through a network
EP0592079A2 (fr) * 1992-09-20 1994-04-13 Sun Microsystems, Inc. Installation de logiciel automatisée et configuration d'environnement d'exploitation sur un système d'ordinateur
US5742829A (en) * 1995-03-10 1998-04-21 Microsoft Corporation Automatic software installation on heterogeneous networked client computer systems
US5872977A (en) * 1997-08-08 1999-02-16 International Business Machines Corporation Object-oriented method and apparatus for creating a makefile

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0116701A3 *

Also Published As

Publication number Publication date
AU6930000A (en) 2001-03-26
JP2003508845A (ja) 2003-03-04
WO2001016701A3 (fr) 2001-09-20
WO2001016701A2 (fr) 2001-03-08

Similar Documents

Publication Publication Date Title
EP1076848B1 (fr) Installation a distance de systemes d'exploitation informatiques
US6167567A (en) Technique for automatically updating software stored on a client computer in a networked client-server environment
US7788350B2 (en) Software distribution application supporting operating system installations
US6751794B1 (en) Intelligent patch checker
US7743242B2 (en) Method and system for automatic generation of operating system boot images
US7290258B2 (en) Managing multiple devices on which operating systems can be automatically deployed
US7814126B2 (en) Using task sequences to manage devices
US7779406B2 (en) Method and system for managing lifecycles of deployed applications
US6871221B1 (en) Method and apparatus to manage network client logon scripts using a graphical management and administration tool
EP1133738B1 (fr) Procede et dispositif servant a installer un nouveau pilote de peripherique par un systeme d'exploitation
EP1978672B1 (fr) Procédé pour mettre en place le logiciel de gestion, matériel avec logiciel préconfiguré et procédé de mise en place correspondant
US6944653B2 (en) Zero-click deployment of data processing systems
US20030055919A1 (en) One-click deployment of data processing systems
US20040025155A1 (en) Method, computer program product, and system for configuring a software image for installation into a computer system
WO2001016701A2 (fr) Installation a distance de systemes d'exploitation informatiques
DE10228796A1 (de) System und Verfahren zum Installieren eines Fenster-Installiererdienstes ohne Neustarten
CN102662884A (zh) 一种基于网络的设备驱动程序配置方法
US20030182074A1 (en) Automated method for installing and configuring a test suite on a unit under test
Anderson et al. Large Scale Linux Configuration with {LCFG}
US8024430B2 (en) System and method for installing software
CN102197367A (zh) 映象过程
US6718462B1 (en) Sending a CD boot block to a client computer to gather client information and send it to a server in order to create an instance for client computer
CN100480998C (zh) 可透过网路进行基本输出入系统的更新方法
US20060179132A1 (en) Automated replacement of old computer by new computer in network environment
NZ507743A (en) Remote installation of computer operating systems

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020221

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20021018

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20030301