| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1692.1 | | NETCAD::STEFANI | Welcome to the Revolution! | Fri May 19 1995 15:23 | 12 |
| We have a known problem with the DEFPA NDIS 2.01 drivers (both DOS and
OS/2) in which the IRQ *must* be on the secondary PIC. That is, you
should make sure the IRQ is set to 9, 10, 11, 12, 14, or 15. If the
IRQ is set on the primary PIC (eg. IRQ 5), the driver won't work
properly.
This problem is getting fixed, but for now, verify that the IRQ is on
the secondary PIC. Also, Microsoft fixed some PCI-related problems in
EMM386, so if you're using EMM386.EXE, make sure it's at v4.49 or
greater.
-Larry
|
| 1692.2 | IRQ and EMM checked | MUNICH::RADLER | | Mon May 22 1995 05:17 | 16 |
| .1
I used IRQ 9 on the Celebris and I tested IRQ 9 and 15 on my XL 566.
The EMM386 shipped with the lanmanager driver kit has never worked on my computers.
I always used the EMM386 from DOS 6.22 or no extended memory manager. But it doesn't
matter wheter or not EMM is used.
Which PCI-related problems do you mean? Where are the fixes for this problems?
I think my problem is only driver or MS-DOS related. I use the same adapter in the same
computer with Windows NT and I have a very good performance.
Are there some suggestions I can try? Perhaps do some older driver work?
Regards
Dieter
|
| 1692.3 | | NETCAD::STEFANI | Welcome to the Revolution! | Mon May 22 1995 13:48 | 28 |
| >>The EMM386 shipped with the lanmanager driver kit has never worked on
>>my computers. I always used the EMM386 from DOS 6.22 or no extended
>>memory manager. But it doesn't matter wheter or not EMM is used.
>>
>>Which PCI-related problems do you mean? Where are the fixes for this
>>problems?
I don't know what Microsoft fixed, but basically, if you're going to
use EMM386.EXE on a PCI system, make sure it's at v4.49 or later.
>>I think my problem is only driver or MS-DOS related. I use the same
>>adapter in the same computer with Windows NT and I have a very good
>>performance.
>>Are there some suggestions I can try? Perhaps do some older driver work?
There is no other driver for NDIS 2.01 on DEFPA. However, if it's
possible to use the DOS ODI client driver (DEFPA.COM), that's another
option. However, since the DOS ODI client driver supports FDDI
natively, I have some doubts that the LAN Manager protocol stacks will
support it properly.
We'll look into getting the DEFPA.DOS driver running under your version
of LAN manager. I don't know why it wouldn't work since the driver is
very close to the DEFEA.DOS driver and we don't have a similar problem
report issued against that driver.
/l
|
| 1692.4 | No emm v4.49 available | MUNICH::RADLER | | Tue May 23 1995 11:17 | 8 |
| I checked my EMM Version, it is v4.48.
But it is already DOS 6.22, where can I get a newer EMM386? I checked also Microsoft
Driver Library on the Technet CD, but nothing.
Could you provide this EMM386 version?
/Dieter
|
| 1692.5 | | NETCAD::STEFANI | Welcome to the Revolution! | Tue May 23 1995 12:17 | 13 |
| EMM386 is a Microsoft piece of SW. We simply can't send it to a
customer. It's possible that the MS-DOS 6.22 releases are different
from the US and Europe, but I hadn't heard before that this was the
case. You could try other Microsoft channels to get the version,
however, after speaking with another engineer about this, they believe
that the "bad" versions of EMM386 would cause the driver to hang upon
loading. This behavior hasn't been seen, correct?
It's quite possible that the client configuration is fine and that this
is a server configuration problem. What additional steps has the
customer done to isolate the problem?
/l
|
| 1692.6 | more information | MUNICH::RADLER | | Wed May 24 1995 14:05 | 24 |
| You are right, loading of the driver was only prevented by the EMM Version
provided on the DEFPA driver disk.
With the v4.48 of the german MS-DOS 6.22 there is no problem.
What have we done for troubleshooting?
- Using IRQ 9 and 15 on the XL 566 and Celebris
- Changing latency between 40h and 88h
- Using only minimal configured config.sys and autoexec.bat. That means
no use of drivers or tools except the neccessary for using the DEFPA
- Using Pathworks 5.1.008 Client Software (using NDIS)
- we tried only TCP/IP, that worked better (ftp->get: 120KB/s)
- we tried Pathworks with NEBEUI only -> same problem or low responce 5KB/s
....
regards
/Dieter
|