DDU for CC3

How to prevent the Stone DDU from installing certain drivers on CC3

Scenario

There are situations where you may wish to prevent the DDU installing certain drivers, for example, a network controller driver for a specific motherboard. The DDU includes basic functionality to control which types of driver are deployed.

Instructions for Global Settings

Simply modify the DDUSet.INI file located in the DDU folder. This has a section for desktop and notebook drivers. Modify each section as required to turn off those driver types.

Instructions for Specific Models

Use this option to turn off drivers, again using the desktop and laptop sections as above, but this time for specific models.

Steps:

Ensure model specific settings are enabled. DDU 1.43 and newer has this enabled by default.
- Do this by making sure that the line enablemodelspecificsettings=1 is not commented out i.e. make sure it doesn't have a semi colon in front of it
Get the DDU name of the system. For example, the Stone / MSI H61M-P31/W8 (BOAMOT-443) has a DDU name of H61M-P31-W8-MS-7788.
- You can find this name in the C:\Stone\DRVINST.LOG file from a system that you have already built. Or alternatively, some of the packs contain Readme files which contain model names. Most hardware packs also have model descriptors, such as models.txt, which contains the list of the models that the pack supports.
Copy the DDUSet.INI file and paste the copy using the name of the model, for example H61M-P31-W8-MS-7788.INI
Modify the new INI file to turn off the drivers that you don't want installed
This new INI file now needs to go into the DDU folder, however it must follow the 8.3. character file limit for DOS, for example filename.txt. H61M-P31-W8-MS-7788.INI is too long; so this must be put into a ZIP file called Settings.ZIP
- DDU 1.44B and newer has a Settings.ZIP file by default. Simply drag the new INI file such as H61M-P31-W8-MS-7788.INI into Settings.ZIP

An example of the Settings.ZIP file for the motherboard above is attached. This Settings.ZIP file will turn off the network driver installation for the Stone / MSI H61M-P31/W8 (BOAMOT-443) model.

Note: The Stone DDU folder is located in: x:\RMNetwork\RMManage\RMRebuild\XPBuild\I386\$OEM$\$1\RM\HotFix\StoneDRV (where x is the drive that holds your RMNetwork folder)

Applies to:

Stone Computers DDU for CC3

Where can I find the latest DDU for CC3 Compatibility list?

The Stone Computers DDU for CC3 compatibility list is attached. This enables you to see which Stone models are supported by the DDU. (Last Updated 30/9/2013).

As of September 2013, no new models are planned to be supported due to the industry's withdrawal of support for Windows XP. The last models to be added were:

Lenovo Thinkpad Edge E530 (June 2013, available in Lenovo Notebook Pack 2).
MSI H61I-E35V2/W8-MS-7677 (September 2013, available in HWPack1).
Lenovo Thinkpad Edge E530C (November 2013, available in Lenovo Notebook Pack 2).

Note: The Compatibility list spreadsheet contains links to all of the DDU downloads and packages.

Applies to:

Desktop and laptop products compatible with the DDU for CC3 networks.

How to Solve No LAN Connectivity during Windows Setup on CC3

Problem

During the graphical (GUI) part of Windows Setup on CC3, the machine doesn't get a network Connection. Even though the DDU installs and appears to install the correct LAN driver, LAN connectivity is available until the machine is rebooted. Rebooting the machine during the build process breaks the build process from fully completing.

This problem occurs on machines manufactured in 2012 and 2013 that have a Realtek LAN Controller.

Cause

The cause is the Realtek LAN driver that is installed by CC3 early during installation. This driver is installed as it has a matching base device ID, however this driver does not properly support the Realtek LAN controller that is present, resulting in no functioning network connection. Because an old driver is installed, when the Stone DDU installs a new driver Windows XP automatically requests a restart before the new driver can take effect.

Resolution

This issue can be resolved by upgrading some of the native CC3 drivers to more modern versions. This can be done either by installing the latest CC3 Hardware support pack, or by using the Stone DDU Realtek NIC Hotfix utility. This utility upgrades the Realtek LAN drivers in the PC201LAN and c_Novatec1 subfolders in the build area:

x:\RMNetwork\RMManage\RMRebuild\XPBuild\FP\CUDRV\NET\c_Novatec1\
x:\RMNetwork\RMManage\RMRebuild\XPBuild\RMDRV\Net\PC201LAN\

Note: We recommend that you take a backup copy of these folders before using the upgrade utility, as this upgrade cannot be uninstalled.

Instructions

Connect to your build server via RDP or use the physical console.
Download the utility to your build server
Extract it to a folder
Run INSTALL.BAT. Follow the on screen instructions.

Applies to:

Stone desktop systems running CC3 which have a Realtek Network Controller such as the Stone / MSI H61M-P31/W8 (BOAMOT-443).

Where are the latest DDU downloads for CC3?

Main Downloads for Stone Computers 2010-2012 Desktops and Laptops

DDU for Desktops and Laptops (1.48 26/9/2013)

Download this file to your server and extract it to a folder.
On your build servers, run INSTALL.BAT to to a fresh install or UPGRADE.BAT to retain existing settings.

Note: If you dont need laptop support you can download and install a smaller package: DDU for Desktops Only (1.48 26/9/2013).

Bootdisk Drivers Download

Extract this download to your build disk to make it support all of the recent Stone desktop network adapters:
Boot Disk Download (updated 20/9/13 - file date June 2013).

DDU Manual

DDU Manual Download

Basic DDU Instructions

1/ Always ensure the machine is set to run in IDE mode. Set the machine's BIOS Advanced > Drive Controller Configuration mode from "AHCI" to "IDE".
2/ Generate a boot disk / pen drive as you would normally.
3/ Extract the Stone bootdisk NDIS2 driver files to this floppy / pen drive.
4/ Install the DDU onto your server.
5/ Boot the systems to be built using your modified boot disk/floppy. They should start the build process normally. When Windows XP has been installed, the DDU will kick in and install all of the drivers automatically.

For More Downloads

See the link to the CC3 compatibility list below.

Applies to:

Stone Computers Driver Deployment Utility (DDU) for CC3 Networks

I'm using the Stone DDU but CC3 packages aren't deploying during the build process. What can I do?

Problem

Packages may not deploy reliably on Stone systems on a CC3 network in some situations. This usually occurs when the system boots faster and completes loading all of the required services before the network adapter has had a chance to finish connecting to the network.

Cause

This is caused by the performance of the machine being far greater than was originally anticipated when Windows XP was designed. There are two sub-causes:

The NETLOGON service fails to connect to the domain server in time. This can cause problems with group policy updates and deploying packages at any time.
The AUTOEXNT service fails during the build process because the network connection is not ready when the service has started. This causes the deployment of packages during the build process to fail.

Resolution

DDU 1.42 and newer has enhanced fixes for both of these problems. The main fix is the AutoFIX component which is installed by the DDU and causes the AUTOEXNT service to succeed by adding a time delay. Install the latest DDU available to get access to the latest features.

The AutoFIX program is also available as a stand-alone utility however this cannot help with the package deployment during buildtime, whereas the AutoFIX utility included with the DDU can.

Installation Methods Available

Install the latest Stone DDU onto your build server. This can be configured to provide the AutoFix component even on unsupported motherboards.After installing the latest DDU, rebuild the problem system.
or, install the stand-alone AutoFIX utility directly onto machines which are already built, to enable them to download future packages more reliably.

Applies to:

Stone Computers DDU for CC3

How can I tell which version of the DDU or Packages that I have installed?

Showpack Utility

The DDU includes the Showpack utility to list the installed DDU version and packages.

To access this utility, first of all find where the DDU is installed using Windows Explorer. The DDU is normally installed in this location: X:\RMNetwork\RMManage\RMRebuild\XPBuild\I386\$OEM$\$1\RM\HotFix\StoneDRV - where X is the drive that holds your RMNetwork folder.

Then find the Showpack icon and doule click. This will list the DDU version and packages as below.

Applies to:

Stone Computers DDU for CC3

How to fix system hangs during the DOS text mode part of the CC3 Build Process

Problem

Some modern systems with Windows 8 compliant BIOSes may cause the text-mode Windows 98 portion of the build process to hang the system, typically just after the "Scanning for Drivers" stage.

Cause

This problem appears to be a caused by a combination of BIOS compatibility and levels of system performance that were not envisaged when the Windows 98 DOS mode environment was designed.

Resolution

Download and extract this ZIP file (last updated 21/9/13) to your build disk, to update the BUILD.CAB file. This replacement BUILD.CAB file will slow the build process, so this download should only be used where needed.

Note: This ZIP file does not contain the updated NDIS2 network drivers which are also needed when updating the build disk. These should also be downloaded and extracted to the build disk.

Applies to:

Windows 8 compliant Desktop and laptop systems building onto CC3 networks.

Stone / MSI H61M-P31/W8 Based System: BIOS stuck on code B2 after first stage of CC3 build process

Problem

Customers may experience problems on the Stone / MSI H61M-P31/W8 based systems during the CC3 build process. The symptoms are a B2 code being displayed on the BIOS POST screen. The system then does not boot any further.

Cause

The MSI H61M is primarily designed for Windows 8 and Windows 7. Whilst Stone have ensured that this platform is as compatible as possible with legacy operating systems such as Windows XP, the CC3 build process uses a Windows 98SE boot sector. The MSI H61M Windows 8 BIOS does not recognise the Windows 98SE boot sector as valid on hard drives. This causes the POST to fail to complete, displaying a B2 code on the screen.

Resolution

If affected by the issue, you will need to perform a BIOS flash downgrade on the system to version 3.0. However, to boot the system to run the downgrade, you may need to disconnect the hard drive first.

Downloads

There are several BIOS flashes available:

A downgrade to BIOS 3.0 (recommended for this issue)
(The latest BIOS for this motherboard are avaialble on the motherboard's BIOS download page).

Steps for Downgrade to BIOS version 3.0

Download the BIOS flash and extract it to a Windows 98SE bootable USB key (this will work with the existing BIOS as it is a removable drive)
Make sure the problem system is powered off.
Disconnect the serial ATA hard drive
Connect the BIOS update USB pen drive
Turn the system on and use the F11 key to obtain the boot menu (look for USB KEY in the menu).
Boot from the USB key and run the FLASH.BAT utility.

Note 1: To boot from a Windows 98SE USB pen drive, you may need to disable Secure Boot in the BIOS (Advanced > Secure Boot > Disabled). An alternative method of flashing is to go into the BIOS and to use the M-FLASH menu - this will negate the need for changing any other BIOS settings.

Note 2: This problem does not appear on the older G3 version of the motherboard, as this does not use the updated Windows 8 BIOS.

Applies to:

Stone desktops using the MSI H61M-P31/W8 (BOAMOT-443) motherboard being used on CC3.