IE Script debugging and WPI

[Ctwizzy]

I asked this in the unattened part of the forum, though no one is answering and it pertains more to WPI, and I would like this resolved asap as im almost done my cd.

I have IE script debugging in my Tweaks file, which is run from commandlines.txt (t-12) and WPI is t-13 I thought, so my tweak should be applied. But its not (at least as far as I can tell)

;-----  Disabled IE script debugger
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
"Disable Script Debugger"="yes"

So either its not working or my WPI installs happen before the tweaks are applied. If the latter I need to know how to apply this before hand. A cheap trick I could do is make a reg file be the first thing my WPI does which does the IE debug, but there has to be an easier way.

Anyone know?

Thanks

[Kelsenellenelvian]

In the common folder of wpi is a reg file that wpi calls during wpi.cmd just add this in there.

[Ctwizzy]

woot thanks!!

Maybe this should be added in as default, and then turned back on when WPI is finished. Unless im the only one with the problem.

[Kelsenellenelvian]

I have never had the problem.

As far as I know the problem has not been reported by others.

[Ctwizzy]

Ok so even after putting that reg file in the WPI reg file im still getting the error.

I get this randomly throughout the WPI installations. I know its the WPI as the msgBox says WPI at the title bar and then says IE script is running slow, do you want to abort? YES, NO

I cant ever leave it unatteneded as once this screen pops-up It no longer works.

[Kelsenellenelvian]

Ummm are you calling WPI.cmd??

This issue was fixed with a release a loooong time ago.

When do you run WPI??

[Ctwizzy]

No I do it like this: (from website)

In winnt.sif:

[GuiRunOnce]
%systemdrive%\install\InstallWPI.cmd
;Renames Admin acct, and disables guest
%systemdrive%\install\admin.cmd
;cleansup the crap
%systemdrive%\install\cleanup.cmd

InstallWPI.cmd

@ECHO OFF
cmdow @ /HID
ECHO.
ECHO Calling WPI
ECHO.
start /wait %systemdrive%\install\WPI\WPI.HTA
exit

Should I be calling WPI.cmd?

I heard from asta you can call WPI from RunOnceEx instead and u chose ur apps at the beggining instead of after XP has installed. As I dont know anything about RunOnceEx I havnt attempted this yet.

On a side note should I be upgrading to a newer WPI?

[Kelsenellenelvian]

Yeah probably should upgrade.

Lots of people call it from guirunonce through winnt.sif.

Call it like this=

[GuiRunOnce]

%systemdrive%\install\wpi\wpi.cmd

and it will run after first logon of windows.

Apparently you really need the regtweaks included with wpi.cmd so either call it through .cmd or put the regtweak into wpi and have it done first.

[Ctwizzy]

How do I upgrade while still keeping my uA cd working?

Do you advise running it through GuiRunOnce or RunOnceEx?

[Kelsenellenelvian]

Just add the following to your wpi.cmd -

regedit /s "%systemdrive%\install\wpi\common\wpi.reg"

This should fix all probs.

[Ctwizzy]

kelsenellenelvian, thanks for your help, really appreciate it.

So do you recommend RunOnceEx vs GuiRunOnce? or does it really not matter?

Also, how do I upgrade my WPI? I cant see a upgrade thread anywhere, and Im not sure which files I need to move to keep my settings the same.

Thanks again.

[Kelsenellenelvian]

I reccomend guirunonce

Depends on wich modifications you have done and which theme you use.

The main files you need to change are in the wpi scripts folder, take config.js and useroptions.js also take your wpi.cmd file from the old wpi and transfer them to the new wpi and it really is as simple as all that.