n***@gmail.com
2011-03-12 22:35:46 UTC
I had to buy a Win 7 device in order to be able to access internet
without a fixed-line.
Although inet-access has been dumbed-down to http-clik&drool, I
was able under linux, to collect the URLs off-line and auto-fetch
and save all correponding pages to file, for later analysis off-line.
Ie. to avoid the mind-dumbing live-pictures in-your-face of
normal 'browsing', one can use eg. lynx, which is available for
all OSs from DOS, linux....W32.
It's been difficult getting W32lynx set up under Win7.
I run it under 'DOS' and the longFileNames vs 8.3-format is
confusing.
Since IMO there's nothing which can replace the ETHO
textEditing facilities, I regularly have multiple ETHOs running
under linux. So I also want these ETHO facilities on this Win7 PC.
Since I've previously used DOSbased ETHO, that's my natural
choice. But I've had 'out of memory' problems, initially on Win7,
when I tried to have a *.bat which would do:--
For each line/URL in a file
<path>\lynx.exe -dump >> AccumulatingFile
Apparently oo-memory is normally fixed by 'editing config.sys'.
But config.sys seemed to be read-only on this Win7-thing.
It seems natural to use 'WinbasedETHO'; but frankly, I don't want to
waste time familiarising with WinTel technology if the old familiar
DOSbased ETHO can do it.
What version of ETHO is easiest to get working under Win7?
Can WinETHO directly access the tcp/ip stack that some Win7
application already uses, to connect to a URL?
Eg. I believe that DOSbased ETHO had its own tcp/ip stack,
whereas Linux-ETHO uses the linux tcp/ip stack.
And the DOSbased ETHO useded a serial-port-modem,
like NativeOberon did; which won't connect to my USB
Win-driven wireless-modem.
TIA,
== Chris Glur.
without a fixed-line.
Although inet-access has been dumbed-down to http-clik&drool, I
was able under linux, to collect the URLs off-line and auto-fetch
and save all correponding pages to file, for later analysis off-line.
Ie. to avoid the mind-dumbing live-pictures in-your-face of
normal 'browsing', one can use eg. lynx, which is available for
all OSs from DOS, linux....W32.
It's been difficult getting W32lynx set up under Win7.
I run it under 'DOS' and the longFileNames vs 8.3-format is
confusing.
Since IMO there's nothing which can replace the ETHO
textEditing facilities, I regularly have multiple ETHOs running
under linux. So I also want these ETHO facilities on this Win7 PC.
Since I've previously used DOSbased ETHO, that's my natural
choice. But I've had 'out of memory' problems, initially on Win7,
when I tried to have a *.bat which would do:--
For each line/URL in a file
<path>\lynx.exe -dump >> AccumulatingFile
Apparently oo-memory is normally fixed by 'editing config.sys'.
But config.sys seemed to be read-only on this Win7-thing.
It seems natural to use 'WinbasedETHO'; but frankly, I don't want to
waste time familiarising with WinTel technology if the old familiar
DOSbased ETHO can do it.
What version of ETHO is easiest to get working under Win7?
Can WinETHO directly access the tcp/ip stack that some Win7
application already uses, to connect to a URL?
Eg. I believe that DOSbased ETHO had its own tcp/ip stack,
whereas Linux-ETHO uses the linux tcp/ip stack.
And the DOSbased ETHO useded a serial-port-modem,
like NativeOberon did; which won't connect to my USB
Win-driven wireless-modem.
TIA,
== Chris Glur.