Re: New hardware : io conflict (code 12)
From: karma (karma_at_not.a.mail.address.com)
Date: 11/23/04
- Next message: User: "Re: Opening HDD partition in Explorer takes ~30 sec"
- Previous message: Ritter197: "SW for Bass sound reduction?"
- In reply to: R. C. White: "Re: New hardware : io conflict (code 12)"
- Next in thread: R. C. White: "Re: New hardware : io conflict (code 12)"
- Reply: R. C. White: "Re: New hardware : io conflict (code 12)"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 23 Nov 2004 16:50:16 +0100
R. C. White wrote:
> 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
- Next message: User: "Re: Opening HDD partition in Explorer takes ~30 sec"
- Previous message: Ritter197: "SW for Bass sound reduction?"
- In reply to: R. C. White: "Re: New hardware : io conflict (code 12)"
- Next in thread: R. C. White: "Re: New hardware : io conflict (code 12)"
- Reply: R. C. White: "Re: New hardware : io conflict (code 12)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
