The wiki article is good as far as it goes, I collected all the pieces of
the networking puzzle mentioned in the article, but can't seem to assemble
them correctly. My currebn method of file transfer is via USB, and I am
experiencing quite a bit of data corruption.
I have 3 desktops (one full time FreeDOS) and one other connection
available for my laptop PCMCIA. All machines are connected and setup
individually, but I am lost on the final client/host configuration.
On Mon, May 18, 2015 at 5:28 AM, Mateusz Viste <mate...@viste.fr> wrote:
> About networking -- have you looked at the wiki article?
>
> http://www.freedos.org/wiki/index.php/Networking_FreeDOS
>
> It contains already quite a lot of informations, on many aspects of the
> DOS networking world.
>
> Mateusz
>
>
>
>
> On 18/05/2015 10:52, Don Flowers wrote:
> > I have a HP Elite 8000 with 12gb RAM, I use XOSL to boot Kubuntu 14.04,
> > Windows 7, Compaq DOS 5.0, MS-DOS 7.10 and FreeDOS. When running Compaq
> > DOS and/or MS-DOS 7.10, I use the native HIMEM and Windows 3.1 runs fine
> > in enhanced mode; on FreeDOS even standard mode seems buggy, so it is
> > not necessarily a RAM issue but seems to be (IMHO) some kind of kernel
> > incompatibility.
> >
> > As for Wi-Fi, I got it to work on a Compaq Armada 1750 using a Proxim
> > (Orinoco Gold 802.11b PCMCIA card (using WPA), but when we switched to
> > Xfinity service the WPA setup was not compatible with our other wireless
> > devices.
> >
> > I personally would like to see an updated step-by-step how to on a wired
> > home network setup for FreeDOS.
> >
> > On Mon, May 18, 2015 at 4:25 AM, Rugxulo <rugx...@gmail.com
> > <mailto:rugx...@gmail.com>> wrote:
> >
> > Hi,
> >
> > On Mon, May 18, 2015 at 2:16 AM, Guillem <guilevi2...@gmail.com
> > <mailto:guilevi2...@gmail.com>> wrote:
> > >
> > > I've been thinking of dualbooting my Windows PC with FreeDOS,
> >
> > Why exactly? Although it's not a totally horrible idea, it's very
> > tedious and a bit technical. Not worth risking anything important. As
> > I told one guy recently, make sure you backup all important files
> > first, and even then, only if you have all your Windows DVD recovery
> > discs (and product key) nearby.
> >
> > What Windows do you run? WinXP? Win7? With the former, do you run it
> > atop pre-existing FAT or (incompatible) NTFS? I'm not even sure you
> > can (properly) resize NTFS at all before Vista (without Linux GParted
> > or whatever). Also, Vista on up upgraded the boot loader, so it's
> more
> > complicated to adjust, hence probably needing third-party EasyBCD.
> >
> > Native is fun, fast, (sometimes) less buggy, and runs DOS as
> > originally designed. But these days we also have great alternatives
> > like DOSEMU or VirtualBox or QEMU. These emulations are much easier
> to
> > use and less error-prone, albeit no one solution is 100% perfect (not
> > even native). If your cpu supports VT-X, you'll probably benefit
> > greatly from using that (e.g. VBox or KVM or similar) instead of raw
> > booting, esp. for better accuracy and speed.
> >
> > The simplest solution (if your PC can boot from USB) is to use RUFUS
> > to make a bootable jump drive. Heck, you could also use various tools
> > to make a bootable Linux (presumably with DOSEMU). Even if you're
> > using an old Pentium 4 (like my old one), you can still boot USB via
> > PLoP Boot Manager via floppy (or CD or HD).
> >
> > > and the only things that are preventing me from doing that right
> now are the fact that USB serial controllers don't work all the way
> >
> > At best, you're probably just going to have the BIOS detect a USB
> jump
> > drive as a fixed disk that can't be unplugged/removed (without
> > rebooting). Bret Johnson did write some nice UHCI-only drivers, but a
> > lot of machines don't support that, unfortunately.
> >
> > > and also that there's apparently no way to use applications that
> require a sound blaster reliably. Is there any way to make some kind of
> driver
> > > that would sit between the application and the actual soundcard
> (in my case a realtek) and forward what the app is trying to send to the
> > > soundblaster to the realtek the right way?
> >
> > Although it's not native and isn't even a real DOS (no actual FreeDOS
> > being used), the (portable, SDL-based) DOSBox emulator supports a lot
> > of graphics and soundcards, mostly for old commercial games. But
> > you'll need a different host OS for it. (Linux? FreeBSD? Kolibri?)
> > Believe it or not, this is better than even XP's NTVDM for many (but
> > not all) games.
> >
> > > I'm talking from a user's point of view here. I have never tried
> developing anything for DOS so I really don't know about the limitations.
> >
> > In native DOS? Not sure, not many have tried. Most of us aren't savvy
> > enough to do something so extremely technical. I mean, one guy did
> > port SoftMPU (MPU-401 TSR emulator) to DOS, but even that is loosely
> > based upon DOSBox! :-)
> >
> > Like mentioned, there really needed to be a universal API for that
> > (and some did exist), but it was never popular enough for many to
> care
> > hard enough to utilize or fix it. So we have some libs, but nothing
> > universally useful. Also, lots of old games are hard to find, but
> they
> > sometimes do support multiple outputs, even PC speaker. Although even
> > that isn't always physically available, but it's often better than
> > nothing!
> >
> > > Also would FreeDOS actually run on a PC with 8gb of RAM? That's
> what this one has, but after the previous message in this topic I'm not so
> sure.
> >
> > I run it just fine on my 6 GB Lenovo desktop. Of course, due to
> memory
> > holes, I "only" get (roughly) 2.9 GB free, but even that is "too
> much"
> > for some rare software (chokes, dies). But most well-behaved apps
> > (e.g. DJGPP) either work by default or can be massaged.
> >
> > Not sure how well it will work if you're running UEFI (CSM?).
> >
> > > I guess I would also have to figure out networking. I have no way
> of using Ethernet because of how this house is set up.
> > > I can either use Wifi or use my phone with USB tethering, which is
> what I normally do because that PC's network card doesn't work all the way.
> >
> > This alone is probably the biggest advantage of emulators (e.g. VBox
> > or QEMU, both of which I've used lately): easy to setup networking.
> > You know by default that it will work, unlike native, where you can't
> > be sure of anything!
> >
> > Granted, you mentioned Windows, but it's exactly Windows that doesn't
> > support DOS well anymore (if at all). So while it seems crazy to use
> a
> > software-only x86 emulator atop Windows on x86, sometimes it really
> is
> > better than nothing.
> >
> > In short: it depends on what you're trying to do, and whether you can
> > debug your own problems.
> >
>
>
>
>
> ------------------------------------------------------------------------------
> 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-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
------------------------------------------------------------------------------
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-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
