ISA Plug and Play not working (clean install)

[rpgs rock dvds]

On 20 Apr, 21:40, "glee" <gle...@spamindspring.com> wrote:
> 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

This is really excellent news! I will get my Win98 installation back
to the point where those resources are completely left alone and
untouched. (In fact, I'm happy to do a complete reinstall, it doesn't
take all that long, half an hour or so.) That's definitely something
less to worry about now. Thanks.

Best regards from Robert.

 

[glee]

"rpgs rock dvds" <rpgsrockdvds@hotmail.co.uk> wrote in message
news:1ae9934c-94bf-4aec-8515-2d4b41025e32@k37g2000hsf.googlegroups.com...
On 20 Apr, 21:40, "glee" <gle...@spamindspring.com> wrote:
>> 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
>
>This is really excellent news! I will get my Win98 installation back
>to the point where those resources are completely left alone and
>untouched. (In fact, I'm happy to do a complete reinstall, it doesn't
>take all that long, half an hour or so.) That's definitely something
>less to worry about now. Thanks.

Be sure as soon as you have completed the Win98SE installation and necessary
reboots, that you install the proper VIA 4-in-1 driver for the MVP Apollo Pro
chipset. VIA recommends that Win98/98SE users install the older 4.43 drivers for
the MVP#, Apollo Pro## series chipsets:
http://www.viaarena.com/default.aspx?PageID=420&OSID=6&CatID=1110

Here is the direct link to the driver package in zipped form:
http://www.viaarena.com/Driver/VIA_4in1_443v.zip

<quote>
To install the driver, save any unsaved work and close all applications then click
on the driver download link (above). Choose the "Save File" option and save it to
your folder under Windows where you file your drivers. Unzip the file. (To unzip the
file right click and highlight "Extract All") Then double click on the Setup.exe
file to run the installation program. Follow the prompts and restart at the end of
the installation.
</quote>
--
Glen Ventura, MS MVP Windows, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm

 

[Franc Zabkar]

On Sun, 20 Apr 2008 03:47:32 -0700 (PDT), rpgs rock dvds
<rpgsrockdvds@hotmail.co.uk> put finger to keyboard and composed:

>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.

I don't really understand these utilities any more than you do, but
neither utility sees my ISA PnP sound chip.

>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.

Same here. It seems that the PNPBTST utility looks for PnP ISA devices
but doesn't find our sound cards. The NVRAM utility does enumerate
yours, though. I don't have any problems at my end, so I assume this
behaviour is normal. At least it proves (?) that BIOS is finding all
your devices and all their resources, so I would think it must be a
Windows issue.

>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.

I don't have a Sound Blaster card but I get the following in a DOS box
(after I edit the PIF to prevent DOS applications from detecting
Windows).

===================================================================
D:\Software\Drivers\AWE>aweutil /?

AWEUTIL TSR Version 1.20
Copyright (c) Creative Technology Ltd, 1994-95. All rights reserved.

Usage: AWEUTIL [options]
Options: /U Unload
/S Initialize only
.................
/EM:MT32 Enable MIDI Emulation using MT32 Emulation
===================================================================

OTOH, if I type "aweutil" on its own, I get the same as you:

===================================================================
D:\Software\Drivers\AWE>aweutil

AWEUTIL TSR Version 1.20
Copyright (c) Creative Technology Ltd, 1994-95. All rights reserved.

ERR012: AWE32 initialization failed
===================================================================

It seems that your version of aweutil doesn't see "/?" as a help
switch.

This is the utility I used:
http://ccftp.creative.com/manualdn/Applications/Others/279/aweutl.exe

I found it here:
http://tinyurl.com/3hp99y
http://us.creative.com/support/down...1033&OS=15&DriverType=0&sOSName=DOS&details=1

Maybe you need to run the "Creative PnP Configuration Manager"
(ctcmbbs.exe) to setup the card's resources before aweutil (and DOS)
can see it. It shouldn't be required for Win9x, though.

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

 

[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
> --
> _________

Hi! Please note the following information may be helpful -

My legacy Pentium 3 motherboard is:

QDI Advance 10T
Webpage = http://www.qdigrp.com/qdisite/eng/products/Advance10t.htm
Chipset = VIA VT82C694T North Bridge, VIA VT82C686B South Bridge
The main mobo manual says: VIA Apollo Pro 133T: VT82C694T + VT82C686B

When I boot-up, I see the following BIOS information -

Award Modular BIOS v6.00PG
Advance 10T BIOS V1.6SLCP Feb.01,2002

My graphics card is:

Matrox MGA Millennium,

From inside Device Manager, Driver file details shown are -

MGAPDX64.DRV (version 4.10.1682)
MGAPDX64.DRV (version 4.10.1689)

The Matrox card was automatically detected when Win98SE was
installed. It appears to be working fine. However, I do have several
other graphics cards at my disposal, if you feel that it would help to
remove the Matrox card --

I have another "basic" PCI card, S3 chip based.
I also have 3 more advanced APG cards (2 Radeon 9250's, and 1 nVidia
5200 FX).

To double-check and confirm your recommendations --

>> With *Plug and Play OS installed* enabled in the BIOS,

This is enabled. (Please note however, that I'd love to use the AWE64
in pure DOS mode as well as Windows.)

>> also make sure the BIOS has *Assign IRQ for Video* enabled {or other like description,

I have IRQ for VGA enabled.

>> also pre-set any USB, printer, and other that you intend to connect PRIOR to the
original installation of the OS}.

I have USB enabled inside BIOS. (And I've tested the USB ports with a
flashdrive, and it works great.)

I do not use Parallel port, so I disabled this in the BIOS. I also
disabled both serial ports as well. I also disabled onboard legacy
audio too.

>> Have you enabled or do you intend to use Power Management, ACPI

I have disabled this feature inside BIOS.

I also have the following BIOS features set to Disabled -

QDI BootEasy feature
ChipAwayVirus On Guard
HDD S.M.A.R.T Capability
USB Keyboard Support
OnChip Sound
OnChip Modem
Memory Parity/ECC Check
ACPI function

Please also note these settings -

Resources Controlled By = Auto(ESCD)
Assign IRQ for USB = Enabled

Thanks very much for the info regarding firewalls and other software -
I've copied-and-pasted all of this information to a text file for
later use.

Many thanks, Best regards from Robert.

 

[rpgs rock dvds]

On 20 Apr, 22:50, "glee" <gle...@spamindspring.com> wrote:
> "rpgs rock dvds" <rpgsrockd...@hotmail.co.uk> wrote in messagenews:1ae9934c-94bf-4aec-8515-2d4b41025e32@k37g2000hsf.googlegroups.com...
> On 20 Apr, 21:40, "glee" <gle...@spamindspring.com> wrote:
>
>
>
>
>
> >> 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
>
> >This is really excellent news!  I will get my Win98 installation back
> >to the point where those resources are completely left alone and
> >untouched.  (In fact, I'm happy to do a complete reinstall, it doesn't
> >take all that long, half an hour or so.)  That's definitely something
> >less to worry about now.  Thanks.
>
> Be sure as soon as you have completed the Win98SE installation and necessary
> reboots, that you install the proper VIA 4-in-1 driver for the MVP Apollo Pro
> chipset.  VIA recommends that Win98/98SE users install the older 4.43 drivers for
> the MVP#, Apollo Pro## series chipsets:http://www.viaarena.com/default.aspx?PageID=420&OSID=6&CatID=1110
>
> Here is the direct link to the driver package in zipped form:http://www.viaarena.com/Driver/VIA_4in1_443v.zip
>
> <quote>
> To install the driver, save any unsaved work and close all applications then click
> on the driver download link (above). Choose the "Save File" option and save it to
> your folder under Windows where you file your drivers. Unzip the file. (To unzip the
> file right click and highlight "Extract All") Then double click on the Setup.exe
> file to run the installation program. Follow the prompts and restart at the end of
> the installation.
> </quote>
> --
> Glen Ventura, MS MVP Windows, A+http://dts-l.net/http://dts-l.net/goodpost..htm- Hide quoted text -
>
> - Show quoted text -

Thanks very much for your help! Please note that the following is
just to get things clear in my own mind -

The QDI Advance 10T mobo manual says my chipset is -

VIA Apollo Pro 133T: VT82C694T + VT82C686B

Therefore, as you very clearly state in your earlier post to me, the
"4.43 download" must be the correct package for my mobo.

I'm going to start from scratch again (reformat,reinstall), then
install the above mentioned 4in1 package.

Many thanks, best regards, Robert.

 

[rpgs rock dvds]

On 21 Apr, 06:09, Franc Zabkar <fzab...@iinternode.on.net> wrote:
> On Sun, 20 Apr 2008 03:47:32 -0700 (PDT), rpgs rock dvds
> <rpgsrockd...@hotmail.co.uk> put finger to keyboard and composed:
>
>
>
>
>
> >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.
>
> I don't really understand these utilities any more than you do, but
> neither utility sees my ISA PnP sound chip.
>
> >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.
>
> Same here. It seems that the PNPBTST utility looks for PnP ISA devices
> but doesn't find our sound cards. The NVRAM utility does enumerate
> yours, though. I don't have any problems at my end, so I assume this
> behaviour is normal. At least it proves (?) that BIOS is finding all
> your devices and all their resources, so I would think it must be a
> Windows issue.
>
> >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.
>
> I don't have a Sound Blaster card but I get the following in a DOS box
> (after I edit the PIF to prevent DOS applications from detecting
> Windows).
>
> ===================================================================
> D:\Software\Drivers\AWE>aweutil /?
>
> AWEUTIL TSR   Version 1.20
> Copyright (c) Creative Technology Ltd, 1994-95. All rights reserved.
>
> Usage:     AWEUTIL [options]
> Options:   /U       Unload
>            /S       Initialize only
>            .................
>            /EM:MT32 Enable MIDI Emulation using MT32 Emulation
> ===================================================================
>
> OTOH, if I type "aweutil" on its own, I get the same as you:
>
> ===================================================================
> D:\Software\Drivers\AWE>aweutil
>
> AWEUTIL TSR   Version 1.20
> Copyright (c) Creative Technology Ltd, 1994-95. All rights reserved.
>
> ERR012:  AWE32 initialization failed
> ===================================================================
>
> It seems that your version of aweutil doesn't see "/?" as a help
> switch.
>
> This is the utility I used:http://ccftp.creative.com/manualdn/Applications/Others/279/aweutl.exe
>
> I found it here:http://tinyurl.com/3hp99yhttp://us.creative.com/support/downloads/download.asp?Product_ID=1849...
>
> Maybe you need to run the "Creative PnP Configuration Manager"
> (ctcmbbs.exe) to setup the card's resources before aweutil (and DOS)
> can see it. It shouldn't be required for Win9x, though.
>
> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.- Hide quoted text -
>
> - Show quoted text -

That webpage with all the AWE64 downloads was SOO useful, thanks very
much!!

I think you're absolutely right - I must first run "Creative PnP
Configuration Manager" (ctcmbbs.exe) to setup the card's resources
before aweutil (and DOS) can see it.

And my AWE64 gold just arrived this morning from the States, so there
just aren't enough hours in the day!! )

Thanks a lot, Best regards, Robert.

 

[rpgs rock dvds]

On 19 Apr, 14:54, rpgs rock dvds <rpgsrockd...@hotmail.co.uk> wrote:
> 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.

Problem solved! Please see this later-dated thread subject -

"Successful AWE64 ISA PnP installation!"

for details. (Basically, I think the ISA sound card may have been
faulty.)