Re: [Freedos-user] Lynx issues
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. Could you be more specific? Or just re-rerad the various posting refering to that subjects during the last days. ___ WEB.DE DSL Doppel-Flat ab 19,99 euro;/mtl.! Jetzt mit gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2 -- 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
Re: [Freedos-user] Lynx issues
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. I can't get dhcp in Ntool to work? Why come I can get dhcp in mTCP to work but not Ntool? 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
Re: [Freedos-user] Lynx issues
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
Re: [Freedos-user] Lynx issues
Hi :-) Hello, Just got lynx running under freedos. I wanted to thank everyone for the help. Nice! Actually, why Lynx? Arachne would be graphical... 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. Interesting question indeed. 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. That probably is Flash. There is no official Flash for DOS, but it might be possible to port the open source clone GNASH to DOS. Just wondering if it is safe to download the application? Yes but it would not run. And will lynx need software to run, like will a lot of sites want me to download applications and software? As far as I remember, many modern formats are not supported depending on which DOS browser you use. For example CSS, new HTML 4 / 5 features and JavaScript. Even HTTPS / SSL is not always supported in DOS web browsers. I guess others on this list can give you more details about which browser has what. I wonder with YouTube how would dos play a video? Youtube uses Flash FLV and MPEG4 MP4 videos as far as I know and you should be able to play those with MPXPLAY for DOS or maybe with a port of MPLAYER, the latter maybe supported by the HX or HXRT DOS extender. However, only a limited set of AC97 and HDA sound chips is supported, so I am curious which chip you have (or simulate, if you use a virtual PC) and if some media players for DOS support it. As for the virtual PC topic - of course it is easier to use VLC / MPLAYER / Media Player Classic in your host system (MacOS, Linux, Win) then. Cheers, Eric -- 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
[Freedos-user] Lynx issues
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
