nasa@attctc.DALLAS.TX.US (Daniel Poirot) (07/08/89)
-------------------------------------------------------------------------- I just ftped PC/IP off of husc6 and compiled it with MSC 5.1. I have a Western Digital wd8003 card and compiled the programs using that library with out any trouble. I want to use the software in a 16 MHz 386 clone that is running the 386-To-The-Max memory manager. Now the fun starts. I have not been able to get anything in the set of programs to work. I have used CUSTOM.EXE to modify NETDEV.SYS with what I think are the proper settings. The card is set for INT=2, no DMA, base address at 0x0c8000, and has I/O mapped at 0x280. When I tell CUSTOM.EXE to use shared memory starting at c8000, the 386-To-The- Max software reports a memory violation error. When I tell it shared memory starts at c800, nothing works either. I have set up an entry for a name server but the programs report that the name server times out. PING of a valid Internet address also times out. Any ideas? The blurb that accompanies the package suggests that it works with a Western Digital interface. I would be interested in any information available about setting up the package. I know my interface is working, because the NCSA telnet/ftp stuff works just fine. Thanks, Daniel Poirot nasa@attctc.dallas.tx.us Lockheed C87 phone 713/483-2426 2400 Nasa Rd. 1 phax 713/483-6120 Houston, TX 77536 "A mind is a terrible thing."
ddl@husc6.harvard.edu (Dan Lanciani) (07/09/89)
In article <8573@attctc.DALLAS.TX.US>, nasa@attctc.DALLAS.TX.US (Daniel Poirot) writes: | When I tell CUSTOM.EXE to use shared memory starting at c8000, the 386-To-The- | Max software reports a memory violation error. When I tell it shared memory | starts at c800, nothing works either. This seems to be a very popular promlem. You need to set the address to c8000000. Perhaps I should make the prompt more clear. Dan Lanciani ddl@harvard.*
nasa@attctc.DALLAS.TX.US (Daniel Poirot) (07/10/89)
In article <2189@husc6.harvard.edu> ddl@husc6.harvard.edu (Dan Lanciani) writes: >In article <8573@attctc.DALLAS.TX.US>, nasa@attctc.DALLAS.TX.US (Daniel Poirot) writes: >| When I tell CUSTOM.EXE to use shared memory starting at c8000, the 386-To-The >| Max software reports a memory violation error. When I tell it shared memory >| starts at c800, nothing works either. > > This seems to be a very popular promlem. You need to set the >address to c8000000. Perhaps I should make the prompt more clear. > > Dan Lanciani > ddl@harvard.* We got ourselves a WINNER. C8000000 is the answer the CUSTOM.EXE program was looking for. 386-To-The-Max seems to work fine with the software. I now have a different problem. I can get TN.EXE and LPR.EXE to work, but PING.EXE of any host times out. Also, the CUSTOM.EXE program will have nothing to do with any of the EXE files. It complains that they are out of date or some such nonsense. Are these programs supposed to be COM files? Thanks for all the help so far, Daniel Poirot nasa@killer.dallas.tx.us Lockheed C87 phone 713/483-2426 2400 Nasa Rd. 1 phax 713/483-6120 Houston, TX 77536 "A mind is a terrible thing."