Why is this file so big? XMPlay is only 300kB and this is over 1M? And why do you hide it in a Windows Installation wrapper? Why not leave it open in a .zip file like XMPlay for everybody to see.
59 People have been to this web site. My advice: STAY AWAY FROM THIS APPLICATION. Something is fishy when file to set Options is nearly 4X the size of the file you are setting options on. Like a key logger hidden inside? Or maybe a virus? Anyway, something is just not Kosher.
It's over 1M because it contians the VB runtimes and a dll to make registry access easier in VB. I included the runtimes as not everyone will have them. Also, I didn't pack the EXE to make it smaller (which is what's done with XMPlay). It's in a windows installer package as that way there's only one file to distribute and it's easier to install. It's not hidden - there are plenty of free tools around to let you see the files inside it, same as with a zip file. The .MSI file's zipped because geocites won't let me upload a .MSI file. There's no key logger, virus, spyware, adware or any malware inside it.
Complete contents of the MSI file:
# regobj.dll (some classes to make registry access easy in VB)
# scrrun.dll (MS Scriptiing Runtime - used for some file access)
# COMCAT.MSM (merge module - something to do with COM)
# MSVBVM60.MSM (merge module - VB runtimes)
# MSVCRT.MSM (merge module - VC runtimes (not sure why that's included))
# OLEAUT32.MSM (merge module - OLE automation)
It does seem a bit big, looking at it (didn't notice as I'm on broadband). I just built the package in Visual InterDev and let it decide what files to include. The MSI file comes to just 1.19 MB, which I think is better than by using the Package & Deploy wizard. I'll look into trimming the size down a bit.