LEGACY_PCIPORT key in W2K Registry

[DeepSparklePupa]

Hi all!

Any help is appreciated. On every boot, the following error is reported in my system event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Description:
The PciPort service failed to start due to the following error:
The parameter is incorrect.

Months of searching for a clue, I've now turned to searching the registry and found this:
HKEY_LOCAL_MCAHINE -> System -> ControlSet001 -> Enum -> Root -> LEGACY_PCIPORT

Inside, there are a number of values that could serve as the faulty parameter, but I haven't a clue WTF I'm looking at. I simply do not know what the PciPort service is doing. Can anyone shed some light on the subject for me? System Stats (and listed as the SuperPooba below):

Win2k SP2
EPOX 8KHA+
Athlon 1600 no O/C
512 mb Crucial PC2100
MSI GeForce 2 MX400
Promise Fastrak TX2 with two WD 200BB HDDs on RAID 0
Soundblaster Live! 5.1

Thanks!

-DSP

 

[NogginBoink]

<< Hi all!

Any help is appreciated. On every boot, the following error is reported in my system event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Description:
The PciPort service failed to start due to the following error:
The parameter is incorrect.

Months of searching for a clue, I've now turned to searching the registry and found this:
HKEY_LOCAL_MCAHINE -> System -> ControlSet001 -> Enum -> Root -> LEGACY_PCIPORT
>>



"The parameter is incorrect" is one of Windows' most frustrating error messages. As a programmer, you want to scream at the computer, "WHICH parameter, dammit!?"

The area of the registry that governs this service is HKLM\System\CCS\Services\PciPort. But I doubt if tweaking anything in the registry will solve the problem. It sounds like, during the service startup, the service is making a bad call to a Windows API, so the service is failing to start, and the service is reporting the error that it was given from the OS back to the event log.

To the best of my knowledge, pciport is not a MS component. Do you have any idea what this service is? Perhaps that key of the registry will help you determine what it is.

 

[DeepSparklePupa]

NogginBoink - wahoo! Thanks!

OK, here's a dump of the registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PciPort]
"Type"=hex:01,00,00,00
"Start"=hex:02,00,00,00
"Group"="Extended Base"
"ErrorControl"=hex:01,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PciPort\Enum]
"Count"=dword:00000001
"NextInstance"=dword:00000001
"INITSTARTFAILED"=dword:00000001
"0"="Root\\LEGACY_PCIPORT\\0000"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PciPort\Parameters]
"IoPortAddress"=hex:f8,0c,00,00
"IoPortCount"=hex:00,55,00,00

If I were to take a wild guess, I'd say it is some stupid joystick port, or something. That's my natural guess, because I don't use one! LOL! However, I did have a ah heck of a time disabling the onboard sound while getting my SB Live! card running. Any further suggestions?

hehe - fellow programmer, I echo your sentiments on "generalized" error codes. Gaad.

-DSP

 

[NogginBoink]

To turn this service off, just set that start value to 4. If the computer keeps working, go on your merry way and forget about it.

 

[DeepSparklePupa]

Hi! Before I begin hacking the registry, I'd just like confirmation. I should be changing Start=hex:02,00,00,00 to Start=hex:04,00,00,00, right? *gulp*

Thanks!

-DPS

 

[NogginBoink]

Yep.

Or use services mmc to change the startup value to disabled. Which sets this registry value to a 4.

 

[DeepSparklePupa]

Thanks!

While I'm not currently at my machine, I'm 99.9% certain that PciPort does not appear on the list of services on my console, which, perhaps, is the crux of the issue. I'll report results this evening.

-DSP

 

[NogginBoink]

Doh!

My bad. It'll be a device driver.

Device drivers and services both go under this location in the registry.

 

[DeepSparklePupa]

Yahoo!!

Ya know, I amaze myself. I edited the value in the registry, and then hopped over to the device manager to see what I'd done. The PciPort driver is related to the Game Port for Creative SB Live - just as I had guessed! LOL!

Thanks, Noggin, for the assistance. The thing is disabled, and my logs will be cleaner for it.

-DSP