linux-msdos-digest Wednesday, 21 July 1999 Volume 01 : Number 150 In this issue: ---------------------------------------------------------------------- From: Petr Hlustik <[EMAIL PROTECTED]> Date: Fri, 9 Jul 1999 11:27:11 -0400 Subject: Re: dosemu can't access font vga On Fri, Jul 09, 1999 at 01:56:53PM +0200, Steffen Winterfeldt wrote: > > On Thu, 8 Jul 1999, Petr Hlustik wrote: > > > > [...] > > > > > ERROR: X: Unable to open font "vga"ERROR: , trying "vga"... > > > ERROR: X: Unable to open font "vga"ERROR: , trying "9x15"... > > You probably forgot to rebuild the font info; running something like > > mkfontdir /usr/X11/lib/X11/fonts/misc > xset fp rehash You were right. I've done mkfontdir before but I forgot the xset fp rehash step. That gets rid of the ERROR: X message. But the DOSemu window still dies shortly and -debug shows the persistence of the deeper problem: VT_ACTIVATE: Operation not permitted. As I wrote before, this happens even when running dos on the console and even as root. Thanks for your ideas, Petr ------------------------------ From: Doug Springer <[EMAIL PROTECTED]> Date: Fri, 09 Jul 1999 18:15:52 -0600 Subject: DOS Emu bug? PQ magic A quick note-I tried something I did not expect to work-Partition magic 3.0x-their DOS version, and Dosemu exited. Here are the details: Linux DOS emulator 0.98.7.0 ERROR: general protection at 0x1311f: 66 ERROR: SIGSEGV, protected insn...exiting! Running a DOS 6.22 from a boot floppy. I hope this helps. - -Doug ------------------------------ From: "Robert de Bath" <[EMAIL PROTECTED]> Date: Sat, 10 Jul 1999 16:11:18 +0100 (BST) Subject: Terminal Emulator for DOSEMU Many of you will know about a small DOS terminal emulator I wrote a _long_ time ago that I've modified to support DOSEMU special keys directly. Just about every key combination you can get into DOSEMU is generated by pressing that key combination in this emulator. I've recently altered it to work directly with either a BIOS serial driver or across a telnet connection using the WATTCP library. In addition I've improved further the originally very good serial performace with the hardware RS-232 driver; It is usable at 115k2 on _any_ PC (4.77Mhz!) and should work well on an 286 over about 8Mhz, it doesn't need flow control on a 286/16! Personally I use it on an AMD 286/16 in a very nice little Bicom 260i. It's available from my web page at http://www.cix.co.uk/~mayday - -- Rob. (Robert de Bath <http://poboxes.com/rdebath>) <rdebath @ poboxes.com> <http://www.cix.co.uk/~mayday> ------------------------------ From: Steffen Winterfeldt <[EMAIL PROTECTED]> Date: Sat, 10 Jul 1999 18:28:17 +0200 (MEST) Subject: Re: dosemu can't access font vga On Fri, 9 Jul 1999, Petr Hlustik wrote: > > You were right. I've done mkfontdir before but I forgot the xset fp rehash > step. That gets rid of the ERROR: X message. But the DOSemu window still > dies shortly and -debug shows the persistence of the deeper problem: > > VT_ACTIVATE: Operation not permitted. You mean, you get this error even when running xdos??? > As I wrote before, this happens even when running dos on the console and > even as root. I suppose there may be something wrong with your pre-build DOSEMU. You might be better off getting your own version from dosemu.org. The current versions are 0.98.8 ('stable') and 0.99.13 (developer). I've tested both on libc5 and glibc 2.0/2.1 systems. Steffen ------------------------------ From: Niels Ott <[EMAIL PROTECTED]> Date: Sun, 11 Jul 1999 21:58:47 +0200 Subject: Some problems running Simcity 2000 Hi There! I want to run SimCity 2000. It almost works but doesn't display a mouse pointer. The game doesn't complain about having no mouse so the (internal) mouse driver seems to be loaded and working?! The mouse works well with some programs, VGA too. My PC: Matrix Mystique Grapics Adaptor MS Busmouse AMD K6 233 Mhz SuSE Linux 6.0 with Kernel 2.2.5 MS DOS 6.22 I didn't subscribe to the list, please put me into Cc: in case you want to answer. Anybody any ideas? TIA, Niels - -- Wer nicht an Wunder glaubt, ist kein Realist. - -> http://www.tomix.de/niels/ ------------------------------ From: David Anderson <[EMAIL PROTECTED]> Date: Mon, 12 Jul 1999 03:25:23 -0400 Subject: Need to share modem with 4 DOS programs I haven't been able to find anything about modem sharing between dosemu sessions. I've gone through the list archives and documentation in the tarball, so now I ask here hoping that someone has an answer. I need to be able to share one modem for outgoing calls between atleast 4 DOSEMU sessions under Linux. The programs only need occasional access to the modem, and this application is working ( when it dosen't crash) under windows currently. Under windows, the program checks to see if it can open the comport and then proceeds or gives a 'modem unavailable' message. I hope to duplicate that under dosemu, hopefully without having to implement a custom locking scheme. If I have to implement something, it may go like so: What I had thought of was a two layer locking scheme that dosemu would lock at the uucp lock level so another Linux process wouldn't try to get control. Then a dosemu internal locking scheme to track whether a process was actually using the comport. We don't have source to the dos application, and I don't know if this is really even feasible at the dosemu level. Is any of this even necessary? Have I overlooked something obvious that will already allow this in dosemu? Thanks for any help, David A. ------------------------------ From: David Anderson <[EMAIL PROTECTED]> Date: Mon, 12 Jul 1999 03:59:26 -0400 Subject: Re: MS FoxPro Hey Roland, I had problems with a foxpro app that would crash dosemu when run and was about to give up on it when I tried the free drdos703 hdimage. That cleared up all of the crashing problems I was having with foxpro apps with win9x dos. Look here: http://www.calderathin.com/dosemu/ Roland Nagtegaal wrote: > > Hi all, > > It has been asked before, and I know there is 'some information' about MS FoxPro > in the > dosemu FAQ's but that information is very close to useless. > > All the FAQ says is: > > " 11.15 MS FoxPro 2.6 won't run > > FoxPro 2.6 doesn't run on network drives. Alexey Naidyonov > <[EMAIL PROTECTED]> > states on that problem: And I guess your FoxPro files are on > lredir'ed disk, yeah? The matter is > that FoxPro doesn't run on such disk, but when I said disk { > partition ... } in /etc/dosemu/conf, it > runs. " > > I have already tried that, but that is not the problem at all. > > The real problem is that Dosemu segfaults immedeately after starting > AccountView, which is > an MSFoxPro application. > > It apparantly tries to use memory or ports that the Linux kernel protects. > > So: has anybody any idea how to find out what memory that might be, and how I > could give it to > MS FoxPro, and also if that would be save to do ? > > Thank you very much, > > Roland Nagtegaal > > ---------------------------------------------------------------------- > UNIX isn't dead, it just smells funny... > Run Linux! Keep The Net Free! > ---------------------------------------------------------------------- ------------------------------ From: Billy Kuker <[EMAIL PROTECTED]> Date: Mon, 12 Jul 1999 17:03:37 -0400 (EDT) Subject: Multiple DOSEMU sessions with semaphores Please excuse me if this is an innaproprate address to send this too, its all I could find on the dosemu webpage. My problem is this: I have the same program running multiple times under dosemu (msdos win95 version). The program is LORD (an old bbs online game), and the different lord sessions should comunicate with eachother throgh data files and temporary files (I belive the term is semaphores?) The problem is that this interaction isnt happening. when I exit a dosemu and start it again it picks up the new data files. How do I make changes to the hd image (it is an image) show up immediatly to the other dosemus? (I have the hdimage on a partition mounted witht he sync option, my first attempt to fix it) Thank you very much, Bill K ------------------------------ From: "Bjoern.Kahl" <[EMAIL PROTECTED]> Date: Tue, 13 Jul 1999 08:01:16 +0200 (CEST) Subject: RE: Multiple DOSEMU sessions with semaphores On 12-Jul-99 Billy Kuker wrote: > [The] different lord sessions should comunicate with eachother > throgh data files and temporary files (I belive the term is semaphores?) > The problem is that this interaction isnt happening. when I exit a > dosemu and start it again it picks up the new data files. > How do I make changes to the hd image (it is an image) show up > immediatly to the other dosemus? (I have the hdimage on a partition > mounted witht he sync option, my first attempt to fix it) Hallo ! I thing there is now way modifying a "running" hdimage from outside, at least not without filesystem corruption. Best idea: use a Linux-temp-directory (/home/login/lord-temp or so) and redierkt it with lredir in all dosemu-session: something like "lredir G:\ \Linux\fs/home/login/lord-temp" -> *** I don't know the right syntax - see dosemu-docu *** <- ^^^^^^^^^^ Any Change you made to files in this temp directory (Drive in DosEMU) should appear immediately in all other sessions. Bjoern - -- +-------------------------------------------------------------+ | Bj�rn Kahl +++ <[EMAIL PROTECTED]> | | Raum : II 204 +++ Tel. +49 431 880 3934 | | Institut f�r Experimentelle und Angewandte Physik, Uni Kiel | +-------------------------------------------------------------+ ------------------------------ From: [EMAIL PROTECTED] (David Hodges) Date: Tue, 13 Jul 1999 18:49:38 +1200 (NZST) Subject: Re: Some problems running Simcity 2000 > Hi There! > > I want to run SimCity 2000. It almost works but doesn't display a > mouse pointer. The game doesn't complain about having no mouse so the > (internal) mouse driver seems to be loaded and working?! > > The mouse works well with some programs, VGA too. > > My PC: > Matrix Mystique Grapics Adaptor > MS Busmouse > AMD K6 233 Mhz > SuSE Linux 6.0 with Kernel 2.2.5 > MS DOS 6.22 What dosemu version ? (the latest is 0.98.8 from ftp.dosemu.org) ------------------------------ From: Niels Ott <[EMAIL PROTECTED]> Date: Tue, 13 Jul 1999 13:27:06 +0200 Subject: Re: Some problems running Simcity 2000 Hi! David Hodges wrote: > > I want to run SimCity 2000. It almost works but doesn't display a > > mouse pointer. The game doesn't complain about having no mouse so the > > (internal) mouse driver seems to be loaded and working?! [...] > What dosemu version ? 0.98.6 > (the latest is 0.98.8 from ftp.dosemu.org) I downloaded the rpm package but couldn't get it to run so I'm now using version 0.98.6 taken from SuSE Linux 6.1. Yours, Niels - -- Laufe nie einer Frau oder einem Bus hinterher. Du wirst in jedem Fall zur�ckgelassen werden. - -> http://www.tomix.de/niels/ ------------------------------ From: Mark Glassberg <[EMAIL PROTECTED]> Date: Tue, 13 Jul 1999 15:45:21 +0000 Subject: bug report I have a linux system running a compiled version of kernel-2.2.10 on an AMD-K66-2/266, on which I'm running the dosemu-0.98.5-1.i386.rpm package, which does not have the submit-bug-report utility. I have a video problem with an old program, called Chartpro, which uses ega graphics. Chartpro draws, for each datafile selected, a graph of stock prices over time; followed, below, by a second graph of the corresponding volumes. Both graphs have the same time line for their horizontal axis, while the vertical values are different. The top graph has price numbers while the bottom one has volume numbers. These vertical numbers should be printed on the right side of the screen, but they are missing when I run Chartpro under dosemu-0.98.5. Except for this omission, the graphs are correctly drawn. I am running dosemu as root. I am running drdos7.03, both directly and under dosemu. Chartpro works properly when run directly under drdos. It also worked properly under msdos6.2, both directly and under dosemu-0.60.3, which I had compiled on my old kernel-1.1.28, 486DX25, linux system. I am enclosing my dosemu.conf and dosemu.users, as well as the debug output from a failed attempt to run Chartpro using "dos -D +v9 -o /tmp/debug". Also, video bios shadowing is disabled. Any help you can give me will be greatly appreciated. DOSEMU.CONF: ############################################################################## # This file is /etc/dosemu.conf, included by /var/lib/dosemu/global.conf # # Linux DOSEMU configuration for parser versions >= 3 (dosemu-0.97.0.1) # # ./doc/README.txt (chapter 2.) contains a description of the syntax # and the usage of dosemu.conf. # # # Access rights are defined in # # /etc/dosemu.users # ############################################################################## # Notes for editing this section: # # In $_xxx = (n) n is a numerical or boolean value # = = # In $_zzz = "s" s is a string # # Please edit only beteen the brakets and quotes and keep the rest intact. # ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^ $_debug = "-a" # same format as -D commandline option # (but without the -D in front) $_features= "" # list of temporary hacks, see release notes in # the file ChangeLog. e.g "0:1 2:0", which means # to set feature_0 to 1 and feature_2 to 0. $_timint = (on) # emulate INT08 type timer interrupts $_mathco = (off) # or off $_cpu = (80586) # CPU emulation, valid values: 80[345]86 $_rdtsc = (on) # if possible use Pentium cycle counter $_cpuspeed = (0) # 0 = calibrated by dosemu, else given (e.g.166.666) $_pci = (on) $_xms = (0) # in Kbyte $_ems = (0) # in Kbyte # $_ems_frame = (0xe000) $_dpmi = (off) # in Kbyte $_dosmem = (640) # in Kbyte, < 640 $_hardware_ram = "" # list of segment values/ranges such as # "0xc8000 range 0xcc000,0xcffff" $_secure ="0" # secure for: n (normal users), g (guest), d (dexe) # empty string: depending on 'restricted' # "0": always insecure (not recommended) $_odd_hosts = "" # black list such as "lucifer.hell.com billy.the.cat" $_diskless_hosts="" # black list such as "hacker1 newbee gateway1" $_emusys = "" # empty or 3 char., config.sys -> config.XXX $_emubat = "" # empty or 3 char., autoexec.bat -> autoexec.XXX $_emuini = "" # empty or 3 char., system.ini -> system.XXX $_hogthreshold = (1) # 0 == all CPU power to DOSEMU $_irqpassing = "" # list of IRQ number (2-15) to pass to DOS such as # "3 8 10" $_speaker = "" # or "native" or "emulated" $_term_char_set = "" # Global code page and character set selection. # "" == automatic, else: ibm, latin, latin1, latin2 $_term_color = (on) # terminal with color support $_term_updfreq = (4) # time between refreshs (units: 20 == 1 second) $_escchar = (30) # 30 == Ctrl-^, special-sequence prefix $_rawkeyboard = (1) # bypass normal keyboard input, maybe dangerous $_layout = "us" # one of: finnish(-latin1), de(-latin1), be, it, us # uk, dk(-latin1), keyb-no, no-latin1, dvorak, po # sg(-latin1), fr(-latin1), sf(-latin1), es(-latin1) # sw, hu(-latin2), hu-cwi, keyb-user # hr-cp852, hr-latin2 $_keybint = (on) # emulate PCish keyboard interrupt $_X_updfreq = (5) # time between refreshs (units: 20 == 1 second) $_X_title = "DOS in a BOX" # Title in the top bar of the window $_X_icon_name = "xdos" # Text for icon, when minimized $_X_keycode = (off) # on == translate keybord via dosemu keytables $_X_blinkrate = (8) # blink rate for the cursor $_X_font = "" # basename from /usr/X11R6/lib/X11/fonts/misc/* # (without extension) e.g. "vga" $_X_mitshm = (on) # Use shared memory extensions $_X_sharecmap = (off) # share the colormap with other applications $_X_fixed_aspect = (on) # Set fixed aspect for resize the graphics window $_X_aspect_43 = (on) # Always use an aspect ratio of 4:3 for graphics $_X_lin_filt = (off) # Use linear filtering for >15 bpp interpolation $_X_bilin_filt = (off) # Use bi-linear filtering for >15 bpp interpolation $_X_mode13fact = (2) # initial size factor for video mode 0x13 (320x200) $_X_winsize = "" # "x,y" of initial windows size (defaults to float) $_X_gamma = (1.0) # gamma correction $_X_vgaemu_memsize = (1024) # size (in Kbytes) of the frame buffer for emulated vga $_X_lfb = (on) # use linear frame buffer in VESA modes $_X_pm_interface = (on) # use protected mode interface for VESA modes $_X_mgrab_key = "" # KeySym name to activate mouse grab, empty == off $_X_vesamode = "" # "xres,yres ... xres,yres" # List of vesamodes to add. The list has to contain # SPACE separated "xres,yres" pairs $_video = "vga" # one of: plainvga, vga, ega, mda, mga, cga $_console = (1) # use 'console' video $_graphics = (1) # use the cards BIOS to set graphics $_videoportaccess = (1) # allow videoportaccess when 'graphics' enabled $_vbios_seg = (0xc000) # set the address of your VBIOS (e.g. 0xe000) $_vbios_size = (0x6000) # set the size of your BIOS (e.g. 0x8000) $_vmemsize = (1024) # size of regen buffer $_chipset = "plainvga" # one of: plainvga, trident, et4000, diamond, avance # cirrus, matrox, wdvga, paradise, ati, s3 $_dualmon = (0) # if you have one vga _plus_ one hgc (2 monitors) $_vbootfloppy = "" # if you want to boot from a virtual floppy: # file name of the floppy image under /var/lib/dosemu # e.g. "floppyimage" disables $_hdimage # "floppyimage +hd" does _not_ disable $_hdimage $_floppy_a ="threeinch" # or "fiveinch" or empty, if not existing $_floppy_b = "" # dito for B: $_hdimage = "hdimage.first" # list of hdimages under /var/lib/dosemu # assigned in this order such as # "hdimage_c hdimage_d hdimage_e" # If the name begins with '/dev/', then partion # access is done instead of virtual hdimage such as # "/dev/hda1" or "/dev/hda1:ro" for readonly # Currently mounted devices and swap are refused. # Hdimages and devices may be mixed such as # "hdimage_c /dev/hda1 /dev/hda3:ro" # Note: 'wholedisk' is _not_ supported. $_hdimage_r = $_hdimage # hdimages for 'restricted access (if different) $_aspi = "" # list of generic SCSI devices to make available # for the builtin aspi driver (format of an entry # is 'device:type:mappedtarget' such as # "sg2:WORM sg3:Sequential-Access:6 sg4:CD-ROM" or # "sg2:4 sg3:1:6 sg4:5" (which are equal) $_com1 = "" # e.g. "/dev/mouse" or "/dev/cua0" $_com2 = "" # e.g. "/dev/modem" or "/dev/cua1" $_com3 = "" # dito "/dev/cua2" $_com4 = "" # dito "/dev/cua3" $_ttylocks = "" # Lock directory (e.g. "/var/lock") # default ("") is /usr/spool/uucp $_mouse = "" # one of: microsoft, mousesystems, logitech, mmseries # mouseman, hitachi, busmouse, ps2 $_mouse_dev = "" # one of: com1, com2, com3, com4 or /dev/mouse $_mouse_flags = "" # list of none or one or more of: # "emulate3buttons cleardtr" $_mouse_baud = (0) # baudrate, 0 == don't set $_printer = "lp" # list of (/etc/printcap) printer names to appear as # LPT1, LPT2, LPT3 (not all are needed, empty for none) $_printer_timeout = (20)# idle time in seconds before spooling out $_ports = "" # list of portnumbers such as "0x1ce 0x1cf 0x238" # or "0x1ce range 0x280,0x29f 310" # or "range 0x1a0,(0x1a0+15)" $_ipxsupport = (off) # or on $_novell_hack = (off) $_vnet = (off) # 'on' for packet-multi (used by dosnet) $_sound = (off) # sound support on/off $_sb_base = (0x220) $_sb_irq = (5) $_sb_dma = (1) $_sb_dsp = "/dev/dsp" $_sb_mixer = "/dev/mixer" $_mpu_base = "0x330" _______________________________________________________________________________ DOSEMU.USERS: # This is a sample /etc/dosemu.users file # Here you can restrict access to dosemu # # However, THIS ONE DOES ALLOW ALL WEIRD THINGS !!! # For a more secure one look at ./etc/dosemu.users.secure # # Format: # # [ <login> | all ] [ confvar [ confvar [ ... ] ] ] # # <login> the login name of a user # confvar under this name a configuration variable is set which # can be checked via 'ifdef' in /etc/dosemu.conf # Variables starting with 'c_' define class permission # # For more details look at ./doc/README.txt default_lib_dir= /var/lib/dosemu log_level= 0 root c_all all c_all _______________________________________________________________________________ DEBUG FILE: [00000202] debug flags: [00000228] debug flags: +v9 [00000000] VID: Set process control [00000000] VID: Setting windows size to li=25, co=80 [00000000] VID: Set process control [00000007] get_video_ram STARTED [00000007] VID: get_video_ram WAITING [00000007] Kmem closed successfully [00000007] VID: we're active, waiting... [00000007] VID: cleared screen: 0 7 0xb8000 [00000010] VID: Video set to Video_graphics [00000010] VID: config.dualmon=0 [00000010] Permission allowed [00000010] Unspecific VIDEO selected = 0x0000 [00000010] VGA: mem size 1024, banks 4 [00000010] Saving data for Linux Regs [00000010] vga_screenoff [00000010] Store regs complete! [00000010] ALPHA mode save being attempted [00000010] ALPHA mode save being performed [00000010] Mode == 3 [00000010] Banks == 1 [00000015] READ Bank=1, plane=0x00, *mem=0x20202020, GRAPH_BASE=20202020, mem=0x8298008 [00000019] READ Bank=1, plane=0x01, *mem=0x70007, GRAPH_BASE=00070007, mem=0x829a008 [00000024] READ Bank=1, plane=0x02, *mem=0x0, GRAPH_BASE=00000000, mem=0x829c008 [00000028] READ Bank=1, plane=0x03, *mem=0x0, GRAPH_BASE=00000000, mem=0x829e008 [00000028] GRAPH_BASE to mem complete! [00000030] Restore_vga_regs completed! [00000030] Store_vga_state complete [00000030] vga_screenon [00000030] /* BIOS mode 0x03 */ [00000030] static char regs[60] = { 0x5F,0x4F,0x50,0x82,0x55,0x81,0xBF,0x1F,0x00,0x4F,0x0D,0x0E, 0x00,0x00,0x3F,0xFF,0x9C,0x8E,0x8F,0x28,0x1F,0x96,0xB9,0xA3, 0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0B, 0x0C,0x0D,0x0E,0x0F,0x0C,0x00,0x0F,0x08,0x00, 0x00,0x00,0x00,0x00,0x00,0x10,0x0E,0x00,0xFF, 0x00,0x20,0x03,0x00,0x02, 0x67 }; [00000030] Extended Regs/if applicable: [00000031] 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00 [00000031] Extended 16 bit Regs/if applicable: [00000031] 0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x8008 [00000031] VID: cleared screen: 0 7 0xb8000 [00000033] kmem used for loadfile [00000096] Kmem closed successfully [00000096] kmem used for loadfile [00000096] Kmem closed successfully [00000098] VID: install_int_10_handler: do nothing [00000111] get_video_ram STARTED [00000111] VID: get_video_ram WAITING [00000185] Kmem closed successfully [00000186] Starting Video initialization [00000186] Giving temporary access to PIT#2 [00000186] Save hi vector area [00000608] Finished with Video initialization [00000608] Removing temporary access to PIT#2 [00000608] Restore hi vector area [00058284] VID: video_close() called [00058291] Storing dosemu_regs, Releasing vt mode=03 [00058291] Saving data for Dosemu Regs [00058291] vga_screenoff [00058291] Store regs complete! [00058291] ALPHA mode save being attempted [00058291] ALPHA mode save being performed [00058291] Mode == 3 [00058291] Banks == 1 [00058296] READ Bank=1, plane=0x00, *mem=0x690046, GRAPH_BASE=00690046, mem=0x82a0010 [00058300] READ Bank=1, plane=0x01, *mem=0x70007, GRAPH_BASE=00070007, mem=0x82a2010 [00058305] READ Bank=1, plane=0x02, *mem=0x0, GRAPH_BASE=00000000, mem=0x82a4010 [00058309] READ Bank=1, plane=0x03, *mem=0x0, GRAPH_BASE=00000000, mem=0x82a6010 [00058309] GRAPH_BASE to mem complete! [00058311] Restore_vga_regs completed! [00058311] Store_vga_state complete [00058311] Restoring linux_regs, Releasing vt [00058311] Restoring data for Linux Regs [00058311] vga_screenoff [00058311] Restore_vga_regs completed! [00058314] WRITE Bank=1, plane=0x00, *mem=20202020, mem=0x8298008 [00058316] WRITE Bank=1, plane=0x01, *mem=70007, mem=0x829a008 [00058319] WRITE Bank=1, plane=0x02, *mem=0, mem=0x829c008 [00058321] WRITE Bank=1, plane=0x03, *mem=0, mem=0x829e008 [00058321] mem to GRAPH_BASE complete! [00058322] Restore_vga_regs completed! [00058322] Permissions=1 [00058322] vga_screenon [00058323] Restore_vga_state complete [00058323] Permission disallowed [00058323] put_video_ram called [00058323] Kmem closed successfully [00058323] put_video_ram completed [00058325] ------------------------------ From: <[EMAIL PROTECTED]> Date: Tue, 13 Jul 1999 15:17:22 -0500 (CDT) Subject: can't boot dos Hi, I screwed up. I was playing with dosemu and now I can't boot dos from lilo or dosemu. The freedos hdimage works fine. To the best of my recollection, here's what I did: I started by setting the hdimage variable in the config file to /dev/hda1, my dos (Win95) partition. When I ran dosemu, I got the "Starting Windows..." message then dosemu froze, so I killed the process. I saw something in the docs about pressing F4, F5, and F8 for a "dual boot" option. I didn't really understand what this was but I did it anyway. This time I got a dos prompt. Woohoo! Then I tried to run a program (one that I later learned won't run under dosemu anyway, because it uses that ring 0 thingie). Either dosemu crashed or I killed it, I don't remember which. That was the last time I was able to use my native dos. I can still mount /dev/hda1 and see all the files. I meddled with forces I didn't understand and I got burned. I would be grateful If someone could help me resurrect my dos partition. Thanks. Sam ------------------------------ From: [EMAIL PROTECTED] (David Hodges) Date: Wed, 14 Jul 1999 09:23:32 +1200 (NZST) Subject: Re: can't boot dos > I screwed up. I was playing with dosemu and now I can't boot dos from > lilo or dosemu. The freedos hdimage works fine. To the best of my > recollection, here's what I did: I started by setting the hdimage > variable in the config file to /dev/hda1, my dos (Win95) partition. > When I ran dosemu, I got the "Starting Windows..." message then > dosemu froze, so I killed the process. I saw something in the docs > about pressing F4, F5, and F8 for a "dual boot" option. I didn't > really understand what this was but I did it anyway. This time I got > a dos prompt. Woohoo! Then I tried to run a program (one that I > later learned won't run under dosemu anyway, because it uses that ring > 0 thingie). Either dosemu crashed or I killed it, I don't remember > which. That was the last time I was able to use my native dos. I can > still mount /dev/hda1 and see all the files. > > I meddled with forces I didn't understand and I got burned. I would > be grateful If someone could help me resurrect my dos partition. > Thanks. dos does that ocassionally, even if you don't use dosemu. If you use dosemu 0.98.6 or later (latest version is 0.98.8 from ftp.dosemu.org) and use the bootdir method described in the documentation, it will be much harder for dos to screw itself like that since it can't write directly to the filesystem but must use normal file operations through Linux. To make dos bootable again, you probably need to find a DOS boot floppy, boot off it and type "system C:" Also you will want to use a different msdos.sys when booting in dosemu from booting natively so that it doesn't try to start Windows when you boot dos (you need a line that says "BootGUI=0" as described in the documentation) ------------------------------ From: Volker Kuhlmann <[EMAIL PROTECTED]> Date: Wed, 14 Jul 1999 10:38:05 +1200 (NZST) Subject: linux dosemu 0.98.7.0 Phew, managed to get dosemu to go again! First a big thanks - it has saved me the effort of booting back into dos many times! The dosemus on red hat 5.2 and 6.0 are both useless. (developer versions?) Problems: boot hangs, floppy disk access hangs, the whole thing hangs (several times by simply pressing ":" on the keyboard (shift-; for me). Major hassle: configured logical disks (i.e. files containing disk images) were not accessible (illegal drive letter). I gave up. Finally I got your rpm: Name : dosemu Relocations: (not relocateable) Version : 0.98.7 Vendor: DOSEMU-Development-Team Release : 1 Build Date: Sun Jun 6 06:09:51 1999 Install date: Thu Jul 8 00:50:24 1999 Build Host: hlermen2.lermen.priv Group : Applications/Emulators Source RPM: dosemu-0.98.7-1.src.rpm Size : 3463540 License: GPL version 2, (C) 1994-1999 The DOSEMU-Development-Team Packager : Hans Lermen <[EMAIL PROTECTED]> URL : http://www.dosemu.org Summary : The Linux DOS emulator Running on red hat 6.0. one minor problem I can't remember, but works. Even the vbootfloppy works again. Great! I installed MS-DOS 6.2 and 6.22 from the original install floppies, ok. (Copying the files from those floppies onto a disk accessible by dosemu doesn't work, msdos 6.2 insists on installation from A:\, and 6.22 always(!!) crapped out during install with I/O error). Therefore floppy jockeying once more - hadn't done that for years. But it works now. Things I had to change: charset to ibm, or those IBM window making characters ain't there (neither console nor X). rawkeyboard = on, absolutely necesssary or shift-anything or ctrl-anything (e.g. cursor) doesn't work, making the whole thing useless for cut/copy/paste operations under dos. I can't really see how dosemu could be usefully used without this? vbootfloppy and dos partition access via linux and lredir work fine. Then I carted the whole thing to a laptop (Compaq Armada 7800, pentium processor), off-the-CD Red Hat 6.0 installation, and the whole thing fails. It simply hangs after reading from the msdos install floppy for about 3 seconds or so. Nothing I could do to get it to do something. It hangs stone-dead after displaying "Loading MS-DOS..." Only freedos booted... but that's not so useful. If I may say this about freedos: as far as I am concerned, it's rather a waste of time. The development time would be better spent on dosemu. It seems to read neither config.sys nor autoexec.bat? I am interested in compatibility (to save having to boot into dos), not free (license) software in this case. msdos is extremely free (cost) these days - plenty of unused licences lying around everywhere... Has dosemu more problems on laptops? Is there something I can do to get it going? The only difference I can see between the machines is that the PC it works on has the Red Hat kernel 2.2.5-15, recompiled by me, whereas the laptop has the red hat kernel 2.2.5-22 as compiled by red hat. Can that really make a difference? Btw your rpm has the submit-bug-report or some such program missing. One more bug (has been in since 0.6xx days): in the xdos window as well as the console, text scrolling doesn't work properly: the last character on an overfull and therefore wrapped line is repeated in the first column (a little annoying, but it works anyway). Overall: thanks for dosemu!!! Volker ------------------------------ From: "Ian Dobson" <[EMAIL PROTECTED]> Date: Tue, 13 Jul 1999 19:31:38 -0800 Subject: DOSemu and Novell Ok using caldera DR DOS under dosemu 99.1-2 on Redhat 5.2 I want to connect to A Novell network to run ACCPAC Plus. what network drivers should I use? I have it working now with just VLM and built in IPX support, but what is the most reliable way? ans this program uses lots of file and record locking.. Sued? SUED???!!? When MS gets through with you, you're going to WISH that they'd jusT SUED you! These people are EVIL!!! They kidnapped my dog and G$%<S-F4>@^<S-F6>RB. f NO CARRIER ------------------------------ From: Reinhard Karcher <[EMAIL PROTECTED]> Date: Wed, 14 Jul 1999 08:24:10 +0200 Subject: Re: DOSemu and Novell At Wed, 14 Jul 1999 Ian Dobson wrote: > Ok using caldera DR DOS under dosemu 99.1-2 on Redhat 5.2 > I want to connect to A Novell network to run ACCPAC Plus. > > what network drivers should I use? > > I have it working now with just VLM and built in IPX support, but > what is the most reliable way? > ans this program uses lots of file and record locking.. Hi Ian, If it works that way, use it! I think, it is the fastest and most reliable way. I never had any problems. Reinhard ------------------------------ From: Reinhard Karcher <[EMAIL PROTECTED]> Date: Wed, 14 Jul 1999 08:31:58 +0200 Subject: Re: bug report At Tue, 13 Jul 1999 Mark Glassberg wrote: > I have a linux system running a compiled version of kernel-2.2.10 on an > AMD-K66-2/266, on which I'm running the dosemu-0.98.5-1.i386.rpm package, > which does not have the submit-bug-report utility. I have a video problem > with an old program, called Chartpro, which uses ega graphics. Chartpro draws, > for each datafile selected, a graph of stock prices over time; followed, below, > by a second graph of the corresponding volumes. Both graphs have the same time > line for their horizontal axis, while the vertical values are different. The > top graph has price numbers while the bottom one has volume numbers. These > vertical numbers should be printed on the right side of the screen, but they > are missing when I run Chartpro under dosemu-0.98.5. Except for this omission, > the graphs are correctly drawn. > > $_video = "vga" # one of: plainvga, vga, ega, mda, mga, < $_console = (1) # use 'console' video > $_graphics = (1) # use the cards BIOS to set graphics > $_videoportaccess = (1) # allow videoportaccess when 'graphics' enabled > $_vbios_seg = (0xc000) # set the address of your VBIOS (e.g. 0xe000) > $_vbios_size = (0x6000) # set the size of your BIOS (e.g. 0x8000) > $_vmemsize = (1024) # size of regen buffer > $_chipset = "plainvga" # one of: plainvga, trident, et4000, diamond, avance > # cirrus, matrox, wdvga, paradise, ati, s3 Hi Mark, I'm not an expert in this field, but I suggest, that you try to set $_chipset to the value of your video card, if you have got a supported modell. Reinhard ------------------------------ From: Chris Evans <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 00:38:58 +0100 (GMT) Subject: Booting from floppy unbearably slow Hi, Version 0.98.8 or 0.99.10 or 0.99.13(!) Launch with "dos -A", default dosemu.conf Boot floopy is MSDOS6.2 OR MSDOS5 or even MSDOS 7.0 from Win 95 and doing "sys a:" dosemu displays "Starting MSDOS" then hangs for _ages_. strace reveals process "dos" is here: vm86(0x1, 0x8115780, 0, 0xfffafff1, 0x2 <--- hanging On a previous run, with the same problems, strace showed _enormous_ amounts of repeated vm86(0x1, ....) over and over. Kernel is 2.2.5. System is essentially RH5.9 I'm sure someone else has come across this bug of hanging/repeated vm86 calls when trying to boot from a standard MS-DOS floppy. Anyone care to volunteer the fix? :-/ Cheers! Chris PS. I thought vm86 only took 2 args, have I also found a bug in strace? ------------------------------ From: Chris Evans <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 03:04:07 +0100 (GMT) Subject: dosemu slow/hanging: more details (+solution?) Hi, OK my situation was booting MSDOS6.2 floppy. It seems that dosemu-0.99.13 "hangs" during the MSDOS boot. If I press "uparrow" or "keypad enter" though, the boot continues and works fine. Virtual hard disk boots are unaffected by this phenomena. dosemu-0.98.8 behaves identically. dosemu-0.99.10 is broken for me - the boot hangs in the same place but pressing enter does not help, and my console is locked out. Note however that this could be a RedHat packaging flaw because 0.99.10 is a RedHat binary whereas the other binaries I built myself. As far as I'm concerned my problem is solved - I can cope with pressing "enter". Anyone know why this is neccessary though? If I boot the floppy "normally", things proceed without needing the keypress. Cheers Chris ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 11:24:26 +0200 (MEST) Subject: Re: Booting from floppy unbearably slow On Thu, 15 Jul 1999, Chris Evans wrote: > Version 0.98.8 or 0.99.10 or 0.99.13(!) > > Launch with "dos -A", default dosemu.conf > > Boot floopy is MSDOS6.2 OR MSDOS5 or even MSDOS 7.0 from Win 95 and doing > "sys a:" > > dosemu displays "Starting MSDOS" then hangs for _ages_. can you please try the binary distribution ftp://ftp.dosemu.org/dosemu/dosemu-0.98.8-1.i386.rpm (its sufficient to just replace the /usr/bin/dos binary) and report back. > On a previous run, with the same problems, strace showed _enormous_ > amounts of repeated vm86(0x1, ....) over and over. This is normal and is the way DOSEMU works: looping through vm86. ( and yes, its normal to return '-1 ENOSYS' ) > PS. I thought vm86 only took 2 args, have I also found a bug in strace? No, the 'new' vm86-interface is in since _ages_ (linux-2.0.28). ... and you obviously are happy to have a strace that displays 'vm86()' instead of 'SYS_166()' ;-) Hans <[EMAIL PROTECTED]> ------------------------------ From: Chris Evans <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 12:20:03 +0100 (GMT) Subject: Re: Booting from floppy unbearably slow On Thu, 15 Jul 1999, Hans Lermen wrote: > can you please try the binary distribution > > ftp://ftp.dosemu.org/dosemu/dosemu-0.98.8-1.i386.rpm > > (its sufficient to just replace the /usr/bin/dos binary) > and report back. Will do - note I persevered a bit last night and found that dosemu will continue on if I press "keypad enter" or "up-arrow". Very strange - this isn't needed if the floppy is booted normal rather than under dosemu. > > PS. I thought vm86 only took 2 args, have I also found a bug in strace? > > No, the 'new' vm86-interface is in since _ages_ (linux-2.0.28). > ... and you obviously are happy to have a strace that displays 'vm86()' > instead of 'SYS_166()' ;-) Heh, I had SYS_166 initially. I grabbed the latest i386 RedHat strace-3.99 RPM from rawhide, did the trick! I'll see if the RPM you pointed me to boots without me having to press a key. later tonight Cheers Chris ------------------------------ From: Chris Evans <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 21:48:54 +0100 (GMT) Subject: Re: Booting from floppy unbearably slow On Thu, 15 Jul 1999, Hans Lermen wrote: > > dosemu displays "Starting MSDOS" then hangs for _ages_. > > can you please try the binary distribution > > ftp://ftp.dosemu.org/dosemu/dosemu-0.98.8-1.i386.rpm > > (its sufficient to just replace the /usr/bin/dos binary) > and report back. That binary exhibits the same fault I'm afraid; try to boot MSDOS-6.2 boot disk. I see the usual "Starting MS-DOS..." text. Then it hangs. When I press keypad enter or up arrow or any of a few other keys, booting resumes. Hard disk boots are fine. Cheers Chris ------------------------------ From: "Eugene Wong" <[EMAIL PROTECTED]> Date: Thu, 15 Jul 1999 16:55:22 -0700 Subject: add I'm sorry, if this is the wrong place to join the list. ------------------------------ From: [EMAIL PROTECTED] (David Hodges) Date: Fri, 16 Jul 1999 19:54:00 +1200 (NZST) Subject: Re: add > I'm sorry, if this is the wrong place to join the list. Read the dosemu HOWTO at http://www.dosemu.org - it will tell you how to join the mailing list as well as other useful info about dosemu. There are also pointers to the mailing list archives at http://www.dosemu.org ------------------------------ From: Chris Evans <[EMAIL PROTECTED]> Date: Fri, 16 Jul 1999 20:15:08 +0100 (GMT) Subject: Re: Booting from floppy unbearably slow On Fri, 16 Jul 1999, Hans Lermen wrote: > On Thu, 15 Jul 1999, Chris Evans wrote: > > > That binary exhibits the same fault I'm afraid; try to boot MSDOS-6.2 boot > > disk. I see the usual "Starting MS-DOS..." text. Then it hangs. When I > > press keypad enter or up arrow or any of a few other keys, booting > > resumes. > > Ok, so we can exclude libc problems. And egcs miscompiling :-/ > I'm not sure, but it maybe a 2.2.x kernel problem and unfortunately I'm > not able to reproduce your locking condition here on my testing suite. OK, I will try upgrading to 2.2.10. I'll also see I can dig up a 2.0.36 kernel from somewhere. I have an SMP system if it makes any difference... I'll try getting a debug trace. Cheers Chris ------------------------------ From: Juergen Leising <[EMAIL PROTECTED]> Date: Fri, 16 Jul 1999 23:56:08 +0200 Subject: 0.98.8 and DMA problem Hello, since I upgraded from 0.98.6 to 0.98.8 I get a kernel message floppy0: cannot allocate DMA memory and drive a: is indeed not able to be accessed - neither by dosemu itself nor by mtools; the problem can be solved by stopping dosemu (exitemu). The problem occurs after dosemu having run for several hours. Has anybody a better suggestion than exiting dosemu? Thank you! Juergen. - - ***************************************************************** * Juergen Leising, E-Mail: [EMAIL PROTECTED] * * http://www.stud.uni-bayreuth.de/~a0037/ * ***************************************************************** ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Sat, 17 Jul 1999 01:01:55 +0200 (MEST) Subject: Re: Booting from floppy unbearably slow On Fri, 16 Jul 1999, Chris Evans wrote: > > > > Ok, so we can exclude libc problems. > > And egcs miscompiling :-/ Yup. > > > I'm not sure, but it maybe a 2.2.x kernel problem and unfortunately I'm > > not able to reproduce your locking condition here on my testing suite. > > OK, I will try upgrading to 2.2.10. I'll also see I can dig up a 2.0.36 hmm, better wait for 2.2.11; 2.2.10 is reported to have other problems. > kernel from somewhere. > > I have an SMP system if it makes any difference... ^^^^ Ahhh, yes, _that_ explains the problems. Timings under SMP always have been weird for DOSEMU. In order to do it properly the DOSEMU process should stay on the _same_ CPU, what isn't possible to force under Linux. Under 2.0.x you even won't get any relyable behave concerning timer emulation :-( I was told 2.2 is doing it better, but due to lack of hardware I never was able to test it. Hans <[EMAIL PROTECTED]> ------------------------------ From: <[EMAIL PROTECTED]> Date: Sun Jul 18 21:21:55 CST 1999 Subject: Regards from Net21 Hi! I am NetSpirit, I come from Singapore. My mission is to establish a Global Business Network for your future grow. By downloading a NetSpirit free of charge and registering yourself, you stand a chance to win a pair of Secure Biz-Com2000, worth USD600. http://www.net21.com.sg/ns-outreach.htm From: Net21 Technologies Pte Ltd 1 Maritime Square #09-06&27 World Trade Centre Singapore 099253 ------------------------------ From: "Vitor ??????" <[EMAIL PROTECTED]> Date: Sun, 18 Jul 1999 17:41:16 PDT Subject: Stunts don't work under dosemu I noticed that the game stunts (STUNTS.EXE) don't work under dosemu. I can't give more detailed information because I noticed it in the computer of a friend of mine. It crashes just when you start playing. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ------------------------------ From: Mark Ryan <[EMAIL PROTECTED]> Date: Sun, 18 Jul 1999 21:12:06 -0400 (EDT) Subject: Re: Stunts don't work under dosemu What version of DOS is your friend running in DOSEmu? I have yet to get anything graphical running in DosEmu, but I can tell you that Stunts doesn't run properly in real Windows 95 or 98. I guess M$ thought backwards compatibility was a waste of time. So if your friend is using DosEmu with "DOS 7" AKA Win9x, that could be the problem. mark ------------------------------ From: Quinho <[EMAIL PROTECTED]> Date: Mon, 19 Jul 1999 20:01:04 -0300 Subject: Stunts.. for DOS HI You asked [EMAIL PROTECTED] for stunts for dos, because he told you that this cool game doesn't work on DOSEmu. Well... I am the friend that he is talking about, so I am sending you the game. The codes for the game are in the file stunts.txt Also, the game is in a .tar.gz format, but it is the MS-DOS Version of stunts Thanks Quinho - -- \|/ Quinho @ @ mailto:[EMAIL PROTECTED] - ---------oOo-(_)-oOo---------------- http://uolhacker.cjb.net -------- ICQ: 1754643 (http://wwp.mirabilis.com/scripts/Search.dll?to=1754643) ------------------------------ From: Vignani Alberto <[EMAIL PROTECTED]> Date: Tue, 20 Jul 1999 12:45:58 +0200 Subject: R:dosemu dump file as requested > ---------- > Da: Chris Evans[SMTP:[EMAIL PROTECTED]] > Inviato: Tuesday, July 20, 1999 12:57 AM > A: Vignani Alberto > Oggetto: dosemu dump file as requested > > <<File: debug.out.gz>> > I had a look at that file. Unfortunately -D9a produces too big a logfile, and the conservative parameters in utilities.h cut all but the latest part, which isn't very useful. At the start of the logfile you sent we are _already_ into a keyboard busy waiting loop in bios.S, which is called from int 0x16. The problem now is: who calls int 0x16? DOS itself or the VGA BIOS? I repeated the DOS 6.2 boot from floppy on my system and saw no trace of int 0x16, so I suspect either your VGA, or something in the keyboard code. Note that 1) the timer seems to work fine 2) you said all is working when booting from HD, so IMHO there are no SMP-related issues in your case. It also seems to me to remember that I had once the same problem, maybe on a laptop; but it was a very long time ago, and whatever was, it disappeared soon. What to do... well, either edit src/base/misc/utilities.c and change the INITIAL_LOG... parameters (but you'll end up with a 20Mb+ logfile), or be more selective with your debug options, e.g. -D1g only, until you find who is issuing that int 0x16 which starts the keyboard wait loop, and what's the difference between FD and HD boots... Alberto ------------------------------ From: Haroldo Stenger <[EMAIL PROTECTED]> Date: Thu, 20 Jul 2000 10:54:17 -0300 Subject: DOS Error Documentation This is somewhat off-topic, so accept my apologizes. I'd like to find a _full_ and _comprehensive_ explanation of DOS errors like: 01 Invalid Function number. Program made an invalid function call. 02 File Not Found. File does not exist or cannot be opened. 03 Path Not Found. Referenced Directory does not exist. 04 Out of File Handles (too many open files-no open handles left).Not enough FILES in CONFIG.SYS or network config. 05 Access Denied. File/Data locked or no rights to file on network. 06 Invalid handle program. Used a file handle which is not open. 07 Memory Corrupt (memory control blocks destroyed). DOS memory chain is corrupt. Possible software corrupted chain or hardware failure. 08 Insufficient Memory 09 Invalid Memory Block Address. Program tried to use an invalid memory block. A(10) Invalid Environment I've found quite difficult to understand what some of them mean, or how to interpret them. Can anybody point me to a web site containing the info? Thanks for your help. - -- Saludos, Haroldo. - ------------------------------ "Y con esto me despido Sin expresar hasta cuando. Siempre corta por lo blando El que busca lo siguro; Mas yo corto por lo duro, Y ans� he de seguir cortando." Jos� Hern�ndez - Mart�n Fierro - ------------------------------ ------------------------------ From: medcure <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 01:01:08 -0400 Subject: DOS EMU Client Setup We are attempting to setup a DOS EMU Client using Caldera 2.2 Linux that attaches to a Novell 5 Server. The application's database is stored on the server and uses Novell's Transaction Tracking System for lock manager support. The DOS EMU client use DOS4gw for the application and has connected with the server using several different configurations. Our problem is that the DOS EMU client is not processing the TTS system properly resulting in error messages. How can we configure this application to work with Novell's TTS . What is the best configuration for this application? Any reccomendations would be greatly appreciated. Thanks, [EMAIL PROTECTED] ------------------------------ From: medcure <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 01:13:56 -0400 Subject: Keyboard Mapping Our DOS Application uses the keys, Ctrl-Home, Ctrl-Ins, Ctrl-Page up and a few other keyboard commands to operate the program. Within a DOS EMU session the keyboard is remapped resulting in the inability to use all the commands that use the Ctrl key. Where can we find information on how to remap the keyboard to meet the requirements of our application within a DOS EMU session. Any assistance is greatly appreciated. Thanks, [EMAIL PROTECTED] ------------------------------ From: [EMAIL PROTECTED] (Bernhard Bialas) Date: Tue, 20 Jul 1999 20:33:59 -0400 Subject: Problems with DMI-Programs Hello, after installation of the new dosemu version 0.98.8 I have the following Problem with the program "Tascbase" which use the dos4gw extender: after start the firs window with graphic appears and after this immediately the program die: in the left top corner the dos-prompt appears. After this I can switch to a another console, but when I try (instead) to start the program again, the whole Linux hangs-nothing goes. I use Suse-Linux 6.0 with Kernel 2.2.5. Before: under the dosemu-versioms 0.98.1-0.98.7 this a.m. program works perfectly (on the console only). Regards Bernhard Bialas ------------------------------ From: Donnie Oberst <[EMAIL PROTECTED]> Date: Tue, 20 Jul 1999 16:50:15 -0500 Subject: Having a problem with configuring DOSEMU I have a problem configuring DOSEMU to work with my dos partitioned drive. I have got the drive mounted in Linux but I do not know how to get DOSEMU to recognize it. Can you plese tell me step by step how to make DOSEMU recognize the drive. Thanks. ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Tue, 20 Jul 1999 20:26:11 -0400 (EDT) Subject: Re: Stunts don't work under dosemu make sure you use xdos for that, I've actually got a lot of sucess with games, etc with xdos. On Sun, 18 Jul 1999, Mark Ryan wrote: > What version of DOS is your friend running in DOSEmu? I have yet to get > anything graphical running in DosEmu, but I can tell you that Stunts > doesn't run properly in real Windows 95 or 98. I guess M$ thought > backwards compatibility was a waste of time. So if your friend is using > DosEmu with "DOS 7" AKA Win9x, that could be the problem. > > mark > > > ------------------------------ From: Josue Mora <[EMAIL PROTECTED]> Date: Tue, 20 Jul 1999 19:29:22 -0500 Subject: I need Help Help!!!... My name is joshua... I have a server linux (suse 5.1 Kernel 2.0.33), and i have a DOSEMU 0.66.1792, and I have a connection with a server NOVELL, ( to run DOS-CLIPPER aplications ), and it is perfect !!!... Question? I need connect to a server WINDOWS NT, to run DOS-CLIPPER aplications I try with SAMBA, but the records locks (in a Data Base) no it is equal with NOVELL Please help me ... Espa�ol ---------------Spanish Ayuda !!!... Mi nombre es Joshua ... Tengo un servidor linux (suse 5.1 Kernel 2.0.33), y acticavado el DOSEMU 0.66.1792, y, ademas tengo una coneccion con un servidor NOVELL, ( para executar aplicaciones DOS-CLIPPER ), y, esto esta perfecto !!!... Pregunta? Como me conecto a un Servidor Windows NT, para executar aplicaciones DOS-CLIPPER Trate con SAMBA pero el bloqueo de registros (en una base de datos) no es igual al Servidor NOVELL, Porfavor nececito ayuda !!! ... ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Tue, 20 Jul 1999 20:50:59 -0400 (EDT) Subject: Re: Keyboard Mapping I'd like to know too, I can't use CTRL-C and the < key On Wed, 21 Jul 1999, medcure wrote: > > > Our DOS Application uses the keys, Ctrl-Home, Ctrl-Ins, Ctrl-Page up and > a few other keyboard commands to operate the program. Within a DOS EMU > session the keyboard is remapped resulting in the inability to use all > the commands that use the Ctrl key. Where can we find information on > how to remap the keyboard to meet the requirements of our application > within a DOS EMU session. > > Any assistance is greatly appreciated. > > > Thanks, > > [EMAIL PROTECTED] > > > > ------------------------------ From: Reinhard Karcher <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 08:26:52 +0200 Subject: Re: Keyboard Mapping At Wed, 21 Jul 1999 medcure wrote: > Our DOS Application uses the keys, Ctrl-Home, Ctrl-Ins, Ctrl-Page up and > a few other keyboard commands to operate the program. Within a DOS EMU > session the keyboard is remapped resulting in the inability to use all > the commands that use the Ctrl key. Where can we find information on > how to remap the keyboard to meet the requirements of our application > within a DOS EMU session. > Hi, try $_rawkeyboard = (1) in your dosemu.conf. Reinhard ------------------------------ From: Reinhard Karcher <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 08:28:27 +0200 Subject: Re: Having a problem with configuring DOSEMU At Tue, 20 Jul 1999 Donnie Oberst wrote: > I have a problem configuring DOSEMU to work with my dos partitioned > drive. I have got the drive mounted in Linux but I do not know how to > get DOSEMU to recognize it. Can you plese tell me step by step how to > make DOSEMU recognize the drive. Thanks. Hi, look for lredir in your dosemu documentation. But don't use lredir with freedos. freedos has lredir not yet imlemented. Reinhard ------------------------------ From: Prathibha Divya <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 06:36:06 -0400 (EDT) Subject: sharing data between xdos and linux application is there an efficient way to share data between Linux application and xdos? I am trying to port a huge 16-bit Real mode DOS application which includes a Hardware driver. My idea is to port the Hardware driver to Linux and keep the remaining 16-bit code running in xdos. Thanks. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ------------------------------ From: "Rodney Myrvaagnes" <[EMAIL PROTECTED]> Date: Wed, 21 Jul 1999 10:13:45 -0400 Subject: RH 6.0 hangs repeatably?? I have Redhat 6.0 sharing a disk with Win95 using Lilo. My Win95 became unstable (surprise) not because of linux. I wanted to delete the /windows/system directory on the vfat partition which I thought linux ought to be able to do. ls gave the munged files as ??????.??? while in Windows they looked like high-bit ascii. Any attempt to delete the contents caused a coredump, follewed by no prompt. I finally shut off the machine without proper shutdown. Linux rebooted fine and forced check on the file system, as it should. Attempting to do anything to the munged folder resulted in the same kind of crash. I finally copied all data files from the vfat partition into linux and reformatted the vfat partion to reinstall W95 clean. I can understand linux being unable to deal with filenames outside its character set, but I don't understand why this would cause such a severe reaction. Any gurus out there have a clue? Rodney Myrvaagnes J36 Gjo/a Associate Editor Electronic Products 20+ years without a car, a TV, or a website ------------------------------ End of linux-msdos-digest V1 #150 ********************************* To subscribe to linux-msdos-digest, send the command:
