Deleted files re appear in the folder?

[tomer]

Hi
I am trying to delete a DLL from a folder,the DLL appears in the RECYCLE BIN
But when i open the folder i can see the "deleted" dll!!

What am i doing wrong?

thanks in advance.

[Jason Teagle]

> I am trying to delete a DLL from a folder,the DLL appears in the RECYCLE
BIN
> But when i open the folder i can see the "deleted" dll!!
>
> What am i doing wrong?

Which DLL are you trying to delete and why? WinXP protects files it has
listed as special system files and will put them back if you try to delete
them.


--
--
Jason Teagle

[tomer]

So how i can i create installtion for my software which need to update some
dll's
like OLE,JET etc..?


thanks.


"Jason Teagle" > wrote in message
...
> > I am trying to delete a DLL from a folder,the DLL appears in the RECYCLE
> BIN
> > But when i open the folder i can see the "deleted" dll!!
> >
> > What am i doing wrong?
>
> Which DLL are you trying to delete and why? WinXP protects files it has
> listed as special system files and will put them back if you try to delete
> them.
>
>
> --
> --
> Jason Teagle
>
>
>

[Jason Teagle]

> So how i can i create installtion for my software which need to update
some
> dll's
> like OLE,JET etc..?

Well, with installer packages they will try to install the version of the
DLLs they think are right; if the installed DLL is newer than what the
system had, XP will leave them alone. If it is older than the one XP already
had, it will be silently replaced - the installer will think it succeeded.

You made it sound as if you were trying to manually delete the DLL... if you
just delete it rather than replacing it with another one, then XP has no
choice but to replace it. If you have a legitimate updated version of the
DLL, then XP should allow you to replace it if it's done with a proper
install package (including ones you can set up, such as InstallShield and
InnoSetup).

If you're creating an install package, that will take care of making the
attempt to install a new DLL, and XP will take care of not allowing old
copies to creep in.

To be honest, though, you should not be trying to update those particular
files (the ones you mentioned) since they are so close to the system core.
It is better to point users to an official MS update package that will
install the latest Jet (after all, you can't have anything later than they
have!)... or maybe even just tell them to use Windows Update to update the
required packages (for example, using critical updates to patch issues).
Otherwise you risk installing only half a matched set of DLLs, and that will
cause major problems for the end user.

Does this help?


--
--
Jason Teagle

[tomer]

Yes, you helped me a lot!!

The system files which i mentioned,are installed using microsoft
installtion package

VBRUN60SP5 and JET 4.0 SP 8(WINDOWS XP-KB829558-X86-ENU.EXE)

Maybe a better way is to run(possible?) the windows update from my
installtion package?

thanks in advance.

"Jason Teagle" > wrote in message
...
> > So how i can i create installtion for my software which need to update
> some
> > dll's
> > like OLE,JET etc..?
>
> Well, with installer packages they will try to install the version of the
> DLLs they think are right; if the installed DLL is newer than what the
> system had, XP will leave them alone. If it is older than the one XP
already
> had, it will be silently replaced - the installer will think it succeeded.
>
> You made it sound as if you were trying to manually delete the DLL... if
you
> just delete it rather than replacing it with another one, then XP has no
> choice but to replace it. If you have a legitimate updated version of the
> DLL, then XP should allow you to replace it if it's done with a proper
> install package (including ones you can set up, such as InstallShield and
> InnoSetup).
>
> If you're creating an install package, that will take care of making the
> attempt to install a new DLL, and XP will take care of not allowing old
> copies to creep in.
>
> To be honest, though, you should not be trying to update those particular
> files (the ones you mentioned) since they are so close to the system core.
> It is better to point users to an official MS update package that will
> install the latest Jet (after all, you can't have anything later than they
> have!)... or maybe even just tell them to use Windows Update to update the
> required packages (for example, using critical updates to patch issues).
> Otherwise you risk installing only half a matched set of DLLs, and that
will
> cause major problems for the end user.
>
> Does this help?
>
>
> --
> --
> Jason Teagle
>
>
>

[Alex Nichol]

tomer wrote:

>I am trying to delete a DLL from a folder,the DLL appears in the RECYCLE BIN
>But when i open the folder i can see the "deleted" dll!!



That will be a protected mode dll, and system file protection is
restoring a standard copy to prevent the stability (or indeed
functioning) of the system being put at risk. Precisely which dll is
this and what are you trying to achieve?


--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. (remove the D8 bit)

[Jason Teagle]

> The system files which i mentioned,are installed using microsoft
> installtion package
>
> VBRUN60SP5 and JET 4.0 SP 8(WINDOWS XP-KB829558-X86-ENU.EXE)
>
> Maybe a better way is to run(possible?) the windows update from my
> installtion package?

I honestly don't recommend this. For one thing, if your program is to be
used on a non-XP machine, then this would be the wrong update for that
machine. For another thing, etiquette says you should not make core changes
/ updates to a user's machine without their agreement, and installing such
updates is exactly that.

Your install package should provide a readme file BEFORE it starts trying to
install files, which explains to the user that they need to update their Jet
package, and gives a quick description of how they can do this (not a link
to that file, since as I said it is not right for all machines!). If they
don't go and do this before installing your program, then they can't
complain that the program doesn't work because you told them why.

(As for VBRUN60SP5, I believe it is reasonably safe to do that automatically
since it is not a core update but rather just some additional files -
however, if this update corresponds to the SP5 that developers apply to
Visual Studio, then there is a risk that the update may break existing VB
programs on the user's machine that were written without the service pack.
I'm not saying don't do it, just trying to advise of the possible
side-effect.)


--
--
Jason Teagle