ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > General Software Discussion

Where do i find the SATA Controller !

<< < (2/3) > >>

hulkbuster:
4wd : i followed everthing as you have shown in the snapshot, but couldn't get it anywhere. Really
--- End quote ---


But i managed to get my hands on a Floopy Drive i think i will forget about Slipstreaming it into a Disc.
I Downloaded Intel Chipset Driver 7.2.2.1006.zip.
  So i believe this too is the SATA Controllers Drivers for Win 2000.
  
  
  So i just copy/pasted it into the A:\ it was merely 480 KB in size, during setup i pressed F6 key to install the controller. After a while it prompted to install it from A:\
    It said txtsetup.oem is missing, which later i made it and wrote something like this.
    
    [Unattended]
    OemPreinstall = Yes
    OemPnPDriversPath="drivers\IntelINF"
    ;;; DriverSigningPolicy = Ignore ; optional
    
    Then later i ran the setup and then when it prompted to run from A:\ Drive it gave this error.
   " Line 1 of the inf file is invalid.
    Setup cannot continue.
    Press any key to exit." :huh: :huh: :huh:



infanswr.txt Contained the following txt:

--- ---; ****************************************************************************
; ****************************************************************************
; **    Filename:  INFAnswr.txt
; **    Abstract:  Windows* 2000 installation answer file to enable
; **               Intel(R) INF file preload.
; **    Last Update:  Sept 12, 2003 (Version 6.0.0 Build 1001)
; ****************************************************************************
; ****************************************************************************


[Unattended]
    OemPreinstall = Yes
    OemPnPDriversPath="drivers\IntelINF"
    ;;; DriverSigningPolicy = Ignore ; optional


; Copyright (c) 2000-2003 Intel Corporation
; Copyright (c) 1993-1999 Microsoft Corporation

; ************************************************************
; Intel is making no claims of usability, efficacy or
; warranty.  
; ************************************************************
; Information in this document is provided in connection with
; Intel products.  No license, express or implied, by estoppel
; or otherwise, to any intellectual property rights is granted
; by this document.  Intel assumes no liability whatsoever,
; and Intel disclaims any express or implied warranty,
; relating to sale and/or use of Intel products including
; liability or warranties relating to fitness for a particular
; purpose, merchantability, or infringement of any patent,
; copyright or other intellectual property right.  Intel
; products are not intended for use in medical, life saving,
; or life sustaining applications.

; ************************************************************
; Intel Corporation disclaims all warranties and liabilities
; for the use of this document and the information contained
; herein, and assumes no responsibility for any errors which
; may appear in this document, nor does Intel make a
; commitment to update the information contained herein. Intel
; reserves the right to make changes to this document at any
; time, without notice.
; ************************************************************
; ************************************************************

; * Third-party brands and names are the property of their
; respective owners.

:-\
    

  :o4wd can you tell me what do i need to do further. With all the rigs and Controllers in place it is not helping me much in my work.

If too much of a trouble i would better give up the effort.  :(

4wd:
That file, infanswr.txt, is not a TXTSETUP.OEM file - that's the UNATTEND.TXT example file they mention in the readme of the other driver zip.

TXTSETUP.OEM is a lot more involved than the simple UNATTEND.TXT.

Try this or this to create a floppy.

hulkbuster:
 :o 4wd i tried the links you provided , but i still get the same reading when i do the setup of Win 2000

Where do i find the SATA Controller !

Just can't figure out what to do next, man.

Ohhh : what would you do 4wd

Shades:
@hulkbuster
I think it would make your life easier if you downloaded a tool called nLite.

That is used to create bootable Windows CD's (nLite supports XP and Windows 2000).
What is good from this software is that it lets you alter things, it enables you to add/remove Windows applications, adjust standard folders, add/remove default drivers, add/remove service packs, unattended installation etc.

The adding/removing default driver part is interesting in your case. Don't play with the other functionality unless you really understand what you are doing and are able to reverse the damage you can do yourself.

It is all wizard driven, so if you have an original Windows 2000 installation CD, create a new one but with the driver you have downloaded. Have done the same myself (but for XP) for a computer that supported SATA, but that particular SATA controller was not recognized by Windows, requiring me to use/create a Floppy Disk with the particular driver on it.

After I was done that PC could be installed from my new bootable CD without any intervention on my part anymore.

 

4wd:
What would I do?

That's easy...use one of the IDE drives sitting around in my cupboard gathering dust to install on, then install the SATA drivers, then clone it to the SATA drive.

Or do what Shades suggested and use nlite.

BTW, it'd help if we knew what we were looking at with that picture.

ie. How many drives are in the machine and what are they, SATA/IDE ?

If it's just the one SATA drive, then the drivers have been loaded correctly, so you can create partitions and format the drive to continue installation.  Because W2K was around before SATA really took off, the drivers probably put the interface into IDE Compatibility Mode for W2K, so it will show up as an ATAPI drive.

If they didn't load you wouldn't see the drive at all.

You also need to remember that if the drive you're using was previously used for XP or later then it probably uses a later version of NTFS, (assuming NTFS formatted), than W2K - as such it will possibly show up as Unformatted or Damaged as far as W2K is concerned.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version