GØnter Knab wrote:
> a dos program can't reach the COM1 int 4 under dosemu. This int seems
> to be mapped to int 12. The program itself can't be configured to use
> this int.
Hmm. That seems strange since irq4 is always mapped to int12
in dos unless you manually reprogram the master PIC.
So try
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 f
Andreas Moroder wrote:
> I changed my apllication to use the Yield function in the following asm
> file, but it seem sto help nothing ( This function helps very much in win
> NT )
> ;; Author: Sz,l Viktor <[EMAIL PROTECTED]>
This is strange since this method _is_ supported by dosemu via hogthr
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 th
Hello.
The purpose of this patch is to fix a crash when mouse moves under X.
It prevents reentering to the mouse handler by using a standart PIC model
of handling interrupts. This should work for every program including dpmi apps.
I beleave that other internal drivers should also be changed to th
George Petri wrote:
> 1. To compile DOS programs
> 2. To play games
> Point 1 works fine but DosEMU has MAJOR problems with Point 2.
> This is because sound support is pathetic and 16-bit SVGA support
What about root console dosemu instead of xdos? SVGA support seems to
work well under console.
An
Narendra wrote:
> problem in formatting a removable disk (a or b) by using format in xdos.
Do you really need to format it in dosemu? Why don't you just use mkdosfs instead?
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More
Marcus Roeckrath wrote:
> I discovered that if you run the old dosemu code with the new kernel it
> works well *provided* that it is run by root. Suid root is not enough. I
> cannot explain this, but this is actually happening...
> I would also appriciate any hints.
The answer is here:
http://
Stas Sergeev wrote:
> Marcus Roeckrath wrote:
> > I discovered that if you run the old dosemu code with the new kernel it
> > works well *provided* that it is run by root. Suid root is not enough. I
> The answer is here:
> http://marc.theaimsgroup.com/?l=linux-msdos&
"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 p
<[EMAIL PROTECTED]> wrote:
> As you may know, to have fast, fullscreen console graphics, DOSEmu must be
> run as root or SUID root.
> (please note that a small bug in 1.0.2 prevents you from running as root but
AFAIK, it prevents from running SUID, but running _as_ root works.
> Hans Lerman poste
slaanesh wrote:
> I need help with dosemu-1.0.1-10. I installed dosemu, freedos and xdos
Thing to try: install latest version dosemu-1.0.2.1
> on my computer. I set in dosemu.conf line "$_hdimage = bootdir" where i
> put dos files ( /var/lib/dosemu/bootdir). However when i type dos or
> xdos on
Russell Poyner wrote:
> PS. I am contacting the vendor of avimark to try and decipher the
> mysterious "Runtime error 200" message.
This error message is magic and this question is asked very frequently.
Try starting this program before starting your program:
http://www.geocities.com/stssppnn/sdi
Martin 'pisi' Paljak wrote:
> time, no program that uses dos4gw.exe [whatever it is, I'm not a dos
> professional] doesnt work. If i'm not mistaken this one provides some kind
> of memory managment or something. Maybe there is a way to make them work
> somehow?
Definitely, there is. Everything (al
"Vlad Romascanu (LMC)" wrote:
> it seems that in p-mode, if cpl > iopl, popf instructions are not trapped.
No, if cpl > iopl, they *are* trapped, and otherwise they are executed.
> under window$ nt this freezes the dos session (virtual interrupts are never
> reenabled because popf is not trapped)
Hans Lermen wrote:
> > it seems that in p-mode, if cpl > iopl, popf instructions are not trapped.
> correct.
> DPMI under DOSEMU runs in normal Linux user space, hence protected mode
> with IOPL=0 and CPL=3.
> In protected mode popf _never_ traps (except for stack fault), from
> the Intel Programm
Hello.
Yesterday I have looked into the sound code of dosemu and found it in not
as miserable state as I expected after so many complains in this list.
Now I already made some programs to work with sound: pv (mp3 player),
iplay (stm player) some other utilities and some games.
The fact that I don
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) i
Oliver Ob wrote:
> > Now I already made some programs to work with sound: pv (mp3 player),
> > iplay (stm player) some other utilities and some games.
> > The fact that I don't have a sound card appears to be not a big problem: I
> have
> > pc-speaker, and that just required some more hacks.
> wha
Hello.
"Vlad Romascanu (LMC)" wrote:
> For Doom and the like it should be easy to incorporate a workaround into
> DosEmu (it's tougher to do in WinNT because NT's NTVDM.EXE does not
> expose a proper interface for what is needed, but anyway).
According to this, it would be easier to patch doom it
Hello.
"Vlad Romascanu (LMC)" wrote:
> No good; most of the games patched using cli2nop crash after a few seconds;
> -- if the game uses sti/cli for mutual exclusion then keeping interrupts
> enabled all the time won't guarantee any mutual exclusion. If DosEmu *does*
> disable interrupts but for
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 cau
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
Hello.
"Vlad Romascanu (LMC)" wrote:
> If interrupts have been
> disabled for more than a certain amount of time (easy to detect from within
> the emulated IRQ0 generator, maybe coupled with the CLI/STI trap handler),
> DosEmu could force the enabling of interrupts. Then Doom should then get
OK,
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 pr
Hello.
The complain that dosemu hogs CPU when program is idle, appears to be
very frequent in this ML, so I decided to post my experemental patch here
in hope that someone who have this problem, will test it. I beleave that the
problem is that dosemu doesn't release time slices when the program p
"Steve K. Sears" wrote:
> Got it down to 35 seconds before it starts to print by following your
> suggestion. Still don't know why it takes that long to process a 2K
> ASCII file.
> I thought maybe dosemu was hogging all the resources (from reading
> previous threads),
When dosemu hogs CPU, it ac
Hello.
Sergey Suleymanov wrote:
> I've used cmdline.exe and anything work fine. But now
> cmdline.com (link to generic.com ) doesn't do his work. Has
> something broken?
Seems like that. The forgotten braces and other wierd things indicates that
the code was never executed since porting to coopth
Pablo Bacherer E. wrote:
> Is it really so difficult to make the print screen key work on dosemu (as
> expected)?
Yes, sometimes it turns out to be really a bit difficult to get working a thing
that is not implemented yet:)
> I've unsuccessfully tried with Dosemu 1.0.1 under the following conditi
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 p
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 V
"John C. Alden" wrote:
> What PCI sound cards work OK within dosemu?
The idea is to emulate a classic SoundBlaster's DSP (and DMA) and output a
sound to /dev/dsp, so that you will be able to use *any* sound card that is
supported by Linux kernel, while the dos prog will think that it uses SB (you
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
http://www.dosemu
"Edward Mendelson" wrote:
> To run WordPerfect for DOS, I wanted the Number Pad Plus and Minus keys
> to work they work under ordinary DOS. By commenting out the $_X_keycode =
> (off)
Why don't just change it to $_X_keycode=(on)?
> Shift-F1 gets interpreted by WPDOS as Shift-F3, Shift-F2 gets
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 un
Hello.
"Peter Jay Salzman" wrote:
> also, someone on the list sent me email saying that he thinks the sound
> code in dosemu is completely broken, as in, dosemu can't utter a peep
> right now. but he wasn't sure.
But why can't you just check it out?
> is this pretty much the situation for
> do
Hello.
"John Goley" wrote:
> I think I remember you saying on list that you go Dosemu
> 1.0.2.1 running
^^
> Trying version 1.0.2 with freedos on my new P4 1.7 ghz machine wouldn't
> work at all.
This was fixed in 1.0.2.1 and in 1.1.2, so upgrade.
-
To unsubscribe from this list: send th
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 protecte
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 neces
Hello.
pesarif wrote:
> Liero and OMF2097 sound stutters a bit (the kind of sound stuttering you hear
> when a system is under a heavy load).
OK, as I said before, OMF's problem is fixed. LIERO's problem is now also
fixed, get a new patch:
http://www.dosemu.org/~stas/snd-patch5-1.1.2.diff.gz
Lie
Hello.
"Sergey Suleymanov" wrote:
> Grigory>Hi! I'm testing dosemu-1.0.2. VLM.EXE from Novell
> Grigory> Netware client crashes when I try to use it.
> I guess, you need suid root dosemu.bin to vlm.exe work.
One small addition: you need suid-root *and* dosemu-1.1.2, because AFAIK
suid-root
Hello.
pesarif wrote:
> > OK, as I said before, OMF's problem is fixed. LIERO's problem is now also
> > fixed, get a new patch:
> Thanks, I'll test out your patch.
I worked around clicking in many progs by increasing the minimal OSS buffer
size. It adds latency, but it is better than clicking.
So
Hello.
"Vlad Romascanu (LMC)" wrote:
>> Liero was setting a very small transfer size, so sometimes it
>> happened that
>> it was not able to handle interrupt until another one is
>> arrived, hence
>> stuttering. I worked around the problem by pausing DMA between the
>> interrupt request and ack
Hello.
"Vlad Romascanu (LMC)" wrote:
>> Just to be more specific: I am only pausing DRQs, which doesn't always
>> mean pausing DMA, but for single mode it does.
> OK. On SB-16 DMA *transfers* will pause
What exactly it does to pause DMA?
OK, atleast my code must be correct for SBPro (which is wh
Hello.
"Julius Chrobak" wrote:
> Caldera Dr-Dos. If I want to run it now it writes this:
> Phar Lap err 35: The 386 chip is currently executing in virtual 8086
> mode under the control of another program. You must turn off this other
> program in order to use 386|DOS-Extender to run in protect
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 th
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 onl
Hello.
pesarif wrote:
> I've just tested out your patch.
Thanks:)
> In general, it's perfect :) except that most programs still can't detect it
This is improved in the devel version of dosemu, but don't expect perfection
anyway.
> and there's no music :(
Upgrade your soundcard with a midi daug
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"
comm
Hello.
"bascule" wrote:
> hi, i've joined this list to see if i can get some help on getting dosemu to
> work - or rather to play 'monkey isalnd 2', i run mandrake 8.1 plus
> cooker enhancements i.e. bits if it are bleedin edge:-) dosemu version is
> 'dosemu-1.0.1-8mdk',
Have you tried Mandrak
Hello.
"bascule" wrote:
>> is to use a self-compilled (with debug info) latest version of dosemu.
> i tried compiling the latest mandrake src.rp, it didn't run, i'll
> recompile and post the error
I mean sources from ftp.dosemu.org/pub/dosemu/Development
And, if you need sound, then patches from
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 i
Hello.
Megas of Vecanti wrote:
> I doubt that it's 2.4-specific, then-Since I've seen this page fault
> happen even back when I was running 0.98 on 2.2 kernels!
You are right, it is not:(
> I'll probably try Mr. Sergeev's kernel patch, though.
No need: I explicitly stated in brackets that it do
Hello.
"Stas Sergeev" wrote:
> BTW, your program (MegaZeux) uses DPMI, right? In this case
> you are out of luck, I suppose, as there is currently no
> active DPMI maintainer AFAIK.
> And if it doesn't use DPMI, it is worth to have a look at.
Hmm, it doesn't s
Hello.
Boris wrote:
> That sound patch from stas works great.
Thanks :)
> -Their seems to be abit of a bug in it though.
I would be happy if there is only one bug, but
in fact there are many more right now (development
stage). I was updating the patch rather frequently,
but now I am slightly out
Hello.
Boris wrote:
> -The third is that when tring to run doom1,doom2, It loads the data,
> but
> *always* halts when setting up the "I_StartupTimer().
Almost forgot: several month ago I have already implemented
one of the possible workarounds (not the best one though)
and it works. Revisit my
Hello.
> file-->save-->1.txt, It says "Edit was unable to find the
> path 'C:\1.txt".
> I can't seem to create new files. I can open up an
> existing file and save
> it. It just has problems saving new files. Any ideas on
> how to fix that?
I wonder if a log (something like -D9+dRW) can shed som
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 u
Hello.
Boris wrote:
> So is something wrong with the DPMI part of dosemu that
> haults Doom2?
This patch simply measures a time period of a disabled interrupts
and re-enables them in case of a timeout (timeout is set in
a $_features, my recommendation is 200 usecs).
Doom2 needs this because it us
Hello.
Peter Jay Salzman wrote:
>C:\>mscdex /D:MSCD0001 /L:E
>Not enough drive letters available
> can someone help me resolve this error message?
Have you tried something like LASTDRIVE=Z adding in your
config.sys?
> i never really used
> DOS, so i don't grok things very well.
For mos
Hello.
Peter Jay Salzman wrote:
> unfortunately, the system freezes up for something like 30 seconds when
> the cdrom is first accessed (or when i do a DIR in a cd directory that
> hasn't been cached yet).
Are you using a redirector to access your
cd, or dosemu's cdrom.sys?
With cdrom.sys this ta
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
Hello.
Johan Gill wrote:
> I have Dosemu 1.1.3 installed, under which I run Msdos 6.
> I am trying to run Star Trek 25th Anniversary, CD version on this
> setup,
> with all sound disabled. It works, but it loads REALLY slowly, about 10
> minutes to get it going. How comes?
$_hogthreshold now b
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 tha
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.
Dosemu List wrote:
>> This seems like a problem with the latest
>> 2.4 kernels.
> I have the dosemu 1.1.3 with the patch for 2.4 kernel but now the
> system is block
> when I have a pb and I am oblige to do a kill .
Do you mean dosemu gets blocked, not the whole
system I guess, else how c
Hello.
Witold Filipczyk wrote:
> And now a few programs, that don't work as they should:
> R80 - Spectrum emulator - any keypress cause exit with General
> Protection Fault.
Yes, DPMI gets broken in 1.1.3 somehow:(
It must (and hopefully will) be fixed,
but I've no idea when:)
Try the attached p
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 i
Hello.
Grigory Batalov wrote:
> Ok, DR-DOS 7.03 works little better, vlm is working. But dosemu
> crashes when I start FoxPro 2.6/DOS:
> DPMI: realmode hlt: 0xfc920
> DPMI: switching from real to protected mode
> DPMI: Free Mem Blk. for handle 0003
> MAPPING: free, cap= DPMI, addr=0x404ad0
Hello.
Johan Gill wrote:
> This is the symptom: Dosemu seems to lock up for some time when the
> game
> is supposed to read from CD. Refreshing of the Dosemu X window stops
> for at least half a minute.
Try starting xdos from within gdb and
interrupt it with ^c when it locks. Then
you can do a
Hello.
Jim Hartley wrote:
> I have an old DOS game called Sherlock which I would like to run under
> Dosemu. It does not work, just hangs up
Just started it under xdos (dosemu-1.1.3),
and it works perfectly.
Console dosemu currently doesn't work for
me, but I am sure that if the program works
und
Hello.
Jim Hartley wrote:
> So what's the trick? You say "xdos" ... does that mean I use "xdosemu"
> to run it?
Yes. "xdosemu" is a link to a startup script
called "dosemu", but it makes sense which one
to start.
xdos is a link to a binary called "dos", which
was used in older dosemu versions an
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 so
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 abl
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 Er
Hello.
Sergey Suleymanov wrote:
> Stas> And where is this glorious patch of yours? Having a proper
> Stas> keymap could be very handy.
> Well, here is it. (for 1.1.3)
Thanks, it works.
But one thing is strange: when I use a native
X switch (Xkb) to switch to Cyrillic, everything
works O
Hello.
Stas Sergeev wrote:
> Sergey Suleymanov wrote:
>> Stas> And where is this glorious patch of yours? Having a proper
>> Stas> keymap could be very handy.
>> Well, here is it. (for 1.1.3)
> Any ideas why this happens with BackSpace?
Well, turning off
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 p
Hello.
Grigory Batalov wrote:
> Why do you prefer that patch than koi8-r from extra_charsets plugin?
> It seems working for me.
It works for me as well except for
typing cyrillic since there is no
"ru" keymap without this patch.
How are you getting it to understand the
cyrillic typing using a
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 ma
Hello.
Grigory Batalov wrote:
>> Grigory> Also I set $_external_char_set = "koi8-r"
>> Grigory> $_internal_char_set = "cp866" in ~/dosemu/conf/dosemurc and
>> Grigory> it works.
>> As the Alt+keypad sequences.
>Is it bad? =)
Are you sure that you are using a
*system* switch (xrus,
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 su
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.
Bill Giannakopoulos wrote:
> when i
> am typing wrong the the program and dosemu is crach.
> Do you have any idea what to do??
You have to provide an URL to your
program and the exact instructions
of how to reproduce the crash with
the latest dosemu, which is currently
1.1.3.
-
To unsubs
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 loggin
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.
Stian Sletner wrote:
> I know this has been discussed before,
Sure.
> I searched the archives but
> couldn't deduce a clear answer.
Very strange...
> Is sound in Doom definitely out of the question, both now and in the
> foreseeable future?
Doom, Duke3d and the like games are
*already* f
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 t
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 pr
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.
> Now I examined the dosemu 1.0.3
1.0.3 is a non-existant version.
Do you mean 1.0.2, or 1.1.3, or is
it something SuSE-specific?
> I'm using symlinks c/d pointing to mounted real dos drives in
> /var/lib/dosemu
> in dosemu 1.0.1. Has this possibility gone in 1.0.2?
It is still there.
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:
E:\TEMP
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,
the
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 pr
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 W
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
>
Hello.
Bart Oldeman wrote:
> Please test the improved joystick support from Clarence Dang: it looks
> very nice, but I don't have a joystick. He claims it works faster if
> you enable pthreads (see compiletime-settings), but I experienced DPMI
> crashes that way (DJGPP gcc immediately nukes DOS
1 - 100 of 592 matches
Mail list logo
