OcTroN

Member
  • Content count

    45
  • Joined

  • Last visited

Community Reputation

0 Neutral

About OcTroN

  1. Instead of using volume names like C:/D: etc. you better use DISK 0. LIST DISK to list your disks. SELECT DISK 0 to select disk 0, works like a charm over here !
  2. Ah I see. Maybe you can try some unofficial way like I do: start %systemdrive%\install\Vista.exe is a one line AutoIt script that waits for the Introductionscreen to popup, after that it gives a shutdown -r -t 0 command. I don't remember why I made it this way (some years ago now) but it is needed in my installs tho. If no one is posting a official Microsoft solution you might want to try that, offcourse the shutdown thing has to be changed to start your .cmd Let's hope someone has the knowledge to post a official solution haha
  3. Yes it will ! That's the way I do it tho In your xml: end.cmd Haven't give me any problem for some months now [Edit] Noticed you want to use RunOnceEx where I use RunOnce, guess it won't give you any problems but I'm not 100% sure ..
  4. Arrow, you are great! Been looking a while for doing this via such a easy way. No import/export and powercfg s*** Thanks man !
  5. Why not make a floppy which fit your needs. Then burn this with Nero to a cd... (hold ctrl + n when selecting data cd, see http://www.bootdisk.com/nero.htm). Now you have your bootflop on bootable cd. Just an idea ;-)
  6. How about Win98SE keys works with Win98FE? At least when I have to reinstall for someone I always use Win98SE cd, no matter it has a FE key or not, it takes all ;-)
  7. The product key listed in a unattended install file decides which version to install. In this .wim, with combined 32bit and 64bit builds, does it still automatic pick the right vista version according to the key? Any ideas? Or should I just test it next monday ;-)
  8. Excellent guide mate. Helped me a lot with some things !
  9. I got it working ! In the unattend.txt I simply added this, like ChrisBaksa said. Thanks mate ! Unattend.txt This ""IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"" so it will still work with inbox controllers. [OEMBootFiles] are in $OEM$\Textmode Peace of cake ! Thanks for the help all !
  10. I think this link is useful for you: http://blogs.msdn.com/archon_team/archive/...ersInWinPE.aspx Good luck !
  11. Ah ok, thats what I was missing. I will try it out tomorrow and let you know if it worked! Thanks a lot mates! B)
  12. Like the topic title says i'm trying to integrate RAID drivers into WinPE. The controller I want to add is the Intel ICH6R, sata (on the Asus P5GD1 Pro) After doing some research and reading trough the Windows PE manual it should be quiet easy, what I did was the following: 1. Copy the F6 floppy install files to "\I386\SYSTEM32\ICH6" 2. Edit I386\SYSTEM32\WINPEOEM.SIF this way: [OemDriverParams] OemDriverRoot="" OemDriverDirs=ICH6 I removed all the other crap out of winpeoem.sif This is what the manual says to do, so quiet easy. So I created a RAID1 volume within the controller and boot the new created WinPE CD. It sees the HD and formats it (where I got a red cross before, it gives a green V now . The next steps it does is like normal, activate the network card, connect to the server and preloads :-) After this is done it reboots and you see the XP setup screen (which you try to install). Here it quickly loads all drivers like a normal Windows XP CD does in the beginning. At the end of this screen it gives a nice blue screen with the error "Stop 0x0000007B". According to this KB (http://support.microsoft.com/default.aspx?scid=kb;en-us;324103) it has to do with the Device Drivers. So it looks like it's not loading the drivers in the Windows XP setup but it does in WinPE. The Windows XP setup is on the HD though, since WinPE copies the whole image from the server to the HD, and then reboots and continues. Strange thing is that it looks like the loaded XP setup on HD want the drivers served another way since this is just a xp setup loaded from HD. Looks like i'm doing nothing wrong and this driver simply won't work. But I hope any of you has a solution or sees what I forget. Any reference material: http://blogs.msdn.com/archon_team/archive/...ersInWinPE.aspx Original WINPEOEM.SIF: ; ; WinPE OEM driver list ; [Version] signature="$Windows NT$" ; ; Use this section to replace the inbox driver ; list with your own files ; ;[massstoragedrivers.replace] ;mydriver = mydriver.sys ; ; ; Use this section to append non-pnp drivers to ; the list of the drivers already present ; in the inbox ;[massstoragedrivers.append] ;mydriver = mydriver.sys ; ; ; Use this section to load pnp/non-pnp oem drivers ; in addition to the inbox driver list ; ; OemDriverRoot : Indicates the path relative to ; the system directory of WinPE. If ; none, then specify "" ; ; OemDriverDirs : Specifies series of directories separated ; by comma. Each specified directory has the ; txtsetup.oem which has the information on ; what driver to load. ; ; e.g. OemDriverRoot = "" and OemDriverDirs = drv1, drv2 ; indicates to the WinPE that under WinPE's system32 directory ; there are two directories named drv1 and drv2. Each of these ; directories contain txtsetup.oem file which lists which ; driver to load ; ;[OemDriverParams] ;OemDriverRoot="" ;OemDriverDirs=
  13. Thanks mate, testing it out right now. Will let you know if it worked.
  14. I can't get EnZip to install silent. It is a InstallShield package but /s or /silent don't work. The returned error is -5 what means the file does not exist (?). Anyone know a workaround, or does this error mean the package is screwed by the creator? Download: http://www.brothersoft.com/Utilities_File_...nZip_15521.html