DookieToo

I'm not sure what the point would be, unless it's to bypass the setup.exe used by the program.msi. Even then, most of those you can just write a setup.ini to designate certain variables. Any stand-alone .msi starts the Installer service when you click it. I am very curious as to the application of this project. Not being skeptical by any means, just genuinely intrigued. By the way, UniExtractor uses E_WISE to decompile the .msi, you can find the source code (Pascal) here. Also, you've likely already played with them, but here are the parameters that apply to msiexec.exe: Windows ® Installer. V 3.01.4000.1823 msiexec /Option <Required Parameter> [Optional Parameter] Install Options </package | /i> <Product.msi> Installs or configures a product /a <Product.msi> Administrative install - Installs a product on the netwo /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID Advertises a product - m to all users, u to current use </uninstall | /x> <Product.msi | ProductCode> Uninstalls the product Display Options /quiet Quiet mode, no user interaction /passive Unattended mode - progress bar only /q[n|b|r|f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI (default) /help Help information Restart Options /norestart Do not restart after the installation is complete /promptrestart Prompts the user for restart if necessary /forcerestart Always restart the computer after installation Logging Options /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile> i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options /log <LogFile> Equivalent of /l* <LogFile> Update Options /update <Update1.msp>[;Update2.msp] Applies update(s) /uninstall <PatchCodeGuid>[;Update2.msp] /package <Produ Remove update(s) for a product Repair Options /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode> Repairs a product p - only if file is missing o - if file is missing or an older version is installed (def e - if file is missing or an equal or older version is inst d - if file is missing or a different version is installed c - if file is missing or checksum does not match the a - forces all files to be reinstalled u - all required user-specific registry entries (default) m - all required computer-specific registry entries (def s - all existing shortcuts (default) v - runs from source and recaches local package Setting Public Properties [PROPERTY=PropertyValue] Consult the Windows ® Installer SDK for additional documentation on the command line syntax. Copyright © Microsoft Corporation. All rights reserved. Portions of this software are based in part on the work of the Independent JPEG Group.

Sounds like a scripting error, as in it's not running correctly. Are you restricting Javascript?

Straight from the horse's a**. I mean mouth.

You've probably disabled Javascript or redirecting. I use Firefox instead of IE, but I know if you go to internet options in Control Panel, you can reset all of these settings & try it. It's possible a 3rd party program could affect it, too. Check your firewall, spyware blocker etc.

This guy managed to extract them on the fly, haven't really dug into the coding or anything to find out how, but I've used it a few times, and it seems to work with Msi's that require triggers. It just extracts the Msi's content to a designated folder.

I ran into this problem once, unfortunately was never able to find a fix. If it's the same problem, the BIOS itself is corrupted. You could try flashing it if you can get BIOS upgrades for it. I couldn't on the old laptop I was trying to repair, it was WAY outdated. It would however boot from a linux disk (I used Knoppix) no problem, and I retrieved the person's data from it at least. The only other option I could find was to use an EEPROM, which was hardly worth it on that old POS. Hopefully it's not that drastic, but it sounds very similar. You might also try an app that will wipe out & restore the MFT (Master File Table), but only if nothing else works. Also try Googling MSDos Recovery Console. It may save you without too much grief. You should be able to access it if you can get as far as reformatting from a boot disk.

How Refreshing... To find a forum that has so few rude posts while having a seemingly endless amount of knowledge on Bill's Evil Empire. (Don't take that or my avatar the wrong way, I'm not militant anti-Windows or anything) I must say that a great bunch of minds have converged here, resulting in me learning more about the guts of the OS in a few days than I would have in months tediously browsing MSDN. Hopefully I'll be able to chip in & help from time to time. Thanks to all involved for making this great forum what it is, now excuse me while I read up on hacking my ntoskrnl...

Hello all. ADG, I think this is the file you start with: winntbbu.dll Haven't played with it yet, but I extracted all the resources & it contains the Bmp's and such. I've seen a tut on how to add progs, but I can't remember where... Edit: How silly of me. It was here: http://www.msfn.org/board/index.php?showforum=92