Setup.dll, what does it do

PaulFix · #1 (**permalink**) 08-03-2007, 01:09 PM

I am trying to make an oem of SPB traveler and cannot figure out what setup.dll is doing. Anyone tell me how to do it please.

Thx

**luv2chill** · #2 (**permalink**) 08-03-2007, 02:43 PM

You need to use a registry editor to dump the entire registry to a text file. Then install the cab quickly, then immediately dump the entire registry again to a separate text file.

Then bring those files over to the PC and use WinDiff (or equivalent compare app) to find the differences between the two files. Some of the entries you will want to ignore, the rest are the changes that the cab and/or its setup.dll made.

It takes a lot of trial and error... that's why we hate setup.dlls so much

PaulFix · #3 (**permalink**) 08-03-2007, 03:14 PM

Thx, I will have at it

PaulFix · #4 (**permalink**) 08-03-2007, 03:17 PM

What is the difference between the red and yellow sections in windiff

**luv2chill** · #5 (**permalink**) 08-03-2007, 03:21 PM

Red usually means something is in the right side file only
Yellow means in the left file only, but also check the little symbols on each line that will tell you if the line is new or just moved.

PaulFix · #6 (**permalink**) 08-03-2007, 03:23 PM

Thx

**nuguy** · #7 (**permalink**) 08-05-2007, 01:05 PM

On a related note:

I have several progs installed on my sd card, in most of the install directories there is a setup.dll file.

They are mostly all the same size and date, I keep thinking I could just delete them - especially for progs I am not likely to uninstall.

Any words of advice be ore I do?

**luv2chill** · #8 (**permalink**) 08-05-2007, 01:33 PM

Well you have to be careful about that. What you should do is check the original cab installation file for that app to see if it has a setup.dll in it with that name. If so, yes you can probably delete it from the program folder. But some apps might actually use a dll called setup.dll (with no relation to the type of setup.dll we're talking about here) and therefore deleting it might cause problems for the app.

Best thing would be to just rename or move the dll first and make sure the app still works fine--if so then it's probably safe to delete the dll.