Zbigniew B. wrote:
> I want to replace a DOS installation on quite old computer - it is
> 386SX25 - which I'm keeping around just because it's s.c. "booksize
> PC". It has no ACPI, not even APM. I understand, that the FDAPM is
> most recommended method, but - from the other side - using this very
2011/3/13, Robert Riebisch:
> It's very unlikely that a 386SX will overheat ever.
Yes, I'm aware, that it probably won't overheat - still: by keeping
CPU cool, we'll let it live longer. If it breaks - no chance to
replace.
I can recall similar problem many years ago, with broken 286/12 (not
sure,
On Sunday 13 of March 2011 at 10:20:51, Robert Riebisch wrote:
> It's very unlikely that a 386SX will overheat ever. No need to play
> around with IDLEHALT or FDAPM.
Maybe. But it's still nice to lower the temperature of the chip, to make it
last longer, and not warm up components that are around
Hi!
>> Yes! The good news is that newer FreeDOS kernels even have a simple
>> version built into the kernel itself. [..]
>
> Good news! Well, I should have googling for "FreeDOS idle CPU",
> instead of "DOS idle CPU". ;)
:-)
>> However, the normal way to let the CPU idle while DOS is idle is
2011/3/13, Mateusz Viste:
> Maybe. But it's still nice to lower the temperature of the chip, to make it
> last longer, and not warm up components that are around it. Plus, it's
> always
> a little more electricity saved. Running FDAPM costs nothing, and provides
> cool advantages. There's no reaso
Any update here?
Eric
On Sat, Mar 12, 2011 at 11:40 PM, Lee Eric wrote:
> Hi,
>
> I installed FreeDOS with wattcp and FreeDOS has recognized the
> ethernet interface in the system. However, how can I get DHCP IP from
> the server? Here's C:\AUTOEXEC.BAT file content.
>
>
> @echo off
> SET dosdir
Thanks mates.
Eric
On Sun, Mar 13, 2011 at 4:41 AM, Michael B. Brutman
wrote:
>
> I had seen the original suggestion to use CTTY to redirect the console
> to a serial port but
>
> I had seen the original question on how to redirect DOS to use the
> serial port and I probably should have chipped
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 t
I've found that the usefulness of CTTY is usually limited to batch files where
I want to hide the annoying output of some programs as they are loading:
CTTY NUL
{load things here that I don't want to see the output of}
CTTY CON
Make sure you don't forget the CTTY CON at the end, or you won
hello,
I have freedos running in virtualbox on my laptop. I am trying to set up lynx
which came with freedos.
I could use some help. when I first tried to run the lynx exe file I got an
error saying that c:\fdos\temp directory doesn't exist.
I was told by a member of the mailing list, that I
cordat...@aol.com wrote:
> An alternative is to use Mike Brutman's mTCP DHCP program.
This is of course true, but there is another alternative . . .
> So to sum up: if your application program uses the right
> version of WATTCP then you don't need to do anything,
> run the program and it w
The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file,
which is pointed to by an environment variable. It's a simple matter of
programming/scripting to convert the output from either one into
something that looks like a static WATTCP configuration. I've tested my
DHCP client f
In reply to my suggestions, Jim Collins wrote:
>> set HOME=.
>> set wattcp.cfg=%HOME%
>> set wattcp_cfg=.\
>> with an underdash, not a dot.
> I edited lynxbat.bat to have the underscore with no luck
Did you try
set HOME=.\
set wattcp_cfg=%HOME%
I am not sure whether "." only shall wo
13 matches
Mail list logo
