raymondbreen

Hi, I have been using ris with ripref very succesfully since march/april, as it stands at the moment my company has rolled out over 200 machines with all of two images As for the error "The BINL service cannot locate a flat image with a version that matches the version of the RIPREP image." . I have had this when you have created a ripimage from a full xp installation source that doesnt exist on your ris share as riprep requires a normal installation from ris to be carried out before you can riprep. Great script, I will give it a go next time i need to update our driver pack images as its a pain in the butt to do it manually. Thanks

Hi, I have created a fully automated boot image but am having problems trying to get it to fit into the 700mb limit on a normal cd. I have chosen option 2 as the build to the driver packs are compressed on the image and to get it to fit on ive had to delete the wireless, as this is going to be rarely used, but I would like to have this also on the image. Any ideas for reducing the size of the image?

indeedy, its where do you stop aint it. The reason i mentioned a modem pack is because next to the packs you have atm, its the next most common(for corporates), as we have a lot of laptops, and not every hotel has ethernet for broadband. Chipsets do come first though, there isnt too many of them

Hi Bash, Do you happen to have any plans for a modem driver pack?

okedoke

bugger, my offer still stands though, if you need a backup site, just let me know, means I would get faster downloads

Hi Bashrat, Its Realtek ac'97 Audio, on a Sony Vio(model no VGN-B1XP). The pcid for the sound card is System Information report written at: 03/17/05 07:54:24 [sound Device] Item Value Name Multimedia Audio Controller Manufacturer Realtek Status Error PNP Device ID PCI\VEN_8086&DEV_24C5&SUBSYS_81C5104D&REV_03\3&61AAA01&0&FD I/O Port 0x00001C00-0x00001CFF I/O Port 0x000018C0-0x000018FF Memory Address 0xE0100C00-0xE0100DFF Memory Address 0xE0100800-0xE01008FF IRQ Channel IRQ 9 You can grab the driver files from http://www.rbreen.plus.com/5.12.01.4060-040810.zip Hope this helps mate.

Hi Guys, I have used an older version of the sound driver pack(5.022) and during the detect phase for the sound card on two laptops(different manufacturers, one hp and the other sony). I am prompted with the new hardware wizard, upon pressing return, it finds a suitable driver(strange as you would think that it would automatically install the driver without user input) and then blue screens. if i obtain the driver from realtek and install then all is fine, is this a known issue and if so, has been it fixed in the later versions?

good luck with your exams mate, and drop me a message with your paypal info and I will get some money your way. I was going to download your latest driver packs but the site appears to be down, with a bandwidth exceeded limit. I have a couple of servers, one in the usa and one in the uk, which i can use as a backup for these driver packs if you would like, could even possibly host your main site. Let me know what your bandwidth/storage requirements are.

Hi Bâshrat the Sneaky, you got your paypal account set up yet? after the time and effort you have put into all the packs i am sure i can convince my company to make a reasonable payment to you

yea, it requires ad and has some other requirements, reason I didnt go the linux route is because its very easy to setup, it just has some quirks

great stuff, unfortunately most of the machines i am deploying onto are significantly slower, so the installation phase is longer(method one) than copying files across the network(method two). Regarding time, i can have a old p677mhz compaq en sff with 256mb ram, at a login prompt after 20 minutes, compared to around double that for an automated cd install. As for wifi pxe card, nothing springs to mind, but it wouldnt surprise if me if most machines with built in ones can do it. on second thoughts, you could always get a ethernet to wifi bridge, this should do the trick, as this would also solve the possible issues with drivers during the text/gui setup stages.

fortunately or unfortunately depending on what way you look at it, we have sms 2003 for deploying our applications, which makes things interesting

yea, i do agree the hal restriction is a pain, but with the modification of a few files, you can have another riprep image in a few minutes, same goes with the restriction on the disk size, you can edit the imirror.dat and change some of the values and you can install onto any size harddisk, no matter what size harddisk the original riprep image machine had.

yea, but a riprep image is significantly faster than method 1 at least imo, and from my testing

yup, bastianbu, that was a pain to get sorted. I was actually replying to Bâshrat the Sneaky, but it took me a while to write that posting, and you ended up replying in between

ok great, basically ris is purely file based as opposed to the likes of ghost / Acronis whch are sector by sector copies. I have found ris to be much more flexible once its setup. You can create images in ris using two methods, one is basically an automated network install which basically uses the network instead of cd for the source files. The second involves an image being created using the automated network install and then you adding any files, applications etc etc to the image, then using riprep to copy the changes to the ris server. When you install using this text based and gui based install are used from the network installation, and then after that has completed the whole directory structure is copied to the pc. For both methods there is an unattended answer file stored in a templates directory that is processed by ris, this is very similiar to a typical answer file with a few extra settings for ris. Important directory layout Method 1 - Network install Typical directory structure -$oem$ -$1 -Drivers -nic - All required driver files including .cab, .inf, .sys, .dll etc etc -$i386 - All unexpanded source files from cd -Templates - ristndrd.sif - Answer File - .inf, .cab, .sys for unrecognised nic's The reason for the same files being in two different places is becuase during the text setup, the i386 directory is searched for the network files, but during the unattended gui the $oem$ drive is search instead. Nothing like consistency eh Sample Ristndrd.sif (with unnessary lines removed) ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="1" edInstall="Yes" floppyless="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" LocalSourceOnCD=1 [setupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [unattended] UnattendMode=FullUnattended DriverSigningPolicy=ignore oempreinstall=yes OemSkipEula=Yes TargetPath=\WINDOWS FileSystem=LeaveAlone NtUpgrade=No OverwriteOemFilesOnUpgrade=No One thing to bear in mind is that some drivers that are shipped as part of the typical exe install will not actually work without some modification to the .inf files to work on ris. Intel and broadcom are two that spring to mind. Fortunately Intel provide .inf files specifically for ris, whereas the broadcom you have to edit manually to work. Method 2 - RipRep image As i mentioned before the riprep image is nothing more than the final step in the network image install where it copies the whole directory tree to the machine at the end of the text part install. This allows you to be able to modify pretty much anything so you do not have to keep on creating new images everytime a driver is required for a new piece of hardware. What I basically did was to copy the i386 directory to a temp area , and then followed your steps for integrating your drivers into this. Once it had been completed , i simply opened the .sif file that you created and copy and pasted the oempnpfiles string, directly into the software driverpath hive under windows/system32/config ,then copied over the driver files. Hey presto it worked fine The main integratiion that would save me a lot of messing about would be the facility to put the txt and gui setup files into the required area, and also update the software driverpath. Its pretty difficult for me to extract the required files from the network driverpack and place into the i386 directory without creating extra files needlessly. Also I see the issue whereby you may have inf, dlls' etc etc with the same filename, not sure how you would get around this? Maybe just copy the files that are not supported by microsoft, as any existing ones will be upgraded if they are in your driver pack during the GUI / first boot stage. Sorry for the long post, but I hope it helps.

Firstly I would like to say that these packs have saved me many hours in combining my own. I am using ris and riprep functionality and by adding these drivers to the riprep image they work without any issues at all, what would be excellent would be if there was a driver pack for the nic and ideally the storage drivers specifically designed for ris. i do not mind assisting in this if you need a hand. ps if anyone needs info on how i put the driver packs into a riprep image as well as cloning a riprep image using a different hal, give me a shout