Here we go,
I've attached three logs
BOOT.OK is a log from a dosemu 1.1.1.x which is working fine (I can print to
my serial printer)
BOOT.NO is the same printing from a dosemu 1.1.4.12 which is not working, see
how smaller it is compared to the first one
BOOT.NI is a little printing (a couple
Ok, with this patch it works ok :)
So I've switched to 1.1.4.13, but now my clipper program is not able to print to a
serial
printer anymore :( even if a
dir com1:
from dos prompt works ok, but my program uses a third party library to communicate with
serial devices
I fear it has to do with
Maurilio, were you using freedos with dosemu before you switched to
1.1.4.13 and your clipper apps were printing? In freedos? I never could
put clipper printing (neither serial nor parallel) to work with
freedos+dosemu, but I started to use dosemu with 1.1.4, and never tried
any previous
No, I use an old MS-DOS 5.x, now, even with latest patch from Bart, I can print to my
serial
printer with a
dir com1:
but not from my clipper (protect mode, telepathy as comx: access library) app...
To be more precise I can print very short strings, that is
tp_open(1...) // open com port 1
That is,
int14 is working ok, but serial emulation is not (telepathy does a direct serial
access and does
not depend on int14 service).
regards
Maurilio Longo ha scritto:
No, I use an old MS-DOS 5.x, now, even with latest patch from Bart, I can print to
my serial
printer with a
dir
Hello.
Maurilio Longo wrote:
int14 is working ok, but serial emulation is not (telepathy does a
Unless you provide all the necessary
logs, you'll of course not get any
concrete suggestions.
works, but if there are more tp_send() one after the other I get no
output!?!!
Great, in that case you
Any comments?
Nobody stumbled on this issue?
curious :)
Maurilio.
Maurilio Longo ha scritto:
Hi,
latest dosemu has problems (locks up here and there) if it is run on a 2.4GHz
pentium IV and inside dosemu.conf I have
$_rdtsc(on)
$_cpuspeed(0)
I think this comes from the fact that on
Any comments?
Nobody stumbled on this issue?
curious :)
I'd wager that nobody on this list owns a machine that fast. 8)
latest dosemu has problems (locks up here and there) if it is run on a 2.4GHz
pentium IV and inside dosemu.conf I have
--
Ryan Underwood, nemesis at
I fear that cpu speed is inside a long int and this shoud explain why it happens, I'd
like to know from someone who writes dosemu if this is true and how they plan to fix
this.
regards.
Ryan Underwood ha scritto:
Any comments?
Nobody stumbled on this issue?
curious :)
I'd wager
On Wed, 12 Mar 2003, Maurilio Longo wrote:
I fear that cpu speed is inside a long int and this shoud explain why it happens, I'd
like to know from someone who writes dosemu if this is true and how they plan to fix
this.
it's a multiplication that overflows from an int -- try this patch:
---
Hello.
Bart Oldeman wrote:
it's a multiplication that overflows from an int -- try this patch:
The attached one might also be
necessary to get the correct
output.
--- src/base/init/config.c Wed Feb 19 16:17:30 2003
+++ src/base/init/config.c Wed Mar 12 22:09:27 2003
@@ -493,7 +493,7 @@
On Wed, 12 Mar 2003, Stas Sergeev wrote:
Bart Oldeman wrote:
it's a multiplication that overflows from an int -- try this patch:
The attached one might also be
necessary to get the correct
output.
- warn (Linux kernel %d.%d.%d; CPU speed is %Ld Hz\n,
+ warn
12 matches
Mail list logo
