Fencer128

Hi, Sorry if this is a stupid question - but what is the point of this thread? Andy

Yes, though he must have posted after me and his link is not to the manufacturer. Andy

Hi, In winxp regedt32 and regedit both point to the same file I believe - so it shouldn't be an issue (though maybe it is an issue during setup... so try changing to REGEDIT first). In my cmdlines.txt instead of running the reg tweak directly, I call a batch file, which in turn executes the regedit command. I'm not sure this is relevent but it works for me. Try creating a batch file (e.g. registry.cmd) and place it in $OEM$. Then change your cmdlines.txt to read: [COMMANDS] "registry.cmd" Then ensure the registry.cmd batch file contains the following: REGEDIT /S test.reg etc... Good luck Andy

Hi, Have you enabled the RIS service on your server? If not then you should If you're using flat images (i.e. those created via risetup.exe) then you can usually just copy them from one server to another. If you're using riprep images though, in addition to copying the images themselves, you'll also need to run risetup.exe on the new server in order to have a flat image available. I suggest that you search MS TechNet to read some of the basic guides about setting up RIS. There's a fair amount to learn. Good luck, Andy

Hi, I tried using the PXE boot disk - but still no joy. I wasn't particularly hopeful anyhow as the machine PXE boots ok, it's just the start of GUI mode setup that's the problem. I've contacted our system vendor to get their support, as they should check these things as part of our QA procedure. From other tests I've carried it out I'm pretty sure the problem is with either e1e5132.inf and/or e1e5132.sys. The drivers just don't work correctly with this part in RIS. I'll post any follow ups. Cheers, Andy

No problem. I wasn't sure what you already knew. That is correct. In fact, it you don't export it through regedit and forget to add the following to each *.reg file (which regedit adds automatically), things don't work: Windows Registry Editor Version 5.00 Please note that you can include multiple registry changes within the same reg file, but you only need the above title once (at the top of the file). I have my registry entries split into several reg files as I found that sometimes adding too many to a single file causes a failure. You can easily add 10 - 20 though in my experience, without issue. There is a stickied thread in the "Unattended Windows" forum here that lists lots of different registry entries so you don't have to hunt for them manually. A cmd file is just a batch file. Exactly the same for all intents and purposes of what we are doing here, but different suffix. I'm sure *.bat will work the same as *.cmd. As such, I'm sure you know how to make them RIS is very specific about certain file locations. Look up some MS info on RIS to see what I mean. BTW it is $OEM$ and not OEM. RIS is really picky! Good luck, Andy

Hi, All the info you require is here: http://technet2.microsoft.com/WindowsServe...2a74e01033.mspx Click on [RemoteInstall] We use: [RemoteInstall] Repartition = Yes UseWholeDisk = Yes To completely remove all existing partitions and create a single volume the size of the entire disk. Cheers, Andy

Hi, That's what we do here. The way we do it is via a combination of SIF file entries and REG modifications to the default user profile. By adding the REG modifications as HKLM and/or HKCU at build time in the way described below, they will automatically apply to the default user profile. The registry modifications are contained within .reg files. These . reg files are processed using the following command: REDEDIT /S TEST1.REG ... REDEDIT /S TEST9.REG These commands are contained within a cmd file (i.e. reg_add.cmd) that is placed in the $OEM$ folder. The cmd file is called from the "cmdlines.txt" file. This is a file recognised by Windows setup and should also be located within the $OEM$ folder. For example, for the case above the contents of cmdlines.txt would simply be: reg_add.cmd Hope that gives you a pointer. Cheers, Andy

Hi, RISult v1.1.2 now available. The newest BTS DP Base 6.02.4 will NOT work with previous versions. The only change to the latest version of RISult is to restore functionality with the newest version of DP Base. Cheers, Andy

I second that! Major mistake! Andy PS leenamhee PMed me and told me that the folder name change did fix the problem. However, it looks like he may of inadvertently caused another!

Hi, Just found the problem! Change the name of the folder: $1$ to $1 Retest. I bet it works Andy

Hi, You don't mention *exactly* what the problem is... i) Does the RIS installation complete only for the client system to not have the Windows driver for the Broadcom NIC installed? or ii) Does the RIS server refuse to load the image through text-mode setup saying that "There is not a suitable driver for your hardware" or something to that effect? If the problem is i) then the answer lies with checking your SIF file. If the problem is ii) (which I suspect) then you need to check that you followed the Broadcom RIS instructions 100% and that you have restarted the BINL service. I suspect that not restarting the BINL service is the most likely cause as you don't mention it in your otherwise comprehensive post. To restart the BINL service, first make sure you have copied the required Broadcom *.inf and *.sys driver files to the i386 folder. Next, log on to the RIS server and open a "cmd" prompt. Then type: NET STOP BINLSVC NET START BINLSVC Your drivers should now work. Please let me know how it goes. Cheers, Andy ps - There is one other possibility which is that you need to make sure you are using the latest Broadcom drivers. They are v8.48e for gigabit NICs. Also, note (this is a big note!) Broadcom changed their RIS instructions recently. You seem to be using the old method. Try this instead (from the Broadcom site):

Hi, Thanks 5eraph. Cheers, Andy

Hi 5eraph, I managed to nuke my unattened files, scripts, the lot and am currently rebuilding them as best I can. I am unable to download the montior pack though. Could you test the link again? Thanks, Andy

Hi, I'll give it a go tomorrow - though as you say, it's a bit of a long shot as the boot floppy generator from 2003 doesn't support any Intel 1000 NICs. I'll let you know how it goes. Cheers, Andy

Hi, PXE is already enabled - I just can't get RIS to admit that it has a suitable text-mode driver. I suspect that the old workarounds for RIS and Intel parts have either: i) not been implemented correctly yet for this particular NIC or ii) don't work when a PCIe bus is used (as opposed to PCI) I guess we'll have to hold off on the platform and wait for 10.3 drivers, which will *hopefully* fix this. Cheers , Andy

Hi, The NIC appears in Device Manager as PRO/1000 PM I have not seen it referenced anywhere else as such. It is an on-board NIC and so Intel usually refer to them by the ethernet controller part. That is, 82573V. If you look that part up you see that it is in the supported list for the PROSet 10.2 drivers (hence I guess why it works under windows). If you look up 82573V NIC specifically it points to the PROSet drivers for download. They just don't work in RIS. Cheers, Andy

Hi, Fixed our RIS problem that might have been the cause of this - but RIS still refuses to acknowledge a driver exists for the NIC. Just noticed that the Intel data sheet for the ethernet controller (82573V) lists a PCIe interface bus. All the on-board NICs we've used before were PCI 32/64. Anyone think that might make a difference? Cheers, Andy

Hi, The driver download for the 945GTP motherboard just points to the normal 10.2 PROSet drivers. The actual conroller is listed above: Intel® 82573E Gigabit Ethernet Controller Intel® 82573L Gigabit Ethernet Controller Intel® 82573V Gigabit Ethernet Controller In a windows environment the e5132.inf file is fine for doing an install, the device gets recognised correctly. So, we can assume that the generic HWID I posted above is all that is needed. It still won't boot under RIS though...! *scratching head* Cheers, Andy PS - Just spotted a RIS problem we're having - probably not related but I'll check first and get back to you!

Hi, Since Intel moved to their 10.x drivers I've not had any issues with getting their hardware RIS compliant. However, we're just in the process of migrating from Intel 915GUX PRO/100 VE based motherboards to 945GTP PRO/1000 PM motherboards as our stable platform. The relevant HWID for the 945GTP is: PCI\VEN_8086&DEV_108C&SUBSYS_30998086&REV_03\4&6C79FC5&0&00E0: Intel(R) PRO/1000 PM Network Connection I've not been able to get this RIS booting at all. RIS complains it does not have a driver. I've checked both the e1e5132.inf and e1000325.inf RIS-variant files but do not find a reference to the exact hardware above. There is a catch all in e1e5132.inf (I believe) for: PCI\VEN_8086&DEV_108C but this is obviously not working. I tried adding a line for the specific hardware above, but that made no difference either. I find it extremely annoying that Intel's SIPP (stable image platform) motherboard will not RIS boot and imagine that someone has found a way around this... Any ideas anyone? Cheers, Andy

Hi, If you manage to get that working and have other questions then there's an unattended RIS sub forum, complete with guides, etc for slipstreaming/integrating files... Good luck, Andy

Hi, Can you give details of how you created your unattended DVD? I suspect the problem may be with this, as opposed to the BTS DriverPacks specifically. Cheers, Andy

Hi, RISult 1.1.1 up now. Had to fix issue with sif file. If you use the default ristndrd.sif file then there is no change. If you use a custom sif file then after RISult has completed you will need to copy the two GUIRunOnce commands added by RISult from ristndrd.sif to your custom sif file. You will then need to delete ristndrd.sif. Cheers, Andy

Hi, Assuming that the extra "sp3" hotfixes you added aren't causing your problem, have you installed the latest chipset drivers for your motherboard? Do you have UDMA enabled for your IDE controller in Windows and in the BIOS? Do you have Bus mastering enabled for your IDE controllers in the BIOS? Just a few obvious points to check first. Cheers, Andy

Hi, No it's not. You may not have created a bootable CD in the right way, or possibly something else is causing your problem. Without more detail on what you did to create your CD we can't give any useful help I'm afraid. Andy