|
-
Jun 19th, 2005, 10:59 AM
#1
Thread Starter
Hyperactive Member
Obtaining DLL files
I know that we aren't supposed to use dll files from the system32 folder, but what if I do a fresh install on a computer then copy the dlls on to a disk for use. Would it be safe to use those files?
The reason I ask is because I used ********** and it said I have 32 files not found. I am having a real hard time finding all the dll files that it wants.
I thought my idea would work because the dlls would not have been altered by any programs that were installed.
Any help would be great. I never knew about the dangers of using system32 files before recently so this is the first time I am giving this much attention to this matter and want to make sure I do it right from now on.
Thank you for your help.
By the way, I have done a search of this forum, google, and searched the microsoft site and have found some files for download but am having a hard time finding many of them.
-
Jun 19th, 2005, 11:02 AM
#2
Re: Obtaining DLL files
Have you tried this page?
http://www.dll-files.com/
ØØ
-
Jun 19th, 2005, 01:00 PM
#3
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
Yes, here are the ones that I cannot find that ********** says that I need.
msjint35.dll
msjro.dll
msjter35.dll
msrepl35.dll
vbajet32.dll
the other ones it says that I need I am not so sure that I need.
vb5db.dll
vb6stkit.dll
Thank you for the help.
-
Jun 19th, 2005, 04:06 PM
#4
Re: Obtaining DLL files
What about this page then? I tried one of yours and found it:
http://www.dlldump.com/download-dll-.../download.html
It was the first result using google...
ØØ
-
Jun 19th, 2005, 04:08 PM
#5
-
Jun 19th, 2005, 04:42 PM
#6
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
I was at that page at one point but I was doing them in alphabetical order so I must have forgotten to go back to that page for those.
Thank you for the help.
-
Jun 19th, 2005, 05:26 PM
#7
Re: Obtaining DLL files
You should use Inno Script as well as the Automatic OS Updater, available from www.***********
-
Jun 19th, 2005, 05:57 PM
#8
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
Ok, these are the last ones that it says that I need, that I haven't been able to find.
32autole.dll
msdev.exe
regsvr32.exe
msod.dll
rebootnt.exe
-
Jun 19th, 2005, 05:59 PM
#9
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
I am using **********. When I made my own script with inno and opened the lst file in notepad I didn't have half the files that ********** is telling me I need to use.
-
Jun 20th, 2005, 03:57 AM
#10
Re: Obtaining DLL files
Krenshau,
You have those file but you failed to read the documentation on SAFE/UNSAFE files. This would give you a key to where these files are and why they are unsafe and what you should or could do to remedy the situation.
-
Jun 20th, 2005, 10:37 PM
#11
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
I did not fail to read the safe unsafe files section.
Here it is:
Unsafe File Processing
********** comes with a file named UnSafe.fil that resides in the same location where ********** was installed. Using this feature you can select if you want the program to check to see if the files in the script are unsafe and if found in the list they will be eliminated from the script. Unsafe File Processing is not to be confused with Unsafe Mode, of which if selected ********** will search the Windows System folders for files otherwise in Safe Mode the program will not search these folders for files.
The only time it will seem like the Windows System folders are searched is when ********** finds files that are in the systems folder even though Safe Mode is on. This is because the registry is checked to see if the file is registered and if so it will take the source location from the registry.
You can edit the Unsafe.fil file to include any files that are not on the list at the time of release. You can open this file from the main screen to edit or browse it.
of the entire sections this portion:
"********** comes with a file named UnSafe.fil that resides in the same location where ********** was installed. Using this feature you can select if you want the program to check to see if the files in the script are unsafe and if found in the list they will be eliminated from the script."
Is the only part that deals directly with unsafe files. The rest says what unsafe files are not. This section doesn't say why this is important, why the files are unsafe. How to get safe files or make the ones you have safe. If you need the files that are found to be unsafe.
In fact there is no section that explains the logic of the search. How does the program know what files to look for, what basis is it using to think that it needs the files.
Randem, please, please, please don't take what I am saying as knocking the program. In my novice understanding of this area it looks like a great program, and based on it's usage that I have seen people talk about, I am confident that it works great. I am just trying to express the frustration of lack of information. It's like learning to swim by jumping in the ocean. After a while you can figure it out, but until you do it is a great challenge. I want to learn to use and understand ********** as well as the people that have been doing this for years. I just don't want to have to learn it by trial and error.
-
Jun 20th, 2005, 11:02 PM
#12
Re: Obtaining DLL files
Krenshau,
Here are some explainations from the manual. Let me know where you are having problems in operation.
Installation Problems
Searching
If searching takes longer than you expect on a conversion... (The program may seem to be hung), you can change the primary search paths that ********** takes in its search for source files. If files are not found, just add the folder to the search path and it will be found the next time you attempt a conversion.
HINT: Add the new folder to the start of the search path area.
The Path Refresh button will get the computers current path and replace the text in the search path area.
UNC path names can be added automatically to the .iss output file by just depressing the UNC button in the toolbar. If you do not want UNC path names, leave it un-depressed.
After searching for the files that belong to the script, ********** will replace your search path area with only the folders where files were actually found. This will speed up searching on the next conversion. This is because the program searches the search path area folders first when attempting to find files
More complex processes can be done once you familiarize yourself with **********’s features:
1. Safe Mode - Do not get any files from any systems folders. - Default
2. Unsafe Mode - Get files from systems folders.
-
Jun 26th, 2005, 09:57 AM
#13
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
I think I have this figured out. I am uploading my iss file if someone could take a look at it and tell me if it looks right? I didn't use ********** but I did read the information and built my own based on it. I think because I couldn't see exactly what was going on I didn't understand it well. It helps me to see exactly what everything is and what it does.
Thank you to whoever can look at this and check it over.
I want to make sure it works for Windows 95 to XP.
BTW, your post gives an example of what I am posted previously, no offense. I don't know what a UNC is, maybe I should, but I don't.
-
Jun 26th, 2005, 11:12 AM
#14
Re: Obtaining DLL files
Krenshau,
I will take a look when I can. But most things are only a Google away:
UNC path
Universal/Uniform Naming Convention. A UNC path describes the location of a volume, directory, or file.
The format for a UNC path is \\server\volume\directory\file and is not case-sensitive. For example:
\\Shared1_svr\Shared1\WGroups\Network\Orders.xlsRather than describe the location of a file or directory by drive letter, the Network Group will typically communicate a UNC path to describe the actual location of a file or directory. Windows drive letter mappings are arbitrary, whereas a UNC path is specific and applies to all operating systems.
Note: The UNC method started with the UNIX operating system. UNIX uses the forward-slash character as a path separator. Many network services (ex. FTP) have their origins in the UNIX operating system, so they use forward-slashes instead of the backslashes that DOS/Windows uses. It is important to recognize this distinction when using these services.
-
Jun 26th, 2005, 08:13 PM
#15
Re: Obtaining DLL files
Krenshau,
You have a complete script. Now you have to test it on the target OS. Preferrably a clean system.
-
Jun 26th, 2005, 09:38 PM
#16
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
I have tested it on several systems now.
When I tried it on a windows 98 system it said that it couldn't register msjint.dll. Since I am running the auto os update in my setup do I still need to register it manually, as it is now? It gave me that error before it ran the auto update.
The other issue I had was when I ran it on a friends windows XP on uninstall it asked if I wanted to delete the shared file DCOM98.exe. I can just make that delete on uninstall with a flag right?
I also read the page about the auto update again and it said that the auto update includes all of the VB files, do I need to register them seperatly, like my script is doing now?
One last question, I have been installing the cab file from the P&D setup. Since I am pulling in the files manually thru inno do I need to take the cab file with me, or can I just leave that out?
BTW, thank you for looking at the script. it is a big help and I am very grateful.
Last edited by Krenshau; Jun 26th, 2005 at 09:44 PM.
-
Jun 26th, 2005, 09:46 PM
#17
Re: Obtaining DLL files
Krenshau,
Your script should always contain the VB Runtime files. This will insure that they are installed no matter what. The Auto OS Updater has Dcom98 in it also so you do not really need to have that in your script.
What is msjint.dll used for. It is probably in one of the SPs that gets installed. What file is this a dependency for. (********** gives you a list of this in the debug log).
-
Jun 26th, 2005, 09:57 PM
#18
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
Sorry, it is msjint35.dll, it is a driver for microsoft jet. Which I thought I saw the auto OS Updater had the jet database engine drivers. This one is 3.5.
With the DCOM98.exe I just decided to make it neveruninstall.
-
Jun 26th, 2005, 10:08 PM
#19
Re: Obtaining DLL files
Krenshau,
Well, that file is installed with the MDAC 2.0. So you do not need to include it if you are installing the MDAC.
-
Jun 26th, 2005, 11:55 PM
#20
Thread Starter
Hyperactive Member
Re: Obtaining DLL files
Ok, I went back thru and looked at each dll and ocx and looked at what the auto updater installs and what is in the MDAC 2.0 and took out all of the duplicates, expect for the VB 6 files. I think it should work good now.
Thank you for your help.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|