Jump to content

mbouchard

Member
  • Posts

    162
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by mbouchard

  1. I had this happen to me when I converted between 1.0 and 1.2 and found it was an error on my part. Check your bat files, startnet OC OC2 and comment out any EXIT's that you have, then recreate and try it again.
  2. I do not believe that you can change it in 2004 as MS sets this. One reason they set it to X was that in older versions it took the first available letter.
  3. No, All you need to do is copy the XP i386 folder into the folders you used to create your PE CD and recreate your ISO.
  4. Yes it is possible, it has been a while since I looked at this zip, but here is some files that can help you. I have included both a CD and a network method and the folder structure required. Basically, what I do is this, -Boot to PE -Gather info from user -Diskpart/format disk 0, this will delete all partitions on disk 0. -write some files to the HD, mostly vbs. -Copy i386 folder to PC -launch setup from local source. PE.zip
  5. I believe that the ramdrive instructions above was for older versions of WinPE and will not work with WinPE2005. But, it really isn't needed as WinPE2005 when built using Windows 2003 SP1 has RamDrive functionality. Check the WinPE.chm, there are instructions there on how to do this.
  6. Folder structure is such: C:\RamDrive Winnt.Sif WinPE2005.iso C:\RamDrive\i386 Bootfix.bin Ntdetect.com Setupldr.bin In the Sif [setupData] BootDevice = "ramdisk(0)" BootPath = "\i386\System32\" OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe2005.iso" At the suggestion of someone else, I moved all the files in the i386 to the root folder. I didn't get the error anymore but nothing happened on the VirtualPC that I tested the iso on, black screen only. Havn't burned a CD yet but plan to do so today.
  7. That would be against the License Agreement.
  8. Yes, at the root I have the ISO, i38 The Architecture entry must be present for x64 computers. For i386 computers, you can omit this entry or ensure that the value of the Architecture entry equals i386.
  9. Did this in step 1. 1) Created and tested my initial WinPE iso Here is my Winnt.sif, basically copied what was in the chm. The winPE2005.iso is in the root of the ramdisk folder
  10. I finally received a copy of 2005 and am in the process of testing the ram drive boot option. Following the instructions in the help file I: 1) Created and tested my initial WinPE iso 2) Created the folder structure as specified (c:\ramdisk) 3) Copied bootfix.bin, ntdetect.com, and setupldr.bin to the c:\ramdisk\i386 folder. 4) Created the Winnt.sif file and placed it in the c:\ramdisk. 5) Created the iso When I attempt to boot to it but get this error: Am I missing a step?
  11. 1.6 or 2005 or whatever they are going to call it is built off of 2003 Server w/sp1. While I have not looked at it I do know that it adds Ramdisk support.
  12. I do not believe that it is possible to join a domain. What resources are you trying to access?
  13. I use WinPE for installs so am not certain if this would work when creating an unattended CD install, but couldn't you just logon with your local Admin account and map a drive using Net Use in the bat file? I do something similar in PE and have not had any issues.
  14. is this being called from a Bat file or a vbs file? Also, are the the files located on the CD or did you copy them down before starting your setup? Lastely, for the post, did you type this out or copy and past what you use? The reason I ask is that I find a couple problems. Updated
  15. In my experience I would receive this error when my switches for Winnt32.exe were incorrect. Post the line that you are using to call Winnt32 include the switches.
  16. Where did you find WinPE 2005? I have looked in my Licensing downloads but have not seen it yet.
  17. Does your editor color code HTML? If so, just link your HTA to it. I use editplus and created an entry in the INI file for HTA's and used the HTML syntax.
  18. I have gotten both compiled and non-compiled AutoIT scripts working in PE. All I needed to run the non-compiled scripts were the files that are installed when you install AutoIT on your PC. I did not need to register anything.
  19. Also, if I remember correctly the /NoReboot switch only affects the initial GUI phase of the setup. Basically, after launching winnt32.exe it does it's thing then stops, you would then have to reboot PE to get the Text mode going.
  20. This file should be in your WinPE folder in the root of your disc
  21. This is an older one but it will give you a start. PE.zip
  22. I have posted a zip of files that I use where I work that does this. I am able to install on any "approved" platform which includes drivers. If you can't find the post let me know and I will look for the file.
  23. Not in my experience. With the Dell Optiplex 280, WinPE 2004 worked for me with no problems. I then tried to get the Precision 370 working and started to run into the same problems as you did, blue screens. I had to add the drivers to the PE image, just followed the included directions, and to the mass storage drivers section of the unattend.txt. Once I did this, I was able to get the 370 loading. I have only done this once so, I would not be the best one to help you on this, but there are others here that do this quite often and if they see this post will be a bigger help.
  24. What OS are you installing? From what it sounds like, you will probably need to add the mass storage drivers into the unattend.txt file.
  25. And it depends on your support contraints. Use WinPE and you can get support from MS. User BartPE and you probably can't. This is an issue in a Corporate environment. Also, I have not had any issues adding any needed drivers, both NIC and mass storage. yes it took some work, but I needed to do it for a XP setup also.


×
×
  • Create New...