DOS ain't dead - DHCP / Watt / WATTCP.CFG / WSTEST / OWB / MPXPLAY FTP / D&A

DOS386

24.05.2010, 07:22

DHCP / Watt / WATTCP.CFG / WSTEST / OWB / MPXPLAY FTP / D&A (Users)

Watt has a new page: http://home.broadpark.no/~gvanem/ (was "www.bgnett.no/~giva" ) :-|

regrettably it doesn't work that well ...

[image]

That's what WSTEST.EXE brews if it works (address is $FFFF'FFFF - valid ??? redirect not found ...). But in some cases it hangs instead with DHCP waiting (gives up too late or not at all).

Same for OWB - sometimes it works and sometimes not. BTW, OWB can process the JavaScript on RapidSh** - the "countdown" runs to ZERO and then the big download button comes up. Regrettably clicking it has no effect (and OWB can't download from reasonable servers either ... :-( ).

MPXPLAY is worse ... with 1.57b4 it always hangs, if it gets aborted, it "returns to DOS", but MPXPLAY screen is still on and the keyboard is disabled - not even CTL-ALT-DEL works :-( So, I was not able to test the FTP fixes ...

Oddly, I never have such problems with Arachne nor DOSLynx, they always work (if DOSLYNX.CFG is correct).

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Berlin, Germany,
24.05.2010, 14:42

@ DOS386

DHCP / Watt / WATTCP.CFG / WSTEST / OWB / MPXPLAY FTP / D&A

Post reply

> Watt has a new page: http://home.broadpark.no/~gvanem/ (was
> "www.bgnett.no/~giva" ) :-|

Thanks! I've updated my Links page.

---
Forum admin

Mpxplay

26.05.2010, 12:23
(edited by Mpxplay, 26.05.2010, 12:43)

@ DOS386

DHCP / Watt / WATTCP.CFG / WSTEST / OWB / MPXPLAY FTP / D&A

Post reply

> MPXPLAY is worse ... with 1.57b4 it always hangs, if it gets aborted, it
> "returns to DOS", but MPXPLAY screen is still on and the keyboard is
> disabled -
> not even CTL-ALT-DEL works :-( So, I was not able to test the FTP fixes
> ...
>
> Oddly, I never have such problems with Arachne nor DOSLynx, they always
> work (if DOSLYNX.CFG is correct).

Yeah, I did want to say, that it's rather a WATTCP bug, not Mpxplay.
WATTCP was good for me, because it's 95% Win32 (BSD?) compatible, so I could easily make the DOS port of my ftp-client. But it seems it doesn't work...
Currently I have no time to write a completely different DOS/TCPIP handling for Mpxplay, and I also have no testing environment for the develop...

Ideas:
1. Try -bn8 option at Mpxplay
2. It seems the HX extender also uses WATTCP (it has wattcp.cfg).
Do you have success with a win32 ftp program under HX?
If yes, did you try the wattcp.cfg file of HX for Mpxplay?

btw. at tcp initialization, HX and Mpxplay also call only a sock_init() function from wattcp (Mpxplay and other programs hang here), nothing to correct on our side...