Jump to content

Tribble

Member
 View Profile  See their activity

  • Posts

    87

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Germany

 Content Type 

Posts posted by Tribble

    Windows Setup is unable to find a system volume..

    in Windows Vista

    Posted

    Iam running into the same problem. Error msg is the same:

    Windows Setup is unable to find a system volume that meets its criteria for installation

    My config is:

    Booting WinPE from USB Stick, use setlw (http://www.911cd.net/forums//index.php?showtopic=24365) to make the usb stick fixxed drive Y. Diskpart the internal hdd and running the vista setup.exe from the thumb drive.

    From my investigation it looks like my usb stick is set as the active boot partition and the Vista installer needs to write the boot sector it, which it cant because the usb stick is a removeable drive.

    Any idea how I can get it to work?

    I boot up the winpe via:

    find --set-root --ignore-floppies /images/winpe.iso

    map --mem /images/winpe.iso (hd32)

    map --hook

    chainloader (hd32)

    boot

    0

    Post-Sysprep Errors hanging Setup

    in Unattended Windows Vista/Server 2008

    Posted · Edited by Tribble

    Ok, Ive just found out something interesting/funny to this case.

    As You can read here: http://blogs.technet.com/b/inside_osd/archive/2007/08/08/why-does-vista-end-up-on-the-d-drive.aspx the install.wim from the dvd was originally captured from a drive D - lmao. To get around this problem I could create 2 partition via diskpart, installing Vista on the 2nd one I guess?

    However I dont want to end up having 2 partitions and Vista installed on D drive. Does anybody know how I can use the original install.wim to get it working on one partition and on the C drive?

    0

    Post-Sysprep Errors hanging Setup

    in Unattended Windows Vista/Server 2008

    Posted · Edited by Tribble

    Hi guys,

    Iam running into a similar problem. What Iam doing is:

    Booting a Winpe 3.0 over network, acces my network share and try to deploy the original Vista wim from Microsoft. Everything goes fine, the image is deployed the target pc is booting fine.

    Unfortunately it always ends up with

    "The system registry contains invalid file paths. Installation cannot proceed. This system image was applied without guaranteeing that drive-letter assignments would match across computers."

    This is what I do:

    diskpart /s z:\diskpartcmd4.txt >nul

    ECHO **** APPLYING - Windows Vista Business 32-Bit - IMAGE ****

    ECHO.

    imagex.exe /apply Z:\images\VISTA_32_SP2.wim 1 C:

    bcdboot C:\windows /l de-DE /s C: >nul

    bootsect.exe /nt60 C: >nul

    copy Z:\Unattend.xml C:\windows\system32\sysprep >nul

    And my diskpart cmds:

    select disk 0

    clean

    create partition primary

    format fs=ntfs label="WINDOWS" quick

    assign letter c

    active

    exit

    As You can see there is only one primary and active partition, so this is not the problem.

    Does anybody have any idea what to do, to get around this problem? As I stated above, Iam using the original wim from a microsoft disc. Its working very well this way with Windows 7 and Windows 8 with the same configuration. However Vista is making these trouble. Maybe the Vista wim is not made to be distributed in this way?

    PS: In thought this problem maybe coming from a faulty Unattend.xml I removed that line for testing puposes with the same results.

    0

    Simple commands menu

    in Windows PE

    Posted

    Hi guys,

    iam looking for a very simple tool, to create a menu to choose via cursor/enter from. Something very simple in the design of menu.c32 from Syslinux:

    http://www.syslinux.org/wiki/index.php/Screenshots

    or like the boot menu in xp.

    I want to use it for my batch file, where the user choose which OS should be installed (which is running in WinPE!). Actually Iam using the SET /P solution within the batch file. But I want to use the cursor keys to choose from a menu and simple hit enter. Current choosen line should be colored, like in menu.c32

    Any ideas?

    0

    Strange problem with FirstLogonCommand from Shared Network Folder

    in Unattended Windows 7/Server 2008R2

    Posted

    Thanks for ur reply, uid0.

    I started thinking about the network problem either. So I decided to mount the shared network folder with the persistent:YES option. Now during the setup of install.cmd I opened up an explorer window and watched the mounted drive. Whoala, it was disconneced. After this I started thinking how this could happen and had several ideas:

    - during the installation of install.cmd LAN-Drivers are updated

    - during the installation of install.cmd chipset drivers are updated

    Both can or will lead to disconnect the mounted network folder. The only strange thing left is, that I was getting the error after doing the windows activation via install.cmd. I dont think the network drive gets lost, when activating windows. Anyway I have setup a sleep in the install.cmd right after installing the chipset driver and the lan drivers. Now I did another install and whoala, its working. Will give it another ~5 installations with different machines, just to make sure its indeed working.

    Alternatively, you could try copying anything you need from z: to %temp% before running dpinst, because I still reckon that's bouncing your network.

    This is no option, since there are several gigs to copy.. big waste of time.

    0

    Strange problem with FirstLogonCommand from Shared Network Folder

    in Unattended Windows 7/Server 2008R2

    Posted · Edited by Tribble

    Is it losing network access temporarily? You could test for e.g. if exist z:\nul then sleep for a few seconds and retry.

    I guess if dpinst swaps your network drivers then that would take it down for a bit.

    Its not losing the network access. I have already tried that with linking the network shared and then do a sleep for x seconds. But that doesnt make any difference.

    You should be using a .cmd extension for Windows 7!

    I have tried that and it doesnt make any difference.

    This is a good test but FirstLogonCommands doesn't use a command prompt (opened by a user) to process the command. You can try outputting your command to a file using the " > file.log" method to see what exactly isn't working.

    Can You tell the exactly command? I guess I need to add it to the AutoUnattend.xml?

    Have you tried using CMD /C instead of /K and see if that makes any difference?

    Yes, its not working either. With cmd /c switch the INSTALL.CMD does not even starts running. :( I have even tried to push the INSTALL.CMD with CALL and START, but this results in not executing it either.

    In the meanwhile I have rebuild the INSTALL.CMD (INSTALLATION.bat before) completely.

    The beginning looks like this now:

    @echo off
    ver | findstr /i "5\.1\." > nul
    IF %ERRORLEVEL% EQU 0 (
      if %PROCESSOR_ARCHITECTURE%==x86 (
        echo Installing Windows XP x86 Drivers..
        start /w %~d0%~p0TREIBER\XP_32\DPInst.exe /q
      )  
      if %PROCESSOR_ARCHITECTURE%==AMD64 (
        echo Installing Windows XP x64 Drivers..
        start /w %~d0%~p0TREIBER\XP_64\DPInst.exe /q
      )
    )
    ver | findstr /i "5\.2\." > nul
    IF %ERRORLEVEL% EQU 0 (
      if %PROCESSOR_ARCHITECTURE%==x86 (
        echo Installing Windows 2003 x86 Drivers..
        start /w %~d0%~p0TREIBER\2003_32\DPInst.exe /q
      )  
      if %PROCESSOR_ARCHITECTURE%==AMD64 (
        echo Installing Windows 2003 x64 Drivers..
        start /w %~d0%~p0TREIBER\2003_64\DPInst.exe /q
      )
    )
    ver | findstr /i "6\.0\." > nul
    IF %ERRORLEVEL% EQU 0 (
      if %PROCESSOR_ARCHITECTURE%==x86 (
        echo Installing Windows Vista x86 Drivers..
        start /w %~d0%~p0TREIBER\VISTA_32\DPInst.exe /q
      )  
      if %PROCESSOR_ARCHITECTURE%==AMD64 (
        echo Installing Windows Vista x64 Drivers..
        start /w %~d0%~p0TREIBER\VISTA_64\DPInst.exe /q
      )
      echo Windows wird aktiviert..
      cscript c:\windows\system32\slmgr.vbs /ato >nul
    )
    ver | findstr /i "6\.1\." > nul
    IF %ERRORLEVEL% EQU 0 (
      if %PROCESSOR_ARCHITECTURE%==x86 (
        echo Installing Windows 7 x86 Drivers
        start /w %~d0%~p0TREIBER\7_32\DPInst.exe /q
      )  
      if %PROCESSOR_ARCHITECTURE%==AMD64 (
        echo Installing Windows 7 x64 Drivers
        start /w %~d0%~p0TREIBER\7_64\DPInst.exe /q
      )
      echo Windows wird aktiviert..
      cscript c:\windows\system32\slmgr.vbs /ato
    )
    echo Notebook-Hersteller wird ermittelt..
    for /f "tokens=1,*" %%i in ('Systeminfo^|find "Systemhersteller"') do set "Systemhersteller=%%j"
    If "%Systemhersteller%"=="LENOVO" goto :ibmtools
    If "%Systemhersteller%"=="IBM" goto :ibmtools
    goto anderetools

    Im getting the same error message mentioned in the OP. It occurs right after doing the activation (cscript c:\windows\system32\slmgr.vbs /ato). The interesting thing is, that the "echo Notebook-Hersteller wird ermittelt.." is not even displayed on the screen before the error message, which is the right next command after the activation stuff. This is funny.. a lil bit.

    0

    Strange problem with FirstLogonCommand from Shared Network Folder

    in Unattended Windows 7/Server 2008R2

    Posted

    Hi,

    I have a very strange problem with unattended installation of Windows 7 32-bit. In the past I have used an usb stick to unattended install Windows and run a batch from the stick via FirstLogonCommands. Its working like a charme and tested 100 times.

    Now I have decided to switch from usb installation to network/pxe installation. Win7 32-bit-Installation is working fine, autounattended.xml is placed in "sources" folder and works like a charme.

    I use the following code to create a shared folder connection and automatically kick a batch file:

                            <FirstLogonCommands>
                                    <SynchronousCommand wcm:action="add">
                                            <Description>Network Share</Description>
                                            <CommandLine>net use z: \\SERVER\INSTALLATION /user:bleh 1000 /persistent:NO</CommandLine>
                                            <Order>1</Order>
                                            <RequiresUserInput>false</RequiresUserInput>
                                    </SynchronousCommand>
                                    <SynchronousCommand wcm:action="add">
                                            <Description>Post Setup Installation</Description>
                                            <CommandLine>cmd /k Z:\INSTALLATION.bat</CommandLine>
                                            <Order>2</Order>
                                            <RequiresUserInput>false</RequiresUserInput>
                                    </SynchronousCommand>
                            </FirstLogonCommands>

    The shared network folder is created. The INSTALLATION.bat starts up. No problem so far. But now comes the confusion. After the batch is starting and pushing the first commands I get the following error message (batch stops):

    Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen.

    means The system cannot open the device or file specified. It stops right after the "echo ..done!" line on executing the "goto act_ossel"

    Here is a snippet of my batch:

    @echo off

    REM Treiber installieren
    ver | findstr /i "5\.1\." > nul
    IF %ERRORLEVEL% EQU 0 goto ver_XP
    ver | findstr /i "6\.0\." > nul
    IF %ERRORLEVEL% EQU 0 goto ver_Vista
    ver | findstr /i "6\.1\." > nul
    IF %ERRORLEVEL% EQU 0 goto ver_Win7
    goto warn_and_exit

    :ver_Win7
    if %PROCESSOR_ARCHITECTURE%==x86 (
      echo Installing Windows 7 x86 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\7_32\DPInst.exe /q
      echo.
      echo ..done!
    ) else (
      echo Installing Windows 7 x64 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\7_64\DPInst.exe /q
      echo.
      echo ..done!
    )
    goto act_ossel

    :ver_Vista
    if %PROCESSOR_ARCHITECTURE%==x86 (
      echo Installing Windows Vista x86 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\VISTA_32\DPInst.exe /q
      echo.
      echo ..done!
    ) else (
      echo Installing Windows Vista x64 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\VISTA_64\DPInst.exe /q
      echo.
      echo ..done!
    )
    goto act_ossel

    :ver_XP
    if %PROCESSOR_ARCHITECTURE%==x86 (
      echo Installing Windows XP x86 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\XP_32\DPInst.exe /q
      echo.
      echo ..done!
    ) else (
      echo Installing Windows XP x64 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\XP_64\DPInst.exe /q
      echo.
      echo ..done!
    )
    goto act_ossel

    :act_ossel
    ver | findstr /i "5\.1\." > nul
    IF %ERRORLEVEL% EQU 0 goto manucheck
    ver | findstr /i "6\.0\." > nul
    IF %ERRORLEVEL% EQU 0 goto activate
    ver | findstr /i "6\.1\." > nul
    IF %ERRORLEVEL% EQU 0 goto activate


    :activate
    REM Aktivierung durchfuehren
    cscript c:\windows\system32\slmgr.vbs /ato
    echo.
    echo.
    echo Windows-Aktivierung durchgefuehrt!
    echo.
    echo.
    goto manucheck

    To find out what is wrong I changed the windows 7 part of the batch to:

    if %PROCESSOR_ARCHITECTURE%==x86 (
      echo Installing Windows 7 x86 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\7_32\DPInst.exe /q
      echo.
      echo ..done!
      goto act_ossel
    ) else (
      echo Installing Windows 7 x64 drivers in silent mode now...
      start /w %~d0%~p0TREIBER\7_64\DPInst.exe /q
      echo.
      echo ..done!
      goto act_ossel
    )

    This time the command prompt is pulling two times the error message

    Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen.
    . So Im pretty sure its because of the goto act_ossel. Of course I have tried changing it to "goto :act_ossel" and even some simpler name for the variable like active1 instead of act_ossel. I still get this error message.

    But thats not all: As I said already the batch is working flawless when installing from usb stick, no error messages at all. After getting the

    Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen.
    error message Im sitting at the command prompt as I said. Now if I start the batch manually by just typing "Z:\INSTALLATION.bat" its working like a charme. WTF?

    Ok, so in short words:

    Unattended installation with a batch file is working like a charme from usb key, but on network installation the batch file stops after some lines because of a goto problem. Starting the batch file manually again and its working.

    I have even tried to start another batch file from within the first batch file, making the system I think that im starting it by my fingers and not automatically but I get the same error.

    Anybody got a clue what could be wrong in this strange case?

    0

    CDIMAGE v2.52

    in Multi-Boot CD/DVDs

    Posted

    And i dont really think Cyberain is still working on his GUI Version, since Beta 3 is old as hell already. I mean not that there is a reason to work on it, b/c there dont seems to be any problems with the beta 3.

    But im interested in CDImage v2.52, too :)

    0

    Office Shrinker [reduce source of o2k3/xp/2k]

    in Microsoft Office

    Posted

    Office 2003 SP1 is out.

    Anybody got a script or a gui like nuhis nLite to slipstream the SP1 into the Office CD? Slipstreaming Office SPs is not that easy like with Windows SPs. The Command Line is much longer and there are 3 command lines at least to update the Office CD Source.

    But there are some good tutorials like here to get into it, so dont worry. Would just be interesting if anybody was diligent and code some easy using gui tool for slipstreaming :)

    0
×
×
  • Create New...