Yellow> ! PCI bus ...Device Manager after ACPi
Mike
activated ACPi via bios & Install new hdwe
& problems...
de-activated it and problems remain
re-activated it...etc... reinstall 98 ... fiddle....
Device Manager
! PCI bus
Yellow exclamation showing
properties report;
"Windows could not load the drivers for this device because
the computer is reporting two PCI.VXD bus types.
(Code 2 )
Contact your computer manufacturer to get an updated
BIOS for your computer."
Reflashed bios, it had been working fine before I flipped that
Award bios switch to On
... reloaded Win98... no help,,, older saved scanreg /restore ,,,no help
either
Can't seem to beat this one,,,
PCi bus won't give or assign IRQ's to;
PCi Graphic card
PCi Sound card
PCi Modem
After blood, sweat & tears plus lots of unmentionables
I finally got lucky with an ISA modem... so now I ask,;..
Any helpful suggestions ?
Thanks,
Walter Clayton
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Mike wrote in message ...
Mike
Thanks Walter... enabled (2)bios USB's ... no diff's .
also clicbox enabled in DevMgr PCI bus Properties...
IRQ Steering is noted as disabled there.
Doesn't seem to matter which combination
of 'PCI bus' `properties switches are checked,
it's marked Disabled there.
Wishing for a simple oversight.
PCI bus is being very stubborn...
guess its appetite for irq's currently is `Ziltch.
Walter Clayton
suggestion is a little hairy, but it's work for me in the past.
Leave USB enabled in the BIOS. Boot into safe mode, go into devman and
delete everything in the system branch. Reboot. 98 will begin to reconfigure
itself to any differences in the BIOS. During this process it will reboot
quite a few times. Also, you may temporarily loose access to your CD. If at
any point during the reconfiguration it asks for a driver from the CD and
the CD has not yet been set up, just hit cancel for that driver. Once 98
boots back up without asking for a reboot. Go back into device manager and
see what the remaining problems are. First clear up any unknown and
duplicate entries. Easiest way to do that is to delete the unknowns, and for
any device that is listed more than once, delete all occurrences of that
device then reboot. Again, this may take several reboots but it should sort
it self out. After that install anything missing, although I don't think
you'll see of those.
Post back with the results.
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Mike wrote in message ...
>
MrScary
http://www.via.com.tw/support/faq.htm#16
--
Attila Szabo
Microsoft-MVP (DTS)
Bell Atlantic-Services Technician
a.k.a.' MrScary '
x-no-archive: yes
Walter Clayton <w-cla...@SPmailandnewsAM.com> wrote in message
news:uKnzhqXy#GA.308@cppssbbsa03...
Mike
MrScary > wrote
: What about applying VIA's patch for IRQ routing?
: http://www.via.com.tw/support/faq.htm#16
:
VIA... It's installed v1.3a latest I think, shows up in Add/Remove too :)
thanks though.
I've deleted HKLM...Enum and forced redetection ,
& re-enum'd hdwe both with & without ACPI enabled .
!PCI bus exclamation stays and won't let IRQ's flow.
will `Find hdwe again (after some fiddlings shortly) & see if Detect.txt
shows anything diff but I don't 4see anything changing. Thinking I'm
overlooking??? or..
MrScary
a reinstall if the latest version after a full reboot might be worth trying.
Have you seen this info already?
IRQ STEERING AND DEVICE ENUMERATION
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
**Should be off-line to do this**
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1.) Right click on ' My Computer '
2.) Select ' Properties ' from the pop-up menu
3.) Select the ' Device Manager ' tab of System Properties
4.) Tick on ' View Devices by type ' and open ' System Devices ' found at
the bottom of the device tree
5.) Highlight ' PCI bus ' and click on the ' Properties ' button
6.) Adjust or Disable the settings under the ' IRQ Steering ' and/or the '
Settings ' tab to get the desired results. Make note of how you found these
settings before you attempt to change them as a precaution.
a.) FIRST try changing the Device Enumeration under the 'Settings' tab
from Hardware to Bios. This does the trick in many cases for various
problems. If Not....
b.) Experiment with enabling or disabling all the combinations of
possible settings to try to get the desired results. At times, the bios
setting that you may or may not have , PnP Aware OS, also has a bearing on
these settings....(See below for more info)
7.) Make sure you do a full reboot after every change while testing.
GENERAL INFO
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Settings Tab.....
1.) Device Enumeration -You can use either hardware or BIOS to configure
devices connected to the PCI bus.
- Click Use Hardware for faster performance with fewer problems.
- Click Use BIOS if one or more devices are not working properly when
Use Hardware is selected.
NOTE: Clicking Use BIOS can cause Windows or a device to stop
responding.
2.) Override Bridges - Select this check box to disregard the BIOS settings
for the PCI bridge.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The IRQ Steering Tab.....
1.) Use IRQ Steering - Specifies that Windows programs use IRQ steering. If
you select the Use IRQ Steering check box, PCI bus devices behave more like
Plug and Play devices. If you click to clear the Use IRQ Steering check box,
then BIOS programs dictate IRQ steering.
IRQ steering is determined by one of four routing tables. Windows searches
for one of the selected routing tables in the order listed and uses the
first one it finds.
- Do not change the default settings for IRQ steering unless there is a
problem with a PCI device.
- If there is a problem, click to clear the Get IRQ table using ACPI
BIOS check box and restart Windows.
- If the problem persists, select the Get IRQ table from Protected Mode
PCI BIOS 2.1 call check box and restart Windows.
- Select the Get IRQ table from Protected Mode PCI BIOS 2.1 call check
box only if a PCI device is not working properly.
a.) Get IRQ table using ACPI BIOS - Specifies that this is the first IRQ
routing table that Windows tries to use to program IRQ steering. If there is
a problem with a PCI device, click to clear the Get IRQ table using ACPI
BIOS check box and restart Windows.
b.) Get IRQ table using MS Specification Table - Specifies that this is
the second IRQ routing table that Windows tries to use to program IRQ
steering.
c.) Get IRQ table from Protected Mode PCI BIOS 2.1 call - Specifies that
this is the third IRQ routing table that Windows tries to use to program IRQ
steering. Select the Get IRQ table from Protected Mode PCI BIOS 2.1 call
check box only if a PCI device is not working properly.
d.) Get IRQ table from Real Mode PCI BIOS 2.1 call - Specifies that this
is the fourth IRQ routing table that Windows tries to use to program IRQ
steering.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hope this helped,
Attila Szabo
Microsoft-MVP (DTS)
Bell Atlantic-Services Technician
a.k.a.' MrScary '
x-no-archive: yes
Mike <fro...@askd.faq>
Bill Drake
you've wiped-out the changes to MACHINE.INF and MSHDC.INF necessary
to find the VIA PCI BUS controller chip -- and this is what is causing your
grief.
Go back and reinstall all the VIA patches, starting with the INF updater
*first*. (It's necessary to get the PCI BUS and the VIA Power Management
controller working properly as the first items, before you install the
rest.)
Once you've done this, make backups of the appropriate INF files modified
by the VIA INF updater and the rest of the VIA updates. Then, if you need
to reinstall W98 for any reason, you can copy back the INFs that W98
overwrites, remove the yellow! items, reboot and redetect, and all will be
well.
Hope this helps.
Best I can do for now. <tm>
Bill
Mike <fro...@askd.faq> wrote >
> MrScary > wrote
Jason Grove
via patches with no luck. I have yet to try reinstalling windows without
loading the via drivers, which I may do later...
Jason Grove
Bill Drake <bdr...@direct.ca> wrote in message
news:OwVicsay#GA.266@cppssbbsa03...
Mike
Bill Drake wrote
: Hi, Mike. If you've reinstalled W98 since you installed the VIA patches,
: you've wiped-out the changes to MACHINE.INF and MSHDC.INF necessary
: to find the VIA PCI BUS controller chip -- and this is what is causing
~~~~
Thanks Bill, I imagine you're right.
But now the darn win98 is stubborn & the VIA setup>install "VIA Chipset
Functions' Registry" won't install ?? ....
Run Setup from a floppy .. InstallShield starts, VIA presents itself -
Click the go button and in a blink it thinks you should reboot to finalize -
but in actuality nothing was done ...Zero.
Tired.. been up all night with this .....
these things, you can't hold them in your hands, things that you,
that you just can't see nor feel. ... virtual unreality.!
Mike
Walter Clayton
instead of deleting the system root from inside devman.
So, your best bet now is to go the VIA Taiwan site at
http://www.via.com.tw/
and download the latest drivers (for some reason the US site tends to be
behind).
The only drivers you _might_ need are the IRQ miniport and AGP drivers. I
say might because I don't use them and have no problems at all.
Next, after you those drivers handy go into the BIOS and enable USB (this is
very important) then reinstall 98. Do _not_ immediately install the VIA
drivers. You may not need them. Go into devman and see if things have
improved. If not then install the IRQ and AGP drivers. Do not install any
other VIA drivers. 98 does not need them.
The installation instructions are identical to what you will find at
http://www.via.com.tw/support/faq.htm
and more specifically
http://www.via.com.tw/support/faq.htm#win98
with the exception of conditionally installing the IRQ miniport and AGP
drivers.
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Mike wrote in message ...
>
Walter Clayton
steering unless this is set, regardless of whether your using USB or not.
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Jason Grove wrote in message ...
Mike
reinstalls with slight changes beforehand... from inside dos & windows,,,
with & without different bios & settings.. each time I'll still have the
dreaded Exclamation
have deleted entire device manager except for bare essentials I hate to
lose...
modem, adapter, com, video..etc. have moved stuff in and out of pci slots.
subtracted secondary slave,,, secondary master,,,
I'm wondering if I'm not Doomed...
w98....it works great !
no sound ...no video interupts but dont know why it needs one cause it
working...matrox milli2 pci ) performance feels good... looks good to
NortonSI... i could go forever maybe without sound but something else will
glitch eventually - acpi is neat .
too many progies go away if a reformat,,,or...
still could be the bios/moboard/whatever too.
right now DevMgr looks UpsideDown & is missing some...
made a hdwe configuration copy... win stops at boot and asks which config
profile.. I tell it neither.. hoping to confuse w98 for the next reinstall
to be different. have tried deleting glitches noted in Detlog.txt from
within the registry hoping to get lucky... some of the reg folders are
multiplying with the reinstalls...
been looking for Trialware/freeware/whatever SoftWare reg fixer supreeme
bought Que book on registry,,, its Ok $20 handbook.
Gives me something to tinker with ... and curse at too. (not unlike a
spouse;)
now i'm talking too much
Mike
guess they see confusing Pci busses in plural or win98 just wont let them.
Thought,,,,
DevMgr
PCi bus
Properties
Drivers button ... what do you have in there ?
Walter Clayton
away from regedit for the moment.
Let's look at exactly where you are now.
You can eliminate the hardware profile prompt by going into the system
applet and selecting the hardware profile tab. Delete everything except
'Original' and reboot.
Once you've done that proceed with the following:
For now ignore detlog.txt. Concentrate only on what you see in device
manager.
You said that currently you have no sound. Is that what is currently banged
out in deivce manager or does it even appear? Exactly what else is banged
out?
Do you have any 'other/unknown' devices listed? What other devices do you
have that currently do not show up?
Also, launch sysinfo and display your current IRQ assignments. Copy and
paste them here.
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Mike wrote in message ...
Jason Grove
it has soemthing to do with the fact that IRQ routing driver is from
04/23/99 and Windows98 SE is newer. I just did a clean install, without any
extra VIA drivers (AGP or IRQ) and have exactly the same settings as before
and the same problems. Has anyone had any contact with VIA about this? I
noticed that none of the FAQs talk about ACPI or Win98SE. IRQ steering is
functioning the same as if the drivers were installed.
Jason
Mike <fro...@askd.faq> wrote in message
news:cqqh3.303$Z31....@dfiatx1-snr1.gtei.net...
Van Souders
Jason Grove
machine2.inf files in the windows\inf folder it appears that from the
registry key that the device is in that the driver is loading or detected as
an EISA bus and an ISA bus. I believe that neither my Soyo 5EHM motherboard
or my FIC VA-503+ motherboard have an EISA bus. They both have VIA
chipsets....
Any suggestions on what to change the driver to? Is it possible to modify
the inf file (machine2.inf) to remove the EISA bus from the file?
BTW it is conflicting:
Input/Output Range 0374 - 0377 used by:
Secondary IDE controller (dual fifo)
Input/Output Range 0374 - 0377 used by:
VIA Bus Master PCI IDE Controller
Which no matter what I manually change the settings, it reverts back to
the automatic settings on both machines, one is running Windows98 (APM) the
other is Windows98 SE (ACPI).
Thanks,
Jason
Van Souders <vsou...@jps.net> wrote in message
news:37884eb7...@news.supernews.com...
Jason Grove
http://support.microsoft.com/support/kb/articles/q125/1/74.asp about the
error message, however there appears to be no solution to this, and for me
it happens on Windows 98 without ACPI and with Windows98 ACPI.
Jason
Mike <fro...@askd.faq> wrote in message
news:yr5h3.216$Zm2....@dfiatx1-snr1.gtei.net...
Mike
Walter C<> wrote
: Also, launch sysinfo and display your current IRQ assignments. Copy and
: paste them here.
:
Microsoft System Information;
IRQ
0 System timer
1 Standard 101/102-Key or Microsoft Natural Keyboard
2 Programmable interrupt controller
3 Communications Port (COM2)
4 Internal 56K Voice Video Faxmodem
5 Printer Port (LPT1)
6 Standard Floppy Disk Controller
7 ACPI IRQ Holder for PCI IRQ Steering
8 System CMOS/real time clock
9 SCI IRQ used by ACPI bus
10 ACPI IRQ Holder for PCI IRQ Steering
11 %String1%
12 PS/2 Compatible Mouse Port
13 Numeric data processor
14 Standard IDE/ESDI Hard Disk Controller
15 Standard IDE/ESDI Hard Disk Controller
DMA
0 (free)
1 (free)
2 Standard Floppy Disk Controller
3 (free)
4 Direct memory access controller
5 (free)
6 (free)
7 %String1%
stuck some picts of dev mgr at
http://online.pair.com/dev.mgr/
still don't have sound -- beginning to miss it too.
- came on once, then disappeared sometime
after I removed duplicates from a fresh reinstall
- dma controller, - and a - motherboard resources
hdwe search shows up
red Xout SystemTimer - (I didn't do it)
and the PCi bus with yellow-exclamation
taking a break from tinkering
... next I'll attack sound again & udma HDD controllers
but up & running seemingly well.
Bill Drake
website is insufficient.
The IRQ miniport and AGP drivers *depend* upon a fully-functional
PCI-PnP interface to the BIOS. Without that, all secondary items are
irrelevant.
Until Mike reforms the linkage between W98 and the PnP-manager in the
BIOS (which is one of the things the PCI driver is involved with), none
of the other stuff which depends upon this primary-interface is going to
work.
IOW, Mike's problem is closer to the base of the pyramid. Fiddling with
the upper-stages is not going to solve the problem until the foundation
upon which the upper stages depends is fixed.
Best I can do for now. <tm>
Bill
Walter Clayton <w-cla...@SPmailandnewsAM.com> wrote
> You took a slightly wrong turn by clipping the enum root in the registry
> instead of deleting the system root from inside devman.
> So, your best bet now is to go the VIA Taiwan site at
> http://www.via.com.tw/
> and download the latest drivers (for some reason the US site tends to be
> behind).
> The only drivers you _might_ need are the IRQ miniport and AGP drivers. I
> say might because I don't use them and have no problems at all.
> Next, after you those drivers handy go into the BIOS and enable USB (this
is
> very important) then reinstall 98. Do _not_ immediately install the VIA
> drivers. You may not need them. Go into devman and see if things have
> improved. If not then install the IRQ and AGP drivers. Do not install any
> other VIA drivers. 98 does not need them.
> The installation instructions are identical to what you will find at
> http://www.via.com.tw/support/faq.htm
> and more specifically
> http://www.via.com.tw/support/faq.htm#win98
> with the exception of conditionally installing the IRQ miniport and AGP
> drivers.
>
> --
> Walter Clayton
> Zone id: Dr_Doom_Ky
> Any technology distinguishable from magic is insufficiently advanced.
>
> Mike wrote in message ...
> >
Bill Drake
and thinks it's already installed -- whereas the INF updates are not correct
and as a result the PCI bus support can't be installed.
Things to check:
1. Can you get someone who has a motherboard with the same chipset
to send you copies of their MACHINE.INF and MSHDC.INF files?
You can then check those files against the ones you have installed
and see if there are differences or not.
2. It is possible you have Registry corruption which is preventing the PCI
bus enumeration data from being properly incorporated into the Registry.
Try running the W98 Registry checker with the "fix" option
(Scanreg /fix from MSDOS mode) to see if this will repair the corruption
and allow your enumeration process to proceed successfully.
3. Are you running the latest flashBIOS available for your motherboard?
If you have updated your flashBIOS, did you properly reset the CMOS
data and then re-enter that data after resetting the CMOS values to
their defaults?
Note: The above is a *must do* procedure when you update your
flashBIOS. CMOS data is specific to a *particular* BIOS
version. Leaving old data in the CMOS registers when using
a newer BIOS version may cause a *completely different*
set of hardware configurations to be installed in the chipset,
leading to all sorts of various weirdness.
After performing a flashBIOS update, it is mandatory to clear
your CMOS data (Load Setup Defaults) and save the CMOS
in that form. (This overwrites all the CMOS data with new
values which are correct for the new BIOS version.)
Once you have a valid set of default data, you can then
customize the CMOS values to your heart's content and save
the changes as desired. However, please remember that you
will have to do this again *each time* you update the
flashBIOS. There's no getting around this -- ya gotta do yer
homework... <g>
4. In the worst-case scenario, (if nothing else works) the only solution I
can offer is a full-pull reinstall-from-scratch. This is the only way
to ensure that whatever Registry corruption is causing your problem
with your current install is removed from affecting your system.
Note: A reinstall of W9x over top of an existing installation does
*not* replace all Registry values. Many values are left as
found, since the reinstall procedure assumes that changes were
made for good reason.
In most cases, this assumption is correct. However, in the
case of certain kinds of Registry corruption, stuff gets left
alone that should be overwritten. Consequently, if a reinstall
doesn't solve the problem, a full-pull reinstall-from-scratch
may be the only way to create a functional Registry again.
Hope this helps.
Best I can do for now. <tm>
Bill
Mike <fro...@askd.faq> wrote
>
> Bill Drake wrote
> : Hi, Mike. If you've reinstalled W98 since you installed the VIA
patches,
> : you've wiped-out the changes to MACHINE.INF and MSHDC.INF
> : necessary to find the VIA PCI BUS controller chip -- and this is what is
Walter Clayton
looking for the specs on a Via based board. They don't have any. What they
do have are Eteq and SiS based SS7 boards. This one is an Eteq. Using the
IRQ miniport drivers directly from VIA (if that's where they came from)
instead of Soyo/ETEQ may be a big part of the problem.
Also looks like some more miscommunication is happening as well. He said his
system timer and PCI bus was banged out when the image he posted showed com1
and the PCI bus. Com1 being banged is ok as long as it's not being used.
Also his sound card inf or registry entry looks seriously hosed.
I'm to the point now that it is time to blow it all away and start over, and
use the Soyo setup instructions rather than the VIA instructions ,
especially in light of all the registry tinkering he indicates he's done.
And on this pass, stay far, far away from the Via supplied drivers. Just
stick with what's available on the Soyo site. Even if the base chipset is an
MVP3 chipset, there are no telling what kind of modifications Soyo or Eteq
made beyond relabeling the chips.
--
Walter Clayton
AKA DrDoom
Any technology distinguishable from magic is insufficiently advanced.
Bill Drake <bdr...@direct.ca> wrote in message
news:#Zwpo71y#GA.232@cppssbbsa04...
> Hi, Walter. In Mike's situation, the methodology suggested on the VIA
> website is insufficient.
>
> The IRQ miniport and AGP drivers *depend* upon a fully-functional
> PCI-PnP interface to the BIOS. Without that, all secondary items are
> irrelevant.
>
> Until Mike reforms the linkage between W98 and the PnP-manager in the
> BIOS (which is one of the things the PCI driver is involved with), none
> of the other stuff which depends upon this primary-interface is going to
> work.
>
> IOW, Mike's problem is closer to the base of the pyramid. Fiddling with
> the upper-stages is not going to solve the problem until the foundation
> upon which the upper stages depends is fixed.
>
>
> Best I can do for now. <tm>
>
>
> Bill
>
>
>
> > >Bill Drake wrote
> > >: Hi, Mike. If you've reinstalled W98 since you installed the VIA
> patches,
> > >: you've wiped-out the changes to MACHINE.INF and MSHDC.INF necessary
> > >: to find the VIA PCI BUS controller chip -- and this is what is
causing
Walter Clayton
--
Walter Clayton
AKA DrDoom
Any technology distinguishable from magic is insufficiently advanced.
Mike <fro...@askd.faq> wrote in message
news:5XQh3.1345$U47....@dfiatx1-snr1.gtei.net...
Poly Bius
Walter
: Have you been loading the Via drivers from the Via website on this board?
~~
Via drivers - I normally grab from www.via.com.tw/drivers/
havent tried loading any via drivers lately as last time they were tried,
they would Not load.
Followed that attempt with the eteq 4/1 package from Soyo.com.tw - same Non
loading(diff date drivers?)
Mike
Bill Drake wrote ...
: Hi, Walter. In Mike's situation, the methodology suggested on the VIA
: website is insufficient.
:
: The IRQ miniport and AGP drivers *depend* upon a fully-functional
: PCI-PnP interface to the BIOS. Without that, all secondary items are
: irrelevant.
don't have/use AGP card ... havent tried installing via AGP patch
as via instructs to install AGP card before installing the via agp vxd.
via miniport - havent tried it lately, instructed to PCi bridge Patch
1st
which won't load
+-+-+-+
: Until Mike reforms the linkage between W98 and the PnP-manager in the
: BIOS (which is one of the things the PCI driver is involved with), none
: of the other stuff which depends upon this primary-interface is going to
: work.
+++
BIOS & DevMgr appear in communications, as i can change checkbox in win98
PCi bus Properties & bios will change and a bios change reflects
visa-versa
provided the bios is enabled in PCi Properties.
~ so bios should be enabled in win and auto in bios ? ... (been trying
combo's galore)
bios has switch, pci/isa irq autoreset = enabled/disabled which will
change things,
one shot update to cmos I think - when adjustments made !
+-+-+-+
: IOW, Mike's problem is closer to the base of the pyramid. Fiddling with
: the upper-stages is not going to solve the problem until the foundation
: upon which the upper stages depends is fixed.
bios works,
dos levels works,
actually windows is performing extreemly well,
ACPI works well - Does exactly what it's supposed to
- one error (msg) so far...
'Rain' cpu cooler 'Halt instruction program &
acpi conflicted not allowing win to enter suspend
just need interrupts from within
windows to use graphic & sound card correctly
...or any pci card... plus it appears to effect;
Hdd controllers as it doesnt like anything
except the standard windows esdi-506.pdr std drivers
Mike
Mike
Bill Drake wrote ...
: Hi, Mike. OK, what it sounds like is the update is checking the Registry
: and thinks it's already installed -- whereas the INF updates are not
correct
: and as a result the PCI bus support can't be installed.
:
: Things to check:
:
: to send you copies of their MACHINE.INF and MSHDC.INF files?
: You can then check those files against the ones you have installed
: and see if there are differences or not.
wish someone with 5eh/m- orgWin98 & ACPi could email or upload those,
would like to compare - grab my email at http://online.pair.com/dev.mgr/
and send note first - (hate to get 100, 50kb copies when one will do)
++++
:
: 2. It is possible you have Registry corruption which is preventing the PCI
: bus enumeration data from being properly incorporated into the
Registry.
:
: Try running the W98 Registry checker with the "fix" option
: (Scanreg /fix from MSDOS mode) to see if this will repair the
corruption
: and allow your enumeration process to proceed successfully.
+++
i'll try that, but have previously /fix.
/Fix just grabs last working scanreg set?
- thinking rename the backup scandisks
saved regs, so it cant use them and actually
tries to `Fix
had sound once after a reinstall
deleted duplicates in dev mgr that
did not show yellow, per Microsoft,
and sound went away - one was
duplicated DMA controller..
other was a motherboard resource (I think)
++++
:
: 3. Are you running the latest flashBIOS available for your motherboard?
:
: If you have updated your flashBIOS, did you properly reset the CMOS
: data and then re-enter that data after resetting the CMOS values to
: their default
+++
always shorted pins & yes Reset to SetupDefault is my norm route
bios is march 99 lastest non-beta version
++++
Mike
http://online.pair.com/dev.mgr/diff-hmm.gif
8kb
this is old/new (smart) file compare machine.inf
some references to PCi notes, I'll scratch around
maybe help
- although parrity, was enabled in bios mysteriously ,
so I turned it off cause do't have ParMem chips
- maybe some bios ideas there... fiddler at heart
Mike
Mike
did it online,
replaced PCI bus driver, pointed it at w98CD & MS file base.
Said I already had best driver... but others were available.. took the
others.
Loaded all the Via default BM drivers ..and pci bridge...etc
tons of them, at least it seemed like tons... took a bit w/56k modem
after all the reeboots and more driver & files.. it works, almost.
just got sound working and some other glitches.
Now a new Question
Soyo 5EHM ... ETEQ or VIA (m)VP3 .... (no AGP card here)
guess it needs upgraded drivers .. rather than default w98 stuff.
Via has three sets of downloads for me;
http://www.via.com.tw/drivers/index.htm
IRQ Routing Driver
Updated 04/16/99
For all VIA chipsets using VT82C586A or VT82C586B
southbridge chips
VIA IRQ Routing Driver ver. 1.3a
(Win95/98)
USB Filter Driver
Updated 07/06/99
This driver adds support for more USB devices to the
VT82C586B and VT82C596
USB Filter Driver ver. 1.06
----this one is needed I think ???
PCI Bridge Patch
Updated 07/06/99
This patch allows Win98/98SE/95 to recognize the VIA
chipset in the system device manager
VIA PCI bridge patch ver. 1.6
I hate to ... not knowing what the outcome might bring. What ya think ??
Mike
System Information reports though it's not yellow exclamtion'd;
Problem Devices;
ISA Plug and Play bus
System
This Device Has a Problem: Code=2 (0x2)
Device failure: Try changing the driver for this device.
If that doesn't work,see your hardware documentation.
Registry Key: HKEY_LOCAL_MACHINE\enum\ACPI\*PNP0A00\0
Alloc resources: None
Forced resources: None
Boot resources: None
Filtered resources: None
Basic resources: None
Driver: System\0102
Driver Date: 7-28-1998
Driver: pcimp.pci
File Size: 15744 (0x3D80)
File Date: 5/11/1998 8:1 AM
Company Name: Microsoft Corporation
File Version: 4.10.1998
Driver: pci.vxd
File Size: 65895 (0x10167)
File Date: 5/11/1998 8:1 AM
Company Name: Microsoft Corporation
File Version: 4.10.1998
Walter Clayton
works, you may be able to do a relatively clean install without having to
reload your apps.
I'm suspicious about using the VIA website drivers on an ETEQ chipset
though. I have yet to find out what the relationship is between those two
companies and I'm thinking that part of your problem is running VIA
reference drivers on an ETEQ chipset instead of the ETEQ drivers.
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Poly Bius wrote in message ...
Jason Grove
That is really extreme considering I have the same problems on 2
motherboards, one with the ETEQ drivers loaded only, and one with the VIA
drivers. There are problems in 98 and se in both, although neither give an
yellow exclamtion mark for soem reason, they are listed as problem
devices.... The ETEQ are really via drivers, for some reason they put a
sticker over the chip.....
Jason Grove
Walter Clayton
afterwards, although testing it I did not have any problems.
To do this you need to be able to install from a boot diskette. One of the
options you need to use on setup will not work in a GUI.
First, boot with an EBD with CD-Rom support (or copy the CD to disk).
Change directory to C:\windows\inf
Del *.* (don't worry about read only files that don't get deleted)
CD other (sub directory)
Del *.*
[d]:\setup /nd /d /pf ---- (where [d] is your CD-Rom (or location of the 98
setup program). If you want acpi support, change the last switch to /pf;j -
that's /pf[semicolon]j)
Setup should ask about saving setup files. Select no. They're garbage right
now any way.
Once this is done, install the ETEQ IRQ miniport only. Do not install any of
the other ETEQ drivers. And do _not_ install any of the VIA website based
drivers. I still think they are what caused and are causing your current
problems.
See it this clears your problem up.
Notes:
With the exception of what is noted, your existing installed apps should
make it through this basically intact.
Using the /nd switch in setup and deleting everything in the inf folder may
cause problems with some of your installed apps. You won't know until you
try to run them, but that's the least of your problems at present. You
should be able to just reinstall those apps without have to worry about the
data. This causes setup to overwrite newer files.
The /d parameter is going to skip processing existing windows configuration
(e.g. whatever you may have in win.ini and system.ini)
The /pf switch will cause setup to clean out the enum root of the registry.
This can only be used from a DOS prompt.
--
Walter Clayton
AKA DrDoom
Any technology distinguishable from magic is insufficiently advanced.
Walter Clayton <w-cla...@SPmailandnewsAM.com> wrote in message
news:e#jE7HIz#GA.63@cppssbbsa05...
Walter Clayton
format and clean install. This route should preserve the installed
application base. The intent is remove all references to anything but 98
infs and drivers and thus allow installation of nothing but the ETEQ drivers
only.
Are you certain that all ETEQ did was relabel the chipset? Like I said, I
have yet to find out what the relationship between ETEQ and VIA is. If ETEQ
is licensing the chipset from VIA do you know for a fact that ETEQ makes no
changes to the chipset? (And not I'm not trying to be difficult (yeah that's
the polite word 8) ) I am genuinely curious, because if ETEQ made any
changes in the chipset then the VIA sourced drivers could cause problems).
I'm basing my judgement on staying away from the VIA drivers in this
instance based on some sound card chipset experience (when is a Vortex
chipset not a Vortex chipset even though the OEM calls it Vortex? When it's
installed on a Diamond, Turtle Beach, Xitel, TerraTec or VideoLogic card.)
--
Walter Clayton
Zone id: Dr_Doom_Ky
Any technology distinguishable from magic is insufficiently advanced.
Jason Grove wrote in message ...