Fencer128

Hi, It's interesting how often people cite MCSEs who don't know half as much as they should. I know quite a few MCSEs who are very knowledgable, as well as ones who are not. I think the key problem has been that because an MCSE has been such a desirable qualification to have when it comes to CV building, many people have gone on cram style courses/revision marathons in order to get it. Whilst this will, through attrition of exam attempts, eventually succeed it does not develop the understanding and wider knowledge gleaned with experience. Conversely, there are others I know with 30+ years of IT experience who are only now getting past Win9x and DOS to learn about current OS, AD, etc. So, experience on its own can also be lacking in certain, sheltered environments. Because of the above factors I believe certs to be a good thing, but only in conjunction with steady learning and experience. Pieces of paper rapidly gained on a CV are not as impressive as those spread out a little more in time to allow for *real* learning. Cheers, Andy

Hi, The 255 character limit has been expanded. http://support.microsoft.com/default.aspx?...5&Product=winxp Cheers, Andy

Hi, If you need to get problematic NIC drivers working in RIS (text mode setup) then I've found that 99% of the time the fix is to edit the appropriate INF file as described below. The article is from Broadcom but applies to other INF files too. The instructions for editing them can be found here on Broadcom's site under "No. 79": http://www.broadcom.com/drivers/faq_drivers.php It appears to be a parsing problem. Once you know this you should be able to get those drivers working on all your boxes. I have Broadcom, Marvell and Intel drivers all working this way on many PCs (actually the newer Intel drivers ship with RIS specific INFs in the driver folders - or they just work "out of the box" - it was the older pre 10.0 drivers that needed the editing mostly). Cheers, Andy

Hi Bashrat, Creative have updated (15/11/05) their X-Fi series driver to version 5.12.14.1144 [2.07.0004]. It can be downloaded from here: http://uk.europe.creative.com/support/down...ype=1&x=30&y=11 Cheers Andy

Hi Bashrat, Intel have released (26.10.05) a new version of their generic 2200BG/2915ABG WLAN drivers (9.0.3.0) and PROSet software (9.0.3.9). It can be downloaded from here: http://downloadfinder.intel.com/scripts-df...&ProductID=1784 Cheers once again, Andy

Hi Bashrat, Marvell have updated their Yukon gigabit Ethernet drivers to v8.46.4.3 (22.11.05). You can download it here: http://www.marvell.com/drivers/driverDispl...o?dId=116&pId=3 Cheers, Andy

Hi Bashrat, Nvidia Forceware 81.95 (WHQL) has been released. It can be downloaded from: http://www.nvidia.com/object/winxp_2k_81.95.html Thanks, Andy EDIT: Realised I shouldn't really be putting update requests in this topic. Will post more sensibly for future requests. Thanks.

Hi, I haven't had time to run through all your post as I'm quite busy at the moment, but it may be worth your while having a look at this: http://www-w2k.cs.berkeley.edu/admin/docs/docs/dhcpris.txt It could be of use to you if you have your clients and either the RIS and/or DHCP servers on different subnets. Good luck, Andy

Hi, Is it possible you could post the HWIDs in question? There's a utility linked in Bashrat's signature (save_hwids.exe) if you need the program. Cheers, Andy

Hi, Did you get a positive result with this driver? Andy

Hi, You are not using the latest driverpack base. You are also using an out of date graphic pack A. Try rebuilding with current packages. Andy

Hi, I posted the link to an Intel download page. I assume Bashrat took the link in my post, so the download is "official" if this is the case. Cheers, Andy

Would you believe it.... Nvidia ForceWare 81.94 has been released. You can get it from: http://www.nvidia.com/object/winxp_2k_81.94.html Cheers, Andy

Hi Bashrat, I always use method 2, GUIRunOnce, No KtD. Cheers, Andy

Hi, I don't get the above error. Please see my attached HWID.txt for your information. Good luck, Andy hwids.txt

RISult 1.0.6 now available. See enclosed changelog for details. Andy

Hi, I'm still slightly confused as I didn't realise that executing a batch file invoked the 16-bit sub-system, anyhow... In my experience I would suggest integrating RyanVM update packs before slipstreaming BTS driver packs. I would also suggest that you make sure your Win XP source (which you are going to integrate the files into) is a clean, untouched CD (i.e. no customisations of any kind). BTS driver packs will make all drivers available at build time, but will only install the one's relevant to your hardware, using method 2. Once the build is complete you will only have the drivers relevant to your installed hardware on the hard disk, the others contained in the relevant BTS packs should have been deleted. I think I'm right with this, but if anyone else knows better please feel free to correct me Good luck, Andy

Hi, Could you post some more info? What OS is the computer running the driver pack slipstream using? What OS are you trying to integrate the drivers into? What else have you done to the OS that you are trying to integrate the drivers into (i.e. used nlite, ryanvm packs, etc.) Andy

Hi, This is the code I use to set English (UK) for everyone. We also have many IMEs as well as east asian and r-l packs installed, which may explain the extra entries under "LanguageGroup". [RegionalSettings] Language=00000809 LanguageGroup=1,7,8,9,10,11 SystemLocale=00000809 UserLocale=00000809 InputLocale=0809:00000809 I note that there are differences between the keys in your code and mine. Maybe you need the "Language" key? I know that you shouldn't need any kind of registry hack to accomplish this - it should be possible from the sif file. Cheers, Andy

Yes, less driver packs means less files to expand, which in turn means GUI mode setup starts quicker. Cheers, Andy

Hi, The driver packs are being uncompressed from their .7z archive. This is normal. Andy

Hi, Try replacing InputLocale=0c09:00000409 with InputLocale=0c09:00000c09 Good luck, Andy

Hi, I don't have any promise or nv hardware, and I don't get any associated blue screens. Good luck, Andy

@midiboy Interesting, I'm just examining the fact that the "D" directory is now present after install (it wasn't with earlier 5.10.x base packs - but I never checked with later ones). It's not complete however, there are only a couple of sub-directories (i.e. G, M, L) and within them some numbered folders (i.e. 4, 5 and 6). In those sometimes there is nothing and other times an inf file or 2 and some "INFCACHE.1" (I can't remember the exact name as I don't have access to the machine at this moment) files. The exact contents depend on the hardware. I thought it was probably because of my RIS method but maybe it's something else (I mention it here in case this is so). RISult uses method 2. If I find any further info I'll post it. EDIT: As I suspected, it was my method at fault and not DP BASE. (I was trying to delete cmdow.exe from a batch file run from cmdow! - the command to delete "D" occured after this and so the batch file executed without processing the "D" deletion). Cheers, Andy

RISult v1.0.5 now available for download from usual link. Changes include removal of some file operations made unecessary by changes to BTS packs. See enclosed changelog for details. Should now work with RyanVM 2.0.0 update pack, Integrator 1.0.2 and BTS base pack 5.11.2. Please post any problems to this thread. Thanks, Andy