Knowing which DLLs are missing 
Author Message
 Knowing which DLLs are missing

  Delphi requires no DLL's to run, unless you're using the BDE or
ReportSmith....  So, what DLL is it you're using?

--
Jason Wallace
SL Software

--
"We are MicroSoft.  You will be assimilated.  Resistance is Futile."
--

Quote:

>Hi Folks,

>I am building an application with Delphi 2.0 Developer and it runs
perfectly
>in my computer, but I doesn't work in no other computer (where Delphi is
not
>installed). I think that some DLLs may be missing, but I was not able to
>detect which ones... I know exactly the program line that is causing the
>error. Is there any way to know what DLL is this command line using that is
>not present in the machines???

>I tried to use TDump utility to know all required DLLs, but it does not
show
>me all DLLs needed, just some...
>Is there a solution??? Or will I have to install Delphi in all machines???
>(I wont do it, just joking!)



Wed, 18 Jun 1902 08:00:00 GMT
 Knowing which DLLs are missing

Hi Folks,

I am building an application with Delphi 2.0 Developer and it runs perfectly
in my computer, but I doesn't work in no other computer (where Delphi is not
installed). I think that some DLLs may be missing, but I was not able to
detect which ones... I know exactly the program line that is causing the
error. Is there any way to know what DLL is this command line using that is
not present in the machines???

I tried to use TDump utility to know all required DLLs, but it does not show
me all DLLs needed, just some...
Is there a solution??? Or will I have to install Delphi in all machines???
(I wont do it, just joking!)

Thanks in advance

                                                      []s Rafael Guimaraes



Wed, 18 Jun 1902 08:00:00 GMT
 Knowing which DLLs are missing


Quote:

>  Delphi requires no DLL's to run, unless you're using the BDE or
>ReportSmith....  So, what DLL is it you're using?

Or any OCX or VCL that uses external DLLs.
Yesterday I had a problem installing my program on a new PC. It already
installed on 4 other PCs on the same LAN without a problem. But this time I
always got the message that (something) was not registered. It uses an OCX,
but I had installed it along with 3 DLL's that it uses.
But in the end it turned out that the PC didn't have the MS DLLs that very
often has to be installed with OCX's: MFC40.DLL and MSVC40.DLL. They are
usually installed by a lot of other programs though, so I never bother
putting them on my install disks, as I always install them myself. It's like
with the VB run-time DLLs.

Quote:
>>I am building an application with Delphi 2.0 Developer and it runs
>perfectly
>>in my computer, but I doesn't work in no other computer (where Delphi is
>not
>>installed). I think that some DLLs may be missing, but I was not able to
>>detect which ones... I know exactly the program line that is causing the
>>error. Is there any way to know what DLL is this command line using that is
>>not present in the machines???

>>I tried to use TDump utility to know all required DLLs, but it does not
>show
>>me all DLLs needed, just some...
>>Is there a solution??? Or will I have to install Delphi in all machines???
>>(I wont do it, just joking!)

--
|| Bjorn K. Nilssen      // http://home.sn.no/~bjoernk/  // mainly 3D ||


Wed, 18 Jun 1902 08:00:00 GMT
 Knowing which DLLs are missing

I used the TFTP component, which obviously is an ActiveX component, and I
put the required OCX and those dlls you refer to (MFC40.DLL and MSVC40.DLL)
in the windows/system directory on the destination computer.
I still get an EOLEsys exception when I try to start my application...

Q1: What can be wrong?
Q2: Do I have to REGISTER all OCX and DLL files, even if they are in
windows' system directory? In that case; Why?



Wed, 18 Jun 1902 08:00:00 GMT
 Knowing which DLLs are missing

Quote:

> I used the TFTP component, which obviously is an ActiveX component,
> and I
> put the required OCX and those dlls you refer to (MFC40.DLL and
> MSVC40.DLL)
> in the windows/system directory on the destination computer.
> I still get an EOLEsys exception when I try to start my application...

> Q1: What can be wrong?
> Q2: Do I have to REGISTER all OCX and DLL files, even if they are in
> windows' system directory? In that case; Why?

OCX's are not found via their filename, like DLL files are. Instead
there is a GUID ((allegedly) Globally Unique ID), which is a 128 bit
number which is used as a lookup into the system registry to locate the
executable code related to that ID.  Even if you copy the OCX into the
system directory (or any other directory for that matter) when your
application is looking for a specific GUID, the system will have no idea
where to look to find the actual executable for it.  That is where
registering comes in.  In fact, I recommend putting OCX's or ActiveX
DLL's into the application directory, because it reduces the likelyhood
of a filename collision.

-andrew



Wed, 18 Jun 1902 08:00:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Missing dll message - oidmfnt.dll

2. INITIALIZE DEVICE- -What am I missing???

3. What am I missing....?

4. Integrated Security: What am I missing here?

5. HELP: Am I missing the point or something ?

6. Help with SQL Query - what am I missing?

7. What am I missing

8. Am I missing something????

9. Transaction Snapshots - What am I Missing?...

10. Simple set variable, what am I missing

11. What am I missing???

12. Restore of Master -- What am I missing?


 
Powered by phpBB® Forum Software