keypresses ignored in dosemu console window
Hello, I am running dosemu with dosemu -t in a console window und KDE. I find that a number of special keys don't work at all: - shift-right and shift-left - ctrl-c, ctrl-e, ctrl-m and several other ctrl-key combinations. This is unfortunate because I need these key-combinations for e.g. foxpro 2.6, quattro pro 5.6 and the freedos - edit.exe. I tried to set $_rawkeyboard = (0) in .dosemurc and in dosemu.conf in combination with starting dosemu as dosemu -t -k ctrl-c does seem to be passed through to the command-prompt, but to any application. can you provide any help or advice? Harry Wyrobnik - 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: differences between xdosemu and dosemu in a console?
i got it it was to simple dosemu -V to force using the card video bios that made everything work On 4/16/07, RobRoy Kelly [EMAIL PROTECTED] wrote: what config differences are there between xdosemu and dosemu what ever xdosemu uses gives me the proper vesa config for graphics and the proper ansi mode dosemu in a virual console which used to work does not. The mouse in xdosemu has tracking problems or i would just use the xdosemu. Do xdosemu and dosemu share the same conf file ? - 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: console problem
On Mon, 5 Sep 2005, UNIREA Sannicolau Mare wrote: Didn't found $term_char variable in your dosemu.conf... I have the latest version of dosemu rpm (1.2.2-1), running on a Fedora Core2 I can't always remember the exact name, you should have been able to see it. Ok! I found it: is called $_term_char_set! What value should I give? well that was step #1 , now if you can just change it to ibm - 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: console problem
Hi! I have a dos program builted in FoxPro - when I run in it console mode ($dosemu), it looks horrible - when I runt it in GUI mode ($xdosemu), it looks perfect Problem is that I want it run in console mode! 1. what do you mean by 'horrible' the font, layout, colors, controls, mode? 2. from other mail you said you have latest 1.2 version this is NOT the latest, fetch the cvs version, it has a number of improvements and bugfixes. (don't expect 1.2 or any other to be stable, it is an emulation soft anyway) CUIN Kaczy - 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: console problem
Didn't found $term_char variable in your dosemu.conf... I have the latest version of dosemu rpm (1.2.2-1), running on a Fedora Core2 Why do you use all old stuff? Many console problems where fixed in later versions. Alain - 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
Fw: console problem
What you have to do is use the VGA font in the console. How to do it... I am trying too. Can anyone help? Alain UNIREA Sannicolau Mare escreveu: Hi! I have a dos program builted in FoxPro - when I run in it console mode ($dosemu), it looks horrible - when I runt it in GUI mode ($xdosemu), it looks perfect Problem is that I want it run in console mode! What can be the problem? - 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: console problem
Hi! I have a dos program builted in FoxPro - when I run in it console mode ($dosemu), it looks horrible - when I runt it in GUI mode ($xdosemu), it looks perfect Problem is that I want it run in console mode! What can be the problem? Did you set the $term_char variable in your dosemu.conf? also could you be using a UTF locale? Didn't found $term_char variable in your dosemu.conf... I have the latest version of dosemu rpm (1.2.2-1), running on a Fedora Core2 - 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: console problem
On Thu, 1 Sep 2005, UNIREA Sannicolau Mare wrote: Hi! I have a dos program builted in FoxPro - when I run in it console mode ($dosemu), it looks horrible - when I runt it in GUI mode ($xdosemu), it looks perfect Problem is that I want it run in console mode! What can be the problem? Did you set the $term_char variable in your dosemu.conf? also could you be using a UTF locale? Didn't found $term_char variable in your dosemu.conf... I have the latest version of dosemu rpm (1.2.2-1), running on a Fedora Core2 I can't always remember the exact name, you should have been able to see it. - 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: console problem
On Wed, 31 Aug 2005, UNIREA Sannicolau Mare wrote: Hi! I have a dos program builted in FoxPro - when I run in it console mode ($dosemu), it looks horrible - when I runt it in GUI mode ($xdosemu), it looks perfect Problem is that I want it run in console mode! What can be the problem? - 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 Did you set the $term_char variable in your dosemu.conf? also could you be using a UTF locale? - 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: Symantec Ghost Console Client under Dosemu
On Sat, 2 Oct 2004, Per von Zweigbergk wrote: On Sat, 2 Oct 2004, Stas Sergeev wrote: Per von Zweigbergk wrote: Dosemu monopolising the network card as well as the hard drive will not be a problem, since the only thing needing those resources would be Ghost itself, which runs under Dosemu. Wouldn't it be better to just stop using linux and install only DOS then? Why do you need linux and dosemu that is monopolizing everything and merely turn yours linux box into a DOS box? Except the network card I have doesn't have Linux drivers. That's the main reason I'm going to be trying this experiment. Correction: I meant the card doesn't have DOS drivers. Sorry for the confusion. (I should proofread my e-mails better.) -- Per von Zweigbergk [EMAIL PROTECTED] - 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: Symantec Ghost Console Client under Dosemu
Hello. Per von Zweigbergk wrote: Wouldn't it be better to just stop using linux and install only DOS then? Except the network card I have doesn't have Linux drivers. That's the main reason I'm going to be trying this experiment. Looks like the reversed logic to me, grrr. If you don't have the linux drivers, then you are of no hopes running it under Linux, no matter whether you use dosemu or not. So, you have the DOS drivers, but no linux drivers, and that makes your argument for trying it under linux instead of the DOS? - 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
Symantec Ghost Console Client under Dosemu
I administer a few Microsoft Windows machines at work. We have recently purchased Symantec Ghost Corporate Edition 8.0 for centralized disk image administration. However, I failed to consider that Ghost requires a DOS-compatible network card when performing remote imaging tasks and other similar stuff. To compensate for this, I thought it might be worth trying to modify Norton Ghost's special boot partition, which is basically just an installation of IBM PC-DOS on a seperate partition, bootstrapped with drivers and the Ghost executable. This boot partition could be modified to use some form of Linux -- probably a customized distribution, or something based on existing boot disks depending on complexity. This would allow me to use Dosemu in single user mode to run Ghost Console Client under Dosemu, conveniently launched through some startup scripts. I would use Dosnet to allow Ghost to access the network card through Linux drivers. The cards in question do have Linux drivers which I have tried and verified that they work using Knoppix. In order for this to work, I have to be able to do the following: 1) The MAC address of seen by Ghost in DOS needs to be the same as the physical MAC address, and outgoing packets need to have the MAC address of the physical card. This is because the Ghost Console identifies computers via their MAC address, and will probably freak out otherwise. I haven't looked closely into Dosnet, but this should probably be doable. Any info on doing this specifically would be helpful. 2) Ghost will probably need to be able just to access the hard drive directly -- without any form of file system redirection drivers or partition table remapping or other forms of hacks. I don't need to be able to access the hard drive from Linux itself -- I can happilly just make a system that does what I want and load it as an initrd ramdisk. (Possibly also using loadlin or other evil things.) I can't seem to find if this is possible in current versions in the HOWTO, although I seem to have seen indications that this at least used to be possible in earlier versions. 3) Ghost Console Client has to be runnable under Dosemu. While this setup will probably be wildly unsupported from Symantec's end, and I haven't seen anybody else on the Internet doing this, I'll be in uncharted terrirory, but I won't really be able to test this until I solve problems 1 and 2. I'm not really an expert programmer when it comes to the sort of code Dosemu is made of, but I might be able to iron out a few wrinkles and hack a few patches if it proves to be necessary. I'd like to hear some opinions on my chances of pulling something like this off. Also, some pointers on my questions above would also be immensely helpful. I'd also like to know if any of the components, specifically Dosnet and direct hard disk access is known to be particularilly flaky. Potential data loss is not an issue, since image files will be backed up to a safe location and all important data is stored remotely on a Samba server running FreeBSD anyway. Finally, although offtopic, if anybody has any alternate suggestions for solving my problem, I'd appreciate to receive some of those as well, as long as those replies are kept off-list in order to keep the mailing list on topic. Thanks in advance! Per von Zweigbergk [EMAIL PROTECTED] - 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: Symantec Ghost Console Client under Dosemu
On Thu, 30 Sep 2004, Stas Sergeev wrote:
So it was removed. Not really, just disabled in
global.conf, AFAICS. You can easily get it back
with a trivial hack in global.conf (or even
without any hacks at all).
you don't even need global.conf -- global.conf syntax also works in
dosemu.conf.
$_hdimage =
disk {wholedisk /dev/hda}
in dosemu.conf (or root's ~/.dosemurc if root runs dosemu) does
the job. Though I had to use $_vbootfloppy (a floppy image) to boot, since
DOSEMU doesn't like GRUB in the MBR (tries to go to protected mode
itself).
It was never really removed, just never supported in the new dosemu.conf
syntax (Feb 98, 0.97.2, over two years before I was involved). But right
now there isn't much of a reason anymore; as it used to be dosemu was
suid-root by default and any user could get the wholedisk (depending on
dosemu.users), now it solely depends on the permissions of /dev/hda.
So I'm not opposed to it, just too lazy to add the support to dosemu.conf
;)
Bart
-
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
Virtual Console
Stas, Here's the latest output from boot.log after running default-configure -d and recompiling DOSEmu: CONF: config variable parser_version_3 set CONF: config variable c_system set CONF: Parsing built-in dosemu.conf file. CONF: config variable version_3_style_used set CONF: Parsing built-in global.conf file. CONF: config variable version_3_style_used unset CONF: config variable version_3_style_used set CONF: opened include file /etc/dosemu/dosemu.conf CONF: closed include file /etc/dosemu/dosemu.conf CONF: mapping driver = 'auto' debug flags: -a+cw CONF: Enabling use of pentium timer CONF: dosbanner on CONF: timer freq=18, update=54925 CONF: CPU set to 586 CONF: 8192k bytes XMS memory CONF: 2048k bytes EMS memory CONF: EMS-frame = 0xe000 CONF: DPMI-Server on CONF: PM DOS API Translator on CONF: dosemu running on console CONF: VGA-BIOS-Segment 0 CONF: VGA-BIOS-Segment set to 0xc000 CONF: VGA-BIOS-Size 0 CONF: VGA-BIOS-Size set to 0xf400 CHIPSET: 11 SER: directory /var/lock namestub LCK.. binary No MOUSE: /dev/gpmdata, type 2 using internaldriver: yes, emulate3buttons: no baudrate: 0 CONF: Keyboard-layout keyb-user CONF: Keyboard-layout auto device: /dev/fd0 type 2 h: 0 s: 0 t: 0 floppy A: CONF: fastfloppy = 1 CONF: IPX support off CONF(LPT0) f: (null) c: lpr o: -Plp t: 20 port: 0 CONF: not allowing speaker port access CONF: Packet Driver disabled. device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C: CONF: config variable c_system unset CONF: running exclusively as ROOT: uid=0 (cached 0) gid=0 (cached 0) DBG_FD already set DOSEMU-1.3.1.0 is coming up on Linux version 2.6.8.1 CONF: reserving 640Kb at 0x0 for 'd' (Base DOS memory (first 640K)) CONF: reserving 64Kb at 0xF for 'r' (Dosemu reserved area) CPU: Stack bottom 0xbfffe000, top 0xc000, esp=0xb8c0 major = 4 minor = 6 CONF: reserving 128Kb at 0xA for 'v' (Video memory) registering /dev/gpmdata for internal_mouse SERIAL $Header: /cvsroot/dosemu/dosemu/src/base/serial/ser_init.c,v 1.9 2004/05/07 13:49:45 stsp Exp $ ERROR: cpu exception in dosemu code outside of VM86()! trapno: 0x00 errorcode: 0x cr2: 0x eip: 0x4013d882 esp: 0xb874 eflags: 0x00013256 cs: 0x0073 ds: 0x007b es: 0x007b ss: 0x007b Division by zero VFLAGS(b): 010011001001010110 EAX: EBX: 4015c590 ECX: 03da EDX: VFLAGS(h): 00013256 ESI: 40161240 EDI: b9f4 EBP: b8b8 CS: 0073 DS: 007b ES: 007b FS: GS: FLAGS: PF AF ZF IF RF IOPL: 3 OOPS : 24 18 8d b3 b0 4c 00 00 56 99 - f7 bb 84 4c 00 00 6a 10 c7 83 System info: libXxf86vm.so.1 = /usr/X11R6/lib/libXxf86vm.so.1 (0x4002b000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x40031000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x4003f000) libgpm.so.1 = /lib/libgpm.so.1 (0x40109000) libvga.so.1 = /usr/lib/libvga.so.1 (0x4010f000) libslang.so.1 = /usr/lib/libslang.so.1 (0x40162000) libm.so.6 = /lib/libm.so.6 (0x401d4000) libdl.so.2 = /lib/libdl.so.2 (0x401f8000) libc.so.6 = /lib/libc.so.6 (0x401fb000) libncurses.so.5 = /lib/libncurses.so.5 (0x40331000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.2.3 Linux believers 2.6.8.1 #1 Wed Aug 18 00:13:53 MDT 2004 i686 unknown unknown GNU/Linux -000a rwxs 00:06 11842 /dev/zero (deleted) 000a-000c rw-s 000a 03:41 458810 /dev/mem 000c-0011 rwxs 000c 00:06 11842 /dev/zero (deleted) 08048000-0817e000 r-xp 03:41 2883692/usr/local/bin/dosemu.bin 0817e000-081ae000 rw-p 00136000 03:41 2883692/usr/local/bin/dosemu.bin 081ae000-084fd000 rw-p 081ae000 00:00 0 4000-40015000 r-xp 03:41 786461 /lib/ld-2.3.2.so 40015000-40016000 rw-p 00014000 03:41 786461 /lib/ld-2.3.2.so 40016000-40017000 r--s 03:41 458810 /dev/mem 4002b000-4002f000 r-xp 03:41 2293856 /usr/X11R6/lib/libXxf86vm.so.1.0 4002f000-4003 rw-p 3000 03:41 2293856 /usr/X11R6/lib/libXxf86vm.so.1.0 4003-40031000 rw-p 4003 00:00 0 40031000-4003e000 r-xp 03:41 2293810 /usr/X11R6/lib/libXext.so.6.4 4003e000-4003f000 rw-p c000 03:41 2293810 /usr/X11R6/lib/libXext.so.6.4 4003f000-40106000 r-xp 03:41 2293820 /usr/X11R6/lib/libX11.so.6.2 40106000-40109000 rw-p 000c6000 03:41 2293820 /usr/X11R6/lib/libX11.so.6.2 40109000-4010e000 r-xp 03:41 786453 /lib/libgpm.so.1.18.0 4010e000-4010f000 rw-p 4000 03:41 786453 /lib/libgpm.so.1.18.0 4010f000-40158000 r-xp 03:41 1703963/usr/lib/libvga.so.1.4.3 40158000-4015d000 rw-p 00049000 03:41 1703963/usr/lib/libvga.so.1.4.3 4015d000-40162000 rw-p 4015d000 00:00 0 40162000
Re: Virtual Console
On Thu, 26 Aug 2004, TP Reitzel wrote: Here's the latest output from boot.log after running default-configure -d and recompiling DOSEmu: Following the last legit line number (in vga.c) it crashes in vga_setpage() in svgalib. What's the chipset you configured svgalib to use? nv3? IMHO being able to use svgalib+dosemu is sheer luck, and highly hardware dependent, that's why it's not compiled in by default. You mentioned though that the only thing you changed was the kernel version right (it worked on 2.4.x but not 2.6.x?) In any case you could try $_chipset = plainvga. No guarantees though, but if the console runs in text mode (no fbdev) that normally works, at least for basic VGA graphics mode, and ctrl-alt-fn flipping with other text consoles. Personally I use fbdev on the console with an ATI card. lspci -vv mentions under :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA]) ... Region 1: I/O ports at c000 [size=256] Respecting this, using plainvga and $_console_pci = (on) $_console_ports = fast range 0xc000,0xc0ff DOSEMU works for me even with fbdev (radeonfb) but vc switching is completely broken (ie. entering dosemu that way temporarily causes Linux to be single-tasking ignoring remote connections), so this still not very nice (I rarely use it, except for comparing bugs in VGAEMU with the real thing, thus avoiding a reboot). Anyway, maybe this gives you some ideas about alternatives. Bart - 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
Virtual Console
I'm getting a blank screen when using DOSEmu 1.3.1 or 1.2.2 with the newer 2.6.x kernels and the virtual console. The screen blanks and DOSEmu silently exits. I need the virtual console with the SVGA driver instead of X with some games. Speaking of games, will someone please add FM synthesis to DOSEmu soon? I'd really prefer to use DOSEmu instead of DOSBox with my DOS games. TIA Slackware 9.1 Dropline GNOME 2.6.1 Kernel 2.6.8.1 nVIDIA GeForce FX5200 _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ - 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: Virtual Console
Hello. TP Reitzel wrote: The screen blanks and DOSEmu silently exits. Have a look into ~/.dosemu/boot.log for info. I need the virtual console with the SVGA driver instead of X with some games. Configuring dosemu for fast VESA under console may be not easy. There are no docs about that and this is a very specific to the particular video card. And if you want LFB - not possible at all (currently). Speaking of games, will someone please add FM synthesis to DOSEmu soon? No but you can try this patch: http://dosemu.sourceforge.net/stas/opl1c.diff And you can also use MIDI if the game supports 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
Virtual Console
Output from boot.log while running virtual console as root with the SVGA library: CONF: config variable parser_version_3 set CONF: config variable c_system set CONF: Parsing built-in dosemu.conf file. CONF: config variable version_3_style_used set CONF: Parsing built-in global.conf file. CONF: config variable version_3_style_used unset CONF: config variable version_3_style_used set CONF: opened include file /etc/dosemu/dosemu.conf CONF: closed include file /etc/dosemu/dosemu.conf CONF: mapping driver = 'auto' debug flags: -a+cw CONF: Enabling use of pentium timer CONF: dosbanner on CONF: timer freq=18, update=54925 CONF: CPU set to 586 CONF: 8192k bytes XMS memory CONF: 2048k bytes EMS memory CONF: EMS-frame = 0xe000 CONF: DPMI-Server on CONF: PM DOS API Translator on CONF: dosemu running on console CONF: VGA-BIOS-Segment 0 CONF: VGA-BIOS-Segment set to 0xc000 CONF: VGA-BIOS-Size 0 CONF: VGA-BIOS-Size set to 0xf400 CHIPSET: 11 SER: directory /var/lock namestub LCK.. binary No MOUSE: /dev/gpmdata, type 2 using internaldriver: yes, emulate3buttons: no baudrate: 0 CONF: Keyboard-layout keyb-user CONF: Keyboard-layout auto device: /dev/fd0 type 2 h: 0 s: 0 t: 0 floppy A: CONF: fastfloppy = 1 CONF: IPX support off CONF(LPT0) f: (null) c: lpr o: -Plp t: 20 port: 0 CONF: not allowing speaker port access CONF: Packet Driver disabled. device: /etc/dosemu/drives/c type 4 h: -1 s: -1 t: -1 drive C: CONF: config variable c_system unset CONF: running exclusively as ROOT: uid=0 (cached 0) gid=0 (cached 0) DBG_FD already set DOSEMU-1.3.1.0 is coming up on Linux version 2.6.8.1 CONF: reserving 640Kb at 0x0 for 'd' (Base DOS memory (first 640K)) CONF: reserving 64Kb at 0xF for 'r' (Dosemu reserved area) CPU: Stack bottom 0xbfffe000, top 0xc000, esp=0xb8c0 major = 4 minor = 6 CONF: reserving 128Kb at 0xA for 'v' (Video memory) registering /dev/gpmdata for internal_mouse SERIAL $Header: /cvsroot/dosemu/dosemu/src/base/serial/ser_init.c,v 1.9 2004/05/07 13:49:45 stsp Exp $ ERROR: cpu exception in dosemu code outside of VM86()! trapno: 0x00 errorcode: 0x cr2: 0x eip: 0x4013d882 esp: 0xb894 eflags: 0x00013256 cs: 0x0073 ds: 0x007b es: 0x007b ss: 0x007b Division by zero VFLAGS(b): 010011001001010110 EAX: EBX: 4015c590 ECX: 03c0 EDX: VFLAGS(h): 00013256 ESI: 40161240 EDI: EBP: 8000 CS: 0073 DS: 007b ES: 007b FS: GS: FLAGS: PF AF ZF IF RF IOPL: 3 OOPS : 24 18 8d b3 b0 4c 00 00 56 99 - f7 bb 84 4c 00 00 6a 10 c7 83 System info: libXxf86vm.so.1 = /usr/X11R6/lib/libXxf86vm.so.1 (0x4002b000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x40031000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x4003f000) libgpm.so.1 = /lib/libgpm.so.1 (0x40109000) libvga.so.1 = /usr/lib/libvga.so.1 (0x4010f000) libslang.so.1 = /usr/lib/libslang.so.1 (0x40162000) libm.so.6 = /lib/libm.so.6 (0x401d4000) libdl.so.2 = /lib/libdl.so.2 (0x401f8000) libc.so.6 = /lib/libc.so.6 (0x401fb000) libncurses.so.5 = /lib/libncurses.so.5 (0x40331000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.2.3 Linux believers 2.6.8.1 #1 Wed Aug 18 00:13:53 MDT 2004 i686 unknown unknown GNU/Linux -000a rwxs 00:06 7074 /dev/zero (deleted) 000a-000c rw-s 000a 03:41 458810 /dev/mem 000c-0011 rwxs 000c 00:06 7074 /dev/zero (deleted) 08048000-0816c000 r-xp 03:41 2883692/usr/local/bin/dosemu.bin 0816c000-0819b000 rw-p 00123000 03:41 2883692/usr/local/bin/dosemu.bin 0819b000-0849f000 rw-p 0819b000 00:00 0 4000-40015000 r-xp 03:41 786461 /lib/ld-2.3.2.so 40015000-40016000 rw-p 00014000 03:41 786461 /lib/ld-2.3.2.so 40016000-40017000 r--s 03:41 458810 /dev/mem 4002b000-4002f000 r-xp 03:41 2293856 /usr/X11R6/lib/libXxf86vm.so.1.0 4002f000-4003 rw-p 3000 03:41 2293856 /usr/X11R6/lib/libXxf86vm.so.1.0 4003-40031000 rw-p 4003 00:00 0 40031000-4003e000 r-xp 03:41 2293810 /usr/X11R6/lib/libXext.so.6.4 4003e000-4003f000 rw-p c000 03:41 2293810 /usr/X11R6/lib/libXext.so.6.4 4003f000-40106000 r-xp 03:41 2293820 /usr/X11R6/lib/libX11.so.6.2 40106000-40109000 rw-p 000c6000 03:41 2293820 /usr/X11R6/lib/libX11.so.6.2 40109000-4010e000 r-xp 03:41 786453 /lib/libgpm.so.1.18.0 4010e000-4010f000 rw-p 4000 03:41 786453 /lib/libgpm.so.1.18.0 4010f000-40158000 r-xp 03:41 1703963/usr/lib/libvga.so.1.4.3 40158000-4015d000 rw-p 00049000 03:41 1703963/usr/lib/libvga.so.1.4.3 4015d000-40162000 rw-p 4015d000 00:00 0 40162000-401b8000 r-xp
Re: Virtual Console
Hello. TP Reitzel wrote: Output from boot.log while running virtual console as root with the SVGA library: [] (gdb) #0 0x402ab399 in waitpid () from /lib/libc.so.6 No symbol table info available. Please run default-configure -d in a source tree and recompile your dosemu to get a debug info in, then retry things. Oh, and if your glibc is compilled without a frame pointers, I am wondering whether the gdb will be able to rewind the stack out of waitpid() even with the debug info for dosemu... - 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: console font problem
Hello If this is on the console, you will have to try issuing the commands I mentioned (charset or setfont depending on what kernel version you have). I tried with setfont -m cp437, but no change I tried also with Stas Sergeev's tip $_external_char_set=utf8 In this case the result was only the @ characters on my screen The only way I realized what I want I chaned in the /etc/sysconfig/i18n file LANG=en_US.UTF-8 to LANG=en_US:en with SYSFONT=latarcyrheb-sun16 and setting my console fonts with setfont -m cp437, but the setfont command allowed only for root, and in this case my dos programs are OK, but I have deranged lines in 'mc' The other problem what I have : when I print tables with my dos programs in place of the tables border's line character appear some ather characters, don't mather if in my screen appear correct or not Alpar - 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: console font problem
Hello. Kovacs Alpar wrote: Sorry, I have redhat 8.0 (it use utf8 encoding), and I tried with $_term_char_set =ibm $_external_char_set = cp437 $_external_char_set must match your locale settings, and uncommenting $_term_char_set is of no use. So try $_texternal_char_set = utf8 - 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: console font problem
On Tue, Apr 20, 2004 at 09:36:13AM +0300, Kovacs Alpar wrote: ^^^ Sorry, I have redhat 8.0 (it use utf8 encoding), and I tried with $_term_char_set =ibm $_external_char_set = cp437 $_internal_char_set = cp437 If this is on the console, you will have to try issuing the commands I mentioned (charset or setfont depending on what kernel version you have). -- Ryan Underwood, [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: console font problem
I searched on this list's archive and I tried with settings listed but the problem persist You didn't mention what settings you tried. ^^^ Sorry, I have redhat 8.0 (it use utf8 encoding), and I tried with $_term_char_set =ibm $_external_char_set = cp437 $_internal_char_set = cp437 ALpar - 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
console font problem
Hi all, I have a problem with console fonts in dosemu(dosemu-1.2.0-1). The Norton Commander and other programs show a deranged screen with strange line characters in console mode. In X-Windows everything is okay. I searched on this list's archive and I tried with settings listed but the problem persist any ideas?? Kovacs Alpar - 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
DOS Console Graphics- not as root
Greetings Programs, I know this has been answered, but I have only found pieces of the solution. I am a newbie to linux, so if you could answer with step-by-step instructions, I'd sure appreciate it. The question? How to run DOS Graphics on console, not as root user? Right now I've got things running great as root. But because this system is used by many different users, I can't just leave the root terminal open. I need users on the machine, to able to run dosemu with the DOS console graphics features available to root, but have those users log in as themselves. I've seen rumors that this is supposed to work --- # addgroup dos # adduser me dos # adduser buddy dos Then, make /usr/bin/dos setuid root and executeable only by group 'dos': # chown root.dos /usr/bin/dosemu # chmod 450 /usr/bin/dosemu Now, only users in group 'dos' can run dosemu and it will run as root. --- I tried this- but no luck. It runs the reduced graphics functional DOS. Am I missing a step? Is this the right approach for addressing this problem? What do I need to do, to properly configure my system? I use the Debian distro. I'm starting with dosemu -kVt Any help would be most appreciated. -Carl Leonard __ Introducing the New Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp - 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: DOS Console Graphics- not as root
On Tue, 6 Apr 2004, C Leonard wrote: How to run DOS Graphics on console, not as root user? I've seen rumors that this is supposed to work --- # addgroup dos # adduser me dos # adduser buddy dos Then, make /usr/bin/dos setuid root and executeable only by group 'dos': # chown root.dos /usr/bin/dosemu # chmod 450 /usr/bin/dosemu Now, only users in group 'dos' can run dosemu and it will run as root. --- I tried this- but no luck. The problem is that /usr/bin/dosemu is a script, and scripts can't (and should not for security reasons) be run suid-root. It runs the reduced graphics functional DOS. Am I missing a step? Is this the right approach for addressing this problem? The program you need to apply this too is /usr/bin/dosemu.bin. You might also need to edit /etc/dosemu/dosemu.users. By default it gives you console graphics only but I think the Debian setup is a little more conservative. If you use dosemu-1.2.0 or higher then it's better (a little more secure) to use sudo (see README.txt, Security), since sudo has the same effect as suid-root for DOSEMU -- will switch back to normal user -- but more fine-grained access checking, and allows you to have one single non-privileged dosemu.bin executable. dosemu -s implies sudo dosemu.bin which detects sudo, drops privileges, and switches back to joeuser. sudo dosemu (if that's allowed) runs dosemu with full root rights. Bart - 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
WP 5.1, graphical preview, in console
Hi, I have been trying out dosemu 1.2. I have used previous versions of dosemu occasionally. I would like to run WordPerfect 5.1 in a console (with no X) and have all the Fkeys work (doing rawkeyboard seems to work) and be able to do the graphical print preview. In previous versions of dosemu, 1.0.2 I think, this would all work except that you had to be root. The graphical part would be messed up if you were a non root user. I have an ati rage video card. I installed the binary distribution. Right now I cannot get the graphics mode to work in the console, as either root or non-root. I have tried a number of different configuration settings. Has anyone else gotten graphics mode to work from the console, or do you all use it from in X windows ? --Rob - 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: WP 5.1, graphical preview, in console
Justin == Justin Zygmont [EMAIL PROTECTED] writes: Justin Justin did you set your $_console=1 and $_graphics=1 in dosemu.conf? Yes. Actually it is conf/dosemurc in the precompiled distribution. I also set $_video = vga, $_rawkeyboard = (1), $_vbios_post = (1), $_chipset = ati and also tried $_chipset = plainvga, and various combinations of those. Does graphics from the console work for you ? Are you using the binary distribution, or did you compile it from source ? If so, did you edit compiletime-settings at all ? --Rob - 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: WP 5.1, graphical preview, in console
On 25 Jan 2004, Rob Ristroph wrote: Justin == Justin Zygmont [EMAIL PROTECTED] writes: Justin Justin did you set your $_console=1 and $_graphics=1 in dosemu.conf? Yes. Actually it is conf/dosemurc in the precompiled distribution. I also set $_video = vga, $_rawkeyboard = (1), $_vbios_post = (1), $_chipset = ati and also tried $_chipset = plainvga, and various combinations of those. Does graphics from the console work for you ? Are you using the binary distribution, or did you compile it from source ? If so, did you edit compiletime-settings at all ? not sure about wp 5.1 but console graphics work for most programs for me. I compiled my own, but I don't see why that should really matter. I have a custom download you can try if you want to see: ftp://solarflow.dyndns.org How about xdosemu? if that won't do the graphics, I don't know what will. - 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
No console.
Hi people. I have a strange message: no console So, if I run dosemu, I can type in the console, but if I run xdosemu, i don't can type anything. Do you can help me? Regards _ Charla con tus amigos en línea mediante MSN Messenger: http://messenger.yupimsn.com/ - 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: fonts in console dosemu
I'd like to know how to get my fonts in a console session of session to look decent. Right now, line draw and fill characters look terrible. easiest way is run as root with $_rawkeyboard, $_console $_graphics on, i guess. For text-mode you should try $_term_char_set=ibm []s Anderson Pereira Ataides - 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: fonts in console dosemu
I'm sure this has been asked many times before. I'd like to know how to get my fonts in a console session of session to look decent. Right now, line draw and fill characters look terrible. I know that one! The ibm character set: $_term_char_set = ibm pbs Peter B. Steiger Cheyenne, WY - 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: fonts in console dosemu
Bart Oldeman wrote: On Mon, 30 Jun 2003, Anderson Pereira Ataides wrote: I'd like to know how to get my fonts in a console session of session to look decent. Right now, line draw and fill characters look terrible. easiest way is run as root with $_rawkeyboard, $_console $_graphics on, i guess. For text-mode you should try $_term_char_set=ibm and if that fails, then you should try setfont default8x16 before starting dosemu. $_graphics is somewhat tricky (depening on hardware) if you use fbdev instead of the 80x25 text mode on the console. Bart try to set $_term_char_set = ibm $_external_char_set = cp437 $_internal_char_set = cp437 $_video = vga # one of: plainvga, vga, ega, mda, mga, cga $_console = (0) # use 'console' video $_graphics = (0)# use the cards BIOS to set graphics $_videoportaccess = (0) # allow videoportaccess when 'graphics' enabled $_vbios_seg = (0xc000) # set the address of your VBIOS (e.g. 0xe000) $_vbios_size = (0x1)# set the size of your BIOS (e.g. 0x8000) $_vmemsize = (1024) # size of regen buffer $_chipset = plainvga # one of: plainvga, trident, et4000, diamond, avance somehow console video and graphics mess with pseudo graphics i am from bulgaria and upper options is here: $_term_char_set = latin1 $_external_char_set = cp855 $_internal_char_set = cp855 this work perfect with pseudo graphics on paradox4.5 and cyrllic font on my console dosemu version is 1.1.4.0, in older versions i dont have succes with pseudo-graphics and my language -- no pain no gain - 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: fonts in console dosemu
Ralph Alvy wrote: I'm sure this has been asked many times before. I'd like to know how to get my fonts in a console session of session to look decent. Right now, line draw and fill characters look terrible. Okay, here's the upshot after reading all your replies (many thanks!). Only one setting was needed: $_graphics (1). Of course that means I can only run that as root (or it has no effect). No other settings talked about here helped, other than that one. I also find that Shift Tab does indeed work, as long as I use rawkeyboard. Thanks again. - 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
fonts in console dosemu
I'm sure this has been asked many times before. I'd like to know how to get my fonts in a console session of session to look decent. Right now, line draw and fill characters look terrible. - 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
dosemu console video
Hi, if I have two dosemu started on the consoles and I use $_console = 1 the ipx is down after about 5 minutes on one of the consoles the other dosemu is still good, if $_console = 0 they are good. Is it fixed in newer dosemu ? I use woody and dosemu 1.0.2 I'd like to use the console video and several dosemu simultaneously thank you -- - - A t t i l a :: [EMAIL PROTECTED] :: S z a b o - - - 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: odd console fonts persist
Claudia Neumann writes: Claudia Is there another trick to change the font? What about this $_term_char_set= $_external_char_set = iso8859-1 $_internal_char_set = cp437 and maybe 'charset G0 iso01' command. -- Sergey Suleymanov - 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
console fonts problem / .dosemurc-file
Hi all, Hi Bart, Next step: try setfont drdos8x16 before starting dosemu (using $_term_char_set=ibm / $_external_char_set = cp437). I don't seem to have drdos*x16-fonts in Mandrake 8.1! I copied drdos*x16.psfu.gz from Suse 8.0 kbd.rpm, but Mandrake doesn't like psfu.gz-font-files. Do you know, how I can convert them to psf.gz-file? But perhaps it is not so important anymore. I did the logging and discovered, that dosemu used a .dosemurc-file I didn't know, that it existed. So every change in the dosemu.conf-file I made had no effect because of the .dosemurc-file. So I deleted the file. The Norton Commander looks better now with $_term_char_set=ibm $_external_char_set = $_internal_char_set = The double lines are double lines, only the edges are still same odd characters. But now I can't use Umlaute. I still have to try same other configurations. But then I noticed, there came up the .dosemurc-file with a copy of the /etc/dosemu/dosemu.conf-File of the next time I started dosemu after I deleted the file. So now I have to delete the .dosemurc-file first, before I change the /etc/dosemu/dosemu.conf-file. Odd. Is there another bug? I check the other configurations shortly. Regards Claudia - 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: console fonts problem / .dosemurc-file
On Mon, 3 Feb 2003, Claudia Neumann wrote: Next step: try setfont drdos8x16 before starting dosemu (using $_term_char_set=ibm / $_external_char_set = cp437). I don't seem to have drdos*x16-fonts in Mandrake 8.1! I copied drdos*x16.psfu.gz from Suse 8.0 kbd.rpm, but Mandrake doesn't like psfu.gz-font-files. Do you know, how I can convert them to psf.gz-file? I don't know, but there might be other fonts in /usr/lib/kbd/consolefonts that might be suitable. The double lines are double lines, only the edges are still same odd characters. But now I can't use Umlaute. I still have to try same other configurations. But then I noticed, there came up the .dosemurc-file with a copy of the /etc/dosemu/dosemu.conf-File of the next time I started dosemu after I deleted the file. So now I have to delete the .dosemurc-file first, before I change the /etc/dosemu/dosemu.conf-file. Odd. Is there another bug? Hmm, did dosemu ask you the following? Going to install your private DOSEMU files into the directory $HOME/dosemu Enter an empty string to confirm, a new path, or none (without the quotes) if you don't want this: that however should not happen if you just delete ~/.dosemurc since we only copy if: if [ ! -f $HOME/.dosemurc -a -f $BPATH_FILE -o ! -f $HOME/.dosemu/disclaimer ]; then i.e. either ~/.dosemurc does not exist but ~/.dosemu/bindist_path exists (then it tells you an upgrade story) or ~/.dosemu/disclaimer does not exist (then it asks you the question I wrote above) Can you check that you're not using an old 'dosemu' script? I'll probably do something about the situation in any case (it violates the principle of the least surprise) by just putting/adjusting $_hdimage in ~/.dosemurc and adding a comment that other things can be adjusted (see systemwide dosemu.conf), rather than copying the dosemu.conf over to .dosemurc. Bart - 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
console font problem
Hi all, Hi Bart,
now I tried in /etc/dosemu/dosemu.conf and deleting /home/praxis/.dosemurc:
$_term_char_set=ibm
$_external_char_set=cp437
$_internal_char_set=cp437
Norton Commander looks good, no Umlaute, instead {:.- etc.
$_term_char_set=ibm
$_external_char_set=
$_internal_char_set=
the same as above
$_term_char_set=ibm
$_external_char_set=cp850
$_internal_char_set=cp850
Norton Commander deranged, äöü okay, but ÄÖÜ wrong.
$_term_char_set=latin
deranged
$_term_char_set=latin1
deranged.
I attached the dosemu.log with dosemu -D+v which had the configuration:
$_term_char_set=ibm
$_external_char_set=
$_internal_char_set=
Regards
Claudia
CONF: config variable parser_version_3 set
CONF: config variable c_system set
CONF: Parsing built-in dosemu.conf file.
CONF: config variable version_3_style_used set
CONF: Parsing built-in global.conf file.
CONF: config variable version_3_style_used unset
CONF: config variable version_3_style_used set
CONF: opened include file /etc/dosemu/dosemu.conf
CONF: closed include file /etc/dosemu/dosemu.conf
CONF: opened include file /home/praxis/.dosemurc
CONF: closed include file /home/praxis/.dosemurc
CONF: config variable skip_dosrc set
CONF: mapping driver = 'mapshm'
debug flags: -D+v
CONF: Disabling use of pentium timer
CONF: dosbanner on
CONF: timint on
CONF: timer freq=18, update=54925
CONF: CPU set to 586
CONF: 8192k bytes XMS memory
CONF: 2048k bytes EMS memory
CONF: EMS-frame = 0xe000
CONF: DPMI-Server on
CONF: dosemu running on console
SER: directory /home/praxis/dosemu/lock/christian namestub LCK.. binary No
MOUSE: /dev/mouse type 7 using internaldriver: yes, emulate3buttons: no baudrate: 0
CONF: Keyboard-layout keyb-user
CONF: Keyboard-layout de-latin1
device: /dev/fd0 type 2 h: 0 s: 0 t: 0 floppy A:
CONF: fastfloppy = 1
CONF: IPX support off
CONF(LPT0) f: (null) c: lpr o: -Plp %s t: 20 port: 378
CONF: not allowing speaker port access
CONF: Packet Driver disabled.
device: /home/praxis/dosemu/win98 type 4 h: -1 s: -1 t: -1 drive C:
CONF: config variable c_system unset
CONF: mostly running as USER: uid=503 (cached 503) gid=503 (cached 503)
CONF: Warning: PCI requires root, disabled
video_mem_charset=cp437
output_charset=terminal_cp437
DBG_FD already set
DOSEMU-1.1.4.9 is coming up on Linux version 2.4.8-26mdk
CONF: reserving 640Kb at 0x0 for 'd' (Base DOS memory (first 640K))
CONF: reserving 64Kb at 0xF for 'r' (Dosemu reserved area)
major = 4 minor = 1
VID: Setting windows size to li=25, co=80
VID: Video set to Video_term
VID: config.dualmon=0
VID: terminal_initialize() called
mapping internal characters to terminal characters:
mapping: - 0020 -
mapping: - 263a -
mapping: - 263b -
mapping: - 2665 - h
mapping: - 2666 - d
mapping: - 2663 - c
mapping: - 2660 - s
mapping: - 2022 - ù
mapping: - 25d8 - ²
mapping: - 25cb - o
mapping:
- 25d9 - ±
mapping: - 2642 - ¢
mapping: - 2640 -
mapping:
- 266a - û
mapping: - 266b - ï
mapping: - 263c - *
mapping: - 25ba -
mapping: - 25c4 -
mapping: - 2195 -
mapping: - 203c - º
mapping: - 00b6 - ã
mapping: - 00a7 -
mapping: - 25ac - þ
mapping: - 21a8 - ¨
mapping: - 2191 - ô
mapping: - 2193 - õ
mapping: - 2192 - ¯
mapping: - 2190 - ®
mapping: - 221f - À
mapping: - 2194 - Í
mapping: - 25b2 - ^
mapping: - 25bc - v
mapping: - 0020 -
mapping: ! - 0021 - !
mapping: - 0022 -
mapping: # - 0023 - #
mapping: $ - 0024 - $
mapping: % - 0025 - %
mapping: - 0026 -
mapping: ' - 0027 - '
mapping: ( - 0028 - (
mapping: ) - 0029 - )
mapping: * - 002a - *
mapping: + - 002b - +
mapping: , - 002c - ,
mapping: - - 002d - -
mapping: . - 002e - .
mapping: / - 002f - /
mapping: 0 - 0030 - 0
mapping: 1 - 0031 - 1
mapping: 2 - 0032 - 2
mapping: 3 - 0033 - 3
mapping: 4 - 0034 - 4
mapping: 5 - 0035 - 5
mapping: 6 - 0036 - 6
mapping: 7 - 0037 - 7
mapping: 8 - 0038 - 8
mapping: 9 - 0039 - 9
mapping: : - 003a - :
mapping: ; - 003b - ;
mapping: - 003c -
mapping: = - 003d - =
mapping: - 003e -
mapping: ? - 003f - ?
mapping: @ - 0040 - @
mapping: A - 0041 - A
mapping: B - 0042 - B
mapping: C - 0043 - C
mapping: D - 0044 - D
mapping: E - 0045 - E
mapping: F - 0046 - F
mapping: G - 0047 - G
mapping: H - 0048 - H
mapping: I - 0049 - I
mapping: J - 004a - J
mapping: K - 004b - K
mapping: L - 004c - L
mapping: M - 004d - M
mapping: N - 004e - N
mapping: O - 004f - O
mapping: P - 0050 - P
mapping: Q - 0051 - Q
mapping: R - 0052 - R
mapping: S - 0053 - S
mapping: T - 0054 - T
mapping: U - 0055 - U
mapping: V - 0056 - V
mapping: W - 0057 - W
mapping: X - 0058 - X
mapping: Y - 0059 - Y
mapping: Z - 005a - Z
mapping: [ - 005b - [
mapping: \ - 005c - \
mapping: ] - 005d - ]
mapping: ^ - 005e - ^
mapping: _ - 005f - _
mapping: ` - 0060 - `
mapping: a - 0061 - a
mapping: b - 0062 - b
mapping: c - 0063 - c
mapping: d - 0064 - d
mapping: e - 0065 - e
mapping: f - 0066 - f
mapping: g - 0067 - g
mapping: h - 0068 - h
mapping: i - 0069 - i
mapping: j - 006a - j
Re: console font problem
On Mon, 3 Feb 2003, Claudia Neumann wrote:
now I tried in /etc/dosemu/dosemu.conf and deleting /home/praxis/.dosemurc:
$_term_char_set=ibm
$_external_char_set=cp437
$_internal_char_set=cp437
Norton Commander looks good, no Umlaute, instead {:.- etc.
this is because your S-Lang library is broken. Mine is broken too. I'm
really not very happy about this as I thought we could by now trust the
system S-Lang but apparently not.
What happened is that the SLsmg_Display_Eight_Bit variable is completely
ignored by the slang library I have here (1.4.4). My self-compiled slang
(1.4.7) is doing it OK, so you could check if updated slang and
slang-devel libraries are available somewhere.
Now the quickdirty workaround:
in any fairly dosemu source =1.1.4.3 you'll find
src/lib/libarch_linux_slang-elf.a
what you need to do is to copy this file to
src/lib/libslang.a
in your current DOSEMU source tree. Then type make and the umlauts should
work.
Bart
-
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
console font problem not eliminated
Hi all, hi Bart, I upgraded to dosemu-1.1.4.9 and used your patch, but - I am sorry to say - it didn't change anything. In the Norton Commander the vertical lines are still big i and the horizontal lines -, the edges use some sort of A. Shall I use same other console font? Regards Claudia - 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: console font problem not eliminated
Hello. Bart Oldeman wrote: $_term_char_set=ibm $_external_char_set = $_internal_char_set = That works for me now (with that patch). Hmm, this doesn't look correct. At least for those who have different internal and external charsets (me) this doesn't work. IIRC Eric suggests to comment out $_term_char_set entirely and use only other two options, which is what works for me perfectly. So, unless I am missing something, $_term_char_set is absolete and is used in the new kbd code only for compatibility purposes (is this correct?) - 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: console font problem not eliminated
On Fri, 31 Jan 2003, Stas Sergeev wrote: Bart Oldeman wrote: $_term_char_set=ibm $_external_char_set = $_internal_char_set = That works for me now (with that patch). Hmm, this doesn't look correct. At least for those who have different internal and external charsets (me) this doesn't work. yes, but I was just trying to ask about the simplest configuration for terminal-in-console for which you should be able to get the box characters. IIRC Eric suggests to comment out $_term_char_set entirely and use only other two options, which is what works for me perfectly. So, unless I am missing something, $_term_char_set is absolete and is used in the new kbd code only for compatibility purposes (is this correct?) essentially, yes. $_term_char_set = ibm is equivalent to: $_external_char_set = cp437 $_internal_char_set = cp437 also, if *everything* is commented out then ibm is the default on the console (latin is the default via network or xterm). The bug was that with $_external_char_set = cp437, DOSEMU forgot to do the equivalent of echo -e '\033(U' which effectively selects cp437 on the Linux console. This doesn't seem to help the OP though ... Bart - 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
console font problem
Hi all, I have a problem with console fonts in dosemu. The Norton Commander and other programs show a deranged screen with strange line characters in console mode. In X-Windows everything is okay. The RPM-Package with dosemu-1.0.2 is okay in console mode. Dosemu-1.1.3, 1.1.3.7, 1.1.4 and 1.1.4.6 all show the strange characters in console mode. I tried all modes in dosemu.conf with $_term_char_set = ibm, latin, latin1 $_external_char_set = , iso8859-1, iso8859-15 $_internal_char_set = cp437, cp850 in console mode its all the same. I even tried echo -ne '\033(U' without any change. Do I have to change the console fonts? Specs: Mandrake Linux release 8.1 (Vitamin) for i586 Kernel 2.4.8-26mdk on an i686 Any ideas? Claudia - 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
VESA in console
Are there any special procedures needed to get VESA working in the linux console, other than a kernel with VESA support(and a VESA resoulution) In the console i get a standard no VESA driver available, and in X running with xdosemu it works fine. - 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: VESA in console
On Tue, 24 Sep 2002, Michael wrote: Are there any special procedures needed to get VESA working in the linux console, yes. other than a kernel with VESA support(and a VESA resoulution) well the way it works now it completely bypasses the kernel. AFAIK with a kernel with VESA (lfb) support you can just switch to a preset resolution at boot time and NEVER again. In the console i get a standard no VESA driver available, and in X running with xdosemu it works fine. Yes. In X, VESA is provided by DOSEMU itself, and then works using *emulated* registers. In the console, VESA is provided by the card's video BIOS, using *real* registers. This is why xdosemu works for everyone in the same way but the console stuff is hardware dependent. Bart - 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: Keymaps SHIFT+F2 with ssh and dosemu console
Dear all, To resume : # Control keys # -- keycode 60 = F2 F112 control keycode 60 = F122 control alt keycode 60 = Console_2 String F2=\033[[B String F112=\036s\033[[B String F122=\036c\033[[B keycode 61 = F3 F113 control keycode 61 = F123 control alt keycode 61 = Console_3 String F3=\033[[C String F113=\036s\033[[C String F123=\036c\033[[C In that case the F2 and SHIFT+F2 keys work fine under dosemu ( by ssh), NOT the F2 and the SHIFT+F23 Keys If I put the configuration of keycode 61 before then the F3 and SHIFT+F3 keys work fine but not the F2 and the SHIFT+F2 !! How can I do ? I really need a solution or some help. Thanx in advance. Lionel - 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: Keymaps SHIFT+F2 with ssh and dosemu console
On Thu, 2002-04-25 at 06:16, Sergey Suleymanov wrote:
dosemu writes:
dosemu Dear all, I try to use SHIFT keys with dosemu in console mode
dosemu by a ssh connection and I use loadkeys on the source to do
dosemu this with the configuration :
Dosemu 1.0.x recognize Shift+F2 as F12 key. You may patch it:
--- dosemu-1.0.2.orig/src/base/keyboard/keyb_slang.c
+++ dosemu-1.0.2/src/base/keyboard/keyb_slang.c
@@ -432,32 +460,36 @@
{^(k8), KEY_F8}, /* F8 */
{^(k9), KEY_F9}, /* F9 */
{^(k;), KEY_F10}, /* F10 */
- {^(F1), KEY_F11}, /* F11 */
- {^(F2), KEY_F12}, /* F12 */
+ {^(F1), KEY_F1 | SHIFT_MASK}, /* F11 aka Shift F1 */
+ {^(F2), KEY_F2 | SHIFT_MASK}, /* F12 aka Shift F2 */
{^(kI), KEY_INS}, /* Ins */
{^(#3), KEY_INS|SHIFT_MASK}, /* Shift Insert */
This is a piece of my dosemu-keymap for linux terminal:
keycode 60 = F2
shift keycode 60 = F12
control keycode 60 = F22
alt keycode 60 = F32
altgr shift keycode 60 = F12
altgr control keycode 60 = F22
altgr alt keycode 60 = F32
control alt keycode 60 = Console_2
altgr control alt keycode 60 = Console_2
altgr shift control alt keycode 60 = Console_2
string F12 = \033[24~
string F22 = \036c\0362
string F32 = \036a\0362
--
Sergey Suleymanov
-
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
Dear All,
With this configuration :
keycode 60 = F2 F112
control keycode 60 = F122
control alt keycode 60 = Console_2
String F2=\033[[B
String F112=\036s\033[[B
String F122=\036c\033[[B
IT WORK FINE !! : the F2 and the SHIFT + F2
BUT If I need to add ( and I must to add) another key or some keys like :
Keycode 61 = F3 F113
control keycode 61 = 123
control alt keycode 61 = Console_3
String F3=\033[[C
String F113=\036s\033[[C
String F123=\036c\033[[C
THEN... the F3 and SHIFT+F3 keys work fine but th F2 and the SHIFT+F2
doesn't work ??!!!
Could you help me please
Lionel
-
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
Keymaps SHIFT+F2 with ssh and dosemu console
Dear all, I try to use SHIFT keys with dosemu in console mode by a ssh connection and I use loadkeys on the source to do this with the configuration : test : keycode 60 = F2 F112 control keycode 60 = F122 alt keycode 60 = F132 control alt keycode 60 = Console_2 String F2=\033[[B String F122=\036s\033[[B String F132=\036c\033[[B loadkeys test Could you help me Why it doesn't work ? Thanx in advance. Lionel - 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: Keymaps SHIFT+F2 with ssh and dosemu console
dosemu writes:
dosemu Dear all, I try to use SHIFT keys with dosemu in console mode
dosemu by a ssh connection and I use loadkeys on the source to do
dosemu this with the configuration :
Dosemu 1.0.x recognize Shift+F2 as F12 key. You may patch it:
--- dosemu-1.0.2.orig/src/base/keyboard/keyb_slang.c
+++ dosemu-1.0.2/src/base/keyboard/keyb_slang.c
@@ -432,32 +460,36 @@
{^(k8), KEY_F8}, /* F8 */
{^(k9), KEY_F9}, /* F9 */
{^(k;), KEY_F10}, /* F10 */
- {^(F1), KEY_F11}, /* F11 */
- {^(F2), KEY_F12}, /* F12 */
+ {^(F1), KEY_F1 | SHIFT_MASK}, /* F11 aka Shift F1 */
+ {^(F2), KEY_F2 | SHIFT_MASK}, /* F12 aka Shift F2 */
{^(kI), KEY_INS}, /* Ins */
{^(#3), KEY_INS|SHIFT_MASK}, /* Shift Insert */
This is a piece of my dosemu-keymap for linux terminal:
keycode 60 = F2
shift keycode 60 = F12
control keycode 60 = F22
alt keycode 60 = F32
altgr shift keycode 60 = F12
altgr control keycode 60 = F22
altgr alt keycode 60 = F32
control alt keycode 60 = Console_2
altgr control alt keycode 60 = Console_2
altgr shift control alt keycode 60 = Console_2
string F12 = \033[24~
string F22 = \036c\0362
string F32 = \036a\0362
--
Sergey Suleymanov
-
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
Font problems on console
I'm a bit new to dosemu and I'm having a font problem when running a text mode dos app. from the console. This program starts up with sort of a textured background (maybe ASCII 0xB1H). Using xdosemu it looks fine but with regular dosemu from the console the background characters are % (percent) chars. What am I doing wrong? -- Ray - 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: Font problems on console
On Fri, Feb 08, 2002 at 02:39:40PM +0800, Albert Loo wrote: Try changing dosemu.conf -- $_term_char_set = to -- $_term_char_set = ibm Thanks Albert, worked like a charm. -- Ray - 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
No access from linux-console to dos with DOSEMU 1.0.2
Hi there, after upgrading my DOSEmu from 1.0.1 to 1.0.2 on Linux SuSE 7.2, I can't access the DOSEMU from the linux-console like: dos -D -a -I'keystroke echo hello world\r' Further I cannot find the file dosexec in /usr/bin/ as where it was in 0.x Versions. Is there a compareable program in the newer versions ? -- Set the controls to the heart of the sun Peter - 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: Two questions: Number Pad and Terminal/Console
On Sun, 13 Jan 2002, pesarif wrote: On Sun, 13 Jan 2002 10:40, Stas Sergeev wrote: Edward Mendelson wrote: and I hope someday it becomes possible to use hardware graphics as an ordinary user, not as root. Will anyone being implementing this soon? Obvious statement --- Are You Volunteering? I would like full-screen, fast, console graphics, as an ordinary user, as well. It is possible under X. - But, I just have to mention that it's really slow (as are all fully-software emulated things). X can give you direct framebuffer access, but no ports, and cannot (yet) switch bpp. If your X is running at 8bpp and your DOS program also wants 8bpp (and maybe also the same resolution as X), then it could run quickly. Completely direct ports access you simply can't get as an ordinary user. A client-server approach could work but then the server, at the very least needs root privileges at start-up. Moreover each port access needs to be catched by the client, and then forwarded to the server - giving a lot of overhead for some (but not all) video modes. Also there is the (new) svgalib approach with a device in /dev/svga for which you can then give a user privileges. However giving a user full access to the video card means giving her/him an ability to crash the system, even if logged in remotely, just like it is now possible with suid-root dosemu. So that does not help a lot. The client-server might appear in DOSEMU in the future, but don't hold your breath. Bart - 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
Two questions: Number Pad and Terminal/Console
As a newcomer to this list, let me first say that DOSEMU is an amazing achievement. VMware costs a huge sum and doesn't support VESA graphics, and runs slowly. DOSEMU runs at top speed, supports VESA graphics, and is amazingly flexible. Many thanks to everyone who helped put to together. Two questions (I'm running 1.0.2.1 under Red Hat Linux 7.2, with MS-DOS 6.22 as the DOS version): 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) line in doemurc, I was able to get the number pad plus and minus keys to work properly - but only if I toggled on the NumLock key before starting DOSEMU. In other words, the NumLock key seems to produce the opposite effect of the one it should have - with NumLock OFF, the Plus and Minus keys produced plus and minus signs; with NumLock ON, they scrolled up and down one screen in WPDOS. Is this a bug? (I reported as one to [EMAIL PROTECTED], but maybe I'm just misunderstanding something in the configuration). Second, I'm having a lot of trouble getting DOSEMU to work well in an ordinary terminal (./dosemu, not ./xdosemu) or in the console. In a terminal, WPDOS tends to lock up quickly, or the function keys seem not to work at all. In the console, the unshifted function keys work well, but Shift-F1 gets interpreted by WPDOS as Shift-F3, Shift-F2 gets interpreted as Shift-F4, etc. The Alt- and Ctrl- function keys seem not to work as expected at all. Also, in the console, I can't figure out how to tell DOSEMU to use the box drawing characters in hardware instead of the replacment characters that get used instead. Is there a fix for this? Finally, I've experienced the same bug reported elsewhere on this list in which DOSEMU shuts down after giving one or two commands, and I hope someday it becomes possible to use hardware graphics as an ordinary user, not as root. Thanks again for any advice, and for a splendid program. Edward Mendelson - 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: Two questions: Number Pad and Terminal/Console
On Sun, 13 Jan 2002 10:40, Stas Sergeev wrote: Edward Mendelson wrote: and I hope someday it becomes possible to use hardware graphics as an ordinary user, not as root. Will anyone being implementing this soon? I would like full-screen, fast, console graphics, as an ordinary user, as well. It is possible under X. - But, I just have to mention that it's really slow (as are all fully-software emulated things). Thanks, pesarif - 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
