Kelsenellenelvian

place the msi in the c:\ drive like c:\6.6.5.msi open a run box from the start menu or by presing winkey + r type in cmd then in the command box that pops up type in c:\6.6.5.msi /?

orca (Its an .msi properties editor) using the /? switch

Actually I think we are thinking 2 different things. The bug only appears when upgrading a system that already running to SP3. A SP3 integrated disk does not have this error.

As long as he didn't add any preregged apps or any cracks to it then it isn't warez. I did try driverpacks again and it DOES not use a OEM folder it uses the standard $oem$ folder style. I have no clue what or how he did it but would like to find out...

I've seen it... But the patch works fine. http://www.softwarepatch.com/windows/windo...0x0000007E.html

That power supply uses a way different input voltage than standard also... Not quite enough to cause brownouts when you power up but it will still do the job and is DAMNED sexy! http://www.newegg.com/Product/Product.aspx...N82E16817814011

The EULA was put there for your protection more than Nuhi's. Think like this: You make a nLited setup for your company, get it all nice and neat, and install it on 100-1000 pc's. All of a sudden your network goes down because you removed, modified something stupid like remote registry. Now you company is screwed because EVERYTHING has to go down while a fresh OS is installed, updated and the rest of the programs added. Thousands of dollars down the drain and hundreds of man hours wasted while everyone waits for their pc's to come back online. Now you boss is pi**ed because you used an app you can't provide support for and your out of a job and possibly in court, while they are looking at sue-ing Nuhi too. Besides while the app is not illegal some of what it does is illegal as it COMPLETLY breaks the MS eula! These things are stuff a personal user can get away with but MS will notice and sue YOUR company if all of a sudden the get 1000 or more error reports, service calls because you f'ed up the windows build you had the balls to use at work. You are just bein lazy, anything nLite can do you can easily do by hand, Then you can fully support your work and decision to your bosses...

Here is a quick start package that will set your windows disk up to use WPI with runonceex. This is for use with all versions of Windows 2000, XP and 2003! To make use of this archive all you need to do is unRAR it and place the %oem% folder beside the I386 and WPI folders. $OEM$ Folder (The forum is messing up this link so copy www.wpiw.net/downloads/$oem$.rar ) Contents of the %OEM% archive: cmdlines.txt RunWPI.exe (Sets the runonceex and MCE themeing entries used for WPI)

Did you just let it sit when the light went off for a sec? Or did you panic and try to reset it immediately? Yes you have killed your motherboard Basically it's brain dead, During the process of flashing the bios the old one is deleted and the new one is programed in. The process got interrupted (Might be from any reason, power fluctuations, user interruption, wrong bios) but it has no brain anymore therefore it's dead Jim. Don't panic quite yet though. Is it under warranty? Call and see if your warranty covers this. Usually the company can recover it for you. REMOVE your harddrive BEFORE you send it in though... Most of the time you'll find that when it comes back all your info is gone. Also try taking the battery out and unplug it then leave it over night (If its not under warranty then find and remove the CMOS battery too) and hope the darned thing will reset itself. I've seen it happen. Remeber when flashing BIOS on a laptop make sure your battery is charged and the laptop is plugged in and DON'T touch it untill it says it is done. Disable your screensaver too. When you call Compaq just tell them it went dead and you have no clue why...

Hey Geek, Hirens is warez m8..

September 18, 2007 is when it was released thats 10 months... NOT 2 years.

Kinda late answer but I put them in the system32\shellext directory.

This has become a known conflict with UAC,

OK here goes: No need to start from CD\DVD at all. (I keep mine on a seperate parttion and run it from there ALL the time) WPI only really checks for a cd\dvd drive to disable\enable the extra buttons (Options, Config and About WPI) So your good to go.

Hell I dunno. I have never seen a disk like that. Must be because it is a warez disk and they musta used some odd style of formatting. It shouldn't cause any conflicts but seeing as how you didn't even build the disk in question I don't see how I can help you much further as MSFN has very strict policies about the use of and assisting with warez... I can't even "politely" ignore the fact it is warez.

Wait are you saying there is an OEM folder without the $$??? If there is it is trash. The folder HAS to be named $OEM$ for it to work...

OK Now does your disk layout look like the included picture? What are the other files in the $oem$ folder used for? Do you actually need them?

Copy the .exe or .inf file that is inside the downloaded $oem$ folder and add it to cmdlines.txt. Just like so "RunWPI_Zune.exe".

Downloading and redistributing any Microsoft programs\apps online is illegal unless you are getting them straight from the distributer. So in effect downloading any os or oem disk is illegal especially from torrents and for buisiness purposes. However on the good side there is another way AFAIK. Look here = http://www.msfn.org/board/Multi-Manufactur...ion-t71016.html

eset smart security says its good.

What OS??

Well see thats the thing if you add it to the reg and it's put in there then you have to remove it at sometime. Open wpi.hta with notepad. You will see where we have made a section that adds some regentries. You can add it there.

Actually yes most installer can be called with switches to launch and run them silently.

Besides being disabled WPI is actually the only real important thing I do (Besides being a husband and a father) Yeah its kinda over the top. Your just jealous

Sorry I got mad.. Yeah its not visual basic its just c++..