ar_seven_am
-
Posts
47 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by ar_seven_am
-
-
hi liam, just suggestion, in wim manager also AIO tool, instead checking "IMAGE NAME" why not checking "IMAGE INDEX"? it's more accurate becuz even in the *.wim image u have the same "IMAGE NAME" but different architecture (x86 or x64) it will correctly load/mount the image we choose.
why I said that? I give my test result (actually I forget to rename the "IMAGE NAME" of image that I want to build in dual architecture (x86 n x64) but I found ur tool bug).
1. Source: install.wim -> Windows 7 ULTIMATE (x86) & Windows 7 ULTIMATE (x64) exported manually by imagex. (dont rename the image, just export that)
2. Mount image index 1 (Windows 7 ULTIMATE (x86)), it mounted correct.
3. Mount image index 2 (Windows 7 ULTIMATE (x64)), it will mount image index 1 becuz ur tool only check "IMAGE NAME" which have the same name as "Windows 7 ULTIMATE".
thx in advance.
-
@myselfidem,
I believe the general question remains: Is it better or more reliable to order the x64 sub-section before the x86 sub-section in any area of the Autounattend.xml? If it solves a problem for anyone, and does not cause a problem for anyone else, wouldn't it be better to do it that way?
Cheers and Regards my friend
this is what I'm tryin' to suggest bphlpt, thx for posting that.
-
I'm not having problem, I'm just give you suggestion, is it clear to YOU?
instead DISCUSSION or TEST of this multi autounattend setting, YOU complaining for my language?
oh well nevermind.
-
why it need to be complicated? why not just move x64 unattend setting as first n x86 as the 2nd, do u get what I mean? also sptdinstal is only virtual driver for daemon, I only made that as example
, no need to be serious.The main reason I put that in specialize setting so in OOBE setting, in firstlogon.cmd u can run daemon installer silently n the virtual driver already there (not needed actually if u use audit setting in autounattend).
I dont trust the documentary 100%, almost all of my problem solved in forum.
for virtual machine, I use vmware, but if u want to run x64 aplication, ur processor must have x64 criteria otherwise u cant run that.
note: I use translator too, so I'm sorry if u dont understand, I try my best to explain.
-
have u check in WSIM? how can that feature enable if we cant use the advantage? u can use that in audit, specialize also OOBE, it doesn't related to be more specific as long u put in correct place.
just try to add RunSynchronousCommand in ur multi autounattend, u'll find that case.
-
it's not bout the firstlogon command, it's about numeration, an example if I use this :
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x64.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x86.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>will work to install sptd drivers for x64 in x64 OS, but if I use this :
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x86.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>%SystemDrive%\Install\Apps\Daemon\SPTDinst-x64.exe add /q</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>it will choose x86 setting even what we choose to install is x64 in the first of windows 7 installation (only in windows 7, in windows vista doesn't have effect, it will work).
notice the different mate? only change amd64 first, n the 2nd is x86 setting.
-
myselfidem, I think ur autounattend.xml will not work if we add some extra command in setting specialize also OOBE, an example I make 2 firstlogon command (one for x86, 2nd for x64), becuz since x64 have x86 feature too in the image, it will check x86 setting too even we choose x64 image, that will mess up installation command if we make that separately depend on the system architecture itself (mostly worse in specialize setting, if we choose x86 as first, it will use x86 n ignore x64), all u need to change is move amd64 first as first setting than x86 as 2nd setting in autounattend.xml.
u could test that by urself, thx!
note: I think for windows pe setting, u dont need to make double, just use x86 since it based on ur boot.wim, right? (Please correct me if I'm wrong)
-
I made it after you mentioned it (same day), took 5 minutes lol. Does it work for you? any performance difference?
yes it work (actually it help alot my nephew who work as web designer also graphicist), this tool releasin' memory which somehow default memory optimisation in windows 7 doesn't work well in dual core processor (work normal in x3 or higher processor) if we do multitasking there (in his case is coreldraw, adobe photoshop, adobe indesign, adobe macromedia etc).
this tool help when switching one apps to another (release memory when u didn't used that).
I would recommend people pass this over and avoid it just like all the other garbageware RAM "optimizers".
Per Mark Russinovich
if u dont understand how this tool work, u should try first instead posting some useless comment which might offend someone.
legolash make this apps based on my post here http://www.wincert.n...dpost__p__78749
this tool doesn't offer "MAGIC" thing, it just releasing free memory in ur RAM, it work SIMPLE but very USEFULL.
-
I myself have never had a problem replacing it, make sure you are only doing the one in the sources folder
yes ricks, I replace that in the source folder in boot.wim index 2.
could it be the problem becuz the source DVD? I'm using en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso (Windows 7 SP1 x64 media refresh) source.
edit, now I can integrate that, strange....
-
You extract them and update the DVD root files with them, some apply to WAIK and boot.wim but not in the auto integration sense, you still have to manually decompress and overwrite files (KB2495879 needs a registry edit)
BTW dont go by what the KB articles say about integration into boot.wim, whoever wrote those are idiots who dont know their sh!t
hi rick, I'm havin' trouble integrate KB2495879-x64 into boot.wim index 2 since when I try to replace wdstptc.dll with the updated one, I always have error message "Can't read source file" even I've take ownership the file, hmmm....
I'm using windows 7 sp1 x64 host by the way...
-
http://www.wincert.n...6-freeram-tool/
Let me know what you guys think
lol, lego u make that as an application, eeergh I spend 1 day just to make this executable, havent know u separate this as single application.
thx mate.
-
It's not a tweak, its just 3 lines of code which W7T runs every so often to release unused memory which W7T has used but not needed anymore. So again it's not a registry tweak, command prompt run, script, etc...
Are you planning on making you're own program to do the same?
hmmm, but it's actually work in releasing CPU from too much resources (when I see task manager, the CPU bar is back to normal, n it makes the notebook perform better).
I'm not planning on makin' my own program, it just I'm spending about a month tryin' to make windows 7 work just like I expected in this notebook but I have no luck. Yesterday I'm just checking ur new w7toolkit n I got surprised becuz ur "Free Memory" options in W7 toolkit is actually fix performance issue while using Windows 7 in this notebook (there are 3 os, freedos (linux), xp x64, n windows 7 x64).
thx in advance.
-
@liam, in w7tookit options, u've add "Free Memory" which keep releasing available W7T memory, may I know what do u add/edit? I'm tryin' to find out what caused windows 7 are slow in some notebook (in my case its acer aspire 4540, 4 GB ram, AMD Turion II M520) n seem ur tweak in "Free Memory" work perfectly, so I think it can be used as tweak in global setting for windows 7 too.
mind to share that mate? thx in advance...
-
*** Update request filled ***
-
If you are using this on MCE ignoring my warning I HIGHLY suggest you remove/delete the following text from Entries*.ini
[sysoc]
SonicDVDandCDBurning=ocgen.dll,OcEntry,sonic.inf,,7
WinPlus=ocgen.dll,OcEntry,plusoc.inf,,7
[ExtraFileEdits]
SYSOC.INF|Freestyle=medctroc.dll,MedCtrOCISetupProc,medctroc.inf,HIDE,7|Freestyle=ocgen.dll,OcEntry,medctroc.inf,HIDE,7|1And
[AddMCEReg]
HKLM,"SYSTEM\WPA\MediaCenter","Installed",,"1"I'm sorry rick, I didn't mean to ignoring ur warning, but I just want u to know it work or not. I only test it on a real machine for the real prove, n I've deleted the entries before u tell me (except for the last registry entry, sorry) I learn from u by the way, remember when I ask for makin' my own addons a year ago? Anyway, thx in advance!
-
I'm sorry rick, r u sure it can be integrated into xp mce 2005 disk? I've test into xp mce 2005 n it work, anyway here's the step I make :
1. Update the xp mce 2005 source with sp3 with update/addon creator from onepiece/nonno fabio
2. Slipstream onepiece updatepack v4.10 for xp sp3 with ryanvm integrator.
3. Slipstream ur addon with nlite
I install in acer aspire 9410 (it had xp mce 2005 OEM version pre installed before but it need to reinstall just like I told u before) n work charmlesly. Even the media centre it self updated same as we update with rollup 2.
Regards
-
This addon is NOT to be used with xp media center disk, it does not update it with update rollup 2
uuugh, I see, thx rick!
-
Rick, I'm sorry if it's late since it's an old thread but lately when I help my friend in his store there's some consumen ask me to reinstall his notebook, he gave me 2 CD XP MCE 2005 as a source. My question is, do I still need this addons since the first page said it convert XP pro to MCE 2005 or it work too since it had update rollup 2 n some hotfix needed for XP MCE 2005?
-
I'm sorry kels, i've test kel's cpl v10.4.4 but it seems some tools just like hp format tools is not displayed, so i check the .inf file, i've edited n compared to ur previous version n I guess I know what's the problems, its the icon display, so if everyone has the same problems as I'm here's my edit, hope Kels don't mad at me :worthy: n happy birthday for u, sorry if I'm late.
-
Thx Rick, i wasn't read carefully bout ur post, the answer is there, i'm really sorry!
-
Hello all, i'm new to this forums! I want to make a true addons using tools that provided this forums, i'm still confused to make an inf n ini file. Just for example if i want to make directx addons that slipstreamed completely use ryanvm or nlite, i dont know what exactly list of file should i choose to build ini n how to make inf file too! I take a look at reg2inf programs which can convert *.reg to inf but i dont know what in the regedit i've to import! Anyone can show me a tutorial for makin true addons?
Any help from u is very appreciated, n i'm sorry for my english, i'm not too good at this!
, no need to be serious.
Create your own Autounattend.xml All-In-One (x86/amd64)
in Microsoft Windows 7
Posted
myselfidem, you dont need to set 2 setting in "<settings pass="windowsPE">" becuz that only for boot.wim which we used only one (x86 boot.wim), if we do add x64 setting too, some automated task like "Accept EULA" will be asked again if we choose x64 image.
also I'm still tryin' to find out how to make custom menu so incase we need to repair our windows installation, we can still use our customized dvd (if we add autounattended setting there, it will skipped n directly to windows installation).
also guys, if you use usb as ur installation media, it's recommended to follow ricktendo methode (copy the autounattend.xml into boot.wim image index 2, offcourse you need to mount that first and unmount with option commit), that methode work for me everytime.