Ryan Underwood wrote:
> Dumb question, but are you certain that you are running the new dosemu
> executable? Issue a 'which dosemu' to see which one the shell is
> running, and ls -l that file to ensure that the timestamp indicates that
> it is the freshly compiled one. It is possible that you h
On Tue, Jul 20, 2004 at 09:09:03PM -0700, Ralph Alvy wrote:
>
> on a configured 1.3.1 untarred source. After 'make' and 'make install' I
> find that I no longer crash like before, but I have the same problems
> previously outlined:
Dumb question, but are you certain that you are running the new
Bart Oldeman wrote:
> On Tue, 20 Jul 2004, Ralph Alvy wrote:
>
>> >> patch < lpt2.diff
>> >>
>> >> and try again.
>> >>
>> >> Bart
>> I mean, should that have been
>>
>> patch -p0 < lpt2.diff
>>
>> instead?
>
> yes, sorry for forgetting that -p0.
Okay, I figured that after reading
On Tue, 20 Jul 2004, Ralph Alvy wrote:
> >> patch < lpt2.diff
> >>
> >> and try again.
> >>
> >> Bart
> I mean, should that have been
>
> patch -p0 < lpt2.diff
>
> instead?
yes, sorry for forgetting that -p0.
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-ms
Bart Oldeman wrote:
> Hi Ralph,
>
> Stas did not only try to fix something, but also cleaned up. This cleaning
> up was problematic (note to Stas: fops.write can be either printer_write
> or stub_printer_write; printer_write is not a wrapper that calls the
> function pointer -- and *if* you're cl
>> patch < lpt2.diff
>>
>> and try again.
>>
>> Bart
I mean, should that have been
patch -p0 < lpt2.diff
instead?
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majo
Bart Oldeman wrote:
> Hi Ralph,
>
> Stas did not only try to fix something, but also cleaned up. This cleaning
> up was problematic (note to Stas: fops.write can be either printer_write
> or stub_printer_write; printer_write is not a wrapper that calls the
> function pointer -- and *if* you're cl
Hi Ralph,
Stas did not only try to fix something, but also cleaned up. This cleaning
up was problematic (note to Stas: fops.write can be either printer_write
or stub_printer_write; printer_write is not a wrapper that calls the
function pointer -- and *if* you're cleaning up you should change *t
Bart Oldeman wrote:
> On Tue, 20 Jul 2004, Ralph Alvy wrote:
>
>> [EMAIL PROTECTED]:~/dosemu-1.3.1/bin$ ./xdosemu
>> ERROR: cpu exception in dosemu code outside of VM86()!
>> trapno: 0x0e errorcode: 0x0006 cr2: 0x053f3805
>> eip: 0x40165512 esp: 0xb79c eflags: 0x00210207
>> cs: 0x0023
On Tue, 20 Jul 2004, Ralph Alvy wrote:
> [EMAIL PROTECTED]:~/dosemu-1.3.1/bin$ ./xdosemu
> ERROR: cpu exception in dosemu code outside of VM86()!
> trapno: 0x0e errorcode: 0x0006 cr2: 0x053f3805
> eip: 0x40165512 esp: 0xb79c eflags: 0x00210207
> cs: 0x0023 ds: 0x002b es: 0x002b ss:
Stas Sergeev wrote:
> Hello.
>
> Ralph Alvy wrote:
>> I get now, when attempting to load the app in question, is this:
> Please attach your boot.log.
Here's more detail I have extracted from this. With 1.3.1, I can't print
with hogthreshold at either 1 or 2. With 1.2.2, I can print with hog at
Hello.
Ralph Alvy wrote:
I get now, when attempting to load the app in question, is this:
Please attach your boot.log.
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-inf
Bart Oldeman wrote:
> On Mon, 19 Jul 2004, Ralph Alvy wrote:
>
>> I downloaded and successfully compiled and installed dosemu 1.3.1. I find
>> the same problems with printing that I outlined before. I assume that
>> 1.3.1 has the patch you talked about earlier.
>
> No, 1.3.1 was released on the
On Mon, 19 Jul 2004, Ralph Alvy wrote:
> I downloaded and successfully compiled and installed dosemu 1.3.1. I find
> the same problems with printing that I outlined before. I assume that 1.3.1
> has the patch you talked about earlier.
No, 1.3.1 was released on the same day as 1.2.2, it doesn't co
Stas Sergeev wrote:
> Hello.
>
> Ralph Alvy wrote:
>> Well, I'll wait until the next binary.
>> I'm not sure how to use that patch.
> You can also upgrade from CVS. As a bonus,
> all the remaining problems with MaxThink
> (if there are still), should vanish.
> If you do neither, then the next bin
Stas Sergeev wrote:
> Hello.
>
> Ralph Alvy wrote:
>> Well, I'll wait until the next binary.
>> I'm not sure how to use that patch.
> You can also upgrade from CVS. As a bonus,
> all the remaining problems with MaxThink
> (if there are still), should vanish.
> If you do neither, then the next bin
Hello.
Ralph Alvy wrote:
Well, I'll wait until the next binary.
I'm not sure how to use that patch.
You can also upgrade from CVS. As a bonus,
all the remaining problems with MaxThink
(if there are still), should vanish.
If you do neither, then the next binary
is not guaranteed to have your problem
Stas Sergeev wrote:
>
> Hello.
>
> Ralph Alvy wrote:
>> With version 1.2.1, hogthreshold at 2 keeps the CPU at 60% and printing
>> is almost immediate at a timeout value of 10.
> Probably the attached patch can
> rectify the problem?
Well, I'll wait until the next binary. I'm not sure how to us
Hello.
Ralph Alvy wrote:
With version 1.2.1, hogthreshold at 2 keeps the CPU at 60% and printing
is almost immediate at a timeout value of 10.
Probably the attached patch can
rectify the problem?
--- src/base/dev/misc/lpt.c 2004-06-07 00:14:59.0 +0400
+++ src/base/dev/misc/lpt.c 2004-07-1
Ralph Alvy wrote:
> Bart Oldeman wrote:
>
>> A new stable version is out, 1.2.2, and you can obtain it from
>> http://www.dosemu.org/stable
>
> With this version, I notice with a particular database program
> (DataPerfect), setting hogthreshold to 1 causes printing problems (jobs
> not sent to t
Bart Oldeman wrote:
> A new stable version is out, 1.2.2, and you can obtain it from
> http://www.dosemu.org/stable
With this version, I notice with a particular database program
(DataPerfect), setting hogthreshold to 1 causes printing problems (jobs not
sent to the printer without first doing ot
Bart Oldeman wrote:
> A new stable version is out, 1.2.2, and you can obtain it from
> http://www.dosemu.org/stable
I'm sure it doesn't need to be said, but thanks for what you do here. Your
work, and the work of your predecessors, allows me to continue to use my
DOS database to run my office, on
A new stable version is out, 1.2.2, and you can obtain it from
http://www.dosemu.org/stable
Version 1.2.2 (2004-07-11)
=
* Backported bitmap font support for xdosemu from the development code.
These are used by default! If you want to use the X fonts you must
explicitly set $_X_fon
23 matches
Mail list logo
