Game problem Re: Freshly installed dos-6.22 with disk image doesnot work
Now I tried some games, some worked, some didn't. E.g. doom2 didn't, supaplex (a boulder dash clone) did. Now back to work. ;-) After setting up doom2 to no sound, it works. Supaplex uses a kind of split screen, the lower part contains time and other status info, the upper part is a 2D scrolling screen. The problem is that under xdosemu, the lower part is scrolling, too where it shouldn't. Pinball Fantasies does not start, I do not know why, maybe because of the network drive? Serf City (Settlers I) starts but its mouse handling is too fast(?): the mouse is too sensitive. Xmas Lemmings: the screen is flashing, movements are too slow. It also uses the split screen VGA feature. Maybe it polls the horizontal retrace too much? Best regards, Zoltán Böszörményi - 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-info.html
Re: Game problem Re: Freshly installed dos-6.22 with disk image doesnot work
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 part is a 2D scrolling screen. The problem is that under xdosemu, the lower part is scrolling, too where it shouldn't. Vga emulation is far from perfection, use dosemu in a console mode instead to get the proper graphics. Pinball Fantasies does not start, I do not know why, maybe because of the network drive? Unlikely. Serf City (Settlers I) starts but its mouse handling is too fast(?): the mouse is too sensitive. Yes, there is something weird with the mouse driver of dosemu. Under console you can use an external mouse driver however. Also try fiddling with emumouse.com. 2. in xterm type xset fp rehash to make your X server to search for the new fonts. But I did neither this not /etc/rc.d/init.d/xfs reload. Today morning I switched on the machine, the font is working, as I expected. But you asked for the way of doing that without restarting an X server, didn't you? Hmm... - 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-info.html
Re: Freshly installed dos-6.22 with disk image does not work
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 1.1.3.7 with just static linking (while investigating why it wouldn't compile I removed all other options using setup-dosemu) and dosemu seems to run OK now. The removed options doesn't necessary lead to any real problems. Removing them only limits the flexibility. So while the goal of setup-dosemu is to let you alter the options, in fact you end up with the default ones, not even knowing about that. - 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-info.html
Re: DOSEMU does not pick up all packets
Hi again. 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 wasn't. ;) * At 2002-11-29T03:40+0300, Stas Sergeev wrote: : | Note that I never actually tried something like that, so it would be | interesting to hear if it works, or what am I missing. I'm having problems compiling the dosnet module in RH8. Gives all sorts of parse errors. I'd paste only I think I fucked with the file already. | I think you have to do bridging to your eth0 device *and* to dsn0 | device. I don't know if this is doable. Would I need some sort of program to tee them together? -- Stian Sletner - 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-info.html
Re: DOSEMU does not pick up all packets
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 there are problems compiling dosnet under RH8. The fix is to get the fresh kernel sources and make a proper symlinks for /usr/include/linux and /usr/include/asm I'd paste only I think I fucked with the file already. Btw, to get the trick working, you'll (most likely) need the latest dosnet (ie from dosemu 1.1.3.4). | I think you have to do bridging to your eth0 device *and* to dsn0 | device. I don't know if this is doable. Would I need some sort of program to tee them together? Hmm, but I supposed your bridging software can do that. Why are you limited with bridging between only 2 interfaces? - 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-info.html
Re: DOSEMU does not pick up all packets
* At 2002-11-29T23:27+0300, Stas Sergeev 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? stian:~$ nice -20 dos -D+P -o dos.debug dos.out 21 dos.debug: debug flags: -a debug flags: +P Sending packet== packet to send: : Dest.=ff:ff:ff:ff:ff:ff: Source=0:40:95:0:3c:31: Type= 3781 PD ERR: AX=0481 BX=03bc CX=003c DX=0c08 FLAGS=00033017 SI=163c DI=164a BP=ff7c SP=ff6e CS=f000 DS=0f90 ES=0f90 SS=17f1 SIGILL while in vm86() ERROR: unexpected CPU exception 0x06 err=0x cr2= while in vm86 (DOS) leavedos(4|0x4) called - shutting down dos.out: Linux kernel 2.4.18; CPU speed is 300676000 Hz Dosemu-1.1.3.7 Running on CPU=586, FPU=1 [?25h[0m[H[2JERROR: unexpected CPU exception 0x06 err=0x cr2= while in vm86 (DOS) Program=sigsegv.c, Line=162 EIP: 8b2e:3669 ESP: 17f1:ff70 VFLAGS(b): 0 0011 0110 EAX: 7ff9 EBX: 000e ECX: 003d EDX: 0733 VFLAGS(h): 3006 ESI: 163c EDI: 164a EBP: ff7c DS: 0f90 ES: 0f90 FS: GS: FLAGS: PF IF RF VM IOPL: 3 STACK: 35 02 e6 19 00 b8 92 ff 15 07 - 13 00 27 13 08 16 90 0f 82 03 OPS : 00 00 00 00 00 40 6a 13 33 01 - ff ff ff ff ff ff 02 00 00 00 8b2e:3669 ??? di | I'm having problems compiling the dosnet module in RH8. | It was already reported that there | are problems compiling dosnet under | RH8. The fix is to get the fresh | kernel sources and make a proper | symlinks for /usr/include/linux and | /usr/include/asm Ah. | Why are you limited with bridging between only 2 interfaces? Well, it only listens on one interface, and packs up the packets in IP and sends them off in UDP through normal networking means. And listens for UDP (IPADDR_ANY) and unpacks and puts them out on the interface. What I'm currently using is SIB, btw. (It's on freshmeat somewhere if you want to look.) -- Stian Sletner - 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-info.html
Newbie with terminal video problems
Hi,
I have xdosemu running fine under gnome but experience the mouse click
problem under kde.
I am attempting to get it running in a terminal and am experiencing some
difficulties.
When I finish my dos session and type exitemu or attempt to switch terminals
or back to x I get some kind of weird lock with my monitor going to non
active mode and my machine inaccessable.
I am running Mandrake 9.0 and the problem occurs both with dosemu 1.1.3.0
and 1.0.2.1
The graphics card is a nvidia tnt 32Mb as such i have used the plainvga
setting for unsupported cards.
I have tried lots of settings in the conf file but so far to no avail.
I have read on one of the old lists that there maybe a bios issue. If this
is the case can someone tell me what may need changing and what it does I
have amibios simple setup utility 1.24k (I don't usually even look in there
as my brother sets up that side of my machine).
Any help would be greatly appreciated.
Any flames for inappropriate newbie behaviour understood.
Paul
PS As an incentive to all my windows me disk is now about 2 programs away
from becoming a drinks coaster {after I've knicked all the dlls for
possible use in wine :)}.
--
There are only 10 types of people in the world those who understand binary
and those who don't
-
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-info.html
