[ykchanaed]

Lately , I think untill these few months , I observed that the reg , cmd files in HFGUIRunOnce folder were not implmented in the resulting OSes!

Now I am using beta J v10 and testing the OS with VMware Workstation 8.
The resulting SOURCESS folder did have the HFSLPGUI.inf, HFSLPGUI.cmd and the various compressed HFGUI# files.

Does anyone has that problem?

I am still working on it and testing in various senarios!

This post has been edited by ykchanaed: 18 October 2012 - 08:06 AM

[tomasz86]

From HFSLIP:

Quote

HFGUIRUNONCE - MSI files and silent EXEs to be installed at 1st GUI logon

and

Quote

HFSVCPACK - REG files, INF files and CMD files (installed at T-13)

[Geej]

Actually HFGUIRunOnce can also take .cmd .reg & .inf files

[ykchanaed]

I have been using HFSLIP for more than 4 years , in English XP and Chinese XP.

I deliberately modified the HFSLPGUI.cmd in the SOURCESS folder so that it would not hide the console window and pause during the execution. And then made the ISO and tested it in VMware.
The resulting OS did not show up any HFSLPGUI.cmd window during the First GUI.

As far as I know , HFSLIP add the command in the HKLM\...\RunOnce registry key.

At the same time , one Addon I personally made, that used the HKLM\..RunOnce to change the resolution during GUI also failed. It WORKED previously!!!! Untill around 2 months ago when I tried to make the unattended XP again.
...... So far , I still can not figure out the problem.
But when I changed the key to HKLM\...Run, it worked.

Personally I suspect some new hotfixes especially the ActiveX ones, may be the culprit because I noticed that the HFSLPGUI.INF manipulated the "ActiveX Compatibility" key. JUST a wild guess!!!

This post has been edited by ykchanaed: 19 October 2012 - 04:19 AM

[tomasz86]

You're right about HFGUIRunOnce. It supports MSI / EXE / CMD / REG / INF:

Spoiler

FOR /F %%I IN ('DIR/B HFGUIRUNONCE') DO SET GUICNT=1
IF DEFINED GUICNT (
	TITLE %T1% - Processing GUIRunOnce apps&ECHO.&ECHO Processing GUIRunOnce apps...
	FOR /F "DELIMS=" %%I IN ('DIR/B/ON HFGUIRUNONCE') DO (
		IF /I "%%~xI"==".MSI" (
			ECHO %%I&ECHO>>WORK\HFSLPGUI.TXT START/WAIT MSIEXEC /i %%I /qn /norestart ALLUSERS=1
			ECHO>>SOURCESS\I386\TXTSETUP.SIF HFGUI!GUICNT!.MSI = 1,,,,,,,998,0,0,"%%I"&ECHO>>SOURCESS\I386\DOSNET.INF d1,HFGUI!GUICNT!.MSI
			COPY "HFGUIRUNONCE\%%I" WORK\I386E\HFGUI!GUICNT!.MSI >NUL
		) ELSE IF /I "%%~xI"==".EXE" (
			ECHO %%I&ECHO>>WORK\HFSLPGUI.TXT START/WAIT %%I
			ECHO>>SOURCESS\I386\TXTSETUP.SIF HFGUI!GUICNT!.EXE = 1,,,,,,,998,0,0,"%%I"&ECHO>>SOURCESS\I386\DOSNET.INF d1,HFGUI!GUICNT!.EXE
			COPY "HFGUIRUNONCE\%%I" SOURCESS\I386\HFGUI!GUICNT!.EXE >NUL
		) ELSE IF /I "%%~xI"==".CMD" (
			ECHO %%I&ECHO>>WORK\HFSLPGUI.TXT START/WAIT CALL "%%I"
			ECHO>>SOURCESS\I386\TXTSETUP.SIF HFGUI!GUICNT!.CMD = 1,,,,,,,998,0,0,"%%I"&ECHO>>SOURCESS\I386\DOSNET.INF d1,HFGUI!GUICNT!.CMD
			COPY "HFGUIRUNONCE\%%I" WORK\I386E\HFGUI!GUICNT!.CMD >NUL
		) ELSE IF /I "%%~xI"==".REG" (
			ECHO %%I&ECHO>>WORK\HFSLPGUI.TXT START/WAIT REGEDIT /S "%%I"
			ECHO>>SOURCESS\I386\TXTSETUP.SIF HFGUI!GUICNT!.REG = 1,,,,,,,998,0,0,"%%I"&ECHO>>SOURCESS\I386\DOSNET.INF d1,HFGUI!GUICNT!.REG
			COPY "HFGUIRUNONCE\%%I" WORK\I386E\HFGUI!GUICNT!.REG >NUL
		) ELSE IF /I "%%~xI"==".INF" (
			ECHO %%I&ECHO>>WORK\HFSLPGUI.TXT START/WAIT rundll32.exe advpack.dll,LaunchINFSection "%%I",DefaultInstall
			ECHO>>SOURCESS\I386\TXTSETUP.SIF HFGUI!GUICNT!.INF = 1,,,,,,,998,0,0,"%%I"&ECHO>>SOURCESS\I386\DOSNET.INF d1,HFGUI!GUICNT!.INF
			COPY "HFGUIRUNONCE\%%I" WORK\I386E\HFGUI!GUICNT!.INF >NUL
		)
		SET /A GUICNT=!GUICNT!+1
	)
)

Have you tried to add your custom scripts without anything else? Don't slipstream any updates, etc. Just add your scripts to a clean XP SP3 source, run HFSLIP and then try to install it.

[ykchanaed]

I have made various tests.

In XP system , NOT during Setup of the XP OS:
1. If using INF to add command to the HKLM\...\RunOnce key in XP ,using Default Install section, the command wound execute at once , not untill the next reboot!

2. If using cmd to reg add HKLM\...\RunOnce , the command would execute in the next reboot!

Do above make any clues?

[ykchanaed]

It also happened when using nLite.

I used Onepiece update pack plus my own HKLM\..\RunOnce Addon using nlIte.
The HKLM\..\RunOnce failed to run.

[tomasz86]

If the same problem happens with nLite then it's not HFSLIP to cause this issue, is it?

Could you show / upload an example of your script so that we could test it too?

[ykchanaed]

Let me explained my addon:
A cmd script to add a command to HKLM\...\RunOnce during SVCPACK stage(SVCPACK script). The command is an cmd script to change resolution to 800x640 (ChangeRes script).
To test it , I made the scripts all visible and pause.

Test 1:
All up-to-date hotfixes,
some essential Addonsin HFAAO folder,
AND my personal addon mentioned above.
No files in HFGUIRUNONCE folder.

Result 1:
The script during SVCPACK showed up and successful.
BUT during 1st GUI the change , the change res script did not show up.!


Test 2:
Without any hotfixes in HF folder.
The same essential Addons in HFAAO folder,
AND the same my personal addon
No files in HFGUIRUNONCE folder.

Result 2:
The script during SVCPACK showed up and successful.
The change res script showed up and worked!

My home-made Addon attached. It's purpose is to just change the resoltion to 800x640 at 1st logon so that the annoying warning would not appear because I did Virtual testing very often.

Attached File(s)

•  QResGUI_Addon_WinDir.7z (4.69K)
  Number of downloads: 7

This post has been edited by ykchanaed: 19 October 2012 - 07:39 AM

[ykchanaed]

Test 3:
All up-to-date hotfixes EXCEPT WindowsXP-KB2736233-x86-XXX.exe,
Same esstential Addons,
Same my personal addon.
NO files in HFGUIRUNONCE folder.

Result 3:
My personal change res script showed up during 1st GUI logon and worked!!!


So the preliminary conclusion would be :

Quote

The culprit is
WindowsXP-KB2736233-x86-XXX.exe

Maybe I have to make a KB2736233 switchless installer to tackle this problem!

This post has been edited by ykchanaed: 19 October 2012 - 08:17 AM

[ykchanaed]

Test 4:
Essentially same as Test 3 with minor changes:
a. WindowsXP-KB2618451-x86-XXX.exe in HF folder (the one before the culprit KB2736233)
ie. ALL hotfixes except KB2736233 but with the previous ActiceX update
b. Now with with reg files in HFGUIRUNONCE Folder

Result 4:
My personal addon run and successful.
The reg files in the HFGUIRUNONCE folder were incoprated.

This post has been edited by ykchanaed: 20 October 2012 - 08:25 AM

[ykchanaed]

Test 5:
All up-to-date hotfixes EXCEPT WindowsXP-KB2736233-x86-XXX.exe,
BUT put it (KB2736233) in HFSVCPACK _SW1 folder,
Same essential addons,
Same my personal addon,
No files in HFGUIRUNONCE folder.

Result 5:
Personal addon worked without any problem.

Preliminary conculsion:

Quote

Putting KB2736233 in HFSVCPACK_SW1 did not interfere HKLM\...\RunOnce behaviour during XP setup!

No need to make a separate KB2736233 installer!

This post has been edited by ykchanaed: 21 October 2012 - 03:31 AM

[ykchanaed]

After numerous, numerous and numerous tests......

I found out that the Sysinternals Suite Installer was the culprit!!!

The Sysinternals Suite Installer was built with SSIBuild (Sysinternals Suite Installer Builder)Version: 2.7

The installer so created would delete the entries in the HKLM\...\RunOnce key.

I noticed it when I used it with other addons in HFSLIP or nLite to make XP.

The Sysinternals Installer was run in SVCPACK stage.
And when it was run AFTER other addons that add entries in HKLM\..\RunOnce key, then these addons would not work in next reboot!!
When it was run before other addons , the other addons worked OK.

I have tested it in the virtual XP. Immediately after the Sysinternals Installer run , the entry in HKLM\..\RunOnce was gone!

I have extracted the SysPath script inside the installer and test it .
It had no effect on the HKLM\..\RunOnce key !!!!

So

CASE CLOSED

This post has been edited by ykchanaed: 20 November 2012 - 01:56 AM

[ykchanaed]

I finally understand the mechanism behind this:

The keys in HKLM\..\RunOnce are actually not deleted BUT actually already run.
The commands in the RunOnce key are being run DURING inf setup, and Sysinternals Suite uses inf setup.
Only that the commands are run in SVCPACK stage and hence have no effect.