Jump to content

kyor

Member
  • Posts

    113
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by kyor

  1. It doesn't matter whether you use the diskpart format command or the format.com.

    Both methods produce this error.

    Greetings

    kyor

    After chkdsk c: /f i become sometimes a new error message

    Fehler in Volumebitmap werden berichtigt.

    Windows hat Probleme im Dateisystem festgestellt.

    Führen Sie CHKDSK mit der Option /F (Fehlerbehebung) aus, um die Probleme zu

    beheben.

    Translate form german to englisch

    Correcting errors in Volumebitmap.

    Windows found Problems in Filesystem.

    Run CHKDSK/f to correct the error.

  2. I am the creator of the Thread "Installing Winxp via winnt32 under Winpe v2.0 (Vista PE)" and i

    always use this workaround. Otherwise i can't install Windows XP :wacko:

    I bet when you create and format your partition with winpe 2.0 (diskpart) and use

    after that imagex, you have this problem, too.

    Greetings

    kyor

  3. @ ubernerd

    Imagex is fine but when you apply a Vista image to 40 machines, you can wait a long time.

    Ghost can multicast.

    Or have i overlook something ?

    Vista content with software 9 GB

    Doing it with ghost multicast 9 GB

    Doing it with imagex 9 GB * 40 = 360 GB

    To transfer 360 GB over network takes a long time

  4. I you do not want to use Nero Scout, do the unattended installation of Nero

    after that use the following command:

    Regedit /s DisableNeroScout.reg

    Contents of DisableNeroScout.reg

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Ahead\Nero Home\MediaLibrary]
    "DisableNeroScout"=dword:00000001

    Greetings kyor

  5. @toto51

    Thanks toto that's it :thumbup

    I tried it on Windows XP and it works great when i install directx before i install Nero silently :rolleyes:

    You can also use the Directx package that is in Nero.

    It's under NeroDemo\Redist\DirectX

    So i can do

    NeroDemo\Redist\DirectX\dxsetup.exe /silent

    and

    SetupX.exe /qb! /NORESTART RebootYesNo="No" NERO_SCOUT="FALSE" serialnum_userval="serialnumber" AgreeToLicense="Yes" EULA_AGREEMENT=1

    and then it works under WinXP

    I have now to test it with vista

    Greeting

    kyor

  6. Hi all

    After installing Windows XP via winnt32 i get a chkdsk error when i execute

    chkdsk c: under Windows XP.

    I get the same error when I try do deploy a sysprep’ed based XP

    Image via Imagex. The XP image works fine on the master PC without error,

    until I deploy it to other PC’s via Imagex and WINPE2.0.

    When i deploy the same WIM Image via WinPE2005 it works fine.

    i have attached a picture with the error.

    Anyone know a fix for that ?

    I think it has to do with the new format utillity in PE2.0 :realmad:

    Anyone knows if a 3rd party format utillity exist for WinPE ?

    I have tried execute the PE2005 format utillity under WinPE2. But i

    can't start it.

    Greetings

    kyor

    post-33407-1170168235_thumb.jpg

  7. @knockz

    It's a workaround that Microsoft sends me via email. It does not exist a KB article as i know.

    @Jazkal

    If you found a solution for imagex and w2k3, please post it here. My college have to handle

    with win2003.

    But do you really need bootsect on winpe 2005 ?

    I think i have tried imagex on winpe 2005 to install a sysprep Windows XP image without bootsect. It works in the beta version of imagex.

    have a great weekend :rolleyes:

    kyor

  8. ok i think here is the complete workaround to solve

    the installation issue with winnt32.exe

    do the following only for xp and win2003 installations.

    On vista you will get performance problems with raid controllers

    if you use the fixbootxp.reg

    1. run winpe 2.0

    2. regedit /s fixbootxp.reg (attached in this post)

    3. diskpart

    4. bootsect /nt52 c:

    5. start winnt32

    It works's for me. But i do additional test's :rolleyes:

    Greetings

    kyor

  9. It depends of what version of Winpe you use.

    If you use Winpe 1.x (OPK Kit from Windows 2003 Server or XP) you have to use the drvinst

    command

    For WinPE 2.0 you have to use the command line tool peimg /inf to integrate .inf-based drivers.

    See in the electronic documentation winpe.chm that is located onto your harddisk when you installed the OPK Tools

    kyor

×
×
  • Create New...