First post, by zerker
- Rank
- Member
Hello folks. So I recently caved in thanks to an LGR video and bought a Unisys CWD4002-ZE. It's arrived and I've got DOS and a few other things on it, but I'm having trouble getting the network interface going. I've read it has an NE2000-compatible network interface, so I downloaded the driver package from Gammy's github page and ferried it over to the machine with floppies. I already had mTCP configured on my other retro PC, so I opted to copy that particular copy instead of the one from Github (saves me re-entering IRC info and stuff).
Here are my (still bare bones) autoexec.bat and config.sys files:
autoexec.bat
@ECHO OFFPROMPT $p$gPATH C:\DOSSET TEMP=C:\TEMPSET MTCPCFG=C:\Apps\mtcp\network.cfgC:\Drivers\Network\pktdrv\ne2000.com -i 0x60 9 0x300 > c:\log.txtC:\Apps\mtcp\dhcp >> c:\log.txt
config.sys
DEVICE=C:\DOS\SETVER.EXEDEVICE=C:\DOS\HIMEM.SYSDOS=HIGHFILES=30
But here's what actually happens:
Packet driver for NE2000, version 11.4.3Packet driver skeleton copyright 1988-93, Crynwr Software.This program is freely copyable; source must be available; NO WARRANTY.See the file COPYING.DOC for details; send FAX to +1-315-268-9201 for a copy.System: [345]86 processor, ISA bus, Two 8259sPacket driver software interrupt is 0x60 (96)Interrupt number 0x9 (9)I/O port 0x300 (768)My Ethernet address is 00:00:E8:CD:B5:BFmTCP DHCP Client by M Brutman (mbbrutman@gmail.com) (C)opyright 2008-2015Version: Jul 5 2015Timeout per request: 10 seconds, Retry attempts: 3Sending DHCP requests, Press [ESC] to abort.DHCP request sent, attempt 1: TimeoutDHCP request sent, attempt 2: TimeoutDHCP request sent, attempt 3: TimeoutError: Your DHCP server never responded and no packets were seen on the wire.Check your cabling and packet driver settings.
I used the wonderful 'HWiNFO tool, version 5.5.5 to see if I could confirm resource usage. It SAYS it seems an NE2000 compatible interface at address 300 on the ISA bus. IRQ 9 just says "Rerouted IRQ2" where IRQ2 says "Slave 8259 Interrupt Controller", so it seems correct, no?
I opened up the case to see if I could see anything, and uploaded a pile of pictures. But aside from downclocking to 50 MHz (for eventual better Ultima 7 speed), I didn't find anything that would help me isolate what might be happening.
Any thoughts?
Just to be clear, with the same router, same network cable and same mtCP settings (but different packet driver), my other retro machine has no problems getting an IP address via the mTCP DHCP tool.
