• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About luke123

Profile Information

  • OS
    none specified
  1. Yes, you can take these files for the nLite textmode driver integration procedure, but you can use the 32bit RST driver you get from >here< as well. The content is exactly the same. Worked like a charm and just completed my first slipstreamed XP installation. Many thanks for your assistance and advice, Fernando.
  2. One more newbie query, Fernando, if I may. After integrating the RST 32bit (for XP) driver with nLite, is there a simple way to test (or find out) I've done things correctly? I mean, the last thing I want is to go through the whole XP installation process (with BIOS SATA mode set to AHCI), only to be greeted by a BSOD? Or will the BSOD occur early during installation if the integration has been done incorrectly? I do know that F6 shouldn't be pressed when using a slipstreamed nLite with SATA driver integration. Thanks again!
  3. No, the complete RST package, which includes the RST driver and the RST Console software, is not "universal":The RST driver is only needed, if your system has an actual Intel Southbridge from ICH7R/M up, which is running in AHCI or RAID mode. All other Intel related systems neither need nor are able to use the RST driver and the complete RST driver/application package. The Intel RST Console software can easily be installed by running the EXE file once the OS is up, but I only recommend to install it, if your are using the SATA Controllers in RAID mode. Does the Intel 945GC chipset fit the above criteria and can use the RST driver?
  4. Answers:2. If your SATA hdd is running in AHCI or RAID mode, you have to integrate just the small driver package. You can take the link to the v9.6.0.1014 WHQL certified 32bit (for XP) or 64bit (for XP x64)one. Should I use only the files in \Drivers\x32 (from the extracted RST package v9.6.0.1014 you provide) for integration? This will be my first nLite exercise, so please excuse my newbie questions! Thanks again.
  5. Trying to answer my own query (1), should I simply use the files in \Drivers\x32 (from the extracted RST package v9.6.0.1014 you provide - see above quote) for the SATA/AHCI driver only? Can this small package work with both the HM57 Express and 945GC chipsets? Thanks in advance!
  6. Answers:1. Yes, but it is a new technology and not only a new name. 2. The v9.5.6.1001 drivers do support all ICH SATA RAID and SATA AHCI Controllers from ICH7R/M up. 3. Yes. Here is the TXTSETUP.OEM line: iaAHCI_8MEM = "Intel(R) ICH8M-E/M SATA AHCI Controller" And here is the HardwareID line of the IAAHCI.INF for ICH8M (mobile) chips: %PCI\VEN_8086&DEV_2829&CC_0106.DeviceDesc% = iaStor_mobl_Inst, PCI\VEN_8086&DEV_2829&CC_0106 I found the above post in Jan 2010 which presumably answers my query (3). In particular, would the Intel 945GC chipset be supported by the Rapid Storage drivers?
  7. Fernando I want to install Windows XP 32-bit on a Dell Vostro 3400 notebook with the Intel HM57 Express chipset and a Core i3-330m CPU. Having read through your excellent guide in the very first post, I wonder if you might offer a few pointers regarding the following: (1) Which small driver package should I use for the HM57 Express, or do I need the complete Intel Rapid Storage package? (2) If the complete Intel Rapid Storage package is needed, is there a step-by-step guide to accomplish the integration? I downloaded the latest package from Dell's support site but am not sure what files/folders to integrate with nLite. (3) Is a complete Intel Rapid Storage package "universal" in the sense that it can be used on all desktop/notebook motherboards with any Intel chipset made in, say, the last four years? Thanks in advance for your feedback and advice. Luke
  8. Well, if I am "MSFN SuperB", for basic equal opportunities reasons Tripredacus must be referred as "K-Mart-ian Legend" . jaclaz Sorry, jaclaz. I was so relieved that I mistyped your handle...
  9. Bingo! After I uninstalled Ext2 IFS for Windows, the two FAT16 partitions become hidden again. Thanks, MSFN SuperB and Tripredacus, for your pointers!
  10. Yes, I did install EXT2 IFS for Windows about two weeks ago, but the "loss" of the two partitions' hiddenness only happened a few days ago. Strange...
  11. Thanks for your feedback, jaclaz. I recently installed Eraser 6.07 and suspected this might be the cause, but its developer said otherwise. I'm not familiar with dosdev but am reading about it now. The challenge: how do I reverse whatever was done so that the previous "hidden" state can be reverted to?
  12. Hi I've a Dell pc with a small, hidden diagnostic FAT16 EISA partition, before the Windows partition, on the system drive. Starting a few days ago, this formerly hidden partition appears to have become visible to Windows XP which automatically assigns it a drive letter. I used the command "mountvol /d" to remove such newly created drive letter, but it reappears everytime Windows boots or restarts, even in Safe Mode. Has anyone experienced anything similar? Is it possible that a certain registry setting relating to the (formerly) hidden partition has somehow been altered? If so, how can this be reversed so that no drive letter is assigned automatically to the (formerly) hidden partition? An interesting observation is that, in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices, there is no \DosDevices\{x} (where {x} is the drive letter) which corresponds to the drive letter now assigned to the (formerly) hidden partition. I cannot use the Disk Management MMC Snap-in to remove the drive letter assignment, since selecting the partition and right-clicking only brings up a single "Help" line in the context menu, without any of the usual options (like "Change Drive Letter and Paths..."). By way of background, my current system drive was made by cloning the original system drive over a year ago. The latter is now used as an internal second drive. After the cloning exercise, the Dell hidden FAT16 diagnostic partition on the second drive (the previous system drive) was set to type 16 using PTEDIT32, whilst that for the current system drive remains as DE. Until recently, both these FAT16 partitions have stayed hidden to Windows XP and, for example, do not appear as drives/partitions when the disk defragmentator is used (although they can be viewed in "Disk Management", without any assigned drive letter). Checking with PTEDIT32 shows the DE and 16 type settings for the two partitions remain unchanged. Thanks in advance for any suggestions and feedback! Luke