Hans Lermen wrote:
Stas Sergeev did send me a patch that solve the problem.
hmm, what patch are we talking about here?
I have posted a potential fix to Andreas and it works.
The explanation is that if we want to prevent calling int 0xe0, we have
to do it for ax=0x300 and not for any other
Keith Duthie wrote:
The game is called Ringworld: Revenge of the Patriach. This problem could
This is really great: this game crashes when moveing the mouse and it does
*not* use dpmi. Previously I sought it is a dpmi problem, but now I see how I
was wrong.
Also now I think I understand where
David Milligan wrote:
Some of our (and others) programmes appear to either crash or pause if
they are left running for around 30 minutes or more.
Is this with dosemu-1.0.2?
This is especially apparent in our programmes which have a screen saver
feature. The screen saver routine is pretty
Rodrigo Gallardo wrote:
When receiving commands from the DOS program, the emulation sets a
timer. After it expires, it tries to raise an interrupt (IRQ 6), so
the DOS programm will go on. In my timer handler, I call
pic_request(pic_irq_list[6]).
I beleive you can do pic_request(PIC_IRQ6)
Oliver Ob wrote:
Hi Bart, please be so kind as to
What do you need? Sound support is incomplete anyway so not only Doom
is silent. Enjoy Wolf for now:)
technically exlpain why no sound with DOS-DOOM
Quoting http://www.jsiinc.com/dl/SoundFX.txt:
---
Execution of an CLI or STI instruction causes
pp wrote:
I got dosemu 1.0.2.1, and after trying to tun application I got such an error:
Phar Lap err 35: The 386 chip is currently executing
Phar Lap and other dos-extenders are used to work under dosemu if dpmi is
enabled.
What should I do?
Check $_dpmi option in your dosemu.conf, it is
Ross Boylan wrote:
I have tried various settings of hogthreshold, but I can't prevent a
certain program (GrandView) from grabbing all the CPU when it runs.
Is there something I can do about this?
Currently there is probably nothing to do, but you can still try playing with
nice(1).
The
Peter Eser wrote:
...I send it again (Stas), first time it was not at the whole mailgroup
In earlier releases I worked as normal user with suidroot, but that
seems to be forbidden now.
What's your problem? You've been (privately) suggested to upgrade to 1.0.2.1
because it is a fix for your
Chris Elvidge wrote:
E.g. after invoking ./dosemu
dir - directory listing
dir - linux shell prompt
This is already a second report of this bug.
With first reporter we came to a conclusion that Scroll() is called with an
invalid screen address for some reasons.
Could you please make a Video
Hello.
pesarif wrote:
I got dropped from the list for a while (don't know why so I rejoined), did I
miss any other of your patches? If so, please send them to me.
No, I haven't posted any more due to a complete lack of interest.
But I have just uploaded a latest version to
Hello.
Bernhard Bialas wrote:
1). I get only connection (by starting the driver) when I start DOSEMU
from the console as root.When I start as normal user, the driver fails
to start and I dosemu hangs.What I can do to get the communication from
xdos?
(looking in the ChangeLog) I am under
Hello.
ERROR: general protection at 0xfadf: 66
ERROR: SIGSEGV, protected insn...exiting!
shouldn't dosemu catch segmentation violations and perhaps print a more
It does, else you would have been seeing segmentation fault (core dumped:).
This is just an evil dos4gw trying to enter protected
Hello.
pesarif wrote:
I did all your patches at that URL (sound + serial) and got:
i.e. the serial patches required fuzzing and the DPMI patch failed. Using
dosemu 1.0.2.1. What I am doing wrong?
At least one thing: serial patches have nothing to do with sound stuff, so it
is not necessary
Hello.
John Goley wrote:
mouse doesn't work like it is suppose to. It will not work at all if I just
left mouse click on the menus. Nothing happens. But if I hold down
the right mouse button and then click hard with the left button then it
will work sometimes. What is wrong? Is there a
Hi.
Vlad Romascanu (LMC) wrote:
However, even if the transfer was block it will still pause on
terminal-count if DREQ is deasserted, no?
From manual:
The difference between Block and Demand is that once a Block transfer
is started, it runs until the transfer count reaches zero. DRQ only
needs
Hello.
Vlad Romascanu (LMC) wrote:
you (the SB) can always deassert DRQ and the DMAC
will actually check DRQ when reaching terminal-count, no?
Yes (even in auto-init I think, my docs are incomplete though), but how
to stop block DMA xfer when TC is not yet? I mean I can issue a Pause
command
Hello.
Jacob Perkins wrote:
Whenever I run dosemu-freedos 1.0.2.1 it will eventually
cause my
computer to reboot. I'm running Gentoo Linux with kernel
2.4.17 with preempt patch.
Due to an obvious bug in the latest 2.4 kernels, dosemu can
easily cause the system to panic. Generally it
Hello.
gobo wrote:
trying to access com1 (3f0 - 3ff)under dosemu. i've
given dosemu access to that address range.
dosemu emulates serial ports, so no need to use a direct
access. Have you tried a $_comX settings in dosemu.conf?
no matter
what i try, i can't get to the ports.
You can't use
Hello.
Bryan J. Smith wrote:
Tried this under both DOSEmu 1.0.2 and 1.1.1.
Try 1.1.2 (or, better, even 1.1.2.9)
1. Run as su'ed root (so I can access /dev/ttyS0)
2a. Set $_com1 = /dev/ttyS0
2b. Set $_ports = device /dev/ttyS0 range 0x3F8,0x3FF
If I don't do #1, I get an error on DOSEmu
Hello.
Suporte wrote:
Problem:
The Dosemu starts to send the report for the spool of Linux(lpt1) before
the application finishes to generate the report, with this, the report
is printed in parts without control.
How to leave printer_timeout infinite? == This resolve?
You mentioned that
Hello.
Dosemu List wrote:
I use dosemu-1.0.2.1 from Debian...really nice product !
You may want to upgrade to dosemu-1.1.3
Mar 19 15:14:47 costes kernel: invalid operand:
Mar 19 15:14:47 costes kernel: CPU:0
Mar 19 15:14:47 costes kernel: EIP:
Mar 19 15:14:47 costes kernel:
Hello.
I am wondering about the versions of dosemu. Somebody suggested I use
dosemu-1.1.3. However, while i did find a redhat package with this
version number,
You are definitely confusing something -
pre-packaged dosemu-1.1.3 must not exist.
Could you provide a link to where you've seen it?
Hello.
I'm running MSDos 6.2 on dosemu 1.0.2. The program asm5600.exe, which
runs in native dos, causes the below error message when run in dosemu.
Just tried under PC-DOS 7.0, dosemu-1.1.3:
Motorola DSP56000 Assembler Version 5.3.20
Copyright Motorola, Inc. 1987-1994. All rights reserved.
Hello.
Grigory Batalov wrote:
I. Dosemu-1.1.3 and freedos still crashes while loading vlm:
ERROR: general protection at 0x20360: 50
Program=do_vm86.c, Line=389
Make sure you have enough XMS/EMS/DPMI memory
configured.
It would be better to apply them together with
this one, but then
Hello.
Suporte wrote:
send directly for the LTP1, the dosemu close job and sends a piece of
the archive for the spool of the Linux.
Because the Dosemu does not wait that the application finishes the
execution of the report to order job for the spool of the Linux?
What I can modify in source
Hello.
Felix Karpfen wrote:
My remaining question is, are there benefits from overwriting the
installed (already-working) dosemu-1.0.2 by the compiled version?
The benefit is that you can compile something
more modern instead of your 1.0.2, which is
known to be buggy. And also you will be able
Hello.
Sergey Suleymanov wrote:
Grigory looks like 'P') when in X. Some time ago I got patch from
Grigory Sergey Suleymanovor for dosemu-1.0.2 that fixes problem for
Grigory 1.0.2 version. Maybe such patch exist for 1.1.3?
Just for 1.1.2 + Eric's patch.
I think that this Eric's
Hello.
Sergey Suleymanov wrote:
Any ideas why this happens with BackSpace?
Stas Well, turning off X_keycode fixes the problem. Can live with
Stas this:)
Hmm, can't reproduce that :(. 3592 in both modes.
Well, I have investigated a little more
and found that the attached patch
Hello.
Sergey Suleymanov wrote:
Stas altgr table is enough.
Actually only these are needed at all. ;)
But in fact this means that the problem
is still there.
The problem is that normally altgr map is
similar to the alt map, so the special keycodes
in it are mapped as for the alt map.
Hello.
Thomas Weidner wrote:
what do i need to get sound in old dos games working ?
You need this:
1. dosemu-1.1.3 sources
2. New SB (Pro) emulator from this page:
http://dosemu.sourceforge.net/~stas/
Do i need a dos soundblaster
driver ?
No, you don't need any because old SB
cards are
Hello.
Justin Zygmont wrote:
I tried that
When? Are you using the latest revision (16)
of the patch?
but the sound would only work for about 5 seconds, then
freeze up dosemu.
Have you applied only SB patch, or also some
other patches?
Does it lock dosemu hard (so that Ctrl-Alt-PgDn
doesn't
Hello.
Bryan J. Smith wrote:
1. I'm having a bit of difficulty trying to figure out how to enable
debugging.
There are a lot of debug options.
You may enable the debug logging with
-D9+xxx option, where xxx specifies the
type of events you are going to log.
So, to enable a file access
Hello.
[EMAIL PROTECTED] wrote:
Is there any way I can get some debug output?
Debugging output can be enabled with
-D option (consult `man dos`), and with
-o option you have to specify the file to
which the logging being written.
Also try to start the game under console
suid-root dosemu since
Hello.
Thomas Neidhart wrote:
i have some problems getting the mouse to work under dosemu-1.0.2.
And you are lucky that you don't
have many other problems with that
particular version.
First i had the problem that the mouse movement was just not smooth,
but with
setting hogthreshhold to 0
Hello.
Thomas Neidhart wrote:
i tried dosemu-1.1.3.1 and it got somewhat better:
Good:)
The mouse clicking problem is also getting
better,
although from time to time it occurs again.
Please produce the -D9+Xm log.
But upgrading to 1.1.3.1 also created some new problems.
With DPMI
Hello.
Thomas Neidhart wrote:
i have tried all patches from you, and with them the programs don't
crash anymore.
Very good. These patches are aimed to fix
the 1.1.3 DPMI breakage and, while they don't
currently cover the whole issue, they are
getting there (addressing many other problems
at
Hello.
Kara Van Horn wrote:
When I tried adding WINPKT.COM (as
mentioned in the docs) to my IPX stack (WINPKT replacing PDIPX,
followed by
VLM), and specified a packet driver address as 0x60, it said there was
not one at that location.
Make sure that $_vnet is *off* and then:
Hello.
Johan Gill wrote:
I have dosemu-1.1.3.1 with mouse and dpmi_iret patches applied.
According the log, it doesn't seem to
use DPMI, so dpmi_iret patch might not
affect.
When I try running Space Quest 2, dosemu exits.
How good is it without any patches?
Does it work on dosemu-1.0.2.1?
It
Hello.
Johan Gill wrote:
It also crashes on 1.1.3. I don't remember exactly what went wrong with
1.0.2.1 since it was a while ago.
OK, I have downloaded something
called the Space Quest, which
turned to be a game dated 1987
with CGA graphics, by Sierra.
If this is the game you mentioned,
then
Hello.
At last I was able to track down the problem. It turned out to be that
one should have the real floppy accessible in order to boot from the
image. In my case, ordinary users have no access to /dev/fd0.
I suggest the change below.
Your patch doesn't seem to attack
the root of the
Hello.
the
aplication I try to run is a Multi-user mode application that run on
DOS sessions
Such programs might not work under
dosemu. I am afraid you expecting
way too much.
Error [35]: General Protection Fault in ZIMRTMU.EXE at 0377:011C
Make sure that this program works on
either
Hello.
Stephen Lee wrote:
I forgot to mention that Dosemu is run under Redhat 7.2
No, you forgot to mention the version
of dosemu you are using.
My Foxpro application recognizes the F1-F12 keys fine but not the Shift
or the Control Fkeys. I ran a keyboard scan program in the DOS session
and
Hello.
Scott Andreas wrote:
We run an foxbased application that crashes after 2 min. I'm running
the app
inside a secure terminal via ssh...its so cool, well after about two
minutes the app crashes and dumps...
Me and Bart were busily resolving
tonns of the foxpro+IPX issues
in a latest
Hello.
Patrick J. LoPresti wrote:
The only good thing here is that the amount of progs that works on
486 but not on 386 is very minor...
But how annoying when you run into one :-).
I really don't think it is a major
advantage to have an ability to
pass the first stage of NT install... :)
Hello.
Bart Oldeman wrote:
functionality. Then you can safely
remove the BUG stuff I think.
Yes, that looks like the proper fix to me.
We probably have to contact
Alberto to find out if his tests
are passed with that patches
because my testcase for the
BUG includes only FoxPro...
Would you
Hello.
Per Jessen wrote:
It is not totally reproducable - it varies. Timing problem ?
Try using a standalone lredir.
Compile the lredir.c from
src/commands (not from
src/plugin/commands) and see
if it also suffers. If it is,
compile it with debug info and
try to locate the problematic
place
Hello.
Per Jessen wrote:
attached is a patch for the \P on the keystroke
config option not working with the unicode keyboard
It's a very late night here
and I have looked neither in
the code nor in the problem,
but somehow it happened that
I don't like your patch (sorry).
I'll have a look
Hello.
Per Jessen wrote:
let me know - it works here.
Good :)
If you don't like the added
debug output, well ... :-)
I don't like it because you
have a single string duplicating
many times. Just putting it
right before the switch() would
be OKey I think. Also for 'A'
you are adding that
Hello.
Oscar A. Valdez wrote:
Do the keystroke configure and -I commandline options still work on
Dosemu 1.0.2?
Still works fine on 1.1.3.2.
I've been trying them without luck.
How exactly you are doing that?
The example from the docs works for me.
Try passing the options directly to
Hello.
Larry Alkoff wrote:
I would not have thought that the modem wouldn't run if the device was
not locked.
Well, it is just a polite behaveor (not a
bug), but in fact it is possible to use the
device without locking it. There are reasons
against doing this however.
was trying to avoid
Hello.
mat.hieu wrote:
Sim city or Dune ( I found abandonwares, it's pretty good !) but when I
click with any buttons, the pointer goes to the upper left corner and I
can't click on anything.
This problem is reported too frequently but
I still can't reproduce it.
I don't know how could you
Hello.
Chris Wilson wrote:
Are there any plans to introduce proper keyboard layout support under
slang?
Yes, upgrade to 1.1.3.2 and apply the keyboard
patches from
dosemu.sourceforge.net/stas
to try out the new keyboard engine.
It would be better to provide patches for
both, your patch is for
Hello.
I configured dosemu with the IBM characters table. That's fine, but some
characters are not correctly displayed... My program uses a C library called
vl850 (a graphical library in MS-DOS) . The problem occurs when I execute my
program and the graphical characters of the ASCII table
Hello.
I cannot run it setuid, due to the dosemu script which disallows this.
dosemu 1.2.0.1
Such version doesn't exist yet (1.2 is only planning).
Downgrade to something more real, like 1.1.3.2 and
don't expect to get any help for the not-yet-written
software:)
-
To unsubscribe from this
Hello.
Szabo Atti wrote:
If they run two sessions on the text console
I suspect it is a grafical console in fact.
It is done that way that when dosemu is switched
out of a graphical console, it gets frozen until
it switched back. Being frozen for too long, it
lost connection.
Try setting
Hello.
Grigory Batalov wrote:
I have a legacy DOS system, MSM (Micronetic M-System).
It crashes under dosemu-1.1.3.4 with or without latest Stas' patches.
Is this because a lot of my patches are already
in, or not? I mean, with what dosemu version it
used to work? Now we have not more than one
Hello.
Grigory Batalov wrote:
I have full logs (-D9+M) if someone is interesting:
OK, AFAICS it have nothing to do with 1.1.3.4 - this
bug was always there and I wonder why nobody noticed
it before (oh, about a year ago Bart forwarded me
something similar from djgpp-devel, IIRC).
Try this
Hello.
Grigory Batalov wrote:
can you give some common hints to improve performance
of such DPMI programs as MSM?
No unless I have this program handy, and even
then most likely still no, but you can try:)
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a
Hello.
Oscar A. Valdez wrote:
A friend reports a segmentation fault after quitting a FoxPro 2.6
application for the second time.
Dosemu: 1.0.2.1
Update your dosemu!
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More
Hello.
Bart Oldeman wrote:
Isn't 1.0.2.1 the latest 'stable' version,
whilst 1.1.3 is unstable' ?
Yes.
Well, no:)
Consider this: 1.0.2.1 had enough *known* bugs
for too long. Version that have known bugs (in
contrast to unknown, which are always present)
can't be called stable or recommended
Hello.
Bart Oldeman wrote:
your problem is mostly not video shadowing
I tried this privately already - doesn't work:)
but just that DOSEMU does
not support this video card and does not open up enough ports.
Note however that this must not be the case for
VGA modes.
And esp. if the person
Hello.
phrostie wrote:
not support this video card and does not open up enough ports.
what ports?
could you expand on this part?
i have a S3
For S3 cards you must not worry about this issue
at all. Setting $_chipset=s3 worked for my S3 Trio
flawlessly both for VGA and VESA modes. Don't
Hello.
Bart Oldeman wrote:
Well VGA only uses standard ports so the only problem is to pass the
VBIOS initialization in the first place, that is executing the code at
c000:0003
Where does it do that? I have found only
init_vga_card(), but that doesn't seem to be
the place. Also I searched the
Hello.
Bart Oldeman wrote:
c000:0003
Where does it do that? I have found only
init_vga_card(), but that doesn't seem to be
the place. Also I searched the +g log for
c000:0003 and found nothing...
src/base/bios/bios.S, line 507, F800:4200.
init_vga_card() pushes f800:4200 on the stack
Hello.
phrostie wrote:
last night i was going thru the different runtime options, but
regardless of
what i try i still can't seem to get any of my VGA stuff working again.
Then create a log of video events (-D9+v option
to dosemu) and see what's going wrong.
And upgrade your dosemu:
Hello.
Guennadi Liakhovetski wrote:
the application I want to use uses this ncurses-analog terminal mode,
and youo use {CTRL,ALT,SHIFT,}-Fx for various configuration options...
Yes, I saw the thread about just this, and using 1.1.3.2 didn't help.
Set $_rawkeyboard=(1) then.
The thread you've
Hello.
Grigory Batalov wrote:
Stas, can you give some common hints to improve performance
of such DPMI programs as MSM? It works quite slow (taking
all CPU power).
Just recalled something: when I upgraded to kernel 2.4 from
2.2, I noticed a DPMI speed-up of 20 times!
IIRC you are still using
Hello.
Stian Sletner wrote:
it booted up and got to the usual map01 starting point, but I couldn't
move at all, I tried moving the mouse and waiting like 10 minutes to see
if there was any reaction at all, but there wasn't.
Now you may want to try 1.1.3.4. As for
dosemu's IPX, it is still a
Hello.
Giuliano Pellegrini wrote:
I use DosEmu ver 1.0.0
Sure you could find even older dosemu? :)
ERROR: general protection at 0xbb2f: 66
ERROR: SIGSEGV, protected insn...exiting!
I have try to change in the file /etc/dosemu.conf these directives:
$_xms = (8192) # in Kbyte
Hello.
phrostie wrote:
an update i did finally get dosemu working.
What update you did and where was the problem
at the end?
keen 4 and above still lock up.
Update your keen. See this:
http://marc.theaimsgroup.com/?l=linux-msdosm=103211907106200w=2
-
To unsubscribe from this list: send the
Hello.
Bart Oldeman wrote:
could you check dosemu.map to see where 0x401ace06 is?
It might just be out of DOSEMU's scope; in that case it might be a DPMI
page fault
Current buggy fault handler (to be fixed
with my fault handling patch) have this:
if (in_dpmi)
return dpmi_fault(scp).
So,
Hello.
Bart Oldeman wrote:
but for now you told there is another buffer
overflow in mfs, isn't it?
No, that's what *you* suspected.
I was referring to this:
---
Silly buffer overflow
indeed but I never imagined network redirectors working in
such a way
---
Yes, this is fixed in Patchset 5,
Hello.
John Elliott wrote:
They cause
dosemu to abort if DPMI function 0x300 is used to call interrupt 0xE0
or higher;
What exactly interrupt from this range do
you want to execute?
is this correct,
Of course it is not. If your program installs
the realmode handler for that ints, it will
Hello.
Michael wrote:
I'm wondering if anyone has any ideas on what might be causing this
error i'm getting with a old game i've got.(Broken Sword 1)
When i run the main executable it yields Failed to install timer
services... exiting
Fill in the bug-report on SF and upload the
game there
Hi.
Bart Oldeman wrote:
Doing the reset call from within DOS brings
everything back in a sane state.
Just wondering, why this reset is needed so badly?
Just a very rough guess: proper initialization of certain BIOS
variables in the range 0x400-0x4ff (0040:-0040:00ff) ?
Exactly! Plus
Hello.
Peter Forst wrote:
can someone explain me about the following error-message
Dosemu somehow happened to execute an
invalid code, which caused a GPF in vm86().
The dosemu craches while starting an application from our, via
novell/ipx mapped network drive.
Does this happen when starting
Hello.
Bart Oldeman wrote:
slower than xdos... why ioperm() doesn't allow
0x3ff ports?..
Once upon a time Linus decided that a 128 byte per-process i/o bitmap
is ok, but 8192 bytes is excessively large.
Yes, and there was a reason then, which was
that ISA had 10-bit IO space most likely, but
Hello.
Lars BjÛrndal wrote:
I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the
line largest executable program size 617K, 1.1.3.5, the same command
and config gives 611K. Why, do you think?
I can recall only one change in a memory
allocation algo of that times, which is
Hello.
Hartmut Figge wrote:
Looking in the folder, in which ancient batch files resides, shows e.g.
push.bat, which contains the line 'loadfix push'.
That cured the problem with the 'corrupte file' and was the only way,
to use that game.
I don't agree. loadfix works around the
exepack bugs by
Hello.
Bart Oldeman wrote:
a) the DOS time is the same as in the previous PIC call.
PIC schedules the next activation time
and then works in polling mode to see
when that time is reached. Even when it
reached, there are no guarantees that it
is possible to fire the int right away,
so it can
Hello.
Sergey Suleymanov wrote:
When I run dosemu without root privs, it says: (here 333 is
internal net of the native NetWare server)
ERROR: IPX: Failure adding route 0333 through
0111:0001
Is this ok?
Doesn't look healthy to me.
Does this patch help?
Patch is
Hello.
Lars BjÛrndal wrote:
Thank you! Now, wp.exe works perfect!
Fine. Now we know that was just another
exepack bug, not fixable by loadfix btw.
The note should even be added in FAQ I
think, because nobody knows how many bugs
will we chaise in a future thanks to an
exepack (and UPX!) authors.
Hello.
Bart Oldeman wrote:
I can see also this misterious dosemu-bugs
list which even I haven't seen, also made
itself public.
No it's not public. You only see it if you are logged in.
Yes, now I see. So you have killed an idiocy
only partially:)
submit-bug-report script in dosemu that
Hello.
Cezar Cichocki wrote:
I'm looking for NDIS emulation for DOSEMU.
Not available natively:(
Must be implemented.
I've tried PKTDRV/PDETHER mix
and it works however it's unable to load ODINSUP (PDETHER provide
Ethernet_II only frames and ODINSUP requires also 802.2 and 802.3).
Quote from
Hello.
Stian Sletner wrote:
haven't had a chance to test this until now. Just tried with 1.1.3.7,
Right:)
but I can't get past trying to load PDETHER. It says:
FATAL: Packet Driver not found on software interrupt 60 hex.
Check if $_pktdriver=(on) and that
dosemu is running with root perms.
Hello.
julius junghans wrote:
i tried to run msdos 6 with this tutorial
http://www.geocities.com/sunil_tt/dos.txt
Not the best instructions: boot
sector can be omitted as dosemu
can create the boot sector on
startup, so you need only a
system files. The boot.blk is
not even documented for that
Hello.
julius junghans wrote:
but dosemu exits with :
./dosemu: line 386: 2712 Segmentation fault
Check your system log for Oopses.
This was a long-standing bug of
the 2.4 kernels.
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL
Hello.
Bernie Gardner wrote:
slow to keep up. Is there a way to speed up the com port?
Probably no - emulation is an emulation.
It works quite fast in a FIFO mode
(buffering), but when there is no
buffering and each operation must
be performed immediately, if falls
down with a perforance.
You
Hello.
Ged Haywood wrote:
I do not think FIFO buffering will help a program which manipulates
the DTR line directly, as the UART is not actually sending data in
the normal way - it's just being used as a 1-bit data latch.
Right, that's what I implied to actually.
It works quite fast in a FIFO
Hello.
Peter Jay Salzman wrote:
linux 2.4.19 (linus, not ac)
Not possible, Linus is no longer maintains
the 2.4 kernels.
-ac is recommended for dosemu users as
Alan Cox kindly applied all the dosemu-
related patches in 2.4.19, while Marcelo
have done that only in 2.4.20-pre (and
not so kindly,
Hello.
Stian Sletner wrote:
I experimented some more with this, since it seemed to be the right
thing to do, the dosnet stuff is IP oriented after all, and shouldn't
be necessary to achieve this, I would think.
Dosnet have nothing to do with IP.
It's goal is to emulate an Ethernet
network on a
Hello.
Stian Sletner wrote:
The incoming IPX
packets _are_ to broadcast address, but DOSEMU does not pick them up
because (I assume) they originate from the same interface, eth0.
Well, all the outgoing packets have
the PACKET_OUTGOING type. They are
not intended to be received on the
same
Hello.
Boszormenyi Zoltan wrote:
After setting up doom2 to no sound, it works.
You haven't applied the necessary
patches from here:
http://dosemu.sourceforge.net/stas/
so what is to expect.
Supaplex uses a kind of split screen, the lower part contains time
and other status info, the upper
Hello.
Ged Haywood wrote:
Don't use setup-dosemu script for now as it removes some important
options from compiletime-settings.
What options are important that it removes?
Just compare the fresh compiletime-settings
file with the one created by setup-dosemu to
see which ones.
I compiled
Hello.
Stian Sletner wrote:
I thought I had a clever idea, ifconfig'd up a virtual interface eth0:0
and set $_netdev = eth0:0, but that made dosemu crash so it probably
How exactly the crash looks like?
I'm having problems compiling the dosnet module in RH8.
It was already reported that
Hello.
Simon Bridger wrote:
I want to use it in a console window. Unfortunately I get a message
telling me there is no vesa driver.
Known problem:(
This largely depends on your video
card however.
Get a card where the extended registers
are accessable via the VGA registers -
and you have VESA.
Hello.
Mushroom wrote:
Yes - the problem remains as it was. I'll try playing with some more
settings but it doesn't seem promising.
OK, I think all the problems we have
with video, are because dosemu is
trying to POST the video bios not
accordingly the PCI specs.
I intended to introduce a
Hello.
Michael Lee wrote:
Has anyone had success using dosemu in redhat 7.2 (kernel 2.4.18)?
Yes.
However, the kernel upgrade is recommended
as there was some dosemu-related work done
in 2.4.19 and 2.4.20.
downloading the latest (1.0.2.1) dosemu from
sourceforge and compiling that.
No,
Hello.
Mushroom wrote:
OK, try the attached patch.
That's fixed it!!!
Great!
Hmm, that was just too easy, there
is still something fishy about that.
Do you have $_pci option disabled
or enabled?
If it is enabled, could you try to undo
the patch, set $_pci=(off) and reproduce
the problem?
Oh,
Hello.
Simon Bridger wrote:
Slow is a nuisance, but it isn't terminally slow.
The showstopper is the mouse behaviour. What happens is this. When the
mouse reaches the edge of the autotrax screen, autotrax pans, and moves its
own mouse cursor back to the middle of the screen.
If only this is a
1 - 100 of 396 matches
Mail list logo
