New hardware : io conflict (code 12)

[karma]

Hi !

I know, crossposting is really really bad, but this drives me crazy :

I've recently bought a Leadtek TV2000xp Expert. The problem is I just
can't use it under Windows XP Pro because of a "code 12" error code in
the device manager (not enough free resources blablabla). After looking
a bit deeper, it seems like my geforce 6800 GT is sharing some I/O
memory access with the mainboard cpu-to-agp controller.

I can't change any I/O memory addresses under XP ("use manual settings"
checkbox in the control panel is always grayed, for ALL devices).

- it seems I can't disable ACPI in motherboard's bios. Even reinstalling
XP with ACPI disabled doesn't help
- All devices have a different IRQ
- I can't disable any device because I need all of them.
- All drivers (including INF for motherboard devices, bios, ...) are up
to date.

Is there a tweak to load drivers in high memory (tweak that could be
used for other devices) under Win XP pro? Can I modify Leadtek INF files
to change memory usage ?

Thanks in advance for your help !

Karma


PS: Here is all the hardware I have. Please tell me if you need more
details.

Abit IS7-e2 (bios 1.6, Drivers 6.2.1.1001)
Intel P4-3GHZ
512 DDR PC3200
Onboard Lan (Realtek 8139 with latest driver from Abit)
Onboard AC97 Sound device (same issue with additional PCI SBLIVE card)
Geforce 6800 GT with latest NVIDIA WHQL Driver
2 IDE Hard drives (SATA controller is disabled)
1 IDE DVD burner (pioneer 107D)

 

[R. C. White]

Hi, Karma.

I know, crossposting is really really bad, but this drives me crazy :

Crossposting is not bad, so long as it is not abused. Careful selection of
2 or 3 appropriate NGs is quite acceptable.

I've recently bought a Leadtek TV2000xp Expert.

What is that? A modem? A printer? Graphics card? What? Do you have the
right WinXP drivers for it?

the device manager (not enough free resources blablabla).

Is there a tweak to load drivers in high memory (tweak that could be used
for other devices) under Win XP pro?

These lines sound like you haven't yet dumped the Win9x/ME mindset. We
never worry about "free resources" in WinXP. And WinXP has no need for the
concept of "high memory" like we had to deal with in MS-DOS and Win9x/ME.
Are you dual-booting with an MS-DOS-based version of Windows on this
computer?

I have other questions, but these will do for now.

RC

 

[karma]

Hi !

Thanks for your answer, I'll try to be more precise.

Crossposting is not bad, so long as it is not abused. Careful selection
of 2 or 3 appropriate NGs is quite acceptable.

You're right, but being stuck in 640x480x4bits is quite annoying to read
docs like this one (poor excuse, I know).

What is that? A modem? A printer? Graphics card? What? Do you have
the right WinXP drivers for it?

As the name suggests, it's a TV/FM tuner (PCI). I have of course the
latest Leadtek drivers for WinXP.

These lines sound like you haven't yet dumped the Win9x/ME mindset. We
never worry about "free resources" in WinXP. And WinXP has no need for
the concept of "high memory" like we had to deal with in MS-DOS and
Win9x/ME. Are you dual-booting with an MS-DOS-based version of Windows
on this computer?

I've read somewhere that fixes exist for some drivers so they take less
ressources where these are needed (seen on Microsoft support site). I
never had to worry about free ressources before, but this time I'm quite
confused : I've only 1 pci device, 1 AGP and 2 onboard, and Windows just
can't find enough IO addresses ?!? I've also tried do deactivate every
devices but AGP one (included network, sound card, USB, ...), and it
doesn't help. Seems like they both want their part of memory, without
being willing to move elsewhere.

I have other questions, but these will do for now.

RC

Let's go

Bye!

Karma

 

[karma]

Oops, I forgot to answer one question :

Are you dual-booting with an MS-DOS-based version of Windows
on this computer?

The answer is no

Bye


Karma

 

[R. C. White]

Hi, Karma.

As the name suggests, it's a TV/FM tuner (PCI). I have of course the
latest Leadtek drivers for WinXP.

Ah! OK. I don't have that, but my graphics card is an ATI All-in-Wonder
9000, so I do get to enjoy watching TV on my computer - but no FM.

I've read somewhere that fixes exist for some drivers so they take less
ressources where these are needed (seen on Microsoft support site).

Could you point me to that site? I'm no techie and may not understand what
I read there, but lots of true gurus read this newsgroup and one of them
should jump in with some solid advice on this.

I never had to worry about free ressources before, but this time I'm quite
confused : I've only 1 pci device, 1 AGP and 2 onboard, and Windows just
can't find enough IO addresses ?!? I've also tried do deactivate every
devices but AGP one (included network, sound card, USB, ...), and it
doesn't help. Seems like they both want their part of memory, without
being willing to move elsewhere.

These problems sound familiar - but I haven't seen them since I left Win98
behind. I did have IRQ problems for the first year after switching to
Win2K, but that was before hardware manufacturers had written new
Win2K/XP-compatible drivers for their peripherals. Up to that point, I had
to intervene strongly in trying to get the right PCI cards in the right
slots to avoid IRQ conflicts - and never did get my ADSL modem and Sound
Blaster working simultaneously. Finally, I found a "beta" BIOS on the
website for my motherboard maker (DFI) and flashed that. Within a day or
two, my IRQ conflicts resolved themselves and I had no more such problems.

You may be trying too hard, Karma. In your first post, you said:

- it seems I can't disable ACPI in motherboard's bios. Even reinstalling
XP with ACPI disabled doesn't help

Why would you want to disable ACPI? I think this is the key to getting your
problem resolved. I would try these steps:

1. Enable ACPI on mobo; the easiest way might be to reset the BIOS to
defaults, or to optimal defaults, if they are available in that BIOS.

2. Disconnect all hardware except the minimum to install WinXP.

3. Boot from the WinXP CD-ROM and install WinXP. (Use the in-place upgrade
procedure from KB 315341 to preserve existing applications.) This should
detect the HAL (ACPI) properly and insure that support for it is installed
in WinXP.

4. Add back the PCI cards one at a time, rebooting after each to let WinXP
detect it and install the default drivers on the WinXP CD-ROM. I probably
would start with the problem card - the Leadtek.

5. When all the cards are in and working, at least minimally, go to the
website for Abit, Leadtek and the others to get the latest drivers and
install them.

Have you asked the Abit gurus at alt.comp.periphs.mainboard.abit? Surely
you are not the only Abit user with such problems.

RC

 

[karma]

Could you point me to that site? I'm no techie and may not understand
what I read there, but lots of true gurus read this newsgroup and one of
them should jump in with some solid advice on this.

http://support.microsoft.com/default.aspx?scid=kb;en-us;321060

It's about a code 12 with a pcmcia lan card. Their hot fix seems to be a
new inf file. (quote : "IMPORTANT: After you install this hotfix, the
driver can load into any available physical memory to eliminate the code
12 error, ..."). I think it may be possible to do the same with other
devices

Why would you want to disable ACPI? I think this is the key to getting
your problem resolved.

I've also read somewhere that acpi driver prevents user from playing
with irq and memory resources. In fact I can't modify any settings even
with ACPI disabled.

I would try these steps:

1. Enable ACPI on mobo; the easiest way might be to reset the BIOS to
defaults, or to optimal defaults, if they are available in that BIOS.

Already done. First move, in fact

2. Disconnect all hardware except the minimum to install WinXP.

Done too, second move, but the conflict is still there (all onboard
devices disabled, soundcard removed,...).

3. Boot from the WinXP CD-ROM and install WinXP. (Use the in-place
upgrade procedure from KB 315341 to preserve existing applications.)
This should detect the HAL (ACPI) properly and insure that support for
it is installed in WinXP.

I've even tried to change HAL during the install procedure. Still
doesn't help. Always the same conflict with the same IO adresses.

4. Add back the PCI cards one at a time, rebooting after each to let
WinXP detect it and install the default drivers on the WinXP CD-ROM. I
probably would start with the problem card - the Leadtek.

The problem is that the conflict (and the vgasave mode) appears as soon
as I add this device in my box (first or last device inserted).

5. When all the cards are in and working, at least minimally, go to the
website for Abit, Leadtek and the others to get the latest drivers and
install them.

Already done, of course, (I would call it 'move 0'). I wouldn't ask here
before searching a bit myself (ok ok, some people do that).

Have you asked the Abit gurus at alt.comp.periphs.mainboard.abit?
Surely you are not the only Abit user with such problems.

Yep, nvidia too, and I've also written to abit and leadtek tech support
(no answer yet).


Thanks again for your suggestions


Karma

 

[Woody]

Some system boards have a restriction on using AGP and first PCI slot.
Possible conflict....

 

[R. C. White]

Hi, Karma.

Sounds like you've already thought of everything I can think of. :>(

Sorry I can't help. Good luck, and please post back when you find the
answer.

RC

 

[Kadaitcha Man]

Hi, Karma.

Sounds like you've already thought of everything I can think of. :>(

Sorry I can't help. Good luck, and please post back when you find the
answer.

BWAHAHAHAHAHA!!! How to become an MVP (Most Valueless Prostitute)... reply
to technical posts with "Sorry, I can't help you. But I'll post anyway!"




--

 

[karma]

Hi!

Some system boards have a restriction on using AGP and first PCI slot.
Possible conflict....

I've tried all pci slots for the new tv card, with all other devices
disabled. Resetting the bios didn't help either :/ The only thing I can
do now is putting the tv card in another (linux) box. I don't have all
features but, at least, it works...

+++

karma