Win98 New Install/Device Mmanager issues

[PaulRichards]

Spec: mobo Asus A8N-VM CSM with AMD Athlon 64 3500+ and nVidia GeForce 6150 and 1GB RAM

Installed Win 98SE and (eventually) the drivers for the nVidia GeForce 6150. However there are some issues in Device Manager:

(i) under 'Other Devices' are listed the following all with yellow question marks after them:

PCI Bridge

PCI Communication Device

PCI Input Controller

PCI Multimedia Audio Device

PCI System Management Bus

PCI Universal Serial Bus

Each entry has the message 'The drivers for this device are not installed (Code 28)'

(ii) Under 'System Devices' there are 4 entries for Motherboard Resources. The last 3 are shown as 'working properly. The first one, with an exclamation mark, has a message 'This device is causing a resource conflict (Code 15)'. If I look at the Resources tab, in the Conflicting device list four Input/Output ranges are identified as causing conflicts:

0500-057FF: alias of Secondary IDE Controller (single fifo), and of Standard Dual PCI IDE Controller

0580-055F : alias of Primary IDE Controller (single fifo), and of Standard Dual PCI IDE Controller

0900-097F: alias of Secondary IDE Controller (single fifo), and of Standard Dual PCI IDE Controller

0980-09FF: alias of Primary IDE Controller (single fifo), and of Standard Dual PCI Ide Controller

In terms of Win 98 operating I don't detect any problems but there clearly are some issue here, and I really don't know how to fix them so advice would be appreciated.

TIA

[submix8c]

This one?

NVIDIA GeForce 6150 + nForce 430

First, fair warning - HD Audio drivers don't exist for Win 9x so you'll need an add-in card then disable the On-Board.

Second, you've not installed Part#2 ChipSet Drivers(?) according to info found here.

(Full Topic is here.)

More on (defunct - i.e. links don't work) Driver Packs. I have them all but it's unknown if it'll "cure" your problem.

Question - what is the source of the "drivers" you installed? (may help to sort this out).

Also, could you possibly export, zip, and attach the "HKLM/ENUM" branch of the Registry? (this is where the Device ID's live). so they can be inspected? Either that or download and install Everest Home Edition and find the pertinent "Ven/Dev/Subsys" (etc) entries and report what they are?

(I assume your BIOS is set to ATA/IDE mode and not SATA mode, correct?)

[PaulRichards]

submix8c: thanks for replying. I'll answer your last question first as I suspect this might be moot!

(I assume your BIOS is set to ATA/IDE mode and not SATA mode, correct?)

I'm actually dual-booting WinXP with W98 so in the BIOS set up under IDE configuration, Serial-ATA 1 Controller and Serial-ATA 2 Controller are both set to 'Enabled'. ( the only other option is Disabled).

Assuming that doesn't rule out further progress, yes, the motherboard is the one you have linked to

This one?

Second, you've not installed Part#2 ChipSet Drivers(?) according to info found here.

I opened up the CD that came with the m/b and received a message to the effect that there was no support for "Win 4.11"

Question - what is the source of the "drivers" you installed? (may help to sort this out).

I originally downloaded and attempted to install 81.98_forceware-Win 9X_international.exe from the nVidia website. This failed since the 6150 was not included in the nvaml.inf file. I then found a modified version 81.98_forceware-Win 9X_english for all cards up to G7.exe which included the 6150. This installed and gave me the nVidia Control Panel and enabled changes of resolution etc

Also, could you possibly export, zip, and attach the "HKLM/ENUM" branch of the Registry?

I've zipped up this branch from the Win98 registry and attached it.

Thx for your help.

HKLM-ENUM.zip

[PaulRichards]

Can anyone provide further guidance on what I might do to overcome the issues outlined?

TIA

[submix8c]

Temporarily working on a project - will get back with you. At least you are up and running...

[PaulRichards]

Ah, OK. Thx for your interest

[PaulRichards]

Bump ;-)

[submix8c]

"Quick Fix" (haven't had time to look at the attachment - still extremely busy) -

Go into "Safe Mode" and one-by-one, Uninstall ALL devices in Device Mangler (DO NOT REBOOT BETWEEN EACH DELETION). When all are gone, reboot normal and let Window "re-find" everything. This may tell some of the story. BTW, in "System Tools->System Information", you'll probably see any/all "problem" areas and what they may be (look there before the "quick fix").

During "re-finding" be prepared to reinstall any hardware Windows didn't store away in the INF directory.

I have an Athlon/nVidia MoBo I haven't yet tried to load yet as I'm trying to back the HDD up to preserve the OEM Restore stuff. Tricky since it''s a (@#$%^) Dell.

Edited January 6, 2012 by submix8c

[PaulRichards]

Well, that's screwed up my Win98 completely. After several restarts as 98 tried to discover my hardware I now cannot boot into 98 - I get a black screen with 'Windows Protection Error - Please restart your computer' message.

[loblo]

My bet is that your board is an nForce4 chipset based board and AFAIK there are no win98 drivers in existence for such boards. So I think that if you're lucky enough to get it to work with all the mentioned issues in device manger, that's the best you're going to get IMO.

For fully supported Socket939/Athlon64 you need an nForce3 based board (the best of which seems to be the MSI K8N Neo2 Platinum) or a VIA based board (the best of which seems to be the ASUS A8V Deluxe).

[PaulRichards]

Loblo: it's all a bit academic now. It was working, it now doesn't.

[loblo]

Well you've successfully installed from scratch before screwing it, I guess you can do it again, can't you?

[PaulRichards]

Yes, most probably. At least I know what can go wrong

[submix8c]

SOOOOOO Sorry!

Must have been the nForce(4) drivers that bit you. The method DOES work (generally speaking) with "standard" (read as "compatible") MoBo's. I've done it before, failsafe (all drivers present and accounted for, if nowhere else in the CAB's folder - the STANDARD place to install from OEM-style).