Hello,
Just got lynx running under freedos. I wanted to thank everyone for the help.
I ran dhcp through mTCP and then edited wattcp.cfg manually. I guess now I
should try and automate some stuff. I wonder why I can't get Ntool to work? I
think It would be easier to automate stuff if I got Ntool to work.
I have a question about lynx I went to YouTube.com and was going to search for
a video and lynx asked me to download an application. Just wondering if it is
safe to download the application? And will lynx need software to run, like will
a lot of sites want me to download applications and software?
Also I wonder are there limitations to lynx running in freedos. Like I wonder
with YouTube how would dos play a video? Just curious, I think it is neat to
browse with lynx.
Anyway thanks again. And any added info or help would be great.
Sent from my iPhone
On Mar 19, 2011, at 8:27 PM, cordat...@aol.com wrote:
>
> I got Lynx 2.8.5 running on FreeDOS in Virtual Box on Windows. I was able to
> navigate to yahoo.com and some other spots.
>
> There are some "anomolies" in the way Lynx works compared to typical WATTCP
> programs.
>
> It looks like Lynx is using WATT-32 which makes sense in retrospect since
> Lynx is compiled with DJGPP.
>
> Apparently DHCP does not work right in this case. I detected that Lynx sends
> a DHCP request message immediately rather than the expected DHCP discover
> message (which if successful is then followed by DHCP request).
>
> Bottom line: Lynx does not work with DHCP. Someone would need to re-link
> with a later version of WATT-32 assuming that there exists a later version
> with DHCP working right.
>
> So the idea of using NTOOL is probably the right way to go here.
>
> Here is my WATTCP.CFG file:
>
> my_ip = 192.168.1.41 (assigned via DHCP, then manual edit file)
> nameserver = 8.8.8.8 (google public nameserver)
> gateway = 192.168.1.1 (my wireless router)
> netmask = 255.255.254.0
>
> You need to set up some environment variables.
> I put all the lynx files in a directory called c:\lynx.
>
> I then deleted the local WATTCP.CFG file since I already have one. Again the
> behavior is squirrely perhaps because it's using WATT-32.
>
> SET WATTCP.CFG = C:\
> SET HOME=C:\lynx
> SET LYNX_CFG=C:\lynx\lynx.cfg
>
> Put yourself into the directory c:\lynx, type lynx, things start working...
>
> I have VirtualBox set up as bridged mode so that the VM gets its own IP from
> the router. You could in theory
> also do NAT and share the host IP.
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
