linux-msdos-digest Tuesday, 5 October 1999 Volume 01 : Number 155 In this issue: ---------------------------------------------------------------------- From: Tasos Chronis <[EMAIL PROTECTED]> Date: Tue, 21 Sep 1999 15:17:43 +0300 Subject: Re: dosemu / floppies Bad floppy drive or bad floppy (very very common). try man badblocks "Bas R. Leeflang" wrote: > > Dear dosemu team, > > I have been trying to get dosemu (0.99.10-4, 0.99.10-6, RPM builds) to > work with floppies. After some non-succeful attemps with a kernel > upgrade (from RH 2.2.5-15 to 2.2.5-22) I tried browsing through > email-archives. Here the suggestion was made to downgrade to the 0.98.8 > version whih is a 'stable' release in stead of the 0.99 developer > release. > > This was an improvement in so far that the dosemu was so kind to com > back and tell me that it could not read the floppy. The error-logging, > however was rather similar: > > Sep 21 11:28:56 bocpc1 kernel: floppy0: sector not found: track 0, head 1, sector 1, >size 2 > > Sep 21 11:28:57 bocpc1 kernel: floppy0: sector not found: track 0, head 1, sector 1, >size 2 > > Sep 21 11:28:57 bocpc1 kernel: end_request: I/O error, dev 02:00 (floppy), sector 18 > > Dosemu produced these lines several times (once per second). > For my configuration the use of a stable release did not bring the > expected. > > Do you have any further suggestions. > > BTW the floppy hardware works fine. Both mtools and normal linux mounts > work fine for both the floppy and the hard disk partitions. > > Kindest regards, > > Bas Leeflang > > -- > Bio-Organic Chemistry group Dr. Bas R. Leeflang > Bijvoet Center for Biomolecuar Research Tel. : int+31.30.253.3498 > Utrecht University Fax : int+31.30.254.0980 > Padualaan 8, NL-3584 CH Utrecht Email: [EMAIL PROTECTED] > The Netherlands http://www.boc.chem.uu.nl ------------------------------ From: "Maciek Radzikowski" <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 13:49:40 CEST Subject: DOSEMU problem Please help. I wantd to use key combination : Alt F5, Ctrl F8, Alt P, Ctrl W in DOSEMU. How can I do it ? Regards Maciek from Poland. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ------------------------------ From: [EMAIL PROTECTED] Date: Wed, 22 Sep 99 15:49:11 MESZ Subject: Data transfer via serial port Is anybody (successfully :-) ) using dosemu to transfer data via a serial port ? We're trying to use a closed-source data transfer program with freedos, and while sending seems to work well (but slower than the selected baud rate would suggest), even small files (<10 kByte) cannot be received unmangled. The software does not detect any errors, but there are random blocks of data missing, suggestive of a buffer overrun. I guess that there is something amiss in the handshaking code , but would like to make sure that i am not missing any configuration options before i start digging. This with both the most recent 'stable' and 'development' versions off the dosemu.org site, and both recompiled to use the 'old' interrupt mechanism. (The latter makes transfer go slightly faster, but not better.) Configuring irq passing for interrupts 3 and 4 just makes the comm program hang immediately on startup. Any help is greatly appreciated... Martin - -- Dr. Martin Kroeker, daVeg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED] Precision Powered by Penguins ------------------------------ From: "ted katz" <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 12:21:00 -0400 Subject: keyboard and com keyboard decode problem Runnig redhat 5.2 and dosemu I have run into a keyboard decode problem the com program does commutate with the device but using the control key + ??? does not. I there a keyboard mapping file/script that needs to be modified? i.e. press the ctrl+f5 should open a file for capture, nothing happens. The F key work ok just the function of ctrl +** fails. Any help would be appreciated ------------------------------ From: Karsten Hilbert <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 19:51:30 +0200 (MESZ) Subject: Re: dosemu / floppies Hello ! Did you try to access the floppy several times in succession ? If your floppy driver is compiled as a module it won't find the floppy on the first attempt. The next one should do fine, though, since the modules is loaded then. This happened to me before. Did this help any ? Karsten (ncq) ------------------------------ From: Juergen Leising <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 20:15:52 +0200 Subject: Re: DOSEMU problem On Wed, Sep 22, 1999 at 01:49:40PM +0200, Maciek Radzikowski wrote: > Please help. > I wantd to use key combination : Alt F5, Ctrl F8, Alt P, Ctrl W > in DOSEMU. > How can I do it ? Hi, rawkeyboard=(1) At least this has helped me using this old word 5.0. Bye, Juergen. - -- ************************************************************************* * Juergen Leising, Germany http://leising.home.pages.de/ * * [EMAIL PROTECTED] http://leising.freeshell.org/ * ************************************************************************* ------------------------------ From: Juan Carlos Castro y Castro <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 17:32:52 -0300 Subject: The VGA font This is a multi-part message in MIME format. - --------------2CA8EDAA7653DB4DA9F20DE8 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I'd like to know if there's a version of the VGA font which matches codepage 850. xdos runs great in text mode, but when I type a capital accented "�" I get a text-box character. Thanx 4 any help, - --------------2CA8EDAA7653DB4DA9F20DE8 Content-Type: text/x-vcard; charset=us-ascii; name="jcastro.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Juan Carlos Castro y Castro Content-Disposition: attachment; filename="jcastro.vcf" begin:vcard n:Castro;Juan tel;work:55 (21) 540-9100 x-mozilla-html:FALSE url:http://www.appi.com.br/jcastro org:APPI Inform�tica Ltda.;Desenvolvimento adr:;;Av. Ataulfo de Paiva, 135/1410;Rio de Janeiro;RJ;22449-900;Brazil version:2.1 email;internet:[EMAIL PROTECTED] title:Consultor note:One man alone cannot fight the future. USE LINUX! x-mozilla-cpt:;28896 fn:Juan Carlos Castro y Castro end:vcard - --------------2CA8EDAA7653DB4DA9F20DE8-- ------------------------------ From: Rob Clark <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 18:26:05 -0500 Subject: $_hdimage=bootdir, LPT1 problem Re: dosemu-0.99.12 and .13 I switched a user from a standard hdimage to the new lredir'ed boot directory option to give him more disk space. Using the command "COPY AUTOEXEC.BAT LPT1" still works, but now his DOS application no longer prints. Now it creates a file called LPT1 in the working directory instead. Everything was fine using a hdimage-- must I switch back? Thanks, Rob Clark, [EMAIL PROTECTED] ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Wed, 22 Sep 1999 23:46:05 -0400 (EDT) Subject: Re: DOSEMU problem hi, just set $rawkeyboard=(1) in the /etc/dosemu.conf file. That should do it. On Wed, 22 Sep 1999, Maciek Radzikowski wrote: > Please help. > I wantd to use key combination : Alt F5, Ctrl F8, Alt P, Ctrl W > in DOSEMU. > How can I do it ? > Regards Maciek from Poland. > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > ------------------------------ From: "Alexander I. Evseev" <[EMAIL PROTECTED]> Date: Thu, 23 Sep 1999 10:56:45 +0600 Subject: FreeDOS Hallo! I have one problem: I am not able make hard disk image from floppy with FreeDOS Beta 3, bacause it version not contain Kernel.exe & IPL.sys, but only kernel.sys. And when I start setup-hdimage it nor work properly. When I try make image with mkfatimage16, it made image, but dos not loading. it type FAT ROOT and hunging up. Can you help me ? PS: Sorry my terrible english. - --- Alexander I. Evseev ([EMAIL PROTECTED]) Altai Regional Travel Agency ------------------------------ From: [EMAIL PROTECTED] (David Hodges) Date: Wed, 22 Sep 1999 09:42:11 +1200 (NZST) Subject: Re: CSDPMI under dosemu > I have tried to run 'Coach 8.2' under dosemu, but it requires CSDPMI to run, > which that reports 'Protected mode not accessible'. The Doc says this occurs > when already in protected mode, but when I try to run coach without CSDPMI > present, it says it needs it. It works under win95 without it, so it is not a > hardcoded check. Any ideas? You just need to put a line like $_dpmi = (4096) or however many kilobytes you need in /etc/dosemu.conf You don't need to use CSDPMI and you can't - CSDPMI won't work under dosemu, Win95 etc. ------------------------------ From: mundy matthew <[EMAIL PROTECTED]> Date: Thu, 23 Sep 1999 11:28:01 -0400 Subject: Re: CSDPMI under dosemu Thanks, I tried that. It didn't complain about CSDPMI now, but it just did not run ex. c:\>coach c:\> Maybe it's a setting I missed. Oh well, I'll keep working on it. Thanks Matt On Wed, 22 Sep 1999, David Hodges wrote: > > I have tried to run 'Coach 8.2' under dosemu, but it requires CSDPMI to run, > > which that reports 'Protected mode not accessible'. The Doc says this occurs > > when already in protected mode, but when I try to run coach without CSDPMI > > present, it says it needs it. It works under win95 without it, so it is not a > > hardcoded check. Any ideas? > > You just need to put a line like > $_dpmi = (4096) > > or however many kilobytes you need > in /etc/dosemu.conf > > You don't need to use CSDPMI and you can't - CSDPMI won't work under > dosemu, Win95 etc. > ------------------------------ From: "Trachier, Gary M CRL" <[EMAIL PROTECTED]> Date: Thu, 23 Sep 1999 16:45:45 -0400 Subject: DOSemu in background Hi All, Now that dos is running, and it can talk to the serial ports, the next step is to have it run in background. In looking at the dos manpage, it looks like the -U option and named pipes provides a mechanism to do this. It sounds like I can run dos with a command something like dos -U dosin:dosout & where dosin and dosout are named pipes and look like p-w------- 1 trachier users 7 Sep 23 14:27 dosin| pr-------- 1 trachier users 0 Sep 23 13:52 dosout| In one terminal window I used cat dosout to read from DOS's output pipe, and used printf "exitemu\n" > dosin on a second terminal window to write to DOS. What happens when I start dos on a third terminal window, I get the following message 100 myhost> kernel CPU speed is 451031025 Hz Running on CPU=586, FPU=1 [1] + Suspended (tty output) dos -U dosin:dosout 100 myhost> Beyond this, there is no response. I am using a new installation of RH6.0, and dosemu-0.99.10-4 . Do you have any suggestions, or short code examples to get me started? Thanks for your help. ~ Gary /--------------------------------------------------------------------------- \ | Gary Trachier / U. S. Army Cold Regions Research & Engineering Laboratory | | Internet: [EMAIL PROTECTED] | | CorpsMail: [EMAIL PROTECTED] | | Telephone: voice (603) 646-4303 fax (603) 646-4720 | | USnail: (.^.) USA CRREL / 72 Lyme Road / Hanover, NH USA / 03755-1290 | \--------A--U--A------------------------------------------------------------ / ------------------------------ From: Mike Duncan <[EMAIL PROTECTED]> Date: Thu, 23 Sep 1999 21:30:25 -0500 Subject: New beginner here Hello all, I have recently installed RH 6.0 and it seems to have also installed dosemu by default. The version is 0.99.10, which seems to be a development release, so I hope my questions can be answered. How do I set up dosemu to run programs off my dos drive? I have a partition devoted to Windows still and would like dosemu to see it (I think). There are several programs on there for my son that I would like to run under Linux. Whenever I type 'dos', the terminal goes blank, then returns to the Linux prompt again. What do I need to do in dosemu.conf to correct this? (If this is even the right file) When I try ./setup-hdimage, it returns with a 'cannot find ..../check-mtools' message--do I need to DL mtools to get this? It seems to have already been installed with Linux. Thanks for your patience, Mike My system: PII 233 Mhz Red Hat 6.0 on hda1/2/3 Windows 95 on hdb1 ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Fri, 24 Sep 1999 00:29:51 -0400 (EDT) Subject: Re: New beginner here first, I'd recommend uninstalling 99.10 and loading on 98.8. Then probably the easiest way to get at your dos drive is to create a subdirectory somewhere, for example /dos and copy the files from your dos boot disk into there. Then edit your dosemu.conf file and change the setting to the directory name. On Thu, 23 Sep 1999, Mike Duncan wrote: > Hello all, > > I have recently installed RH 6.0 and it seems to have also installed > dosemu by default. The version is 0.99.10, which seems to be a > development release, so I hope my questions can be answered. > > How do I set up dosemu to run programs off my dos drive? I have a > partition devoted to Windows still and would like dosemu to see it > (I think). There are several programs on there for my son that I would > like to run under Linux. Whenever I type 'dos', the terminal goes > blank, then returns to the Linux prompt again. What do I need to do in > dosemu.conf to correct this? (If this is even the right file) > > When I try ./setup-hdimage, it returns with a 'cannot find > ..../check-mtools' message--do I need to DL mtools to get this? It > seems to have already been installed with Linux. > > Thanks for your patience, > > Mike > > My system: > > PII 233 Mhz > Red Hat 6.0 on hda1/2/3 > Windows 95 on hdb1 > > ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Fri, 24 Sep 1999 10:47:21 +0200 (MEST) Subject: Re: DOSemu in background On Thu, 23 Sep 1999, Trachier, Gary M CRL wrote: > Now that dos is running, and it can talk to the serial ports, the next step > is to have it run in background. > [...] > > dos -U dosin:dosout & nope, don't expect dos{in,out} being STD{IN,OUT}. These pipes _only_ serve as _control_ communication between a frontend process (such as kdos, dosctrl) and DOSEMU. Have a look at src/base/misc/userhook.c on what input/ouput is expected and use dosctrl as a tiny example frontend. Hans <[EMAIL PROTECTED]> ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Fri, 24 Sep 1999 15:05:28 +0200 (MEST) Subject: RE: DOSemu in background On Fri, 24 Sep 1999, Trachier, Gary M CRL wrote: > That is unfortunate news, No reason to give up with this issue ;-) There are some limited ways to run DOSEMU in the background. However, STDIN can't be feed in via a pipe, you need the 'keystroke' feature to 'type-in' some few commands (rest has to be DOSish). Look at ./doc/README.txt chapter "Running a DOS-application directly from Unix shell" and especially "Running DOSEMU within a cron job". The below script would run DOSEMU, start an application 'myapp' and then exit. The (DOSish) output goes into the file '/tmp/outfile' : #! /bin/bash export TERM=dumb exec dos </dev/null 2>/dev/null >/tmp/outfile \ -I 'video{none} keystroke "myapp\rexitemu\r"'" ... and this script very well should run in the background ;-) Hans <[EMAIL PROTECTED]> ------------------------------ From: [EMAIL PROTECTED] Date: Fri, 24 Sep 1999 19:12:24 MET_DST Subject: RE: DOSemu in background > From: Hans Lermen <[EMAIL PROTECTED]> > However, STDIN can't be feed in via a pipe, you need the 'keystroke' > feature to 'type-in' some few commands (rest has to be DOSish). Unless I put necessary commands in AUTOEXEC.BAT; I found it to be useful to set a variable in environment, then run DosEmu, and read the variable in DOS, then select action based on the variable value. But seems the example you sent will help me a lot to simplify methods I use to run DOS applications from cron - thanks! ------------------------------ From: <[EMAIL PROTECTED]> Date: Fri, 24 Sep 1999 14:55:14 -0400 (EDT) Subject: Printing in DOSEMU Hi... we're running Dosemu 0.98.1, and I'm having trouble with printing with a specific tailor-made application that we have here. I'm trying to get it so that I can have a remote office connect to the system and print to their local printer. Sending a job directly to the printer (lp12) works, and if i copy a file to the lpt1 port from dosemu, it works, but printing from that application doesn't work unless a printer is directly attached to the computer. Is there any way around this, or any options or something that I could use.. I've been looking for information, and I hope that someone can help me here. Thanks, Ben ------------------------------ From: Niki <[EMAIL PROTECTED]> Date: Sat, 25 Sep 1999 13:14:41 -0400 Subject: dosemu on permedia 2 based card When I try to run any vga based program (let's say warcraft II or wing comander 1) it hangs. When I set EGA, hangs too. What configuration I must use in case I want to see some video programs with dosemu I am using Permedia 2 based card. BTW when I run vgaon it tays CANNOT INIT VIDEO MODE. VIDEO BIOS NOT MAPPED IN. but in the docs there is no word about mapping video bios or else. I am not using any cache on the video bios. Any sugestions? ------------------------------ From: Mike Warnecke <[EMAIL PROTECTED]> Date: Sat, 25 Sep 1999 17:53:03 -0600 (CST) Subject: End and Home keys don't show up under Xtermdos When running xtermdos under XFree86, I can't seem to make the End and Home keys work. Upon running dosemu with they key debugging, I get the following when pressing end: [00007015] KBD: do_slang_getkeys() [00007015] KBD: cc found 4 characters (Xlate) [00007015] KBD: do_slang_getkeys() found 4 bytes And that is it. Normally it will produce this while on the console: [00203068] KBD: do_slang_getkeys() [00203068] KBD: cc found 4 characters (Xlate) [00203068] KBD: do_slang_getkeys() found 4 bytes [00203068] KBD: scan=0000e04f Shift_Flags=00000000 str[0]=5 str='^[[3~'len=4 [00203068] KBD: slang_send_scancode(lscan=0000e04f, ch='') [00203068] KBD: putkey(PRESS, e04f, ' ') called [00203068] KBD: writing to queue: bios_key=0000 shift=0002 scan=0000e02a [00203068] KBD: writing to queue: bios_key=4fe0 shift=0002 scan=0000e04f [00203068] KBD: put_bios_keybuf(4fe0) [00203068] KBD: putkey(RELEASE, e04f, ' ') called [00203068] KBD: writing to queue: bios_key=0000 shift=0002 scan=0000e0d3 [00203068] KBD: writing to queue: bios_key=0000 shift=0002 scan=0000e0aa What could cause this, and how do I fix it? I'm running dosemu 0.98.5.0 from the RedHat 6 rpm. I use rxvt as the terminal. Any help is greatly appreciated! Thanks, Mike Warnecke | Database Export (Records/Second) IT Manager | Linux: --------209.0-----------> 67s Audio Warehouse/ | NT: -40.3> 347s Century Sound & Music | Case closed. Open source rocks! ------------------------------ From: Justin Wheeler <[EMAIL PROTECTED]> Date: Mon, 27 Sep 1999 04:18:35 -0400 Subject: bla My apologies for bothering all of you .. but I have one simple question, First, before asking, I'd like to say VERY nice piece of software you have here ... a bit confusing at times, but it is amazing software. My question is: I have an ATI 3D Rage II+DVD card, and I set the ati in the conf file and everything, but I want to be able to run the m64diag program that came with the card for diagnostics, and testing of the card, as no such programs exist for linux ... now, I realize that I could easily just boot to DOS, but I'd like to make use of your software... when I attempt to run the program, I get the following: ERROR: general protection at 0x89ef: 66 ERROR: SIGSEGV, protected insn...exiting! .... The software I am using is freely available in the file UTL-314.EXE which can be found on the www.atitech.ca webpage under support for the card mentioned above in DOS. My apologies for taking up your time, Best regards, Justin Wheeler [EMAIL PROTECTED] ------------------------------ From: "A.Vignani" <[EMAIL PROTECTED]> Date: Mon, 27 Sep 1999 18:49:48 +0200 Subject: Re: bla Justin Wheeler wrote: > > My apologies for bothering all of you .. but I have one simple question, > > First, before asking, I'd like to say VERY nice piece of software you > have here ... a bit confusing at times, but it is amazing software. My > question is: I have an ATI 3D Rage II+DVD card, and I set the ati in > the conf file and everything, but I want to be able to run the m64diag > program that came with the card for diagnostics, and testing of the > card, > as no such programs exist for linux ... now, I realize that I could > easily > just boot to DOS, but I'd like to make use of your software... when I > attempt to run the program, I get the following: > > ERROR: general protection at 0x89ef: 66 > ERROR: SIGSEGV, protected insn...exiting! > > .... The software I am using is freely available in the file UTL-314.EXE > > which can be found on the www.atitech.ca webpage under support for > the card mentioned above in DOS. My apologies for taking up your time, > > Best regards, > Justin Wheeler > [EMAIL PROTECTED] Tried it on my Ati Rage Pro, with dosemu-0.99.13. I don't see any SIGSEGV, but the program exits because it says it can't find a Mach64 chip. Looking into the debug logs I saw many accesses to high IO ports (in the ranges 0xe0e0..0xffe0); I tried to add some ports and once the program said Mach64 was there but its aperture could not be initialized, etc. It looks like there are a lot of 'exotic' IO addresses involved. I suggest you to forget this diagnostic program. You would have to fiddle with these very dangerous IO accesses and possibly crash the entire machine. Alberto ------------------------------ From: Enrico Weigelt <[EMAIL PROTECTED]> Date: Sat, 25 Sep 1999 21:29:42 +0000 Subject: HELP! dosemu crashes X if i start dosemu (0.98.4.0) on the console and then switch to X, my Xserver crashes. it keeps still running, but i'm not able to do any inputs anymore. whith xdos i've got no trouble. what'S the problem ? ew. - ------------------------------------------- lets go to another world ... oberon ------------------------------ From: hawk <[EMAIL PROTECTED]> Date: Tue, 28 Sep 1999 10:18:11 +0200 Subject: Re: HELP! dosemu crashes X Hi. Enrico Weigelt wrote: > if i start dosemu (0.98.4.0) on the console and then switch to X, > my Xserver crashes. it keeps still running, but i'm not able to > do any inputs anymore. This is my problem > > > whith xdos i've got no trouble. > > what'S the problem ? > > ew. > ------------------------------------------- > lets go to another world ... oberon - -- Hawk , SuSE6.1 Kernel2.2.9, KDE1.1 mailto: [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] ------------------------------ From: Enrico Weigelt <[EMAIL PROTECTED]> Date: Tue, 28 Sep 1999 14:51:42 +0000 Subject: Re: HELP! dosemu crashes X hawk wrote: > > Hi. > > Enrico Weigelt wrote: > > > if i start dosemu (0.98.4.0) on the console and then switch to X, > > my Xserver crashes. it keeps still running, but i'm not able to > > do any inputs anymore. > > This is my problem > hmm.. i've updated my system (from SuSE6.0 to SuSE 6.2 - new X, but no new dosemu) and now all works fine. was there a bug in the old XF86 ? but i still have such problems, if i send a STOP signal to dosemu (okay, perhaps i should not do that ... ) ew. - ------------------------------------------- lets go to another world ... oberon ------------------------------ From: Valentijn Sessink <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 12:15:40 +0200 Subject: Font selection anomality Hello all, I think I'm going to report a WindowMaker bug, but I'm not sure. Please read on :) I finished a fine 10x20 font for DOSemu, and while that worked well I decided to put DOSemu in my Windowmaker menu. This popped up the regular VGA font. Huh? Looking further with -D9-a+cX showed a couple of differences, starting with xterm xdos saying: CONF: dosemu running on _xterm and the menu one saying: CONF: dosemu running on console CHIPSET: 0 CONF: VGA-BIOS.... etcetera. And yes: making a menu item with "xterm -e /usr/bin/xdos" worked like it should. I don't know if this is a DOSemu bug or a Windomaker one - supplying the wrong $0. My DOSemu version is 0.99.11, but to check/doublecheck I also tried 0.99.13. Same thing. Valentijn p.s. not on the mailing list - a reply to [EMAIL PROTECTED] is appreciated. - -- ------------------------------ From: Jon Schneider <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 12:26:57 +0100 Subject: linux only I thought dosemu was a dos emulator for many x86 unixen. Now it appears to have gone all proprietry. Why ? Jon ------------------------------ From: Keith Duthie <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 00:19:13 +1200 (NZST) Subject: alsa sound support? Is anyone working on alsa sound support for dosemu? - -- Understanding is a three edged sword. Do you *want* to get the point? http://www.albatross.co.nz/~psycho/ O- ------------------------------ From: "bkiev" <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 19:52:37 +0400 Subject: foxprox.exe 2.6 in dosemu Hi everybody ! I can not run foxprox.exe under dosemu . The application demands much memory so foxpro.exe does not fit . I suppose $_dpmi should been set . After I set it ( $_dpmi = (4000) ) and run foxprox.exe the dosemu give me a message 'segmentation fault' and crash . I've tried it on dosemu 0.99.13 and hdimage msdos 6.22 . Does anybody have any success in such matter ? Thanks advance for answer Sergey ------------------------------ From: Enrico Weigelt <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 14:48:34 +0000 Subject: Re: HELP! dosemu crashes X hawk wrote: > <snip> > > My linux is a SuSE6.1. When I running the dos-emu in the terminal-mod and > switching to the X-server, then the mouse is freez. I've now updated to SuSE 6.2 - new XF86, but still the old dosemu - all works fine now. before the upgrade i've used an SVGA server, now i'm using an acceleted RivaTNT server. perhaps there were some bugs in the old XF86 ... > The graphical dos applications is not running in the emulator or if is > start , then not use the klaviatura and mouse. hmm.. i also had problems with graphics some time ago, i've tried some options in dosemu.conf, but didn't help. (but it already had worked before!). so i reinstalled it completely - and it worked. > My video-card is a ATI 3D Rage II/c 4MB Ram AGP , X-server is a > Xfree3.3.3 > (with ATI 3D charger driver). > The DOS -games not work in the dos-emu and not have a sound of the > applications > ... Why? And what can I do? i never tried it on my current machine. on my old machine [am486,sb16,4MBram] it worked fine. there are some options for it in dosemu.conf. dosemu can emulate an sb16 and redirects the data to any oss compatible device. (try sb emulation or something like that) bye, ew. - ------------------------------------------- lets go to another world ... oberon ------------------------------ From: [EMAIL PROTECTED] (David Hodges) Date: Thu, 30 Sep 1999 08:05:39 +1200 (NZST) Subject: Re: linux only > > I thought dosemu was a dos emulator for many x86 unixen. Now it appears to > have gone all proprietry. Not proprietary, just Linux-only. > Why ? Because the NetBSD etc. developers haven't bothered to make the latest versions of dosemu work on their operating systems. The only people maintaining dosemu are Linux users. It probably does still work on NetBSD to some extent but not all of the features will work ------------------------------ From: "Alejandro Nestor Vargas" <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 17:28:38 -0300 Subject: RE: foxprox.exe 2.6 in dosemu > I can not run foxprox.exe under dosemu . The application demands much > memory so foxpro.exe does not fit . I suppose $_dpmi should been set . > After I set it ( $_dpmi = (4000) ) and run foxprox.exe the dosemu give me > a message 'segmentation fault' and crash . > I've tried it on dosemu 0.99.13 and hdimage msdos 6.22 . Check the parameters in the command line of foxprox and make it match the $_dpmi value. A friend tells me that foxprox needs 16 MB of RAM to run! ------------------------------ From: "Alejandro Nestor Vargas" <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 17:29:41 -0300 Subject: .dexe Hello. I am developing a software under linux, but it needs to call other program provided by other persons. They provide me various versions of this software: msdos exe, win32 exe, msdos LIB (library), and DLL 32 bits (library). I asked for a way to link the lib into my C program, but it seems to be unpossible. Then, I runned the msdos version under dosemy with good results. But I want to accelerate the execution of the program. The README.txt file of dosemy talks about mkdexe script that is included in mtools, but I can't find it. Not in bynary nor in source packets. Somebody can tell me where to find mkdexe or help me in order to link the lib or dll version of the program? ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Wed, 29 Sep 1999 23:15:55 +0100 (BST) Subject: Re: alsa sound support? On Thu, 30 Sep 1999, Keith Duthie wrote: > Is anyone working on alsa sound support for dosemu? Given that one of the stated aims of the ALSA project is compatability with the OSS interface, the current code should work with ALSA. There was some code for midid which was written to support the ULTRA driver (the precursor to the ALSA project ?) and this may or may not work with ALSA. Should anyone want to write an ALSA driver then feel free - all I ask is that you tell me first (so I can ensure we don't get duplication of effort) and send patches directly to me. Alistair ------------------------------ From: "bkiev" <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 12:41:56 +0400 Subject: foxprox.exe 2.6 in dosemu (solved) My problem was $_cpu="80586" but should be $_cpu = "80386" although my cpu is pentium . thanks for attention Sergey ------------------------------ From: "White, Bob" <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 06:58:56 -0500 Subject: Autoexec.bat Hi All, I am having trouble with a DOS application which loads by way of a .bat file. In the .bat file there are commands to load other files using %1 %2 %3 etc... It seems the program quits loading and freezes. Is there a setting in dosemu.conf or a path statement I need to add to get this to work. For that matter what should my path statement have in it? Also, how do you exit dosemu and get back to the linux command line? TIA Bob White [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ------------------------------ From: "Gregory Doyle" <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 06:21:51 -0700 Subject: xdos error and display problems I have installed dosemu 0.99.10-4 which came with RH 6.0 that I have alsoinstalled. I am using Caldera DR-DOS 7.02. When I run xdos I get the following error messages: ERROR X unable to open font "vga"ERROR: , trying "vga"... ERROR X unable to open font "vga"ERROR: , trying "9x15"... Following the error messages xdos then runs. I was trying to run a Clipper Program. The Program runs, however, the box and line drawing characters come out as strange foreign characers. I have set the Term_Char_Set to 'ibm' hoping this would help. I have also run dosemu from the console, where I get the line and box characters display correctly, but the colours of the display are messed up to such a degree that it is very difficult to read some things on the screen. Anyhow I was wondering if anybody could offer me some advice on how I could go about fixing this problem. Thanks so much, G. P. Doyle - --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. ------------------------------ From: Ian Carr-de Avelon <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 15:28:25 +0100 Subject: EMU Fail MACHXL I get a failure if I try to use MACHXL2.1 (a program for programing PALs available free from www.vantis.com.) This is a pity as there is no Linux software available to do the same thing. Unfortunately reading EMUfailure.txt seems to indicate that there is no likely fix for this: C:\MACHXL\EXE>machxl Fatal Error 286.1020: This program requires VCPI or DPMI in V86 mode. Does anyone have any other ideas? Yours Ian ------------------------------ From: Keith Duthie <[EMAIL PROTECTED]> Date: Fri, 1 Oct 1999 01:51:35 +1200 (NZST) Subject: Re: xdos error and display problems On Thu, 30 Sep 1999, Gregory Doyle wrote: > ERROR X unable to open font "vga"ERROR: , trying "vga"... > ERROR X unable to open font "vga"ERROR: , trying "9x15"... Did you do "xset fp rehash" in X? - -- Understanding is a three edged sword. Do you *want* to get the point? http://www.albatross.co.nz/~psycho/ O- ------------------------------ From: "Alejandro Nestor Vargas" <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 11:41:46 -0300 Subject: RE: Autoexec.bat - ----- Mensaje original ----- De: White, Bob <[EMAIL PROTECTED]> Para: <[EMAIL PROTECTED]> Enviado: Jueves, 30 de Septiembre de 1999 08:58 a.m. Asunto: Autoexec.bat > Also, how do you exit dosemu and get back to the linux command line? Use exitemu.com to exit dosemu. ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 23:15:00 +0200 (MEST) Subject: Re: foxprox.exe 2.6 in dosemu (solved) On Thu, 30 Sep 1999, bkiev wrote: > My problem was $_cpu="80586" but should be $_cpu = "80386" although my cpu is > pentium . ... to make it clear: The $_cpu setting simply influences the flag settings shown to DOS, hence what the DOS-application _detects_ as CPU. DOSEMU itself does not react on $_cpu otherwise. However, if your DOS application adapts to the CPU it is detecting, then it will most likely use different code for different CPUs. In the case of foxprox it looks like restricting to 386 code avoids problems with DOSEMU. Conclusion: With $_cpu="80386" you beg the DOS-application to use 386-code only, ... nothing more. Hans <[EMAIL PROTECTED]> ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Thu, 30 Sep 1999 18:14:50 -0400 (EDT) Subject: Re: xdos error and display problems I had a similar problem and if I remember correctly, installing the stable version of dosemu (98.8) solved it. Hope this helps.. On Thu, 30 Sep 1999, Gregory Doyle wrote: > I have installed dosemu 0.99.10-4 which came with RH 6.0 that I have alsoinstalled. >I am using Caldera DR-DOS 7.02. When I run xdos I get the following error messages: > ERROR X unable to open font "vga"ERROR: , trying "vga"... > ERROR X unable to open font "vga"ERROR: , trying "9x15"... > Following the error messages xdos then runs. I was trying to run a Clipper Program. > The Program runs, however, the box and line drawing characters come > out as strange foreign characers. I have set the Term_Char_Set to 'ibm' hoping this >would help. > I have also run dosemu from the console, where I get the line and box characters >display correctly, but the colours of the display are messed up to such a degree that >it is very difficult to read some things on the screen. > Anyhow I was wondering if anybody could offer me some advice on how I could go about >fixing this problem. > > Thanks so much, > > G. P. Doyle > > > --== Sent via Deja.com http://www.deja.com/ ==-- > Share what you know. Learn what you don't. > ------------------------------ From: Ian Carr-de Avelon <[EMAIL PROTECTED]> Date: Fri, 1 Oct 1999 13:27:58 +0100 Subject: EMU sucess MACHXL Many thanks for all those who in response to my question tipped me off to try DPMI. I had been lead astray by the reference to VCPI in EMUfailure.txt. This file is in dosemu-0.98.8/doc/, although one corespondent thought that it is outdated and nolonger in the distribution. The program now starts. Yours Ian ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Sat, 2 Oct 1999 00:48:28 +0100 (BST) Subject: Re: xdos error and display problems On Thu, 30 Sep 1999, Gregory Doyle wrote: > I have installed dosemu 0.99.10-4 which came with RH 6.0 that I have > alsoinstalled. I am using Caldera DR-DOS 7.02. When I run xdos I get > the following error messages: > ERROR X unable to open font "vga"ERROR: , trying "vga"... > ERROR X unable to open font "vga"ERROR: , trying "9x15"... > Following the error messages xdos then runs. Either none of the DOSEMU fonts were installed, or, as the other mail suggested, you haven't run the 'xset fp rehash' command. You should not have to run this command if you have started X more recently than the installation of DOSEMU. The other mail mentioned it was solved by installing a previous version of DOSEMU. This is probably because this installation used *OUR* RPM file, not a RedHat one. It looks like RedHat have a broken RPM - quite aside from their ridiculous decision to include a *developer* copy of DOSEMU on a "production" release of their CDs. If the font is missing from your X font directories then you might want to consider either upgrading to one of our RPMs, installing from source, or getting a VGA font from somewhere. We have one in the contrib directory of your favourite ftp.DOSEMU.org mirror. > I was trying to run a Clipper Program. The Program runs, however, the > box and line drawing characters come > out as strange foreign characers. This is to be expected if you don't have the correct font. > I have set the Term_Char_Set to 'ibm' hoping this would help. Thats *Term*_Char_Set, not *XTerm*_Char_Set. It doesn't apply to xdos. > I have also run dosemu from the console, where I get the line and box > characters display correctly, but the colours of the display are messed > up to such a degree that it is very difficult to read some things on the > screen. Sounds like you were either running on a video card that isn't handled correctly, or you were running it at the same time as running X. Alistair ------------------------------ From: Daniel Maes <[EMAIL PROTECTED]> Date: Mon, 04 Oct 1999 22:57:42 +0000 Subject: dosemu Dear sir , I have SuSE 6.2 , and try to work with Linux . I like to run some old Dos-programs ( I made tem myself with Clipper ) in Linux . But .... When I try to start dos or dos -X , I see 'now I start Windows' and then the content of the autoexec.bat , and All stops !! I have to warm-boot the computer . What's going on , and what's wrong . Can you make suggestions a newbie , Daniel Maes [EMAIL PROTECTED] ------------------------------ From: "Dr. Harishankar Ramachandran" <[EMAIL PROTECTED]> Date: Tue, 5 Oct 1999 15:04:07 +0530 Subject: Problems with dosemu Hi, I have just got dosemu-0.98.1-2 istalled and working (I know 0.98.8 is the latest version and will check it out soon), and have some problems. I am running linux 2.0.36-0.7, from the Redhat 5.1 distribution, and have dos 6.22 with windows 3.1 on /dev/hda1. First what works: 1. I could get dos and xdos to work. This took some doing especially as the "setup-hdimage" script was missing in my installation (Redhat 5.1 distribution). However, I tinkered and got things to work. (Basically I violated rule 0 and put /dev/hda1 as my first hdimage, booted off it and then transferred the system to the freedos image. It worked, which justifies all :^) 2. I could get even a graphics program that used ega graphics to run under xdos. What does not work: 1. The graphics program uses CTRL-BREAK as the escape key it listens to. Unfortunately I can't get this to do anything in xdos. I tried setting rawkeyboard to "1" but that did not help. Any ideas how I can get this key combination to work? (I cannot change the DOS program, for which I have only the executable). 2. The program has a choice of ega and cga under which it works. The CGA mode does not work, complaining that the video mode cannot be set under the current screen. (I am running 1024x768 with 8 bit colour as my linux screen). Any ideas how I can get CGA to work? Strange as it may seem, I require that mode :^) 3. The colours are completely messed up. The ega graphics should have been white on black, and showed up as blue on black and hardly visible. The rest of the screen was completely mangled as well. However, everything cleared up once the ega mode was exited. 4. The "dexe" facility also seems to be missing in my distribution. What I finally did was to have autoexec.bat look for an "autorun.bat" in a lredir'd partition and if it existed, to execute it. For my current purposes, it is satisfactory, but hardly elegant. What did _not_ work was an attempt to ask dosemu to startup on an alternate "autoexec" file via xdos -I '$_emubat=101" ' (I tried various combinations of single and double quotes and escaping the $ and so forth, but no luck). What is the proper way to ask dosemu to boot off of an alternate set of files? [Note that I ran as a priveliged _user_, i.e., gave my user account "c_all" permission.] Thanks to anyone who can help/advise. hari ramachandran Institute for plasma research [EMAIL PROTECTED] ps: Information on my system: Celeron 350 MHz, SiS 6215 SVGA card. pps: Changes in my dosemu.conf: $_video = "vga" # tried ega and even cga, but no use $_console = (1) # no observable effect $_graphics = (1) # no observable effect $_chipset = "plainvga" # The SiS chipset is not supported by dosemu $_hdimage = "hdimage.first" # this is the default, actually. The graphics settings did not do anything to solve the problem, though the rest of the screen looks slightly less wierd with these settings. ------------------------------ From: "Alejandro Nestor Vargas" <[EMAIL PROTECTED]> Date: Tue, 5 Oct 1999 10:28:26 -0300 Subject: RE: dosemu - ----- Mensaje original ----- De: Daniel Maes <[EMAIL PROTECTED]> Para: <[EMAIL PROTECTED]> Enviado: Lunes, 04 de Octubre de 1999 07:57 p.m. Asunto: dosemu > Dear sir , > > I have SuSE 6.2 , and try to work with Linux . > I like to run some old Dos-programs ( I made tem myself with Clipper ) > in Linux . But .... > When I try to start dos or dos -X , I see 'now I start Windows' and then > the content of the autoexec.bat , and All stops !! I have to warm-boot > the computer . > What's going on , and what's wrong . > Can you make suggestions Make a boot diskette and try starting dos -A in order to boot from this diskette. If this works, try sys c: ------------------------------ From: "Julia A . Case" <[EMAIL PROTECTED]> Date: Tue, 5 Oct 1999 16:10:51 -0400 Subject: Virtual Com Port - --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii A few years ago I wrote a patch to dosemu to use virtual modems. I'm unable to make it work under the current releases of dosemu. Is someone able to help me update my diff to work better with the current dosemu? I'll attach the diff as a attachment. Julie - -- [ Julia Anne Case ] [ Ships are safe inside the harbor, ] [Programmer at large] [ but is that what ships are really for. ] [ Admining Linux ] [ To thine own self be true. ] [ Windows/WindowsNT ] [ Fair is where you take your cows to be judged. ] - --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dosdoors.diff" diff -ru dosemu/src/base/init/lexer.l dosemu-0.63.1.33/src/base/init/lexer.l - --- dosemu/src/base/init/lexer.l Sat Jun 8 11:28:51 1996 +++ dosemu-0.63.1.33/src/base/init/lexer.l Thu Jun 13 16:02:00 1996 @@ -147,6 +147,7 @@ baudrate return(BAUDRATE); device return(DEVICE); com return(COM); +virtual return(VIRTUAL); /* lock file stuff */ directory return(DIRECTORY); diff -ru dosemu/src/base/init/parser.y dosemu-0.63.1.33/src/base/init/parser.y - --- dosemu/src/base/init/parser.y Sun Jun 9 14:08:28 1996 +++ dosemu-0.63.1.33/src/base/init/parser.y Thu Jun 13 16:05:23 1996 @@ -60,6 +60,7 @@ static int c_hdisks = 0; static int c_fdisks = 0; +extern int no_local_video; extern struct printer lpt[NUM_PRINTERS]; static struct printer *pptr; static struct printer nullptr; @@ -152,7 +153,7 @@ /* lock files */ %token DIRECTORY NAMESTUB BINARY /* serial */ - -%token BASE IRQ INTERRUPT DEVICE CHARSET BAUDRATE +%token BASE IRQ INTERRUPT DEVICE CHARSET BAUDRATE VIRTUAL /* mouse */ %token MICROSOFT LOGITECH MMSERIES MOUSEMAN HITACHI MOUSESYSTEMS BUSMOUSE PS2 %token INTERNALDRIVER EMULATE3BUTTONS CLEARDTR @@ -612,6 +613,9 @@ | serial_flags serial_flag ; serial_flag : DEVICE STRING { strcpy(sptr->dev, $2); free($2); } + | VIRTUAL { sptr->virtual = TRUE; + no_local_video = 1; + strcpy(sptr->dev, ttyname(0)); } | COM INTEGER { sptr->real_comport = $2; com_port_used[$2] = 1; } | BASE INTEGER { sptr->base_port = $2; } @@ -1009,6 +1013,7 @@ sptr->real_comport = 0; sptr->fd = -1; sptr->mouse = 0; + sptr->virtual = FALSE; } } diff -ru dosemu/src/base/serial/ser_init.c dosemu-0.63.1.33/src/base/serial/ser_init.c - --- dosemu/src/base/serial/ser_init.c Sat Mar 2 13:26:47 1996 +++ dosemu-0.63.1.33/src/base/serial/ser_init.c Thu Jun 13 16:26:31 1996 @@ -54,6 +54,8 @@ #include "serial.h" #include "ser_defs.h" +int no_local_video = 0; + /* See README.serial file for more information on the com[] structure * The declarations for this is in ../include/serial.h */ @@ -206,18 +208,29 @@ if (com[num].fd != -1) return (com[num].fd); - - if ( tty_lock(com[num].dev, 1) >= 0) { /* Lock port */ - - /* We know that we have access to the serial port */ - - com[num].dev_locked = TRUE; - - - - /* If the port is used for a mouse, then remove lockfile, because - - * the use of the mouse serial port can be switched between processes, - - * such as on Linux virtual consoles. - - */ - - if (com[num].mouse) - - if (tty_lock(com[num].dev, 0) >= 0) /* Unlock port */ - - com[num].dev_locked = FALSE; + if ( com[num].virtual ) + { + if (tty_lock(com[num].dev, 0) >= 0) + { + dbug_printf("Opening Virtual Port\n"); + com[num].dev_locked = FALSE; + com[num].fd = 0; + no_local_video = 1; + } } + else + if ( tty_lock(com[num].dev, 1) >= 0) { /* Lock port */ + /* We know that we have access to the serial port */ + com[num].dev_locked = TRUE; + + /* If the port is used for a mouse, then remove lockfile, because + * the use of the mouse serial port can be switched between processes, + * such as on Linux virtual consoles. + */ + if (com[num].mouse) + if (tty_lock(com[num].dev, 0) >= 0) /* Unlock port */ + com[num].dev_locked = FALSE; + } else { /* The port is in use by another process! Don't touch the port! */ com[num].dev_locked = FALSE; @@ -497,8 +510,10 @@ /* Pull down DTR and RTS. This is the most natural for most comm */ /* devices including mice so that DTR rises during mouse init. */ - - data = TIOCM_DTR | TIOCM_RTS; - - ioctl(com[num].fd, TIOCMBIC, &data); + if(!com[num].fd, TIOCMBIC, &data) { + data = TIOCM_DTR | TIOCM_RTS; + ioctl(com[num].fd, TIOCMBIC, &data); + } } diff -ru dosemu/src/base/serial/ser_irq.c dosemu-0.63.1.33/src/base/serial/ser_irq.c - --- dosemu/src/base/serial/ser_irq.c Sun Feb 4 19:03:24 1996 +++ dosemu-0.63.1.33/src/base/serial/ser_irq.c Thu Jun 13 16:15:46 1996 @@ -210,10 +210,16 @@ ioctl(com[num].fd, TIOCMGET, &control); /* WARNING: Non re-entrant! */ - - newmsr = convert_bit(control, TIOCM_CTS, UART_MSR_CTS) | - - convert_bit(control, TIOCM_DSR, UART_MSR_DSR) | - - convert_bit(control, TIOCM_RNG, UART_MSR_RI) | - - convert_bit(control, TIOCM_CAR, UART_MSR_DCD); + if(com[num].virtual) + newmsr = UART_MSR_CTS | + convert_bit(control, TIOCM_DSR, UART_MSR_DSR) | + convert_bit(control, TIOCM_RNG, UART_MSR_RI) | + UART_MSR_DCD; + else + newmsr = convert_bit(control, TIOCM_CTS, UART_MSR_CTS) | + convert_bit(control, TIOCM_DSR, UART_MSR_DSR) | + convert_bit(control, TIOCM_RNG, UART_MSR_RI) | + convert_bit(control, TIOCM_CAR, UART_MSR_DCD); delta = msr_compute_delta_bits(com[num].MSR, newmsr); diff -ru dosemu/src/env/video/terminal.c dosemu-0.63.1.33/src/env/video/terminal.c - --- dosemu/src/env/video/terminal.c Sat Jan 27 15:49:32 1996 +++ dosemu-0.63.1.33/src/env/video/terminal.c Thu Jun 13 16:24:06 1996 @@ -59,6 +59,8 @@ * 001 000 Underline * anything else is invalid. */ +extern int no_local_video; + static int BW_Attribute_Map[256]; static int Color_Attribute_Map[256]; @@ -180,8 +182,12 @@ rotate[4] = 1; rotate[5] = 5; rotate[6] = 3; rotate[7] = 7; - - Video_term.update_screen = slang_update; - - + if(no_local_video!=1) { + Video_term.update_screen = slang_update; + } + else + Video_term.update_screen = NULL; + SLang_Exit_Error_Hook = sl_exit_error; SLtt_get_terminfo (); diff -ru dosemu/src/include/serial.h dosemu-0.63.1.33/src/include/serial.h - --- dosemu/src/include/serial.h Sun Feb 4 19:03:25 1996 +++ dosemu-0.63.1.33/src/include/serial.h Thu Jun 13 16:01:04 1996 @@ -56,6 +56,7 @@ int real_comport; /* The actual COMx port number. 0 for invalid */ int base_port; /* Base port address handled by device */ int interrupt; /* IRQ line handled by device */ + boolean virtual; /* virtual modem */ boolean mouse; /* Flag to turn on mouse sharing features */ boolean dev_locked; /* Flag to indicate that device is locked */ boolean fossil_active; /* Flag: FOSSIL emulation active */ - --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=README [Patch for dosemu-0.63.1.33 (should work with 0.63.1.19 also] I'm not much of a documentation writer so if all this doesn't make sense feel free to write me at [EMAIL PROTECTED] for more info. I wanted a better way of running doors than in local mode via dosemu. And this is what I managed to do to fix that problem. This patch will allow you to add an additional keyword to the serial configuration in dosemu.conf. The 'virtual' flag will allow you to set the current tty that dosemu is running on to be a virtual modem. For things to work right you need to make the following changes in your dosemu.conf file. 1. Remove all video definitions but the terminal. This forces terminal mode. Which we need to avoid local video. 2. add serial { virtual com 1 } this makes the current tty COM1 Now when you run an dosemu it will only display the data that is going to the COM port. A DOS door can be run in remote mode vs. the local mode that we have all been running them in. On bug that I've found is that on a non-modem tty the speed defaults to 2400 baud. I tried to change this in dosemu, but it really didn't work. What I did find that works though is to get down X00v150.ZIP. X00 is a very good fossil, which some doors will need, beyond that though it has a utility called XU.EXE that lets you set the port speed, I call this from autoexec and set the port speed to 57600 and everything works fine. This should allow for RIPScrip doors to be run, but at present my testing has show the acceptance of my terminal being RIP compatable to be less than reliable. I'm not sure what is causing that. I'll keep looking at it though. I've run the following doors via this mode. 1. Solar Realms Elite 2. Barren Realms Elite 3. Falcons Eye 4. Global Wars 5. Terra Firma 6. Legend of the Red Dragon 7. Exitilus [Change Log] 29Jan96 First Release (DosEMU-0.60.3) 30Jan96 Fix for Carrier detect on actual modem lines 12Jun96 Updated for 0.63.1.33 release of DosEMU - --FCuugMFkClbJLl1L-- ------------------------------ End of linux-msdos-digest V1 #155 ********************************* To subscribe to linux-msdos-digest, send the command:
