Jump to content

Jopster

Member
  • Posts

    30
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by Jopster

  1. I can give you that answer. There's a bug in Windows setup that prevents WinRE from being installed before the specialize phase of setup. Only way you can get it to work is by running it after that phase (specialize, audituser for instance) through a batch file. I have it working like this. I created 2 partitions, first one for my recovery purposes and assigned drive letter z: to it, but made it partition 1. Second one for my OS, made it partition 2 and assigned drive letter c: to it. Install your OS on the OS partition, afterwards run a batch file with "imagex /apply <path of your WinRE image> 1 z:" and it should deploy nicely. Only thing you have to do next is to run the setautofailover.cmd /target z: and you're all done. The drive letter will disappear because it's made hidden and you should boot nicely into the recovery console.
  2. Not too many people with the problem apparently. Anyway, just got confirmation from Asus as well. They supplied me with a beta BIOS with the latest PXE update for one of their boards. Problem fixed. I've sent a list of "problem boards" to them and they will update the BIOS in the coming weeks.
  3. A small update: I can confirm it's again related to the PXE version of the nVidia nic. MSI just supplied me with a BIOS update with the latest PXE ROM (232.0529) integrated and it worked in combination with the nVidia RIS drivers (version 4.7.1) I always have been using. Last year, a PXE update also solved these problems. I think once in a while they make a change in the chipset which makes PXE booting with RIS incompatible. I've send a request to my contacts at both MSI and Asus to implement this latest PXE update in their nVidia boards. I've already got confirmation from MSI and I'm waiting for confirmation from Asus. If your PXE version is lower than version 229.xxxx, it's my experience that it won't work and you'll have to ask your motherboard manufacturer to implement a new PXE version in the BIOS. So to summon it up: the problem I'm having is a blinking cursor in the left top of my screen after selecting the OS through RIS. The OS is loaded, but after the progress bar I'll get the blinking cursor. Sometimes I've seen the issue that it locks during the progress bar state. The RIS driver 4.7.1 works. You'll need to copy the .inf and .sys file to the I386 directory. In addition, you'll need to copy the .sys file to your i386\system32 directory, otherwise it'll give an error during installation.
  4. True. A bit of a misunderstanding from my side I think. I thought he meant a central network driver source for the loading of the configuration set/image which does look for the drivers in the I386 directory. I must be getting old or need a vacation.
  5. As far as I know, it's not possible. RIS looks for the drivers in the I386 directory of the image that is being loaded at that time. It would be handy though. Saves a lot of time if you have many different nic drivers. I have to manually add new drivers to 22 images. Hell of a job, but I'm used to it now I guess.
  6. It depends on what kind of nic you have. Only a few have these options. I don't know about yours. But do you even have a PXE ROM on your nic? Can you turn it on seperately in your BIOS (Boot from LAN / Enable nic (option ROM)? Do you see a nic boot screen during startup or nothing at all. If the answer to the above is "no", there's a good possibility your onboard nic doesn't support PXE and you will have to use a seperate nic to PXE boot the system.
  7. Couple of things you could try. - You could look in the BIOS if there's an option to turn on the boot rom for the nic. - Do you ever get to see the NIC boot screen? I've seen cases in which you have to change the setting of the nic to "PXE" in the nic's BIOS. You could check if there's a hotkey available to enter the nic's BIOS. - Try a BIOS update. - Only set the nic as boot device and disable the rest and see what that does. - You could always try a seperate nic in case all of the above doesn't work.
  8. Sure you can do that. The end-user needs to accept it. If he's present he can accept it. Another way is to install the OS for the customer and run Sysprep at the end of the installation. The only disadvantage (from memory) is that the user account you created during the installation will remain, so the customer gets 2 user accounts after creating one himself. Perhaps there's a workaround for that, but I don't know it.
  9. I used to have similar problems with WinPE over RIS. In my case the naming of the clients was causing the problem. They all had the same name when connected to the RIS server. I solved it by setting the name to be related to the MAC address instead of a user name. You must change this for the RIS server. It's a setting in AD. I'm able to run as many installations as I want now. Hope this helps.
  10. A bit late, but I've got some comments about this issue. The problem has been known for quite some time now. Last year, I talked with both Microsoft and motherboard manufacturers about this issue. The problem back then was related to the PXE ROM version of the nVidia nic. I asked several manufacturers (I'm a system builder) to implement the new PXE version in their BIOSses. They did and the problem was solved. Now, the problem has come back and I've contacted them again. From my testing, PXE ROM version 215.0503 doesn't work at all anymore. I've had (limited) success with version 220.xxxx and higher. Right now, I'm waiting for Asus and MSI to provide me with a beta BIOS with the latest PXE ROM included. I don't believe it's driver related. I hope I'm wrong though, but experience has tought me that this is purely PXE ROM related. I'll keep you updated.
  11. Just change the names in your "Images" directory. For example: if you have multiple Windows installations, name them AWindows, BWindows, CWindows, etc...
  12. "Drivers\X200\Chipset;Drivers\X200\modem;Drivers\X200\video;Drivers\X200\audio;Drivers\D400\NIC;Drivers\D400\PCMCIA;Drivers\D400\Video;Drivers\D400\Audio;Drivers\D400\Modem;Drivers\D410\system;Drivers\D410\texas;Drivers\D410\Chipset;Drivers\D410\video;Drivers\D410\audio" Try it without the "". They don't belong there. So OemPnpDriversPath=drivers\blabla Furthermore, watch the spelling. It's OemPnpDriversPath, not OemPnpDriverPath
  13. Try /quiet /norestart. That will work. Just be sure you install the package with .Net installed otherwise it'll fail.
  14. Both Intel and Broadcom need special RIS drivers. The Intel ones you can find on the Intel site. You can find more info on this subject on: Link And if you haven't tried yet: try to reboot the binlsvc service in order to make the clients look for new/updated drivers.
  15. Figures... don't know about that one. I would try other Yukon drivers. Also, it could be that your PXE ROM version of the Yukon nic needs an update, but so far I only needed an update for the nVidia nics. Yukon always worked for me, but I've had to experiment with different drivers.
  16. It could be driver related. I've had problems with Yukon drivers as well, only not these problems. I only experienced these problems with nVidia nics and on certain Asus motherboards without (it sounds strange, I know) PCI cards installed. You could try other Yukon drivers. They differ a lot. Furthermore, what motherboard do you have?
  17. This sounds familiar. What nic do you boot from?
  18. There are some great sites out there where one can find good information. So I don't find it strange that we meet in both of them. If you will make it public that you're going to share that RIS driver with the rest of the world, it could perhaps be a problem if nVidia finds out, but in the worst scenario they will ask you to remove that specific driver. You bet!
  19. You're welcome. Thought your nickname looked familiar, Bingo. I'm always willing to help over here too. There's a lot of useful information I have been able to get from here, so if I can do something back... Jopster aka Jos p.s. be careful on posting the drivers. They're under NDA.
  20. Thanks for pointing that out. It's just that there're so many threads about these subject, one almost doesn't know where to look anymore. In my case, I overlooked something. I'm just glad it's working now. It look me long enough...
  21. Got it working now. Finally... I forgot the entry DriverSigningPolicy = Ignore. It solved all my problems. It's finally working after all this time due to one entry... I feel a bit stupid now.
  22. Those links look familiar. I was going to write a whole story of what wouldn't work and bore you with my life story, but it looks like it's working or at least going to work. It seems like I made some kind of mistake in my dosnet.inf file or I forgot to copy some files into the correct directory. Right now Windows is installing just fine and all seems to work smoothly. I'm gonna look into it. Edit: The install on a Promise S150 TX4 went fine, but after the complete installation Windows starts looping. Trying to find the cause I installed Windows on a normal IDE harddisk, keeping the Promise card in the system. Installed everything without a glitch and looked in my device manager and noticed something weird. My Promise card was detected as a "Raid Controller" without any driver details or manufacturer details. Another weird thing is when I want to update the drivers it automatically detects and installs the correct driver which was copied during the installation process. It's not the first time I've experienced this problem, but it is the first time using this method. Anyone knows what causes this perhaps? I'm confused here.
  23. Same problem here. Currently, I have 9 RAID drivers installed this way and I grew tired of it. It takes up so much time to get it to work and even now not all drivers work flawlessly. I've been experimenting with the txtsetup.inf method, but that doesn't seem to work in this case. It only seems to work for a cd-based installation. The best way would be to integrate the drivers somehow, but I have yet to meet the person who can accomplish this. Or I haven't searched very well, but I've been searching for de decent solution for over a long while now without any luck.
  24. Does anyone know how to extract files and/or do a silent install from a Setup Factory 6 install file? I can't seem to find this information anywhere. Heck, I've never even heard of it before.


×
×
  • Create New...