Target.lnk error - Windows XP

[randy benson]

There was a thread with this subject started 2003-09-17 by Eric that never
got resolved, as far as I can tell, and I'm having the same problem:
<quote>
"Anyone seeing this? I'm trying to browse the network while doing a
'save as' in a program. I'm using a Windows XP computer (fully
updated). The rest of the network is Windows 2000 (fully updated).
When I click on My Network Places it shows the same folders as it does
in c:\documents and settings\Username\nethood. When I click on
'Entire network' I can browse through no problem. When I click on a
direct network folder link I sometimes get an error saying:

"The drive or network connection that the shortcut target.lnk refers
to is unavailable. Make sure the disk is properly inserted or the
network resource is available". I press "OK" and the folder contents
are displayed properly. I went to the Nethood directory and deleted
all of the folder links and recreated them, but it still does it.

Like I said, there is no error if I browse to the network directory
using "Computers near me" (which I added), or browsing through "Entire
Network", or even if I browse through "My Network Places" from the
desktop and use the same folder shortcut. It only seems to happen
when I am trying to "save/open/save as" in a program and then try to
access the same networked folder shortcut."
<unquote>

This was tracked to the critical update 821557, which according to a reply
by Meku, cured the problem by its removal.

1) Has anyone but me still got this problem? Every time I try to 'save as'
from an application, I get "The drive or network connection that the
shortcut target.lnk refers to is unavailable. Make sure the disk is
properly inserted or the network resource is available". I press "OK" and
the folder contents are displayed properly.

2) 821557 doesn't show up in my uninstal folder except as a part of rollup
826939 (MS03-027); when I try to uninstall 826939, the uninstall fails with
the complaint that spuninst.exe "setup cannot copy the file ntdll.dll",
although it exists in the uninstall folder.

3) Is there any way to uninstall 821557 separately from 826939?

4) Is there any other way to cure this?

 

[ted jordan]

i reinstalled memory to get rid of the "setup cannot install file" ... error
message

ted

 

[randy benson]

?

Cheers -- but that wasn't it -- I spent 6 hours with MS Tech Support today,
and Joy has returned to Muddville. I'm tired; I'll post the cure tomorrow

 

[randy benson]

Hi folx --

Never really got this one resolved either -- after I called MS, obtained &
installed the hotfix for KB824143, the system degenerated into a continuous
boot problem that like I said took 6 hours on the phone with a competent,
patient MS tech support guy in India to correct; after trying what seemed
like a dozen unsuccessful fixes, he finally cured the perpetual boot prob
with a 'big copy' of system files. The original issue I was trying to cure
with the hotfix remains:

"The drive or network connection that the shortcut target.lnk refers
to is unavailable. Make sure the disk is properly inserted or the
network resource is available". I press "OK" and the folder contents
are displayed properly.

but by now I'm so happy just to be booting successfully again that I'm
unwilling to try and fix it again. I'll wait for SP3...

FWIW, here's a copy of his instructions (he first had me copy and email my
c:\windows\system32\system, which he then resurrected and sent back - a
quick DOS copy and I was back in business):

<quote>
Here are the instructions I was speaking of for a Big Copy of Windows 2000.
The overall scheme is to copy the core Windows 2000 files (files in
\System32 and \Drivers folder).

1. First, install Windows 2000 Advanced Server to another partition on the
server. For this install, just install it as a Member Server for simplicity
sake. I think you said that you have plenty of space on the E: and Service
Pack it up to the same Service Pack as the corrupted install. Note that
this is also testing the hardware on the server. If the install goes bad or
it can't boot, then we're looking at bad hardware. Call Compaq immediately
to get assistance.

2. Once you have installed a parallel, you should be able to see the
original drive and install folder (most commonly C:\Winnt). Go into that
folder and make a copy of the System32 folder and the Drivers folder and
copy it to the E: drive as a backup.

3. Once you do that, go into the new installation's \winnt folder and go
into the drivers folder. In there, select and copy all the files in there
(just the files, NOT THE FOLDERS!) and paste them into the drivers folder of
the corrupted installation.

4. Once we do this, reboot and try to go into the original installation.
Note that the original install will be the second choice on the boot menu.

5. If this does not work, then try safe mode and see if it hangs at the same
spot.

6. If the problem persists and this machine is a Domain Controller, then
call or email me and I will call you back. If the original install is a
member server then continue with the next steps

WARNING: DO NOT CONTINUE WITH THE NEXT STEPS IF THE ORIGINAL INSTALLATION IS
A DOMAIN CONTROLLER

7. Boot back into the parallel installation and this time, copy the files
(again, not the folders) from the System32 folder over to the original
installation.

Thanks,

Ayham Helwani

<endquote>