tomasz86

There wasn't anything personal in my comment I just wanted to say that the proper driver files are located inside one of the MSI installers and are: nusb3drv.cat nusb3drv.inf nusb3hub.sys 1.0.1.0 nusb3xhc.sys 1.0.1.0 The rest of the stuff included in the package should not be needed. I also don't own any NEC USB 3.0 controller so I can't test it. My predictions are that the result will be similar to the Etron one I've got here. The driver can be installed but doesn't start By the way, does anyone know how to investigate what the problem with the driver is? I'd like to know why it doesn't start.

A new daily version of UURollup-v11 is ready: - fixed checksum of mfc100u.dll (wrong checksum made slipstreaming impossible) I've also uploaded some of the older stable versions of UURollup just in case someone wants to check them. By the way, I want to thank all people (you know who you are) very much for testing and reporting bugs

Thanks, I41Mar You need to extract the x86 MSI package to get the proper driver. I've got doubts that it will work in Win2k though.

OK, I'm going to prepare a driver pack but first I need to know what devices are used and connected to this board. 1) What's your CPU? Do you use an APU? If not then please tell me what your graphic card is. 2) Do you use the integrated Realtek ALC889 sound card? 3) Do you use the integrated Realtek RTL8111E LAN card? 4) Are there any other devices used? There shouldn't be many drivers needed for this particular motherboard: - mass storage drivers - sound drivers - LAN drivers and probably - graphic drivers If this is everything then preparing the package will be very simple. Actually the board doesn't officially support Windows 2003 Server and some drivers may not be available for the OS. You'll have to use XP drivers which should work in most cases but don't have to.

The readme talks about using $OEM$ folders. I don't use them to integrate anything because that's not a real integration. I don't think I can help you in this matter.

I can't say for 100% sure yet but I think the problem doesn't happen any more in the newest Firefox Aurora version so it seems that there was something wrong in Firefox itself. I'm still using the same graphic drivers.

I'm sure that most of those folders and INF files on the CD are not needed when integrating drivers I could create a package for you which you would just integrate using the script (one click integration) but there is a catch - you would have to follow my instructions 100% Actually nothing needs to be preinstalled. As long your HDDs are detected and there are no errors during the installation then you can just install all drivers later after the first boot.

A new daily (d120807) version of UURollup-v11 is ready: - added updated MS VC++ 2010 libraries from KB2723430 - added the following files from the newest BWC kernel: ole32.dll 5.0.2195.7104 user32.dll 5.0.2195.7144

You don't need to do anything with EnableBigLba if you integrate USP5.1 into the source (it's switched on by default in it). You may find this topic interesting if you want to integrate drivers.

But did you integrate the driver or just used the floppy to install it at the beginning of the setup? If you want to integrate all drivers then the link I mentioned above in #6 has everything you need to integrate them... This is the only way to have FULL control of the process. Of course you can try adding them through nLite but then it's trial and error game.

I'm not sure if I understand everything correctly. Are these new two HDDs empty? Are you trying to restore the system from the backup image and you can't do it because there is no proper RAID driver? Is this correct? Will you be able to restore the previous configuration if you install SBS 2003 again? I'm guessing that this is what you're trying to do now and this is why you're trying to integrate the SATA/RAID driver for AMD A75. Are there no HDDs detected when you run the SBS 2003 installation? What to you mean by "very similar to XP"? Is SBS 2003 recognised by nLite? If the folder structure, etc. is different then nLite may not integrate the drivers properly. This is how you can integrate the driver manually (use only the files from the x86 folder): and after that you should add more lines to: dosnet.inf [FloppyFiles.1] d1,ahcix86.sys txtsetup.sif [SourceDisksFiles] ahcix86.sys = 1,,,,,,4_,4,1,,,1,4 [SCSI.Load] ahcix86 = ahcix86.sys,4 [FileFlags] ahcix86.sys = 16 [HardwareIdsDatabase] PCI\VEN_1002&DEV_4391&CC_0106 = "ahcix86" PCI\VEN_1002&DEV_4392&CC_0104 = "ahcix86" PCI\VEN_1002&DEV_4393&CC_0104 = "ahcix86" PCI\VEN_1002&DEV_4394&CC_0106 = "ahcix86" PCI\VEN_1022&DEV_7801&CC_0106 = "ahcix86" PCI\VEN_1022&DEV_7802&CC_0104 = "ahcix86" PCI\VEN_1022&DEV_7803&CC_0104 = "ahcix86" PCI\VEN_1022&DEV_7804&CC_0106 = "ahcix86" [SCSI] ahcix86 = "AMD AHCI Compatible RAID Controller-x86 platform" hivesys.inf [AddReg] HKLM,"SYSTEM\CurrentControlSet\Services\ahcix86\Parameters",,0x00000012 HKLM,"SYSTEM\CurrentControlSet\Services\ahcix86\Parameters\PnpInterface","5",0x00010003,1 and then also make cab of ahcix86.sys and copy it to i386 (so at the end there will be two copies of the file, one in driver.cab and one in i386).

In older updates there was only one "BUILDTIMESTAMP" entry but now they seem to use BUILDTIMESTAMP + EXPIRETIMESTAMP. I'm not really sure what's the purpose of it.

Could you first answer these few questions? 1. You're saying that the other motherboard failed... are you now trying to connect the HDD(s) to the new one? How many HDDs were used? 2. Do you want to run the existing installation of the SBS 2003 or to install it from scratch? 3. SBS (Small Business Server) doesn't sound like something used at home. nLite is for personal use only and I'm not sure about the structure of the CD of SBS 2003. Is it the same as Windows 2003 Server? Even without using nLite you can integrate SATA drivers very easily manually. I can help you in this matter but please first answer questions 1) and 2). Edit: By the way, there's no *.oem file in the archive.

Actually the problem with .NET Framework 2.0 and uxtheme.dll doesn't affect only the applications which use uxtheme.dll itself. I think the core of the problem is that .NET Framework 2.0 "thinks" that the OS is XP/2003 when uxtheme.dll is present in %windir%\system32 and calls for APIs which don't exist in Windows older than XP. Programs which simply need .NET Framework 2.0 files to be present in the system will probably work anyway but if they really use some of the .NET functions and call for them then the issue will occur.

Are you sure the driver is correct? Could you post the URL where it can be downloaded?

New weekly (w120805) version of UURollup-v11 is ready. Everything from the latest daily is included in it except the new comctl32.dll which means that the 32-bit icon support is still there.

When a program doesn't work it doesn't necessarily mean the problem lies in the program itself. Something may be broken in the OS which makes it unable to run the program Just a few days ago after updating Firefox on my computer it suddenly stopped working (the UI was completely frozen). I thought that something had been changed in Firefox itself but in the end I realised that there was a problem in my system, not Firefox, and it was gone after I restored the system from a backup image. Anyway, what I want to say is that unless you've tested the application on different configurations and it didn't work on any of them saying that it "doesn't work" can have many different meanings.

That's a potential problem. It is possible to include different versions of the same driver (by renaming the files & modifying the INF files accordingly) but then the question is whether the OS will be able to apply them correctly. It would probably have to be tested under different version of VBox and other VMs.

But last year when I downloaded AMSN I got an alert from Windows Defender telling me it had adware. And it removed the file for me. Windows Defender flagged A MSN as having adware,which was the Open Candy that they put in AMSN. I got the alert on Windows Defender on both Windows XP and Windows 7. So AMSN has adware or malware in it. See here about Open Candy from the Microsoft website-http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?name=ADWARE:WIN32/OPENCANDY So AMSN is out. But there is Emesene which is safe to use. And it looks a lot like MSN Messenger 7.5. But Emesene does not support video or voice chat. So it has limited functions. And AMSN also looks like the old MSN Mesenger 7.5 but AMSN is not safe to use. Andrea Borman. While I personally dislike it very much when there's another software/toolbars bundled with an installer I don't really think there's anything risky in installing aMSN as long as you look at the screen before clicking "yes" and don't agree to install any additional software. aMSN itself is open source. About OpenCandy: http://en.wikipedia.org/wiki/OpenCandy

This is my "final" solution. I'll try to describe everything in details basing on the following example. Realtek 10/100/1000 PCI-E NIC Family driver (already mentioned before) 1) List of files: netrtle.cat Netrtle.inf Rtenic.sys RtNicprop32.DLL RTNUninst32.dll 2) I said in #53 that modifying layout.inf was inevitable. This is only partially true. A proper answer should be that the drivers must use a layout file in order to be automatically installed during the Windows setup and also in a running system when a device is being connected. The method described before didn't work in the second case. The solution to this problem is very simple. Instead of editing the original layout.inf (which is digitally signed) you can just create a new layout file for the drivers. Let's name it "layout2.inf". This is how its basic structure should look like: layout2.inf [Version] Signature="$Windows NT$" [SourceDisksNames] 1=,,,\i386 [SourceDisksFiles] 3) Normally 3rd party (non-M$) drivers check for files by using the path set in [sourceDisksNames] in their INF files. In order to make them use the structure from layout2.inf you have to: - add "LayoutFile=layout2.inf" under [Version] - remove [sourceDisksNames] and [sourceDisksFiles] sections completely Before: [version] Signature = "$Chicago$" Compatible = 1 Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} Provider = %Realtek% CatalogFile.NT = netrtle.cat ;;for WHQL certified DriverVer = 02/22/2012,5.794.0222.2012 [SourceDisksNames] 1=%DISKNAME%,,, [SourceDisksFiles] Rtenic.sys = 1 Rtenicxp.sys = 1 Rtenic64.sys = 1 RTNicProp32.dll = 1 RTNicProp64.dll = 1 RTNUninst32.dll = 1 RTNUninst64.dll = 1 After: [code][version] Signature = "$Chicago$" Compatible = 1 Class = Net ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318} Provider = %Realtek% CatalogFile.NT = netrtle.cat ;;for WHQL certified DriverVer = 02/22/2012,5.794.0222.2012 LayoutFile = layout2.inf 4) Now you should add the driver files to dosnet.inf, txtsetup.sif, layout2.inf and drvindex.inf: dosnet.inf (only layout2.inf, *.cat and *.inf) [Files] d1,layout2.inf d1,Netrtle.inf d1,netrtle.cat txtsetup.sif (only layout2.inf, *.cat and *.inf) [SourceDisksFiles] layout2.inf = 1,,,,,,,20,0,0 Netrtle.inf = 1,,,,,,,20,0,0 netrtle.cat = 1,,,,,,,20,0,0 layout2.inf (no *.cat and *.inf) [Version] Signature="$Windows NT$" [SourceDisksNames] 1=,,,\i386 [SourceDisksFiles] Rtenic.sys = 1,,,,,,,,3,3 RtNicprop32.DLL = 1,,,,,,,,3,3 RTNUninst32.dll = 1,,,,,,,,3,3 drvindex.inf (no *.cat and *.inf) [driver] Rtenic.sys RtNicprop32.DLL RTNUninst32.dll"[driver]" means here that the files are located in driver.cab. 5). Now you can add the files to driver.cab, pack layout2.inf, other *.inf and *.cat and move them to i386. Details about how to do it are available in #41. In case of mass storage (SATA, SCSI, etc.) drivers more edition is required and I'm going to explain everything in details next time (as I'm running out of time now). I also need to check one thing about the proper location of *.cat files of each driver because they seem not to be signed now... Anyway, the method described above is really exactly the same as the one used by M$. The only difference is that the layout file's name is not "layout.inf" but "layout2.inf"

There's always aMSN...

Opera 12.01 is ready... but still buggy (the UI freezes completely from time to time, at least in Win2k). @Kurt_Aust What do you think about adding information about Firefox ESR 10 to the guide? It officially supports Win2k and is going to be updated until February 2013.

I've updated the mozillaZine topic. It's now possible to install newer versions of Firefox after adding a small registry "fix" and thanks to a user xabolcs we've now got an addon which makes it possible to use the auto update function Thanks to this addon you can actually update your Firefox 12 (or older) installation to the newest one (but you still need to have UURollup/BWC kernel installed and uxtheme.dll placed in Firefox folder to run the newer versions). @blackwingcat Thanks. I'll check a different driver and let you know about the result.

Great! Thanks for testing slipstreaming. The issue with mspaint.exe is a very good finding. This is a known problem of HFSLIP but it can be overcome by placing the file in HFEXPERT\win\system32. I'll try to update the Complete method on my website. This is a new daily version of UURollup-v11 (d120804). Changelog: - remnants of the 32-bit icon support removed completely - added ole32.dll 5.0.2195.7103 shell32.dll 5.0.3900.7174 user32.dll 5.0.2195.7142from the newest BWC kernel

@blackwingcat I've just checked the newest version of the kernel (v20a2). There's a new ole32.dll there... but why has it got the same version number as the last official one from KB924432? KB924432 Ole32.dll 5.0.2195.7103 KB935839-v20a Ole32.dll 5.0.2195.7103 Shouldn't it be v7104?