Fencer128

Hi, To add text mode LAN drivers to your RIS image (which is what I assume you're wanting to do) just copy the required *.inf and *.sys files for each adapter to the i386 directory of your RIS image once RISult has run. Once you have done this restart the binlsvc service in your RIS server and you are good to go. Cheers, Andy

Hi, The DriverPacks should be in *.7z format (not *.7za). You seem to have everything else correct. To add text mode LAN drivers to your RIS image (which is what I assume you're wanting to do) just copy the required *.inf and *.sys files for each adapter to the i386 directory of your RIS image once RISult has run. Once you have done this restart the binlsvc service in your RIS server and you are good to go. Cheers, Andy

Hi, Regardless of which method you use/how you do it, it's worth mentioning that the driverpacks are put together with Windows XP in mind. There's no guarantee that they will work with win2k. Good luck, Andy

Hi, If you go to download any pack there's a link to the changelog for each pack. That tells you what is contained within A, B, etc. I don't think a new naming scheme is required, just need to read what you are downloading before you do it. I don't think that the "B" pack is set up to necessarily get less updates than the "A" pack. Cheers, Andy

Hi, My script modifies all references to the CD drive, so yes it should modify PRESETUP.CMD Admittedly, it's been a while since I've looked, but there should be a REM statement in the code explaining this. Cheers, Andy ps - please note that my script is written and tested for method 2 only.

Hi, Are you using RIPREP or RISETUP to create your RIS image? - because I use RISETUP to create a flat image and I don't have a $win_nt$ folder. Andy

Hi, Please see the stickies at the top of the page. Regards, Andy

Hi, DP Graphics A 6.02 has not been released. That is why you can't download it. Make sure you are using DP Base 6.02 if you are using the "Update Checker". Cheers, Andy

Hi, Have you seen the stickied posts at the top of the forum? Check out RogueSpear's RIS Guide V2 and AutoRIS, as well as my RISult. Cheers, Andy

Hi, Forgive me for stating the obvious, but are you sure there's no way to import either excel or tab delimited data into your accounts package? That would definitely be the easiest way. Regards, Andrew

Hi, As you said - just copy them into the DriverPacks directory, exactly as you would do with other BTS packs. The run the slipstreamer. It's easy. Good luck, Andy

Hi, I don't have much experience with Ghost - but I'm pretty sure that because it's a binary image format you can't make hardware independant images. What you need is a flat file image (i.e. using RIS and RISETUP). This will allow you to install Windows over a network in the true sense, rather than just simply drop a binary onto a disk and hope it boots. This will give you greater hardware independance. Good luck, Andy

Hi, If you post details of the errors in the appropriate threads then they be investigated. It's been so long since I've worked on these files manually that I'll need to do a little revision before I can remember exactly what to do. I believe RogueSpear's guide used to have such instructions, IIRC. Cheers, Andy

Hi, Have a look in the "Unattended RIS Installation sub-forum" of the MSFN forums (under "Unattended Installation") for details specific to RIS. Particularly please see the 2 stickied posts concerning RISult (me) and RIS Guide V2/AutoRIS (Roguespear). Cheers, Andy

Hi, I have a working cmdlines.txt inside of $oem$. I'm pretty sure that's where it should be. I suspect your problem lies with cmdlines.txt itself, or failing that possibly your sif file. Good luck, Andy

Hi Bashrat, Marvell have updated their Yukon drivers to v 8.49.2.3. They are available from: http://www.marvell.com/drivers/search.do Thanks, Andy

Hi Bashrat, Just to let you know that 3ware have a 8500, 9500S, 9550SX series driver 3.00.01.052 [9.3.0.3] available for download. http://www.3ware.com/support/download.asp? Thanks, Andy

Hi, The update tracker is incorrect. You have the latest version. There is nothing to worry about. Andy

Hi, I'm currently using the packs on a variety of hardware, some Realtek HDA or AC97, some using other sound handware. Upshot is that I'm personally building around ten machines a week (others are building more with the same drivers) and not getting bluescreens, so for me it is handy to have the drivers there and there's no advantage in taking them out (quite the opposite actually). Cheers, Andy

That's just what I did straight off. Problem solved ) Andy

Hi, Thanks for the information. Do you use Ghost-based images for all your OS deployment? BTW - You mention that RIS wouldn't be suitable for allowing BIOS flashes and secure HD erases - I wonder if this is true? With the right tools available via the CIW menus I'm sure there's a good chance it would work. We use RIS to fire up partition magic and PC check for example, amongst other utilities. Anyhow, I'm sure it's a non-trivial amount of work to set up reliably. Cheers, Andy

Hi, What is your PXE boot environment exactly? Do you have a product name or is it a completely custom developed application? Cheers, Andy

Hi, Please can you elaborate. If you check AD on the server do you see the machine account of the client PC in the correct container? What I'm trying to tell is whether once you have selected the correct AD credentials from within the CIW the machine account is actually being created. This will allow us to see whether it is a problem with account creation or having the client PC join the domain. I'm sure you know this but I can't be absolutely sure from what you've written so far. Cheers, Andy

Hi, The files themselves go into the i386 folder directly. You will need the inf file too to get them working (you do not list it). For text mode setup you ONLY need the inf and sys files as far as I know (and possibly the din file too?). The rest of the driver files are not used during text mode setup and should not be copied into i386. If you do not do this then the Pro/100 drivers will not be available during text mode setup, which is where you need them. Remember to keep the $OEM$... folders and files too as these are used during GUI mode setup and will be the drivers used by Windows proper. I always put all of the driver files, just as you have done, into the $OEM$... folder and not just the inf, sys and din. You seem to be doing everything else correctly. You do not need the $OEM$ folder nested within i386. You only need the $OEM$ folder alongside i386. Cheers, Andy

Hi, This does not seem to make sense. On the one hand you say you used the same machine to create the RIPREP image as you later did to attempt to install the same image via PXE boot/RIS. Then you have to delete the HAL type declaration from the RIPREP image sif file to get RIS to show the same image in the oschoice menu for the same machine as that mentioned above. The type aacpi *should* be the same hal type as the machine on which the RIPREP image was built (it always has been in my experience). The only reason you wouldn't have seen the image in the oschoice menu is because the machine you PXE booted does not have the correct hardware to work on the halaacpi hal type!?!? I'm curious as to if the installation worked once you removed the hal dependancy from the sif file? Andy