mhuwaaa problem is not entirely fixed, the above is not correct... it is partially fixed when i use GuiRunOnce but then the desktop.ini issue arises again (not in the startup folder (you fixed that) but in startmenu and some other folders). i now have completely rewritten the winnt.sif and precopy.cmd and made some batchfiles because i cannot wait any longer i need a working install cd... you can lock this topic if nobody else has this problem if you like.

I'd like to get more details about that desktop.ini issue you describe. It's not much work to add more work-arounds if necessary.

This fixed my problem.

What exactly? Removing that whitespace? That doesn't make sense, you can indent any entry in a .ini format file as far as you want, any ini parser will ignore the whitespace...

Friends4U wrote:

I do not know, driverpacks aranges that for me...

But i choose RunOnceEx at 999 but i will choose RunOnce for the test i am doing now.

And how do you install your programs? Runonce? WPi?.......

No i don't use WPI... just the RunOnce the base creates in the winnt.sif but he puts the tag in there with a tab (white space) before it.... i manually removed the space and testing again now.

It does work for everybody else, so it must be something specific to your system

LOL i think you tought that before But ok, i did not report this as a bug either... just trying to solve my problem.

I do not know, driverpacks aranges that for me...

But i choose RunOnceEx at 999 but i will choose RunOnce for the test i am doing now.

And how do you install your programs? Runonce? WPi?.......

But i choose RunOnceEx at 999 but i will choose RunOnce for the test i am doing now.

Could you post the exact routine you use to create the CD/DVD so the guru's can analyze it.

i.e. Do you integrate Ryan VM etc. What versions ????

When integrating, this time gladly no errors but a new problem arises... the Finisher is NOT starting after the Windows Install... it just starts windows.