There is WIFI drivers available,but they are often made for a specific
wireless card.Your best bet is to make a driver that can interpret ethernet
signals.Since information is coming from the internet to the ethernet
cables,you can get information/data from the internet using a parallel port
driver.This may help.
-Jayden
On Sun, May 17, 2015 at 1:03 AM, Steve Nickolas <[email protected]> wrote:
> On Sat, 16 May 2015, Louis Santillan wrote:
>
> > On Sat, May 16, 2015 at 7:44 PM, JK Benedict <[email protected]>
> wrote:
> > [SNIP]
> >> - Base resources, such as file system options/changes
> >> - Connectivity tools
> >> * Modernized web browser (I am working on one now - a text based
> >> prototype)
> >
> > There's Georg Potthast's Dillo port (in XFDOS [0]), and Arachne
> > (besides links or lynx), both leave a lot to be desired in a JS heavy
> > web. I personally think it could more productive to go after app
> > specific tools for Google [1], Facebook [2], Twitter [3], LinkedIn
> > [4], etc. For example, Facebook is entirely accessible over HTTP [5].
>
> I agree. An all-purpose browser needs code to handle a lot of corner case
> stuff, but a one-purpose browser only needs to be able to handle the
> specific case it was designed for. (But it may need to be able to update
> itself in case an update to the site breaks it.)
>
> I have considered writing such tools, but my head exploded at the idea of
> having to do so much string parsing in C, a language that really can't
> handle it well. To date the only apps I managed to complete were rdate
> and airc (both using wattcp), and the source code to the former is now
> lost.
>
> (Keep in mind my target system was a VERY low resource environment, such
> as the 5160 I still have in my closet.)
>
> >> - LapLink is still purchase-ware
> >> * Has a specific protocol via LPT ports, etc
> >> * PPP/PPPD in linux is open source... possible use of that?
> >> * If not... let's write fdlink :)
> >
> > David Dunfield has LAPTALK, DDLINK & RDC [6]. If LAPTALK (source in
> > MC323EXA) isn't sufficient, maybe he'd be willing to open source
> > DDLINK and/or RDC?
>
> I almost would want to suggest that a FreeDOS app for this purpose mimic
> INTERLNK/INTERSVR, since that was such a tool actually included in PC DOS
> 5.02 and later, and MS-DOS 6.0 and later. (Some old-timers here might
> know I'm a little too familiar with MS and PC DOS and what each version
> comes with. :P That's actually why I no longer actively contribute.)
>
> As for PPP, you already have LSPPP as a GPL'd option. If it works, and I
> believe it does implement the Crynwr packet driver interface most TCP apps
> for DOS require, there's no need to reinvent the wheel.
>
> http://ladsoft.tripod.com/lsppp.html
>
> -uso.
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Freedos-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
