1.5.0.5855: Jobs in Post-Setup change sort direction when creating ISO?

D

DenalB

New Member
I'm using v1.5.0.5855 now and when creating new jobs in Post-Setup they are changed in the sort direction when creating the ISO file. Before this version everything works fine.
  1. Create jobs in Post-Setup section above the placeholder line.
  2. Create ISO (Windows Server 2016).
  3. Mount ISO and install OS.
  4. No job is executed because the last job is for deleting all setup files. But this job is now the first job.
  5. Load the ISO file in NTLite and see that sort direction is changed.
  6. Correct the sort direction.
  7. Create ISO again.
  8. Mount ISO file and install OS. Now jobs are executed correctly.
I could reproduce the issue two times. May be I'm not the only one with this problem?
 
DenalB said:
I'm using v1.5.0.5855 now and when creating new jobs in Post-Setup they are changed in the sort direction when creating the ISO file. Before this version everything works fine.

I could reproduce the issue two times. May be I'm not the only one with this problem?
Click to expand...

I have seen that too, have you had any problem?
I know, that could be a problem if a program's update moves upwards before the program setup but i don't install any program (yet) with Windows setup.
 
Today I tried it again and the problem still exists. But the problem only occurs if the image is build for the first time. If mounting the image for the second time, sort order is changed but stays in that way. If I build the image again sort order does not change.

May be it helps finding a solution?
 
@DenalB,

thanks for the report, however I cannot replicate the issue.

If I add just a command "test" and apply, this is in .\sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd

Code: 
@echo off
test
del /q /f "%0"

If you see different, please attach a preset, or the existing SetupComplete.cmd before NTLite, maybe that's where the issue is.

Thanks.
 
nuhi said:
thanks for the report, however I cannot replicate the issue.

If I add just a command "test" and apply, this is in .\sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd
Click to expand...

Try adding 5 or more commands with different names each and you will see (i have 14 commands).
 
@nuhi
You have to add more "post jobs" than only 1 because with only 1 command you are not able to see the different sorting. ;)
 
OK, will retry these days, added to priorities.
I thought from the first post:
"No job is executed because the last job is for deleting all setup files. But this job is now the first job."
I didn't realize that more commands are necessary to provoke that.

Thanks for the feedback.
 
nuhi said:
"No job is executed because the last job is for deleting all setup files. But this job is now the first job."
Click to expand...
Oh sorry... I mean that I have 8 commands as post jobs. The last command is for deleting the complete folder on drive c after deployment is done. But when creating the iso for the first time this deletion job jumps to position 1 and so the folder is deleted before all post jobs are done. ;)
 
DenalB said:
But when creating the iso for the first time this deletion job jumps to position 1 and so the folder is deleted before all post jobs are done. ;)
Click to expand...
In my experience, the deletion command didn't move to the first place, only the first or second command exchange it's place with the next (a del command goes first, instead of rd).
 
@DenalB, I cannot replicate this. However, can you please try the newly released build 6025, I have added a potential fix.

Thanks.

edit: Next version should be much better in this, I finally got my hands on a file demonstrating the issue.
 
Last edited:
You must log in or register to reply here.
Back
Top