Installing ecs12 on a newly built system. basic dfi miniatx mb w/integrated via nic. ect. did a couple test installs w/ecs11 while waiting for 12. got everything working - nic, sound, usb, video - if a little cludgy. I had peer and tcpip working. now installed ecs12 on a clean partition and I cant even ping myself. it is like the stack has not been started. peer is dead as well. the nic driver loads and sees the chip, the nic talks to the router ( or seems to by the lights).
I open the tcpip configbook and I see the routes ect I put in, but netstat -r says ' no routes' . ping reports 'no route to host' even to localhost. when i boot w/ lan0 set to auto/dhcp and nothing plugged in i do NOT get an error - so either it thinks it is getting a tcpip address from an imaginary server, or tcpip is not running. maybe.
when i set it to manual still dead. for peer, the requester will not start errors out as 'network failed'
so i go back and reinstall ecs11 on a test partition cause it worked before, right? so there must be some problem with the ecs12 install.... ha ha, now the ecs11 install does the same thing... what the h*** .....?
did i blow the nic somehow?? but even with no nic i should be able to hit the loopback interface, right?
driver problem?? but i am using the same driver i used before, the one that nicpak recommends. local corruption of driver?? maybe, did fresh download and sneakernet over, still no go. at my wits end w/this.
done evrything I can think of to try, any fresh ideas, help out there???
ok so i did some digging and reading. for some reason setup.cmd was not running. when i run it I am able to ping localhost, so the loopback is now working. the issue seems to be some conflict that is preventing protocol.ini from properly binding to the nic. lantran.log says ' multiple adapters trying to use same interupt..' but i have only the one adapter and driver installed... hhhmmmmmm
any more ideas?