Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

It's the activation urie, but not the logo etc, before that I use ur methode in vista section bout oem dvd (converted to 7) n I also use Se7en_UA by veegertx, but it's only work for single OEM not multi OEM, anyway I download the apps but now with daz loader n guess what, the scripts call the loader to install the key n certificate, anyone had an answer for this? I'm really confused here, why it's not work for x64 but x86 r succesfull????

 

weird, ill have to try myself..

 

@ ar_seven_am, it will be the way the registry is in x64 Van i,e, (MaxXP) had problems with Jump2REG to begin with had to alter it for certain x64 it wasn't reading certain registry strings.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

@ tcntad, does sam's script activate x64 ? just wondering because as ar_seven_am mentioned, searchengine's doesn't.

 

urie, I'll test for u, but by now there's no client machine that had slics 2.1, n my lappy is borrowed until tomorrow, I guess I've to wait tomorrow becuz when I test in vmware (with patched slics) the searchengine scripts work in x64, strange...

 

Im not entirely sure if it activates 64bit or not.. I would need a computer to test it.. My gf will use my computer for studies later and it seems something's wrong, either memoryleak or perhaps with the satacontroller.. I can start and run vmware for example but it will use almost all my ram, same if i copy files from/to other drives.

Thats weird.. as i said, il have to try that myself and we need to wait for searchengine's comment on this

 

I am installing on vmware with using searchengine $oem$ at the moment to see what happens, may also try full install on my own machine tommorow.

 

Great!

Would be goodif you could try your real machine tomorrow to verify if its working or not

 

You need to login to view this posts content.

 

Great! I will also try this later

I whonder why it doesnt work for him though:/

 

Sorry, I've to correct ur comment, I've said that it work on vmware but not on real machine! Both sam scripts n searchengine work well, I dont know why it doesn't work on a real machine,

 

Aha seems i/we missunderstood

Then we need to know which link you used:
Link 1, 2 or 3?

Link 1 is only for bios with SLIC 2.1 (to activate w7 offline like oems do it)
Link 2+3 is using a loader to "copy"/act as SLIC 2.1 in BIOS, this loader is loaded before windows really starts.

But why x64 fails and not x86 would be harder.. Maybe like urie said, could be some mess up with registry or whatever he wrote few posts earlier

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

There are no drivers for activating machines, only reading what oembrand and slic it has then install key+cert and finally oemlogos..

If you have a yellow mark in device manager its beacuse you havent installed all necessary drivers.

 

BUMPS, it's solved, it's not becuz the driver problem, it's becuz my unattend.xml, since it use OOBE command then I remember what Max aka veegertx aka van told me, see this OOBE section in autounattend.xml :

<OOBE>
<SkipMachineOOBE>true</SkipMachineOOBE>

it should set to false, the question why x86 success but x64 failed becuz I use different media as a source (USB pendrive n DVD rom) n I forget to edit the x64, uuuuuuh just a silly mistake but had a big effect,

 

No oobe.cmd should be in C:\Windows\Setup\SCRIPTS but most delete the scripts using the oobe.cmd.

Code:

::all processing finished, delete used files, and EXIT::
:CLEANUP
IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul
DEL /F /Q %0% >nul

or here is oobe.cmd from official dell dvd.

Code:

@echo off

start /w regedit /s %systemroot%\setup\scripts\oem.reg
del /F /Q %systemroot%\setup\scripts\oem.reg
if not exist %systemroot%\panther mkdir %systemroot%\panther
if not exist %systemroot%\panther\unattend.xml copy %systemroot%\setup\scripts\oem.xml %systemroot%\panther\unattend.xml
call %systemroot%\setup\scripts\slp.cmd
del /F /Q %systemroot%\setup\scripts\slp.cmd


:Cleanup
del /F /Q %systemroot%\setup\scripts\oobe.cmd

As for panther folder check out log files for errors.

 

You need to login to view this posts content.