• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dabone

  1. Ok this is the parseFile sub only, to use this just replace you entire parseFile sub with this. This version of the sub will extract the image name where ever it is in the childnodes. '**************************************************************************** '* parseFile ''**************************************************************************** Sub parseFile() Set objSel1 = window.document.getElementById("select1") objWIM.Source = myFilepath + objSel1.options(objSel1.selectedindex).text objWIM.GetWIMInfo strWimInformation = objWIM.XML ImageCount = objWIM.ImageCount Set xNodes = objXMLDocument.selectNodes("//IMAGE") Dim strlen Dim namestart Dim nameend Dim namepos Redim strIndx(ImageCount-1) Redim strNames(ImageCount-1) namepos = 1 verpos = 1 blnLoaded = objXMLDocument.loadXML(strWimInformation) k = 0 If (blnLoaded = True) And (objXMLDocument.parseError = 0) Then For Each xNode In xNodes objWIM.ImageIndex = k +1 namestart=InStr (namepos,strWimInformation,"<NAME>") nameend=InStr (namepos,strWimInformation,"</NAME>") strlen = nameend - namestart strNames (k) = Mid(strWimInformation,namestart+6,strlen-6) namepos = nameend + 1 strIndx(k) = xNode.getAttribute("INDEX") k = k + 1 Next End If enumDirs End sub Hope this helps. Also, I'm putting together a posting on my version and the correct way to have multiple wims with a menu. Later, dabone
  2. Ok, I've written the code to parse the xml for image names. It doesn't care where in the file it lives. It's just using string functions, I didn't bother trying to figure out that xml crap anymore. It will handle mixed mode images (created with pe 2 and then appended with 3 or vice versa) And its alot faster than using the gimagex com. Do you mind if I post the new parsefile code here? Later, dabone
  3. Ok, I've done a little more playing and noticed if you append an older wim with the newer imagex, the xml data for the different images stay the same as the imagex version used.. (I.e PE2.0 images in the wim file have the name located in the first child node, pe 3.0 images have the name in the last child node.) The modification I did uses the gimagex com to select the image number then extract the imagename. It works with new and old and the mixed images I have generated. (I have quite a few images, 40 or 50 of them, so redoing them would be a pain). To speed up the parsing of the xml file, would any of you real programmers care to write a parse routine that takes the raw xml data, then parse out the image number followed by the name? We already have all of the xml in memory, the original programmer just used the xmlcom method of grabbing image number followed by grabbing a specific child node for the name. (Would love to get the windows version out also, so the boot sector type wouldn't be tied by name) Later, dabone
  4. Here is my customized version of the imagex.hta. I've been using it in house for awhile now. This version runs under winpe 3.0 (x86 so far, I'll try X64 tomorrow) The big changes I made to get it to run are. The command window.confirm doesn't seem to work for me in pe 3.0 so they got replaced. The xml for the wims are different, so I changed the way the program gets image names, the new way is much slower, but you can use it with new or old wims. This version only support writing out images, giving a command shell, reboot, or shutdown. I made this for system builders to deploy images only. If the Image description has the letters XP in it, the program will automatically put the nt52 bootsector on. Hope this helps other people. later, dabone
  5. on my customized version you can run ghost32 reboot or shutdown. All other options have been removed, also the tech has NO control over drive partitioning. I've got it parsing the Image Description for any occurance of xp and if it finds that then it automatically runs the correct bootsect command. Now all I need to do is add custom labeling of the destination drive (i.e. imagename) and get a real progress bar and then this program is perfect for my usage. (I know how to do the custom label, I'm just taking a few days break from modifying the source) Anyone know any examples on how to display the output of imagex to a popup window as a progress bar? And after I'm done I'll be sure to upload it. Later, dabone
  6. I had to remove the com objWIM.ApplyImage command and go with the command based imagex.exe because in a networked enviroment the objWIM.ApplyImage is locking the wim file. I needed to be able to deploy to multiple machines at once so the file being locked is a REAL show stopper. I've send a message to the author of the GImageX_COM.dll to ask how to apply a image without locking the file. The upside is I have a status indicator now. (I'm showing the cmd window.) Later, Mark
  7. Ok, I've gotten some more experience with your program. A few questions and feature requests. I'd like to be able to define a variable in the file for a default diskpart action. i.e. set kill=1 to always run the custom diskpart.txt file without any prompts. Also I'd like to be able to define a default apply path (c:) without prompting. I see you are getting rid of browse.exe, would that get rid of when you select browse that it defaults to the c: (My wims are located on z:\wims, and that is the default set in the hta file.) I'm getting around the xp deployment problem by hitting alt-f4 and running bootsect /nt52 c: after image deployment. I'm going to try storing all os load for each motherboard in 1 wim for 32bit and 1 for 64bit. Very nice tool and thank you for your hard work. (I didn't look but do you have a paypal for donations?) Later, Mark
  8. I'm doing the following.. I copy my xp sp2c cd to a temp dir. Using the extracted sp3 I go to the update dir and say update /integrate:c:\xpdirectory Then I'm using nlite to insert the intel achi and raid drivers for ich 7 - 9. Then I have that dir as a network share under winpe 2.0. Trying again today, the problem only happens when I insert the textmode drivers. Just loading the servicepack has no problems. Strange that the entire setup will complete without a reported error. Also, the sp3 with the drivers installed works fine from a cd based install. Later, dabone
  9. I'm trying to install a slipstreamed version of xp pro sp3 oem. I took a sp2c media and slipstreamed in sp3. I then tried to deploy it with the regular ms opk. It seems to install fine, but has errors. (the start menu doesn't have IE is has a Internet icon that takes you to ie's properties) Some services are missing (Can't install the Intel 12.4 lan drivers). I've also tried a manual install with the WINNT32 /syspart:c /tempdrive:c using winpe2.0. It gives the same results. The weird thing is.... it works fine if installed off the cd. Any suggestions? Thanks. Mark
  10. Ok, reading more the use of multpile sku per wims does make sense to me (Sorry, to much ghost on the brain). But I'm still confused about imaging xp. I see that there are problems doing a xp image because of the way diskpart formats the drive. How does gimagex know that the image is a xp image and partition and format the drive correctly? How does it know to lay down the correct mbr and bootsector? Thanks. Mark
  11. I've got a certain use for this program and wonder if it can do the job. I'm a oem system builder that sells around 8 different models of systems at any given time. For each system I do a preload of the following operating systems. XP Home, XP Pro, Vista Home Basic, Vista Home Premimum, Vista Business, Vista Ultimate, Vista Business X64, and Vista Ultimate X64. All of these loads have the office 2k7 oem preload and the correct device drivers and updates for the system they are going on. I'd like to keep each load in a seperate wim file and keep the wims in different directories for each motherboard. Also I'd like the gimagex to see that the filename starts with xp and apply the mbr fix to the destination drive. Is this possible with the framework of this program? (I.e. stripping out the need to select which image from the wim and always default to image 1, filename checking for xp. etc.) This will be used in a pxe booting enviroment so the only hd in each system will be the destination drive. Thanks for any input. Mark