XP/.net problem - .lnks open windows

  • Thread starter Thread starter t_p_paterson
  • Start date Start date
T

t_p_paterson

Dear All,

We're having a problem on two of the machines in our office.

When we open a dialog box to save or open (for example in AutoCAD), if
we click on a link to a directory on the network (\\SERVERNAME
\DRIVELETTER\FOLDER), instead of the dialog box looking into that
directory, it opens a new window with that directory. Not very
helpful for saving. We can get there via the drop-down My Network
Places and navigating all the way through, but that's not a great
solution.

Anyone who can explain what is going on and how to fix it? It's like
there's a driver or object not running correctly.

I believe it is .net related as these are the only two machines which
have successfully run the .net 2.0 and 3.0 updates.

Many thanks,

Thomas.
 
How does this related to Windows Update?

The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.

We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.

For that reason, I believe the problem originates with an update.

Thomas.
 
The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.

We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.

For that reason, I believe the problem originates with an update.

[To keep track of things, it helps immensely if you include all of previous
message(s) in your replies to the newsgroup. Thank you.]

My apologies for not seeing that you'd crossposted to WinXP and Windows
Update newsgroups.

What updates specifically are you referring to?

If the problems are related to the .NET Framework updates you installed,
uninstalling them should correct the problem. Does it?
~~
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/
 
(e-mail address removed) wrote:

<paste>


The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.
We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.
For that reason, I believe the problem originates with an update.

[To keep track of things, it helps immensely if you include all of previous
message(s) in your replies to the newsgroup. Thank you.]

My apologies for not seeing that you'd crossposted to WinXP and Windows
Update newsgroups.

What updates specifically are you referring to?

If the problems are related to the .NET Framework updates you installed,
uninstalling them should correct the problem. Does it?
~~
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Adminhttp://aumha.net
DTS-Lhttp://dts-l.net/

Uninstalling them didn't work - they won't uninstall as they claim
multiple pieces of software with dependency. We tried reinstalling
windows because we'd had problems with the .net framework and this was
the result. That was a format-and-reinstall.
 
We're having a problem on two of the machines in our office.
When we open a dialog box to save or open (for example in AutoCAD), if
we click on a link to a directory on the network (\\SERVERNAME
\DRIVELETTER\FOLDER), instead of the dialog box looking into that
directory, it opens a new window with that directory. Not very
helpful for saving. We can get there via the drop-down My Network
Places and navigating all the way through, but that's not a great
solution.

Anyone who can explain what is going on and how to fix it? It's like
there's a driver or object not running correctly.

I believe it is .net related as these are the only two machines which
have successfully run the .net 2.0 and 3.0 updates.
</paste>

How does this relate to Windows Update?
The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.
We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.
For that reason, I believe the problem originates with an update.

[To keep track of things, it helps immensely if you include all of
previous
message(s) in your replies to the newsgroup. Thank you.]

My apologies for not seeing that you'd crossposted to WinXP and Windows
Update newsgroups.

What updates specifically are you referring to?

If the problems are related to the .NET Framework updates you installed,
uninstalling them should correct the problem. Does it?
~~
Uninstalling them didn't work - they won't uninstall as they claim
multiple pieces of software with dependency. We tried reinstalling
windows because we'd had problems with the .net framework and this was
the result. That was a format-and-reinstall.

[crosspost to Windows Update newsgroup removed]

Are both machines currently fully patched at Windows Update?

What .NET Framework versions are currently installed?
 
I am having the same problem as you and have no idea why but I'm also having
a problem with automatic update. I get error code 0x80242006 for update
KB934238. Have any ideas? This has been going on for 2 weeks now and I'm
completely stumped. Thanks for your assistance.
 
<paste>
We're having a problem on two of the machines in our office.
When we open a dialog box to save or open (for example in AutoCAD), if
we click on a link to a directory on the network (\\SERVERNAME
\DRIVELETTER\FOLDER), instead of the dialog box looking into that
directory, it opens a new window with that directory. Not very
helpful for saving. We can get there via the drop-down My Network
Places and navigating all the way through, but that's not a great
solution.
Anyone who can explain what is going on and how to fix it? It's like
there's a driver or object not running correctly.
I believe it is .net related as these are the only two machines which
have successfully run the .net 2.0 and 3.0 updates.
</paste>
How does this relate to Windows Update?
The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.
We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.
For that reason, I believe the problem originates with an update.
[To keep track of things, it helps immensely if you include all of
previous
message(s) in your replies to the newsgroup. Thank you.]
My apologies for not seeing that you'd crossposted to WinXP and Windows
Update newsgroups.
What updates specifically are you referring to?
If the problems are related to the .NET Framework updates you installed,
uninstalling them should correct the problem. Does it?
~~
Uninstalling them didn't work - they won't uninstall as they claim
multiple pieces of software with dependency. We tried reinstalling
windows because we'd had problems with the .net framework and this was
the result. That was a format-and-reinstall.

[crosspost to Windows Update newsgroup removed]

Are both machines currently fully patched at Windows Update?

What .NET Framework versions are currently installed?
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Adminhttp://aumha.net
DTS-Lhttp://dts-l.net/

..NET 1.1 and .NET 2.0 at the moment. One of the two machines also
has .NET 3.5
 
<paste>
We're having a problem on two of the machines in our office.
When we open a dialog box to save or open (for example in AutoCAD),
if
we click on a link to a directory on the network (\\SERVERNAME
\DRIVELETTER\FOLDER), instead of the dialog box looking into that
directory, it opens a new window with that directory. Not very
helpful for saving. We can get there via the drop-down My Network
Places and navigating all the way through, but that's not a great
solution.
Anyone who can explain what is going on and how to fix it? It's like
there's a driver or object not running correctly.
I believe it is .net related as these are the only two machines which
have successfully run the .net 2.0 and 3.0 updates.
</paste>
How does this relate to Windows Update?
The update that seems to have caused it was an Update to .NET
framework 1.0 or 2.0 sent through Automatic updates.
We have two machines that are otherwise identical, but the updates
didn't install (failed). On these machines, we don't have the bug.
For that reason, I believe the problem originates with an update.
[To keep track of things, it helps immensely if you include all of
previous message(s) in your replies to the newsgroup. Thank you.]
My apologies for not seeing that you'd crossposted to WinXP and Windows
Update newsgroups.
What updates specifically are you referring to?
If the problems are related to the .NET Framework updates you
installed,
uninstalling them should correct the problem. Does it?
~~
Uninstalling them didn't work - they won't uninstall as they claim
multiple pieces of software with dependency. We tried reinstalling
windows because we'd had problems with the .net framework and this was
the result. That was a format-and-reinstall.

[crosspost to Windows Update newsgroup removed]

Are both machines currently fully patched at Windows Update?

What .NET Framework versions are currently installed?
--
.NET 1.1 and .NET 2.0 at the moment. One of the two machines also
has .NET 3.5

Repost: Are both machines currently fully patched at Windows Update?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top