Fencer128

Mine are working fine too...

Hi Joey, Glad to hear you got that solved! Good luck, Andy

Hi, I'm assuming Outlook 2003 here, but I'm sure the setting exists for other versions too. Launch Outlook and go to: Tools --> Options --> Other --> General Pane Uncheck "Make Outlook the default program for E-mail, Contacts, and Calendar." Close Outlook and go into Internet Options. Make sure that Outlook Express is set as the default mail client. Let me know what happens. Cheers, Andy

Hi, Maybe: CPLS Should read? CLS We'll see what Bashrat says. Cheers, Andy

Hi Joey, Sounds to me that you're doing everything right. That means that unless we've missed something it must be a server setup issue. Can you please check and confirm the following, to be absolutely sure: 1. You have authorised the new production RIS server on the domain (should be from what you say)? 2. You are definately connecting to the correct server when client PXE boots, in case you have more than one production server? 3. What other roles is your RIS server performing (i.e. SMS, DNS, SQL, etc.) 4. The folders used to store your RIS images have not had the permissions tampered with (that might stop writes/deletions/etc)? Could you also let me know if all your RIS servers use the same OS version and what that is? EDIT: The more I think about this the more I think something is wrong with the service or server. Could you have a look in the event log and see if there's any related errors? Is it possible you can rebuild this server (long shot I know) if nothing wrong can be found? Cheers, Andy

Hi, Could you elaborate on this? Restarting the BINLSVC and then attempting a client install should generate the PNF files for sure (I manage several RIS servers and this is always the case for me). Regards, Andy

Hi Bashrat, The Realtek AC'97 drivers have been updated yet again. Here is the download link: ftp://202.65.194.18/pc/ac97/alc650/WDM_A383.zip Cheers, Andy

Hi, The reason for the number choice is simply that I need to make sure that these 2 commands are the last to execute. Therefore if you want to run more than 8 commands you'll need to bump the numbers of the RISult added entries up slightly. With regards to if it works without 1 - 8, it still works as everyone who uses RISult would not get the files cleaned at the end of the installation (which I know does occur). You can use any of the numbers you like. The important point reagarding the BTS entries is simply that they are executed in the right order and preferably last of all. As you correctly suppose, the commands are executed in numerical order. Cheers, Andy

Hi, The 71.89 driver was the last official release to support the GeForce 2 Pro (I know this because I'm using one now and that's the latest one that works). Just thought I'd post this in case it helps. Andy

Hi, Version 1.1.0 is now up. Fixed a couple of bugs (see enclosed changelog). Hopefully the release cycle may slow down again now... Cheers, Andy

Hi, You'll need to post more detail of how you exactly are creating your unattended installation. IMHO your porblem most likely stems from one of two reasons: 1. Your Windows XP source is corrupt 2. Your unattended production method has damaged the source You can check point one yourself by creating a new vanilla WinXP SP1a file set. To check point two with the forum we'll need that extra detail. Cheers, Andy

Hi, To get support for 3rd party NIC drivers during text mode setup (which is what you want to do) then copy the *.inf and *.sys driver files for the NIC into the i386 folder of your RIS image. In the case of Intel you may want to make sure that you've removed any existing e100...sys, etc. driver files that relate to Intel NICs first. You also want to make sure that you're using the RIS specific driver files supplied with the Intel 10.2 drivers, and not merely the Windows XP driver files. Finally you will need to restart the BINLSVC on the RIS server. To do this type the following at a cmd prompt: NET STOP BINLSVC NET START BINLSVC Everything should now work. You will still need the Windows XP drivers located within the $OEM$\$1\NIC... folder and the "OEMPnPDriverPath=" ristndrd.sif file entry as these are used by Windows during GUI mode setup. BTW - You should have really posted this in the Unattended RIS Installation sub-forum. Good luck Andy

Hi, I have put up RISult 1.1.0b1 for testing. There have been a couple of changes: - File location for WatchDriverSigningPolicy.exe - Environment variables for calling various executables used in BTS_DPs_Finish.cmd Please can you give it a try - and if you encounter any errors/problems post them along with an attached RISultLog.txt file. Please ensure that you have read the enclosed instructions and particualrly that you are using: BTS method 2, GUIRunOnce, No KtD. It can be downloaded from: BETA now complete - see below Thank you, Andy

Hi rathcoffey, I think something is not quite right with your source/set up. You should definately get the drivers installed if you follow the instructions. Can you please check the following: 1. You have set up your folder structure as per the RISult instructions 2. You are using the latest versions of all programs/packs 3. You have used BTS Method 2, GUIRonOnce, No KtD (other methods do not work) 4. You have no spaces in any of your folder names/paths 5. You are happy that the ris *.sif file you are using is correct Please let me know as I've never seen a problem with the drivers not getting installed before. I'll have a detailed look at your log too when you attach it. Thanks, Andy

Hi rathcoffey, I'm intrgued by the file not found errors you're getting. Could you please attach the RISultLog.txt file to a post so I can have a look. Please also let me know which version of RISult you used. With regards to your file locations, I'm away from the office at the moment so I can't check exactly where everything should be. I'll be able to have a look sometime on Thursday though. If you've followed the instructions then everything should be in the correct place anyhow. Please make sure you're now using v1.0.9. You must have used an older version before as you should have another file (WatchDriverSigningPolicy.exe) in the $OEM$/$1/D folder. This was corrected in a later version (see changelog). I suspect this will eliminate one file not found error and leave you in the same position as Resonate (see above). Thanks, Andy

Hi Res, It sounds as if things are getting better now. The plug 'n play monitor issue is a known MS issue and can usually be fixed via a hotfix. The internet look up is something I've not seen before and that has not happened to me. I'm not convinced it's to do with RISult directly as I certainly don't play with the internet at all. Cheers, Andy p.s. If you could attach your last RISultLog.txt to a post here that would be helpful as I'd like to know exactly what file is not found.

Hi Res, Right - I think the file not found problem during "Post processing" is due to a 3rd party LAN driver included with w2k3 server that isn't present for w2k server. I imagine that it will not make any difference to your build and can be ignored. The driver will no date be old anyway compared to the ones in the BTS pack. If it isn't a driver then I suspect it's a different file not present on a w2k3 server and can again be ignored. The last lines in your log files as correct as far as I can tell, you should not have other entries after those shown in the post. I'm off to see the girlfriend for lunch now (it is Valentine's day after all ) - please let me know how the build goes, I'll have a read when I get back. Cheers, Andy

Hi Res, Thanks for doing a test. With regards to W2k server, I didn't write RISult with it in mind, but I have a suspicion it works anyway. Please let me know at the end of your trial if it works for you finally. Thanks, Andy

Hi again Res, Doh! This is most likely very simple. Do you have a folder %SYSTEMDRIVE%\Temp after install has completed? I bet that MOVE just creates a new file if it can't find the folder. I'll put an IF statement somewhere to fix this and make sure the folder is created. Once I'm done I'll release 1.0.9. Cheers, Andy EDIT: v1.0.9 now up.

Hi Resonate, In order to do these things it would probably be easiest to create a cmdlines.txt file and have it call a *.reg file that integrates some registry changes. cmdlines.txt and *.reg should be located in $OEM$ (and if you don't already have a $OEM$ folder it should be created at the same level as i386). The format of cmdlines.txt should be: [COMMANDS] "REGEDIT /S *.reg" There is a stickied list of common reg hacks at the top of the unattended forum, and many more can be found via google. Cheers, Andy

Hi Resonate, Please see my comments below: I have found the problem here. I have not carried through the variable that defines the custom.sif file. At one point there is still a hard linked "ristndrd.sif" specified. I have made a change that should fix this, but I am away from the desk at the moment so am unable to test it! If you have the time I'd appreciate it if you could run RISult and give some feedback. Maybe I've missed an update of BTS or maybe the way in which I've used RISult previously wasn't impacted by this - but I can see that WatchDriverSigningPolicy.exe is not located within OEM/bin. I've amended the path now so you should not get a file not found error again. I've had a look at this and it is something I'll need to spend a little time on. I've fixed the problem with BTS...Cleanup.cmd. There should have been a "DEL" in there. Presetup.cmd should now no longer be run but deleted instead - I blame cut and paste for that one The problem with moving BTS...Finish.cmd to a new location is unusual. It must be to do with the parsing of that particular command line within the context of an fedit statement. The MOVE command is correctly formatted when used in a simple batch file - it isn't working here though. I'll have a look and see if I can fix it. Failing that I'll see if I can do a copy/delete instead. With regard to the errors you get after executing BTS...Cleanup.cmd I suspect that's caused, as you suppose, by presetup.cmd erroneously executing. As such, this should now also be fixed. I (and others) have previously had problems with the "D" folder not getting deleted at end of the build installation. If the "D" folder is still present after you have otherwise successfully installed then this may not be a RISult issue. I'm currently in the middle of creating a VB version of RISult, as I have moved on a larger project - which incorporates RISult, as well as ISO and PE build creation in a GUI VB environment. As such, one of the things I'm working on is improving the logging abilities and making the file/folder specification process less error prone/intuitive. It's still a while away so I'm still supporting the batch RISult but I hope you can see that the idiosyncracies of batch file operation should eventually be a thing of the past! Given that the current 1.0.7 build of RISult has problems I'm going to post 1.0.8 immediately, with the caveat that it hasn't yet had the testing it usually gets and that the MOVE BTS...Finish problem appears to still exist. If you could re-run 1.0.8 and let me know of any remaining problems/improvements I'd be most grateful (I'm on vacation this week and have no VPN access to my work). Thank you for taking the time to report all of this. Andy

Hi Resonate, Thank you for your thorough reporting of your problems. You've found a couple of issues that I'll look into and fix tomorrow when I've got some free time. I'll also respond to each of your points in detail. Expect a v1.0.8 real soon! Cheers, Andy

Hi, RISult has been updated (v1.0.7 available). Thanks to "lightsout" for finding that the b57xp32.sy_ file wasn't being correctly expanded. Enjoy, Andy

Hi, Yep - my mistake! I managed to somehow forget to expand b57xp32.sy_. This has been corrected in RISult 1.0.7 that is now available. Please let me know if this works for you. Also, some files you may want to delete are: bcm42xx5.sys bcm4e5.sys These are older Broadcom drivers inserted by RISETUP.exe and are of no use if you're using the newer Broadcom drivers. Cheers, Andy

Hi, It's possible that your LAN controller is not yet supported. Please can you post the make/model of your NIC? Thanks, Andy