PCI System Bus Management, & Unknown Device Problems.

OK, I really need some help! I just built a new computer, using only four things from the old computer. The nVidia gForce4 MX440-SE 64MB video card, the LiteOn burner, & two hard drives.

In addition, the new system contains a Tyan S2099A Trinity i845E MB, 1.8Ghz CPU, 512MB DDR RAM, Creative Audigy Soundblaster 5.1, Creative PCI V.92 Modem, Sony CD ROM,
& Sony Floppy Drive. Multiple OS's of Windows 98SE.

Am having some conflicts in Device Manager, & don't know how to resolve them. Started out with three. Seemed to have resolved one, although I don't know exactly how I did it. Still have two left that I don't seem to be able to fix. Device Manager Statistics & System Information Statistics are listed below.

Conflicting Agent = System PCI Bus Management

General Tab
Device Type: Other Devices
Manufacturer: Non Specified
Hardware Version: 001
Drivers for this Device Are not installed (Code28.). To reinstall the drivers for thisdevice, click Reinstall Driver.
Exists in all hardware profiles.

Driver Tab
Provider:
Date:
No driver files are required or have been loaded for this device. To update the driver files for this device, click Updater Driver.

Resources Tab
The resources this device is using do not match any of its known configurations. To assing resourcers manually for this device, click Set Configuration Manually.

Resource Type Setting
Input/Output Range 0500 - 051F
No Conflicts

In Set Configuration Manually
Use Automatic Setting is checked.
Resource Type Setting
Interrupt Request: 00
Input/Output Range 0500 - 051F
No Conflicts

Conflicting Device List:
No Conflicts.

In System Information, this is waht it says.

PCI System Management Bus
Unknown
This Device Has a Problem: Code=28 (0x1C)
The drivers for this device are not installed correctly. To install the driver
for this device, click the Driver tab, and then click Update Driver.
Registry Key: HKEY_LOCAL_MACHINE\enum\PCI\VEN_8086&DEV_24C3&SUBSYS_24C28086&REV_01\BUS_00&DEV_1F&FUNC_03
Alloc resources: Logical Configuration 0
IO Range: Base=x0500 End=x051F Min=x0000 Max=xFFFF Alias=xFF, Decode=x00
Forced resources: None
Boot resources: Logical Configuration 0
IO Range: Base=x0500 End=x051F Min=x0000 Max=xFFFF Alias=xFF, Decode=x00
Filtered resources: None
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xFFFF
IO Range: Base=x0500 End=x051F Min=x0000 Max=xFFFF Alias=xFF, Decode=x00
HW Revision: 001
Driver: Driver Not Installed

------------------------------------------------------------
Conflicting Agent = Unknown Device.

General Tab
Device Type: Other Devices
Manufacturer: None Specified
Hardware Version: Not available.

Driver for this device are not installed (Code28.). To reinstall the drivers for this device, click Reinstall Driver.
Exixts in all hardware profiles.

Driver Tab
Provider:
Date:
No driver files are required or have been loaded for this device. To update the driver files for this device, click Updater Driver.

Resources Tab
Use Automatic settings is checked
Resource Type Setting
Memory Range FFB80000 - FFBFFFFF
No Conflicts
------------------------------------------------------

In System Information this is what it says.

Unknown Device
Unknown
This Device Has a Problem: Code=28 (0x1C)
The drivers for this device are not installed correctly. To install the driver
for this device, click the Driver tab, and then click Update Driver.
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*INT0800\0
Alloc resources: Logical Configuration 0
Memory Address Range: Base= xFFB80000 End= xFFBFFFFF
Forced resources: None
Boot resources: Logical Configuration 0
Memory Address Range: Base= xFFB80000 End= xFFBFFFFF
Filtered resources: None
Basic resources: Logical Configuration 0
Memory Address Range: Base= x00000000 End= x00000000 Min= xFFB80000 Max= xFFBFFFFF
Driver: Driver Not Installed
**

These devices are listed with yellow Question Marks & the little exclamation points, even though the resource tabs say no conflicts.

On the Tyan CD the default drivers for installation are Intel, but there is a folder on it containing several sets of VIA 4 in 1 drivers.

Does anyone have any answers for me, please. I am at my wits end trying to resolve these conflicts.

 

Wasn't sure exactly where my post belonged.
Thanks for moving it.

I haven't messed with the VIA drivers. The default drivers on the CD are Intel, so I figured that was the ones to use when I installed them.

I have no idea how these conflicts came about. Need to get them resolved. They seem to be causing my computer to hang a lot, resulting in having to push re-set button when Ctrl+Alt+Del don't fix things.

I've been fighting with these for days, & am really out of ideas. I've never had this much trouble resolving conflicts in Device Manager before. I really could use some help.

Thanks.

 

Two out of Four Isn't Bad -

As in Hard drives - it appears that you took your old hard drives out of your old machine and simply put them, pre-existing drivers and all, into your new machine. Unfortunately, Windows (any version) wasn't designed to acommodate this. I'd say you did very good to even boot up.

You can try removing everything with the yellow exclamation mark in device manager and see if Windows wants to help you sort things out after re-booting but I think you have just set yourself up for a series of permanent ongoing problems.

Never could understand why anyone would want multiple versions of the same operating system on one machine but as they say - "whatever blows your skirt up ".

An eventual "over the top" reinstall may help you recover without losing any data or other software, but I'd be hard pressed to recommend this as your ultimate solution. Personally, I'd buy a new HDD, do a clean install with the existing drives disconnected, reconnect the existing drives after installing any other software from original disks or discs onto the new HDD and then transfer your docs, data, email, addresses, contacts, favorites, cookies and anything else you want to salvage. Then you could reformat your other drives and get down to one good solid installation of your OS.

I know - you like having all those OS copies floating around on different partitions. Enough said.

Good Luck

 

First off, yes I did just hook everything up, not thinking straight, of course. I was not feeling well at the time, & probably should have just waited, but I didn't.

When things weren't working right, I did a full fresh re-install of windows on the first primary partition at the beginning of the hard drive, thereby deactivating the other two primary's, I thought. Anyway the only one I could boot to was the new fresh one on Primary 1. I disabled the onboard Audio right off the bat. I first inatalled the Graphics card, then the sound card, then the Modem softwares.

I forgot about installing the chipset at that time, but did it later after the conflicts appeared again. One of the three original conflicts was resolved when I installed the default chipset. Two were left to contend with. I tried removing the conflicts out of device manager a number of times, & allowing windows to do it's thing, but to no avail. It did not help.

I did image the new OS over to the other two partitions right away, after installing it to the first one, but they remained hidden to the first one since I had them hidden to begin with.

I am prepared to begin from scratch, although I do not wish to, of course.

In answer to the question of why anyone would want more than one of the same OS's on a drive is that I run several different program types. These types seem to work much better on separate OS's. Not nearly as much fighting between the programs for System operational resources, & system files overwrights don't happen nearly as much. I get less operational conflict on program softwares this way.

Since I started this post, & accidently hit the wrong button & had to edit, I cannot see the rest of what you all wrote. I am hoping I have answered your questions. I will check again & post a suplemental if I missed anything.

I think I already went, & got the latest drivers for my board, but haven't installed them yet. I will check to make sure.

Thank you for your input. I will get back to you again soon.

 

Here's something you could give a try. Be sure to have all your drivers handy. I'd make sure I had the latest chipset drivers also (important).
http://www.billsworkshop.com/techtips/cleaninstall.html

 

Yes, I keep all important data on separate partitions. Some of it is on the Master & some on the slave, but I do have enough room on the slave to move all important data from the master to the slave if necessary. And if I have to start over, I will use Partition Magic Rescue disks to convert Primary 2 & 3 into Logicals before I begin, in case that would help. I don't want to have to reformat the whole 30GB drive, unless I really need to.

No, I haven't tried to update the drivers for the PCI System Management Bus. I can't understand hardly any of that stuff on the Tyan site. They aren't too clear about stuff to me. I only used the ones on the CD. The Intel INF, the Intel (R) Application Accelerator, & the USB 2.0 drivers. All others were Optional on stuff I don't have anyway.

I will try to compare your readout to mine for the stuff in PCI Bus. That should be in System Information somewhere, right?

I discovered a new twist. Just for the heck of it, since I haven't decided for sure what to do next, I tired installing Tyan drivers on the 3rd duplicate OS.

On the INF file drivers I got a "coundn't find the patheway in the Registry, & that the registry was corrupt. It went ahead with the process though. As I recall that happened on the fresh install on Primary 1.

On the Intel (R) Application Accelator I got that I had incompatible hardware & it wouldn't install. Don't remember it doing that on the fresh install of Primary 1, but it may have. Don't think it did though. It didn't say what the incompatible hardware was though, of course. I cannot imagine what incompatible hardware I might be running for that Application Accelerator not to install. Is that Accelerator necessary? It seems to me I remember that it installed on Primary 1, but refused to on Primary 3. There should have been no difference, since they were identical.

The USB drivers installation went off without a hitch on both Primary's.

So what I need probably is the latest Tyan Drivers for my MB, the latest PCI drivers, & what else?

Windows Update will not let me in. It says I have to be running a Windows Operating System, which I am. A full OEM version. The only way I can get updates & etc., is to go to the Corporate IT site.

I am so weary of all of this. I looked on the Tyan CD, & found nothing about a Win98 Patch that could be applied for anything.

 

I have the 80GB about half full now, & the 30GB is over half full. There are not enough CD's in my house to do this. LOL All of it is important. Not a scrap of it isn't.

I have so far dwonloade these things from Intel.

Performance Software - Intel® Application Accelerator IAA23_ENU.EXE, IAA23_MULTI--iaa23_enu.exe

Performance Software - Intel® Application Accelerator IAA222_ENU.EXE, IAA222_MULTI--iaa222_enu.exe (this is the ones my CD has on it)

Aug. 2003-Tyan 2099A i845E INF Drivers-infinst_enu.exe

Intel Chipset ID Utility [CHIPID.EXE]ChipUtil.exe

AQnd From Tyan: TYAN Trinity i845E (S2099) V1.07 013003 Bios--2099_107.zip

Is this enough stuff, or do I need something else? If so, what?

 

I think I have pretty much decided to re-format the partition, like I did before, as the OS had no problem recognizing both hard drives, & all of my logical partitions, & my CD ROM drives when I fresh installed before. I am a little confused as to what order to do things in though.

I think it would go like this:

1. Reformat & Install Windows. Let it do it's thing.
2. Install INF drivers.
3. Install USB drivers
4. Install Video card
5. Install Sound card
6. Install Modem

I have never flashed a BIOS, & that sounds real scary to me. Don't I need a certain BIOS flash utility for it, or does the BIOS exe I already have, have that in it? It confuses me a lot.

Here is some info I dug up for you to see.

This is what the Intel chipset ID utility says.

Detected Chipset: Intel(R)845E
Memeory Controller: 82845E
I/O Controller: 82801DB(ICH4)
Integrated Graphics: Not detected or Disabled.

(I don't have integrated graphics, just integrated sound which is disabled in the BIOS.)


This is my PCI Bus info.

PCI bus
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0A03\00000001
Alloc resources: Logical Configuration 0
IO Range: Base=x0CF8 End=x0CFF Alias=x00, Decode=x00
Forced resources: None
Boot resources: Logical Configuration 0
IO Range: Base=x0CF8 End=x0CFF Alias=x00, Decode=x00
Filtered resources: Logical Configuration 0
IO Range: Base=x0000 End=x0000 Min=x0CF8 Max=x0CFF Alias=x00, Decode=x00
Basic resources: Logical Configuration 0
IO Range: Base=x0000 End=x0000 Min=x0CF8 Max=x0CFF Alias=x00, Decode=x00
Driver: System\0007
Driver Date: 4-23-1999
Driver: pcimp.pci
File Size: 16208 (0x3F50)
File Date: 4/23/1999 10:22 PM
Company Name: Microsoft Corporation
File Version: 4.10.2222
Driver: pci.vxd
File Size: 65895 (0x10167)
File Date: 4/23/1999 10:22 PM
Company Name: Microsoft Corporation
File Version: 4.10.2222

Most of the above concures with yours, but not all.

I have several of the ACPI IRQ Holder for PCI IRQ Steerings Listed. They are below.

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000001
Alloc resources: Logical Configuration 0
IRQ: 11 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0022
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000002
Alloc resources: Logical Configuration 0
IRQ: 10 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0023
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000003
Alloc resources: Logical Configuration 0
IRQ: 10 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0024
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000004
Alloc resources: Logical Configuration 0
IRQ: 11 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0025
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000005
Alloc resources: Logical Configuration 0
IRQ: 5 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0026
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
This device is disabled.
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000006
Alloc resources: None
Forced resources: None
Boot resources: None
Filtered resources: None
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0027
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
This device is disabled.
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000007
Alloc resources: None
Forced resources: None
Boot resources: None
Filtered resources: None
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0028
Driver Date: 4-23-1999

ACPI IRQ Holder for PCI IRQ Steering
System
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0C0F\00000008
Alloc resources: Logical Configuration 0
IRQ: 9 Mask: x0000
Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Basic resources: Logical Configuration 0
IRQ: 0 Mask: xDEB8
Driver: System\0029
Driver Date: 4-23-1999

 

This is what I would do.

Remove sound and modem cards from computer.
Format.
Install windows.
Install chipset drivers.
Install video drivers.
Add in sound card and install drivers.
Add in modem and install drivers.

A BIOS flash may not be necessary. You have to have the absolutely correct flash software, or you end up with a paperweight.

 

Pete, Zander, Mark,

I re-formatted Primary 1, C drive, and re-installed Windows. Let it do it's little dances.

Then Installed the Intel INF drivers I downloaded from the site Pete gave me. They went in just great.

Then installed the USB 2.0 drivers off of the Tyan CD.

Then installed the Video card, then the Sound card, then the Modem.

Bless my happy little heart, all is working as it should now. No conflicts listed!

I had hoped to fix it without having to start fresh, but Oh well, guess you have to do what is necessary.

One thing I learned from this is that when you try to put an existing OS onto a newer motherboard, even if it does have the same BIOS version as the old one, it DON'T work. I'd never tried that before, but hey, you learn what don't work by trying stuff.

Another thing, I learned is that installing the MB drivers is an absolutely essential first task after installing a fresh OS.

Thank you Pete, so much, for those links to get the drivers, & stuff. I really appreciate it. You'll never know how much. I probably would have never found them on my own.

Thanks to all of you, Pete, Zander, & Mark. I do appreciate all of you so much. You're a bunch of sweeties.

 

1 out of 3 Ain't Bad....

Glad to learn that you have a working OS on there but is this to say you have two others that aren't?

 

Rockster,

The other two worked, & still do. Just not the way they are supposed to, and yes, for the moment I still have them on here. How do you think I'm answering these posts? Without another Internet ready Primary, I couldn't do that right now. Even though it isn't working exactly properly, it will still get me to the BBS. No need for me to worry about it. The other two are hidden from the main one. It can't see them. None of them can see each other.

Very soon they will be working just like the Primary 1 does when I get Primary 1 fixed up with the basic necessary programs for maintenance, & image it over to them, then proceed to install the programs on them that are pertinent to their reason for existence.

I desire no other OS at the present time, & whether you believe it or not, Rockster, there are definite advantages to having 2 or 3 Primary's of the same OS. There are much less program conflicts, much less system file overwrites, specific tasks for each Primary OS to contend with instead of umpteen dozen of them for only one. Less resource conflicts between programs. Operations run much more smoothly with specific programs installed on specific Primary's for specific tasks. Not to mention, if Primary 1 crashes, I still have others I can boot to, & restore a working image for it, using one of them to do it, or the Drive Image rescue disk.

When I had only one Primary, I was experiencing almost constant program conflicts. With 2 or 3 that are set up for specific operations, I don't have that problem. It may not be worth it to you but it is very much worth it to me.

When I tried to set up this new system, no, It didn't work the way I tried it, & I had to start from scratch, & I made mistakes again. EVERYONE makes mistakes! Even experts! Just that experts usually know how to resolve them more quickly, & easily than the majority of us do.

One thing I do know is that by having different Primary's for performing certain operations is not a mistake, & works great for me. Much better than having only one that has constant conflicts between programs, mostly because of system file overwrites upon program installations, which happens a lot, even when you make sure your program installations are done on a basis of the age of the programs, with older progs going in first. With the way I set mine up, this problem is almost non existent. Sure, Windows still has it's occasional brain scrambles, but not nearly as often.

Although I have increased my computer knowledge maybe 20 or 30 times over since I first bought one, since all I could do was turn one on back then, there is much more that I have to learn, & even with the frustrations that come with them, each experience teaches me something, & no experience goes without it's rewards, even when I must have help to resolve the problems, or to confirm what I already suspect what I will have to do.

Thanks again to all of you who helped me to resolve this by giving helpful constructive advice, & providing utilities that were very useful. I appreciate it more than you know.