Re: [announce] dosemu-1.3.3

Re: [announce] dosemu-1.3.3

[Alain]

Hi Bart,

I erroneously sent this to your return address an it appears that it got 
lost, so I am repeating it here...

I am having a very bad keyboard behaviour since I moved to Mandriva
2006. I tested dosemu 1.3.2 but it doesn't compile any more :( and CVS
november 28 version is the same.

I have made some real improuvements changing the check_key_available()
function in int16.c and the delay calls.

Please tell me where to find the INT 2fh function 1680h, there might be
something to be done there too.

Most affected programs are NDN, Setedit and BC31 (only compile time,
editor is ok)

Up to now I using basicaly my DOS knowledge, I will probably need more
specific dosemu later,

thanks,
Alain

Re: [announce] dosemu-1.3.3

[Bart Oldeman]

On Fri, 30 Dec 2005, Alain wrote:

> I have made some real improuvements changing the check_key_available()
> function in int16.c and the delay calls.

The delay calls have also changed in CVS after 1.3.3 so you might want to 
update that again (src/emu-i386/cputime.c). The delays were a bit too long 
and were not interrupted by signals. But if you still have problems even 
with "speed 0" that won't help.

http://sourceforge.net/tracker/index.php?func=detail&aid=1387967&group_id=49784&atid=457447

shows that issue.

> Please tell me where to find the INT 2fh function 1680h, there might be
> something to be done there too.

"grep" is your friend. src/base/async/int.c

Bart

Re: [announce] dosemu-1.3.3

[Alain]

Hi Bart,

>> I have made some real improuvements changing the check_key_available()
>> function in int16.c and the delay calls.
> 
> The delay calls have also changed in CVS after 1.3.3 so you might want 
> to update that again (src/emu-i386/cputime.c).

I will check, is it suposed to change again?

> But if you still have problems even with "speed 0" that won't help.

speed 0 is ok, even something like speed form 2 to sometimes 4. BUT, in 
both cases I get 98% cpu usage.

> "grep" is your friend.

Only if you are lost in the forrest XOR you have a lamp, but not both ;-)

Thaks and Happy new year,
Alain

[announce] dosemu-1.3.3

[Bart Oldeman]

A new developer's release was uploaded. As with 1.3.2 this is a
reflection of CVS HEAD, and only source code (no binaries) is
available, at http://www.dosemu.org/bleeding

This release is nearing a stable 1.4.0 release, apart from documentation and 
any issues that may come up in any testing.

(sorry for the previous message without a subject line)

Bart

Re: [announce] dosemu-1.3.3

[Ralph Alvy]

Bart Oldeman wrote:

> A new developer's release was uploaded. As with 1.3.2 this is a
> reflection of CVS HEAD, and only source code (no binaries) is
> available, at http://www.dosemu.org/bleeding
> 
> This release is nearing a stable 1.4.0 release, apart from documentation
> and any issues that may come up in any testing.

I notice that all my previous problems with dosemu > 1.2.1 are gone with
this release. However a new one is introduced. When running dosemu 1.3.3
with MSDOS 6.22, I find that the TSR called ZipKey can't read its own data
file, informing me that, no matter what zip code I type, that zip code is
not in the database. But if I switch back to running dosemu 1.2.1 with
MSDOS 6.22, it works fine.

Re: [announce] dosemu-1.3.3

[Bart Oldeman]

On Fri, 23 Dec 2005, Ralph Alvy wrote:

> Bart Oldeman wrote:
>
>> A new developer's release was uploaded. As with 1.3.2 this is a
>> reflection of CVS HEAD, and only source code (no binaries) is
>> available, at http://www.dosemu.org/bleeding
>>
>> This release is nearing a stable 1.4.0 release, apart from documentation
>> and any issues that may come up in any testing.
>
> I notice that all my previous problems with dosemu > 1.2.1 are gone with
> this release.

Good to hear that.

> However a new one is introduced. When running dosemu 1.3.3
> with MSDOS 6.22, I find that the TSR called ZipKey can't read its own data
> file, informing me that, no matter what zip code I type, that zip code is
> not in the database. But if I switch back to running dosemu 1.2.1 with
> MSDOS 6.22, it works fine.

Can you try to do the exact same procedure for 1.2.1 and 1.3.3 using the 
-D+dD switch (just type one zip code, it succeeds in 1.2.1, and fails in 
1.3.3, then immediately exit dosemu), and save the resulting 
~/.dosemu/boot.log files?

The differences between the logs may give us some clues.

Bart

Re: [announce] dosemu-1.3.3

[Ralph Alvy]

Bart Oldeman wrote:
>> However a new one is introduced. When running dosemu 1.3.3
>> with MSDOS 6.22, I find that the TSR called ZipKey can't read its own
>> data file, informing me that, no matter what zip code I type, that zip
>> code is not in the database. But if I switch back to running dosemu 1.2.1
>> with MSDOS 6.22, it works fine.
> 
> Can you try to do the exact same procedure for 1.2.1 and 1.3.3 using the
> -D+dD switch (just type one zip code, it succeeds in 1.2.1, and fails in
> 1.3.3, then immediately exit dosemu), and save the resulting
> ~/.dosemu/boot.log files?
> 
> The differences between the logs may give us some clues.
> 
> Bart

I sent them to you via private email.