> On Jul 20, 2016, at 10:24 AM, Rugxulo <rugx...@gmail.com> wrote:
>
> Hi,
>
> On Wed, Jul 20, 2016 at 6:01 AM, Eric Auer <e.a...@jpberlin.de> wrote:
>>
>>> I just downloaded the bootable FD 1.2pre22 CD and booted a VM in
>>> VirtualBox. I see `FDAPM APMDOS` in autoexec.bat. No IDLEHALT in
>>> FDCONFIG.SYS. CPU also spikes to 100% when I run `edit autoexec.bat`.
>>
>> I remember that this is a problem with certain EDIT versions. Of
>> course IDLEHALT is nice, but FDAPM APMDOS should be okay as well.
>>
>> Here is what for example EDIT 0.7c did in DFLAT's dispatch_message:
>> ...
>> Please check the sources or ask Aitor Santamaria and Joe Cosentino.
>> Maybe your version is missing some patches...
>
> According to DFP100S.ZIP's "source/dflatp/message.c":
>
> BOOL dispatch_message(void)
> {
> WINDOW Mwnd, Kwnd;
> /* -------- collect mouse and keyboard events ------- */
> collect_events();
>
> /* only message.c can fill the event queue, but all components */
> /* can fill the message queue. Events come from user or clock. */
> if ( (EventQueueCtr == 0) && (MsgQueueCtr == 0) &&
> (handshaking == 0) ) { /* BORED - new 0.7c */
> union REGS r;
> #if 0 /* int 2f is often quite crowded */
> r.x.ax = 0x1680; /* release multitasker timeslice */
> int86(0x2f, &r, &r); /* multiplexer call */
> #else
> r.h.ah = 0x84; /* "network" idle call */
> int86(0x2a, &r, &r); /* network interfaces */
> #endif
> ...
> }
>
> But indeed, even with IDLEHALT, that doesn't seem to work with FD
> EDIT. Nor does TDE, strangely enough, which uses DJGPP's
> __dpmi_yield(). Even e3-16 is guilty (no surprise there, it's quite
> simplistic).
>
> I also tried ancient Stevie 3.69a (TurboC?) and newer VILE 9.8
> (DJGPP), yet surprisingly both seemed to not hog the host cpu at all.
> Must be a vi thing! :-P
>
> P.S. IDLEHALT works quite well otherwise, esp. when just sitting at
> the console / shell doing nothing. That's why I mentioned it in the
> first place, it's better than nothing.
Yeah, EDIT runs at 100% CPU usage for me as well.
I had a user complaint that FDIMPLES “was great” but you could fry an egg on
their CPU.
Oops, sorry, Took about 3 seconds to fix. Just forgot to do something.
Threw an assembly 0xF4 (HLT) in before keyboard check in its polling loop.
Yay, CPU usage own to 6%.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
