• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Phorze

  • Birthday
  1. I have the same problem, using the official version with SP1 integrated (technet) and trying to transfer the OEM to it for my laptop. looks like the $OEM$ folder trick doesn't work anymore trying to turn it into an OEM DVD. If they don't want me to do it they should have supplied a proper vista dvd with my laptop.
  2. netsh wlan set autoconfig enabled=no interface="Networkname" will do the trick, however, it will be switched on as soon as you reconnect, or restart your system Use this tool to monitor the autoconfig, it'll make sure it stays disabled.
  3. Having this problem for months now, I have called WD several times, and they claim it's a vista problem. (ironicaly the product is "vista ready") What i've found out the last weeks is that the bios detects it as a bootdrive and somehow vista can't handle that. Basically both Micro$haft and WD are too lazy to take up this problem, waiting for eachother to fix it. I'm very close to smashing the case to very tiny pieces and just use the bare drive instead
  4. ATM i got the same issue, the driver likes to install like 40 unsigned drivers. Now , i got a fully vlited install, but i got some application installs that can't be done with vlite yet (but knowing nuhi it wont be that long before we can integrate apps again ) But meanwhile i actually reopen the installation with WAIK, and slap in a sysprep session.... So my idea is, not using the inf driver integration method, but adding a silent install to sysprep and putting in the BCDEDIT command before it and forcing a reboot. It might work, ill check back with the results. I think i read somewhere else it's possible with a regtweak too. I'll see.
  5. Somehow i just can't get it to work, i have slimmed down Autounattend to find the problem but no avail. Notes: the Administrator account is made , but on oobe i get the standard dialog to make an account. If i use administrator as accountname, it gives an error saying the name is allready taken. When i pick user named "test" and log in, there is no other account than test , and test is the administrator account (what happened to "administrator"? ) None of the applications are installed, no errors during setup. According to the SET command in cmd, no APPSROOT var is set. By the looks of it just skipped the whole audit section. All tests are done in VMware 5.3 Autounattend: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi=""> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>cmd /c FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\AppsRoot.txt SETX AppsRoot %i: -m</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>2</Order> <Path>%WINDIR%\system32\sysprep\sysprep.exe /quiet /audit</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings> <settings pass="auditUser"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi=""> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Path>cmd /c %AppsRoot%\Switchless\Office\Office.exe</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>2</Order> <Path>cmd /c %AppsRoot%\Switchless\Firefox\Firefox Setup /S</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>4</Order> <Path>cmd /c %AppsRoot%\Switchless\MPC\MPC_addon.exe</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>3</Order> <Path>cmd /c %AppsRoot%\Switchless\VCP\vcpack.exe</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>5</Order> <Path>cmd /c %AppsRoot%\Switchless\Nero\Nero- /VERYSILENT /USER="Roos" /COMPANY="None" /SERIAL="=removed="</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Order>6</Order> <Path>cmd /c %WINDIR%\system32\sysprep\sysprep.exe /quiet /oobe /reboot</Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi=""> <AutoLogon> <Password> <Value>encryptedpassword</Value> <PlainText>false</PlainText> </Password> <Enabled>true</Enabled> <Username>Administrator</Username> <LogonCount>5</LogonCount> </AutoLogon> </component> </settings> <cpi:offlineImage cpi:source="wim:f:/vistawork/dvd/sources/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> setupact.log: removed, see attachment (was a bit long) :rolleyes: setuperr.log was empty. setupact.txt
  6. I heard about dell and other manufacturers shipping OEMs that are preactivated and bound to the hardware in several ways. Might be one of those?
  7. Thanks Firegeier , great guide Another question, is it possible to get feedback if something goes wrong? Because somehow my application installs don't get installed at all, and i can't know for sure what went wrong.
  8. Like "cmd /c %AppsRoot%\Switchless\Office\Office.exe" ?
  9. Ok you where right, it did NOT work with v6.86, i got it working now with v6.85. Thanks for the help fernando!
  10. Both? i have to pick nvraid.inf and nvatabus.inf? Because if i load one of the two, i can't add another , it will say something like "driver allready added" So i guess it comes down to nvraid.inf OR nvatabus.inf. anyway, im going to check out 6.65 now. ( i wonder if it actually has different fileversions) EDIT: Sorry fernando i think i know what you meant with both drivers, you mean select both proposed controller drivers after you select one of the INF files. Yeah thats what i've been doing since the beginning, and ofcourse loading them as TXT mode drivers.
  11. ok i've added the last session of one of my most recent failed builds to the first post.
  12. Recently i have become interested in tweaking windows, creating unattended installations, these boards are allways very helpfull. However today i have an issue i simply cannot grasp I have nLited a windows install, and it works correctly on VMware. However , if i try it on my PC, it won't boot. Here's what happens: The installation runs correctly untill the final reboot. (the last parts are "registering components" and "saving settings" or something, then it reboots). Normally after this reboot it should initiate the first windows use (change resolution etc) BUT it keeps rebooting, my pc ends up in a rebooting loop. So somehow it doesnt recognise the fresh installation. In addition it seems to erase the complete MBR record because it doesnt let me boot to my old installation when that happends. The thing is , how can i ever know what's the problem if i dont get an error report If i should post any of the SIF files please ask, im not sure what can be usefull. [EDIT] I use the integrated NVraid drivers , from the "legacy" folder of my nForce driver package, v6.86 My NVraid biosversion is 4.84. [EDIT2] I've read the guide for integrating NVraid drivers but im still not sure what i should pick. I have a Nforce 4 ultra chipset. Should i use the SATARAID folder or the LEGACY folder. Untill this stage i have allways chosen the LEGACY folder. However it contains 2 .inf files i can choose from: "nvraid.inf" and "nvatabus.inf" LAST_SESSION.INI Last_SessionLATEST.ini