Welcome Guest.   Make a donation to an author on the site December 20, 2014, 09:08:04 AM  *

Please login or register.
Or did you miss your validation email?


Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.


You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
 
The N.A.N.Y. Challenge 2013! Download dozens of custom programs!
   
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Where do i find the SATA Controller !  (Read 5019 times)
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« on: October 19, 2011, 07:11:59 AM »

Hello folks, i  need some suggestion here . U see i want to install Win2000 in a SATA HDD and i later came to know it requires SATA Controller. I have Win 2000 Sp4 Retail CD, i plan to do the installtion prior to 2000 Installation maybe integrate it in the CD itself.
    So somewhere i read CPUID would show  the SATA  Controller. I got the snapshot : is this the Controller i should looking for.
   
    SATA
   

  This is the first time i have tried to do this. Any suggestion from any fellow dontioncoder would be great.
   
After rrunning Belarc Advisor it showed the Controllers as:
Standard floppy disk controller
Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Primary IDE Channel [Controller] (2x)
Secondary IDE Channel [Controller] (2x)

    So what should i look for. ???
   
Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
4wd
Supporting Member
**
Posts: 3,528



see users location on a map View Profile Read user's biography. Give some DonationCredits to this forum member
« Reply #1 on: October 19, 2011, 07:49:10 AM »

You would probably be better off going into the BIOS and changing the SATA interface to IDE mode rather than trying to find SATA drivers for Windows 2000.

That will pretty much guarantee it works with Windows 2000 because it's extremely doubtful whether any of the advanced features of SATA, (NCQ, AHCI, etc), would be available in drivers that old.

Of course, that's assuming that the BIOS has that option:


EDIT: These drivers supposedly work with Windows 2000.

Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0

It's that one.
« Last Edit: October 19, 2011, 07:57:38 AM by 4wd » Logged

I do not need to control my anger ... people just need to stop pissing me off!
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #2 on: October 19, 2011, 08:23:23 AM »

 I have already downloaded a bunch of  SATA Controllers just after Googling Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0: and their is a readme.txt for integrating it prior to installation .

yeah i downloaded that Controller too ,a beatiful thank you to you.

So you say its possible.
I found the Onboard SATA Controller : its enabled for time being.
Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #3 on: October 19, 2011, 11:06:01 AM »

EDIT: These drivers supposedly work with Windows 2000.

Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
It's that one.

      Please help me with this: i want to lipstream this in Win 2000 SP4 Retail CD but the readme.txt from the zip files says these:

So i need to make a directry under I386\OEM\$$\INF,  what does the $$ sign signify here. Its making it more complex. How much folder do i need to make. ???

[copy or print]
************************************************************
* 8A.  INSTALLING THE WINDOWS* 2000 INF FILES PRIOR TO
*      OS INSTALLATION
************************************************************
NOTE: The Windows* 2000 OEM Preload Kit distribution CD
      contains a setup directory with all the base operating
      system setup files and installation programs
      (WINNT.EXE and WINNT32.EXE). 

The name of the directory may vary depending on the
distribution CD (e.g., \I386\).

1.  Create the following directory structure under the
    <WIN2000 Setup Directory>:

       \$OEM$\$$\INF

2.  Copy the Windows* 2000 INF files from
    <INF Extract Directory>\Win2000 to the directory
    created in Step 1 above:

       <WIN2000 Setup Directory>\$OEM$\$$\INF

3.  Create the following directory structure under the
    <WIN2000 Setup Directory>:

       \$OEM$\$1\drivers\IntelINF

4.  Copy the Windows* 2000 INF files and the catalog files
    (.CAT) from <INF Extract Directory>\Win2000 to the
    directory created in Step 3 above:

       <WIN2000 Setup Directory>\$OEM$\$1\drivers\IntelINF

5.  Either modify the default Windows* 2000 installation
    answer file, UNATTEND.TXT, located in <WIN2000 Setup
    Directory>, or create a customized answer file. The
    answer file must include the following information:
   
       [Unattended]
       OemPreinstall = Yes
       OemPnPDriversPath="drivers\IntelINF"

    A sample answer file for preloading the Intel(R) Chipset
    Software Installation utility files is available at:
    <INF Extract Directory>\Win2000\INFAnswr.TXT
   
    For more information about Windows* 2000 answer files
    and unattended installations, please refer to the
    Microsoft* Windows* 2000 Guide to Unattended Setup.
    If you are a computer manufacturer, refer to the
    Microsoft Windows* 2000 OEM Preinstallation Kit (OPK)
    User Guide for more information about the \$OEM$ folder.
    Otherwise, refer to the Microsoft Windows* 2000 Deployment
    Guide.

6.  Run "WINNT.EXE /u:<answer file name> /s:<WIN2000 Setup
    Directory>" to install Windows* 2000.


Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
4wd
Supporting Member
**
Posts: 3,528



see users location on a map View Profile Read user's biography. Give some DonationCredits to this forum member
« Reply #4 on: October 19, 2011, 10:00:48 PM »

$OEM$ directory contains any OEM specific files for installing Windows, eg. specific interface drivers, extra programs, etc, etc.  These files are copied to the destination drive at installation time - where they're copied depends on the sub-directory they're in under the $OEM$ directory.

$OEM$\$1 = The root directory of the installation drive, eg. C:\
$OEM$\$$ = Windows directory, eg. C:\Windows

So, (assuming C: is the drive you're installing to):
\$OEM$\$$\INF = C:\Windows\Inf
\$OEM$\$1\drivers\IntelINF = C:\drivers\IntelINF

When W2K is installed, the files in the $OEM$ directories on the installation media, (CD, etc), will be copied into the corresponding directories on the destination drive.
The Intel .inf files are written to look for the driver files, (.sys, etc), in the \drivers\IntelINF on the destination drive when they are to be installed.  After the system is completely installed, that directory could be deleted.

The UNATTEND.TXT file tells the Windows setup program to look for and install the driver files contained in IntelINF before doing anything else - this is so necessary hardware is available when it comes to installing Windows.

In this case, the Intel SATA drivers will be installed before anything else - this should make any HDD connected to the SATA interface available for installing Windows on.

To install W2K then you need to run: "WINNT.EXE /u:UNATTEND.TXT /s:<WIN2000 Setup
    Directory>" where <WIN2000 Setup Directory> is the location of the W2K setup files, (CD, etc), eg. D:\

For more on the $OEM$ folders, look here.
For more than you could ever wish for on unattended installation, MSFN forums are the place to go.
In your case: Unattended 2000/XP/2003


So, to answer the question, in steps:

1) Create an image of the W2K install CD, (using ImgBurn, etc), in ISO format.
2) Using UltraISO or similar, open the ISO and create the necessary directories: $OEM$\$$\Inf and $OEM\$1\drivers\IntelINF
3) Copy the appropriate files into each directory.
4) Create the UNATTEND.TXT file with the three lines given and then copy it into the root of the install media.
5) Save the modified ISO and then write it to a CD-RW, (saves wasting CDs if something went wrong).

I don't know how W2K is installed but you should be able to run the necessary command to start installation, (assuming D:\ is the CDROM drive):

winnt.exe /u:UNATTEND.TXT /s:D:\

On the CD, besides the normal Windows setup files, you should also have:
« Last Edit: October 19, 2011, 10:35:12 PM by 4wd » Logged

I do not need to control my anger ... people just need to stop pissing me off!
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #5 on: October 25, 2011, 10:29:19 AM »

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


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:
[copy or print]
; ****************************************************************************
; ****************************************************************************
; **    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.

undecided
    

  ohmy4wd 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.  Sad

Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
4wd
Supporting Member
**
Posts: 3,528



see users location on a map View Profile Read user's biography. Give some DonationCredits to this forum member
« Reply #6 on: October 25, 2011, 06:47:57 PM »

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.
Logged

I do not need to control my anger ... people just need to stop pissing me off!
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #7 on: October 27, 2011, 08:37:43 AM »

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



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

Ohhh : what would you do 4wd
Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
Shades
Member
**
Posts: 1,696


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #8 on: October 27, 2011, 09:26:52 AM »

@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.

 
Logged
4wd
Supporting Member
**
Posts: 3,528



see users location on a map View Profile Read user's biography. Give some DonationCredits to this forum member
« Reply #9 on: October 27, 2011, 06:44:52 PM »

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.
« Last Edit: October 27, 2011, 07:53:04 PM by 4wd » Logged

I do not need to control my anger ... people just need to stop pissing me off!
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #10 on: October 29, 2011, 12:46:55 PM »

I think its too complicated with nLite, i tried it once:(it is too confusing may be i 'll check with that later) and proceeding to format and delete the partition and recreating would prove too expensive in my time, i been their without installing the SATA Controllers it wasn't good :i had to redo the partition table.
       huffff...... may be i will giveup this madness for trying WIn2000 on a new PC after all its a 12 year old OS and with limited feature like xp does. Latest games wouldn't run in Win 2000 after all, XP still is good for me. smiley  Thmbsup
        Here i rest my case, thank you all for trying to help me especially 4wd who was at the start of this thread, i have taken a printout of all the comments for future reference, dont know when it would prove valuable again...!!!
    
        
Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
Ath
Supporting Member
**
Posts: 2,303



see users location on a map View Profile WWW Give some DonationCredits to this forum member
« Reply #11 on: October 29, 2011, 01:24:42 PM »

may be i will giveup this madness for trying WIn2000 on a new PC

It would help (me that is, or at least clarify) if you could give a reason for trying to install that old, no longer MS-supported, OS on any system.
Even on old hardware I wouldn't install Windows 2000, it'd be either some form of Linux or Win XP, if performance is the bottleneck.
Logged

Shades
Member
**
Posts: 1,696


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #12 on: October 29, 2011, 05:19:56 PM »

I did install Windows 2000 (+SP4) actually...on a 11 year old HP laptop, which actually runs rather fine and stable. And with 128Mb of RAM XP is not a real option, just as more recent Linux distro's. After it is booted up it consumes 64Mb RAM, leaving a whole 64 Mb RAM to play with  Wink

And I believe that with some TLC I can get several years more out of it, running 2000. As it is not connected to the interweb, there is not a lot of reason to be afraid it will run into the ground.

Believe it or not, I worked for a company in Holland which is always on the lookout for 286 PC's. Several sections have such harsh conditions that newer processor models cannot handle. And I was parked inside those environments for 8 working hours a day. Each 30 minutes you were allowed a 5 minute break...so you would not freeze up too much.

I just want to say that for some there is literary no other option than to run old hardware and as a consequence also old O.S.'s
Logged
hulkbuster
Participant
*
Posts: 218


see users location on a map View Profile Give some DonationCredits to this forum member
« Reply #13 on: November 27, 2011, 09:21:17 PM »

i just wanted to bring to the users and the OP notice who commented here, last time i integrated SATA controller of a small ASUS notebook by using nLite and upon booting for the setup process  it recognised the Disk's and the Partitions, and i was then able to format the disk and install XP, but in my case i wanted 2000 to be installed in a SATA Controller disk which would not recognise the disk and the partition at all, too bad now i can completely relax and give away this urge to install Win 2000 on a SATA Disk, from my first hand experience.
Logged

Autorun Virus Remover.V.2.3 / Look n Stop Firewall.v2.07 / Sandboxie.v4.08  / Some Sense
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
 
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.042s | Server load: 0.26 ]