Set Key=HKLM\*RunOnceEx

[Corn~Julio]

If this has been posted before my appologies, if so if anyone could point me towards the thread it would be a big help

The only change I made last night was adding users in my user.cmd & an entry in my user.reg then to test this out I did my unattended

When the Install got to T12 & ran my 1st_boot.cmd to insert lines in runonce I get this

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

Out Of Environment Space

Then all my Reg Add lines fail

I removed the changes tried it again and got the same error

I let the unattended finish & to try to figure out what happened I ran regedit and runonce is there I also checked all permissions and they are as they should be

The I ran the .cmd from the a cmd window and got the same error on the 3rd run of the .cmd it ran fine

I have run the unatteded 3 times & then tried it from a cmd window with the same results

Folks I am completely lost..... any ideas

[cluberti]

The problem is likely that you've actually run out of environment space in the DOS environment window. The default environment space in a command session is, I believe, 1024k (1MB) during Windows setup. If you are adding a lot of users, or calling external application installs, you can actually run out of environment space (remember, every application called by the command window runs as it's child, and shares it's environment space during Windows install). If you've rolled back your changes and the issue persists, you may want to create a new .cmd file and copy and paste the data from the old into the new and try again (I've seen wierder things before during unattend, and new files have fixed similar issues after rolling changes back).

[Corn~Julio]

I didn't know that was basically the same as the older dos error Not Enough Memory, I only ever ran into that when I created a self extracting file that was to big so I would cut down the size

Since all my bat files were pretty small with out a large amount of requested functions I never had this problem and honestly it never occured to me a bat could max the free mem...

I've been at this for many years but I work more on cause and effect rather than actual understanding

I know I'm rambling... so more to the point what you said made sense in my cmdlines.txt it ran user.cmd in this I used the call function for 1st_boot.cmd and called on another cmd from there not realizing adding the additional functions and then 3 concurrent cmd's was pushing the limitations

I made changes to the cmdlines to run each cmd individually so on each exit it will hopefully give a partial reset on the free mem so I might be able to add addtional functions to 1 or more of my cmd's later on

I re-inserted my previous changes and I've run the unattended twice without any hitch

Many many thanks for your reply cluberti

[cluberti]

Great! You learn something new every day .