K8T Neo2-F Interrupt Request Table

hello
which pci slot should i take to have one interrupt pin only for my audigy2 soundcard?
Its the only pci card.
thanks

Just try and find out...
But why are you looking for this?
All IRQ's are remapped by Apic anyway....

Similar Messages

MSI K8T Neo2 FIR, need help installing drivers

Hi there,
I need help with installing drivers. Here’s my setup:
CPU: AMD Athlon 64 3500+
Mainbord: MSI K8T Neo2 FIR (VIA K8T800Pro)
OS: Windows XP Professional, SP2 installed
ATI Radeon 9600 Pro
I updated per MSI Live Monitor, but when I run ‘dxdiag’, I says I have to update the ‘VIA standard host bridge’. I don’t know what this is or where it can be found. It could be I saved the updated drivers in the wrong file (F:\ Program Files\...) where F is my primary harddisk and the drivers should be saved in F:\Windows\ System 32.
Also, my hardware setup tells me there are two videocards 'installed': a Radeon 9600 Pro and a radeon 9600 Pro (secundary). Do I need to de-install the secundary one?
Here’s a piece of my most recent dxdiag:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
System Information
Time of this report: 5/22/2005, 10:22:20
Machine name: UIWDC2ARUPUS49X
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: MSI
System Model: MS-6702E
BIOS: Version 07.00T
Processor: AMD Athlon(tm) 64 Processor 3500+, MMX, 3DNow, ~2.2GHz
Memory: 1024MB RAM
Page File: 285MB used, 2687MB available
Windows Dir: F:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found. DirectDraw test results: All tests were successful. Direct3D 7 test results: All tests were successful. Direct3D 8 test results: All tests were successful. Direct3D 9 test results: All tests were successful.
Sound Tab 1: No problems found.
Music Tab: DirectMusic test results: All tests were successful.
Input Tab: No problems found.
Network Tab: No problems found. DirectPlay test results: The tests were cancelled before completing.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: RADEON 9600 SERIES
Manufacturer: ATI Technologies Inc.
Chip type: ATI RADEON 9600 Series AGP (0x4150)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_4150&SUBSYS_000217EE&REV_00
Display Memory: 128.0 MB
Current Mode: 1280 x 1024 (16 bit) (60Hz)
Monitor: Plug en Play-monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6546 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 5/4/2005 04:28:54, 226816 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n.v.t.
Mini VDD: ati2mtag.sys
Mini VDD Date: 5/4/2005 04:28:34, 1133056 bytes
Device Identifier: {D7B71EE2-0210-11CF-CC6D-0820A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x4150
SubSys ID: 0x000217EE
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: All tests were successful.
D3D7 Test Result: All tests were successful.
D3D8 Test Result: All tests were successful.
D3D9 Test Result: All tests were successful.
Sound Devices
Description: Sound Blaster Live! 24-bit
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_10061102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: P17.sys
Driver Version: 5.12.0001.0314 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 6/4/2004 10:27:46, 840960 bytes
Other Files:
Driver Provider: Creative Technology Ltd.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 96000
Static/Strm HW Mix Bufs: 64, 63
Static/Strm HW 3D Bufs: 64, 63
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: Sound Blaster Live! 24-bit
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: P17.sys
Driver Version: 5.12.0001.0314 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2004 10:27:46, 840960 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
DirectMusic
DLS Path: F:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Sound Blaster Live! 24-bit, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI-mapper (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Creative SoundFont Synth (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: All tests were successful.
DirectInput Devices
Device Name: Muis
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Toetsenbord
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
USB Devices
+ USB-hoofdhub
| Vendor/Product ID: 0x1106, 0x3038
| Matching Device ID: usb\root_hub
| Lower Filters: vulfntrs
| Service: usbhub
| Driver: usbhub.sys, 8/3/2004 23:08:44, 57600 bytes
| Driver: usbd.sys, 9/7/2001 14:00:00, 4736 bytes
Gameport Devices
PS/2 Devices
+ Standaardtoetsenbord (101/102 toetsen) of Microsoft Natural PS/2-toetsenbord
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 00:55:30, 53760 bytes
| Driver: kbdclass.sys, 8/4/2004 00:57:18, 25216 bytes
|
+ Toestenbordstuurprogramma voor Terminal Server
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:03:48, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 00:57:18, 25216 bytes
|
+ HID-compliant Wheel Mouse
| Vendor/Product ID: 0x046D, 0xC03D
| Matching Device ID: hid\vid_046d&pid_c03d
| Upper Filters: LMouFlt2
| Lower Filters: LHidFlt2
| Service: mouhid
| Driver: mouhid.sys, 9/6/2001 19:04:40, 12288 bytes
| Driver: mouclass.sys, 8/4/2004 00:53:38, 23552 bytes
| Driver: LHidFlt2.Sys, 12/17/2003 09:50:00, 25505 bytes
| Driver: LMouFlt2.Sys, 12/17/2003 09:50:00, 70801 bytes
| Driver: Logi_MwX.Exe, 12/17/2003 09:50:00, 19968 bytes
|
+ Stuurprogramma voor muis van Terminal Server
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:03:48, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 00:53:38, 23552 bytes
DirectPlay Service Providers
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: The tests were cancelled before completing.
Registry: OK
DirectPlay Adapters
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: LAN-verbinding 2 - IPv4 -
DirectPlay Voice Codecs
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
DirectPlay Lobbyable Apps
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 65.4 GB
Total Space: 76.3 GB
File System: NTFS
Model: ST380011A
Drive: F:
Free Space: 56.7 GB
Total Space: 78.2 GB
File System: NTFS
Model: Maxtor 6Y080L0
Drive: D:
Model: LITE-ON COMBO SOHC-5232K
Driver: f:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:54, 49536 bytes
Drive: E:
Model: LG CD-ROM CRD-8521B
Driver: f:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:54, 49536 bytes
System Devices
Name: VIA CPU to AGP2.0/AGP3.0 Controller
Device ID: PCI\VEN_1106&DEV_B188&SUBSYS_00000000&REV_00\3&61AAA01&0&08
Driver: F:\WINDOWS\system32\DRIVERS\VIAAGP1.SYS, 5.01.0000.3442 (English), 7/2/2003 04:42:00, 27904 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&61AAA01&0&07
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&61AAA01&0&04
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&61AAA01&0&03
Driver: n/a
Name: VIA Standard PCI to ISA Bridge
Device ID: PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&61AAA01&0&88
Driver: F:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (Dutch), 9/6/2001 18:20:18, 36352 bytes
Name: VIA USB 2.0 Enhanced Host Controller
Device ID: PCI\VEN_1106&DEV_3104&SUBSYS_70201462&REV_86\3&61AAA01&0&84
Driver: F:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: F:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/4/2004 01:03:12, 7168 bytes
Name: VIA OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1106&DEV_3044&SUBSYS_702D1462&REV_46\3&61AAA01&0&70
Driver: F:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/3/2004 23:10:10, 61056 bytes
Driver: F:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/3/2004 23:10:08, 53248 bytes
Driver: F:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/3/2004 22:58:30, 61824 bytes
Driver: F:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/3/2004 22:58:30, 60800 bytes
Driver: F:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 23:46:40, 6400 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&83
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&82
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&81
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&80
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&61AAA01&0&02
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&61AAA01&0&01
Driver: n/a
Name: VIA Bus Master IDE Controller
Device ID: PCI\VEN_1106&DEV_0571&SUBSYS_70201462&REV_06\3&61AAA01&0&78
Driver: F:\WINDOWS\system32\DRIVERS\viaide.sys, 1.00.0001.0001 (English), 8/3/2004 22:59:44, 5376 bytes
Driver: F:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:42, 25088 bytes
Driver: F:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&61AAA01&0&00
Driver: n/a
Name: Sound Blaster Live! 24-bit
Device ID: PCI\VEN_1102&DEV_0007&SUBSYS_10061102&REV_00\3&61AAA01&0&30
Driver: F:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (Dutch), 8/4/2004 01:03:14, 4096 bytes
Driver: F:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (Dutch), 8/4/2004 01:03:38, 130048 bytes
Driver: F:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (Dutch), 8/3/2004 23:15:22, 140928 bytes
Driver: F:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:00, 60288 bytes
Driver: F:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/3/2004 23:15:50, 145792 bytes
Driver: F:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (Dutch), 8/3/2004 23:08:04, 48640 bytes
Driver: F:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 01:03:40, 23552 bytes
Driver: F:\WINDOWS\system32\CtDvInst.dll, 0.00.0000.0008 (English), 7/25/2003 11:35:48, 131072 bytes
Driver: F:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.0172 (English), 9/22/2003 02:47:38, 178672 bytes
Driver: F:\WINDOWS\system32\drivers\ctsfm2k.sys, 5.12.0001.0172 (English), 9/22/2003 02:48:06, 130192 bytes
Driver: F:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2001 08:35:46, 36864 bytes
Driver: F:\WINDOWS\system32\sfms32.dll, 5.12.0001.0172 (English), 9/22/2003 02:51:52, 172032 bytes
Driver: F:\WINDOWS\system32\ct2mgm.sf2, 9/22/1999 09:18:00, 2167684 bytes
Driver: F:\WINDOWS\system32\P17res.dll, 5.12.0001.0308 (English), 3/29/2004 04:02:48, 136704 bytes
Driver: F:\WINDOWS\system32\P17.dll, 1.00.0001.0029 (English), 4/8/2004 04:37:40, 60928 bytes
Driver: F:\WINDOWS\system32\drivers\P17.sys, 5.12.0001.0314 (English), 6/4/2004 10:27:46, 840960 bytes
Driver: F:\WINDOWS\system32\drivers\Pfmodnt.sys, 3.00.0000.0003 (English), 3/5/2003 12:19:28, 15840 bytes
Driver: F:\WINDOWS\system32\A3d.dll, 80.00.0000.0003 (English), 4/11/2002 03:41:06, 65536 bytes
Driver: F:\WINDOWS\system32\P17CPI.dll, 1.00.0000.0002 (English), 10/2/2003 12:48:18, 53248 bytes
Name: Ethernet-controller
Device ID: PCI\VEN_10EC&DEV_8169&SUBSYS_702C1462&REV_10\3&61AAA01&0&58
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&61AAA01&0&C3
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&61AAA01&0&C2
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&61AAA01&0&C1
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&61AAA01&0&C0
Driver: n/a
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Help would be very much appriciated, thnx!

The two vis.cards issue is normal, it sees the primary output (VGA) as a device and the TV-out a separate device.
Go to device manager to see if there's any device on ur rig that doesn't have drivers.
Did u install the 4-in1 drivers, get the latest version from the MSI support site.
good luck.

MSI K8T Neo2 F vs. MSI K7N2 Delta ILSR

Hi there !
I have an amd Athlon XP 3200+ overheating problem, and contacted the technical support of the shop where the processor and CPU was coming from.
Since they do not have any XP 3200+ to replace mine, they propose me to replace fro free :
- the XP 3200+ by an AMD Athlon 64 3200+
- my actual MSI K7N2 delta ILSR by an MSI K8T Neo2 F
... and this for free.
Since I do not know this new motherboard that has been proposed, I'd like to have advice on if this is a good deal ?!?
My actual system has :
- an Aluminium case with 2x 12cm FAN's
- 2 IDE hard drives
- 1 SATA hard drive
- TWINX Corsair XMS 2x256MB PC 3200L (Extreme low latency)
- an AGP 8x video card
- An Antec True Power 480W.
will the new motherboard fit with this configuration?
Many thanks for your input !

Not really, unless you really want to oc your cpu. The K8T boards aren't that good in OC-ing. But still, some is possible and you'll be sure that the board is as steady as a rock.
For a moment I thought you were talking about a Neo board ... but I just saw it's a Neo2. That means Socket 939 -> dual channel RAM.
The only risk you have now, is that your RAM won't work in dual channel with the CPU. But that's not really a board-problem, more a CPU/RAM-controller related problem. But then, it's still a great offer and chances are good that it will work. If you run into any trouble, RAM-related, just flash bios to version 1.9 and you will probably be just fine.

K8t neo2-FIR lock ups

hey i'm posting for my friend who recently got a new setup for his computer
antec 400W power supply
3200+
k8t neo2-FIR
sapphire radeon 9600XT
512 meg major brand ram
2 80 gig harddrives
onboard sound/lan
i'm not too sure of the psu specs
the computer (with latest driver updates) has a tendency of locking up where the screen will just go black at random periods
no matter the situation and we will have to restart it (we tried in optimizeed bios settings and default)
the computer when i was there ran fine in video games except for the locking up part
i'm not sure what the problem is nor does my friend any help is appreciated

Run Memtest86 and find out which RAM models he uses. Likely as not it is going to be part of the issue. See if you can read the lable on that PSU as well and find out how many amps are on the 12v rail.

K8T Neo2 V2.0 SATA-Problem

Hi Folks,
I got a "problem" with my K8T Neo2 V2.0. At first I had 3 IDE-drives, but I needed a new DVD-burner to read double-layer discs. So I bought a SATA-Drive, plugged it in and it worked good. (VIA 5.13A hyperions). After that I decided to go for a new, bigger, faster harddisk .. also SATA. I wanted to profit from the speed so I made a clean install of Windows XP on that new SATA-drive. BIOS was set to IDE and the Windows-setup recognized the drive correctly without an driver from floppy. Then I used the newly released 5.14A Hyperions and the strangeness began. Suddenly the safe-removal-icon for the SATA drives in the taskbar was gone, no more hot-plug capabillity I thout. I wanted to install a game from DVD and I realized darn slow read-speed from the new DVD-drive. I read only with 3x-speed and double-layer DVDs with 2x. I made a repair-install of Windows XP an rolled back to the 5.13A Hyperions and now my safe-removal-icon and the normal read-speed is back - but now sometimes I get an "program-lag". When I close a programm and want to open an other, or just a menu or something, sometimes the PC don't react for 1-2 seconds.
Any suggestions? Any knowledge about SATA-behavior on the K8T Neo2 V2.0? (or the VIA Hyperions?)

Well here are some specs:
Athlon 64 X2 4200+
2x 512 MB DDR400 RAM, Infineon
1x IDE HDD, Maxtor 6Y120P0
1x SATA HDD, Seagate ST3250410AS16
1x IDE DVD-Drive Pioneer A06S
1x SATA DVD-Recorder Plextor PX-810SA
Creatice SB Live! 5.1
PSU Enermax 350 Watt (EG365AX-VE / 3,3V=32A; 5V=32A, 12V=26A)
Windows XP Pro with SP2 installed on SATA-HDD
The Hyperions from the MSI-Driver CD also don't work (same no-hot-plug-problem).
In the BIOS the SATA-channels are configured as IDE, I never needed a driver floppy for XP-install.
The system event-log only shows one failure "loading of boot- or systemdriver viamraid failed". When I had my old XP install on the IDE drive (with installed 5.14A hyperions) the VIA V-Raid utility was installed and could be started, the hot-plug-ability was working as I plugged in the DVD-Recorder. Then I installed XP on the new SATA-HDD (with plugged in dvd-recorder) and the problems came up. Also now no via vraid-utility is installed.

MSI K8T Neo2 F 939 pin, any known video or other driver issues?

Using a MSI K8T Neo2 F, AMD 64 3500+ winchestor, 1gb DDR400 3200 memory, New WD 740GD SATA HDD, ATI 9800 GT Pro 256 videocard. Fresh XP Pro SP2 install with all the update, latest Via 4 in 1s.
Seems like my problems began when I upgraded video drivers to either Cat 4.9s or 5.1s (ATI Radeon 9800 GT Pro 256) in order to get Doom3 running as it wouldn't run on the v 3.4 drivers that came on the cd-rom with the videocard.
HL2 would play fine with those old drivers. After upgrading to newer drivers, HL2 and Doom 3 (which now at least plays) won't play for more than 5 minutes yet other games will. The same videocard (perhaps 3 months old now) with cat 4.9 drivers ran perfectly in my old system so I know the videocard's still OK.
I can use a restore point prior to installing the newer drivers BUT that doesn't solve the problem as to why I can't use the newer drivers.
I've heard where some have problems with XP SP2 vs SP1. Anyone here have opinions on that?
I have spare HDDs so I can use one with another fresh XP install, even try just SP1 if that'd matter? Doing that would eliminate hardware as being an issue.
It's now not just games either, it'll crash doing Turbotax and other (not demanding) times when not gaming. Games put alot of demand on any system.
Have also tryed another PSU, now an Antec Truepower 430W vs a cheaper brand 550W. Not heat related as I've tryed this with a house fan blowing on high directly at the mobo, cpu side (cover's off).
I've been trying to solve this for about a month now and it's very annoying.
I ran Memtest for 8 hours last night, no errors so the memory's OK. I'm now running another test program called Prime95 via advice from someone at Anandtech.com. http://forums.anandtech.com/messageview.aspx?catid=32&threadid=1513208
If ANYONE here has seen anything like this relating to this motherboard (which I suspect might be a problem?), please share your thoughts.
Thanks

Can you explain where I'll find "VPU recover (adapter settings)"? In display settings or ATIs cat. control center, guessing? I'm at work now but will check that soon.
AGP fast-write has been off.
As for going back to older video drivers, it did seem OK with the old Cat. v3.4 drivers that came on the videocards driver cd-rom and played HL2 fine with those drivers HOWEVER, Doom3 doesn't run with those older drivers and needs the newer drivers to function.
When it crashes, the screen usually goes to black (not BSOD). Sometimes it'll just freeze with skipping sound for a few seconds before going black, sometimes it'll reboot but usually I just reboot it. Can't 3 finger solute to task manager or Esc out of it either.

Dual channel memory mixing on a K8T Neo2

Hey all,
I have a K8T Neo2, Winchester core 3000+ and had it running with 2 TwinMOS 512 MB-DDR400 sticks in dual-channel mode. Recently I decided to add RAM, but to invest in a more solid brand. So I bought a Corsair TWINX1024-3200C2 set and plugged it in. AFAIK the right combination in the board would be the have one set in slots 1 & 3 and the other set in 2 & 4. So far the board will only post with the Corsairs in 1 & 3 (and not with the Twinnies there). But if it posts, the clock is set to 333 MHz (which is an issue of the Winchester core I understood), but more importantly the system becomes unstable: reboots etc. Even stranger is the fact that sometimes after POST I get 8 beeps from the BIOS, which suggests that the Video RAM or framebuffer is defective. Is this somehow related to the RAM I installed? Is the framebuffer mapped to the RAM at bootup for example?
I did try to change the command rate to 2T, didn't seem to help. Bios version is 3.3 by the way. Thanks for any help.
Oh maybe the vid card specs are also relevant: Sapphire Radeon 9800 pro with 128mb. Power supply is Tagan 580W so unlikely to be the problem

Quote from: Tiresmoke on 03-November-05, 23:54:30
Have you tested each stick of RAM with Memtest86 yet? You may have a bad stick. You also may want to try the new set in a different socket sety. Another words if it was in 2/4 then try it in 1/3. If the timings are different on the two sets try setting to the slowest settings of the two. You may have to exchange the set for the twin to the old set just to make it work as mixing RAM rarely works well.
Good idea on the memtesting, I'll do that tonight. I was afraid that the mixing wouldn't work well, but I thought at least if for each channel I used the same pair it wouldn't matter. Practice might indeed prove that as being a wrong assumption

Boot and OS install issues with K8T Neo2 F

Can anybody shed light on my difficulties?
Assembled a new computer yesterday. First power-on produced nothing except 3 (2,3,4) red leds on d-bracket. After reading several postings, tried the following:
Swapped around memory modules;
Did repeated JBAT1 data clears (NB if you happen to get a board with the V1.0 user guide, note that the JBAT1 diagram appears upside down - pin one is closest to the SATA slots (page 2 - 24). The MSI downloadable user guide (V1.2) has that error corrected (page 2-25)
The only memory config that doesn’t produce three red leds is with one 512 stick installed in channel 3 (green).
Can now get to the point where Windows XP boots to the point where install is about to start, and then advises me that it can’t find a hard disk!
Have dis/reconnected the sata cable (using different cables) and checked the bios setup but can find nothing strange except that setup refers to the hard disk as BBS 0 (RAID) ST3120827AS - the reference to “RAID” worries me.

Paul, there have been people here that have had to strip their system down to the bare minimum hardware to get windows to complete the install, so try that. I had trouble completing my windows install as long as I was trying to install the RAID drivers at F6. So I ignored the prompt at F6 and windows installed fine. Then I installed my RAID drivers afterward.
These things are extremely sensitive when it comes to memory. I had the same problem you are having. Mine was cured by a BIOS upgrade to ver. 3.3. The simplest way to do it is to use "Live Watch". It will locate BIOS ver 3.3 for you, and download it to a floppy along with the flash program, and make it bootable all in one easy step. Then all you have to do is boot from the floppy you just made, and follow the instructions. Very simple.
I've read all these stickies and posts now going way back, and IMHO anyone who wants to use RAM thats not on the list should do so at their own risk. Interestingly enough, the recommended list from MSI is not the same as the list from AMD. And the memory manufacturers have their own lists of RAM that they say will work with this board. I'm using 2x 512 sticks of GEIL from the MSI recommended list.
Check out these links to see what I mean. By the way, if you haven't noticed, most of the older posts about memory problems are with respect to the K8T Neo FIS2R which is a socket 754 single channel board, so although they are similar, they're not the same. My point is just because his K8TNeo FIS2R works fine with brand "X" RAM doesn't mean your K8T NEO2 FIR will.
http://www.msi.com.tw/html/products/mainboard/testreport_pdf/6702E/memory.pdf
http://www.crucial.com/store/listparts.asp?Mfr%2BProductline=MSI+%28Micro+Star%29%2B+Motherboards&mfr=MSI+%28Micro+Star%29&cat=RAM&model=MS-6702E+%28K8T+Neo2-FIR%29&submit=Go
http://www.mushkin.com/epages/mushkin.storefront/EN/product/991140
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Athlon_64_Unbuffered_DIMM_AVL.pdf
http://www2.amd.com/us-en/Processors/TechnicalResources/1,,30_182_869_9460%5e9461,00.html?1094454813
Good luck!

Interrupt Request

It is Noah Yang of Texas A&M studying under Dr. Zourntos for Senior Design class(ELEN405). I have couple of questions about Interrupt Request(IRQ) as we embark working on the brain.
The board we are given is a PCI-7831R, so we would have them in the PC to program and then we can have it startup running the program that we develop when it gets power. we can then provide the 5V to the board and it will work on the robot. We need some more specific way to do that.
According to the FPGA Module Training Website at
http://zone.ni.com/devzone/conceptd.nsf/2d17d611efb58b22862567a9006ffe76/62b388db80b5570286257037006...
If you see the Lesson 6 Powerpoint slide, there is some explanation about generating a physical interrupt FROM FPGA TO THE HOST.
Unfortunately, we will attach our brain(PCI-7831R) on the autonomous robot, not in the pc, but we would have it in the pc when programming, hence I don't think we will have Host VI for the window/pc unless we test the the brain of the robot by monitoring its operation on pc.
We hope that MAIN PROGRAM(running to the beacon target) in the FPGA VI should Acknowledge the interrupt(obstacle detection, avoidance, jump back to the main program) from the FPGA VI, itself. And then, FPGA can wait for interrupt to be acknowledged. Lastly, IRQ is cleared by the FPGA.
If that is impossible to have WAIT ON IRQ in the FPGA VI without a HOST VI, I wish to learn how to build our own code(from the scratch) acting like this kind of IRQ as an alternative.
For the reference, our brief algorithm is followed.
==========================================================================
MAIN PROGRAM:
*rushing to the target(signaling 5kHz sound) based on Microphone sensor.
*Interrupt 1 (When Obstacle is detected at 2 feet away)
*Interrupt 2 (crash, when bumper sensor is rising edge triggered)
*End the program when the robot gets to the target
INTERRUPT 1:
   *stop
   *Select direction by comparison of two voltage from two Ultrasonic
    sensors
   *turn until both sensors have above-threshold voltage
   *go straight 2.5 feet
   *return to the begining of the MAIN PROGRAM
INTERRUPT 2:
   *stop
   *step back by 1 feet
   *choose direction
   *return to the main program
==========================================================================
Thanks.
Noah
Noah Haewoong Yang
Electrical Engineering
Dwight College of Engineering
Texas A&M University
801 Spring Loop 2506
College Station, TX 77840
Tel: 979-997-1145
AIM: maroonsox12
I am the proudest member of Fightin' Texas Aggie Class of 05. WHOOP!

Hi Noah,
Your best bet here sounds like a state machine based architecture, which will allow your FPGA VI to handle the various conditions internally, without need to generate an external interrupt. IRQ's in the context of a LabVIEW program are sent from the FPGA to a Windows or Real Time host VI, where it is processed by the operating system and sent to the VI for processing. If the only control hardware on your robot is the FPGA board, then you won't need to explicitly generate these interrupts since there would be no computer with an operating system to receive them. Instead, if you have a state machine architecture (case structure inside a while loop, with a different case for each state and a shift register to store the next state), you can have the FPGA VI handle everything internally.
While we cannot develop your code for you, the basic structure for your algorithm could be as follows:
Move state- move towards target and check sensors for obstacle. If no obstacle, next state is move state. If obstacle 2 feet away, next state is Obstacle. If crash, next state is Crash. If target reached, next state is end.
Obstacle state- handle interrupt 1 code from algorithm (this will require multiple states). When done, set next state back to the move state
Crash state - handle interrupt 2 code (may require multiple states). Next state is move state.
End state - Done.
Of course, this is a highly simplified example, but you can see the basic structure. There are many examples of using a state machine architecture, including a design template that comes with LabVIEW that you can modify to suit your needs.
Cheers,
Matt Pollock
National Instruments

How many K8T Neo2 different versions? (and how to tell them apart)

First of all, hello everyone ^_^ This is my first post so... I hope I won't be annoying anyone.
My questions are: is there a way to tell (from the name/item-code/prod number) which version "K8T Neo2" (code 6702-E) has the Promise controller onboard, and which not?
Are there different mainboards for each country?
The (long...sorry... ) explanation to my question follows :
I live in Italy, and I'm trying to find a "K8T Neo2-FIR" MSI Mainboard, but it seems this mb model has not yet shipped in my country (I can find K8T Neo-FIS2R easily, but not the Neo2).
I visited some (german) online shops, but descriptions are often not clear enough (and images are often taken from the wrong board...): which "6702-E" mb versions have the Promise controller on board?
Having visited MSI site in different languages, it seems to me that for the american market (http://www.msicomputer.com) there are the "FIR" and "F" versions of the MB , the second without the Promise. For the german market ( http://www.msi-technology.de, the nearest country where i found online shops) there is only one 6702-E version of this mb, and it seems it's without the promise controller. Now, for the italian site (http://www.msi-italia.com) ... the link "Mainboards" leads to the international "msi.com.tw" site, where I read that the promise controller is "OPTIONAL"... so this doesn't give me any info.
If anyone has experience of this, or any info, please reply
Thank you in advance

Try the following online stores :-
http://www.ebuyer.com/customer/products/index.html?action=UFNTaG93UmVzdWx0cw%3D%3D
http://www.scan.co.uk/index.asp
http://www.overclockers.co.uk/
I'm sure they will all ship within the EEC.

Nvidia FX5900 Does it work with K8T Neo2-FIR??

I'm considering upgrading my old Ti 4400 to a new FX5900 card. Can anyone tell me if this card works properly in the K8T Neo2-FIR??

Quote
The 6600/6800/X800 series all have newer implimentations of the latest graphics programming and hardware. Buying an older card is OK if money is the only answer and you can even find the older cards cheap enough to matter. However by going with an older feneration card you are getting older generation utility as well. At some point that will come back to haunt you. Even if you don't play games or such that use the newer features now, it is pretty certain that any newer software you may want in the not to distance future will run better on the newer series card than something that is already outdated
ok, to bring the discussion to a funny point :D
1: you forgot the FX series was the last card using the best and unoptimised Anisotropic filtering
2: the shader3.0 model is nearly the same crap the shader2.0 was for the Fx series :D try playing the latest splinter cell with sm3.0 and soft shadows and tell me the fps you get
if you play games like ut2004, hl2 (with the FX shader fix to use the good looking water) then a FX 5900ultra works good enough
if you only need power without thinking about the image quality, which includes the very nice optimised ati-AF then get a Gf 6 series card.
at the beginning i wanted to update my card too coz of the shader model2.0 limitation, but now i wont. too often i compared the rendered quality and the FX always won, so i wait for a card that doesnt need to use "hardware" or "driver" "optimizations" :D - cheater

Help installing XP Pro on K8T Neo2-F!!!

I'm trying to help my cousin install XP Pro on their new pc. It's got an Athlon 64 3000+, K8T Neo2-F, 512mb Samsung ram, and an 80gb ata drive. before i started to fix it, my cousin said that he stopped the xp install midway thru because he forgot to install the RAID drivers. when i try to reinstall xp, it just freezes on DOS when it says "setup is checking hardware configuration" or sumthin like that. i also noticed that their dvdrw drive stops spinning and has a clicking noise at that point. i tried installing win 98 on it and it worked, then tried to upgrade to xp, which froze when the pc rebooted. anyone have any idea what's going on???

Hi. My setup is very similar, and I had a similar problem installing XP as well. Do as simon suggested to make sure your harddrive is clean for a fresh install. Make sure the promise 579 SATA controller and the VIA SATA RAID controller are both disabled in BIOS. Especially if your not using a RAID setup or any SATA drives you wont need them anyway.
Install XP as normal. Do not install the RAID drivers from the floppies by hitting F6. Now the XP installation should be able to complete itself. If you want to use the controllers later, enable the one (or both) you want in BIOS, Then install the drivers from the CD under Device manager update driver option.

Anyone here made WOL work with K8T Neo2?

K8T Neo2 with onboard NIC. + Windows XP SP2/Windows 2003 Server w/ SP1
What i need is to wake the computer over internet
I know the Magic Packet is arriving the computer (by monitoring traffic
when computer is alive)
but it never wakes the computer successfully, regardless the sleep mode
(s1, s3, etc). Keyboard wakes system perfectly.
if you made it work, pls let me know your settings:
- settings in BIOS/OS
- BIOS version
- NIC driver source/version

To Frankenputer:
If you turn off "allow windows to turn off..." option, "allow NIC to wake up system" will be grayed out altogether, won't it?
To Tiresmoke:
Quote from: Tiresmoke on 05-October-06, 00:53:56
What ACPI do you have it set too?
what exactly do you mean?

Transport request table

Hi all,
can u please let me know which table holds the transport request descriptions and stuff.
thanks,
Kiran.

Hi kiran,
1. the following tales :
<b>CTS : Header/Request Table     E070</b>
CTS : Client Source/Target     E070C
CTS : Last Number Of Request     E070L
<b>CTS : Object Entries     E071</b>
CTS : Texts     E07T
2. The bold ones are the important tables.
regards,
amit m.

K8T Neo2 .. Posts, but won't boot the operating system

Hi Folks,
New here. I've got a good one which I may have caused by experimenting with Dynamic overclocking at various levels.
After a normal Post, and noting that all 4 diagnostic leds are lit ( operating system booting ), the screen just goes blank.
- Reset CMOS and Dos Flashed the BIOS to 3.3 ( K8T Neo - F ) to no avail.
The other kicker is that if I try booting from the DVD (IDE Master) drive with an XP OS disk, After "press any key to boot from CD" followed by " Inspecting system configuration" .. or something like that ... again ... the screen goes blank. Dat's it. Any Ideas ?? Ugh.
Here's my machine:
[Athlon64 3500 90nm (Winchester)
K8T Neo2 - F ('64 Socket 939)
1Gb OCZ 500mhz DDR ( this is overkill for this board ... live and learn )
Evga 6800GT
One SATA Seagate 120GB Hard Drive
ASUS DVD Writer
LiteOn Combo DVD/CDRW
LiteOn DVD
Generic 6 in 1 Floppy Drive
Rosewill 500W PSU
Generic? Winmodem

Fafner,
Ok. Here's the scoop. Before reading your last reply ( also I already tried another SATA cable ), I left the SATA enabled in the BIOS, but disconnected the SATA cable from the SATA Drive. Sure enough, the XP Setup flies through all the way untill the ' Install or ' R ' recover ' option screen is displayed. The only other time I got this far was when I disabled the SATA controller in the BIOS. So now, again, with this controller enabled, but the Drive cable disconnected from the Drive, Setup goes as far as it can. Sounds like I somehow fried the SATA Drive .. eh ?
mdak

K8T Neo2-F Interrupt Request Table

Similar Messages

Maybe you are looking for