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.