If you're really concerned about a bunch of other parameters in WATTCP.CFG, the
more elegant solution (in my opinion of course) is this:
Do my original bat file.
At the end of the bat file put this:
echo include c:\otherwat.cfg wattcp.cfg
Keep all your other stuff in otherwat.cfg ...
Most
I suggest that somebody write a small program that takes the current
configuration parameters from the mTCP configuration file and updates a
WATTCP configuration file. It should not be a terribly complicated program -
you just have to do some light string processing.
Here' you go:
/*
For those who want a DIY conversion of MTCP DHCP to WATTCP, you can do this:
Step 1: Install minitrue on your PC. mt.exe ... google it. (I think it's
idiotsdelight.net or something)
Step 2: Create a batch file called M2WAT.BAT
Put this stuff in the batch file:
@echo off
rem convert MTCP
mTCP vs wattcp.cfg - I agree this would be awesome if mTCP could read/write
WatTCP config files for backward compatibility :)
Step 1: Install minitrue on your PC. mt.exe ... google it.
Step 2: Create a batch file called M2WAT.BAT
Put this stuff in the batch file:
@echo off
rem convert
My advice to anyone trying to use a USB storage device on FreeDOS is to first
try
using the BIOS.
First realize that USB drives will be FAT 16 for smaller devices (1G or less)
and FAT32 for
larger devices. So find a device which is small or make sure you are using
the FAT32 enabled
FreeDOS
Karen,
If by getting old hardware on the internet you mean successfully connecting
old hardware to the internet then you may be referring to Mike Brutman and his
networking package mTCP.
If on the other hand by getting old hardware on the internet you mean someone
who buys stuff from ebay or
is the WatTCP program doing something anti-social like calling exit and
killing the program outright?
WATTCP programs generally start by calling sock_init() Sock_init() will exit
the program if a packet driver is not found. If your program might have some
useful purpose without TCP/IP
George,
Where is the printer physically located? Is it an LPT port on the host PC? If
so why not configure
VMWare to use a physical LPT port?
Alternatively VMWare can be configured to send print information to a file
which you could
then send to a network printer from Windows.
Dave
Derp,
First, I suggest you put the text into your email that you want people to read
rather than making them click on a link - you will get more responses.
Second, I personally would recommend VMWare player in this case over Virtual
Box. Use the VMSMOUNT program by Eduardo Casino and you will
You don't say whether you want to run FreeDOS on the bare metal or in a VM.
My suggestion would be that if you already have Windows on your laptop it's
quite easy to
run FreeDOS in a VM, then you can connect the USB port using Windows and set it
up as
COMx inside the VM, then you don't need to
Hi Eric,
Note that this is probably not VM specific and wouldalso happen on real
hardware.
If I'm running DOS in a production environment on real hardware I (personally)
would make sure the hardware could handle it and not overheat. There are
plenty of industrial solutions out there that
Can you describe what exactly were the problems?
As for myself I've had no issues with getting FreeDOS to run in VMWare player,
QEMU and VitualBox. I used the original FreeDOS 1.0 install and have manually
updated the kernel since then. As for VirtualBox specifically, it will run a
VMDK file
Hi FD users,
I've seen some random comments about EMM386 allocating UMBs for its own use but
I have not been
able to locate the source code to check this out.
(Yes, I expect several comments deprecating EMM386 and directing me to JEMM386.)
When using EMS both EMM386 and JEMM386 will allocate a
Thanks for your note Bernd.Some good ideas I can try.
Dave
-Original Message-
From: Bernd Blaauw bbla...@home.nl
To: freedos-user freedos-user@lists.sourceforge.net
Sent: Wed, Jun 6, 2012 12:11 pm
Subject: Re: [Freedos-user] Any success stories with Kernel 2041, FAT32 and
DOSUSB?
I've tried the Panasonic driver, it hangs on my PC. Also tried DUSE, Iomega
and whatever else was on a
boot disk which someone put together. Didn't bother trying Bret's drivers
because I have EHCI / OHCI. Georg's DOSUSB is the only one that works for me to
some degree.
Just curious if
Hi Eric,
My MB has EHCI/USB 2.0 and OHCI/USB 1.1. My understanding was Bret's drivers
are strictly UHCI.
On most OHCI drivers (including DOSUSB), the driver will load but then the
keyboard starts acting erratically. (I'm using PS2 keyboard not USB)
Effectively the computer is not usable at
I've been trying to get USB working under FreeDOS ... My motherboard has EHCI
controller, the only driver which comes close to working is Georg Potthast's
DOSUSB. Currently the system crashes (messages about corrupt MCB) when I try
to access the USB disk.
Just curious if anyone has had
FreeDOS user,
Make sure that the NAMESERVER parameter is filled in your WATTCP file. This
parameter
should come back from the MTCP DHCP program and is probably going to be the
same as your
router IP address.
For fun you can try the IP address 8.8.8.8 as the NAMESERVER if you are unsure
on
FreeDOS User ...
If WATTCP is working correctly you don't need the other lines in your config
file beyond my_ip=dhcp as they are filled in if DHCP works. As has been
discussed here before some versions of WATTCP support DHCP and some don't. My
guess is that yours does support DHCP since if
Tomdean,
I think it should be clear now that it isn't very likely your wireless adapter
can
be directly controlled from DOS (Free or otherwise).
A workable solution would be to boot Windows or Linux on the PC in question and
use
their wireless card drivers, then boot FreeDOS in a virtual
tomdean,
Yes, you need a packet driver. However I'm not sure about running a wireless
card under DOS - packet
drivers are typically not capable of configuring wireless security. They
normally operate with a wired ethernet
port. Others will know more about this than I.
Is there a reason you
All this talk about UIDE prompted me to investigate this tool. It looks
interesting. How does the caching work for disk writes? I assume that when
the cache is full the next sector read in will cause the oldest sector to be
written out?
Is there any sort of a timer which will flush the cache
BTW, how did you detect what messages Lynx sent? neither
-trace nor -wdebug options seem to log protocol IDs.
I use wireshark packet sniffer and recommend it highly.
--
Enable your software for Intel(R)
Updates to what? I think I'm done with this at this point.
-Original Message-
From: Lee Eric openlinuxsou...@gmail.com
To: freedos-user freedos-user@lists.sourceforge.net
Sent: Mon, Mar 21, 2011 5:24 am
Subject: Re: [Freedos-user] Using mTCP DHCP with WATTCP applications
To those of you interested in using the mTCP DHCP client with WATTCP
applications that don't behave well with DHCP please do the following:
a) Find and download minitrue, the executable is MT.EXE. (maybe it's in
FreeDOS 1.0, who knows).
You can find at:
First, it was not necessary to re-install FreeDOS.
Lynx, Ntool, and all other WATTCP programs are applications, not part of the
operating system.
The only OS related thing to consider is whether the packet driver is loaded.
It sounds like now that your virtual machine settings may have changed
How do I load the packet driver manually? I have been running autoxec.bat via
reboot to load the packet driver.
You may need to step back and try reading up a little on DOS. If you don't
understand what a batch file
is or how to run commands from a given batch file manually you will find
Note that WATTCP applications will find this number out manually while mTCP
has to have the same number written
into its config file.
Note that manually should be automatically in the above.
-Original Message-
From: cordata02 cordat...@aol.com
To: freedos-user freedos-user
I downloaded VirtualBox and got FreeDOS running on it with networking (WATTCP
clients) using a Windows host. (Sorry, no macs here)
It looks like a correct packet driver is in fact PCNTPK.COM, so check if that
is in your autoexec.bat file.
I also tested and verified that it is possible to
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
As has been noted here in the past, WATTCP is technically not part of the
operating system,
it's a library that is linked in with the application program.
Wattcp *does* support DHCP and the line my_ip = DHCP should be all you need to
get DHCP running.
The key is that you need to make sure
The discussion about TUNZ got me thinking about the ARC file format.
There are several of the old shareware utilities out on the internet - ARCE,
ARC-E, PKXARC ..
but are there any available which are GPL or close to GPL? (For DOS, of
course!)
Poking around I noticed that Vernon Buerg passed
With all the discussion on mTCP it seems this package is getting a lot of
attention.
Is there any update as to when we might be able to get source or even just a
binary library?
-Original Message-
From: mbbrutman mbbrut...@brutman.com
To: freedos-user
Sorry to sound dense but how do you change the kernel from 16 to 32 bits?
Isn't there just one kernel and it works with a filesystem that is FAT16 or
FAT32? Or are these
kernels compiled with different memory models?
Dave
-Original Message-
From: Marcos Favero Florence de
Hi,
I searched the archives for the answer to this question but I couldn't find
much.
I'd like to be able to detect that the power button on the computer has been
pressed while running freedos.
(Also this would apply to the powerdown event from the QEMU emulator)
I know there is a power
Eric et al,
Thanks for your replies.??? The application is a very old network manager.
The obsolete communications device is a serial board.
It is not, however, a typical serial board.? The serial board performs certain
functions
of a proprietary protocol which is somewhat similar to frame
36 matches
Mail list logo
