Jump to content

jamesagmoore

Member
  • Posts

    43
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by jamesagmoore

  1. I use a cut down version of WinRE. By cut down I mean simply using the WinPE image which boots to the command prompt without the recovery programs.

    You have to download WinPE from the BDD or from the standalone WinPE package.

    Copy the .WIM file and boot.sdi into a \WinRE\ directory on the HDD of your choice. Edit the script below with your settings.

    When you boot Vista, press F8 as it boots. If everything has gone well there will be "Repair your installation" as the first option.

    set drive=D:
    set file=winre.wim

    set RAMDISK_OPTIONS={ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
    set WINPE_GUID={572bcd56-ffa7-11d9-aae0-0007e994107d}

    bcdedit -create %RAMDISK_OPTIONS% -d "Ramdisk Device Options" -device
    bcdedit -set %RAMDISK_OPTIONS% ramdisksdidevice partition=%drive%
    bcdedit -set %RAMDISK_OPTIONS% ramdisksdipath \WinRE\boot.sdi

    bcdedit -create %WINPE_GUID% -d "Windows Recovery Environment" -application OSLOADER
    bcdedit -set %WINPE_GUID% device ramdisk=[%drive%]\WinRE\%file%,%RAMDISK_OPTIONS%
    bcdedit -set %WINPE_GUID% path \windows\system32\boot\winload.exe
    bcdedit -set %WINPE_GUID% osdevice ramdisk=[%drive%]\WinRE\%file%,%RAMDISK_OPTIONS%
    bcdedit -set %WINPE_GUID% systemroot \windows
    bcdedit -set %WINPE_GUID% detecthal yes
    bcdedit -set %WINPE_GUID% nx optin
    bcdedit -set %WINPE_GUID% winpe yes

    bcdedit.exe -set %WINPE_GUID% custom:46000010 yes
    bcdedit.exe -set {default} recoverysequence %WINPE_GUID%
    bcdedit.exe -set {default} recoveryenabled yes
    pause

  2. intel p4 2,6HT, msi i865pe neo-2, 2x256mb (DDR 400 mhz)

    i have a partition prepared.. i have free space on C: for the installation files, but why is it hammering my cpu every time i enter the key or selecting vista ultimate manually.. i even tried entering invalid keys - 100% cpu for a couple of seconds and a "wrong key" message.. what i tried so far:

    In my experience you can install with no key.

    You will get a warning and are then asked which edition of vista to install.

    Of course entry of a key will be necessary before activating when the 14 day period expires.

  3. I am running Vista RC1 on an ASUS A8N SLI Premium Raid 0 array by using the nvidia beta 2 drivers.

    http://www.nzone.com/object/nzone_download...betadriver.html

    The nvidia drivers released a few days ago do not work.

    The way to do it is like so:

    1) Install a basic Windows XP on your c: and boot into it

    2) Copy the sources directory of vista into d:\sources

    3) run vista's setup.exe

    4) When it asks for the drive to install, select load drivers and browse to the nvidia beta 2 drivers.

    5) There should be 4 devices in the list. Select ALL the devices in the list

    6) continue with the installation

    the original install will be moved into windows.old and you can delete it.

  4. My version of IE7 beta 3 fails integration because there is no -q switch. In addition there is no /integrate switch. This is the genuine version from MS's site.

    This is the text in IE7beta3_main.log:

    00:00.000: ====================================================================
    00:00.000: Started: 2006/08/06 (Y/M/D) 13:58:54.515 (local)
    00:00.000: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
    00:00.000: Command line: e:\c3fcef72bdf640945391a839\update\iesetup.exe -q /integrate:"D:\Win\mrmnvda4"
    00:00.000: ERROR: Invalid command line argument: '-q'
    00:00.000: INFO: Message to User: Run iesetup.exe /? for usage.

    Is there a different version that can be integrated? Thanks

  5. I am trying this from a batch called during Windows XP installation, via cmdlines.txt. I get the error in the event logs:

    Product: Microsoft .NET Framework 2.0 -- Error 25007.Error occurred while initializing fusion. Setup could not load fusion with LoadLibraryShim(). Error: The handle is invalid.

    Anyone else installing donnet 2 from cmdlines.txt?

  6. A BIN file contains the data of each sector plus the error correcting codes that are attached to each sector.

    An ISO contains only the data of the sectors.

    When an ISO is burned the ECC is recalculated and added to the CD.

    Because the ECC is included in a BIN it is possible to verify the integrity. That is not possible with an ISO. The decision on which format to use should be based on the likelihood of it being corrupted.

  7. Hello

    I've created a script to change drive letters based on the volume label (from My Computer) or the CD rom device name (which can be seen in device manager). It uses WMI to query to CD drive descriptions and partition labels.

    So for example I can setup the PC like this:

    cscript SetDriveLetterFromDescription.vbs //Nologo "HL-DT-ST DVD-ROM GDR8163B" "Y:"
    cscript SetDriveLetterFromDescription.vbs //Nologo "HL-DT-ST DVDRAM GSA-4163B" "Z:"
    cscript SetDriveLetterFromDescription.vbs //Nologo "Data" "D:"
    cscript SetDriveLetterFromDescription.vbs //Nologo "512MB DISK" "U:"
    cscript SetDriveLetterFromDescription.vbs //Nologo "80Gb USB2 Disk" "P:"

    following a reboot the drive letters in explorer will change.

    Shortcomings:

    1) No support for multiple installations of same type of CDROM or same volume name in a single PC

    2) No neat way of handling removable media (eg, compact flash)

    3) No protection from people breaking their Windows install by reassigning the boot or system drive

    Save the below code in a file named "SetDriveLetterFromDescription.vbs". Take care before running it.

    Const ComputerName = "."
    Const HKLM = &H80000002
    Set wmiServices  = GetObject ( "winmgmts:{impersonationLevel=Impersonate}!//" & ComputerName)

    if WScript.Arguments.count <> 2 then
    WScript.Echo "Usage: " & WScript.ScriptName & " Description DriveLetter"
    WScript.Quit 1
    end if

    SetDriveLetterFromDescription WScript.Arguments(0), WScript.Arguments(1)

    function SetDriveLetterFromDescription(strDescription,strNewLetter)

    currentdriveletter = GetDriveLetterFromDescription(strDescription)

    if currentdriveletter = vbNullString then
     strMessage = " Unknown description"
    elseif UCase(currentdriveletter)=UCase(strNewLetter) then
     strMessage = " Already set"
    elseif ChangeDrvLetter(currentdriveletter,strNewLetter) then
     strMessage = " OK"
    else
     strMessage = " Failed"
    end if

    WScript.Echo strDescription & " " & currentdriveletter & " -> " & strNewLetter & strMessage

    end function


    function GetDriveLetterFromDescription(strDescription)

    Set wmiDiskDrives = wmiServices.ExecQuery("SELECT Caption,Description,DeviceID,Drive FROM Win32_CDROMDrive WHERE Caption =""" & strDescription & """")

    For Each wmiDiskDrive In wmiDiskDrives
     GetDriveLetterFromDescription = wmiDiskDrive.Drive
     exit function
    next

    Set wmiDiskDrives =  wmiServices.ExecQuery ( "SELECT Caption FROM Win32_LogicalDisk WHERE VolumeName =""" & strDescription & """")

    For Each wmiDiskDrive In wmiDiskDrives
     GetDriveLetterFromDescription = wmiDiskDrive.Caption
     exit function
    next

    end function

    Function ChangeDrvLetter(sSourceDrive, sTargetDrive)
    bOK = True  ' Init value
    Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & ComputerName & "\root\default:StdRegProv")

    sKeyPath = "SYSTEM\MountedDevices"
    sSrc = "\DosDevices\" & UCase(sSourceDrive)

    iRC = oReg.GetBinaryValue(HKLM, sKeyPath, sSrc, sValue)

    If iRC = 0 Then
     sTrg = "\DosDevices\" & UCase(sTargetDrive)

     oReg.DeleteValue HKLM, sKeyPath, sSrc
     iRC = oReg.SetBinaryValue(HKLM, sKeyPath, sTrg, sValue)

     If iRC <> 0 Then
     bOK = False
     End If
    Else
     bOK = False
    End If
    ChangeDrvLetter = bOK
    End Function

  8. Disabling Windows File Protection Permanently.

    I made an hacked SFC_OS.DLL for disabling WFP without any registry settings.

    You can replace the file from your Windows XP SP2 source files (don't forget to compress with MAKECAB.EXE) or follow this guide if you have already installed XP.

    Does anyone know where the sfc_os.dll file with no registry check went? It is not possible to download it any more

    Thanks

  9. I think it is using US because the early stages of setup default to that.

    Try something like this but customised for your keyboard:

    [Unattended]
       CrashDumpSetting=0
       Repartition = No
       UnattendMode=FullUnattended
       OemSkipEula=Yes
       OemPreinstall=Yes
       TargetPath=\WINDOWS
       UnattendSwitch=Yes
       KeyboardLayout="United Kingdom"
       WaitForReboot = No
       OEMPnPDriversPath = "drivers\REALTEK\audio;drivers\ATI;drivers\IntelINF;drivers\LINKSYS;drivers\Logitech\msgr"
       DriverSigningPolicy = Ignore
       runoobe=no
       OemFilesPath=d:\win\$OEM$

  10. Only this guy claims to have access to the final build:

    YAAAAYYYYYYY :)

    RTM finally!

    It will still be some time before the you can download it from a Public MS server. But we aren't the general public, are we?

    I'll check with MS (if its okay with them) and post the final build's download link.

×
×
  • Create New...