Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

Community Reputation

31 Excellent

1 Follower

About daniel_k

Profile Information

  • OS
    Windows 7 x64
  • Country


  • Country Flag

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here is the latest/last driver for XP, which fixes the KRACK vulnerability. 1030.31.0102.2018 (Nov 6, 2018)
  2. @jaclaz Pretty sure this is a driver feature. Basically it does what certain USB to SATA bridge controllers do. It detects the disk geometry and automatically changes the sector size reported to Windows according to the table I've posted earlier. At the same time, it "combines" as many 512 bytes sectors as need to match the sector size reported. The driver has some kind of protection. I've almost got it to work: currently only detects optical drives.
  3. Hopefully @Snear is able to test the drivers I've posted here (specially the v3.1 ones). Thanks for the Acer link, it's exactly the same driver I've packaged. I'm sure this AHCI/RAID driver written by Promise automatically changes the sector size according to the disk size. Found an article on Promise's KB regarding support for disks larger than 2TB: For this logical drive size | Select this sector size Up to 16 TB | 4096 bytes (4 KB) Up to 8 TB | 2048 bytes (2 KB) Up to 4 TB | 1024 bytes (1 KB) Up to 2 TB | 512 bytes (512 B) Understanding the 2 TB Limit in Windows Storage TechNet article has comments from owners of Promise products that confirm 7.5 TB disk being usable with Windows 2000 Server.
  4. NAPA is the codename of the SATA controllers using Promise's IP. Sure I can use 7-Zip. Replaced .rar with .7z package. I'm use WinRAR because of the Recovery Record feature for safety reasons.
  5. It's clear that there is something really special in the AHCI driver. Controllers with the following IDs are from NAPA series: PCI\VEN_1002&DEV_4391 PCI\VEN_1002&DEV_4392 PCI\VEN_1002&DEV_4393 PCI\VEN_1002&DEV_4394 PCI\VEN_1022&DEV_7801 PCI\VEN_1022&DEV_7802 PCI\VEN_1022&DEV_7803 PCI\VEN_1022&DEV_7804 AMD licensed Promise's IP for use with their chipsets, there are Promise strings inside the driver (.sys) and the coding is really close to Promise's own FastTrack series drivers. At that time the USB controllers used NEC's IP and the drivers are really similar. They've put the same driver in different folders just to make it clear both chipsets are supported. What is the error message you get when installing V3.1.1540.127? I've put together my collection of AMD drivers, please confirm that the included v3.1.1540.86 is the same as the one you're using. Included versions are: - 3.1.1540.103, 3.1.1540.123, 3.1.1540.151, 3.1.1547.124 - 3.2.1540.24, 3.2.1548.37 - 3.3.1540.40 - (supports Intel controllers, not WHQL for XP) http://www.mediafire.com/file/22ainwe5hip0sv4 Please try them all.
  6. Just tested with BWC's Extended Core and the XHCI USB3.1 driver also has issues with PAE enabled. What a shame. Will update first post with this info.
  7. 32-bit and 64-bit XP drivers can be found here: https://www.win-raid.com/t4035f45-Windows-XP-Bit-and-Server-Bit-on-Modern-Hardware-264.html#msg100534
  8. - Installed Windows 2000 SP4 (with drivers integrated) in MPS Multiprocessor mode (ACPI doesn't work here) on VirtualBox. - Followed the instructions in this question: exporting a virtualbox VDI to a harddrive to boot it natively - Plugged in a PS/2 keyboard, booted Windows 2000 and proceeded with all driver installs. - Used the Composite devices solution outlined here: Universal Serial Bus (USB) Interface drivers (scroll down) - And the result is: Driver works fine with both Intel and VIA controllers.
  9. About testing: - Unfortunately I don't have any optical driver to install Windows 2000 on my Coffee Lake PC, as USB-based install won't work with drivers integrated. - Both drivers were tested on VirtualBox with no issues. - Both drivers passed XP SP3 testing on my Coffee Lake PC with absolutely no issues, even USB-based install was possible.
  10. In this topic I'll post my modified drivers for Windows 2000 with SP4 (no Updates Rollup or Extended Kernel needed). For testing purposes only, so beware. If considered stable, will be promoted to Final. - Intel Matrix Storage (AHCI/RAID) Driver only: Win2000_7.6.9.1002_DriverOnly.7z Complete package: Win2000_7.6.9.1002_Complete.7z This one is slightly newer than BWC's, with a few fixes. - AMD(Hudson?) / Intel / VIA XHCI USB3.1 driver Driver only: 276BETA_W2K.7z Has the same issues with PAE as XP. Don't know if Windows 2000 is also affected by qword ACPI issue (the XHCI controller won't initialize and reports Error code 10). In this case, please try it in MPS Uniprocessor/Multiprocessor mode.
  11. @dencorso, please delete this topic. Didn't test it thoroughly on Windows 2000, can't boot with this driver. Only works for "data" drives. Haven't ever seen this behavior, that is ridiculous.
  12. There is a reason for everything. This version, was the latest I've found to be working as a generic AHCI driver, anything newer only works with ASMedia controllers. If I didn't change the filename, one has a system with an ASMedia controller (onboard or external PCIe card) and decide to update its driver, would render the system unbootable. That's a personal opinion, most drivers have the same filenames for both architectures. Fine by me. Random filename for attached files is a known issue with Win-RAID's forum.
  13. @jaclaz, the driver itself (.sys) was not modified, everything else was. It's just because some guys are "rebranding" (editing strings and resources) and redistributing my modified files as if they were theirs.
  14. It's an original, unmodified ASMedia driver, which was developed as a generic driver (doesn't do any device checks): - uses SCSIPORT.SYS, so it is compatible with Windows 2000/XP and doesn't require integration of STORPORT.SYS (possible on XP only). - performance is fine, seems stable so far, supports 48-bit LBA and maybe up to 8 ports (6 tested here). - original 32-bit (x86) device property sheet didn't support Windows 2000, so I've coded my own version to support the OS, plus it asks to restart Windows if setting is changed. There are only two limitations: - Optical drives are seen as "ejectable" drives and shown in Safely Remove Hardware icon. - If you disable AHCI port 0, ATA and SMART atributtes cannot be read in utilities such as AIDA64. Download at https://www.win-raid.com/t5753f45-Generic-SCSIAHCI-driver-for-Windows-XP.html
  15. Edited first post, it should now be clear. - Supports all Intel USB 3.1 XHCI controllers (7, 8, 9, 100, 200 and 300 series, maybe even HEDT chipsets).
  • Create New...