I don't believe there's any rule in sharing $oem$ folders smorgan. I've shared almost every pre-activation $oem$ folder I've made. The only problem you might have is if you tried to include other full commercial software versions inside your folders as part of install. Like say you put Office2013 PPVL on a wim file, stuff it in the $oem$ folder and script it to apply and install during setupcomplete.cmd I believe they would have a problem with something like that. That being said, I don't think that small commandline versions of programs like the little 7z.exe or unrar.exe would trigger any dmca complaints. I think the no custom ISO rule is a combo of the dmca avoidance and a sanity rule. Everyone and their mother would link to new ISO files every time they made one if we didn't have that rule.
This is why I consulted with Tito on the matter. However I believe in bending the rules however given my past here I wanted to make sure. I think I can poke you in the right direction for the ISO and at the same time I can do the scripting here. However exclude the many of the files in the apps folder.
You would think so however I have not because I just update the software and bypass the trials in my own way. However I make that up by running a crap ton of Virtual Machining on my computers. All this so I can be lazy at some point and just push a button and have all my software pre-configured and everything. I've actually moved away from the scripting seen above to a more modularized basis so that its easier to manage each script. The last thing I did was update 8.1 to Update 1. Most of this was simply a distraction for me
Well time for an update... I'm working on standardizing the pack to make it more friendly. I think I'm running through virtual machines far too fast lol. I'll update the scripts used and the folder structure as well murphy
1. So I wouldn't have to modify my coding to fit with the rules of the forum. 2. The Coding contains pirated and shows how it can be pirated / cracked. 3. On consulting with Tito regarding the forum rules so this what I came up with. Now I believe that justifies posting images because if I made the code fit the forum rules I would of had to edit to remove such material from batch files in question. This would inconvenience the scripting I've already done And this is to serve as an educational way to make the scripting and folder structure for people looking to make OEM Packs. I can't knowingly put my scripting onto the forum as the educational experience would be void.
would it be against the rules to post the code in pastebin.com and then link to the code? That is how people are using the GVLK keys without posting here. Just a suggestion if possible.
Given the software installed and used inside of the OEM Pack is used to crack software I doubt the staff would like that lol
Shouldn't blame the tools for being evil, for it is the user that makes evil use of the tools!!! hehee
(starts to chuckle a bit) Aside from that fact it's still against the forum rules which are alas still in effect. (uses magic weather gauge) yep still there. You can get the scripting elsewhere anyway lol