ISA Plug and Play not working (clean install)

R

rpgs rock dvds

Are there are any noteworthy BIOS or Windows 98 settings I need to be
aware of to get Win98 successfully installed on a QDI Advance 9 or 10
mobo? (VIA chipset). The reason I ask is that I am having a problem
with Win98's ISA Plug and Play mechanism. Win98 is unable to detect
any PnP ISA cards. Please note this occurs with the CMOS settings
cleared and a clean Win98 install, plus I'm just using a basic VGA
graphics card only, or occasionally this graphics card with a
Soundblaster AWE64 (PnP ISA).

For either hardware configuration mentioned above, inside Device
Manager there appears to be some kind of resource problem with this
System resource:

"IO read data port for ISA Plug and Play enumerator"

Looking at the configuration details, there's a conflict with both the
Secondary IDE Controller (dual fifo) and also with VIA Bus Master PCI
IDE Controller. I've tried changing the above-mentioned "ISA PnP
enumerator's" resources to fix the conflict, but my changes don't
appear to make an effect. Also, I don't seem to be able to adjust
either of the two conflicting Controller's IRQ values, although I'm
not too sure if that would help.

I went to the chipset maker (VIA) website and downloaded a "4-in-1"
chipset driver package and installed it, but unfortunately it didn't
fix the problem. The BIOS appears to be on its latest revision. I
also scoured the net's newsgroups and couldn't find any help that I
haven't already tried.

Thanks a lot if anyone can help, best regards, Robert.
 
P

philo

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:939a36bf-d3bb-450c-9662-6a3ec8abf7a0@8g2000hse.googlegroups.com...
> Are there are any noteworthy BIOS or Windows 98 settings I need to be
> aware of to get Win98 successfully installed on a QDI Advance 9 or 10
> mobo? (VIA chipset). The reason I ask is that I am having a problem
> with Win98's ISA Plug and Play mechanism. Win98 is unable to detect
> any PnP ISA cards. Please note this occurs with the CMOS settings
> cleared and a clean Win98 install, plus I'm just using a basic VGA
> graphics card only, or occasionally this graphics card with a
> Soundblaster AWE64 (PnP ISA).
>
> For either hardware configuration mentioned above, inside Device
> Manager there appears to be some kind of resource problem with this
> System resource:
>
> "IO read data port for ISA Plug and Play enumerator"
>
> Looking at the configuration details, there's a conflict with both the
> Secondary IDE Controller (dual fifo) and also with VIA Bus Master PCI
> IDE Controller. I've tried changing the above-mentioned "ISA PnP
> enumerator's" resources to fix the conflict, but my changes don't
> appear to make an effect. Also, I don't seem to be able to adjust
> either of the two conflicting Controller's IRQ values, although I'm
> not too sure if that would help.
>
> I went to the chipset maker (VIA) website and downloaded a "4-in-1"
> chipset driver package and installed it, but unfortunately it didn't
> fix the problem. The BIOS appears to be on its latest revision. I
> also scoured the net's newsgroups and couldn't find any help that I
> haven't already tried.
>
> Thanks a lot if anyone can help, best regards, Robert.


ISA cards typically have jumpers to set the IRQ's...
and if so, the jumpers need to be set manually to avoid conflicts, which
cannot be resolved
from either a bios setting or from within the OS.

My advice would be to remove all ISA cards but one...and once that is
configured...
add the second one...but be sure to manually configure it so as not to
conflict
with the one already setup.

It will definitely take some patience and an amount of trial and error.

Also note that at least *some* ISA cards have two distinct jumper
configurations...
that being manual or plug & play...so if you do have an ISA card with a plug
& play jumper setting...using that
might assuage your conflict problems
 
R

rpgs rock dvds

On 19 Apr, 16:15, "philo" <ph...@privacy.net> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:939a36bf-d3bb-450c-9662-6a3ec8abf7a0@8g2000hse.googlegroups.com...
>
>
>
>
>
> > Are there are any noteworthy BIOS or Windows 98 settings I need to be
> > aware of to get Win98 successfully installed on a QDI Advance 9 or 10
> > mobo?  (VIA chipset).  The reason I ask is that I am having a problem
> > with Win98's ISA Plug and Play mechanism.  Win98 is unable to detect
> > any PnP ISA cards.  Please note this occurs with the CMOS settings
> > cleared and a clean Win98 install, plus I'm just using a basic VGA
> > graphics card only, or occasionally this graphics card with a
> > Soundblaster AWE64 (PnP ISA).
>
> > For either hardware configuration mentioned above, inside Device
> > Manager there appears to be some kind of resource problem with this
> > System resource:
>
> > "IO read data port for ISA Plug and Play enumerator"
>
> > Looking at the configuration details, there's a conflict with both the
> > Secondary IDE Controller (dual fifo) and also with VIA Bus Master PCI
> > IDE Controller.  I've tried changing the above-mentioned "ISA PnP
> > enumerator's" resources to fix the conflict, but my changes don't
> > appear to make an effect.  Also, I don't seem to be able to adjust
> > either of the two conflicting Controller's IRQ values, although I'm
> > not too sure if that would help.
>
> > I went to the chipset maker (VIA) website and downloaded a "4-in-1"
> > chipset driver package and installed it, but unfortunately it didn't
> > fix the problem.  The BIOS appears to be on its latest revision.  I
> > also scoured the net's newsgroups and couldn't find any help that I
> > haven't already tried.
>
> > Thanks a lot if anyone can help, best regards, Robert.
>
> ISA cards typically have jumpers to set the IRQ's...
> and if so, the jumpers need to be set manually to avoid conflicts, which
> cannot be resolved
> from either a bios setting or from within the OS.
>
> My advice would be to remove all ISA cards but one...and once that is
> configured...
> add the second one...but be sure to manually configure it so as not to
> conflict
> with the one already setup.
>
> It will definitely take some patience and an amount of trial and error.
>
> Also note that at least *some* ISA cards have two distinct jumper
> configurations...
> that being manual or plug & play...so if you do have an ISA card with a plug
> & play jumper setting...using that
> might assuage your conflict problems- Hide quoted text -
>
> - Show quoted text -

Hi. Actually this resource conflict issue occurs whether I either use
my PnP ISA card (a Soundblaster AWE64) or no ISA cards at all. (The
AWE64 card is ISA PnP - it appears not to have any configurable
jumpers.)

I am wondering if this problem can be solved by disabling both onboard
IDE ports in the BIOS, and then using a PCI IDE card for my HDD and
DVD drive. My theory is that this will dispense with the need to use
the onboard VIA Bus Master PCI IDE Controller and the Secondary IDE
Controller, because I think that this may be the source of the
resource conflict problem. However, I also wonder if the onboard PCI
to ISA bridge mechanism is not functioning as it should.

Any further thoughts gratefully received, thanks, regards, Robert.
 
M

MEB

http://www.qdigrp.com/qdisite/eng/products/Advance9.htm
http://www.motherboard.cz/mb/qdi/Advance 9.htm - BIOS/chipset - !
scripting caution

Unless absolutely necessary, leave the VIA enabled. The conflict is likely
not there.

Remove all add-in cards. Restart Normal and uninstall any related software.
RESTART in Safe Mode and check for any ghost entries. Remove any found or !
devices. Make sure to check for the Blaster and remove everything related.
Shut down.

RESTART. Make sure the BIOS/CMOS is set for PnP OS installed, then make sure
that you are NOT using manually set entries except for USB, video, keyboard,
printer, or other necessary potentials in the BIOS/CMOS. Turn OFF Trend
anti-virus in the BIOS, Start and install the motherboard drivers. Either
use the VIA 4in1 OR the supplied QDI.

RESTART in Normal Mode. Carefully review the system without add-in cards for
any conflicts, prior to the suggested single card at a time installation and
check. CHOOSE which BUS mastering driver you wish to use [you can only use
one, either the VIA driver, or the offered QDI/third party]

Check the System and devices via Device Manager, if no errors, back up the
registry. Run Find New Hardware and let it review the devices/system. If any
found or otherwise, let them be changed. Restart [cold reboot]. Again run
Find New Hardware, let anything be changed, note whether it found anything.
Recheck the system via Device Manager. Save/backup the registry. Recheck
via Safe Mode for ghosted entries.

NOW add in the other cards, one at a time, but NOT the SoundBlaster AWE64.
After each installation, install any software required, restart if
necessary, and run through the Find New Hardware, using cold reboots after
each installation. If no conflicts, again save the registry.

Download the AWE64 driver from a legitimate site [reports of corrupted
manually modified drivers have been found]. Install that driver. There
should be no conflicts. If there are conflicts, post back and we can work
through the issues now knowing the system is properly configured.

--
MEB http://peoplescounsel.orgfree.com
--
_________

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:fb4795ac-8c4d-405a-80bb-e3fc59144fae@y21g2000hsf.googlegroups.com...
On 19 Apr, 16:15, "philo" <ph...@privacy.net> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in
messagenews:939a36bf-d3bb-450c-9662-6a3ec8abf7a0@8g2000hse.googlegroups.com.
...
>
>
>
>
>
> > Are there are any noteworthy BIOS or Windows 98 settings I need to be
> > aware of to get Win98 successfully installed on a QDI Advance 9 or 10
> > mobo? (VIA chipset). The reason I ask is that I am having a problem
> > with Win98's ISA Plug and Play mechanism. Win98 is unable to detect
> > any PnP ISA cards. Please note this occurs with the CMOS settings
> > cleared and a clean Win98 install, plus I'm just using a basic VGA
> > graphics card only, or occasionally this graphics card with a
> > Soundblaster AWE64 (PnP ISA).
>
> > For either hardware configuration mentioned above, inside Device
> > Manager there appears to be some kind of resource problem with this
> > System resource:
>
> > "IO read data port for ISA Plug and Play enumerator"
>
> > Looking at the configuration details, there's a conflict with both the
> > Secondary IDE Controller (dual fifo) and also with VIA Bus Master PCI
> > IDE Controller. I've tried changing the above-mentioned "ISA PnP
> > enumerator's" resources to fix the conflict, but my changes don't
> > appear to make an effect. Also, I don't seem to be able to adjust
> > either of the two conflicting Controller's IRQ values, although I'm
> > not too sure if that would help.
>
> > I went to the chipset maker (VIA) website and downloaded a "4-in-1"
> > chipset driver package and installed it, but unfortunately it didn't
> > fix the problem. The BIOS appears to be on its latest revision. I
> > also scoured the net's newsgroups and couldn't find any help that I
> > haven't already tried.
>
> > Thanks a lot if anyone can help, best regards, Robert.
>
> ISA cards typically have jumpers to set the IRQ's...
> and if so, the jumpers need to be set manually to avoid conflicts, which
> cannot be resolved
> from either a bios setting or from within the OS.
>
> My advice would be to remove all ISA cards but one...and once that is
> configured...
> add the second one...but be sure to manually configure it so as not to
> conflict
> with the one already setup.
>
> It will definitely take some patience and an amount of trial and error.
>
> Also note that at least *some* ISA cards have two distinct jumper
> configurations...
> that being manual or plug & play...so if you do have an ISA card with a
plug
> & play jumper setting...using that
> might assuage your conflict problems- Hide quoted text -
>
> - Show quoted text -

Hi. Actually this resource conflict issue occurs whether I either use
my PnP ISA card (a Soundblaster AWE64) or no ISA cards at all. (The
AWE64 card is ISA PnP - it appears not to have any configurable
jumpers.)

I am wondering if this problem can be solved by disabling both onboard
IDE ports in the BIOS, and then using a PCI IDE card for my HDD and
DVD drive. My theory is that this will dispense with the need to use
the onboard VIA Bus Master PCI IDE Controller and the Secondary IDE
Controller, because I think that this may be the source of the
resource conflict problem. However, I also wonder if the onboard PCI
to ISA bridge mechanism is not functioning as it should.

Any further thoughts gratefully received, thanks, regards, Robert.
 
R

rpgs rock dvds

On 19 Apr, 17:59, "MEB" <meb@not h...@hotmail.com> wrote:
> http://www.qdigrp.com/qdisite/eng/p...tp://www.motherboard.cz/mb/qdi/Advance 9.htm- BIOS/chipset - !
> scripting caution
>
>  Unless absolutely necessary, leave the VIA enabled. The conflict is likely
> not there.
>
>  Remove all add-in cards. Restart Normal and uninstall any related software.
> RESTART in Safe  Mode and check for any ghost entries. Remove any found or !
> devices. Make sure to check for the Blaster and remove everything related.
> Shut down.
>
> RESTART. Make sure the BIOS/CMOS is set for PnP OS installed, then make sure
> that you are NOT using manually set entries except for USB, video, keyboard,
> printer, or other necessary potentials in the BIOS/CMOS. Turn OFF Trend
> anti-virus in the BIOS, Start and install the motherboard drivers. Either
> use the VIA 4in1 OR the supplied QDI.
>
> RESTART in Normal Mode. Carefully review the system without add-in cards for
> any conflicts, prior to the suggested single card at a time installation and
> check. CHOOSE which BUS mastering driver you wish to use [you can only use
> one, either the VIA driver, or the offered QDI/third party]
>
>  Check the System and devices via Device Manager, if no errors, back up the
> registry. Run Find New Hardware and let it review the devices/system. If any
> found or otherwise, let them be changed. Restart [cold reboot]. Again run
> Find New Hardware, let anything be changed, note whether it found anything..
>  Recheck the system via Device Manager. Save/backup the registry. Recheck
> via Safe Mode for ghosted entries.
>
>  NOW add in the other cards, one at a time, but NOT the SoundBlaster AWE64.
> After each installation, install any software required, restart if
> necessary, and run through the Find New Hardware, using cold reboots after
> each installation. If no conflicts, again save the registry.
>
>  Download the AWE64 driver from a legitimate site [reports of corrupted
> manually modified drivers have been found]. Install that driver. There
> should be no conflicts. If there are conflicts,  post back and we can work
> through the issues now knowing the system is properly configured.
>
> --
> MEBhttp://peoplescounsel.orgfree.com

Hi - thanks a lot for your reply. Before I read your reply, I re-
installed Win98 from scratch and I am at this stage:

Set BIOS OS PnP = No (Please note, reading your reply this may be
wrong - I really don't mind doing another fresh install as I have done
about 6 so far, and don't mind too much about this.)

I then clean installed Win98 with just 1 basic PCI graphics card,
nothing else. (Please note, the PnP mechanism worked fine for this
Matrox PCI graphics card.)

Then, I installed VIA 4-in-1 drivers from VIA's website.
(Unfortunately I do not have the QDI CD.)

Now, in safe mode, I examine Device Manager - I see no general errors,
no general conflicts, but I do see "IRQ Holder for PCI Steering"
listed 4 times inside System Devices. (At this moment in time, I have
not removed any of these duplicates, but I will do if you think this
will help.)

Now, I am about to change the BIOS OS PnP to = Yes, because I read
your reply and I want to try this. I will then check Device Manager
(in safe mode) for any problems. Then, I will insert the AWE64 card,
and see what happens.

Please note that at this moment in time, I would be very happy to get
my Win98 PC working with just a basic PCI graphics card and the AWE64
PnP ISA card. I can do as many clean Win98 installs as necessary to
achieve this. If you have any "start-from-scratch" plan of action,
then I'd be very happy to follow it.

Thanks very much, Best regards, Robert.
 
R

rpgs rock dvds

On 19 Apr, 17:59, "MEB" <meb@not h...@hotmail.com> wrote:
> http://www.qdigrp.com/qdisite/eng/p...tp://www.motherboard.cz/mb/qdi/Advance 9.htm- BIOS/chipset - !
> scripting caution
>
>  Unless absolutely necessary, leave the VIA enabled. The conflict is likely
> not there.
>
>  Remove all add-in cards. Restart Normal and uninstall any related software.
> RESTART in Safe  Mode and check for any ghost entries. Remove any found or !
> devices. Make sure to check for the Blaster and remove everything related.
> Shut down.
>
> RESTART. Make sure the BIOS/CMOS is set for PnP OS installed, then make sure
> that you are NOT using manually set entries except for USB, video, keyboard,
> printer, or other necessary potentials in the BIOS/CMOS. Turn OFF Trend
> anti-virus in the BIOS, Start and install the motherboard drivers. Either
> use the VIA 4in1 OR the supplied QDI.
>
> RESTART in Normal Mode. Carefully review the system without add-in cards for
> any conflicts, prior to the suggested single card at a time installation and
> check. CHOOSE which BUS mastering driver you wish to use [you can only use
> one, either the VIA driver, or the offered QDI/third party]
>
>  Check the System and devices via Device Manager, if no errors, back up the
> registry. Run Find New Hardware and let it review the devices/system. If any
> found or otherwise, let them be changed. Restart [cold reboot]. Again run
> Find New Hardware, let anything be changed, note whether it found anything..
>  Recheck the system via Device Manager. Save/backup the registry. Recheck
> via Safe Mode for ghosted entries.
>
>  NOW add in the other cards, one at a time, but NOT the SoundBlaster AWE64.
> After each installation, install any software required, restart if
> necessary, and run through the Find New Hardware, using cold reboots after
> each installation. If no conflicts, again save the registry.
>
>  Download the AWE64 driver from a legitimate site [reports of corrupted
> manually modified drivers have been found]. Install that driver. There
> should be no conflicts. If there are conflicts,  post back and we can work
> through the issues now knowing the system is properly configured.
>
> --
> MEBhttp://peoplescounsel.orgfree.com
> --
> _________
>
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:fb4795ac-8c4d-405a-80bb-e3fc59144fae@y21g2000hsf.googlegroups.com...
> On 19 Apr, 16:15, "philo" <ph...@privacy.net> wrote:> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in
>
> messagenews:939a36bf-d3bb-450c-9662-6a3ec8abf7a0@8g2000hse.googlegroups.com.
> ..
>
>
>
>
>
>
>
> > > Are there are any noteworthy BIOS or Windows 98 settings I need to be
> > > aware of to get Win98 successfully installed on a QDI Advance 9 or 10
> > > mobo? (VIA chipset). The reason I ask is that I am having a problem
> > > with Win98's ISA Plug and Play mechanism. Win98 is unable to detect
> > > any PnP ISA cards. Please note this occurs with the CMOS settings
> > > cleared and a clean Win98 install, plus I'm just using a basic VGA
> > > graphics card only, or occasionally this graphics card with a
> > > Soundblaster AWE64 (PnP ISA).
>
> > > For either hardware configuration mentioned above, inside Device
> > > Manager there appears to be some kind of resource problem with this
> > > System resource:
>
> > > "IO read data port for ISA Plug and Play enumerator"
>
> > > Looking at the configuration details, there's a conflict with both the
> > > Secondary IDE Controller (dual fifo) and also with VIA Bus Master PCI
> > > IDE Controller. I've tried changing the above-mentioned "ISA PnP
> > > enumerator's" resources to fix the conflict, but my changes don't
> > > appear to make an effect. Also, I don't seem to be able to adjust
> > > either of the two conflicting Controller's IRQ values, although I'm
> > > not too sure if that would help.
>
> > > I went to the chipset maker (VIA) website and downloaded a "4-in-1"
> > > chipset driver package and installed it, but unfortunately it didn't
> > > fix the problem. The BIOS appears to be on its latest revision. I
> > > also scoured the net's newsgroups and couldn't find any help that I
> > > haven't already tried.
>
> > > Thanks a lot if anyone can help, best regards, Robert.
>
> > ISA cards typically have jumpers to set the IRQ's...
> > and if so, the jumpers need to be set manually to avoid conflicts, which
> > cannot be resolved
> > from either a bios setting or from within the OS.
>
> > My advice would be to remove all ISA cards but one...and once that is
> > configured...
> > add the second one...but be sure to manually configure it so as not to
> > conflict
> > with the one already setup.
>
> > It will definitely take some patience and an amount of trial and error.
>
> > Also note that at least *some* ISA cards have two distinct jumper
> > configurations...
> > that being manual or plug & play...so if you do have an ISA card with a
> plug
> > & play jumper setting...using that
> > might assuage your conflict problems- Hide quoted text -
>
> > - Show quoted text -
>
> Hi.  Actually this resource conflict issue occurs whether I either use
> my PnP ISA card (a Soundblaster AWE64) or no ISA cards at all.  (The
> AWE64 card is ISA PnP - it appears not to have any configurable
> jumpers.)
>
> I am wondering if this problem can be solved by disabling both onboard
> IDE ports in the BIOS, and then using a PCI IDE card for my HDD and
> DVD drive.  My theory is that this will dispense with the need to use
> the onboard VIA Bus Master PCI IDE Controller and the Secondary IDE
> Controller, because I think that this may be the source of the
> resource conflict problem.  However, I also wonder if the onboard PCI
> to ISA bridge mechanism is not functioning as it should.
>
> Any further thoughts gratefully received, thanks, regards, Robert.- Hide quoted text -
>
> - Show quoted text -

I have now completed doing the following -

Change the BIOS OS PnP to = Yes. Then, I inserted the AWE64 PnP ISA
card.

When Win98 booted up, it said it was installing "Motherboard
resources". Unfortunately it did not detect the AWE64 PnP ISA card.
Now, inside Device Manager, there are two "Motherboard resources"
entries inside the System Devices section.

I also tried to scan for new hardware, and it could neither find any
new PnP hardware, or any non-PnP hardware either.

Using safe mode, inside Device Manager, there appears to be no general
conflicts, errors or problems. However, as mentioned before, there
are 4 "IRQ Holder for PCI Steering" entries, and now 2 "motherboard
resources" entries.

I think at this stage, it may be worth setting the BIOS OS PnP = No,
and just see if Win98 is able to detect the AWE64 card. I'll try that
now...

Best regards, Robert.
 
R

rpgs rock dvds

On 19 Apr, 17:59, "MEB" <meb@not h...@hotmail.com> wrote:
> http://www.qdigrp.com/qdisite/eng/p...tp://www.motherboard.cz/mb/qdi/Advance 9.htm- BIOS/chipset - !
> scripting caution
>
>  Unless absolutely necessary, leave the VIA enabled. The conflict is likely
> not there.
>
>  Remove all add-in cards. Restart Normal and uninstall any related software.
> RESTART in Safe  Mode and check for any ghost entries. Remove any found or !
> devices. Make sure to check for the Blaster and remove everything related.
> Shut down.
>
> RESTART. Make sure the BIOS/CMOS is set for PnP OS installed, then make sure
> that you are NOT using manually set entries except for USB, video, keyboard,
> printer, or other necessary potentials in the BIOS/CMOS. Turn OFF Trend
> anti-virus in the BIOS, Start and install the motherboard drivers. Either
> use the VIA 4in1 OR the supplied QDI.
>
> RESTART in Normal Mode. Carefully review the system without add-in cards for
> any conflicts, prior to the suggested single card at a time installation and
> check. CHOOSE which BUS mastering driver you wish to use [you can only use
> one, either the VIA driver, or the offered QDI/third party]
>
>  Check the System and devices via Device Manager, if no errors, back up the
> registry. Run Find New Hardware and let it review the devices/system. If any
> found or otherwise, let them be changed. Restart [cold reboot]. Again run
> Find New Hardware, let anything be changed, note whether it found anything..
>  Recheck the system via Device Manager. Save/backup the registry. Recheck
> via Safe Mode for ghosted entries.
>
>  NOW add in the other cards, one at a time, but NOT the SoundBlaster AWE64.
> After each installation, install any software required, restart if
> necessary, and run through the Find New Hardware, using cold reboots after
> each installation. If no conflicts, again save the registry.
>
>  Download the AWE64 driver from a legitimate site [reports of corrupted
> manually modified drivers have been found]. Install that driver. There
> should be no conflicts. If there are conflicts,  post back and we can work
> through the issues now knowing the system is properly configured.
>
> --
> MEBhttp://peoplescounsel.orgfree.com

Sorry for the multiple replies. I have now completed the following -

Changed the BIOS OS PnP = No.

On boot-up, Windows 98 could not detect the AWE64 PnP ISA card.
However, running the "detect new hardware" wizard, it was able to find
"Gameport Joystick" and "Soundblaster 16 or AWE-32 or compatible"
which unfortunately is incorrect. I believe it is incorrect because
those 2 entries are non-PnP elements of the AWE64 card. So what
Windows 98 has found is not the PnP AWE64 card itself, but rather the
two non-PnP components of the AWE64 card. This means that
"soundblaster 16 type" sound effects will work, but AWE effects and
MIDI will not work.

I think that this indicates that Windows 98's ISA PnP mechanism is not
working as it should do. I think that this is because of a resource
problem with -

"IO read data port for ISA Plug and Play enumerator"

The resource conflict appears to be with both the Secondary IDE
Controller (dual fifo) and also with VIA Bus Master PCI IDE
Controller.

Please note, I have now changed the BIOS OS PnP = Yes.

Any further ideas or suggestions would be very gratefully received.
Thank you. Best regards from Robert.
 
R

rpgs rock dvds

On 19 Apr, 18:04, "MEB" <meb@not h...@hotmail.com> wrote:
>  Forgot to add:
>
>  If there are conflicts, please post the make and model of ALL card/devices
> and the driver version used for that device.
>
> --
> MEBhttp://peoplescounsel.orgfree.com
> --
> _________

I think it would be helpful if I explained exactly what I see inside
Device Manager for the "IO read data port for ISA Plug and Play
enumerator" system device.

Inside Device Manager, I click on this "PnP enumerator" system entry
to view its properties. It then tells me that "This device is working
properly". I then click on the "Resources" tab. It tells me -

"The resources this device is using do not match any of its known
configurations. To assign resources manually for this device, click
Set Configuration Manually."

I then click on the Set Configuration Manually button, and it is then
that I see the conflict. There are 4 resource type entries - the
second entry has a conflict. The conflicting device list tells me
that Secondary IDE controller (dual fifo) and also VIA Bus Master PCI
IDE Controller are the conflicting devices for the Input/Output Range
of 0374-0377.

Please note that I have tried to do various actions here. I have
tried using Basic Configuration setting 0001. I have also tried to
change the conflicting 0374-0377 resource setting entry to a different
value entry so that there is no conflict - for example change to
03FC-03FF. Both of these actions do not appear to remedy the conflict
because if I do either of these changes, and then reboot, the resource
conflict problem simply reappears. In other words, my changes do not
appear to be "saved".

Best regards, Robert.
 
M

MEB

Oh boy...

Okay,
1. PlugnPlay OS should be enabled. Make sure to reset the ESDI after/during
saving the BIOS/CMOS.
2. The AWE is NOT installed until you install the *driver* for it. Remove it
again after cleaning up the failed installation(s).
3. The PCI and steering entries are normal.
4. The PnP Blaster and joystick [though not actually there until you install
the driver] being found indicate the card is communicating with the OS.
5. 98 [and particularly SE] has default PnP drivers for the VIA chipset,
uninstall the entire hard drive adapter entries and system entries *OR* use
the default VIA drivers that the 98SE installation used [98 plain version
NEEDS the VIA update].
*IF* installing the VIA 4in1, uninstall the System and hard drive entries in
Device Manager, do not shut down, install the VIA 4in1 drivers. Let it fully
install, shutdown, restart in Safe Mode. Shutdown. Restart in DOS Mode,
Delete c:\{your windows folder}\win386.swp. Restart in Normal Mode.let it
finish installing the VIA 4in1 [make absolutely sure you are using the
correct version for your motherboard.]. *OR* use the default VIA drivers
that the 98SE installation used/will reinstall after you remove those
entries.

CHECK the OS again, as previously posted, AND SAVE THE REGISTRY. Post if
errors. DO NOT INSTALL THE AWE until you post back with results from the
cleanup and re-installation of the other devices.

NOTE: MAKE SURE you update your Win98x OS with its updates BEFORE you
install the AWE driver [they will error out with 98x base installation
files]..The AWE generally works in 98SE but MAY take considerable
modification to work in 98FE/GOLD/plain [check on Google].
Post back after you install the updates and have checked the system for
errors, and BEFORE you install the AWE.

IF you can't wait, search on Microsoft and Google for errors associated
with the AWE64 card and work-arounds BEFORE you install the AWE. Work
through those correction techniques and/or post back with questions.

IF posting back - Post the exact errors or other.


--
MEB http://peoplescounsel.orgfree.com
--
_________

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:4bfddbaf-61fa-45cf-96b4-7b9af2c6d710@d1g2000hsg.googlegroups.com...
On 19 Apr, 17:59, "MEB" <meb@not h...@hotmail.com> wrote:
>
http://www.qdigrp.com/qdisite/eng/p...tp://www.motherboard.cz/mb/qdi/Advance 9.htm-
BIOS/chipset - !
> scripting caution
>
> Unless absolutely necessary, leave the VIA enabled. The conflict is likely
> not there.
>
> Remove all add-in cards. Restart Normal and uninstall any related
software.
> RESTART in Safe Mode and check for any ghost entries. Remove any found or
!
> devices. Make sure to check for the Blaster and remove everything related.
> Shut down.
>
> RESTART. Make sure the BIOS/CMOS is set for PnP OS installed, then make
sure
> that you are NOT using manually set entries except for USB, video,
keyboard,
> printer, or other necessary potentials in the BIOS/CMOS. Turn OFF Trend
> anti-virus in the BIOS, Start and install the motherboard drivers. Either
> use the VIA 4in1 OR the supplied QDI.
>
> RESTART in Normal Mode. Carefully review the system without add-in cards
for
> any conflicts, prior to the suggested single card at a time installation
and
> check. CHOOSE which BUS mastering driver you wish to use [you can only use
> one, either the VIA driver, or the offered QDI/third party]
>
> Check the System and devices via Device Manager, if no errors, back up the
> registry. Run Find New Hardware and let it review the devices/system. If
any
> found or otherwise, let them be changed. Restart [cold reboot]. Again run
> Find New Hardware, let anything be changed, note whether it found
anything.
> Recheck the system via Device Manager. Save/backup the registry. Recheck
> via Safe Mode for ghosted entries.
>
> NOW add in the other cards, one at a time, but NOT the SoundBlaster AWE64.
> After each installation, install any software required, restart if
> necessary, and run through the Find New Hardware, using cold reboots after
> each installation. If no conflicts, again save the registry.
>
> Download the AWE64 driver from a legitimate site [reports of corrupted
> manually modified drivers have been found]. Install that driver. There
> should be no conflicts. If there are conflicts, post back and we can work
> through the issues now knowing the system is properly configured.
>
> --
> MEBhttp://peoplescounsel.orgfree.com

Sorry for the multiple replies. I have now completed the following -

Changed the BIOS OS PnP = No.

On boot-up, Windows 98 could not detect the AWE64 PnP ISA card.
However, running the "detect new hardware" wizard, it was able to find
"Gameport Joystick" and "Soundblaster 16 or AWE-32 or compatible"
which unfortunately is incorrect. I believe it is incorrect because
those 2 entries are non-PnP elements of the AWE64 card. So what
Windows 98 has found is not the PnP AWE64 card itself, but rather the
two non-PnP components of the AWE64 card. This means that
"soundblaster 16 type" sound effects will work, but AWE effects and
MIDI will not work.

I think that this indicates that Windows 98's ISA PnP mechanism is not
working as it should do. I think that this is because of a resource
problem with -

"IO read data port for ISA Plug and Play enumerator"

The resource conflict appears to be with both the Secondary IDE
Controller (dual fifo) and also with VIA Bus Master PCI IDE
Controller.

Please note, I have now changed the BIOS OS PnP = Yes.

Any further ideas or suggestions would be very gratefully received.
Thank you. Best regards from Robert.
 
R

rpgs rock dvds

On 19 Apr, 20:04, "MEB" <meb@not h...@hotmail.com> wrote:
> Oh boy...
>
>  Okay,
> 1. PlugnPlay OS should be enabled. Make sure to reset the ESDI after/during
> saving the BIOS/CMOS.
> 2. The AWE is NOT installed until you install the *driver* for it. Remove it
> again after cleaning up the failed installation(s).
> 3. The PCI and steering entries are normal.
> 4. The PnP Blaster and joystick [though not actually there until you install
> the driver] being found indicate the card is communicating with the OS.
> 5. 98 [and particularly SE] has default PnP drivers for the VIA chipset,
> uninstall the entire hard drive adapter entries and system entries *OR* use
> the default VIA drivers that the 98SE installation used [98 plain version
> NEEDS the VIA update].
> *IF* installing the VIA 4in1, uninstall the System and hard drive entries in
> Device Manager, do not shut down, install the VIA 4in1 drivers. Let it fully
> install, shutdown, restart in Safe Mode. Shutdown. Restart in DOS Mode,
> Delete c:\{your windows folder}\win386.swp. Restart in Normal Mode.let it
> finish installing the VIA 4in1 [make absolutely sure you are using the
> correct version for your motherboard.]. *OR* use the default VIA drivers
> that the 98SE installation used/will reinstall after you remove those
> entries.
>
>  CHECK the OS again, as previously posted, AND SAVE THE REGISTRY. Post if
> errors. DO NOT INSTALL THE AWE until you post back with results from the
> cleanup and re-installation of the other devices.
>
> NOTE: MAKE SURE you update your Win98x OS with its updates BEFORE you
> install the AWE driver [they will error out with 98x base installation
> files]..The AWE generally works in 98SE but MAY take considerable
> modification to work in 98FE/GOLD/plain [check on Google].
>  Post back after you install the updates and have checked the system for
> errors, and BEFORE you install the AWE.
>
>  IF you can't wait, search on Microsoft and Google for errors associated
> with the AWE64 card and work-arounds BEFORE you install the AWE. Work
> through those correction techniques and/or post back with questions.
>
> IF posting back -  Post the exact errors or other.
>
> --
> MEBhttp://peoplescounsel.orgfree.com

Thanks very much for your additional instructions.

Before proceeding, I really must double-check that I am about to do
the correct actions. I will do all of the 9 actions listed below
tomorrow morning in about 12 hours time I can't today because I am so
tired as I have been on the PC for 15 hours trying to fix this
problem.

1. Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
graphics card.

2. Set BIOS OS PnP = Yes

3. Reset the ESDI = Enabled. Also disable BIOS anti-virus.

4. Reformat HDD (I don't mind doing this)

5. Reinstall Win 98SE (I don't mind doing this)

6. Run setup.exe from AWE64 CD, then shutdown PC.

7. Insert AWE64 PnP ISA card inside PC, then turn on PC.

8. At this stage, I believe that Windows 98SE will either not detect
the AWE64 ISA PnP card, or just install a "Motherboard Resources"
system device. If I then run the hardware detection wizard, I believe
that Windows 98SE will either not detect the AWE card, or incorrectly
detect Joystick & Soundblaster 16/AWE32/Compatible.

9. If action number 8 above results in no successful AWE64 detection/
installation, should I then go ahead and try to manually install the
AWE driver using the "Add new hardware" wizard?

Please note - I am not sure if actions numbered 6 and 7 are the
correct actions to do. Action 8 is not really an action, but what I
think might happen - and I could be wrong of course!

I am also unsure about two other actions -

Firstly, I do not know whether I need to connect to the internet to
update Windows 98SE. (If this is required, I will need to install a
PCI-based Ethernet card. I bought one recently, so this is OK, but I
would rather not do this now if it is not required.)

Secondly, I do not know whether I need to install the VIA 4-in-1
package. If it is not required, then I would rather not install it
now.

Thanks a lot, all the best, Robert.
 
M

MEB

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:6f14c119-c303-4968-9f70-39dd9b3b2a1d@26g2000hsk.googlegroups.com...
On 19 Apr, 20:04, "MEB" <meb@not h...@hotmail.com> wrote:
> Oh boy...
>
> Okay,
> 1. PlugnPlay OS should be enabled. Make sure to reset the ESDI
after/during
> saving the BIOS/CMOS.
> 2. The AWE is NOT installed until you install the *driver* for it. Remove
it
> again after cleaning up the failed installation(s).
> 3. The PCI and steering entries are normal.
> 4. The PnP Blaster and joystick [though not actually there until you
install
> the driver] being found indicate the card is communicating with the OS.
> 5. 98 [and particularly SE] has default PnP drivers for the VIA chipset,
> uninstall the entire hard drive adapter entries and system entries *OR*
use
> the default VIA drivers that the 98SE installation used [98 plain version
> NEEDS the VIA update].
> *IF* installing the VIA 4in1, uninstall the System and hard drive entries
in
> Device Manager, do not shut down, install the VIA 4in1 drivers. Let it
fully
> install, shutdown, restart in Safe Mode. Shutdown. Restart in DOS Mode,
> Delete c:\{your windows folder}\win386.swp. Restart in Normal Mode.let it
> finish installing the VIA 4in1 [make absolutely sure you are using the
> correct version for your motherboard.]. *OR* use the default VIA drivers
> that the 98SE installation used/will reinstall after you remove those
> entries.
>
> CHECK the OS again, as previously posted, AND SAVE THE REGISTRY. Post if
> errors. DO NOT INSTALL THE AWE until you post back with results from the
> cleanup and re-installation of the other devices.
>
> NOTE: MAKE SURE you update your Win98x OS with its updates BEFORE you
> install the AWE driver [they will error out with 98x base installation
> files]..The AWE generally works in 98SE but MAY take considerable
> modification to work in 98FE/GOLD/plain [check on Google].
> Post back after you install the updates and have checked the system for
> errors, and BEFORE you install the AWE.
>
> IF you can't wait, search on Microsoft and Google for errors associated
> with the AWE64 card and work-arounds BEFORE you install the AWE. Work
> through those correction techniques and/or post back with questions.
>
> IF posting back - Post the exact errors or other.
>
> --
> MEBhttp://peoplescounsel.orgfree.com

Thanks very much for your additional instructions.

Before proceeding, I really must double-check that I am about to do
the correct actions. I will do all of the 9 actions listed below
tomorrow morning in about 12 hours time I can't today because I am so
tired as I have been on the PC for 15 hours trying to fix this
problem.

1. Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
graphics card.

2. Set BIOS OS PnP = Yes

3. Reset the ESDI = Enabled. Also disable BIOS anti-virus.

4. Reformat HDD (I don't mind doing this)

5. Reinstall Win 98SE (I don't mind doing this)

5A. When installing, chose EITHER [only one method] the default VIA or
follow the routine to remove the default [as decscribe previously] and
install the 4in1 update, making sure its for the motherboard you intend to
use it on.

*5B. **Install all upgrades to your OS*** and other devices BEFORE
installing the AWE driver. Check the Device Manager for any issues. IF you
are suing any old programs you intend to use, it is generally best to
install and update those prior to the system updates.

*5C. MAKE SURE that the AWE driver you use is a good driver [there may be a
newer driver than the CD], look arouind the Internet FIRST and check file
sizes and dates on other potential downloads.

*5D. Unzip or otherwise open the AWE driver you intend to use, making sure
that if any folders are shown, that they are maintained when unzipped or
otherwise.

6. Run setup.exe from AWE64 CD, then shutdown PC.

*6A. Before running from the cdrom, copy the intended Win98 install
directory to the hard drive. Compare the CD drivers from any newer you may
have downloaded. If new hardware was found. direct to the hard drive's
folder where you copied the files or to the folder which contains the newer
driver.
* I find conflicting information on whether to install the card first or the
driver. Perhaps someone can confirm which works best. {The norm is to
install the card then the driver [network cards/devices are sometimes the
opposite.] The only AWE64 that I installed were, IIRC, card first then
driver.}

7. Insert AWE64 PnP ISA card inside PC, then turn on PC.

8. At this stage, I believe that Windows 98SE will either not detect
the AWE64 ISA PnP card, or just install a "Motherboard Resources"
system device. If I then run the hardware detection wizard, I believe
that Windows 98SE will either not detect the AWE card, or incorrectly
detect Joystick & Soundblaster 16/AWE32/Compatible.

9. If action number 8 above results in no successful AWE64 detection/
installation, should I then go ahead and try to manually install the
AWE driver using the "Add new hardware" wizard?

Please note - I am not sure if actions numbered 6 and 7 are the
correct actions to do. Action 8 is not really an action, but what I
think might happen - and I could be wrong of course!

I am also unsure about two other actions -

Firstly, I do not know whether I need to connect to the internet to
update Windows 98SE. (If this is required, I will need to install a
PCI-based Ethernet card. I bought one recently, so this is OK, but I
would rather not do this now if it is not required.)

** Gary Terhune [http://www.grystmill.com/] has two update CDs available.
One is the MS Security Updates circa 2004, and the second contains the
subsequent updates. Gary apparently includes some form of installation
routine to ensure they are installed in the proper order.
**OR download the updates from the catalog from the updates site and burn
them to CDROM [using the machine you are apparently using now] and install
them PRIOR to attempting the AWE install.
**The system should be updated prior to the AWE install, so if necessary
[check the installer date, it is likely well beyond SE RTM date] install
that netcard and update that way.

Secondly, I do not know whether I need to install the VIA 4-in-1
package. If it is not required, then I would rather not install it
now.

*Install that ONLY if you find it necessary [you have SE], IF there are
issues, you MUST follow the previously posted routine to ensure it is
properly installed if you go that route.

Thanks a lot, all the best, Robert.

*Keep us informed....

--
MEB http://peoplescounsel.orgfree.com
--
_________
 
M

MEB

Okay, found the old driver locally [checked on Creative support to see if
there were others/newer], sbw9xup.exe, from the readme.txt:

UPDATING SOUND BLASTER 16/32/AWE DRIVERS FOR WINDOWS 95/98
==========================================================

This package supports Sound Blaster 16, Sound Blaster 32 and Sound
Blaster AWE from Creative Technology Ltd.

To update the drivers for Microsoft Windows 95/98:

1. Put the whole sets of this package in a sub directory (or diskette)
(eg C:\UPDDRV).

2. In Windows 95/98, Click the Start menu, and select Run.

3. Type in C:\UPDDRV\UPDDRV95.EXE where C:\UPDDRV is the directory
where the file is located, and press the Enter key.

4. Drivers will be updated automatically, you need to restart your
computer for the changes to take effect.

Driver dates from 6-98 so contrary to my prior presentation, there should be
no issue concerning when this driver is installed or whether the system was
updated.. Sorry about that, must have been thinking about the 128 or
something...

--
MEB http://peoplescounsel.orgfree.com
--
_________
 
F

Franc Zabkar

On Sat, 19 Apr 2008 13:13:08 -0700 (PDT), rpgs rock dvds
<rpgsrockdvds@hotmail.co.uk> put finger to keyboard and composed:

>8. At this stage, I believe that Windows 98SE will either not detect
>the AWE64 ISA PnP card, or just install a "Motherboard Resources"
>system device. If I then run the hardware detection wizard, I believe
>that Windows 98SE will either not detect the AWE card, or incorrectly
>detect Joystick & Soundblaster 16/AWE32/Compatible.

I don't know if it will help, but you could set "PnP Aware OS" equal
to "No" and allow BIOS to find your ISA devices. Then you can use this
old Phoenix utility to see what BIOS found:

http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/pnpbtst7.exe

You can run it in real DOS mode (better) or from within a Windows DOS
box.

Below is what I see in my old socket 7 system (AMI BIOS). It seems to
match the list of devices under the HKEY_LOCAL_MACHINE\Enum\BIOS key
in my registry. OTOH my CMedia onboard sound chip shows up under
HKEY_LOCAL_MACHINE\Enum\ISAPNP.

=====================================================================
C:\utils\BIOS\BIOSutil\Phoenix>pnpbtst7
Phoenix Plug and Play BIOS Test Utility, Ver 1.07.
(C) Phoenix Technologies, Ltd., 1994-99
All rights reserved.

**********************************************************************
* YOU MUST START IN REAL MODE ONLY!. *
* (Without EMM386 Loaded.) *
**********************************************************************

-- PnPBTst : Version 1.07b ------- Executing in: REAL MODE
--------------
0) Get # DNs 5) Get DockSta Info C) Get ISA Cfg (40h) L) Node
List
1) Get DevNode 9) Set Static Res D) Get Escd Inf (41h) S) Node
Summary
2) Set DevNode A) Get Static Res E) Read Escd (42h) R) Real
Mode
3) Get Event B) Get APM ID Table F) Write Escd (43h) P) Prot
Mode
4) Send Message I) ISA PnP Z)
Header
-----------------------------------------------------------------------------
Enter a function code (<Esc> to Exit Program): S
Enter a Control Code (1=Current, 2=Next Boot): 1

Num Id Resources
------------------------------------------------------------
0 PNP0C01 Mem32F 0x00000000#640KB, Mem32F 0x000E0000#128KB,
1 PNP0000 20h-21h, A0h-A1h, Irq2,
2 PNP0200 Dma4, 0h-Fh, 80h-90h, 94h-9Fh, C0h-DEh,
3 PNP0100 Irq0, 40h-43h,
4 PNP0B00 Irq8, 70h-71h,
5 PNP0303 Irq1, 60h, 64h,
6 PNP0800 61h,
7 PNP0C04 Irq13, F0h-FFh,
8 PNP0A03
9 PNP0501 (3F8h-3F8h)#8, Irq4,
10 PNP0501 (2E8h-2E8h)#8, Irq3,
11 PNP0400 (378h-378h)#8, Irq7,
12 PNP0700 (3F0h-3F0h)#6, Irq6, Dma2,
13 PNP0C02 (4D0h-4D0h)#2, (CF8h-CF8h)#8, (3F7h-3F7h)#1, Mem32F
0x00100000#130048KB, (6100h-6100h)#64,
=====================================================================

You could use the following utility to detect the devices (including
PCI) in your BIOS ESCD table:

http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/nvram120.exe

Here is my sample output:

http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/M571ESCD.TXT
http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/M571ESCD.SUM

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
 
R

rpgs rock dvds

On 20 Apr, 01:04, Franc Zabkar <fzab...@iinternode.on.net> wrote:
> On Sat, 19 Apr 2008 13:13:08 -0700 (PDT), rpgs rock dvds
> <rpgsrockd...@hotmail.co.uk> put finger to keyboard and composed:
>
> >8.  At this stage, I believe that Windows 98SE will either not detect
> >the AWE64 ISA PnP card, or just install a "Motherboard Resources"
> >system device.  If I then run the hardware detection wizard, I believe
> >that Windows 98SE will either not detect the AWE card, or incorrectly
> >detect Joystick & Soundblaster 16/AWE32/Compatible.
>
> I don't know if it will help, but you could set "PnP Aware OS" equal
> to "No" and allow BIOS to find your ISA devices. Then you can use this
> old Phoenix utility to see what BIOS found:
>
> http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/pnpbtst7.exe
>
> You can run it in real DOS mode (better) or from within a Windows DOS
> box.
>
> Below is what I see in my old socket 7 system (AMI BIOS). It seems to
> match the list of devices under the HKEY_LOCAL_MACHINE\Enum\BIOS key
> in my registry. OTOH my CMedia onboard sound chip shows up under
> HKEY_LOCAL_MACHINE\Enum\ISAPNP.
>
> =====================================================================
> C:\utils\BIOS\BIOSutil\Phoenix>pnpbtst7
> Phoenix Plug and Play BIOS Test Utility, Ver 1.07.
> (C) Phoenix Technologies, Ltd., 1994-99
> All rights reserved.
>
> **********************************************************************
> *                  YOU MUST START IN REAL MODE ONLY!.                *
> *                      (Without EMM386 Loaded.)                      *
> **********************************************************************
>
> -- PnPBTst : Version 1.07b ------- Executing in:      REAL MODE
> --------------
>   0) Get # DNs    5) Get DockSta Info   C) Get ISA Cfg (40h)  L) Node
> List
>   1) Get DevNode  9) Set Static Res     D) Get Escd Inf (41h) S) Node
> Summary
>   2) Set DevNode  A) Get Static Res     E) Read Escd (42h)    R) Real
> Mode
>   3) Get Event    B) Get APM ID Table   F) Write Escd (43h)   P) Prot
> Mode
>   4) Send Message                       I) ISA PnP            Z)
> Header
> ---------------------------------------------------------------------------­--
> Enter a function code (<Esc> to Exit Program): S
> Enter a Control Code (1=Current, 2=Next Boot): 1
>
>  Num  Id       Resources
> ------------------------------------------------------------
>    0  PNP0C01  Mem32F 0x00000000#640KB, Mem32F 0x000E0000#128KB,
>    1  PNP0000  20h-21h, A0h-A1h, Irq2,
>    2  PNP0200  Dma4, 0h-Fh, 80h-90h, 94h-9Fh, C0h-DEh,
>    3  PNP0100  Irq0, 40h-43h,
>    4  PNP0B00  Irq8, 70h-71h,
>    5  PNP0303  Irq1, 60h, 64h,
>    6  PNP0800  61h,
>    7  PNP0C04  Irq13, F0h-FFh,
>    8  PNP0A03
>    9  PNP0501  (3F8h-3F8h)#8, Irq4,
>   10  PNP0501  (2E8h-2E8h)#8, Irq3,
>   11  PNP0400  (378h-378h)#8, Irq7,
>   12  PNP0700  (3F0h-3F0h)#6, Irq6, Dma2,
>   13  PNP0C02  (4D0h-4D0h)#2, (CF8h-CF8h)#8, (3F7h-3F7h)#1, Mem32F
> 0x00100000#130048KB, (6100h-6100h)#64,
> =====================================================================
>
> You could use the following utility to detect the devices (including
> PCI) in your BIOS ESCD table:
>
> http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/nvram120.exe
>
> Here is my sample output:
>
> http://www.users.on.net/~fzabkar/BI...on.net/~fzabkar/BIOSutil/Phoenix/M571ESCD.SUM
>
> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.


Thanks a lot for your suggestions. Before I wipe my HDD and start
over, I wanted to try this out, and here are my findings -

Inside BIOS, I changed BIOS OS PnP = No

Then, when booting up, I see BIOS display this information on the
screen -

card number 1
device number 0
dma 1,5
irq=5
device name audio

(It looks like BIOS can see the AWE64 PnP ISA card.)

Also, inside DOS real-mode, I run the nvram120 utility. It tells me -

Display ESCD summary of all nodes:

01: Slot#= 1, Id=___00C7
0 : Irq5, Dma1, Dma5, 220h-22Fh, 330h-331h, 388h-38Bh,
1 : 200h-207h,
2 : 620h-623h,
3 : PnP ISA Ven=___00C7 Ser=0xFFFFFFFF

(rest of information snipped)

I think this is good, because it looks like the nvram120 utility can
see all of the AWE64 card's elements including the AWE midi
functionality at the 620 section -- excuse my ignorant technical
description here, I'm not very technically minded.

Also, I did run the pnpbtst7 utility, but I'm afraid my lack of
technical knowledge makes it difficult for me to understand the
displayed output. One thing I did note however, was I could not find
the IRQ number 5 listed in the output, which may or may not be of use,
I'm sorry I'm not sure.

One final observation - I decided to run a DOS program that was
included on the AWE64 CD called "aweutil". I ran it like this -

aweutil /?

I just wanted to see what options were available. The results
displayed were -

ERR012: AWE32 initialization failed


Thanks, Best regards, Robert.
 
R

rpgs rock dvds

On 19 Apr, 23:34, "MEB" <meb@not h...@hotmail.com> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:6f14c119-c303-4968-9f70-39dd9b3b2a1d@26g2000hsk.googlegroups.com...
> On 19 Apr, 20:04, "MEB" <meb@not h...@hotmail.com> wrote:
>
>
>
>
>
> > Oh boy...
>
> > Okay,
> > 1. PlugnPlay OS should be enabled. Make sure to reset the ESDI
> after/during
> > saving the BIOS/CMOS.
> > 2. The AWE is NOT installed until you install the *driver* for it. Remove
> it
> > again after cleaning up the failed installation(s).
> > 3. The PCI and steering entries are normal.
> > 4. The PnP Blaster and joystick [though not actually there until you
> install
> > the driver] being found indicate the card is communicating with the OS.
> > 5. 98 [and particularly SE] has default PnP drivers for the VIA chipset,
> > uninstall the entire hard drive adapter entries and system entries *OR*
> use
> > the default VIA drivers that the 98SE installation used [98 plain version
> > NEEDS the VIA update].
> > *IF* installing the VIA 4in1, uninstall the System and hard drive entries
> in
> > Device Manager, do not shut down, install the VIA 4in1 drivers. Let it
> fully
> > install, shutdown, restart in Safe Mode. Shutdown. Restart in DOS Mode,
> > Delete c:\{your windows folder}\win386.swp. Restart in Normal Mode.let it
> > finish installing the VIA 4in1 [make absolutely sure you are using the
> > correct version for your motherboard.]. *OR* use the default VIA drivers
> > that the 98SE installation used/will reinstall after you remove those
> > entries.
>
> > CHECK the OS again, as previously posted, AND SAVE THE REGISTRY. Post if
> > errors. DO NOT INSTALL THE AWE until you post back with results from the
> > cleanup and re-installation of the other devices.
>
> > NOTE: MAKE SURE you update your Win98x OS with its updates BEFORE you
> > install the AWE driver [they will error out with 98x base installation
> > files]..The AWE generally works in 98SE but MAY take considerable
> > modification to work in 98FE/GOLD/plain [check on Google].
> > Post back after you install the updates and have checked the system for
> > errors, and BEFORE you install the AWE.
>
> > IF you can't wait, search on Microsoft and Google for errors associated
> > with the AWE64 card and work-arounds BEFORE you install the AWE. Work
> > through those correction techniques and/or post back with questions.
>
> > IF posting back - Post the exact errors or other.
>
> > --
> > MEBhttp://peoplescounsel.orgfree.com
>
> Thanks very much for your additional instructions.
>
> Before proceeding, I really must double-check that I am about to do
> the correct actions.  I will do all of the 9 actions listed below
> tomorrow morning in about 12 hours time I can't today because I am so
> tired as I have been on the PC for 15 hours trying to fix this
> problem.
>
> 1.  Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
> graphics card.
>
> 2.  Set BIOS OS PnP = Yes
>
> 3.  Reset the ESDI = Enabled.  Also disable BIOS anti-virus.
>
> 4.  Reformat HDD  (I don't mind doing this)
>
> 5.  Reinstall Win 98SE  (I don't mind doing this)
>
> 5A. When installing, chose EITHER [only one method] the default VIA or
> follow the routine to remove the default [as decscribe previously] and
> install the 4in1 update, making sure its for the motherboard you intend to
> use it on.
>
> *5B. **Install all upgrades to your OS*** and other devices BEFORE
> installing the AWE driver. Check the Device Manager for any issues. IF you
> are suing any old programs you intend to use, it is generally best to
> install and update those prior to the system updates.
>
> *5C. MAKE SURE that the AWE driver you use is a good driver [there may be a
> newer driver than the CD], look arouind the Internet FIRST and check file
> sizes and dates on other potential downloads.
>
> *5D. Unzip or otherwise open the AWE driver you intend to use, making sure
> that if any folders are shown, that they are maintained when unzipped or
> otherwise.
>
> 6.  Run setup.exe from AWE64 CD, then shutdown PC.
>
> *6A. Before running from the cdrom, copy the intended Win98 install
> directory to the hard drive. Compare the CD drivers from any newer you may
> have downloaded. If new hardware was found. direct to the hard drive's
> folder where you copied the files or to the folder which contains the newer
> driver.
> * I find conflicting information on whether to install the card first or the
> driver. Perhaps someone can confirm which works best. {The norm is to
> install the card then the driver [network cards/devices are sometimes the
> opposite.] The only AWE64 that I installed were, IIRC, card first then
> driver.}
>
> 7.  Insert AWE64 PnP ISA card inside PC, then turn on PC.
>
> 8.  At this stage, I believe that Windows 98SE will either not detect
> the AWE64 ISA PnP card, or just install a "Motherboard Resources"
> system device.  If I then run the hardware detection wizard, I believe
> that Windows 98SE will either not detect the AWE card, or incorrectly
> detect Joystick & Soundblaster 16/AWE32/Compatible.
>
> 9.  If action number 8 above results in no successful AWE64 detection/
> installation, should I then go ahead and try to manually install the
> AWE driver using the "Add new hardware" wizard?
>
> Please note - I am not sure if actions numbered 6 and 7 are the
> correct actions to do.  Action 8 is not really an action, but what I
> think might happen - and I could be wrong of course!
>
> I am also unsure about two other actions -
>
> Firstly, I do not know whether I need to connect to the internet to
> update Windows 98SE.  (If this is required, I will need to install a
> PCI-based Ethernet card.  I bought one recently, so this is OK, but I
> would rather not do this now if it is not required.)
>
> ** Gary Terhune [http://www.grystmill.com/] has two update CDs available.
> One is the MS Security Updates circa 2004, and the second contains the
> subsequent updates. Gary apparently includes some form of installation
> routine to ensure they are installed in the proper order.
> **OR download the updates from the catalog from the updates site and burn
> them to CDROM [using the machine you are apparently using now] and install
> them PRIOR to attempting the AWE install.
> **The system should be updated prior to the AWE install, so if necessary
> [check the installer date, it is likely well beyond SE RTM date] install
> that netcard and update that way.
>
> Secondly, I do not know whether I need to install the VIA 4-in-1
> package.  If it is not required, then I would rather not install it
> now.
>
> *Install that ONLY if you find it necessary [you have SE], IF there are
> issues, you MUST follow the previously posted routine to ensure it is
> properly installed if you go that route.
>
> Thanks a lot, all the best, Robert.
>
> *Keep us informed....
>
> --
> MEBhttp://peoplescounsel.orgfree.com
> --
> _________- Hide quoted text -
>
> - Show quoted text -

Thanks very much for your continued assistance.

Before I list the tasks which I have completed, you may be interested
in my recent reply I gave to Franc Zabkar about my BIOS observations.

Also, please note that I am currently experimenting with an AWE64 PnP
ISA card model CT4520, which is a Value edition, but I am awaiting
imminent delivery of a Gold edition, model CT4390.

Currently completed tasks -

1. Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
graphics card.

2. Set BIOS OS PnP = Yes

3. Reset the ESDI = Enabled. Also disable BIOS anti-virus.

4. Reformat HDD

5. Reinstall Win 98SE

5A. I have decided not to use the VIA 4-in-1 package at this moment
in time.

5B. Right at this very moment, I now need to install all updates to
Windows 98SE before proceeding any further. I need to obtain these
updates. I can either install a new ethernet card which I bought and
connect to the internet, or I can await Gary's response about
obtaining his Windows 98 update CDs - I emailed him this morning about
this.

Some questions please -

A) If I install a network card and attempt to connect to the
internet, I must first obtain a Windows 98SE compatible firewall
program to shut out the bad guys. Any recommendations please? I
think this firewall program needs to be a complete downloadable
program, rather than one which requires you to run it so it then
connects to the internet and then downloads the rest of the package,
because this might not be safe. (Naturally I have another PC to do
this, as I am using it right now to send these newsgroup messages.)

B) Let's say I have successfully and safely connected to the internet
on the Windows 98SE PC -- in order to obtain the Windows 98SE updates,
can I just simply use Microsoft's Windows Update service? Please note
- I would *much* rather have the updates on CD. This is because I can
reinstall Windows98SE very easily, without requiring a working
internet connection.

Many thanks for all your help, best regards, Robert.
 
R

rpgs rock dvds

On 20 Apr, 12:02, rpgs rock dvds <rpgsrockd...@hotmail.co.uk> wrote:
> On 19 Apr, 23:34, "MEB" <meb@not h...@hotmail.com> wrote:
>
>
>
>
>
> > "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:6f14c119-c303-4968-9f70-39dd9b3b2a1d@26g2000hsk.googlegroups.com...
> > On 19 Apr, 20:04, "MEB" <meb@not h...@hotmail.com> wrote:
>
> > > Oh boy...
>
> > > Okay,
> > > 1. PlugnPlay OS should be enabled. Make sure to reset the ESDI
> > after/during
> > > saving the BIOS/CMOS.
> > > 2. The AWE is NOT installed until you install the *driver* for it. Remove
> > it
> > > again after cleaning up the failed installation(s).
> > > 3. The PCI and steering entries are normal.
> > > 4. The PnP Blaster and joystick [though not actually there until you
> > install
> > > the driver] being found indicate the card is communicating with the OS..
> > > 5. 98 [and particularly SE] has default PnP drivers for the VIA chipset,
> > > uninstall the entire hard drive adapter entries and system entries *OR*
> > use
> > > the default VIA drivers that the 98SE installation used [98 plain version
> > > NEEDS the VIA update].
> > > *IF* installing the VIA 4in1, uninstall the System and hard drive entries
> > in
> > > Device Manager, do not shut down, install the VIA 4in1 drivers. Let it
> > fully
> > > install, shutdown, restart in Safe Mode. Shutdown. Restart in DOS Mode,
> > > Delete c:\{your windows folder}\win386.swp. Restart in Normal Mode.let it
> > > finish installing the VIA 4in1 [make absolutely sure you are using the
> > > correct version for your motherboard.]. *OR* use the default VIA drivers
> > > that the 98SE installation used/will reinstall after you remove those
> > > entries.
>
> > > CHECK the OS again, as previously posted, AND SAVE THE REGISTRY. Post if
> > > errors. DO NOT INSTALL THE AWE until you post back with results from the
> > > cleanup and re-installation of the other devices.
>
> > > NOTE: MAKE SURE you update your Win98x OS with its updates BEFORE you
> > > install the AWE driver [they will error out with 98x base installation
> > > files]..The AWE generally works in 98SE but MAY take considerable
> > > modification to work in 98FE/GOLD/plain [check on Google].
> > > Post back after you install the updates and have checked the system for
> > > errors, and BEFORE you install the AWE.
>
> > > IF you can't wait, search on Microsoft and Google for errors associated
> > > with the AWE64 card and work-arounds BEFORE you install the AWE. Work
> > > through those correction techniques and/or post back with questions.
>
> > > IF posting back - Post the exact errors or other.
>
> > > --
> > > MEBhttp://peoplescounsel.orgfree.com
>
> > Thanks very much for your additional instructions.
>
> > Before proceeding, I really must double-check that I am about to do
> > the correct actions.  I will do all of the 9 actions listed below
> > tomorrow morning in about 12 hours time I can't today because I am so
> > tired as I have been on the PC for 15 hours trying to fix this
> > problem.
>
> > 1.  Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
> > graphics card.
>
> > 2.  Set BIOS OS PnP = Yes
>
> > 3.  Reset the ESDI = Enabled.  Also disable BIOS anti-virus.
>
> > 4.  Reformat HDD  (I don't mind doing this)
>
> > 5.  Reinstall Win 98SE  (I don't mind doing this)
>
> > 5A. When installing, chose EITHER [only one method] the default VIA or
> > follow the routine to remove the default [as decscribe previously] and
> > install the 4in1 update, making sure its for the motherboard you intend to
> > use it on.
>
> > *5B. **Install all upgrades to your OS*** and other devices BEFORE
> > installing the AWE driver. Check the Device Manager for any issues. IF you
> > are suing any old programs you intend to use, it is generally best to
> > install and update those prior to the system updates.
>
> > *5C. MAKE SURE that the AWE driver you use is a good driver [there may be a
> > newer driver than the CD], look arouind the Internet FIRST and check file
> > sizes and dates on other potential downloads.
>
> > *5D. Unzip or otherwise open the AWE driver you intend to use, making sure
> > that if any folders are shown, that they are maintained when unzipped or
> > otherwise.
>
> > 6.  Run setup.exe from AWE64 CD, then shutdown PC.
>
> > *6A. Before running from the cdrom, copy the intended Win98 install
> > directory to the hard drive. Compare the CD drivers from any newer you may
> > have downloaded. If new hardware was found. direct to the hard drive's
> > folder where you copied the files or to the folder which contains the newer
> > driver.
> > * I find conflicting information on whether to install the card first or the
> > driver. Perhaps someone can confirm which works best. {The norm is to
> > install the card then the driver [network cards/devices are sometimes the
> > opposite.] The only AWE64 that I installed were, IIRC, card first then
> > driver.}
>
> > 7.  Insert AWE64 PnP ISA card inside PC, then turn on PC.
>
> > 8.  At this stage, I believe that Windows 98SE will either not detect
> > the AWE64 ISA PnP card, or just install a "Motherboard Resources"
> > system device.  If I then run the hardware detection wizard, I believe
> > that Windows 98SE will either not detect the AWE card, or incorrectly
> > detect Joystick & Soundblaster 16/AWE32/Compatible.
>
> > 9.  If action number 8 above results in no successful AWE64 detection/
> > installation, should I then go ahead and try to manually install the
> > AWE driver using the "Add new hardware" wizard?
>
> > Please note - I am not sure if actions numbered 6 and 7 are the
> > correct actions to do.  Action 8 is not really an action, but what I
> > think might happen - and I could be wrong of course!
>
> > I am also unsure about two other actions -
>
> > Firstly, I do not know whether I need to connect to the internet to
> > update Windows 98SE.  (If this is required, I will need to install a
> > PCI-based Ethernet card.  I bought one recently, so this is OK, but I
> > would rather not do this now if it is not required.)
>
> > ** Gary Terhune [http://www.grystmill.com/] has two update CDs available..
> > One is the MS Security Updates circa 2004, and the second contains the
> > subsequent updates. Gary apparently includes some form of installation
> > routine to ensure they are installed in the proper order.
> > **OR download the updates from the catalog from the updates site and burn
> > them to CDROM [using the machine you are apparently using now] and install
> > them PRIOR to attempting the AWE install.
> > **The system should be updated prior to the AWE install, so if necessary
> > [check the installer date, it is likely well beyond SE RTM date] install
> > that netcard and update that way.
>
> > Secondly, I do not know whether I need to install the VIA 4-in-1
> > package.  If it is not required, then I would rather not install it
> > now.
>
> > *Install that ONLY if you find it necessary [you have SE], IF there are
> > issues, you MUST follow the previously posted routine to ensure it is
> > properly installed if you go that route.
>
> > Thanks a lot, all the best, Robert.
>
> > *Keep us informed....
>
> > --
> > MEBhttp://peoplescounsel.orgfree.com
> > --
> > _________- Hide quoted text -
>
> > - Show quoted text -
>
> Thanks very much for your continued assistance.
>
> Before I list the tasks which I have completed, you may be interested
> in my recent reply I gave to Franc Zabkar about my BIOS observations.
>
> Also, please note that I am currently experimenting with an AWE64 PnP
> ISA card model CT4520, which is a Value edition, but I am awaiting
> imminent delivery of a Gold edition, model CT4390.
>
> Currently completed tasks -
>
> 1.  Remove AWE64 card, leaving just 1 basic card inside PC = Matrox
> graphics card.
>
> 2.  Set BIOS OS PnP = Yes
>
> 3.  Reset the ESDI = Enabled.  Also disable BIOS anti-virus.
>
> 4.  Reformat HDD
>
> 5.  Reinstall Win 98SE
>
> 5A.  I have decided not to use the VIA 4-in-1 package at this moment
> in time.
>
> 5B.  Right at this very moment, I now need to install all updates to
> Windows 98SE before proceeding any further.  I need to obtain these
> updates.  I can either install a new ethernet card which I bought and
> connect to the internet, or I can await Gary's response about
> obtaining his Windows 98 update CDs - I emailed him this morning about
> this.
>
> Some questions please -
>
> A)  If I install a network card and attempt to connect to the
> internet, I must first obtain a Windows 98SE compatible firewall
> program to shut out the bad guys.  Any recommendations please?  I
> think this firewall program needs to be a complete downloadable
> program, rather than one which requires you to run it so it then
> connects to the internet and then downloads the rest of the package,
> because this might not be safe.  (Naturally I have another PC to do
> this, as I am using it right now to send these newsgroup messages.)
>
> B)  Let's say I have successfully and safely connected to the internet
> on the Windows 98SE PC -- in order to obtain the Windows 98SE updates,
> can I just simply use Microsoft's Windows Update service?  Please note
> - I would *much* rather have the updates on CD.  This is because I can
> reinstall Windows98SE very easily, without requiring a working
> internet connection.
>
> Many thanks for all your help, best regards, Robert.- Hide quoted text -
>
> - Show quoted text -

I'd just like to add to my post above, specifically this section -

5B. Right at this very moment, I now need to install all updates to
Windows 98SE before proceeding any further.

Gary has extremely kindly agreed to send me the Windows 98 update CDs,
even though my shipping address is international. Thanks very much
Gary. I would like to wait for these CDs to arrive before I proceed
any further.

Thanks, regards, Robert.
 
M

MEB

Okay, this comes as a response and correction pursuant this discussion and
the other related postings/discussions.

* As you indicate that you are obtaining the CDs from Gary, the issue of
updating becomes moot, as does installing and configuring a NIC. Also, that
gives us some time to pre-address some other issues. As you are not using an
old installation and trying to change previous errors [you're using new
installations] we can address the issues in a different form.

* As I indicated, I located my 9X SB 16/AWE driver file and cross-checked
via Creative's support, found it WAS the newest offering for 9X, and that it
should NOT require updating prior to installation. The previous statements
by myself per the need to update likely come from cross-linked XP/9X/other
SB devices, which being my memories, can not be noted then scandisked and
defragged [smile - in my mind] prior to an issue such as this.

That out of the way:
* The sb16AWE.inf included with 98SE is actually dated after the offering
from Creative. It does contain support for your AWE64.
It might be wise to use the configuration offered via this driver/INF
assembly rather than from any other. IF the card is not being automatically
installed/found, you should find an unknown or other device {!} listed in
Device Manager OR when running Find New Hardware. IF it is found or shown
via either method OR IF it does not display your AWE [perhaps as SB16}, then
choose Device Manager > {the found device} > Update Driver > Display List of
all """ > Show All Hardware, and scroll to Creative - choose the AWE64
driver that matches your card.
* IF you need information on what it will install {or has installed} then
open the INF [located in the {drive}:\{Windows folder}\INF]. In this INF you
will note the specific entries for the registry, and also the entries for
system.ini, win.ini, and autoexec.bat. These will provide you with the
ability to cross-check that these are properly setup and installed.

**IF* there are issues after ensuring the needed entries are actually
installed as they should be, OR the card itself is not being found, then it
may be that the connection fingers [in the slot] and/or stripes [on the
card] are NOT making proper connection. Clean these carefully, slots can be
cleaned with de-natured alcohol [making absolutely sure to completely dry
them afterwards AND that ALL electrical was discharged and disconnected
prior to the cleaning] and the card stripes can be cleaned with an pencil
erasure [making sure no residue remains]. Looking, however, at your posting
to Franc per the tests done, it appears this cleaning would not be
necessary. See next>

* There are other potential variables pursuant the motherboard and video
card which can be done as there is no present rush:
With *Plug and Play OS installed* enabled in the BIOS, also make sure the
BIOS has *Assign IRQ for Video* enabled {or other like description, also
pre-set any USB, printer, and other that you intend to connect PRIOR to the
original installation of the OS}.
* Did you post the model of the video card? Its a Matrox PCI but I don't
remember if you posted the actual model involved. Some cards require other
settings in the BIOS and/or driver to ensure they work properly.
* The driver for the Matrox video would need to be installed prior to other
device installations. Relying upon Windows default driver may cause system
conflicts. It would also help knowing the Matrox video driver version you
are using.
# Also:
* As we have a few days and this may also be relevant what is the
motherboard manufacturer and model we are dealing with?
*** Have you enabled or do you intend to use Power Management, ACPI, or
other [the final configuration of your intended setup], and how they are
presently configured?

* You asked if I could recommend a firewall. Presently I use Kerio PFW
version 2.1.5 , which for most 9X users and configurations would be
sufficient. It does require manual configuration as it is a rules based
firewall, though it will pop-up notices when encountering unknown issues and
ask what you want to occur when using the default setting. One rule which
should be manually made is for a Shawcable/communications block as that
*address range* seems to constantly popup when connected to the Internet.
The range is 24.64.0.0 through 24.71.255.255, place it as the first rule and
denied access to TCP and UDP. You will find others when they popup asking
what to do. Check the address when necessary using Who.is or another
registration checking tool. Your firewall can be one of the most important
tools/protections, so make sure you spend some time familiarizing yourself
with setup and configuration issues.
An older version of ZoneAlarm or other can be used, check for the versions
which supported 98. And there are several other firewalls which still
support 9X.

Also the "standards" for other web related issues relating to 9X include:

SpyWare Blaster {Java Cool}- ActiveX and web site protections {bad site
registry settings}

AVAST, Super Anti-Virus, or other anti-virus program. AVG will be ending
official support for 9X this year.

SpyBot Search and Destroy {Safer Networking}, or another SpyWare detection
application.

HiJackThis {Merjin Org}- no need to install unless there are reasons to
test, though installation brings no apparent system "hits".

Many [including myself] also use a HOSTS file to block other sites and
activities. You will find various HOSTS files on the Internet, I have tested
two, one from MDGx [which I presently use and add to] and the other from
MVPS. NOTE: using a HOSTS file may/will cause web pages to be shown
differently than you are familiar with, or may completely block access to
sites you frequent [sites previously determined and included in the HOSTS to
be hack sites, advertising, hijack/SpyWare sites, etc.].

And of course, setting up the browsers and email programs properly for JAVA
and scripting, plain text, and related. There are other
programs/applications you may like or want, including washing/cleaning
programs {like Windows Washer}, system protection programs {like WinPatrol},
and other. 9X can be made fairly secure, but it does require you make an
effort to do so.

Again, Sorry for my prior errors and/or mis-directions. Chalk it up to
getting old, too many OSs and other in mind [and resultant postings
elsewhere], personal web site issues, normal work routine, and in partial
legal mode [ugh]... too many non-related/conflicting things in mind at one
time.

--
MEB http://peoplescounsel.orgfree.com
--
_________
 
G

glee

You are creating your own problem. There is absolutely no problem with the entry for
the "IO read data port for ISA Plug and Play enumerator" showing the message that
"The resources this device is using do not match any of its known
configurations."

I have half a dozen Win 98 systems sitting in front of me with all different
motherboards, and they ALL show exactly the same on the Resources tab. This is
perfectly normal. That is not to say that there aren't some systems that will show
resource settings there on their own, with no conflicts, but none of the systems I
have worked on have them, and there is no problem with it.

You create a problem when you click the "Set Configuration Manually" button. It
will immediately show a resource conflict when you click the button, and you will
not be able to change the resources and have it stick. What will happen is that
upon rebooting you will have put the enumerator into a Forced Hardware
configuration, and it will likely show as such if you then run msinfo32 from
Start>Run.

This has been a known behaviour in Win9x for years. Do NOT try to set the resources
manually for that enumerator. Do NOT click the "Set Configuration Manually" button.

If you can clear the forced hardware, revert the configuration back to its original
setting where it stated "The resources this device is using do not match any of its
known configurations," your PnP may work correctly again. If you can't, and if
deleting the enumerator from Device Manager in SAFE MODE, along with all duplicate
entries in Device Manager and all entries in the "Other" category in SAFE MODE, does
NOT allow it to be redetected, then you may have to wipe out the installation and
reload Windows....and this time do NOT mess with the resource settings for the read
data port for ISA PnP enumerator.

Whatever your problem is loading drivers for your sound card or whatever it was you
were having trouble with, it is NOT related to the original setting for this
enumerator.
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:caf57fbe-ed3f-4d2a-b3b6-999b94ff1f4e@d45g2000hsc.googlegroups.com...

I think it would be helpful if I explained exactly what I see inside
Device Manager for the "IO read data port for ISA Plug and Play
enumerator" system device.

Inside Device Manager, I click on this "PnP enumerator" system entry
to view its properties. It then tells me that "This device is working
properly". I then click on the "Resources" tab. It tells me -

"The resources this device is using do not match any of its known
configurations. To assign resources manually for this device, click
Set Configuration Manually."

I then click on the Set Configuration Manually button, and it is then
that I see the conflict. There are 4 resource type entries - the
second entry has a conflict. The conflicting device list tells me
that Secondary IDE controller (dual fifo) and also VIA Bus Master PCI
IDE Controller are the conflicting devices for the Input/Output Range
of 0374-0377.

Please note that I have tried to do various actions here. I have
tried using Basic Configuration setting 0001. I have also tried to
change the conflicting 0374-0377 resource setting entry to a different
value entry so that there is no conflict - for example change to
03FC-03FF. Both of these actions do not appear to remedy the conflict
because if I do either of these changes, and then reboot, the resource
conflict problem simply reappears. In other words, my changes do not
appear to be "saved".
 
R

rpgs rock dvds

On 20 Apr, 21:38, "MEB" <meb@not h...@hotmail.com> wrote:
>  Okay, this comes as a response and correction pursuant this discussion and
> the other related postings/discussions.
>
> * As you indicate that you are obtaining the CDs from Gary, the issue of
> updating becomes moot, as does installing and configuring a NIC. Also, that
> gives us some time to pre-address some other issues. As you are not using an
> old installation and trying to change previous errors [you're using new
> installations] we can address the issues in a different form.
>
> * As I indicated, I located my 9X SB 16/AWE driver file and cross-checked
> via Creative's support, found it WAS the newest offering for 9X, and that it
> should NOT require updating prior to installation. The previous statements
> by myself per the need to update likely come from cross-linked XP/9X/other
> SB devices, which being my memories, can not be noted then scandisked and
> defragged [smile - in my mind] prior to an issue such as this.
>
>  That out of the way:
> *  The sb16AWE.inf included with 98SE is actually dated after the offering
> from Creative. It does contain support for your AWE64.
>  It might be wise to use the configuration offered via this driver/INF
> assembly rather than from any other. IF the card is not being automatically
> installed/found, you should find an unknown or other device {!} listed in
> Device Manager OR when running Find New Hardware. IF it is found or shown
> via either method OR IF it does not display your AWE [perhaps as SB16}, then
> choose Device Manager > {the found device} > Update Driver > Display List of
> all """ > Show All Hardware, and scroll to Creative - choose the AWE64
> driver that matches your card.
> * IF you need information on what it will install {or has installed} then
> open the INF [located in the {drive}:\{Windows folder}\INF]. In this INF you
> will note the specific entries for the registry, and also the entries for
> system.ini, win.ini, and autoexec.bat. These will provide you with the
> ability to cross-check that these are properly setup and installed.
>
> **IF* there are issues after ensuring the needed entries are actually
> installed as they should be, OR the card itself is not being found, then it
> may be that the connection fingers [in the slot] and/or stripes [on the
> card] are NOT making proper connection. Clean these carefully, slots can be
> cleaned with de-natured alcohol [making absolutely sure to completely dry
> them afterwards AND that ALL electrical was discharged and disconnected
> prior to the cleaning] and the card stripes can be cleaned with an pencil
> erasure [making sure no residue remains]. Looking, however, at your posting
> to Franc per the tests done, it appears this cleaning would not be
> necessary. See next>
>
> * There are other potential variables pursuant the motherboard and video
> card which can be done as there is no present rush:
>  With *Plug and Play OS installed* enabled in the BIOS, also make sure the
> BIOS has *Assign IRQ for Video*  enabled {or other like description, also
> pre-set any USB, printer, and other that you intend to connect PRIOR to the
> original installation of the OS}.
> * Did you post the model of the video card? Its a Matrox PCI but I don't
> remember if you posted the actual model involved. Some cards require other
> settings in the BIOS and/or driver to ensure they work properly.
> * The driver for the Matrox video would need to be installed prior to other
> device installations. Relying upon Windows default driver may cause system
> conflicts. It would also help knowing the Matrox video driver version you
> are using.
> # Also:
> * As we have a few days and this may also be relevant what is the
> motherboard manufacturer and model we are dealing with?
> *** Have you enabled or do you intend to use Power Management, ACPI, or
> other [the final configuration of your intended setup], and how they are
> presently configured?
>
> * You asked if I could recommend a firewall. Presently I use Kerio PFW
> version 2.1.5 , which for most 9X users and configurations would be
> sufficient. It does require manual configuration as it is a rules based
> firewall, though it will pop-up notices when encountering unknown issues and
> ask what you want to occur when using the default setting. One rule which
> should be manually made is for a Shawcable/communications block as that
> *address range* seems to constantly popup when connected to the Internet.
> The range is 24.64.0.0 through 24.71.255.255, place it as the first rule and
> denied access to TCP and UDP. You will find others when they popup asking
> what to do. Check the address when necessary using Who.is or another
> registration checking tool. Your firewall can be one of the most important
> tools/protections, so make sure you spend some time familiarizing yourself
> with setup and configuration issues.
>  An older version of ZoneAlarm or other can be used, check for the versions
> which supported 98. And there are several other firewalls which still
> support 9X.
>
>  Also the "standards" for other web related issues relating to 9X include:
>
> SpyWare Blaster {Java Cool}- ActiveX and web site protections {bad site
> registry settings}
>
> AVAST, Super Anti-Virus, or other anti-virus program. AVG will be ending
> official support for 9X this year.
>
> SpyBot Search and Destroy {Safer Networking}, or another SpyWare detection
> application.
>
> HiJackThis {Merjin Org}- no need to install unless there are reasons to
> test, though installation brings no apparent system "hits".
>
> Many [including myself] also use a HOSTS file to block other sites and
> activities. You will find various HOSTS files on the Internet, I have tested
> two, one from MDGx [which I presently use and add to] and the other from
> MVPS. NOTE: using a HOSTS file may/will cause web pages to be shown
> differently than you are familiar with, or may completely block access to
> sites you frequent [sites previously determined and included in the HOSTS to
> be hack sites, advertising, hijack/SpyWare sites, etc.].
>
> And of course, setting up the browsers and email programs properly for JAVA
> and scripting, plain text, and related. There are other
> programs/applications you may like or want, including washing/cleaning
> programs {like Windows Washer}, system protection programs {like WinPatrol},
> and other. 9X can be made fairly secure, but it does require you make an
> effort to do so.
>
> Again, Sorry for my prior errors and/or mis-directions. Chalk it up to
> getting old, too many OSs and other in mind [and resultant postings
> elsewhere], personal web site issues, normal work routine, and in partial
> legal mode [ugh]... too many non-related/conflicting things in mind at one
> time.
>
> --
> MEBhttp://peoplescounsel.orgfree.com
> --
> _________

Awesome info, thanks so much! I've been on the Win98 box for 14 hours
today, and I now need some rest. Tomorrow morning, I will carefully
go through all of your comments, and reply with some (hopefully!)
useful observations.

Thanks a lot, Best regards from Robert.
 
You must log in or register to reply here.

Similar threads

V
Speaker Not Working Since I Plug in Headphone
Replies
0
Views
22
Vishal69
V
V
Speaker Not Working Since I Plug in Headphone
Replies
0
Views
20
Vishal69
V
D
issues with xbox controller on pc
Replies
0
Views
34
Dorian Thomas1
D
D
issues with xbox controller on pc
Replies
0
Views
26
Dorian Thomas1
D
M
Plug n Play not working
Replies
0
Views
46
michaelhiltunen
M
Back
Top Bottom