Hi,
in 2k there is a lot that is not there in 98. To be more precise, probably there is nothing in 2k that was taken from 98 (to be honest, I hope so 
The Interrupt-Line register is used by software only. It provides storage for the interrupt line that was assigned by software (=BIOS). It has no meaning for the hardware because PCI devices do not care about interrupt lines. Each device uses the same INTA line on the bus. The main board (BIOS) routes the INTA line of each slot to IRQs 0…15. Refer to the PCI spec for details.
At power on the BIOS assigns hardware resources to each PCI device (if this feature is enabled by BIOS setup). The IRQ that is assigned for each device is stored in the Interrupt-Line register of that device.
When Win98 boots up it enumerates all PCI devices. It will use the hardware resources assigned by the BIOS if this does not cause conflicts with other devices. If there are conflicts then Win98 may re-confgure particular devices.
2k does manage all the hardware resources by itself (ACPI mode). It does not rely on the BIOS except for devices that are requried for booting (HD). Therefore, it does not need the Interrupt-Line register.
It seems that Win98 wants to see a valid configuration for a device that has been configured by the BIOS. But, your configuration cannot be valid because the int line is missing.
I could imagine that the problem does not occur if your device is not configured by the BIOS at all. Try the following: Go to BIOS setup. If there is an option labeled “PNP OS” or something like that then set it to PNP OS = yes. Now your BIOS should configure devices only that are required for booting.
–
Udo Eberhardt
Thesycon GmbH, Germany
xxxxx@thesycon.de
www.thesycon.de
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Kanth
Sent: Thursday, July 04, 2002 9:40 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Read-only PCI interrupt line register.
Hi,
Thank you for the reply.
Yeah, I have spoken to the H/W team. But, according to them it
takes quite a
long time to get the next version of the device. But, we have a
demo coming
up. Hence, I want to know is there any method to bypass this problem
temporarily, on Win98 platform.
As I told u earlier, I have developed the driver for same device on Win2k
and couldn’t face any problem. How come? Whats there is 2k thats not there
in 98?
kanth
----- Original Message -----
From: “Udo Eberhardt”
> To: “NT Developers Interest List”
> Sent: Thursday, July 04, 2002 3:46 PM
> Subject: [ntdev] RE: Read-only PCI interrupt line register.
>
>
> > If the Interrupt-Line register is read-only then your device does not
> conform to the PCI specification. You should talk with your hardware guys.
> >
> > –
> > Udo Eberhardt
> > Thesycon GmbH, Germany
> > xxxxx@thesycon.de
> > www.thesycon.de
> >
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Kantharaj
> > > Sent: Thursday, July 04, 2002 7:00 AM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Read-only PCI interrupt line register.
> > >
> > >
> > > Hello Friends,
> > >
> > > I am developing a NDIS Miniport driver for win98. But, in the device,
> > > Interrupt-Line register (i.e. at offset 0x3c of
> configurations space) is
> > > made as read-only register in the hardware. Hence, OS fails
> to read the
> > > BIOS assigned interrupt line and reads it as 0x00. Because of this, my
> > > driver is failing to get installed and gives the messege “BIOS did not
> > > give an IRQ to the device”.
> > >
> > > Please, can somebody help me how can coninue now? How can I know what
> IRQ
> > > was assigned by BIOS and bypass this cross verification by
> OS? How can I
> > > install my driver with this register being read-only?
> > >
> > > Note: I have developed the NDIS driver for same device windows 2000
> > > platform without any problems.
> > >
> > > Any suggestions or solutions are welcome.
> > > Thanking you all in advance.
> > >
> > > kanth
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@thesycon.de
> > > To unsubscribe send a blank email to %%email.unsub%%
> > >
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@uniwide.co.kr
> > To unsubscribe send a blank email to %%email.unsub%%
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@thesycon.de
> To unsubscribe send a blank email to %%email.unsub%%
>
>