geemail.email

Member
  • Content count

    46
  • Joined

  • Last visited

Community Reputation

0 Neutral

About geemail.email

  1. Hello everyone, I want to prompt for the Time Zone and Regional settings but no matter what I do, they default to the standard values. I also tried using this posting as an example and set the Time Zone within the Specialize pass, but it continues to use the default. Any ideas? Thanks in advance for any solutions\recommendations
  2. I am using an HTA which makes several remote tools available and also uses XML and VBScripts to read the Ghost Console directory structure and offers a list of available images from which to choose. Thanks again
  3. IcemanND, First, thank you for the updated WinPE 3.0 guide, I am using it as a launching point of Ghost images via an HTA. One item to note. In your documentation, when adding the packages, I have to revise the following and highlighted my revisions shown in bold. Set DestFolder=c:\winpe_x86\mount Set PackageSource="c:\program files\Windows AIK\Tools\PETools\x86\Winpe_FPs" dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-HTA.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-hta_en-us.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-MDAC.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-mdac_en-us.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-PPPoE.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-PPPOE_en-us.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-Scripting.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-scripting_en-us.cab rem dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-SRT.cab rem dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\WinPE-SRT.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-WMI.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-wmi_en-us.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\WinPE-WDS-Tools.cab dism /image:%DestFolder% /Add-Package /PackagePath:%PackageSource%\en-us\winpe-wds-tools_en-us.cab It appears since your original documenation, the name of the CAB files located in the EN folder have all been appended with "_en-us" Also, I did not find any CAB files in either directory for WinPE-SRT. Thanks, Geemail
  4. Understood on the help and manual files. How do I identify what the Exit Code numbers are for each application \ script ?
  5. mritter.... Ok, so I tried the font increase and saw the results...thanks for the suttle reminder that getting bloody is the best way to learn and sorry for the stupid question. If you would like, I can start a new thread but I if not, here is a new question.... Can you point me to additional help file or user manual, explanation or info on the Config Wizard - "Return Code Requires Reboot." and the Reboot Code Section. I have tried searching for pertinent posts, reading the Documentation page of the site, reading through the Manual part of the WPI.exe but I am not finding any explanation.... i must be missing the big help file somewhere!! Wanting to understand how to require a reboot after an installation of an app, then how to insure WPI starts automatically after logon and continues with the other apps that were selected on the orginal run of WPI. Looking to use this as a standalone app installer post deployment of our "golden" or master image as well as for everyday use when manually installing newly released software. I point that out as I wanted you to know I am not incorporating any runonce commands, etc. Just running the WPI.exe standalone from a network share. FYI...as I am sure you are wondering...if thru my testing I can get this to meet my wish list, we will register as a business. Thanks again for your help
  6. Again...thanks for all this info Couple of follow up items: Mr. Ritter: 1. I was able to get the following code to work for the grayed cond: fileVersionGreaterThan("9.3.3.177",getFileVersion("%programfiles(x86)%\Adobe\ Reader 9.0\Reader\AcroRd32.exe")) || !fileVersionGreaterThan("9.3.3.177",getFileVersion("%programfiles%\Adobe\ Reader 9.0\Reader\AcroRd32.exe")) Two things to note...the code as you listed it contained a space before "Reader 9.0" which I removed, also the code you listed showed [color=#1C2837][font=verdana, arial, tahoma, sans-serif][size=2] Did you intentionally specify the color, font and size code? I was unable to get the code to work when I included the color, font and size settings. 2. In WPI\Themes\Windows\wpi.css I changed the color in the following entry: .grayTxt { font-family: arial; font-weight: bold; color: #AA0000; font-size: 8pt; } a. On a 17" monitor at 1024x768 the font size was a little small and hard to read at 8pt....will increasing the font-size have any adverse effect on the rest of the layout? b. You mentioned "In wpi.css there are 2 entries for each type of text", with the above being the "Traditional" one. I am not sure what you mean here, what is the other text you are referring to?
  7. GhostAvatar and Mr. Ritter... Thank you both for your input.... GhostAvatar....I have tested exactly as you said and the following did indeed work for the file version verification for Adobe Reader. fileVersionGreaterThan("9.3.3.178",getFileVersion("C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe"))==false Mr. Ritter.....I had already tested the above recommendation by the time I got to your recommendation....I will take your recommendation about specifying the %programfiles% variable for Program Files along with the recommended syntax for specifying the Grayed Condition as follows: !fileVersionGreaterThan("9.3.3.178",getFileVersion("%programfiles%\Adobe\Reader 9.0\Reader\AcroRd32.exe")) Also Mr. Ritter....can you tell me which section of the theme's style sheet controls the grayed color....I am using the Windows Theme and looked at the install.css and I see the following section: .WPI_Text { color: GrayText; is there where I would specify a color? Finally....one other thing....using Adobe as an example....I have the Adobe Reader install, then an Adobe Reader Update install....i have wrapped them both together as seperate commands of an application, so when selected, it installs Adobe Reader and when finished, it installs the Adobe Update. The Reader installation is an MSI which on my test computer when it launches, I get the windows Open File Dialog Box and I can select Open and it installs Adobe Reader, then the Adobe Update begins and again, I get the windows Open File Dialog and I can select Open and it installs. I know I can remove the check mark for each file type and then that machine won't prompt again but I would like to automate this and somehow either prevent the Open File Security Warning box or somehow automate the choice to select Open and thereby allowing the string of installations to be automated rather than interuppted by the windows security prompt. Any ideas for circumventing the dialog box? Thanks again for both of your help with this....it is slowly coming together.... Geemail
  8. Sorry about that....I do have the path correctly spelled in WPI....I manually typed the posting and fat fingered it. Any other thoughts as to why I can't get FileVersionGreaterThan to work as a condition? Thanks for the pointer to the Disabling Checkbox....it works perfectly.
  9. Hello, First, love the tool....hoping to put it to good use after testing and resolving all issues. Two Questions: 1. Using WPI 8.1.0 and attempting to use the File System - File - FileVersionGreaterThan condition but cannot get it to work. I can successfully use the FileExists, or FolderExists, or GetFileVersion conditions. Using Adobe Acrobat Reader as an example, once installed, the file version is 9.3.0.148. If I use the Grayed Condition of FileVersionGreaterThan("9.3.0.147",getFileVersion("C:\Program Files\Adobe\Redaer 9.0\Reader\AcroRd32.exe")), the Application Entry for Adobe Reader is not Grayed Out and the color does not change. 2. In the Help File, for "Dependencies" and "Grayed Condition", is states "the entry's color is changed, or can be disabled".....my question is when specifying a Grayed Condition, how can I indicate that I would like the entry to be disabled rather than the color changing? Also, if I want the entry color to change, can you tell me where I can specify what color I would like the entry to change to when meeting the Grayed Condition? Thanks in advance.... Geemail
  10. Thanks Tripredacus....I will follow your guidance and see what I come up with.
  11. Hello WinPE users, I have 2 models which I am unable to find WinPE(Vista) ethernet drivers, if anyone has these models working within a WinPE 2.x environment, please let me know which drivers you are using. Dell Latitude C600 HP/Compaq Evo 510S Thank you in advance for your help
  12. ICEManND, It's been awhile....glad to see this thread is still active and the guide is getting better all the time. To that note...I wanted to let you know, I recently rebuilt my boot cd. Upon doing so, I used 1. WAIK "Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008" 2. Latest set of LAN and MSD drivers from DriverPacks.net (8.05.3) When including all the MSD drivers, I experienced a BSOD with a "Bad_pool_header" message. 1. I rebuilt the ISO without any of the MSD's and it worked without any issue. 2. I rebuilt again and excluded "D, D1, D2, D3" drivers directory from the DriverPack MSD set. This solved the issue. Thought you might want to include an update on page 18 of the guide. Thanks again
  13. Kyor, I have been using the 3Com boot services and I have bene able to successfully boot to my custom WinPE image. However, I would also like to add the WinPE image to a menu and add the choice to the meny to boot from hard disk. Since the 3Com services don't support boot WinPE from a menu, I found this thread which sounded like a solution to my issue. I have followed your step by step guide for PXE boot with pxelinux but without much luck. First, I want to make sure, I can use a windows workstation as my TFTPD server? Also, if I follow your step by step, what is acting as the PXE server? With 3Com, I have to start both the PXE server and TFTP server, but with your instructions, I would only be running TFTPD32. I am running DHCP on another server so I can't run the DHCP server from TFTPD32 and hence, I am not configuring TFTPD32 as a DHCP server. Do I need to somehow add the "pxelinux.0" boot file to my DHCP server? Thank you in advance for any additional guidance you can provide Geemail
  14. Zorphnog, Now you have me feeling really ridiculous....I am not even finding a config.js Here are the exact steps I have done: Downloaded WPI, extracted it to the C:\ For testing, I then copied an executable to C:\WPI\Install To run, I am double clicking on the WPI.hta located in C:\WPI Am I missing the big picture? Humbly, Geemail
  15. Hello all, I am trying to use WPI as a stand alone app for post image deployment installations. I have download 6.3, extracted to the C:\ of a WinXP SP2 workstation running IE7. When I launch WPI.hta, I get the attached errors. My intention is to have users run the HTA by browsing via UNC path and executing the HTA from a shared network folder. Thanks