wireless network and sleep

  • Thread starter Thread starter Lauren89
  • Start date Start date
L

Lauren89

when my laptop goes to sleep, the network connection is lost, is there any
way i can stop i from doing this so that i still have access to my home
network when it is in sleep mode.
 
You may want to reset power management. Or this post may help.

Unable to connect to Wireless ...You may have many options to fix that
wireless doesn't work after sleep. 1. Re-set power management. 2. Upgrade
firmware for the router and driver for ...
www.chicagotech.net/netforums/viewtopic.php?t=2689 - Similar pages

chicagotech.net :: View topic - Vista: Wireless connectivity issue
Symptom: 1. The wireless lose the connection after sleep mode. 2. The
wireless connection may drop when you use battery power. Solution: 1. ...
www.chicagotech.net/netforums/viewtopic.php?t=507


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
 
I have been living with this problem for some time now, and here is what I
have learned:

1. This solution works for quite a number of people : (though sadly, not me)
- Go into Device Manager and click on the "Advanced" properties tab for your
wireless card. Disable "Minimum Power Consumption".

2. This solution has also worked for some:
- Make sure the driver for your wireless card is up to date.
- If that doesn't work, you can try letting the Windows generic driver run
your card.

3. This is always recommended, yet I have seen no evidence or responses
that it works:
- Upgrade the firmware for your wireless router/hub.
(This is really a pain to do. I have done it. It didn't help.)

Here is the list of workarounds:

a. Never let your computer go to sleep (I know, probably unsatisfactory.)

b. Open the Command Prompt and type "ipconfig/renew" after your computer
wakes from sleep. (This works 50-75% of the time for me.)

c. If you have a key combo to disable your card, do that, then re-enable it.
(On my Dell, it is Fn + F2). This usually works, and if it doesn't, it
almost always works if I follow it up with the ipconfig/renew command.

d. Left-click on the network icon and run Diagnose and Repair - reset the
wireless adapter. This occasionally works.

e. If all else fail, reboot your computer and curse. This always works,
but then you sit there, waiting and cursing...


Observations:
There is nothing wrong with the wireless system. Wireless works fine. All
the XP machines on my wireless system work fine. Even when the computer is
disconnected after sleep, the local connection still functions - just the
internet is lost.

There is definitely something wrong with the way Vista comes out of
sleep/hibernation. (This is in the top 3 tech support issues listed on the
Dell support pages.)

I really have to scratch my head that MS has done nothing to address this
issue for over a year!
Well, you can always hope.
 
I have been living with this problem for some time now, and here is what I
have learned:

1. This solution works for quite a number of people : (though sadly, not me)
- Go into Device Manager and click on the "Advanced" properties tab for your
wireless card. Disable "Minimum Power Consumption".

2. This solution has also worked for some:
- Make sure the driver for your wireless card is up to date.
- If that doesn't work, you can try letting the Windows generic driver run
your card.

3. This is always recommended, yet I have seen no evidence or responses
that it works:
- Upgrade the firmware for your wireless router/hub.
(This is really a pain to do. I have done it. It didn't help.)

Here is the list of workarounds:

a. Never let your computer go to sleep (I know, probably unsatisfactory.)

b. Open the Command Prompt and type "ipconfig/renew" after your computer
wakes from sleep. (This works 50-75% of the time for me.)

c. If you have a key combo to disable your card, do that, then re-enable it.
(On my Dell, it is Fn + F2). This usually works, and if it doesn't, it
almost always works if I follow it up with the ipconfig/renew command.

d. Left-click on the network icon and run Diagnose and Repair - reset the
wireless adapter. This occasionally works.

e. If all else fail, reboot your computer and curse. This always works,
but then you sit there, waiting and cursing...


Observations:
There is nothing wrong with the wireless system. Wireless works fine. All
the XP machines on my wireless system work fine. Even when the computer is
disconnected after sleep, the local connection still functions - just the
internet is lost.

There is definitely something wrong with the way Vista comes out of
sleep/hibernation. (This is in the top 3 tech support issues listed on the
Dell support pages.)

I really have to scratch my head that MS has done nothing to address this
issue for over a year!
Well, you can always hope.
 
I have been living with this problem for some time now, and here is what I
have learned:

1. This solution works for quite a number of people : (though sadly, not me)
- Go into Device Manager and click on the "Advanced" properties tab for your
wireless card. Disable "Minimum Power Consumption".

2. This solution has also worked for some:
- Make sure the driver for your wireless card is up to date.
- If that doesn't work, you can try letting the Windows generic driver run
your card.

3. This is always recommended, yet I have seen no evidence or responses
that it works:
- Upgrade the firmware for your wireless router/hub.
(This is really a pain to do. I have done it. It didn't help.)

Here is the list of workarounds:

a. Never let your computer go to sleep (I know, probably unsatisfactory.)

b. Open the Command Prompt and type "ipconfig/renew" after your computer
wakes from sleep. (This works 50-75% of the time for me.)

c. If you have a key combo to disable your card, do that, then re-enable it.
(On my Dell, it is Fn + F2). This usually works, and if it doesn't, it
almost always works if I follow it up with the ipconfig/renew command.

d. Left-click on the network icon and run Diagnose and Repair - reset the
wireless adapter. This occasionally works.

e. If all else fail, reboot your computer and curse. This always works,
but then you sit there, waiting and cursing...


Observations:
There is nothing wrong with the wireless system. Wireless works fine. All
the XP machines on my wireless system work fine. Even when the computer is
disconnected after sleep, the local connection still functions - just the
internet is lost.

There is definitely something wrong with the way Vista comes out of
sleep/hibernation. (This is in the top 3 tech support issues listed on the
Dell support pages.)

I really have to scratch my head that MS has done nothing to address this
issue for over a year!
Well, you can always hope.
..
 
you have posted this three times without actually describing your
problem. while the subject is wireless network and sleep, that isn't
enough to diagnose your issue. if I had to guess, you have a Vista
computer that won't connect after hibernating/sleep. if you could
post the text output of ipconfig /all when it is in this bad state,
we'd know for sure. and send you to
http://support.microsoft.com/default.aspx/kb/933872/en-us

I have been living with this problem for some time now, and here is what I
have learned:

1. This solution works for quite a number of people : (though sadly, not me)
- Go into Device Manager and click on the "Advanced" properties tab for your
wireless card. Disable "Minimum Power Consumption".

2. This solution has also worked for some:
- Make sure the driver for your wireless card is up to date.
- If that doesn't work, you can try letting the Windows generic driver run
your card.

3. This is always recommended, yet I have seen no evidence or responses
that it works:
- Upgrade the firmware for your wireless router/hub.
(This is really a pain to do. I have done it. It didn't help.)

Here is the list of workarounds:

a. Never let your computer go to sleep (I know, probably unsatisfactory.)

b. Open the Command Prompt and type "ipconfig/renew" after your computer
wakes from sleep. (This works 50-75% of the time for me.)

c. If you have a key combo to disable your card, do that, then re-enable it.
(On my Dell, it is Fn + F2). This usually works, and if it doesn't, it
almost always works if I follow it up with the ipconfig/renew command.

d. Left-click on the network icon and run Diagnose and Repair - reset the
wireless adapter. This occasionally works.

e. If all else fail, reboot your computer and curse. This always works,
but then you sit there, waiting and cursing...


Observations:
There is nothing wrong with the wireless system. Wireless works fine. All
the XP machines on my wireless system work fine. Even when the computer is
disconnected after sleep, the local connection still functions - just the
internet is lost.

There is definitely something wrong with the way Vista comes out of
sleep/hibernation. (This is in the top 3 tech support issues listed on the
Dell support pages.)

I really have to scratch my head that MS has done nothing to address this
issue for over a year!
Well, you can always hope.
.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
you have posted this three times without actually describing your
problem.

The 3X posting was unintentional, and not an indication of my irritation
level. (Forum kept bumping me to an email preferences page. There seems to
be no way to edit, or delete a post that was upped by mistake.)

Back to the issue:
Yes, I have precisely the same problem as the original poster, thus I
responded in this thread instead of creating a new one.
post the text output of ipconfig /all when it is in this bad state,

I would be happy to, if you can tell me how to do that without typing the
output by hand. (My command prompt skills are pretty limited.)

This is a "known issue"
Please see: http://support.microsoft.com/default.aspx/kb/933872/en-us
however none of the fixes seem to apply to the Vista 32-bit version?

They do list one of the workarounds I mentioned.
 
there are two downloads on that KB page. one is for x86 which is 32
bit windows.

ipconfig /all instructions:
http://digitalmediaphile.wordpress.com/ipconfig-all-how-to-get-text-output/

The 3X posting was unintentional, and not an indication of my irritation
level. (Forum kept bumping me to an email preferences page. There seems to
be no way to edit, or delete a post that was upped by mistake.)

Back to the issue:
Yes, I have precisely the same problem as the original poster, thus I
responded in this thread instead of creating a new one.


I would be happy to, if you can tell me how to do that without typing the
output by hand. (My command prompt skills are pretty limited.)

This is a "known issue"
Please see: http://support.microsoft.com/default.aspx/kb/933872/en-us
however none of the fixes seem to apply to the Vista 32-bit version?

They do list one of the workarounds I mentioned.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Hi Barb,
there are two downloads on that KB page. one is for x86 which is 32
bit windows.

I tried this, but when I applied it I got "This update does not apply to
your system". That is weird, because the page says it applies to all versions
of Vista. (I am running Vista business.)
ipconfig /all instructions:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\[not shown]>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : [not shown]
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area
Network)
Physical Address. . . . . . . . . : 00-16-CF-D8-6B-9B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1500 Draft 802.11n WLAN
Min
i-Card
Physical Address. . . . . . . . . : 00-16-CF-A8-BB-F5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d8e:91ac:5de7:6940%8(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.105.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 184555215
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-15-C5-BF-01-17
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.105.64%25(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 
please unbind IPv6
http://digitalmediaphile.wordpress.com/ipv6-how-to-unbind-from-a-nic-in-windows-vista/

does this help?

Hi Barb,
there are two downloads on that KB page. one is for x86 which is 32
bit windows.

I tried this, but when I applied it I got "This update does not apply to
your system". That is weird, because the page says it applies to all versions
of Vista. (I am running Vista business.)
ipconfig /all instructions:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\[not shown]>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : [not shown]
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area
Network)
Physical Address. . . . . . . . . : 00-16-CF-D8-6B-9B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1500 Draft 802.11n WLAN
Min
i-Card
Physical Address. . . . . . . . . : 00-16-CF-A8-BB-F5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d8e:91ac:5de7:6940%8(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.105.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 184555215
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-15-C5-BF-01-17
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.105.64%25(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
That did not help.

I think I will just wait for Vista SP-1 which is due out soon. Maybe they
have resolved the problem.

Thanks for your trouble.
 
Go to Change Advanced Power Settings.
Set hard drive to turn off a minute or 2 before sleep.

Set Hybrid and Hibernate modes to "Off"

Under USB settings select "Disable"

Under Multimedia select "Allow ....."
 
This problem is still not fixed after installing SP1.
I see lots of posts all over the place where people have the same problem.
I see a lot of suggestions. Everyone tries them. They do not work.
I tried everything suggested here and then some.

Is there any solution here other than just never letting your computer go to
sleep?
 
Bob,

It might sound rude, but...

People are going in circles, and as far as I can see, you always stop in the
first stages and let the imagination do the rest. Did you notice that out of
every 10 faults, about 1 or so can be fixed?

If gurus like yourself and Chuck can't fix it, isn't it obvious (after
34,590,599,546 posts or so) that something is seriously damaged in the
recent upgrades when it comes to workgroup file sharing, especially with XP?

Common denominators:

1. Workgroup, rather than domain, authentication.
2. Some computers are running XP, some are running Vista. Most of those that
run Vista are laptops - which essentially means wireless connection for
most.
3. People recently upgraded to SP1 or used fixes that constitute it.

You're an MVP, so you probably have a direct channel to the almighty (MS).
Is it possible to ask them to check this stuff again?

Dell's support pretends that me and my problem don't exist. I spent a
***load of time trying to figure this out, and my time (just like everybody
else's) costs money; much worse, this stuff disrupts my work during a very
critical period.
 
do you have the driver from
http://support.dell.com/support/dow...-1&impid=-1&formatcnt=1&libid=5&fileid=202823

installed?

This problem is still not fixed after installing SP1.
I see lots of posts all over the place where people have the same problem.
I see a lot of suggestions. Everyone tries them. They do not work.
I tried everything suggested here and then some.

Is there any solution here other than just never letting your computer go to
sleep?
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Bob,

It might sound rude, but...

People are going in circles, and as far as I can see, you always stop in the
first stages and let the imagination do the rest. Did you notice that out of
every 10 faults, about 1 or so can be fixed?

If gurus like yourself and Chuck can't fix it, isn't it obvious (after
34,590,599,546 posts or so) that something is seriously damaged in the
recent upgrades when it comes to workgroup file sharing, especially with XP?

Common denominators:

1. Workgroup, rather than domain, authentication.
2. Some computers are running XP, some are running Vista. Most of those that
run Vista are laptops - which essentially means wireless connection for
most.
3. People recently upgraded to SP1 or used fixes that constitute it.

You're an MVP, so you probably have a direct channel to the almighty (MS).
Is it possible to ask them to check this stuff again?

Dell's support pretends that me and my problem don't exist. I spent a
***load of time trying to figure this out, and my time (just like everybody
else's) costs money; much worse, this stuff disrupts my work during a very
critical period.

Vadim,

I don't pretend to know all of the answers. What I do know is though if people
keep insisting that there is one problem, the problems will never be solved.

You have to separate each individual problem from each other individual problem,
and attack one problem at a time. If you finish solving two or three problems,
and find that they had a common cause, that's very well and good.

But work on one problem at a time. Don't get into another thread and suggest:
"I had this problem, and fixed it this way."
Unless you were the one who diagnosed the problem, and you can show the new
poster how to diagnose his.
<http://networking.nitecruzr.net/2005/10/computer-uniqueness.html>
http://networking.nitecruzr.net/2005/10/computer-uniqueness.html

Now, along with seeing that many people are reporting problems, you need to
understand etiology. This is a help forum, and it's not unusual that you will
see problem reports here. That's what people post here. Problem reports. But
seeing the problem reports, don't summarily conclude that there is a worldwide
epidemic of problems. Many people are using Vista, some of them have SP1, and
the ones who don't have any problems don't post here.
<http://blogging.nitecruzr.net/2007/04/etiology-blogger-and-you.html>
http://blogging.nitecruzr.net/2007/04/etiology-blogger-and-you.html

What Robert and I do (try to do) is called triage. That's where diagnosis
starts.
 
Vadim,

Chuck and I are just volunteers and try to help. We may be able to pass some
issues to Microsoft. Some Microsoft employees may read posts. However,
improving Microsoft products and services is beyond our control. Let us just
focus on the issue, please.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
 
Hi Chuck,

Thanks for patiently explaining this stuff. (Actually, I didn't realize you
two are volunteers, I thought you are being paid for giving technical
support.)

Yes, I see the parallels that you're implying about.

However, consider this. Out of 1,000 admitted patients about 700 have
exactly the same symptoms, and it happened under exactly the same
circumstances - and in the same period of time. Dr House with IQ of 200+ and
years of experience can only diagnose, say, 20 of them. If this is not an
epidemic, then what is? Real epidemics do happen, don't they? It's not even
about an epidemic; it's about Dr House scratching his head and unable to
find the cause.

You're being modest, but so far I couldn't find any blog on the web giving
better and more detailed advices than yours (and I searched well). Let's
face it: most of the cases such as mine are left unresolved, and you know
this stuff inside out.

I usually fix my hardware / software problems myself; I spent a week trying
to figure this out by myself, then stumbled upon your blog, and then posted
here, and after learning your blog by heart and 9 posts - still nothing. I'd
say more: in a week or so, I only saw one or two of these problems resolved.
Bob usually gives up after 2 posts, you - after 7 or 9. If you people can't
figure it out, a regular MS techsupport guy doesn't stand a chance.

Since you are volunteers, I can't ask much, and you really did a lot - thank
you for that. I'll go harass Microsoft, if it doesn't work - I'll gather
more people and repeat the exercise.

Regards,
Vadim
 
Bob,

Thank you for your reply.

As stated in the message to Chuck, I'll try to contact Microsoft. Won't harm
in any case.

And thank you for trying to help in any case.

Regards,
Vadim
 
Back
Top