PVU

Fernando, I believe you modify the RST drivers. Don't feel pressured by this question, but will you attempt to add in those INF lines - force-fitting the latest to work with ICH8R and ICH8M? I have not tried to do it on my end. Thanks Update: Fernando, I found you (actually in many places), and you have answered my question. Your post 350: There is a widespread misconception that the chipset manufacturers are working to develop their drivers only or primarily on improving performance ... In this respect, it should not surprise if the emphasis of development work at Intel is currently not the backward compatibility for the new RST-driver series... Many thanks.

Within the last day or so, Intel released their latest Intel® Rapid Storage Technology (AHCI/SATA) driver. This is a message for anyone with an ICH8R or M chipset. For whatever reason (perhaps by error), the new driver 10.​6.​0.​1022 does not support ICH8(R or M). I have an Express 965 chipset, and no go today. The new INF file omits: %PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2821&CC_0106 %PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc% = iaStor_Install, PCI\VEN_8086&DEV_2829&CC_0106 PCI\VEN_8086&DEV_2821&CC_0106.DeviceDesc = "Intel® ICH8R/DH/DO SATA AHCI Controller" PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc = "Intel® ICH8M-E/M SATA AHCI Controller" The weird thing is that the older ICH7 chipset is supported - I just updated my 945 box. It's also weird in that Intel's download site indicates 965 support. For those with 965/ICH8, use the old 10.1.0.1008 IRST/SATA driver for now. This could have been an oversight on Intel's part. Who knows. Update: AHCI and RAID drivers completely stopped for ICH8

That's an Intel Chipset. For Windows 2000, I believe the last *official* AHCI (Sata) driver was the 32-bit Floppy Configuration Utility for Intel® Matrix Storage Manager version 5.7.0.1011. I say official, because there may be a newer modified driver out there. See this thread for fun. Fernando 1 may be able to steer you in the right direction. However, if you are not too concerned about ACHI, the basic (latest) Intel Chipset utility may work. Good luck, and let us know how this works out for you.

fdv's site is down, and he's been hosting the Windows 2000 Service Pack 4 Hotfix list. See the attached. Also see the (last) beta J topic on this forum page that should work fine, and you can search the web for the final 1.7.9 Windows 2000 Final Hotfix List.7z

Double posted - see below.

Out of Cycle Update for XP and 2003 Server Microsoft Security Bulletin MS10-046 - Critical - Vulnerability in Windows Shell Could Allow Remote Code Execution (2286198) - Published: August 02, 2010... KB2286198 This replaces nothing.

Get a load of this. The source is pretty solid. The reasoning behind this [extending so-called "downgrade" rights to XP until January 2020] is a little convoluted, but the details are simple enough. According to Microsoft, downgrade rights for XP would have previously expired 18 months after the release of Windows 7, or at the release of Windows 7 SP1, whichever came first. Windows 7 shipped in October 2009, so that date plus 18 months is April 2011. (Which, coincidentally, is when Microsoft now expects to deliver SP1.) ... I'm a little depressed today at the passing of Windows 2000, but amazed at the XP extension. I do wonder about Paul Thurrott's call on the 7 SP1 release, though. It would seem that SP1 would be ready to go way before April 2011.

And here it is. I will be updating the Windows 2000 Hotfixes list at FDV's website until EOL (July 2010). Any issues regarding the list should be addressed to me henceforth, for the duration. To be sure of a prompt reply, it would be great if you could PM me, as well as posting here. I'm a relative newcomer to HFSLIP, and like many of you I too have limits on my time. So in all likelihood I'll need your help, particularly regarding any unofficial updates that come along. That said, I aim to update the page within 3 days (at most) of the release of updates (a rod for my own back there ). Thanks PVU. The page will be corrected with that information shortly. Thanks to all past and future contributors, bristols bristols, thanks for picking this up. Time to deal with an official list was not on the agenda until June/July, so I'm glad you got it. Edit: britols, you got my the IE update. The old IE cumulative update was in your Obsoleted column. Sorry for that. By the way, that's a **** nice hotfix layout. Thanks again.

Tommy, I'll give it a whirl for Windows 2000. I'm not going to worry about 2000 Server, DirectX7, IE5. For February 2010: KB978251 Windows2000-KB978251-x86-ENU.EXE Replaces KB957097 KB975713 Windows2000-KB975713-x86-ENU.EXE Replaces Nothing KB978262 Windows2000-KB978262-x86-ENU.EXE Replaces KB973525 KB977914 Windows2000-KB977914-x86-ENU.EXE Replaces KB971557 KB975560 Windows2000-DirectX9-KB975560-x86-ENU.exe Replaces KB971633 (Windows2000-DirectX9-KB971633-x86-ENU.exe) KB978037 Windows2000-KB978037-x86-ENU.EXE Replaces Nothing KB971468 Windows2000-KB971468-x86-ENU.EXE Replaces KB958687 KB977165 Windows2000-KB977165-x86-ENU.EXE Replaces KB971486 KB978706 Windows2000-KB978706-x86-ENU.EXE Replaces Nothing March 9, 2010 edit corrects KB978251. KB978251 replaces KB957097. There are no March 2010 Windows 2000 Updates. Also, Windows2000-DirectX9-KB975560-x86-ENU.exe goes into HFSVCPACK_SW1

TP, I had a little time today to hit the updates. If you're done, I will post for the next few months, but I'm not planing on testing new updates, and I don't want to mess with an official list right now. I'm sorry about that, but I've got my hands full. We have 4 more months of 2K updates. When this is all said and done for 2K, I can take a crack at the final come June.

Tommy, I'll give it a whirl for Windows 2000. I'm not going to worry about 2000 Server, DirectX7, IE5. For February 2010: KB978251 Windows2000-KB978251-x86-ENU.EXE Replaces KB957097 KB975713 Windows2000-KB975713-x86-ENU.EXE Replaces Nothing KB978262 Windows2000-KB978262-x86-ENU.EXE Replaces KB973525 KB977914 Windows2000-KB977914-x86-ENU.EXE Replaces KB971557 KB975560 Windows2000-DirectX9-KB975560-x86-ENU.exe Replaces KB971633 (Windows2000-DirectX9-KB971633-x86-ENU.exe) KB978037 Windows2000-KB978037-x86-ENU.EXE Replaces Nothing KB971468 Windows2000-KB971468-x86-ENU.EXE Replaces KB958687 KB977165 Windows2000-KB977165-x86-ENU.EXE Replaces KB971486 KB978706 Windows2000-KB978706-x86-ENU.EXE Replaces Nothing March 9, 2010 edit corrects KB978251. KB978251 replaces KB957097.

Dave, the Canon issue has driven me a little crazy. My folks are on a Win2K system, and the Canon camera I got for them has new Canon software that wasn't intended for 2K (I can't get around new libraries calling on DOT NET 3). First off, you may want to look into CAM2PC. I think that Nikon gets the OK. For the Canon TWAIN driver, download TWAIN68.zip or TWAIN69.zip. Then get USBDeview from NirSoft. On a XP machine, plug your camera in and then run USBDeview to see what the device ID is. Then decompress the TWAIN zip file and hack up just 1 of the INF files in the WIN_2K98 folder to call on your camera. I haven't had time to really mess with CAM2PC. It did work great with an older Canon, but I haven't tried it with the new one yet. I intend to this weekend. But the hacked INF file in the TWAIN driver (to include my camera ID) did allow Windows to fully recognize my camera. For a quick fix, I installed Picasa, and Picasa worked well with the Canon TWAIN driver. The only downside is that Picasa creates a temp file for pictures you download - so you will have to copy over your pics before you close Picasa. But since it's not a Canon, your Nikon may not work with the Canon TWAIN driver. But for a very quick fix, I would try that CAM2PC. The only problem is that CAM2PC hasn't been updated for a while. jclaz, thanks for the info on MTP. I will look at the MS package since it is said to work on 2K - but there also seems to be a need for WMP10.

Thanks, Fred. I'll tell you that your public decision came on the heels of my (very) little Canon camera problem. The timing was "perfect" - which is to say that a mild depression set in. IOW, if you two Last Mohicans are making the move, it's probably time to get moving. I know that guy who had reservations about removing components in XP. And I certainly know who Blackviper is - one of the greatest services on the web - especially for newbies. I've been following your work ever since HFSLIP started. I cut my teeth on BV and FDV. For a guy who has a day job, the instruction has been great. There are a lot of folks who have put in solid work on this project, but a special thanks goes out to you and TommyP. In a way, I'm sad that 2K is headed out the door - it was (and is) a great OS. But there's no question that XP HFSLIPers will benefit. Again, a Big Thanks! And that really goes for keeping 2K very operable even today.

I saw that Fred was headed in that direction in 09 based on a 1 or 2 posts, so I'm not surprised. Would you guys mind telling us what it was that pushed you to go? My guess for FDV is that AHCI SATA support is partially the issue. UniATA development stopped in late 08. I haven't really had a need to go all the way for most of the computers I deal with, but I just got a Canon digital camera for my folks, and I am having to hack INF files on the software install. I have been able to hack Canon's latest (but not supported) TWAIN driver for WIN2K (to include the camera USB device ID). I was able to jury-rig the TWAIN driver to work with Picasa. I think I can hack up the full Canon software to work flat out, but we'll see. Canon software use to install a TWAIN driver for Win2K. They dropped that recently, and killed Win2K support. XP definitely plays better with USB cameras. The WIA is real easy. Are you guys pretty much done with 2K? TommyP has been the one keeping up with 2K updates. This is obviously good news for XP HFSLIPers.

Hi all. I have 1 basic question. Can you continue to apply hotfixes to your slipstreamed source folder? I'm 99% sure that you can, but I'm just checking. I just jumped from Office 2000 to 2003, and this program worked like a charm. Thanks, mara-. I plan to check out your Office Integrator project.

Thanks for posting this. I never choose to do a session restore anyway, so for those who want to kill this FF process, go here: http://kb.mozillazine.org/Session_Restore#Disable

http://www.kaspersky.com/scanforvirus Attention! Kaspersky Anti-Virus has detected a virus in the file you have submitted... Scanned file: 7_calc.exe - Infected 7_calc.exe - infected by Email-Worm.Win32.Agent.ggd Addition: Like you, I can't determine if it's a false positive. Sorry.

Tomalak, thanks for this thread. Are you using a modified cab for this? There's this one on this forum: http://www.msfn.org/board/index.php?s=&amp...st&p=812398 I'm putting together a Win2K disk. The modded cab looks OK.

Guys, thanks for the 2K3 list. That's grunt work that's probably beyond the call of duty. tommyp, for the 2000 list, the Windows2000-KB918118-x86-ENU.EXE update links to Windows2000-KB914388-x86-ENU.EXE It should be: http://www.microsoft.com/downloads/details...;displaylang=en

tommyp and fdv, very sweet. Thanks a bunch.

October 14, 2008 Updates MS08-060 Microsoft Security Bulletin MS08-060 – Critical Vulnerability in Active Directory Could Allow Remote Code Execution (957280) http://www.microsoft.com/downloads/details...;displaylang=en Replaces 953235 Microsoft Security Bulletin MS08-058 - Critical Cumulative Security Update for Internet Explorer (956390) For IE6 http://www.microsoft.com/downloads/details...;displaylang=en Replaces 953838 Microsoft Security Bulletin MS08-061 – Important Vulnerabilities in Windows Kernel Could Allow Elevation of Privilege (954211) http://www.microsoft.com/downloads/details...;displaylang=en Replaces 941693 Microsoft Security Bulletin MS08-062 - Important Vulnerability in Windows Internet Printing Service Could Allow Remote Code Execution (953155) http://www.microsoft.com/downloads/details...;displaylang=en Replaces Nothing Microsoft Security Bulletin MS08-063 – Important Vulnerability in SMB Could Allow Remote Code Execution (957095) http://www.microsoft.com/downloads/details...;displaylang=en Replaces 923414 Microsoft Security Bulletin MS08-065 – Important Vulnerability in Message Queuing Could Allow Remote Code Execution (951071) http://www.microsoft.com/downloads/details...;displaylang=en Replaces 937894 Microsoft Windows Malicious Software Removal Tool http://www.microsoft.com/downloads/details...;displaylang=en Edit/Add on 10/23/08 (Thanks Glenn9999) Microsoft Security Bulletin MS08-067 – Critical Vulnerability in Server Service Could Allow Remote Code Execution (958644) http://www.microsoft.com/downloads/details...;displaylang=en Replaces 921883

Dunno why support for Windows 2000 Professional and Windows 2000 Datacenter Server is not declared. But I see no difference between these editions of W2K, only different sofware packaging (client/server) and pricing, licensing. Here is a Intel Matrix Storage Manager log-file from Windows 2000 Professional: System Information Kit Installed: 7.0.0.1020 Kit Install History: 7.0.0.1020 Shell Version: 7.0.0.1020 OS Name: Microsoft Windows 2000 Professional OS Version: 5.0.2195 Service Pack 4 Build 2195 System Manufacturer: Intel Corporation System Model: DQ963FX Processor: Intel® Pentium® D CPU 3.00GHz BIOS Version/Date: Intel Corp. MQ96510J.86A.1738.2008.0617.0002, 06/17/2008 Serial ATA Information Intel Serial ATA Controller: Unknown Controller Number of Serial ATA ports: 4 Driver Version: 7.0.0.1020 Serial ATA Plug-In Version: 7.0.0.1020 Language Resource Version of the Serial ATA Plug-In: File not found ISDI Library Version: 7.0.0.1020 Hard Drive 0 Status: Normal Device Port: 0 Device Port Location: Internal Current Serial ATA Transfer Mode: Generation 2 Model: ST3320620AS Firmware: 3.AAD Native Command Queuing Support: Yes Size: 298 GB I'll gave you some other examples of such "commercial declared incompatibility": 1) Windows 2000 + Intel Chipset Graphics (945, 963, 965, 3 Series, 4 Series). There is no *official support* in this case. But the latest XP driver is working with W2K without problems. Install it through "Device Manager -> Update Driver..." Before installing this driver, as usual, install Intel's Chipsets INF Update. 2) Windows 2000 + ATI/AMD Radeon X300-X1950 Series Graphics (i.e. all pre-X2yyy Series). Use Catalyst driver version 7.4 from ATI/AMD site. 3) Windows NT 4.0 + ATI/AMD Radeon 9800-X300-X600 Series Graphics (i.e. all pre X1yyy series). Use one of drivers listed there: http://forum.radeon.ru/viewtopic.php?p=401081#401081 . 4) Windows NT 4.0 + Intel Chipset Graphics (915, 945 Series). There is no *official support* in this case. But the Intel Embedded Graphics driver version 5.1 is working with NT4. I can expand this list if I remember some more... Yeah, I know. That has certainly been the case for that 7.4 ATI graphics driver for Win2K. I don't know all of the ins and outs of the core drivers, but it's worked. In that particular case, even though they don't advertise 2K support, there remained a C2_44981.inf for Windows 2000. As a side note, the last 7 series driver that ATI advertises for XP is 7.12. I'm not sure why... Since the Intel SATA driver 7 worked for a version of Windows 2000, it would make sense that it would (or could easily) work for any version of 2K. The INF's don't place a restriction on the OS. But unlike the ATI 7.4 driver, there is no INF specifically labled for the OS. Concerning the Intel Matrix Storage Manager log-file, I'm assuming that you post installed the full Intel Matrix Storage Manager after pre-installing the driver. That's bit surprising. I can see pre-installing the driver, but I'm surprised that the post install of the full storage manager worked. That's good news (assuming your BIOS and Board can handle it in the first place). Fernando 1 is a pretty astute guy. I've worked with him before. His take that Windows 2000 really can't take advantage of the Intel AHCI (SATA) driver is interesting. On this point, I wonder if there really is a performance gain to be had using the SATA driver (as opposed to using just the base INF chipset driver) for Windows 2000. It's also interesting that he indicates that the (latest) Intel ICH8/ICH9 SATA AHCI Controllers are not supported by any official Intel textmoding pre-install for XP. The "readme" files indicate that. He's modified the latest driver, but it looks like Mr. Softie is really pushing Vista. You got this above in your modified driver remarks. Thanks

Download: http://downloadcenter.intel.com/Detail_Des...ms〈=eng Release notes: http://downloadmirror.intel.com/15449/ENG/...ase%20notes.htm ReadMe: http://downloadmirror.intel.com/15449/ENG/readme.txt It is also supports ordinary ICH8 in AHCI mode (not listed above). You have to patch some inf's to achieve this ICH8 support IMSM AHCI V7.0.0.1020 (Patched), download: http://rapidshare.com/files/30169630/AHCI_...r_ICH8.zip.html I have a *success* installing Windows 2000 Professional in AHCI Mode with Intel® Desktop Board DQ963FX ICH8-Based mobo. Starting with ICH9 there is NO support for Windows 2000 in AHCI/RAID mode via Intel Matrix Storage Manager. Very SAD. :( bear, that version 7 (unmodified) may get it done, but Windows 2000 Pro is not listed as supported. Windows 2000 *Advanced Server* is. Not really sure why they would go to the trouble of making it work for a server and not Pro (although I can guess that maybe Intel took marching orders from Mr. Softie). Thanks for the modified version. That's a keeper. Next time I get a chance, I'll give it a whirl. As far as the unmodified version is concerned (attached), eanon, your mileage may vary. Let us know how this works out for you. You guys may also want to check out Fernando 1's thread within the nLite forum just for fun. iata70.7z

I think the short answer is no - not that I know of. If you're not worried about AHCI, will the latest Intel INF chipset software work? If so, I wouldn't worry about AHCI. That hardware will eat up Win2K without AHCI. If the latest Intel INF chipset software won't work, you can mess around with the Universal ATA driver for Windows. Sorry for the US/English link to the Chipset software...

fdv did an all encompassing September updates in the XP hotfixes thread. This is specific for Windows 2000 (Server 2000 not included). You got 'em. Sept 9, 2008 Microsoft Security Bulletin MS08-052 – Critical Vulnerabilities in GDI+ Could Allow Remote Code Execution (954593) http://www.microsoft.com/downloads/details...;displaylang=en It replaces KB938127 Sept 9, 2008 Microsoft Security Bulletin MS08-053 – Critical Vulnerability in Windows Media Encoder 9 Could Allow Remote Code Execution (954156) http://www.microsoft.com/downloads/details...;displaylang=en It replaces nothing I don't think anything else was posted for September.