Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by randalldale

  1. I think I just figured it out.... I need to split the file because it is larger than 4.0 GBs... that is why the iso is failing, limitation of the DVD ISO 9660. Really bad part is I've deleted several nice WIM builds. Boy was that a wasted two days. Just loaded it in VMware and it is working fine.
  2. Ok Guys, It appears that it I did not fix it. The image is working fine using OSCDIMG up until I sysprep it. Once sysprep the image is fine if I do an image.exe /info. When I use oscdimg to create the ISO file and mount or burn the DVD when I use image.exe /info the file is now invalid. Here is the oscdimg tag I used. C:\Program Files\Windows AIK\Tools\PETools>oscdimg.exe -bx:\Win7-EA\iso\boot\etfsboot.com -n -m -lWin7-EA -D1 x:\Win7-EA\iso x:\Win7-EA-disk-1.iso Note: the Boot.wim works fine as the system boots without issue. Also I have tried this on two seperate development PCs and both fail at the same location. I'm syspreping a Windows 7 Enterprise build. Got to say it has me stumped... No one has experienced this? I would suspect the development PC or the imaging PC but the install.wim file works fine manually applying from my HDD from any of the 6 indexes.
  3. The only issue with using the WinRE.WIM method is it is not supported by Microsoft for Windows XP and some of the info I have been reading is that a Windows XP install while it will work most of the time using the WinRE method however there seems to be some occasional errors and BSOD's. Since it is not supported I could not get any help from MS thus would be stuck with errors and I can not provide an unsupportable solution. On a side note I plan on using the WinRE method for my Windows 7 installs and will be happy to post a 'how to' when finished.
  4. Mr Jinje, Thank you for the reply, unfortunately I have to use Microsoft tools as I work in a corporate environment that requires correct licenses. I will say that my boot structure is not an issue as the BOOT.WIM works fine, it is just my WIN7.WIM is corrupt after ISO creation. I posted last night before I left for the evening to see if anyone was having the same issues. Since no one posted that they were I will try a clean install and recreation process and let everyone know. Randy
  5. Hi Guys, Thanks for all the previous help. Right now I'm having an issue with OSCDIMG corrupting my wim files when I make the ISO's. ??? I'm copying the WIM files to a new PC running win 7 also and see if something is messed up on my developing box. I've tested my WIMs with imagex /info and they are fine but once I make the ISO files using OSCDIMG I can then mount or check the DVD and the WIM files are corrupt. I'm using the same imagex.exe file to create and check/deploy the WIM files with. If I apply my wim files manually from a HDD they work fine, it is just once created an ISO using OSCDIMG the Win7.WIM becomes corrupt. I should add that the BOOT.WIM is fine. Has anyone see this sort of thing? Thanks again guys, Randy
  6. Hi Guys, I need some help. I have no experience with C++ but need to figure out how to write a .EXE that can do the following lines from my VBScript. Set objWShell = CreateObject("WScript.Shell") objWShell.Run "cmd.exe %systemroot%\system32\diskpart.exe /s %systemroot%\system32\ospart.txt",0,True objWShell.Run "%systemroot%\System32\InstallOS.hta" I need to create a MyShell.exe to call in my WinPE winpesh.ini file with those lines. Has anyone done such a thing? I've tried four recomended conversion programs and none will run in WinPE 3.0. Thanks for your help, if I'm asking too much then that is fine too. Randy
  7. Ok guys, I have figured it out. It's all about sequence: First you have to create your OS partition I chose 20GB becasue my install is a little over 16GB at the moment. Then you create a WinPE partition, you can stop here or do what I did and create a third partition that holds your install files. I did this becasue I didn't want to change my install files scripts because my DVD install forces the dvd to the z: drive. the sequnce goes as follows: 1. Create OS partition, format and assign letter (do not make active yet) 2. Create WinPE partition, format, set active and assign drive letter, I chose 200MB for just booting. 3. Create third partition format and assign letter for installation files. Here is my diskpart.txt file for building the HDD structure. select disk 0 clean create partition primary size=30725 create partition primary size=200 create partition primary size=20480 select partition 1 assign letter format quick fs=ntfs select partition 2 active assign letter format quick fs=ntfs label=WinPE select partition 3 assign letter format quick fs=ntfs label=image exit 4. xcopy WinPE files to the WinPE partition to boot the system. 5. Upon reboot I then run another diskpart.txt file to set drive letters here is that code. select disk 0 select partition 3 assign letter=z select partition 1 active assign letter=s exit 6. I then call my install.hta file and do my installation. This HTA file does an interview that queries name, language, timezone, keyboard and location. 7. as I close and reboot I run the following diskpart.txt (note: these files are not all called diskpart.txt I just call them that here so that you understand what they are doing) select disk 0 select part 2 Delete part select part 3 Delete part exit 8. upon reboot your system will boot to the sysprep.inf and make sure you have included OEMExtendPartition=1 under the [unattend] section then all the HDD will be used. On a side note you can use the WInPE boot as many times as you need if you need to do things and reboot to WinPE just don't set the OS partition active (partition 1) until you're ready to reboot to the install. It's that simple... Thanks all, Randy
  8. Actually guys I may have figured out the issue and solved it my accident. It will be a while before I will know whether it works or not as I have a lot of scripting to finish yet. Here is what the issue is, I was not sure how I could get the system to reboot upon image install and recognize the OS partition as the one to boot. In fixing my problem of creating multiple partitions and loosing the original WinPE boot partition I corrected it by setting the WinPE partition as active last since the MBR sees the last Active partition as the boot partition. So that being said when I create the OS partition and make it active then run my installs upon reboot the system should already know to use the OS partition and I should be able to delete the WinPE partition in fiinshing. More to follow...
  9. My questionaire is a simple HTA file that asks the following: Name Language (we support 8) Timezone (Worldwide company) Keyboard (Worldwide Support) Location (due to SEP considerations I need the location so that I can set one of three SEP server sites with a wim file) Determine platform with a WMI Call. This information is used to dynamically create a sysprep.inf file and apply different WIM files do deploy the image. My current DVD design process: 1) The image system is large and requires two Dual Layer DVDs and one standard DVD, 15+GB due to applications and OS language MUIs. 2) First the system boots using WinPE 2.1 3) During the boot process I set the DVD drive letter to 'Z' using diskpart.exe. 4) I then call an HTA file that runs and determines if the PC is a supported product and a set of FE tools becomes available if the PC is a supported product. The code I use is a WMI call to the baseboard for a SYSID. I use the SYSID call because it then doesn’t matter if a different PC name is used since the SYSID is constant across the platform. 5) Once a PC is approved for imaging the HDD is cleaned using diskpart.exe I then call an HTA file that does an interview. This interview requests, name, language, keyboard and location. Once the interview is complete then the HTA file using VBScript and batch files using this input I create the sysprep.inf dynamically. 6) Using the SYSID I apply the drivers from the drivers.wim file. 7) Using the SYSID I apply the Roxio and WinDVD files from the roxio.wim file. 8) The install.wim is split into seperate swm files I copy the parts of sWinXP.swm to the HDD under the $OEM$ directory swapping out the two DL DVDs in the process. 9) From the last DL DVD using the language input I apply the appropriate base image from the sWinXP.swm file 10) Once applied the system is reboot and completes its install Zero Touch. I now have to port this over to an HDD design so that the image can be applied at the factory the following are my thoughts on design changes. HDD install base design: 1) Create two partitions: a Partition 1 size=512 label=WinPE (512mb boot) b Partition 2 size=20480 label=image (image structure is over 15gb and is seems growing) 2) Copy the WinPE structure under partition 1 3) Copy the imaging structure under partition 2 4) During the boot process assign drive letter 'Z' to partition 2 5) Create the OS partition and assign the letter 'S' 6) Run the installOS.hta as the DVD structure and using all same processes install OS as before. 7) During the reboot process delete partition 2 and add 'ExtendOEMPartition=1' to the sysprep.inf this would use the additional 20GB of space. 8) Boot up installing the OS as before under the DVD structure style. This is the part that I have issues with how do I now let the system know to use the sysprep'd image partition instead of the WinPE boot system under partition 1? On another note once I created the 20gb imaging partition in part 'b' the boot partition quite working and the system no longer boots. Fixed it, was a sequence thing make sure to do active and assign in diskpart on your boot partition last. Let me know your thoughts as I'm open to about anything involving HDD installation that can get this done since I only have until the 13th of Nov to make it happen.
  10. Tripredacus, thanks but it is not covered in the WAIK. It has to run from the HDD becasue these are new PCs shipping from the factory to the end user. Most people don't know that your large manufacturers will actually load your image on new PCs at the factory if you are willing to pay. That is why I need to port my installation files to the HDD and run the install from the HDD. Once finished I will clone it and deliver it to the manu for deployment on our new PCs. Only problem is I only have until Nov 13th to get finished. The one saving factor is I have the image on DVDs and just need to convert it. So this is much like a OEM release except that this is Windows XP therefore not supported anymore and I can not use the winRE.wim function built into winpe 2.0/3.0 as I saw you attempted earlier because it fails randomly with XP and I can not afford any failures. Basically I need to boot the system to a ram drive create an OS partition then using my HTA files do the interview process and apply WIM files from another partition. as I begin the reboot process delete the installation partition and the winpe ram disk partion reboot to the windows install. Simple... I just haven't figured out how to remove the winpe ram disk on reboot. With Winpe 1.5 you could add the Minint folder and it would do it automatically at least that is what I read as I can't find a whole lot of information about that either. Anyone have any ideas? When I figure it out I will post the results here in case someone else needs it in the future.
  11. Close to the IcemanND, the system I explained above needs be ported to a HDD to run the install instead of DVDs. It is windows XP otherwise I would be able to build a WinRE solution if it was Vista or Windows 7. In other words the whole install from boot up to login must run from the same HDD. Once completed this image will be copied/ghosted/cloned to HDDs in PCs leaving the factory. Similar to an OEM build that you would buy. Anyone done such a thing?
  12. I stated earlier that I already using a DVD solution. Since this is a large deployment the powers that be are requiring a Hard Drive solution for what use to be DVD based. So I'm just trying to fiure out how to make it work from a HDD boot and clear all partitions except the OS once finished and since it is being put on at the factory for end user deployment there can not be anything externally used. If it was Vista or Windows 7 I could create the WinRE environment, but since it is XP I have to just live with a building an HDD solution and not worry about a recovery environment.
  13. Hi Guys, I'm not sure if I'm posting in the correct location but I have been tasked with create a Hard Drive base image depolyment solution. I currently deploy my images using two Dual Layer DVDs, yes I know quite large. My current solution is an End User Installation process and I need to port it over to a hard drive solution. Has anyone written a 'How To' for deployment from a HDD? Here is how my DVD solution works: 1. System boots and using a WMI call identifies one of 21 supported platforms through system ID (good call tag to use just go to scriptomatic and under the 'Baseboard' call you find the SYSID). If you system platform is not supported you are told so and asked if you wish to install the base image of which it is password protected. 2. Once system is identified you are asked if you wish to image PC and if you choose yes are given a warning that the HDD will be wiped. 3. Once wiped I call an install HTA file that goes through an interview, Name, Language (we support 8), location (Worldwide) and keyboard. 4. Once you choose the 'Install OS' button then the install.hta file lays down the drivers, additional software, image, and antivirus location files. Then the sysprep.inf file is created using the above information. The cd key and admin password are encrypted until the sysprep.inf is created. 5. Lastly I call the wpeutil reboot command and sit back and watch the system fly. Good system takes about 40 minutes to complete. Now I need to port this imaging structure to a hard drive base install at this point I'm just a little confused as I can create a ram disk WinPE 2.0/3.0 boot for booting and can even run my install.wim but I'm not sure how to remove the ram install partition during the reboot to allow the ExtendOEMPartition=Yes to function. Anyone have any ideas or is there a 'HowTo' out there that I've just not found? Thanks for your help guys...
  14. Ok, I figured it out... Instead of creating the vbScript file I just needed to create a text file and read the lines on it into variables/arguments. Const ForReading = 1 Set Fso = CreateObject("Scripting.FileSystemObject") Set objFile = FSO.OpenTextFile("x:\settingVariables.txt", ForReading) Do Until objFile.AtEndOfStream strLine = objFile.ReadLine Execute strLine Loop objFile.Close MsgBox ProdID MsgBox AdminPassWord Contents of the settingVariables.txt: ProdID = "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" AdminPassWord = "Password" You can now use it to hide important things like the CD ket and admin password inside your boot structure. I hope this helps someone besides me out... Thanks again guys...
  15. Fredledingue, I really appreciate your help but I still do not understand how I'm calling a vbScript and using the paramters in my HTA file. you are saying Sub window_onLoad() MyParam = z:\MYvbScript.vbs.commanline End Sub I get 'Error: Expected Statement' Here is what I'm trying to do, I have a vbScript that sets the parameter: Dim ProdID, AdminPassword ProdID = "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" AdminPassword = "Password" This is saved as settingvariables.vbs ... very simple. I have that file in my boot structure under the BOOT.WIM file. What I need to do is some how call that file and the parameters be usable in my HTA file. I have tried Sub window_onLoad() Set objWShell = CreateObject("WScript.Shell") objWShell.Run("x:\settingvariables.vbs"),0,True End Sub MsgBox ProdID But the paramters do not get passed and are blank. Thanks again for your help, Randy
  16. I'm using HTA files and wscript will not run in an HTA file. Plus I'm not sure about the temp.vbs is this creating it or is it already created? It's kind of confusing to a noobe...
  17. Hi guys, First thanks for all the help in the past. A little background I have an image that I deploy out to a company that they are wanting to switch to end user installs. Becasue of that I need to hide the cd key and the admin password. What I thought is to dynamically build a script that the boot.wim would create a VBS file that would set the CD key and password parameters\variables. What I want to do is then pass them to my script that builds the sysprep.inf file dynamically. So my question is how do I set values in a vbs and then call that vbs to pass parameters? The first part is easy I believe: ProdID = "1234-5678-abcd-efgh-ijkl" AdminPassWord = "Password" Except when I call this from my other script the values don't get set. objWShell.Run "x:\settingVariables.vbs",0, True 'MsgBox ProdID' is blank So what am I doing wrong? Thanks for your help, Randy
  18. I use this to set the DVD drive to the 'z' drive and a timer function. '-------------------------------------------------- ' Here is some code to set the DVD to the z drive '-------------------------------------------------- on error resume Next Set Fso = CreateObject("Scripting.FileSystemObject") Set objWShell = createobject("wscript.shell") Set objWMI = GetObject("winmgmts:\\.\root\CIMV2") set dc = fso.drives found = False for i = 0 to 5 For each d in dc '** We only want to check DVD\CD-ROM drives ** if d.drivetype = 4 Then if d.isready Then dl = d.driveletter '** Set the parent folder ** path = dl & ":\Tools" if fso.folderexists(path) Then set diskpart_script = fso.opentextfile("x:\set_drv.txt", 2, true) diskpart_script.writeline "select volume " & dl & ":" diskpart_script.writeline "assign letter = z:" diskpart_script.writeline "exit" diskpart_script.close wshshell.run "diskpart /s x:\set_drv.txt",2,True found = True exit For end If end If end If Next if found = true then exit For objWShell.Run("wscript.exe sleep.vbs 5000"),0,True Next '--------------------------------------------------- ' Here is the sleep timer. '--------------------------------------------------- Option Explicit Dim ArgObj, vSeconds 'create the object to get the seconds variable Set ArgObj = WScript.Arguments vSeconds = ArgObj(0) set ArgObj = Nothing ' call wscript.sleep wscript.sleep(vSeconds) '<– wait the length of time input ' that’s all folks! I added it as an attachment TXT file too, I hope this helps... Randy SetDVD_Timer.txt
  19. Hi Guys, First thanks for all the help over the years. Question, is there anyway to encrypt the boot.wim file or for that fact your install WIMs? Thanks, Randy
  20. Hi All, First, wanted to say thanks for all the help over the years. Now for my question, has anyone see a guide or made a recovery partition like they do at factories? I was thinkng of adding a recovery partition but was not how to get an image to run from one? Thoughts or guidenance? Thanks, Randy
  21. Ok, here is what I'm trying... will let you know. objWShell.Run "cmd /c copy c:\$oem$\runonce.cmd" & chr(34) & "c:\programdata\microsoft\windows\start menu\programs\startup\runonce.cmd",0, True objWShell.Run "cmd /c copy c:\$oem$\finished.hta" & chr(34) & "c:\programdata\microsoft\windows\start menu\programs\startup\finished.hta",0, True objWShell.Run "cmd /c xcopy c:\$oem$\images\*.*" & chr(34) & "c:\programdata\microsoft\windows\start menu\programs\startup\images /e /i /y /q",0, True
  22. Sure but how am I going to apply a .wim file or copy the files I need that far down in with out changing the attributes?
  23. Hi guys, I was just wondering is there a way to post the file name or a message inside the imagex /apply command? I'm running HTA's for installing and when I apply a .WIM file I would like to post something in the cmd window if that is possible. Here is one of my 'Apply' lines... objWShell.Run "cmd /c imagex /apply z:\Sources\drivers.wim 8 c:",1, True Thanks for the help, Randall
  24. I will give it a shot thanks. Appears to be hidden or something...

  • Create New...