Jump to content

laddanator

Members

  • Joined

  • Last visited

View Profile Find content

Posts posted by laddanator

    ·

    Edited by laddanator

    Having some issues with the new addon. I have tried both the nlite and RVMI version. I use the previous addon for years with no issue and I am integrating the same way as I did the older one so maybe that has change also?

    1. I am using an untouched authentic XP Pro SP3 source

    2. Using nlite to slipstrem addon

    3. Using only

    CODYQX4_OnePiece_Microsoft.NET_Framework_v1.0.3705_True_AddOn-V1.2

    OnePiece_Windows_Media_Player_11_True_AddOn_v2.5.0_ENU_E88D736A2C0648113B3D077BD5DF80E3

    OnePiece_Microsoft.NET_Framework_v1.1.4322.2490_True_AddOn_ENU_FD5D0737325BE429DA5A10310F232F82

    As I have always before. No other addon or update pack and this is what I am getting

    No IE at all

    noie.png

    Uploaded with ImageShack.us

    And in system properties It says Media Center Edition but nothing of MC loaded during install

    notpro.png

    Uploaded with ImageShack.us

    And as you can see, normal XP Pro background and not MCE

    notmce.png

    Uploaded with ImageShack.us

    I must be doing something wrong?

    UPDATE

    Just saw this, so I will try it in this order

    Fortunately this has been fixed in the latest build of W7T - just choose the FULL option when you decide to integrate the unattended.xml file through WIM Manager. :)

    Does this method inject unattend into the mounted wim? If so this method is not practical for me as I only update my Win7 every three months or 4 times a year but I seem to change my unattend every two weeks and with my method above I dont have to mount the wim eveytime I change my unattend becasue as long as my paths and files keep the same name, mysetup.cmd andwimpeshi.ini will always look for my install wim and my unattend

    ·

    Edited by laddanator

    This works as well and you can put Unattended.xml on root of any USB HDD or USB Stick

    Make a command file and call it mysetup.cmd and put this in it

    @echo off
    SET Path=sources
    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:\%Path%\install.wim set DVDdrive=%%I:
    If NOT "%DVDDrive%"=="" echo Found Install.wim at %DVDdrive%\%Path%\install.wim
    IF "%DVDdrive%"=="" (
    echo ERROR - COULD NOT FIND INSTALL.WIM in %Path% folder!
    pause
    pause
    goto :EOF
    )
    if exist %DVDdrive%\unattend.xml SET UN=/unattend:%DVDdrive%\unattend.xml
    if exist %DVDdrive%OEM\nul SET OEM=/m:%DVDdrive%\OEM

    X:\setup.exe /installfrom:%DVDdrive%\install.wim  %OEM% %UN%
    goto :Finish

    :Finish
    wpeutil reboot
    pause

    Mount boot.wim 2 and paste the mysetup.cmd in the Windows\system32 folder along with winpeshl.ini

    Put this in your winpeshl.ini

    [LaunchApps]
    startnet.cmd
    mysetup.cmd

    I know either way you have to mount boot.wim 2 to copy .xml file but I change the unattended.xml allot and if you copy the two files above into the wim one time, never has to be changed again and I dont have to mount my boot.wim twice a month to change my unattended.xml file

    Ummm maybe because MOST home users DO NOT use any of the features in Pro?

    Thus allowing MS to offer a cheaper home friendly version.

    Yes totally with you there...should have said the deployment options. I know the diff between Home and Pro. Kinda sucks the Mini-Setup option was left out of Home.

    AFAIK that feature\features were never implemented in XP Home.

    I never understood why MS treated XP Home like the red head stepchild and Pro got all the goods. I was reading you could use a Winbom.ini to automate the process but not sure how to make one.

    Posted

    XP Home does not use Mini-Setup option and the sysprep.inf will not load the unattended stuff. Pro works fine. Been a long time since I used sysprep for Home. How do you unattend the process for Home? oobeinfo.ini? Need the product key to be entered automatically.

    ·

    Edited by laddanator

    @laddanator, why don't you send IcemanND a PM and post back here if you find out anything

    Will do

    I got the making of the wim down pat and I can install the wim through Minixp(once in MiniXP its pretty much point and click) with GImagex to the pre-formated C drive. MiniXP uses a wim but somehow a XP.bin file extracts the wim and its bootable. :g:

    Thanks mate, she eats enormous amounts of milk, highly unusual for a baby less than a week old

    Chiming in late I know but I have a 3 month old and he looks 6 or 7 months. He weighs 18 pounds at 3 months already! He drinks tons of milk! He is a breast feed boy. Lucky feller! :)

    Posted

    I got a question. I know how to sysprep. I know how to capture an XP image with imageX and I can restore that captured image with imageX no problem from WinPE. My question is, is there anyway to make the XP.wim bootable like Vista and Win7? I know that Vista and Win7 use boot.wim to actually install the install.wim but will bootmgr and rename the XP.wim to install.wim maybe do the same thing?

    ·

    Edited by laddanator

    rick is around. I'd send him a PM in case he's just missed this thread.

    Cheers and Regards

    Thanks bphlpt

    . Not sure how to really describe the issue in detail. If I slipstream updates to a clean Vista install.wim between each setup screen, it locks up for 2 mins. When you finally get to format the hard drive you want to install to, Vista loads fine. Even on the format hard drive screen every button you click on to pick the drive and to delete the partition or to format hard drive locks up for 2 mins in between each click. I have used package manger to slipstream official updates. I have used DISM to slipstream official updates and the new Window 7 tool 1.30 beta to slipstream official updates, all with the same results