Hello all. I've looked into posts on this site, but none have solved my problem yet. I am trying to get a Panasonic CF-74 Toughbook to boot via 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". "My Computer" shows up as "%...%" so I'm pretty sure it's not being recognized. 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. Any help would be appreciated! Thanks. I'll be checking this post daily and responding until the problem is solved.
0 Comments   [ + ] Show Comments

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.

Answers

0
Hi Brad,
have you injected the drivers into the WinPE image?
If yes, tell us how you did it.
Regards, Nick
Answered 12/01/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
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!
Answered 12/03/2007 by: balakb
Senior Yellow Belt

Please log in to comment
0
This was my documentation for the process. Would this be sufficient to create a bootdisk that worked, or is there something else I need to do? I just started a packaging job and would like some professional advice from people who have actually dealt with a situation like this. This seemed a bit strange as well: When I contacted Panasonic, they said that I needed to use an external USB floppy drive OF A SPECIFIC MODEL NUMBER when loading the drivers. Imagine my surprise when they said it had to be a panasonic-made floppy drive. I think they're just pulling my chain on that one...it sounds pretty dubious, but still if there's something out there that would support this claim, I'd like to hear about it.
Answered 12/03/2007 by: balakb
Senior Yellow Belt

Please log in to comment
0
Whoops, sorry for all the back to back posts, but just remembered. Please ignore the comment about

"My Computer" shows up as "%...%" so I'm pretty sure it's not being recognized.

that I posted in the first chapter of this exciting story. It does that with all image jobs regardless of make/model/whatever. I just got excited and overlooked it.
Answered 12/03/2007 by: balakb
Senior Yellow Belt

Please log in to comment
0
Whoops, sorry for all the back to back posts, but just remembered.This forum allows you to edit your posts.
Answered 12/04/2007 by: VBScab
Red Belt

Please log in to comment
0
Thanks Scab. I'm not a big poster unless I run into something I truly do not understand. I'll edit accordingly from now on. Any ideas on how to fix this? Still an issue.
Answered 12/05/2007 by: balakb
Senior Yellow Belt

Please log in to comment
0
Sorry, no. I have zero experience with WinPE and this forum is concerned with software packaging (Windows Installer, MSI files and such). I'd imagine the Altiris forums would be a richer source of information and help.
Answered 12/05/2007 by: VBScab
Red Belt

Please log in to comment
0
Gotcha. I'll try to post this in an Altiris forum...like I said I'm not too familar with posting yet. Thanks for the help Scab.
Answered 12/10/2007 by: balakb
Senior Yellow Belt

Please log in to comment
0
Hi Brad,
don't think your driver injection process is adequate.
See: http://support.microsoft.com/kb/923834/en-us
For the necessary steps to inject a driver, go to step "h".
Hope this helps.
Regards, Nick
Answered 12/10/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity