device manager reading IDE as a SCSI

[anonboy]

I've got a 40 GB white label IDE hard drive thats listed under Disk Drives in Device Manager as:

MDT MD40 0EB-00CPf0 SCSI Disk Device

It's hooked up on the primary IDE channel on the end of the cable. Also had to use a third party IDE Controller when I installed 2k since the install disk doesnt have an onboard ATA controller

Thats listed under SCSI and RAID controllers in Device Manager as:
Win2000 Promise Ultra100 (tm) IDE Controller (PDC20265)

I -think- this is what's causing some slow performance in my Athlon machine, some weird stuff is going on. Like...when i save, or click to rename, or right click for properties performance gets really choppy and for some reason my comp checks my zip drive.

Maybe not though, but why is device manager reading my IDE drive as a SCSI? That doesnt seem to make any sense to me.

Thanks for the help!

 

[Kartajan]

The controller and drive show up as SCSI due to the way that windows handles some types of controllers.
The SCSI indications on the controller and HDD are NORMAL.

The way that you wrote suggests that this is a clean install of 2k, which kills my first guess as to the source of your problem.
Maybe you have something set strangely in your BIOS? Check BIOS settings to ensure they are valid, and if the controller has a BIOS that you can check on start up- check those settings as well.

the way that you stated your install sequence seems a bit... odd. Walk us through it again, step by step. This could shed light on your actual problem's source.

help any?

 

[anonboy]

I dunno if i did anything out of the ordinary...just put the cd in and booted into it, then i pressed F6 when it prompted me for a third party controller at the beginning then went from there, nothin out of the ordinary i can think of. Partitioned the entire drive as NTFS, etc

Here's what my BIOS looks like currently:

Main
----
System Time [21:00:00]
System Date [03/30/2003]
Legacy Diskette A [1.44M, 3.5 in.]
Legacy Diskette B [None]
Floppy 3 Mode Support [Disabled]

Primary Master [Auto]
Primary Slave [Auto]
Secondary Master [Auto]
Secondary Slave [Auto]
>Keyboard Features
Boot Up Numlock Status [On]
Keyboard Auto-Repeat Rate [12/Sec]
Keyboard Auto-Repeat Delay [1/4 Sec]

Language [English]
Supervisor Password [Disabled]
User Password [Disabled]
Halt On [All Errors]
Installed Memory 512 MB

Advanced
----
Current CPU Speed [750Mhz]
Operating Frequency Setting [750 Mhz]
CPU Clock Multiplier [7.5x]
FSB Frequency [100 Mhz]
DRAM Frequency [133 Mhz]
System Performance Setting [Optimal]
CPU Vcore Setting [Auto]
CPU Level 1 Cache [Enabled]
CPU Level 2 Cache [Enabled]
BIOS Update [Enabled]
PS/2 Mouse Function Control [Auto]
USB Legacy Support [Auto]
OS/2 Onboard Memory > 64M [Disabled]

>Chip Configuration
Onboard PCI IDE Enable [Both]
Spread Spectrum Control [Enabled]
S2K Strength Setting [Enabled]
S2K Strength Value [Auto]
AGP 4X Drive Strength [Auto]
AGP 4X Mode [4X]
AGP Fast Write [Enabled]
SDRAM Configuration [By SPD]
SDRAM CAS Latency [3T]
SDRAM RAS Precharge Time [3T]
SDRAM RAS to CAS Delay [3T]
PCI Master Read Caching [Disabled]
Delayed Transaction [Disabled]
PCI to DRAM Prefetch [Disabled]
Byte Merge [Disabled]
>I/O Device Configuration
Onboard FDC Swap A & B [No Swap]

Onboard Serial Port 1 [3F8H/IRQ4]
Onboard Serial Port 2 [2F8H/IRQ3]
UART2 Use Infrared [Disabled]

Onboard Parallel Port [378H/IRQ7]
Parallel Port Mode [ECP+EPP]
ECP DMA Select [3]
>Onboard Peripheral Resource Control
Onboard AC97 Modem Controller [Auto]
Onboard AC97 Audio Controller [Auto]
>PCI Configuration
Slot 1 IRQ [Auto]
Slot 2 IRQ [Auto]
Slot 3 IRQ [Auto]
Slot 4/5 IRQ [Auto]

PCI/VGA Palette Snoop [Disabled]
PCI Latency Timer [32]
USB Function [Enabled]

>PCI/PNP IRQ Resource Exclusion
IRQ 3 Reserved for Legacy Device [No/ICU]
IRQ 4 Reserved for Legacy Device [No/ICU]
IRQ 5 Reserved for Legacy Device [No/ICU]
IRQ 7 Reserved for Legacy Device [No/ICU]
IRQ 9 Reserved for Legacy Device [No/ICU]
IRQ 10 Reserved for Legacy Device [No/ICU]
IRQ 11 Reserved for Legacy Device [No/ICU]
IRQ 12 Reserved for Legacy Device [No/ICU]
IRQ 14 Reserved for Legacy Device [No/ICU]
IRQ 15 Reserved for Legacy Device [No/ICU]
>PCI/PNP DMA Resource Exclusion
DMA 1 Reserved for Legacy Device [No/ICU]
DMA 3 Reserved for Legacy Device [No/ICU]
DMA 5 Reserved for Legacy Device [No/ICU]
>PCI/PNP UMB Resource Exclusion
Reserved MEM Block BASE [No/ICU]
>Shadow Configuration
Video ROM BIOS Shadow [Enabled]
C8000-CBFFF Shadow [Disabled]
CC000-CFFFF Shadow [Disabled]
D0000-D3FFF Shadow [Disabled]
D4000-D7FFF Shadow [Disabled]
D8000-DBFFF Shadow [Disabled]
DC000-DFFFF Shadow [Disabled]

Power
----
Power Management [User Define]
Video Off Option [Suspend -> Off]
Video Off Method [DPMS OFF]
HDD Power Down [Disabled]
Suspend-to-RAM Capability [Disabled]
CPU Fan in Standby Mode [On]
CPU Fan Check at Power on [Disabled]
Fan Check Beeping [Disabled]
CPU Thermal Option [Throttle]

Suspend Mode [Disabled]
PWR Button < 4 Secs [Soft Off]

>Power Up Control
AC Power Loss Restart [Disabled]
PWR Up On External Modem Act [Disabled]
Wake On LAN or PCI Modem [Disabled]

Automatic Power Up [Disabled]

>Hardware Monitor
MB Temperature 28C/82F
CPU Temperature 44C/111F
JTPWR Temperature N/A

CPU Fan Speed 5357 RPM
POWER Fan Speed N/A
CHASSIS Fan Speed 2596 RPM

VCORE Voltage 1.74V
+3.3V Voltage 3.51V
+5V Voltage 5.05V
+12V Voltage 11.79V
-12V Voltage [Ignore]
-5V Voltage [Ignore]

Boot
----
1. Removable Device [Legacy Floppy]
2. ATAPI CD-ROM [SONY CD-ROM CDU4821]
3. IDE Hard Drive [None]
4. Other Boot Device [INT18 Device (Netwo)]

Plug & Play O/S [No]
Reset Configuration Data [No]
Boot Virus Detection [Disabled]
Quick Power On Self Test [Enabled]
Boot up Floppy Seek [Disabled]
SCSI/ATA100 Boot Sequence [ATA100/SCSI]
Load Onboard ATA BIOS [Auto]

Primary VGA BIOS [AGP Card]

Exit
----
Exit & Save Changes
Exit & Discard Changes
Load Setup Defaults
Discard Changes
Save Changes










"3. IDE Hard Drive [None]"

Hmm, its not reading my drive i dont think, maybe something wrong or something i missed when i used the third party ata controller?

Here's a copy of that controllers readme.txt

"
********************************
* *
* Ultra Family Driver Diskette *
* *
********************************


====================
Contents on the disk
====================
README TXT This readme file
ULTRA Microsoft Windows miniport disk label file
TXTSETUP OEM Microsoft Windows miniport text mode setup file

WINXP <DIR>
ULTRA SYS Microsoft WindowsXP miniport driver
ULTRA INF Microsoft Windows miniport setup file

WIN2000 <DIR>
ULTRA SYS Microsoft Windows2000 miniport driver
ULTRA INF Microsoft Windows miniport setup file

WIN9x-ME <DIR>
ULTRA MPD Microsoft Windows9x-ME miniport driver
ULTRA INF Microsoft Windows miniport setup file
ADVPACK DLL Advanced INF file format support file
PTISTP DLL Advanced INF file format support file
PU66VSD VXD Promise power management driver
SMARTVSD VXD Promise S.M.A.R.T. driver

NT4 <DIR>
ULTRA SYS Microsoft WindowsNT miniport driver file
ULTRA INF Microsoft Windows miniport setup file

================
Software Version
================
Microsoft WindowsNT miniport driver 2.00.0 (Build 18)
Microsoft Windows 2000 miniport driver 2.00.0 (Build 18)
Microsoft Windows9x-ME miniport driver 2.00.0 (Build 18)
Microsoft WindowsXP miniport driver 2.00.0 (Build 18)
"

 

[anonboy]

here's a copy of the win2000 ULTRA.INF

"
[Version]
Signature="$Windows NT$"
Provider=%PROMISE%
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
CatalogFile=Ultra.cat
Class=SCSIAdapter
DriverVer=08/17/2001, 2.00.0.18

[SCSIReg]
HKR,,,,%SCSIClassName%
HKR,,Installer32,,"SysSetup.Dll,ScsiClassInstaller"
HKR,,Icon,,"-10"
HKR,,LegacyInfOption,,"SCSI"

[DestinationDirs]
DefaultDestDir = 12 ; DIRID_DRIVERS
MoveMiniPort.NT = 12;

[ControlFlags]
;
; Exclude the following devices from Select Device list.
; These represent 'combination' driver nodes, for which there are separate items to be
; presented to the user. These combination nodes are only used when figuring out what
; driver node to associate with a pre-existing service.
;
; CopyFilesOnly=PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A&REV_02

[Manufacturer]
%Promise%=Promise

[Promise]
%PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A.DeviceDesc%=ultra100PCI_2,PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A

;************** U133 **************
[Ultra133TX2.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT

[ultra133TX2.NT]
CopyFiles=MoveMiniPort.NT

[ultra133TX2.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

;************** U100 **************
[Ultra100TX2.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT

[ultra100TX2.NT]
CopyFiles=MoveMiniPort.NT

[ultra100TX2.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

[Ultra100PCI.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT

[ultra100PCI.NT]
CopyFiles=MoveMiniPort.NT

[ultra100PCI.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

[Ultra100PCI_2.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT
Reboot

[ultra100PCI_2.NT]
CopyFiles=MoveMiniPort.NT
Reboot

[ultra100PCI_2.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

;************** U66 **************
[Ultra66PCI.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT
Reboot

[ultra66PCI.NT]
CopyFiles=MoveMiniPort.NT
Reboot

[ultra66PCI.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

;************** U33 **************
[Ultra33PCI.Uninstall.NT]
DelReg=RegUninstall.del
DelFiles=MoveMiniPort.NT
Reboot

[ultra33PCI.NT]
CopyFiles=MoveMiniPort.NT
Reboot

[ultra33PCI.NT.Services]
AddService = Ultra, 2, ultraPCI_Service_Inst, Miniport_EventLog_Inst

;***************************************

[ultraPCI_Service_Inst]
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 0 ; SERVICE_BOOT_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\ultra.sys
LoadOrderGroup = SCSI Miniport
AddReg = pnpsafe_pci_addreg

;*************************************************************
;These addreg sections should be used when installins services to indicate
;which interface types are safe for PNP and which aren't. INTERFACE_TYPE
;is defined in NTDDK.H

[pnpsafe_pci_addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001

;*************************************************************
;The EventLog entries are the same for all SCSI miniports.
[Miniport_EventLog_Inst]
AddReg = Miniport_EventLog_AddReg

[Miniport_EventLog_AddReg]
HKR,,EventMessageFile,%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll"
HKR,,TypesSupported,%REG_DWORD%,7

;**************** Uninstall for U133
[RegUninstall133TX2]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_4D69&SUBSYS_4D68105A.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra133TX2.Uninstall;VEN_105A&DEV_4D69&SUBSYS_4D68105A"

;**************** Uninstall for U100
[RegUninstall100TX2]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_4D68&SUBSYS_4D68105A.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra100TX2.Uninstall;VEN_105A&DEV_4D68&SUBSYS_4D68105A"

[RegUninstall100]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra100PCI.Uninstall;VEN_105A&DEV_4D30&SUBSYS_4D33105A"

[RegUninstall100_2]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra100PCI_2.Uninstall;VEN_105A&DEV_0D30&SUBSYS_4D33105A"

;**************** Uninstall for U66
[RegUninstall66]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_4D38&SUBSYS_4D33105A.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra66PCI.Uninstall;VEN_105A&DEV_4D38&SUBSYS_4D33105A"

;**************** Unistall for U33
[RegUninstall33]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"DisplayName",,%PCI\VEN_105A&DEV_4D33.DeviceDesc%
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra,"UninstallString",,"RunDll32 ptistp.dll,LaunchINFSection %17%\other\%Promise%Ultra.inf;Ultra33PCI.Uninstall;VEN_105A&DEV_4D33"

[RegUninstall.del]
HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ultra

[UltraPCI.Del.Reg]
HKLM,Enum\PCI\VEN_105A&DEV_4D69&SUBSYS_4D68105A
HKLM,Enum\PCI\VEN_105A&DEV_4D68&SUBSYS_4D68105A
HKLM,Enum\PCI\VEN_105A&DEV_4D68
HKLM,Enum\PCI\VEN_105A&DEV_4D30&SUBSYS_4D33105A
HKLM,Enum\PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A
HKLM,Enum\PCI\VEN_105A&DEV_4D30
HKLM,Enum\PCI\VEN_105A&DEV_4D38&SUBSYS_4D33105A
HKLM,Enum\PCI\VEN_105A&DEV_4D38
HKLM,Enum\PCI\VEN_105A&DEV_4D33&SUBSYS_00000000
HKLM,Enum\PCI\VEN_105A&DEV_4D33


[ultraPCI.PosDup]
*BUS0042

[*BUS0042.Det]
AddReg=ForceMPCopy

[IOS]
HKR,,DevLoader,,*IOS
HKR,,DontLoadIfConflict,,"Y"

[ultraPCI.reg]
HKR,,PortDriver,,Ultra.mpd

[ForceMPCopy]
HKR,,NoSetupUI,,1

[SourceDisksFiles]
;Ultra.mpd = 1
Ultra.sys = 1
;pu66vsd.VXD = 1
;PTISTP.dll = 1
;advpack.dll = 1
;SMARTVSD.VXD = 2
Ultra.inf = 1

[MoveMiniPort.NT]
Ultra.sys

[SourceDisksNames]
1 = "Promise Ultra Family Driver Diskette",,,,
2 = "Windows system",,,,

[strings]
Promise="Promise Technology"
PCI\VEN_105A&DEV_0D30&SUBSYS_4D33105A.DeviceDesc="Win2000 Promise Ultra100 (tm) IDE Controller (PDC20265)"
"

 

[Kartajan]

ok, we are getting too deep into the wrong end of the problem.
what I need to know:
1. Is the system that we are looking at the one in your signature?
2. is the 3rd party controller in question a seperate card you put in, or built on the motherboard?
3. in device manager, do you see any conflicts? look for the ! and the ? marks...
4. (Not real sure about windows update for 2k, but did you run that?)
5. are you current on service packs for 2k? I beleive that 2k is now on SP3..

* if you are not good for #5, #4 will not happen.
* #3 has a good chance of contributing to the problem, if that is the case.

- I am not trying to talk down, I just have a feeling that you do not have a lot of "trigger- time" on this kind of thing...

 

[anonboy]

Don't worry about talking down to me heh, as long as i'm learning something it's all good.

"1. Is the system that we are looking at the one in your signature?"

No the system I'm referring to is my old one:

AMD Athlon / Thunderbird 750mhz
Asus A7V133 Socket A KT133
512MB PC133 SDRAM
ATX Mid Tower w/ 250 Watt
Sceptre D98A 19" Monitor
GeForce4 Ti4200
White Label 40GB
D-Link 10/100
Creative Labs PCI 56k
Altec Lansing ACS 45.2
Creative Labs PCI 128 Sound Card
Sony 48X IDE CD-ROM
Cooler Master Socket A / 370
Windows 2K

"2. is the 3rd party controller in question a seperate card you put in, or built on the motherboard?"

It's a third party ata controller provided by asus since the win2k cd doesnt have an onboard ata controller(needed since i was booting through an ata device). Explantation here:
http://forums.viaarena.com/messageview.cfm?catid=25&threadid=29612&highlight_key=y
Where I got the controller:
http://www.asus.com.tw/support/download/item.aspx?ModelName=A7V

Hmmm...just thought of something...is it the same controller for both the a7v and the a7v133? It looks like it is, I used the a7v though because originally i had an a7v but swaped it out for an a7v133 and forgot when I reinstalled so i used the ata100 controller i originally got for the a7v. They look to be the same though from the looks of it...

"3. in device manager, do you see any conflicts? look for the ! and the ? marks..."

I dont see any conflicts in device manager, i went into console1 and checked System Information > Hardware Resources > Conflicts/Sharing...I have a lot of devices on IRQ 9, which I asked around about earlier to see if that was a problem. Evidently there are supposed to be a lot of devices on IRQ9...

This is what I have on IRQ9:

9 Microsoft ACPI-Compliant System
9 NVIDIA GeForce4 Ti 4200 with AGP8X
9 VIA USB Universal Host Controller
9 VIA USB Universal Host Controller
9 Creative AudioPCI
9 Realtek PCI Fast Ethernet Adapter
9 PCI Simple Communications Controller(modem)
9 Win2000 Promise Ultra100 IDE Controller

"4. (Not real sure about windows update for 2k, but did you run that?)
5. are you current on service packs for 2k? I beleive that 2k is now on SP3.."

Yes and yes.

The thing I dont get is I have this problem right from the get-go of a new installation. Which leads me to believe it has something to do with the controller. Before I do any updates or anything, right at the first boot up after a clean install. Mouse is really choppy, i get weird graphics errors (like i described above, right click to get properties and i get 'shadows' of that drop down menu after im done with it- only lasts a few seconds).

 

[anonboy]

come to think of it when I swaped in my a7v133 i got these errors, so i put my a7v back in and got the same errors, so i put my a7v133 back in yet again

 

[Kartajan]

on reading your other posts, something bothers me. the BIOS flash with a compare error.

I would definitely re- flash the BIOS with the latest and greatest for your MB.

Exactly which A7V133 do you have?
A7V133 A7V133-C A7V133-M A7V133-VM

go to the download section for your EXACT MB, and get the newest drivers (ATA, 4-in-1, etc) as well as BIOS.

Do the BIOS first. the BIOS could possibly be the root of drivers not working properly- and therefore giving you stress.

 

[Kartajan]

Spread Spectrum Control ->DISABLE, slows your system down
Video ROM BIOS Shadow ->DISABLE, not effective with newer cards like yours
CPU Fan Check at Power on ->ENABLE, something you really would want to know if you had a problem
Fan Check Beeping ->ENABLE, something you really would want to know if you had a problem
Plug & Play O/S ->YES, 2k is PnP aware.
Reset Configuration Data ->YES, after you flash.

something many neglect to do when flashing:

once flash is complete, you have to restart. when you do- go into the bios and "set to default settings". then restart, go into BIOS yet again, and set the way you want it.

If you do not do it this way, you have a tendency for old/ invalid settings to give you issues.

 

[anonboy]

It's an a7v133, I flashed the BIOS (it was allready the latest version but i did it anyway) and I reset those BIOS settings. No change so far.

Last couple days however, (before i flashed BIOS), i started to get bluescreens at win2k bootup (at the Windows 2000 Professional Bootup, right at the end of it)

"
***STOP 0x000000D1 (0x00000114, 0x00000012, 0x00000000, 0xBFF754CC)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
***Address BFF754CC base at BFF71000, Date Stamp 3c7eddfb - SCSIPORT.SYS
"

Started bluescreening that just out of the blue, hadnt changed anything, so i hope my comp doesnt die lol. I have to restart it a few times before i can get past it.

 

[Kartajan]

set load onboard ata bios to ENABLE vice AUTO. (might help. maybe.)

was the driver that you used the W2k ATA100 driver or the W2k UATA driver?
maybe the other one is it. You don't see that right away unless you click on OS specific filter on the top of the download page...


did the previous issue with BIOS flashing get fixed, or still present? Current BIOS is 1009.

asus downloads

 

[anonboy]

Only 2 options for load onboard ata bios, disable and auto so i left it on auto.

The driver I used was the ata100, the one i posted above.

BIOS flash worked allthough the one on the a7v133 was allready 1009, i did it anyway and it 'Flashed Successfully'. The flashing errors you read about were the ones on my old a7v.

Every time i restart it blue screens me at the Windows 2000 bootup screen, it only lets me boot past that if i shut the power off and do it that way otherwise i get that SCSIPORT.SYS error.

 

[Kartajan]

so, try the W2k UATA driver- maybe that one will work better for ya...

*Make sure that system restore in enabled before you switch 'em, in order to ease recovery if it does not work...*

I'm pretty much out of guesses past that.

(Clean install of WinXP?
Clean install of Linux?
Beat w/ a large blunt object until it lies in many small pices and buy new replacement parts?!?)

 

[anonboy]

hmm how do i go about doing that? i dont want to screw this up...cuz this has to be it, either that or something specific to my HD

cuz i have this problem right from the get-go of a fresh install, which baffles the heck outta me

 

[Kartajan]

damn. Sorry- I forgot that you are on 2k not XP.
no restore point for you.

if it doesn't work, have the driver that you have been using handy.
if it doesn't work right, you may need to use safe mode to put it back in.

* worst case could require a NEW fresh install, so back up your stuff first. *

 

[Dim]

It's been a while since I had a MB with VIA chipset, but as I recall, the VIA driver (?miniport) made the drives appear as SCSI. To change DMA mode I had to go to the VIA utility, not the System->hardware control panel.

I have a terrible memory, so this observation may be worthless.

 

[anonboy]

ya know what i think that's it, in device manager i have this going on:

>IDE ATA/ATAPI controllers
-Primary IDE Channel
-Secondary IDE Channel
-VIA Bus Master IDE Controller
.
.
.
>SCSI and RAID controllers
-Win2000 Promise Ultra100 (tm) IDE Controller (PDC20265)


That win2k ultra100 IDE controller should be under IDE ATA/ATAPI controllers correct? So when I was prompted at the install to press F6 for 3rd part SCSI and RAID controllers it put it there.

Course the problem now is finding out how to install the win2k ultra100 IDE controller...i read the readme it was no good(didnt say anything about installing), i know what i want to do from here i just dont know how to do it.

 

[Kartajan]

extract driver to a known location on the hdd.
if no setup in there, use device manager to "update driver"

 

[ChefJoe]

It's hooked up on the primary IDE channel on the end of the cable. Also had to use a third party IDE Controller when I installed 2k since the install disk doesnt have an onboard ATA controller

Are you saying that the hard drive that is attached to the cable that runs to your Promise controller card appears as SCSI ? If so, that's normal. My Promise (TX100) card appears as a "SCSI controller" and the drives on it appear as "scsi drives" though they're all IDE stuff.

 

[ScrapSilicon]

Originally posted by: ChefJoe

It's hooked up on the primary IDE channel on the end of the cable. Also had to use a third party IDE Controller when I installed 2k since the install disk doesnt have an onboard ATA controller

Are you saying that the hard drive that is attached to the cable that runs to your Promise controller card appears as SCSI ? If so, that's normal. My Promise (TX100) card appears as a "SCSI controller" and the drives on it appear as "scsi drives" though they're all IDE stuff.

No the system I'm referring to is my old one:

AMD Athlon / Thunderbird 750mhz
Asus A7V133 Socket A KT133
512MB PC133 SDRAM
ATX Mid Tower w/ 250 Watt
Sceptre D98A 19" Monitor
GeForce4 Ti4200
White Label 40GB
D-Link 10/100
Creative Labs PCI 56k
Altec Lansing ACS 45.2
Creative Labs PCI 128 Sound Card
Sony 48X IDE CD-ROM
Cooler Master Socket A / 370
Windows 2K

he doesn't have a separate controller listed.. ....hmmmm....

 

[Kartajan]

the appearance of a seperate card is not the case. to quote ASUS:

IDE Ports 4 x UltraDMA/100 (PromiseR ATA-100)

IDE RAID (Optional) Promise®: IDE RAID Controller to Support RAID 0 or 1

I think that we covered all that earlier on.

anonboy- how's it going? did the driver change do any good, or are you still having problems?

 

[anonboy]

I popped in a spare maxtor i had and did a clean install, did the same thing (when prompted by win2k setup i gave the win2k ultra100 i had on a 3 1/2"), still get the same errors, which driver do i update in device manager, the primary IDE? It's late and i have class early tomorrow ill get back tomorrow afternoon and try some more usin my new install.

 

[Kartajan]

since you have a spare drive, try this.

fresh install without using the drivers at all.

ignore any complaints from the OS.

have the drivers (both UATA and the ATA100) available on a floppy (or 2 if nessessary)

try to get it to load without, and update with UATA when you get in to windows proper.

 

[anonboy]

It wont continue with the OS installation because it doesnt detect a drive if i dont specify a third party controller.

I went to asus' site and dled the UATA for win2k:
http://www.asus.com.tw/support/download/item.aspx?ModelName=A7V133

Put em on a floppy, however when I go to specify a controller im given 4 different options, and it says the 4 options are WinXP controllers(and i double checked to be sure i dled the win2k one).

I dunno maybe thats the way the win2k controllers are supposed to be, here are the 4 UATA options, not sure which to pick:

WinXP Promise ULTRA133 TX2 (tm) Controller
WinXP Promise ULTRA100 TX2 (tm) Controller
WinXP Promise ULTRA100 (tm) Controller
WinXP Promise ULTRA100 (tm) Controller (PDC20265)

Pretty sure it isnt the ULTRA133, not sure about the rest though...

 

[Kartajan]

i'd use the third one.