<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VMI Namespace in Communications and Wireless</title>
    <link>https://community.hpe.com/t5/communications-and-wireless/vmi-namespace/m-p/3284601#M2896</link>
    <description>I've got an NC8000 with the internal, (HP), WLAN adapter. I use the computer to connect by CAT5 at work and the WLAN to connect to my router  at home. Everything has been working very well until about 5 days ago. Now when I reboot my laptop I get a "VMI Namespace could not start" error message. &lt;BR /&gt;&lt;BR /&gt;I can reinitiate the Atheros client manually three or four times and get it started but I get the same VMI Namespace error message the first two or three times I restart Atheros. &lt;BR /&gt;&lt;BR /&gt;This started immediately after I'd upgraded from MS Office 2K Pro to MS Office 2003 Pro. I don't know whether there is any connection between the two but would welcome comments/suggestions. Thanks in advance. Dave</description>
    <pubDate>Mon, 24 May 2004 06:19:54 GMT</pubDate>
    <dc:creator>David E. Bewley</dc:creator>
    <dc:date>2004-05-24T06:19:54Z</dc:date>
    <item>
      <title>VMI Namespace</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/vmi-namespace/m-p/3284601#M2896</link>
      <description>I've got an NC8000 with the internal, (HP), WLAN adapter. I use the computer to connect by CAT5 at work and the WLAN to connect to my router  at home. Everything has been working very well until about 5 days ago. Now when I reboot my laptop I get a "VMI Namespace could not start" error message. &lt;BR /&gt;&lt;BR /&gt;I can reinitiate the Atheros client manually three or four times and get it started but I get the same VMI Namespace error message the first two or three times I restart Atheros. &lt;BR /&gt;&lt;BR /&gt;This started immediately after I'd upgraded from MS Office 2K Pro to MS Office 2003 Pro. I don't know whether there is any connection between the two but would welcome comments/suggestions. Thanks in advance. Dave</description>
      <pubDate>Mon, 24 May 2004 06:19:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/vmi-namespace/m-p/3284601#M2896</guid>
      <dc:creator>David E. Bewley</dc:creator>
      <dc:date>2004-05-24T06:19:54Z</dc:date>
    </item>
  </channel>
</rss>

