Re: Transferring programmes from one partition to another

From: Crash Override (CrashOverride_at_discussions.microsoft.com)
Date: 11/01/04 

Date: Mon, 1 Nov 2004 09:44:06 -0800

You are making the assumption that all developers code their apps to the use
the same dll location. This simply is not true in practice. The exe does in
fact call the dll, however it is called based on an association in the
registry. If the exe file is moved, the association is broken and is not
guranteed to work. The dll may look to the registry but since the exe and
other files were moved, the registry entries are incorrect resulting in a
broken application. Depending on the size of the application and the number
of registry entries involed, you could in theory anyway, update the registry
manually. Not really a place for an amatuer to be poking around in though.
  
"Lee Chapelle" wrote:

>
> "Crash Override" <CrashOverride@discussions.microsoft.com> wrote
> >
> >
> > "Lee Chapelle" wrote:
> >
> > >
> > > "Shenan Stanley" <news_helper@hushmail.com> wrote
> > >
> > > >> I want to have all my programmes on C. At the moment I have some on C
> > > >> and D. Can I transfer all the programmes in D to C by copy and paste?
> > > >
> > > > Likely not.
> > > >
> > > > The number of registry/dll enties/files found on your C drives would
> > > > likely prohibit this.
> > > > Uninstall the applications you wish to move, reinstall them on the D
> drive
> > > > appropriately.
> > >
> > > This frequently works just fine. When you move the application files you
> are
> > > not altering the registry entries or moving dlls. As long as the
> application
> > > support system remains in place the executable should still be able to
> > > function whether from D: or C:.
> > >
> > > I would suggest try one at a time testing as you go.
> > >
> > >
> > > Lee, you have this completely backwards. This practice does not work
> unless you are talking about simple exe files that have no dll or ocx files
> associated with them. Most complex applications have hundreds of files
> associated with them and as many, if not more, registry entries. Moving the
> files will cause the application not to function because the registry
> expects to find the file(s) in a specific location. The registry is not
> dynamically updated when a file is simply moved. The proper way of dealing
> with what the OP asked is to uninstall the applications they want moved and
> then reinstall them. This is the only surefire way to put them where you
> want and have them still function.
>
> I agree that is a better general idea, but one does not always have that
> luxury.
>
> The dlls are generally installed to some folder like c:\windows\system,
> those are not being moved, nor are the registry entries. The executable
> calls the dll and the registry entries, not the other way round. When the
> executable is run it calls the dll. When it looks in c:\windows\system where
> it expects to find a dll, it is there. When it refers to the registry, it
> finds the settings there also. If there are support files within the same
> Program Files folder, they will also be unmoved relative to the executable.
>
>
>

Relevant Pages

  • Problem with performance of IDE devices
    ... index 0, dll tcpstk.dll, context 0x3f8a5c9 ... 0x801abbe8: FSREG: Mounted ROM portion of boot registry ... 0x8014abcc: FSREG: Invalid HKEY 0x00000000 ...
    (microsoft.public.windowsce.platbuilder)
  • Re: secure32.exe
    ... > kind of search could be used - I tried to search files that had the text ... Exe can register this dll as Winlogon ... or as extension in AppInit_Dlls registry key - this allows dll to ...
    (microsoft.public.security.virus)
  • Re: Using same interfaces for in-proc vs. out-proc
    ... I forgot to mention that when I compile the DLL after removing the TYPELIB ... and REGISTRY entries in the RC file I still get this message: ... for the COM part is in the same project as the rest of the EXE code. ...
    (microsoft.public.vc.atl)
  • Re: COM beginner - 2 apps using the same instance of a component.
    ... >> a DLL). ... > an in-proc dll server is because that is how it is used most of the time, ... > I realise I could make an out of proc server exe project and just make it ... > I would prefer not to touch the registry for this project, ...
    (microsoft.public.win32.programmer.ole)
  • Re: HowTo: Unregister a DLL/Control when the File no longer Exists
    ... Tony Proctor wrote: ... recorded in the registry. ... However, matching them up without the original DLL ... The main project references one of the DLLs, ...
    (microsoft.public.vb.general.discussion)
Loading