>>Help all,
>>
>>I have a Win95 (OSR2) which had only a COM1 with a BitSurfr for ISDN support attached.
>>
>>I recently had need to attach another modem, so I bought an internal one and tried to install it on COM2.
>>
>>What happens, though, is that the BitSurfr, which always was on COM1 and remains configured as COM1, somehow gets switched to COM2.
>>
>>Looking at the PORTS under Device Manager, I do see something strange: COM2 shows as "Basic Configuration 02" and correctly is on IRQ#3 and at the right addresses, BUT when viewed through "Basic Configuration 00" it shows the same settings as COM1.
>>
>>I have been into SAFE mode and deleted all COMs, all modems and the MS dial-up adapter, but still no joy when re-installing. All is fine for the re-install of COM1, but when I move on to COM2 all hell breaks loose again.
>>
>>It seems that if I could get rid of that COM2 "basic Configuration 00" setting with the COM1 info, then all would likely be well.
>>
>>Does anyone know a way to fix this? Is there something akin to REGCLEAN for the WIN95 CONFIGURATION information? Does anyone know how to safely manipulate that WIN95 configuration information?
>>
>>I really need to get this new modem operational.
>
>It sounds like the best alternative would be to completely rebuild the hardware enumeration registry key structure. The safest way to do this is to re-run SETUP after going into Device Manager from Safe Mode and deleting all keys. Reboot, and boot to the command prompt; run the OSR2 setup from CD or from a copy already on disk; it's probably better from a disk image, since no real-mode drivers would be needed to get to the Win95 install 9depending on the CD-ROM drive, you might need real-mode ASPI or CD drivers and MSCDEX to load to start Setup.
>
>If you don't want to go through all that, you can delete the registry key hierarchy HKEY_LOCAL_MACHINE\Enum and reboot several times; this will cause Win95 to resense the hardware configuration and rebuild the enum keyset, but it may take several reboots to sort things out.
>
>Since you are dealing with an internal modem, especially if it's an ISA device, make certain that your motherboard doesn't allocate any resources required by the internal modem to PCI; this is especially worrisome if the modem is -not-PnP compliant. You may need to go into the motherboard BIOS and reserve IRQs and I/O ports manually. You may also have to disable on-board devices; for example, even though no connector may be visible, the motherboard may have a second serial port built onto it, and you may have to disable it or change its settings (the exact procedure varies according to the BIOS, so check your motherboard manual.)
>
>You might want to wander out to sysdoc.pair.com (Tom's Hardware Page, a great resource in and of itself) - it has excellent links to BIOS resources, setup and upgrade guides, and aside from a strong anti-Intel BIOS, is probably one of the best one-stop hardware reference pages. Be warned - it is populated and frequented by flat-earther systems programming types and solder weenies....

That should be bias, not BIOS. There's also a strong anti AMI WinBIOS bias, but we don't talk about that in polite company...