I can't even get my ultraiso to create it... I can create the iso but when I try to make it bootable it errors even if I run as admin
Your iso is already bootable. Either open up unmodified iso and add $oem$ folder delete ei.cfg file and add install.wim then save or burn iso file.
I have it extracted to a folder since i was adding updates. I just made the iso using ntlite again...
So I tried an UNTOUCHED iso, just added the oem and make the file with ntlite and the background installed fine... it only errors after integrating the updates... not error but (black background issue). I wonder which update is causing it. This is true for my Windows 7 and Windows 8.1 Its not a huge deal but I am sure everyone would like to get to the bottom of it... Maybe ill try another app to integrate the updates.
Integrate updates with Dism instead of third party apps. The fact that some integrate updates into custom iso's and the project works tells me its the process of creating the iso that breaks it (whether it be the integration of updates or the process of building the iso itself). I will repeat again, use Dism. Either way, this isn't a problem with the project but the integration process of building a custom iso therefore it is a third party problem not related to the project.
NTlite no nuhi, has always done things his way even used to tag files even since vlite. Been at this for a while now used to be slight competition between him and my M8 maxXPsoft when we worked on UnattendXP and Se7en_UA especially at the start when vista came out and we would be testing DISM on maxXPsoft forum but we would post on MSFN next thing new features would be added to vlite Anyway going of the subject I have already stated Simplix Pack works MR-X has since confirmed this and it does use DISM. P.S. no need nowadays to use nlite to cut down OS system hard drives e.t.c are cheaper plus old problem was when SP1 came out people who had used ntlite could not update due to the fact trying to slim down the system core files were removed
That is good to know plus that is why it works (DISM). lol Thanks for sharing that info with all of us urie. I don't do slipstreaming anymore so I really don't know all the third party apps out there. If the subject comes up in this thread again, I will let the experts like yourself and Mr.X handle it. I know my limitations.
Thank you so much!!!! My 7 COA sticker was on the bottom of laptop, and basically melted. Not knowing that OEMs use generic SLP keys, I used a keyfinder app to back up before formatting, and thought I was screwed, since I formatted my Lenovo recovery partition ages ago! If I had to call Lenovo for a repair disc, I might not have gotten one (they might have said "lol no recovery partition and melted COA? Nope."), but I would've had to pay for the call since my Lappy's out of warranty (from 2010). Thanks again!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If i got i correct nuhi and the creator of Dism++ use another way to communicate with the Deployment Libraries, without using dism.exe.
Think these conversations need their own thread because it has nothing to do with this project but slipstreaming methods instead.
We are trying to figure out the cause of the black wallpaper and they suggested it was a slipstreaming issue.
Already discussed, the slipstreaming affects Ease of Access with some slipstream methods. Exactly, not project related.