Jump to content

Mr_Smartepants

Members
  • Content Count

    807
  • Joined

  • Last visited

  • Days Won

    5

Reputation Activity

  1. Like
    Mr_Smartepants got a reaction from Stimpy in [Tool] PEX²³ - Little WinPE Helper   
    "%programfiles%\Windows AIK\Tools\%ARCH%\Servicing\Dism.exe" /Image:"%cd%\WinPE_%ARCH%\mount" /Add-Driver /Driver:"%cd%:\WinPE_%ARCH%\Drivers /Recurse This line is missing the end quote from the /Driver: path.
    Should be:
     
     
    "%programfiles%\Windows AIK\Tools\%ARCH%\Servicing\Dism.exe" /Image:"%cd%\WinPE_%ARCH%\mount" /Add-Driver /Driver:"%cd%:\WinPE_%ARCH%\Drivers" /Recurse 
  2. Like
    Mr_Smartepants got a reaction from Stimpy in Bad News [SSD]   
    All good things come to those who are patient. 
  3. Like
    Mr_Smartepants got a reaction from Sibetinkefe in Happy Birthday Legolash2o   
    Happy Birthday to our WinCert friend Legolash2o!
    Have a great day Liam, and thank you for everything you're doing for Wincert.

  4. Like
    Mr_Smartepants got a reaction from compstuff in [Slim] .NET Framework 4 Full x86/x64 (1-10-2016)   
    For those that want to add the .NET installer and updates to their Win7 .iso, here's what I do.
    1) Make the following folder structure on your .iso. You can use whatever folders you want, but you'll need to adjust the below code accordingly.
    %source_iso%\updates\NET45
    %source_iso%\updates\NET45\32
    %source_iso%\updates\NET45\64
    (Where %source_iso% is the path to where your source files are kept.)
    2) Put the dotnetfx45_full_x86_x64.exe file in the \NET45\ folder. Put any .NET 4.5 .exe updates (when released) into the appropriate \NET45\32 or \NET45\64 folders.
    3) Add this code to your %source_iso%\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd

    @ECHO off & setlocal EnableDelayedExpansion
    SET "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 if exist %%i:\sources\install.wim set CDROM=%%i:
    ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM%

    :PROCESSOR
    :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist.
    SET "ARCH=64"
    IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" (
    IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=32"
    )
    ECHO>>"%LOGFILE%" 2>>&1 System architecture is %ARCH% bit.


    :NET-Framework-45
    ECHO>>"%LOGFILE%" ......................
    ECHO Installing .NET 4.5 Framework & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 Framework
    %CDROM%\updates\NET45\dotnetfx45_full_x86_x64.exe /passive /norestart >>"%LOGFILE%" 2>>&1

    ECHO Installing .NET 4.5 updates & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 updates
    FOR %%X IN ("%CDROM%\updates\NET45\%ARCH%\*.exe") DO (
    "%%X" /passive /norestart >>"%LOGFILE%" 2>>&1
    ECHO>>"%LOGFILE%" 2>>&1 Executed %%X
    )


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


    In this way you can drag & drop .NET updates into your .iso whenever they're released and keep it up to date with minimal effort.
    This isn't as compact as Rick's repack, but you can keep it updated yourself as needed.
  5. Like
    Mr_Smartepants got a reaction from alfreire in [Slim] .NET Framework 4 Full x86/x64 (1-10-2016)   
    For those that want to add the .NET installer and updates to their Win7 .iso, here's what I do.
    1) Make the following folder structure on your .iso. You can use whatever folders you want, but you'll need to adjust the below code accordingly.
    %source_iso%\updates\NET45
    %source_iso%\updates\NET45\32
    %source_iso%\updates\NET45\64
    (Where %source_iso% is the path to where your source files are kept.)
    2) Put the dotnetfx45_full_x86_x64.exe file in the \NET45\ folder. Put any .NET 4.5 .exe updates (when released) into the appropriate \NET45\32 or \NET45\64 folders.
    3) Add this code to your %source_iso%\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd

    @ECHO off & setlocal EnableDelayedExpansion
    SET "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 if exist %%i:\sources\install.wim set CDROM=%%i:
    ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM%

    :PROCESSOR
    :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist.
    SET "ARCH=64"
    IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" (
    IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=32"
    )
    ECHO>>"%LOGFILE%" 2>>&1 System architecture is %ARCH% bit.


    :NET-Framework-45
    ECHO>>"%LOGFILE%" ......................
    ECHO Installing .NET 4.5 Framework & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 Framework
    %CDROM%\updates\NET45\dotnetfx45_full_x86_x64.exe /passive /norestart >>"%LOGFILE%" 2>>&1

    ECHO Installing .NET 4.5 updates & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 updates
    FOR %%X IN ("%CDROM%\updates\NET45\%ARCH%\*.exe") DO (
    "%%X" /passive /norestart >>"%LOGFILE%" 2>>&1
    ECHO>>"%LOGFILE%" 2>>&1 Executed %%X
    )


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


    In this way you can drag & drop .NET updates into your .iso whenever they're released and keep it up to date with minimal effort.
    This isn't as compact as Rick's repack, but you can keep it updated yourself as needed.
  6. Like
    Mr_Smartepants got a reaction from RicaNeaga in Online driver Installer can be run during windows installation process   
    I accomplish this same goal by adding the call to my SAD2 script to the sources\$oem$\$$\Setup\scripts\setupcomplete.cmd

    @ECHO off & setlocal EnableDelayedExpansion
    SET "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 if exist %%i:\sources\install.wim set CDROM=%%i:
    ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM%

    REM :: Snip... ::


    :Drivers
    Start "" /max /separate %comspec% /c %CDROM%\SAD2\DP_Install_Tool.cmd /s

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


    This process takes place after the main install is complete but prior to the first login.
  7. Like
    Mr_Smartepants got a reaction from ar_seven_am in Video Driver not Instaled   
    @Ricktendo64, Thanks for the links. I'll check those out. We've been having problems with Nvidia drivers since they changed their installer method (260-series to present).
    @Kels, Noted.
    @RicaNeaga, I'm sorry that you've had a bad experience with DriverPacks. You are not wrong.
    I've made note of your comments and I will do what I can to split all the Win7/Vista-only drivers apart from each other (unless they're combo drivers). This should make it easier for W7T users, professionals, or folks that know what they're doing to pick out what they need. You're right, sometimes it's easier for us to just update an entire folder than spend the extra time to pick through and separate the drivers.
    However, because of the nature of DriverPacks, we will still continue to produce packs that support all NT6 OS.
    Do you have specific methods you use for testing driver integrity prior to integration? I'd love to hear about it. For Win7 I just integrate with DISM and if we get no errors, we call it 'good'. We want to make sure we build the best & most compatible packs we can.
    Also, if you have specific examples of problems or mismatch, please PM me so I can fix the problems in our packs. We do listen and always love to get constructive feedback. Simply saying "Your stuff is broken" doesn't help anyone.
  8. Like
    Mr_Smartepants reacted to Legolash2o in Driver Architecture Detection on add   
    As well as the addition to above, i have made drivers which are NOT mean't for the OS you have selected they will appear in red, you can then use the 'Remove' > 'Remove All Invalid (Red)' option at the top (W7T v50) to remove them all in one go.
    I believe this is much better because if you 'throw you an error' it would do it for each one which would be very annoying so the method i have implement is much quicker!
    EDIT: This request is finished, closing....
  9. Like
    Mr_Smartepants got a reaction from rosario in Windows 7 Toolkit News [IMPORTANT]   
    Whaaaaat? I thought you were going to barber college or be a plumber!
    Good luck mate!
  10. Like
    Mr_Smartepants got a reaction from nice_guy75 in Integration issue (title fixed)   
    More info here: http://tinyurl.com/3fzod9y
  11. Like
    Mr_Smartepants got a reaction from stsaerox in [Video] Windows 7 AIK/OPK deployment 101 (Updated)   
    I wrote some scripts to do exactly that!
    Here: http://forum.driverpacks.net/viewtopic.php?id=5199
  12. Like
    Mr_Smartepants got a reaction from NIM in The Linux advantage - Why Linux is the best OS   
    Looks like FUD can be used by both sides.
    I'm not a M$ fanboy. I use both Win7 & Linux. They're tools. I don't favor one brand of screwdriver for the same reasons.
    This article is so full of lies I don't know where to start.
    False. The only time a reboot is required is when the change affects the currently logged in user permissions or when a change to an in-use file is required. Linux acts in a similar way when applying patches. The changes are either applied immediately to files not in use or 'staged' for the next reboot for core system files.
    False. In my organization we've been mapping drive letters in the user space in our multi-user environments for at least the past 6 years. On 2k3 server/XP through 2k8 server/Vista configurations. All works perfectly fine.
    We always use the same 3 letters (of course others are available): O-Official, R-Restricted, S-Shared. All are available to each machine regardless of how many users are logged in at the same time.
    Damn, even my home network works fine mapping my two NAS shares to multiple users AT THE SAME TIME.
    Although I agree that hard-mapping A & B to a non-existent floppy drive is just plain stupid for a modern OS.
    Again false. No company "bets their future" on one technology. The phrase "all the eggs in one basket" comes to mind.
    I don't have time to pick out all the lies in this (old?) article but there are loads more. In fact, the whole article stinks like bullsh*t and is probably just troll-bait.
    Linux has one MAJOR downfall that WILL prevent it from going mainstream (if it hasn't killed it's chances yet). And that is OS fragmentation. (Android is just beginning to see this affect)
    If you install an app written for "MacOS" or "Windows", it will work on that platform.
    Try doing that for Linux and be prepared to answer way more questions than you should need to.
    1) what distro?
    2) what architecture?
    3) what package type?
    4) what package manager?
    etc.
    If Linux is to succeed, then the core upstream vendors (RedHat, Debian, Gentoo, Slackware, etc.) need to get together and UNIFY the application installer spec. I shouldn't have to care if an app is distributed as a .deb, .rpm, .tar.gz, or any other package types. Once the core vendors step in line, the rest of the downstream distros will also.
    I should just be able to download, click, and run.
    Until that happens, Linux will ultimately fail on the desktop.
  13. Like
    Mr_Smartepants got a reaction from NIM in Interesting prolem with ATi 9600   
    Newer does not always mean better.
    If the older driver works, stick with it.
  14. Like
    Mr_Smartepants got a reaction from dougiefresh in XPtsp GUI v3.0.0.26 - February 27, 2012   
    Sorry, got one more bug for you with 2.0.1.0.
    %source%\setup.exe is corrupted. Generic icon and doubleclicking setup.exe gives a permission error even when logged in as admin. Also setup.ini is missing.
  15. Like
    Mr_Smartepants got a reaction from Th5Mupp5t in Need some help with Server 2003 R2   
    Sounds like you are looking for PXE boot capability.
    M$ technet has an article on it here:
    http://technet.microsoft.com/en-us/library/cc722358%28WS.10%29.aspx
    I've never done it, but it seems easy enough.
  16. Like
    Mr_Smartepants got a reaction from NIM in [REQ] Search filter for language   
    I have a request. I'm not sure if it's possible with this new forum software.
    I'd like to have an option in the user's profile to flag "Search results from *** language sections only". This would be helpful for those who are monolingual.
    IE. If a English user clicks "View new content" and is presented with a list of 20 results, more than half are going to be from the Italian/Turkish sections (but with English titles).
    There's no indication (sometimes) what international section those threads are coming from. Very confusing for some.
    Can we make that more visible? Or offer the option to filter out those results?
    I don't mean this as a fault against our international visitors, but I can only see this option as a benefit. And it'd be an option, not default.
    I like to scan the international areas every now and then to see if I can help (Google translator is a help), but there are times when I wish I'd only get the search results I want.
    Possible?
×
×
  • Create New...