thank you so much searchengine! these past few days, i've been going through Internet withdrawl because of all the downtime doing clean installs. you cannot imagine how much work/time you have saved me. I downloaded your $OEM$ last week sometime and looked through it, but did not find any .theme file, that's why i assumed it did not support it. I must have missed it. My apologies. Question out of curiosity: 1. Why would it deactivate, after being activated, when removing Windows Components? could it be related to Machine ID?
Loaders can do this if they get flagged so if anyone is using a loader that can happen with older loaders. BTW normally you do not need that much in the setupcomplete.bat file because everything should happen in setup.bat. Here is what I have in my setupcomplete.bat file: Code: @echo off start /WAIT %~dp0Install.bat cd %~dp0 DEL Install.bat del ACER.XRM-MS del ADVENT.XRM-MS del ALIENWARE.XRM-MS del ASUS.XRM-MS del BENQ.XRM-MS del bootinst.exe del COMPAQ.XRM-MS del Casper.XRM-MS del DELL.XRM-MS del eMachines.XRM-MS del EXPER.XRM-MS del FOUNDER.XRM-MS del FSC.XRM-MS del FUJITSU.XRM-MS del GIGABYTE.XRM-MS del grldr del HAIER.XRM-MS del HASSEE.XRM-MS del HCL.XRM-MS del HP.XRM-MS del HPPro.XRM-MS del JOOYON.XRM-MS del LENOVO.XRM-MS del LG.XRM-MS del MEDION.XRM-MS del MSI.XRM-MS del NEC.XRM-MS del NOKIA.XRM-MS del PBell.XRM-MS del QUANMAX.XRM-MS del SAMSUNG.XRM-MS del SONY.XRM-MS del TONGFANG.XRM-MS del TOSASU-Toshiba.XRM-MS del TOSCPL-Toshiba.XRM-MS del TOSINV-Toshiba.XRM-MS del TOSQCI-Toshiba.XRM-MS del Trigem.XRM-MS del VILIV.XRM-MS del WORTMANN.XRM-MS shutdown /r /t 05 del %0 exit Basically what you see is that it just cleans up the system after the operation is complete but that is it. Now I know you have SLIC 2.1 in the bios, I just added the factor about the loader for anyone who is interested so it may be helpful lol. One last thing though, my $OEM$ script does not add any OEM themes or anything, it just activates windows. For that I use Orbit30's OEM Brander that actually modifies the .ISO to add all that stuff like OEM login wallpaper and desktop wallpaper lol.
Interesting, i saw that, but chose to use the $OEM$ by Orbit30. I always assumed it was identical. I thought it just inserted the $OEM$ into the ISO. So the executable is different than the $OEM$ ?
Well Orbit30's branding tool is an actual program that lets you open ISOs to modify them. I was the one that supplied the activation part lol but I had it before I started doing a lot of Orbit30's stuff lol. I get most of it from *another website* but you would normally have to pay to access that site's resources. I think the branding tool actually modifies the WIM files but I am not 100% on that but I think so.
great stuff, i will have to try it out and see. do you know if Orbit30, on TPB, with the Pink Skull, is the real Orbit30? what is the latest release, the numbering system is so confusing. and to have people double/triple post, only adds to the confusion on TPB. I have: - Windows 7 OEM Brander Release 2 - Windows 7 OEM Brander 1.0 - Windows 7 OEM Brander 1.2 Im currently waiting for Win7 Ultimate SP1 RTM to finish downloading so i can integrate this Quick Question: Do you think using MSDN RTM ISO could be causing a problem? I used WZor's leaked OEM ISO for the longest time and never had any issues, then i switched to MSDNs and started having issues. Im just stumped as to why it would deactivate after removing Windows Components.
no problem, no apology needed 1. that's the million dollar question, it is very strange how after being activated; deactivation has been occurring ... it's as though the iso was corrupted with a loader, but I think your original iso was an "untouched" edition? hopefully when you add your $oem$ folder to the integrated SP1 that you are downloading, your headache will be over. using RTM iso is not a problem; I use RTM iso without issue. I'm not familiar with Orbits Win 7 Brander, so I don't know latest version, or how it's supposed to be used.
Whats that about you never provided anything?.. Orbits tool does'nt open ISOs to modify them..lol I know what he does and does not do, your talking silly here bro...lol ?
Hey Sam can you not reference others sites? I know you guys there do developments but rules here are to not spam other sites. Administration here want's to not support sites that charge regular users fee's. It's not personal just not necessary when you make points regarding exploits Much respect timesurfer
Ok NP, I actually was not advertising but more like just saying but I won't anymore lol. @Alfawaves: I was just telling him that Orbit's program modifies the wim files instead of doing the $OEM$ folder cause he asked dude. @All: If I did sound silly I am sorry, been doing college all week and was kinda tired lol
Sam bro, it does'nt touch the wim file.. Its put in sources folder.. EDIT: sam no worries dude i like your work..
thanks dude, with the Orbit tool I was not sure but I thought it used the Wim files lol, I just used it once and it was a long time ago lol.