🚀 go-pugleaf

In article <3gj4sn$648@destiny.itsnet.com>, rsi@itsnet.com (Steve Newell) says:

>I had a similar problem.  It was related to my NE2000 network card of all
>things.  It seems that my NIC was using IO address 0x300.  Apparently, one of
>the Warp device drivers is hardwired to use this address as well.  Any time I
>tried to run selective install, I either hung or trapped.  Solution was to
>rejumper the NIC to use a different IO address.

Hi Steve,

If one of the Warp drivers is tied somehow to 0x300, then there is going to be a problem
with the default installation of the Mitsumi FX-001D CD-ROM drive. I discovered that mine
was set at port 0x300 and, yes, I was having lots of  SYS3175 errors. After I read your
post, I moved the CD adapter to 0x340 - the other 'default' address noted in the Warp
users guide. Warp is considerably more stable now.

The question is: Should we (Warp newbies) assume that no hardware device should be
configured at 0x300? My experience would seem to indicate that 0x300 is used by
something in Warp, and certainly not any of my hardware adapters.

Comments?

- Jim