Tribble

Member
  • Content count

    87
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tribble

  1. Can You update the tool to support the new Avira Free Antivirus 2013 ?
  2. Iam running into the same problem. Error msg is the same: 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:
  3. 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?
  4. 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 This is what I do: And my diskpart cmds: 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.
  5. 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?
  6. 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. This is no option, since there are several gigs to copy.. big waste of time.
  7. Ok, command back. Its not working. It was working exactly one time now. with start /wait. After I tried with start only (no wait), it wasnt working. Changing back to start /wait doesnt made it working either (I did some small changes to the batch (primary echo stuff), which Iam trying to revert now..
  8. OMG, its working now! The magic code is cmd /C start /wait Z:\INSTALL.cmd Anybody knows the technical background now why this "special" code is needed for 'network shared folder batch installing' but not for usb installing, because I have no clue.
  9. 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. I have tried that and it doesnt make any difference. Can You tell the exactly command? I guess I need to add it to the AutoUnattend.xml? 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.
  10. 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): 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 . 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 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?
  11. Anybody got final sp3 patched sfc_os.dll ? Or better: a simple patcher like "Windows File Protection Switcher" for sp3? Windows File Protection Switcher is no longer working since SP3.
  12. Ok, so nobody got a smart, small and handy tool like WFPS to disable WFP??
  13. ... doesnt disable wfp in your current windows installation Little thinking won't harm you. You can disable SFC using nLite on XP SP3 and then extract necessary files from CD and copy it to current windows installation. Cheers Good one, but WFPS was easier
  14. ... doesnt disable wfp in your current windows installation
  15. Disabling it aint the problem, but doing it in a simple 2 or 3 mouse clicks step. Thats why im asking if anybody got a new WFPS or just a patch sfc_os.dll The attached files in that thread aint for RTM SP3 anyway. So does anybody have a simple solution yet for RTM SP3?