Jump to content

sysbuilder

Member
  • Posts

    45
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by sysbuilder

  1. Here's my Display section in my RISSTDRD.SIF. It's for a box which does have a 15.4 inch widescreen but it's a compatible resolution.

    [Display]

    BitsPerPel = 32

    XResolution = 1024

    YResolution = 768

    VRefresh = 60

    AutoConfirm = 1

    The autoconfirm string works as expected, but the default resolution still sits at 800x640, not the 1024x768.

    I just want 1024x768 as the initial default. The native resolution is 1280 x 800

    Thanks!

  2. desktop.ini is now opened automatically whenever a user logs into any box which has been RIS'd.

    These are image folders which were migrated from a previous iteration of RIS in our environment.

    This behavior did not occur in the last RIS server build.

    Can someone assist me? I've seen many posts to this scenario but nothing with an answer.

    Thanks so much!

    [.ShellClassInfo]

    LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787

  3. Dont use Rip Rep.

    the best way to automate the installtion of XP across multiple PC hardware with drivers etc integrated is to use RISSetup images & use autoimage, BTS Driver packs & Ryan VM update packs.

    I appreciate the reply, but you didn't answer my question. This sub forum is for MS technologies.

    The article is not adding up. It's all there in black and white, but the results do not appear.

    I am requesting help with Microsoft Remote Installation, not third party applications.

    So, can someone assist me in getting this to work? I can be available via IM.

    sysbuilder

  4. KB Article 314859 states the following:

    ------------------------------------------

    Note that if you choose to format the partition in the NTFS file system during setup, you cannot copy the newer OEM driver into the System32\Drivers folder after text-mode setup finishes. This is because the Windows Setup program formats the partition as NTFS before copying files. To work around this limitation, install Windows into a file allocation table (FAT) partition that is less than 2 GB in size or into a FAT32 partition that is less than 32 GB in size. Doing this allows access by using a startup disk from Microsoft Windows 98 or Microsoft Windows Millennium Edition (Me). After Windows is installed, use the following command to convert the FAT or FAT32 partition to NTFS:

    convert c: /fs:ntfs

    ------------------------------------------

    i really hope this isnt the case. I can't find this stated anywhere in other MS documentation..

    can someone please help.

  5. RIS appears so cut and dry, until you start applying these concepts in real world.

    I am attempting to integrate video drivers into a RIPREP image. I have completed the instructions listed in the technet article below.

    Adding Plug and Play Drivers to a RIS Image

    URL: http://207.46.196.114/WindowsServer/en/lib...43aeed1033.mspx

    However, it isn't working.

    When the image completes I am still looking at a system without the appropriate video drivers installed. The native resolution isn't there.

    I really like troubleshooting these issues, but I've checked and double checked these instructions and google'd countless other resources.

    It's just not coming together. Can someone assist me?

    Below this line is my riprep.sif file [unattended] section

    [unattended]

    OemPreinstall = Yes

    OemPnPDriversPath="Drivers\STOR;Drivers\VID"

    FileSystem = LeaveAlone

    ExtendOEMPartition = 0

    TargetPath = \WINDOWS

    OemSkipEula = yes

    InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

    LegacyNIC = 1

    Many thanks.

  6. I am customizing a base install of Windows XP SP2 in a RIS environment. I am doing this for a client system which utlilizes a SATA HDD interface. I have integrated the the SATA drivers appropriately. Remote Installation sees the drive and textmode and the guimode complete.

    It's when the system cycles power for the first time after setup completion (and over and over again) it gets to the splash screen and BSOD's on me with an error code of 0x0000007B. There is no description below the STOP error.

    I've researched the articles pointing to this error and I cannot think of other issues beside having something to do with the SATA device drivers. These are the latest drivers from the manufacturer as well.

    Can someone point me in the right direction? Thanks.

  7. Thanks--I've got some users who are adamant on moving back to XP; However, I want to ensure that they can then turn around and use the Vista OEM license later on.

    I know, I know. What's the point? Keeping them at bay and providing what they want.

    Any other places in here where I should place this post?

    Again, many thanks!

×
×
  • Create New...