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

  • Last visited

Community Reputation

0 Neutral

About guinea

  1. Hard-Drive Boot?

    John... OK, I'll take the VM thing under advisement. But are you suggesting that I CAN use the setup.exe (over 1 mb in size) that is in my slip-streamed XP dir, for initiating the installation? Or are you just wishing me luck in trying any of the execs under the tree, in an attempt to install the slip-streamed XP?
  2. Hard-Drive Boot?

    I've gone thru the full process of creating a slipstreamed XP XP3, but DID NOT create an ISO. I did this on my C: Drive, which has a full Microsoft XP XP2 installation. I have 2 other empty logical partitions on the Drive, and now want to install the slipstreamed version onto either of those drives Can I do this directly with the "setup.exe" that is in the slipstreamed XP root directory, or some other file? I don't want to create an ISO and CD -- I just want to install from the Hard Drive.
  3. Integration of Intel's SATA AHCI and RAID drivers

    Sorry 'bout the funny characters in my 1st post on this site (or any site!). I'm even having trouble gettin' back to my own post! In response to your 4th answer -- QUOTE: Textmode drivers for all pre-Vista Operating Windows Systems have a file named TXTSETUP.OEM, whereas PnP drivers just have one or more INF files (files with the extension ".INF" UNQUOTE -- I guess my original question needs elaborating. When a driver package is downloaded from the Web, as with the Intel 945 Express Chipset, an installation utility can "install" the drivers, if the drive is under the umbrella of a working OS. But one can ALSO download the floppy drive to use during the OS installation process by pressing F6. And the 3rd (unmentioned) is the installation of the drivers with inf files. In the case where a new drive is installed on a computer, and only one drive is present, one must install with either a floppy drive (the floppy drive image which was downloaded) or by slipstreaming (the TxtSetup.oem file from the Floppy drive, and its associated files). [Correct me if wrong.] Lets assume that all worked fine, and XP is now installed successfully. When the system now boots, in normal day-to-day activity, how is the drive recognized? Does it need the same txtSetup.oem file to do the whole process again? Or are there lower-level files which conduct the communication to the SATA Host Controller? And again... how do we, as end users, know which route to choose, when integrating drivers into an Installation CD? When given a choice of slipstremaing INF files and associated SYS files, or slipstreaming txtsetup.oem files, INF files win, HANDS DOWN! (use nLite). But how do I know that an INF file is going to do the job? How do I know that I DON'T need to dig further into the Web, to find a Floppy Drive image with txtsetup.oem. Does your response to my question 3 mean that ALL SATA Mass Storage Controllers might need txtsetup.oem / floppy, but never INF files during OS installation? And txtsetup.oem files are never (never is such a harsh word) required for sound boards/nics/scanners/ and the like? If so, I'm finally starting to understand. thanks again.