Thanks mate. It works well.
Eric
On Sat, Mar 12, 2011 at 2:45 AM, Mark Blain wrote:
> Lee Eric wrote in
> news:AANLkTik0R8PLJF5szh9Hfd9mZGqqL5sjeq0GH_=u8...@mail.gmail.com:
>
>> Dose FreeDOS support serial console device? Could I redirect the
>> contents to a serial console device like Linux? I
Sent from my iPhone
On Mar 11, 2011, at 9:54 PM, "Jose Antonio Senna"
wrote:
> James Collins said:
>
>> I looked at lynxbat.bat and the batch files says:
>> set HOME=.
>> set wattcp.cfg=%HOME%
>> so is the batch file expecting to find wattcp.cfg
>> in the current directory?
> It is telling
BTW, if I wanna return to normal back. How do I do? My cmdline is
ctty aux
And furthermore, I notice that VIM cannot work properly under console
mode, the contents will be shown on the screen not the console.
Thanks.
Eric
On Sat, 2011-03-12 at 22:42 +0800, Lee Eric wrote:
> Thanks mate. It works
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=C:\FDOS
REM C:\FDOS\BIN\BANNER2
REM C:\FDOS\BIN\BLACKOUT
set PATH=%dosdir%\bin
set NLSPAT
Hui Li wrote in
news:1299943360.7385.4.ca...@dhcp-14-156.nay.redhat.com:
> BTW, if I wanna return to normal back. How do I do? My cmdline is
> ctty aux
> And furthermore, I notice that VIM cannot work properly under console
> mode, the contents will be shown on the screen not the console.
CTTY
I read, that the source of CPU (over)heating problems under original
MS/PC-DOS was the fact, that its "waiting for key"-loop (or however it
is called) didn't set CPU idle, when user (or application) was idle.
For example: when the computer has been left with the cursor blinking
in the command line.
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 in then, but now you know
the limitations of CTTY.
CTTY to a serial port only works for
Hi!
On 12.03.2011 21:44, Zbigniew B. wrote:
> I read, that the source of CPU (over)heating problems under original
> MS/PC-DOS was the fact, that its "waiting for key"-loop (or however it
> is called) didn't set CPU idle, when user (or application) was idle.
You need a driver for that, it is not
2011/3/12, Eric Auer:
>> I'm wondering, whether this misfeature has been fixed in FreeDOS?
>
> 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"
