Welcome to the DoItYourself Forums!

To post questions, help other DIYers and reduce advertising (like the one on your left), join our DIY community. It's free!

registry help


BSB's Avatar
Member

Join Date: Mar 2001
Posts: 782
WI

09-26-01, 05:10 AM   #1  
anyone know where at in the registry IRQ's are? are they in one central location or spread out?

I hate how MS locks IRQ's wether its plug and play enabled in the bios or not.

Have reloaded win2kpro and 98se on two sep 20gb drives but am unable to get each device to "pick" the correct IRQ I tire of uninstalling and reinstalling each device "hoping" that the correct IRQ is chosen. I have decided that would be easier to just "force" ms to use the IRQ's I choose.

any help is appreciated.

Brian

 
Sponsored Links
2000's Avatar
Member

Join Date: Dec 2000
Posts: 1,019

09-26-01, 05:21 PM   #2  
CtrlPanel, System, [tab] Device Manager is an easier way to view, change, or reserve resources.
Overview: Start winhlp32 c:\windows\help\windows.hlp Index - IRQ, Contents - Troubleshooting.

Editing the Registry directly is the hard way. For IRQs, I/Os, and DMAs dynamically allocated, the .dlls used are under HKEY_LOCAL_MACHINE\DesktopManagement\Data\2 (in my sys.), [cascaded interrupts; not non-cascaded]. Below that is HKEY_LOCAL_MACHINE\Enum\BIOS with subkeys for
system controllers, etc. Below Enum are subkeys for other devices [floppy, modem, etc.]. But most of the entries are combinations of text & DWORDS, and some Keys represent the IRQ itself.

Suggestions before making changes:
1. Print current status. >CP >Sys >DM (x view type) >Computer >Print
2. Verify Wins view & free resources as seen in CMOS. Typical: Advanced >Resource Config >"both" Memory Reservation [I/O ranges] & IRQ Reservation. Assigning known free resources [except IRQ 2 or 9, cascade bridge] through Win and DM will reduce headaches.
3. Use MSD.EXE in RealDOSMode. The three views may help isolate unforeseen problems.

My guess is that some resources will have to be set system wide for both, and others may have to be set current for each OS. Just a guess. "Zip" - my knowledge of Win2000pro.

Got (milk) documentation?

Note to casual readers: BSB is an advanced user, and this is a difficult problem. DO NOT use this message as a guideline for playing with system resource settings. Assigning IRQs and the respective I/O address(es) or DMA channel is not for the faint of heart or casual user. You will be punished if you err.

 
BSB's Avatar
Member

Join Date: Mar 2001
Posts: 782
WI

09-27-01, 12:25 AM   #3  
I would much rather use the device manager to change the IRQ settings, but win2kpro and 98se seem to have unintelligent minds of their own and will not let me change irq settings. (unless I am missing something. hmmm...maybe there is a setting in the registry that will unlock the IRQ's????

Will try the managment console for win2kpro .

thanks for the input. Will keep ya posted if I find a better simpler way.

Brian

 
2000's Avatar
Member

Join Date: Dec 2000
Posts: 1,019

09-27-01, 05:22 AM   #4  
BSB, humor me. One Registy? If so, I suspect Winpro is the culprid (another level of simplicity from MS). A multi-boot manager program, in lue of FDISK to set the active partition, with independant OS installtions might be easier than hacking through hardware and the Regsitry. I understand that your intent differs, but it seems to verify a conclusion: on the current course it's a MS view of the World..., complete with its own specs. [It's my way or the highway]. [And PnP defined by MS does mean limited choices].

Concerning dynamic allocation with DM in Win98 if free resourses are available they can be defined system wide. Given a list of current settings, remove "selected devices", one by one, then reserve the resourse. During device reinstallation you should be able to assign those resouses. If said devices are low level the bloody alternative is abandon PnP management and devices...the non-MS view.

No doubt, someday someone will knuckle bust both into submission. But I don't think it's worth the effort to extract, modify, and import keys, or mangle other control files, especially when MS insists on enforcing their view with auto writes. [The result may be two OSes that run, verses one that runs a full throttle].

P.S.
I fully expect XP to be another layer of incompatible simplicity, and totally invasive [naturally by "consumer demand"]. It's funny how consumers don't know what they want until MS tells them what that is!


 
BSB's Avatar
Member

Join Date: Mar 2001
Posts: 782
WI

09-27-01, 06:37 AM   #5  
Have 2 20Gb removable drives, each has its own OS. Shut down, insert 98se, restart 98se, shutdown, swap drives, restart with win2kpro. (actualy have 3 removable drives, with 2 inserts, the 3rd is a 6Gb storage drive)

I have in the past had to remove all hardware and then re-install each one as I restarted to get the desired IRQ's (or acceptable)how ever this time both OS's seem to be unforgiven in letting me set IRQ's, wont do it trial by error, or setting IRQ's in bois. Because certian devices only work on certain IRQ's, I have to use modem on irq7, no scanner untill I free up 7, and put modem on 9 or sound on 10 and modem on 5. (modem will not work on 2)

Really irks me when this happens, and am mentaly spent by time I finaly get things set up correctly. *groan*

Brian

 
2000's Avatar
Member

Join Date: Dec 2000
Posts: 1,019

09-28-01, 02:38 PM   #6  
Removable drives changes things! I envisioned two primitive scenarios, dubious and "if case then" at best. I did some snooping into 2k and IRQ assignments. Not in depth...but enough to grasp configuration differences.

I suspected PCI steering, so I started with that. In 2k the acronym and new concept for PCI steering is PCI sharing. PCI sharing and steering differ completely. Control concept: sharing 2k - BIOS, steering 9x(2)se - OS.

In both the BIOS initializes PCIs, but with sharing the BIOS sets up extended vectors then hands them to the OS. Sharing does not support ISA - PCI routing ["balancing" in the Official MS BS that follows] http://support.microsoft.com/support.../Q252/4/20.ASP "BS", due to the omission of an undocumented 2k installation feature ["standard pc"] that apparently allows 2k to configure an older emulation. You may find the following helpful http://dv411.com/irqguide.html

As of 95(2) PCI steering could be enabled or disabled from the DM applet, [tab] system [tab] system [tab] PCI bus. [tab] settings to override the PCI bus (IRQ 2 & 9) and or select from the table options to use BIOS, hardware, extended BIOS. 2k - no duplicate feature. BTW, PCI steering is one of the keys to "unlocking" [as you called it] dynamically allocated IRQs in the Registry, but it doesn't apply to 2k. The other key is bios.vdx (disable PnP - a reversion to DOS days).

To ensure facts, I nosed into 9xes a little. A few of the more recent systemboards require a patch for PCI communication between the BIOS and OS to operate correctly. Evidently some of the BIOS PCI initialization vectors are "lost" no matter which table is selected [checked] in the PCI bus property sheet, and 9x OSes use a "default" configuration. The patch, if necessary, applies to similar losses in 2k. I don't know if this is applicable, but I thought I would put it before you.

During my 20 minute tour I ran across any number of MthBd sites spec-ing PCI slots for IRQ assignments. It may save time over trial and error.

My general conclusion is if the MthBd is spec-ed for 2k; chipsets checked for patch updates, the BIOS supports extended vectors; compliant devices are used, and 2k installation is the older emulation to facilitate PCI tweaking, then both OSes have a better chance of coexistence. If you knuckle bust it otherwise, do share.

 
Search this Thread