PDA

Click to See Complete Forum and Search --> : problem


thedee23
Sep 27th, 2000, 11:06 PM
I have written a program in VB 6 on a Windows 95 machine. I have SP4 installed also.

A user of mine has NT 4.0 and he gets this error when he tries and run my program "Run Time error 53. File not found rasapi32.dll". He ran my setup program that I created using the package and deployment wizard.

In my program I have a couple function calls that use rasapi32.dll. What my question is - Shouldn't the package and deployment wizard detect that I am using that and add it to the list of file to distribute or do I need to add this file manually? When ever you do function call to dll's do you need to add these files manually when going through the package and deployment wizard??

thanks

amitabh
Sep 28th, 2000, 04:53 AM
Why don't you specifically include that file in the P&D Wizard. I generally do a manual check of files required before creating a setup package.

[Edited by amitabh on 09-28-2000 at 05:56 AM]

thedee23
Sep 28th, 2000, 08:05 AM
Does win NT and Windows 95, 98 etc.. use the same dlls. If I put rasapi32.dll in my program package and when they install it on their machine, will that effect their machine at all if the rasapi32.dll are not the same?

hitcgar
Sep 28th, 2000, 03:16 PM
1. Ye have to watch dll files between platforms they're not always the same.

2. The directory for NT dll files is "\\winnt\system32" whereas on win9x it's usually "\\windows\system"

So watch out for the differences.

Circumvent these diffs by detecting which system the install is executing on or build 2 different installs.

;)

amitabh
Sep 29th, 2000, 04:09 AM
I don't think you need to create two different setups for 98/95 and NT. If you specify system folder, the setup utility automatically detects the right folder.

shtirliz
Oct 6th, 2000, 12:56 PM
You have to watch for DLLs that are being distrubited with your package. May be you should not include rasapi32.dll in the package, but check if RAS is installed on the target system. Rasapi32.dll relies on the presense of of other DLLs installed when RAS is installed. Use Dependancy Walker to verify.