Hello all. I've looked into posts on this site and was advised to post in an Altiris forum...but none exist. Here's the closest thing I could think of. I am trying to get a Panasonic CF-74 Toughbook to boot via a WinPE cd to create an image file from the HD via Altiris. After the Altiris environment boots up, and rdeploy pops up, I am able to select the location that I want the image to go to, but when I click on "next" to start the creation process, in the lower left corner of the Rapideploy console, it says "disk not found". It's an 82801 chipset. I've looked through many faq's and haven't gotten a clear solution as to how to have rdeploy detect the HD-too many different solutions...and none work. Here's the steps I took:

Bootdisk creation for Altiris Environment for Panasonic CF-74 Toughbook.

1. Took files from working WINPE Altiris BootDisk and copied all contents (to include hidden files and folders) to C:\ BasediscCF74 folder (created manually).

2. Copied all contents of C:\BasediscCF74 folder to c:\UpdateddiscCF74 (created manually).

3. Created C:\UpdateddiscCF74\I386\System32\DISK Drivers\iaahci (to hold driver files for the CF74 mass storage controller).

4. Copied all driver files from floppy disk (made from downloaded and extracted zip file f6fd_74_3_d070637-located @ panasonic's support website) to C:\UpdateddiscCF74\I386\System32\DISK DRIVERS\iaahci. 8 files included: iastor.sys, license.txt, readme.txt, txtsetup.oem, iaahci.cat, iastor.cat, iastor,inf, iaahci.inf.

5. Opened txtsetup.oem (in iaahci folder) and changed the following:

[Defaults] to [Defaults]
Scsi=iastor_ich8m to scsi=iaahci_ich8m

This was done to reference the correct driver (as listed in Computer Management underneath IDE controller icon as current driver). This changed the default driver referenced from ICH8m-E to the correct ICH8m-e/m.

6. Opened C:\UpdateddiscCF74\I386\System32\winpeoem.sif to identify the new driver location. Changes made: Added IAAHCI in list of folders referenced in OEM DriverDirs under [OEM Driver Params]. This added the IAAHCI folder to the list of folders recognized by winpeoem.sif. It points out the correct location of the new ICH8m-e/m driver.

7. Burned bootable ISO from this info and still didn't work. Argh!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity



I'm relatively new to WinPE myself and I'm not using the Altiris to create my images. A couple of things.

Can you see you local hard drive within WinPE before you enter the Altiris program (if that's possible)?

What happens if you create your own WinPE boot disk...can you see the C: drive?

Have you tried adding the drivers into your PE image usign the "pemig.exe /inf=...." command?

And finally, this may or may not be related I had a problem where WinPE could see the hard drive, but after WinPE it couldn't. Read this article......... http://support.microsoft.com/?id=931760

The WinPE.chm may help you out.
Answered 12/10/2007 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
Tried the help article. No help there. All local hard drives when created with our base WinPE image are seen as "%my computer%", even when the disk works, so that's not an issue for me. I'm not familiar with the "pemig.exe /inf=" command. Any more info on that (purpose, employment, switches)? Thanks for the reply. We're currently waiting on a Panasonic-approved USB floppy drive (they said it was necessary to load the appropriate drivers)...which I think is a load of c*** but we're trying it anyway. Looking forward to hearing more on that pemig.exe command. Thanks.
Answered 12/10/2007 by: balakb
Senior Yellow Belt

Please log in to comment
The WinPE.chm can be found in the WAIK from Microsoft. I found it much more helpful that anything else I found on the web. that peming.exe command basically installs your driver and copies the relevant files into the correct location within the WinPE image.

I hope it works out for you.

Add a Device Driver to an Offline Windows PE Image

[/align]The following procedure demonstrates how to use the PEImg tool to add a device driver (.inf) to an offline Windows PE image. Before you can run any PEImg command, you must first apply or mount the Windows PE image by using ImageX. Windows PE provides a base image (Winpe.wim) that you can customize. For an example of how to build custom Windows PE images, see Windows PE Walkthroughs.
To add a device driver to an offline Windows PE image

  • Apply the base image (Winpe.wim) by using ImageX to a local Windows PE directory. For example:

    imagex /apply WinPE.wim 1 c:\winpe_x86\mount\[/align]-OR-

    imagex /mountrw WinPE.wim 1 c:\winpe_x86\mount\[/align]
  • Add the .inf file to the base image by using the peimg /inf command. For example:

    peimg /inf=<path> c:\winpe_x86\mount\Windows[/align]where <path> is the location of the .inf file.
  • Repeat steps 1 and 2 for each additional device driver.

    When you finish customizing the image, prepare the image for deployment by using the peimg /prep command.

    After you prepare the image, you can burn the image to the designated media. First, recapture or commit the local Windows PE directory into a .wim file by using ImageX, create an .iso file by using one of the provided tools, and then burn the .iso file to the appropriate media.[/align][/align][/align]
  • Answered 12/10/2007 by: michaelnowell
    Second Degree Blue Belt

    Please log in to comment
    Very thorough! I'll give it a shot hopefully sometime this week and let you know. Much appreciated.
    Answered 12/10/2007 by: balakb
    Senior Yellow Belt

    Please log in to comment