MAVERICKS CHOICE
Content Type
Profiles
Forums
Events
Posts posted by MAVERICKS CHOICE
-
-
Are your Mb's capable of allowing booting by USB? If so have you set the bios correctly for that option?
0 -
I would also like to take this opportunity to wish all Admin, Mods & MSFNers a very Merry Christmas & fine 2009.
Thanks so much for everyone's response & contributions here throughout the year.
Have a great one......
0 -
What OS & os version are you installing the waik on? I had the same issue with XP sp3 would not install.
0 -
How are you producing your xml? Are you checking it, validating it with the wsim? Looking through your xml appears to have all the necessary fields. Just on the Timezone issue you have a quick review of my xml have specified timezone/location etc four times in total pe,audit, specialize & oobe.
The network problem is overcome with this reg entry.
<SynchronousCommand wcm:action="add"><Order>5</Order>
<Description>Block_ Network </Description>
<CommandLine>cmd /c reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\NewNetworks" /v NetworkList /t REG_MULTI_SZ /d "" /f</CommandLine>
</SynchronousCommand>
The wsim has a great built in help files recheck your xml.
0 -
Just in testing 7 with VLite seems to work fine here. I did notice you cannot remove many files from the Sources dir as we do in Vista cause the installation won't get past the pe boot.
Anyone else noticed this?
0 -
Yep Vlite works fine, exept for drivers (Never worked for me.) and hotfixes.
Those things you need to do with Dism.exe.
(Deployment Image Servicing and Management tool)
Mount an image from Windows 7 and go to "System32" in the mounted wim.
Copy the directory "DISM" and the file "DISM.exe" to the system32 folder of your computer.
For x64 this is wow64 ( Im not sure cause i dont have the x64 version. )
Open the DISM folder and register the dll's inside (Some cant be registered.)
Then do "DISM.exe /?" without the quotes in a command promt.
Then you will see how it works.
I sucsessfully integrated drivers and the hotfix that is there for Windows7. (Used Vista drivers for that, most work fine.)
So the old ways to do this will not work on Windows7 anymore (pkmgr and peimg.)
And very importand is to not empty the sources folder on the root of your windows7 DVD.
With Vista it was no problem to remove all things in there exept "boot.wim" and "install.wim"
Thanks for the heads up spOOf, please empty ya inbox man....
EDIT: Few q's guys whats the min that must be left in the root & sources dir for the OS to work.
0 -
+ 4gig sounds way too big for just integrating sp1?? How did you integrate it? What method?
To give you an idea mines under 3gig with nothing removed from the source?
0 -
As Vista comes in a dvd fashion don't think it's gunna work for you in that case. But I may be wrong...
0 -
I have successfully used VTool as mentioned above with only minor issues. I find it more reliable than VLite & less buggy.
the biggest issue is not so much the integration but the drivers themselves.
0 -
Does anyone have a problem integrating Windows6.0-KB958644-x86-EXPRESS.cab or the Windows6.0-KB954955-x86_Tinkerbell.cab into their source.
For some reason when I integrate with both VLite fails each time all other patches no problem??
I also tried the other soft VTool it integrates without fail but will not install.
Any pointers with these fixes guys?
0 -
Not a 100% certain here as you don't seem to show your entire xml. Pretty sure for this to work as stated you will need to include the user info as well in the OOBE pass, it has been documented on this board previously.
0 -
You can certainly invoke many commands in the install of Vista, you may not be able to incorporate addons into an install but can use many progs such as wpi, I have successfully used wpi with Vista for the past 18 months.
0 -
Regarding Spoof problem.
Buttons don't mess for me in this version (in older it was). I have changed every theme I know, including Corp. It was OK.
Still a problem here but only minor & not affecting the install.
0 -
Not really relevant to this section. However remember most addons generally are "silent installers" or can be run silently with the correct switches.
0 -
No probs installing here. Maybe try DL it again?
0 -
Hi Max...
The download link on your site does not work...
Have you taken it off again?
Just sign up to his Forum & follow the DL links.
0 -
Does everyone have to be spoon fed? Just use the search button...
0 -
Try searching "autounattend.xml" in this section, plenty of hits.
Understand it's not for us members to do it all for you. This UA stuff can take years of study. I can assure you all the info you need to create a Vista UA install is here & can certainly be done.
0 -
Man ya couldn't have searched very far? plenty on this board...The waik help files are great this UA is very time consuming & no one really masters this & its never finished.
0 -
@Kel: I'm having the same issue here, useing the Corp_WinXP theme
edit: After saving the config, the buttons returned to normal!?
Same prob here but no biggy.
0 -
The best way to attack UA is bit by bit, much testing as well. My recommendation is get your answer file down pat first before moving on to apps & cleaning up.
There are plenty of fine ans file xml's on this board that work & can be modified for your use.
Good luck with it.
0 -
Nah I don't
I only have 256kb connection speed so download 1GB+ was an issue.
I spent a fair while just searching for a way to install and use vLite without waik
You really only require the "wimgapi.dll" from the Tools folder to run VLite. It has been put up on these forums before.
0 -
Normally in firstlogon.cmd but could be referred to as first.cmd
This is how I start WPI from UA
<SynchronousCommand wcm:action="add">
<CommandLine>%AppsRoot%WPI\WPI.hta</CommandLine>
<Description>WPI Application Installer</Description>
<Order>120</Order>
</SynchronousCommand>As for shortcuts & cleaning up I do this in WPI.
0 -
Great news Max, got your new site address & look forward to the release.
0
install aps
in Unattended Windows Vista/Server 2008
Posted
The text file should be blank.
You need this in your xml:
Your first logon command should be something similar to the following:
Can't help with the sysprep.