Thanks, James - I'll give it a shot today and see if I can make it work. I'm guessing there's some entry somewhere in the Windows registry that allows Windows to "remember" hardware it's already seen and assign the same resources to that hardware if it sees it again. Cleaning this entry out would probably work, but I haven't been able to find exactly what entry and where it is.
Also, on the Resources tab of the Xen drivers - do you control whether the resources can be modified or not, or is that up to Windows? Many drivers will let you set a manual resource configuration, like changing the IRQ to something else, but it seems like some of them won't let you modify the settings at all. I know, I know, manually assigning resources isn't the greatest idea - I should leave it up to the O/S to device - but it seems like something that may provide a way around this situation without the driver rewrite.
Anyway, thanks, again for the fix - I'll give it a try here in a while and let you know.
>>> "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 2008/11/11 03:29 >>>
I have built a xenpci.sys that will tell Windows not to give it an IRQ
under 16. Other than testing that it doesn't crash I haven't given it
any other testing. You can download it at:http://www.meadowcourt.org/downloads/xenpci.sys.no_irq_under_16.xp.bin
rename the downloaded file to xenpci.sys and copy it to
c:\windows\system32\drivers, then reboot.
I also have a windows 2003 version there.
If, for some reason, windows won't assign an irq > 16 to it then a boot
with /GPLPV will probably fail (bug check 0x7b), but you should still be
able to reboot without /GPLPV.
Let me know how it goes. If it boots, assigns an irq > 16, and your
stability problems go away, then I'll keep the fix in there.
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.