Jump to content

tazmaniandevil

Member
  • Posts

    29
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by tazmaniandevil

  1. Try disabling USB boot in the bios. Text mode seeks bootable drives, and may be trying to interrogate other usb devices.
  2. OK here's the scenario. We currently deploy XP via RIS using a cutom 'universal' RISETUP type build integrated with all updates, driverpacks etc. We are soon to be forced to "upgrade" to WDS when S2K3 SP2 is applied to our servers. From all the MS documentation I can find, WDS can only deploy RIPREP XP builds which are hardware dependent. This is why I have spent the last three years developing our current RIS deployment strategy - to avould hardware dependent installs. I can launch the xp cd setup from within PE, and build the PC quite happily. This however does not allow joining the machine to the correct OU within AD as we currently do via the .osc screens. Does anyone know how to launch the xp setup from within PE using an unattend.xml file to automate the install and join the domain properly?
  3. Hi I had a very similar experience with one of my machines some time ago. The build from cd was fine, no errors, but riprep image would give errors all over the place. Mine turned out to be a memory issue. One of the DIMMs was faulty. Replaced it and all was well. My other question would be, which service pack level is your flat cd install? Do you install a service pack as one of the updates? If so you need to slipstream the service pack into your flat cd install and re-create the reference machine, then riprep again. RIS doesn't like different service pack levels on standard and riprep sources. Taz
  4. midiboy Most new onboard nic's WILL pxe boot quite happily. The problem is that RIS won't recognise the text mode driver. What you need to do is either find a suitable text mode driver, or modify the oem driver to allow RIS to recognise it. This driver should be copied to the i386 folder of your RIS setup. You should read Intel information on this. Most other nic's are a variation of this. You should see the Broadcom information on how to modify the driver .inf file. This is also the same for all other nic's have fun... Taz
×
×
  • Create New...