Jump to content

Mr_Smartepants

Members
  • Content Count

    807
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Mr_Smartepants

  1. PowerPacker can create DVD & USB iso. It works on all NT5 variants (2000, XP, 2003) and DriverPacks. Info here: http://cpu.reboot.pro/viewforum.php?f=8&sid=26703b92d4f366feee06501524dfbefe
  2. I don't like it, but I support your decision. We're going to miss you brother. I sincerely wish that your luck and situation changes for the better in the new year. But I like that!
  3. To test it, I logged in as a normal user and opened a cmd window as admin and pasted the following. start "" /min /separate %comspec% /c shutdown /r /t 90 /c "Finished Phase 1, base install, the system will reboot in 90 seconds and start Phase 2 - RunOnce WU_Satisfy" As expected I got the warning message "Finished Phase1..." and the system rebooted on its own 90 seconds later. Can you get a screenshot of the message? (pause VM, screenshot).
  4. Try this: 1.) Click the below link and the button " Install Windows 8.1 Pro " and choose make USB or ISO file http://windows.microsoft.com/en-us/windows-8/upgrade-product-key-only 2.) Boot to USB and 'install full version' or 'upgrade' your choice (use a Windows 8.1 Pro Key) (if fails, prep the USB key using instructions from http://www.tinkertry.com/rufus-takes-5-minutes-to-create-a-uefi-bootable-usb-3-0-flash-drive-for-windows-8-1-installation/)
  5. The "planned/unplanned" reasons were there only for server OS since they will halt the shutdown/restart to ask for a reason. Consumer OS types don't ask. More info: http://technet.microsoft.com/en-us/library/cc732503.aspx I remember having a problem with shutdown before. This will open a new command window and run the 'shutdown' line from there. It'll also allow the first window to close gracefully while the shutdown is in progress. Try this instead: start "" /min /separate %comspec% /c shutdown /r /t 90 /c "Finished Phase 1, base install, the system will reboot in 90 seconds and start Pha
  6. The "/d p:0:11" parameter is not valid. Major:0, Minor:11 doesn't match anything in the below table. Just skip it. Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\Blah>shutdown /?Usage: shutdown [/i | /l | /s | /r | /g | /a | /p | /h | /e] [/f] [/m \\computer][/t xxx][/d [p|u:]xx:yy [/c "comment"]] No args Display help. This is the same as typing /?. /? Display help. This is the same as not typing any options. /i Display the graphical user interface (GUI). This must be the first opt
  7. You want the official DriverPacks tool...SAD (Stand-Alone Drivers) utility. http://forum.driverpacks.net/viewtopic.php?id=5336
  8. Install in VM both with all 12000+ drivers and without. Then check each "C:\Windows\System32\DriverStore" folder and report back the different folder sizes. You'll see what I'm talking about, and you may change your mind.
  9. Holy Crap that's a lot of drivers! :omg: I can't imagine what your DriverStore folder looks like. It must be HUGE! Typically, I only integrate critical chipset drivers and mass-storage drivers into the .wim files. Then I integrate all the drivers during post-install via our SAD (Stand-Alone Drivers Disc) utility via setupcomplete.cmd. SAD discussion thread (and download): http://forum.driverpacks.net/viewtopic.php?pid=53470#p53470 If you integrate too many drivers then your "C:\Windows\System32\DriverStore" folder will balloon out of control. I don't know if there's a hard-limit but I'm
  10. http://www.microsoft.com/en-us/download/details.aspx?id=39306 I'm guessing that ADK 8.1 isn't final yet since its title says it's for "Windows 8.1 Preview". I'm having problems servicing WS2012r2 testing isos with it. The ADK toolset should be backwards compatible to service OS builds going back as far as Vista. It must be installed on Win7 or higher.
  11. You mean the current directory where the installer files are stored? Sure. Shouldn't be too much of a problem. Thanks for asking, you actually pointed out a minor bug in my code (fixed now). Here ya go: @ECHO off & setlocal EnableDelayedExpansionSET "O_LOGFILE=%systemdrive%\install.log":PROCESSORREM :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist. SET "ARCH=64" & SET "ARCHP=x64"IF /I NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 (SET "ARCH=32" & SET "ARCHP=x86")) ECHO>>"%O_LOGFILE%" 2>
  12. Nice link. :doh: Here you go. http://www.microsoft.com/en-us/download/details.aspx?id=5201 Updates: http://www.microsoft.com/security/portal/definitions/adl.aspx
  13. As a test (Win7 VM), I installed the original .net 4.5 installer (from here: http://www.microsoft.com/en-us/download/details.aspx?id=30653 ). Then after a restart, checked Windows Update and only got a list of 9 updates to install: KB2737083 KB2742613 KB2750147 KB2789648 KB2804582 KB2805221 KB2805226 KB2833957 KB2840642 This differs quite a bit from the list of updates you include in your repack. In fact, KB2519265 doesn't have any M$ page associated with it and isn't available from anywhere other than McRip's archives.
  14. You can try my batch script which will rebuild your source into a dual BIOS/UEFI .iso file. Change the variables to suit your needs. @ECHO offsetlocal EnableDelayedExpansionREM :: Set path to source directorySET "src=%cd%\src"REM :: Set custom name for ISOSET "ISOX=Win7-64":OSCDIMG-checkREM :: Detects the presence of oscdimg for .iso creation function. Critical check, will exit utility IF NOT found.IF /I EXIST "%ProgramFiles%\Windows AIK\Tools\%PROCESSOR_ARCHITECTURE%\oscdimg.exe" (SET "OSCD=%ProgramFiles%\Windows AIK\Tools\%PROCESSOR_ARCHITECTURE%\oscdimg.exe") ELSE (ECHO ** %time%- OSCDIM
  15. Well in that case, here's the same code altered to use x86/x64 folders instead of in the filenames. @ECHO off & setlocal EnableDelayedExpansionSET "O_LOGFILE=%systemdrive%\install.log"FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO (DIR %%i: && IF /I EXIST %%i:\sources\install.wim SET "CDROM=%%i:") >nul 2>&1ECHO>>"%O_LOGFILE%" 2>>&1 Found install-source as drive %CDROM%:PROCESSORREM :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist. SET "ARCH=64" & SET "ARCHP=x64"IF /I NOT EXIST "%SystemRo
  16. Here's a batch script to accomplish the .msp update/install from setupcomplete.cmd (or anywhere else). I haven't tested it in a live install, but I've done a mock-install and the logfile has the correct output. Should be fine. *Edit: Obviously you'd need to change the file paths to suit your needs... @ECHO off & setlocal EnableDelayedExpansionSET "O_LOGFILE=%systemdrive%\install.log"FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO (DIR %%i: && IF /I EXIST %%i:\sources\install.wim SET "CDROM=%%i:") >nul 2>&1ECHO>>"%O_LOGFILE%" 2>>&1 Foun
  17. You do realize that flash media only has so many write cycles and then they die...right? Try it on a different machine. If it's dead, then throw it out (or smash it with a hammer to vent your frustration) and buy another one. They're cheap now.
  18. It doesn't work because Realtek broke it; not because of anything WinToolkit does. This happens all the time. Realtek is notorious for breaking support on older hardware in order to support newer hardware in their monolithic drivers. They're not the only ones either. On my Asus laptop, I'm constantly nagged by Windows Update for an updated USB3 driver (Fresco Logic). When I update to the newer version it kills all my USB ports until I revert back and hide the update. This continues with each new version.
  19. I say this all the time. When it comes to drivers, newer is not always better. There's no reason to upgrade drivers (or bios) unless that update fixes a problem or adds significant functionality or performance. Use the driver that works. End of story.
  20. And your key is most definitely NOT the one on the sticker. Those CoA keys haven't been the real keys since XP SP2. Your key is called an OEM-SLP key and each manufacturer uses the same key on thousands of machines. You can also load the cert/key after the OS is done installing. slmgr.vbs -ilc PATH\to\your\certificate\*.xrm-msslmgr.vbs -ipk KEYKE-YKEYK-EYKEY-KEYKE-YKEYK <reboot>...done!
  21. Rick, I notice you don't list KB2804582. Is that because it is replaced by a newer patch? It's showing a release date of yesterday. http://support.microsoft.com/kb/2836440 http://support.microsoft.com/kb/2804582 If it's superseded, which update replaces it? Thanks!
  22. Instead of messing around with global (system) environment variables (generally regarded as a bad idea), why not just use a symbolic link? http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ http://www.windows7home.net/how-to-create-symbolic-link-in-windows-7/
  23. KB2840149 released today (24 Apr) to solve this problem. http://support.microsoft.com/kb/2840149 http://www.winbeta.org/news/kb2840149-update-windows-7-released-replaces-botched-update-caused-infinite-reboots
  24. Ah, got it. The file ID is in the page HTML code.
×
×
  • Create New...