Re: [Freedos-user] Strange timer-related issue

2012-03-11 Thread Zbigniew
Yesterday I've found another related thing: while trying to test my soundcard with several games, I discovered, that "Civilization" has quite the same issue with FreeDOS: when ran under configuration "JEMMEX + 4DOS" it works very slowly (I'm using Sempron 2 GHz as CPU), playing the background music

Re: [Freedos-user] Strange timer-related issue

2012-03-11 Thread Ralf A. Quint
At 04:47 AM 3/11/2012, Zbigniew wrote: >Yesterday I've found another related thing: while trying to test my >soundcard with several games, I discovered, that "Civilization" has >quite the same issue with FreeDOS: when ran under configuration >"JEMMEX + 4DOS" it works very slowly (I'm using Sempron

Re: [Freedos-user] Strange timer-related issue

2012-03-11 Thread Zbigniew
2012/3/11, Ralf A. Quint : > Still not sure why 4DOS would be causing it (if using that alone, > without JEMMEX), OK, I'll check it out again; maybe I made some mistake, since indeed also I can't see any connection... will repeat the tests, then let you know. > but as I suggested in a off-list r

[Freedos-user] mouse.exe driver - can it be made "auto-resettable"?

2012-03-11 Thread Zbigniew
Its doing fine, with a little exception: when using KVM switch, sometimes mouse "goes mad". As I found out, the Linux mouse driver can somehow detect such misbehaviour, and makes a correction by itself: #v+ psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away

Re: [Freedos-user] Strange timer-related issue

2012-03-11 Thread Bernd Blaauw
Op 11-3-2012 17:21, Zbigniew schreef: >> but as I suggested in a off-list reply to a question >> that Eric Auer send me, the fact that sound output is effected as >> well, this seems kind of confirm my suspicion on how JEMM is handling >> IN/OUT statements when in protected mode, or something alon

Re: [Freedos-user] Strange timer-related issue

2012-03-11 Thread Zbigniew
2012/3/11, Bernd Blaauw : > Please let us know if/when you're able to pinpoint a culprit. > You might want to start with a MSDOS/Win9x bootdisk (www.bootdisk.com) > to eliminate FreeDOS components as the culprit, and to have a proven > reference platform. Tried it yesterday under DOS 6.22 - there