linux-msdos-digest Tuesday, 6 April 1999 Volume 01 : Number 138 In this issue: ---------------------------------------------------------------------- From: becker <[EMAIL PROTECTED]> Date: Tue, 23 Mar 1999 17:19:51 +0100 Subject: AW: Extra form-feed when printing from dosemu > -----Ursprungliche Nachricht----- > Von: Russell Poyner [SMTP:[EMAIL PROTECTED]] > Gesendet am: Dienstag, 23. Marz 1999 15:02 > An: [EMAIL PROTECTED] > Betreff: Extra form-feed when printing from dosemu > > I am slowly inching toward moving the network at my wife's veterinary clinic > from OS/2 to linux/dosemu. The one critical application is a custom database > that runs under dos. It works fine under dosemu 0.98 and rh5.1 at home except > that I always get an extra form feed when printing, wasting a sheet of paper. > I have tried various choices of print filter available in the rh print-tool to > no avail. > > Is there a switch/setting for dosemu that I missed in my rtfm-ing or is it a > matter of getting the right settings in etc\printtab? All suggestions welcome > including pointers to docs I have missed. > > Thanks > Russ Poyner hi, strange that I have had the very same problem with a printer setup using SAMBA. (Thats a program that lets you use the Unix server as a Win95 workgroups file server). At least the "shared" printer on the Linux Server would ALWAYS give a form feed after the job. I only found a "work around" and not a solution. If someone has a solution then please post it: I'm listening. I noticed one day that a similar instaltion using a postscript printer handled the Queue's correctly (without the Formfeed). What I was using was a HP - LaserJet. So I installed my HP-Laserjet "as if it" were a postscript printer (without the printing filter) and then only used the "RAW printer" to printer to. This worked for me. Note that I only using this printer for workstations on the Win95 side. Maybe someone knows more about this.... my regards, Stefan Becker email:[EMAIL PROTECTED] ------------------------------ From: Etienne Verhoef <[EMAIL PROTECTED]> Date: Wed, 24 Mar 1999 12:55:16 +0100 Subject: introducing CargoFinder! Dear Sir/ Madam, Increasing global competitive pressure is leading carriers and shippers to rethink sales, marketing and distribution strategies. It is apparent that supply chain management, globalisation and IT implementation are the important drivers which will propel logistics into the new millennium. CargoFinder is combining all these "drivers" and provides the transportation and logistic industries with the unique opportunity to improve the cargo distribution efficiency by making full use of the Internet as the communication tool and global gateway for business activities. CargoFinder is not merely a new trading mechanism, but a revolutionary and powerful management and marketing tool for the transport industry and gives all players the opportunity to achieve maximum capacity and efficiency in shipping goods around the world. CargoFinder provides for the ability to place offers and inquiries for freight and freight capacity (regardless of the modality), up-to-date market information and an easy and inexpensive tool to get in contact with new business relations. A placed shipper's inquiry for transport is immediately forwarded to all the registered transport and logistic service providers with a matching profile, able to fulfil the shippers demand. Vice versa all offers of "available" freight capacity will be forwarded to shippers. Since you are operating within this industry, we truly believe that your company will have a big opportunity in increasing efficiency, operational profit and expanding business via CargoFinder. Therefor we invite you to register with CargoFinder for the 30 day trial period as a "transport and logistic service provider" or for the FREE shippers account! With your registration are no obligations attached! Home page: http://www.CargoFinder.com More about: http://www.cargofinder.com/cf/more.asp Registration http://www.cargofinder.com/cf/register/default.asp?action=new We are looking forward to welcome you at CargoFinder. Best regards, CargoFinder Mr. Etienne G. M. R. Verhoef PO Box 70, 3740 AB Baarn, The Netherlands phone +31 35 548 0728/fax +31 35 548 0707 email [EMAIL PROTECTED] ------------------------------ From: [EMAIL PROTECTED] Date: Wed, 24 Mar 1999 11:30:51 -0500 (EST) Subject: [none] Hello I am running a linux HD release 5.0 (Hurricane) Kerner 2.0.32 on an i586. I want to know how to get the common dos prompt like C:\ or D:\ because I want to do some copying files and stuff like that. Pls let me know. Actually the linux HD is new for me, and I am kind of learning how to run it. It would be more helpful if you can provide me with the relevant websites. Thank you. ------------------------------ From: Stafford Goodsell <[EMAIL PROTECTED]> Date: Tue, 23 Mar 1999 18:39:33 +1130 Subject: Re: Auto start dosemu In message <[EMAIL PROTECTED]>, Gary Leung writes: >Is there a way that when the user login in to Linux, it goes directly to >dos emulator without the user manually type in "dos"? > >Please advise the relevant documents if available. Tks. > change their shell to dos i.e. in /etc/passwd put user:*:1000:1000:dos emulation:/var/dos:<path to dos> - -- Stafford Goodsell <[EMAIL PROTECTED]> _ C") Programmer, administrator of marys.oz, (_) avid gamer and all-round computer geek. -"- ------------------------------ From: Dale Worley <[EMAIL PROTECTED]> Date: Wed, 24 Mar 1999 13:14:00 -0500 Subject: Re: Auto start dosemu >Is there a way that when the user login in to Linux, it goes directly to >dos emulator without the user manually type in "dos"? change their shell to dos i.e. in /etc/passwd put user:*:1000:1000:dos emulation:/var/dos:<path to dos> It's probably a little easier to give them a .login script (as appropriate for their shell). Certainly, it's easier to debug. Dale ------------------------------ From: Rolandas Juodzbalis <[EMAIL PROTECTED]> Date: Wed, 24 Mar 1999 20:16:42 +0200 (EET) Subject: EPP under dosemu Hello, I'm trying to get work paralel port in EPP mode under dosemu. In dosemu.conf I included this: $_irqpassing = "7" $_printer = "lp" $_ports = "0x378 0x379 0x37a 0x37b 0x37c 0x37d 0x37e 0x37f 0x778 0x779 0x77a 0x77b 0x77c 0x77d 0x77e 0x77f" and with these 3 strings, i think EPP mode can work under emu. thats true or no? Rolandas Juodzbalis +370-7-311270 [EMAIL PROTECTED] +370-85-27747 ------------------------------ From: Ralph Alvy <[EMAIL PROTECTED]> Date: Wed, 24 Mar 1999 17:56:44 -0500 Subject: 0.98.6 boot dir feature I just noticed the bootdir feature in dosemu 0.98.6. Apparently it's been there since the first release of 0.98, but I never noticed it. Well, when I do what I'm told and copy all my relevant DOS files to my /var/lib/dosemu/bootdir directory, and then set my boot pointer as $_hdimage = "bootdir" I get the following error message when attempting to boot dosemu this way: ERROR: can't open /var/lib/dosemu/bootdir: #21 - Is a directory Well, I know it's a directory. It's supposed to be a directory. What am I missing? I really like the idea behind this feature. You supposedly no longer have to create a hdimage. Just dump what you want in that directory and execute dos or xdos from a terminal. I'd like to get that to work. Ralph Alvy [EMAIL PROTECTED] ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 02:58:44 +0100 (MET) Subject: Re: 0.98.6 boot dir feature On Wed, 24 Mar 1999, Ralph Alvy wrote: > I just noticed the bootdir feature in dosemu 0.98.6. Apparently it's been > there since the first release of 0.98, No, it was introduced and tested in 0.99 and now backported to the stable release. > $_hdimage = "bootdir" > > I get the following error message when attempting to boot dosemu this way: > > ERROR: can't open /var/lib/dosemu/bootdir: > #21 - Is a directory Well, then you forgot to upgrade your global.conf in /var/lib/dosemu/ 'make install' doesn't touch your global.conf in case it does already exist. If your have a default one, just copy it from ./etc. Hans <[EMAIL PROTECTED]> ------------------------------ From: Ralph Alvy <[EMAIL PROTECTED]> Date: Wed, 24 Mar 1999 21:36:09 -0500 Subject: 0.98.6 boot dir feature >> Well, then you forgot to upgrade your global.conf in /var/lib/dosemu/ >> 'make install' doesn't touch your global.conf in case it does already >> exist. If your have a default one, just copy it from ./etc. Thanks, Hans. I did this after reading your message. What I now get is a message telling me it can't load the operating system if I have MS-DOS system files there. If I have Caldera DR-DOS system files there, it tells me there isn't any operating system there. Ralph Alvy [EMAIL PROTECTED] ------------------------------ From: Ralph Alvy <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 00:46:27 -0500 Subject: 0.98.6 boot dir feature Hans, More ... I now have bootdir working with MS-DOS system files. But I notice that I can't redirect drives the way I used to be able to. Here's my autoexec.bat (the one I've always been using): lredir x: linux\fs/mnt/dos/c lredir d: linux\fs/mnt/dos/d lredir e: linux\fs/mnt/dos/e lredir f: linux\fs/mnt/dos/f lredir g: linux\fs/mnt/dos/g lredir h: linux\fs/mnt/dos/h lredir v: linux\fs/mnt/card lredir w: linux\fs/mnt/cdrom lredir z: linux\fs/mnt/zip path=<various paths> And here's my config.sys (same as always): device=ems.sys dos=high,umb files=80 buffers=20 lastdrive=z Note in the following that autoexec.bat fails to redirect drives d, e, and f. Note also that it redirects drive c out of order: C:\>lredir x: linux\fs/mnt/dos/c lredir d: linux\fs/mnt/dos/d <- drive d not redirected lredir e: linux\fs/mnt/dos/e <- drive e not redirected lredir f: linux\fs/mnt/dos/f <- drive f not redirected X: = LINUX\FS/MNT/DOS/C attrib = READ/WRITE <- drive c redirected out of order C:\>lredir g: linux\fs/mnt/dos/g G: = LINUX\FS/MNT/DOS/G attrib = READ/WRITE C:\>lredir h: linux\fs/mnt/dos/h H: = LINUX\FS/MNT/DOS/H attrib = READ/WRITE C:\>lredir v: linux\fs/mnt/card V: = LINUX\FS/MNT/CARD attrib = READ/WRITE C:\>lredir w: linux\fs/mnt/cdrom W: = LINUX\FS/MNT/CDROM attrib = READ/WRITE C:\>lredir z: linux\fs/mnt/zip Z: = LINUX\FS/MNT/ZIP attrib = READ/WRITE C:\>path=<various paths> ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 09:46:01 +0100 (MET) Subject: Re: 0.98.6 boot dir feature On Wed, 24 Mar 1999, Ralph Alvy wrote: > >> Well, then you forgot to upgrade your global.conf in /var/lib/dosemu/ > >> 'make install' doesn't touch your global.conf in case it does already > >> exist. If your have a default one, just copy it from ./etc. > > Thanks, Hans. I did this after reading your message. What I now get is a > message telling me it can't load the operating system if I have MS-DOS system > files there. If I have Caldera DR-DOS system files there, it tells me there > isn't any operating system there. You may need to put the bootsector in a file called boot.blk into the bootdir. If you use ./setup-bootdir to generate bootdir.first it would do that. Hans <[EMAIL PROTECTED]> ------------------------------ From: Hans Lermen <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 09:51:44 +0100 (MET) Subject: Re: 0.98.6 boot dir feature On Thu, 25 Mar 1999, Ralph Alvy wrote: > C:\>lredir x: linux\fs/mnt/dos/c > lredir d: linux\fs/mnt/dos/d <- drive d not redirected > lredir e: linux\fs/mnt/dos/e <- drive e not redirected > lredir f: linux\fs/mnt/dos/f <- drive f not redirected > X: = LINUX\FS/MNT/DOS/C attrib = READ/WRITE <- drive c redirected > out of order what error codes are reported for d:, e:, f: Hans <[EMAIL PROTECTED]> ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 13:27:29 -0500 (EST) Subject: Re: your mail Hi, maybe I can help you with getting to know how to use dosemu. What is it that you're trying to do? On Wed, 24 Mar 1999 [EMAIL PROTECTED] wrote: > Hello > > I am running a linux HD release 5.0 (Hurricane) Kerner 2.0.32 on an i586. > I want to know how to get the common dos prompt like C:\ or D:\ because I > want to do some copying files and stuff like that. Pls let me know. > Actually the linux HD is new for me, and I am kind of learning how to run > it. It would be more helpful if you can provide me with the relevant > websites. Thank you. > ------------------------------ From: [EMAIL PROTECTED] Date: Thu, 25 Mar 1999 13:32:48 -0500 (EST) Subject: Re: your mail Hello! I have already typed in dosemu, but if I am not mistaken, the error msg was "cannot execute display" or something like that. basically i can't do anything much as i could not login as the root. i bought the computer from a guy (whom i have lost contact with), and as long as i can't login and enter his password, i will keep getting error msgs like "access-denied" etc etc. if you can help me, just tell how to get a common c:\ prompt or how to change the drive to D:\ because i need to copy something from my CD drive. thank you. On Thu, 25 Mar 1999, UNIXMAN wrote: > Hi, maybe I can help you with getting to know how to use dosemu. What is > it that you're trying to do? > > > On Wed, 24 Mar 1999 [EMAIL PROTECTED] wrote: > > > Hello > > > > I am running a linux HD release 5.0 (Hurricane) Kerner 2.0.32 on an i586. > > I want to know how to get the common dos prompt like C:\ or D:\ because I > > want to do some copying files and stuff like that. Pls let me know. > > Actually the linux HD is new for me, and I am kind of learning how to run > > it. It would be more helpful if you can provide me with the relevant > > websites. Thank you. > > > ------------------------------ From: UNIXMAN <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 13:49:04 -0500 (EST) Subject: Re: your mail sure, if you need to copy something from the CDROM then can you do that with linux? all you have to do is mount the drive first, I can explain that if you want. You really should get the password for root, regardless of what you need to do. If you can't ask the guy then you'll need to boot into single user mode from a boot disk. The message "cannot open display" is what you get when you try to run an X-windows program from the command line, I don't know why dosemu would report this; how do you start dosemu? did you type "dos". hope this helps... On Thu, 25 Mar 1999 [EMAIL PROTECTED] wrote: > Hello! > > I have already typed in dosemu, but if I am not mistaken, the error msg > was "cannot execute display" or something like that. basically i can't do > anything much as i could not login as the root. i bought the computer > from a guy (whom i have lost contact with), and as long as i can't login > and enter his password, i will keep getting error msgs like > "access-denied" etc etc. if you can help me, just tell how to get a > common c:\ prompt or how to change the drive to D:\ because i need to > copy something from my CD drive. thank you. > > On Thu, 25 Mar 1999, UNIXMAN wrote: > > > Hi, maybe I can help you with getting to know how to use dosemu. What is > > it that you're trying to do? > > > > > > On Wed, 24 Mar 1999 [EMAIL PROTECTED] wrote: > > > > > Hello > > > > > > I am running a linux HD release 5.0 (Hurricane) Kerner 2.0.32 on an i586. > > > I want to know how to get the common dos prompt like C:\ or D:\ because I > > > want to do some copying files and stuff like that. Pls let me know. > > > Actually the linux HD is new for me, and I am kind of learning how to run > > > it. It would be more helpful if you can provide me with the relevant > > > websites. Thank you. > > > > > > ------------------------------ From: [EMAIL PROTECTED] Date: Thu, 25 Mar 1999 13:54:44 -0500 (EST) Subject: Re: your mail On Thu, 25 Mar 1999, UNIXMAN wrote: > sure, if you need to copy something from the CDROM then can you do that > with linux? all you have to do is mount the drive first, I can explain > that if you want. You really should get the password for root, > regardless of what you need to do. If you can't ask the guy then > you'll need to boot into single user mode from a boot disk. The message That's my point, I inserted the linux HD as the boot disk. I don't have a floppy drive, (otherwise I would have inserted a normal DOS floppy and I am all set). What is the single user mode? > "cannot open display" is what you get when you try to run an X-windows > program from the command line, I don't know why dosemu would report this; > how do you start dosemu? did you type "dos". > Yeah, I guess the cannot open display error was when I typed in X-windows/xterm etc etc. Now I rememeber, if I type dosemu or dos, it just gives basically the same prompt like before. None of the like usual DOS that i am used to. Anything else that you would like to help is more than appreciated! ------------------------------ From: Dale Worley <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 14:35:54 -0500 Subject: Cursor not appearing I used to have a laptop, and when I started Dosemu with "dos -c -k", the cursor would not show. I assumed that this was because the laptop had some strange video chip in it. But now I am using a much more conventional desktop system, and a version of Dosemu that is two or three years newer (0.66.7, which comes with Red Hat 5.1), and I still see the same problem. Does anyone know what is going on with this? Dale ------------------------------ From: Matt Clay <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 19:12:58 -0800 Subject: Emulating COM Ports I'm trying to emulate a COM port in DOSEmu using psuedo-tty's. I have a program open "/dev/ptyp9" for reading/writing, and have DOSEmu open COM1 as "/dev/ttyp9". Then I can do things like "copy autoexec.bat COM1" and I get the output on "/dev/ptyp9". However, when I try to run a program expecting an active modem connection on COM1, it sends a few characters to COM1 and then "hangs-up" (exits to DOS). Are there some settings I need to use to make sure that the psuedo-tty looks like an active modem connection on COM1? - -- - Matt Clay - Application Programmer - http://www.cowboyz.com/ ------------------------------ From: "Derric L. Tubbs" <[EMAIL PROTECTED]> Date: Thu, 25 Mar 1999 21:46:43 -0600 (CST) Subject: serial problem I am trying to backup my Sharp YO-370 electronic organizer via a DOS program (OL-390) under DOSEmu. I've booted into DOS alone and it worked fine but under DOSEmu the program just hangs whenever I try the actual transfer and I have to kill DOSEmu. The OL-390 program _runs_ just fine under DOSEmu, it just hangs whenever it tries to talk to the COM ports. I downloaded dostest.exe (mentioned in the README-tech.txt) and it says that both COM1 and COM2 are present. The folling lines are in my /etc/dosemu.conf for serial lines: serial { com 1 base 0x03F8 irq 4 device /dev/ttyS0 } serial { com 2 base 0x02F8 irq 3 device /dev/ttyS1 } I've also tried using cua1 with the same result. Any help would be greatly appreciated. Derric Tubbs [EMAIL PROTECTED] ------------------------------ From: "Bjoern.Kahl" <[EMAIL PROTECTED]> Date: Fri, 26 Mar 1999 11:25:21 +0100 (CET) Subject: reproduceable crash in dosemu0.98 (DPMI-code/internal mouse) This message is in MIME format - --_=XFMail.1.3.p0.Linux:990326112305:5004=_ Content-Type: text/plain; charset=us-ascii Hallo ! I have found a reproduceable bug in dosemu-0.98-4, while trying to run cadsoft's free available PCB-Layout Editor "Eagle". TOC: - Description - Why I thing its dosemus fault - How to reproduce - My configuration - Files for reproduction In the following "mouse" refer to a serial mouse. Description: Dosemu-98 can succsessfully run eagle in console-graphics mode and (as long as you do not touch the mouse) in a x-window. In consolemode eagle run stable if dosemus internal mousedriver is disabled, and a dos-mousedriver is loaded or no mouse used at all. If dosemus internal mousedriver is enabled, but the mouse doesn't move, all eagle-funktions available via keyboard (virtualy all) work stable. As soon as the mouse moves, dosemu crashs, emitting a lot of errormessages, saying a DPMI-Error (exact messages in attachment #1 "dosemu.out"). Why I think it is dosemus fault: I think its dosemus fault, because everything works well, if I use a native dos mousedriver (in this case a "noname" driver supporting Mousesystem and Microsoft mouse) and not the dosemu-internal-driver. How to reproduce: - Get the two needed files from cadsofts www-page (s. "Files"). They are freely available, there is no registration or anything else, to my best knowledge. You need about 13 MB of diskspace, every thing went in one single directory. - Run the self-extracting archive "edp355r1.exe". - Make sure you do not use dosemus internal mousedriver or turn your mouse on its back, so you can't accidently generate mouse-move-events - run eagle, type in the installcode found in "license.key" - try some keyboard commands (like (F)ile->(N)ew etc.) everything shoud work. - exit from eagle ((F)ile->E(x)it) - make sure dosemus internal mousedriver in disabled and start an dos-based mousedriver - again play with eagle, everything shoud work - exit eagle - make sure, dosemus internal mousedriver is enabled, and you do not move your mouse by accident. - again, play with eagle, everything works well - move your mouse dosemu crashes. This is true for console-mode as well as xdos, expect that I don't know a way running xdos with an dos-native-mousedriver, since x needs the mouse too. My configuration: - CPU: AMD 486 @ 66 Mhz - RAM: 32 MB - Mainboard: Intel, Chipset ??? - Graphic: Trident tgui9440 - Sound: - - Linux: Suse 5.3 (Kernel: 2.0.35) - DOSEMU: dosemu-0.98.4-1.rpm from dosemu.org - dosemu.conf: Attachment #2 "dosemu.conf" Files: Installation-instruction and general Info (english) <http://www.cadsoft.de/freeware.htm> To run eagle you need two freely available file: <ftp://212.6.150.2/pub/program/edp355r1.exe> (3,242,675 Bytes) <ftp://212.6.150.2/pub/program/license.key> (2,708 Bytes) Bjoern P.S.: I tried hard, to write "readable" english, please ignore any mistakes. For private mail, feel free to use english or german. - -- +-------------------------------------------------------------+ | Bj�rn Kahl +++ <[EMAIL PROTECTED]> | | Raum : II 204 +++ Tel. +49 431 880 3934 | | Institut f�r Experimentelle und Angewandte Physik, Uni Kiel | +-------------------------------------------------------------+ - --_=XFMail.1.3.p0.Linux:990326112305:5004=_ Content-Disposition: attachment; filename="dosemu.out" Content-Transfer-Encoding: 7bit Content-Description: dosemu.out Content-Type: text/plain; charset=us-ascii; name=dosemu.out; SizeOnDisk=1802 robo-mam:/root # xdos -C Running on CPU=486, FPU=1, rdtsc=0 ERROR: DPMI: DPMI_pm_procedure_running = 0x0010 ERROR: DPMI: DPMI_pm_procedure_running = 0x0011 ERROR: DPMI: DPMI_pm_procedure_running = 0x0012 ERROR: DPMI: DPMI_pm_procedure_running = 0x0013 ERROR: DPMI: DPMI_pm_procedure_running = 0x0014 ERROR: DPMI: DPMI_pm_procedure_running = 0x0015 ERROR: DPMI: DPMI_pm_procedure_running = 0x0016 ERROR: DPMI: DPMI_pm_procedure_running = 0x0017 ERROR: DPMI: DPMI_pm_procedure_running = 0x0018 ERROR: DPMI: DPMI_pm_procedure_running = 0x0019 ERROR: DPMI: DPMI_pm_procedure_running = 0x001a ERROR: DPMI: DPMI_pm_procedure_running = 0x001b ERROR: DPMI: DPMI_pm_procedure_running = 0x001c ERROR: DPMI: DPMI_pm_procedure_running = 0x001d ERROR: DPMI: DPMI_pm_procedure_running = 0x001e ERROR: DPMI: DPMI_pm_procedure_running = 0x001f ERROR: DPMI: DPMI_pm_procedure_running = 0x0020 ERROR: DPMI: DPMI_pm_procedure_running = 0x0021 ERROR: DPMI: DPMI_pm_procedure_running = 0x0022 ERROR: DPMI: DPMI_pm_procedure_running = 0x0023 ERROR: DPMI: DPMI_pm_procedure_running = 0x0024 ERROR: DPMI: DPMI_pm_procedure_running = 0x0025 [ ... every number in increasing order ] ERROR: DPMI: DPMI_pm_procedure_running = 0x014f ERROR: DPMI: DPMI_pm_procedure_running = 0x0150 ERROR: DPMI: DPMI_pm_procedure_running = 0x0151 ERROR: DPMI: DPMI_pm_procedure_running = 0x0152 ERROR: DPMI: DPMI_pm_procedure_running = 0x0153 ERROR: DPMI: DPMI_pm_procedure_running = 0x0154 ERROR: DPMI: DPMI_pm_procedure_running = 0x0155 ERROR: cpu exception in dosemu code outside of VM86()! trapno: 0x0d errorcode: 0x00000000 cr2: 0x000a4000 eip: 0x08079ed4 esp: 0xbffff8a8 eflags: 0x00010282 cs: 0x0023 ds: 0x002b es: 0x002b ss: 0x002b General protection exception GDT selector: 0x0000 Exception was caused by DOSEMU robo-mam:/root # - --_=XFMail.1.3.p0.Linux:990326112305:5004=_ Content-Disposition: attachment; filename="dosemu.conf" Content-Transfer-Encoding: 7bit Content-Description: dosemu.conf Content-Type: text/plain; charset=us-ascii; name=dosemu.conf; SizeOnDisk=1719 $_debug = "+a+chM" $_features = "" $_timint = (on) $_mathco = (on) $_cpu = (80486) $_rdtsc = (on) $_cpuspeed = (0) $_pci = (off) $_xms = (4096) $_ems = (4096) $_ems_frame = (0xe000) $_dpmi = (8192) $_dosmem = (640) $_hardware_ram = "" $_secure = "ngd" $_odd_hosts = "" $_diskless_hosts = "" $_emusys = "" $_emubat = "" $_emuini = "" $_hogthreshold = (0) $_irqpassing = "" $_speaker = "native" $_term_char_set = "latin1" $_term_color = (on) $_term_updfreq = (4) $_escchar = (30) $_rawkeyboard = (on) $_layout = "de-latin1" $_keybint = (on) $_X_updfreq = (5) $_X_title = "DOS in a BOX" $_X_icon_name = "xdos" $_X_keycode = (on) $_X_blinkrate = (32) $_X_font = "" $_X_mitshm = (on) $_X_sharecmap = (off) $_X_fixed_aspect = (on) $_X_aspect_43 = (on) $_X_lin_filt = (off) $_X_bilin_filt = (off) $_X_mode13fact = (2) $_X_winsize = "" $_X_gamma = (1.0) $_X_vgaemu_memsize = (1024) $_X_lfb = (on) $_X_pm_interface = (on) $_X_mgrab_key = "" $_X_vesamode = "" $_video = "vga" $_console = (on) $_graphics = (on) $_videoportaccess = (on) $_vbios_seg = (0xc000) $_vbios_size = (0x10000) $_vmemsize = (1024) $_chipset = "trident" $_dualmon = (off) $_vbootfloppy = "" $_floppy_a = "threeinch" $_floppy_b = "" #$_hdimage = "hdimage.first /dev/hda4" $_hdimage = "/dev/hda4 hdimage.first" $_hdimage_r = $_hdimage $_aspi = "" $_com1 = "/dev/cua0" #$_com1 = "/dev/ttyef" $_com2 = "" $_com3 = "" $_com4 = "" $_ttylocks = "" $_mouse = "" $_mouse_dev = "" $_mouse_flags = "" $_mouse_baud = (0) $_printer = "lp" $_printer_timeout = (20) $_ports = "" $_ipxsupport = (off) $_novell_hack = (off) $_vnet = (off) $_sound = (off) $_sb_base = (0x220) $_sb_irq = (5) $_sb_dma = (1) $_sb_dsp = "/dev/dsp" $_sb_mixer = "/dev/mixer" $_mpu_base = "0x330" - --_=XFMail.1.3.p0.Linux:990326112305:5004=_-- End of MIME message ------------------------------ From: Curt Daugaard <[EMAIL PROTECTED]> Date: Fri, 26 Mar 1999 05:58:37 -0600 Subject: Test--haven't been able to post to this list Sorry for this test but two attempts to post a dosemu question to this list have failed. The first, I was told, was rejected by the list's spam filter. Curt Daugaard [EMAIL PROTECTED] ------------------------------ From: Ralph Alvy <[EMAIL PROTECTED]> Date: Sat, 27 Mar 1999 14:40:05 -0500 Subject: DOS com port speed I have dosemu 0.98.6 installed. How do I get my com port to open higher than 38400? That always seems to be the maximum it allows. Ralph Alvy [EMAIL PROTECTED] ------------------------------ From: Ralph Alvy <[EMAIL PROTECTED]> Date: Sat, 27 Mar 1999 14:44:31 -0500 Subject: DOS com port speed Never mind about that. I see my software was opening the port at 38400. I accidentally reset that somehow. Ralph Alvy [EMAIL PROTECTED] ------------------------------ From: Radek Bochenek <[EMAIL PROTECTED]> Date: Sun, 28 Mar 1999 13:39:48 +0200 (CEST) Subject: Floppy Hi, I have problem with floppy under DOSEMU. I tryed many configuration directives and my floppy still have problems under DOSEMU. When I try to boot it (dos -A) it hangs... When I make hdimage from floppy it boots from the image and in DOS prompt I type 'a:' it reads floppy drive for about 2-3 seconds and it hang just like 'dos -A' :( So I cannot boot MS-DOS 6.22 setup disk to install it :((( If anybody can help me, I'll be very thanksful PS. I tryed it on version 0.98.6 and 0.99.10. ________________________ Radek Bochenek e-mail : [EMAIL PROTECTED] http://linux.blah.pl/rad - -- "We all will depart and decay" ------------------------------ From: "Robert W. March" <[EMAIL PROTECTED]> Date: Sun, 28 Mar 1999 12:29:03 -0500 Subject: Re: serial comm with OL-390 "Derric L. Tubbs" wrote: > I am trying to backup my Sharp YO-370 electronic organizer via a DOS > program (OL-390) under DOSEmu. I've booted into DOS alone and it worked > fine but under DOSEmu the program just hangs whenever I try the actual Derric, I too have had this experience attempting to use this program. If you are offered a solution from outside the list, I would appreciate hearing what it is. - -Robert - -- ____________________________________________________________ Robert W. March St. Andrew's House L'Orignal ON Canada ------------------------------ From: "Calvin Loong" <[EMAIL PROTECTED]> Date: Mon, 29 Mar 1999 15:39:05 +0800 Subject: About DOS emulators This is a multi-part message in MIME format. - ------=_NextPart_000_0005_01BE79FA.472451A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I had problem using the emulators The error said that something about "the parse file wrong in line 285" I hope u can help me out of here since i cannot use my favourites msdos = program And can u tell me how to activate windows 95 program under x windows. Thanks.... - ------=_NextPart_000_0005_01BE79FA.472451A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#000000 size=3D2>I had problem using the = emulators</FONT></DIV> <DIV><FONT size=3D2>The error said that something about "the parse = file wrong=20 in line 285"</FONT></DIV> <DIV><FONT size=3D2>I hope u can help me out of here since i cannot use = my=20 favourites msdos program</FONT></DIV> <DIV><FONT size=3D2>And can u tell me how to activate windows 95 program = under x=20 windows.</FONT></DIV> <DIV><FONT size=3D2>Thanks....</FONT></DIV></BODY></HTML> - ------=_NextPart_000_0005_01BE79FA.472451A0-- ------------------------------ From: christian ruediger bahls <[EMAIL PROTECTED]> Date: Mon, 29 Mar 1999 10:47:18 +0200 Subject: yor website is damaged .. i don't know if it's your responsibilaty but : http://www.dosemu.org/stable/announce-0.98.html << i get the page but mi mozilla 4.05 is not showing it ! perhaps something with false statements or so ?? >>> i think it is this ... <td><BR></> <HR><H3>Transfer interrupted!</H3> > </TR> <TR> </TR> <TR> <TD BGCOLOR="#f0f0FF" valign="top"> <SCRIPT language="JavaScript"> <!-- // Re-write this to dynamically determine the height to use -AM document.writeln ('<IMG SRC="../images/empty.gif" ' +'WIDTH="1" HEIGHT="' + 400 +'" ALIGN="LEFT" alt="">'); // end script --> </SCRIPT> <<< 1.) what is </> ?? i dont know this ! 2.) why a <HR><H3>Transfer interrupted!</H3> in your document ?? 3.) > not opened !! 4.) i think a script should be in a comment ... BTW the way you are commenting multiple lines is wrong ! <!-- //--> is right !! look in a HTML reference /www.w3c.org bye bye ICQ :)) ------------------------------ From: "Estuardo Morales" <[EMAIL PROTECTED]> Date: Mon, 29 Mar 1999 16:46:45 PST Subject: =?ISO-8859-1?Q?can=B4t?= get Lredir to work with freedos Hi... i�m a newbee with this thing of linux but i have to get working dosemu with freedos for a project from my company.... i would love if you can tell me why im getting errors like Error f0bc redirecting drive X: to LINUX/FS/directory i have tried with emufs.sys and none of this has worked.... tellme what im doing wrong or if i have to download some patches or something. i hope you can answer soon best regards. from Guatemala Estuardo. Get Your Private, Free Email at http://www.hotmail.com ------------------------------ From: [EMAIL PROTECTED] (Kragen Sitaker) Date: Mon, 29 Mar 1999 22:29:25 -0500 (EST) Subject: Re: can't get Lredir to work with freedos > dosemu with freedos for a project from my company.... > i would love if you can tell me why im getting errors like > Error f0bc redirecting drive X: to LINUX/FS/directory Lredir doesn't work with FreeDOS. Never has. I don't know much about DOS, but I think there's some kind of software support needed in FreeDOS (networking?) to get it to work. Lredir works with DR DOS, which is proprietary but available gratis (I think). - -- <[EMAIL PROTECTED]> Kragen Sitaker <http://www.pobox.com/~kragen/> We are forming cells within a global brain and we are excited that we might start to think collectively. What becomes of us still hangs crucially on how we think individually. -- Tim Berners-Lee, inventor of the Web ------------------------------ From: Sergey Suleimanov <[EMAIL PROTECTED]> Date: 30 Mar 1999 15:36:08 +0400 Subject: errorlevel How can I return errorlevel from dosemu? "exitemu 1" not working. - -- Sergey Suleimanov ------------------------------ From: "Tomasz Kazmierski" <[EMAIL PROTECTED]> Date: Wed, 31 Mar 1999 17:06:21 +0200 (EEST) Subject: Something special - -----BEGIN PGP SIGNED MESSAGE----- Hello ! My problem is a little bit unusual. I've got some software, which works only with special key connected to my PC's parrel port. So, when I run this software under Dosemu it says, that there isn't any. How to make this key visiable for my programs ? Thanks for help Regards... T. - -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQCVAwUBNwI58Nv6IZgpWABdAQGx8QP/QX++hVyJBCq23bs8QfuNVyjv4Cxc2frp HTGRqWs6h9kkz5x+ZeVP4E5ZMcVC+HAjXVRYEt5rr1qO0vsuExzNap4+Ilj0MgLB ljv5wx/YOHSSfekDAbjOO5hpH6ycjc7odqATly+yLZ+IN2SWvdiJjuOePI13ICYW emJFgQD4gew= =Xf7Y - -----END PGP SIGNATURE----- ------------------------------ From: Michael ROGERS <[EMAIL PROTECTED]> Date: Wed, 31 Mar 1999 17:42:15 +0100 Subject: DOSemu problems I've just downloaded and installed DOSemu 0.98.6, and set it up to use my Win95 partition as the hard disk image. After a bit of CONFIG.SYS tweaking I got it to boot without error messages, but when I run an application (so far I've only tried EDIT.COM and a synth emulator called Audiosim), the keyboard stops working. When I exit the application I find whatever I typed has appeared at the command prompt instead. Can anyone help me? For reference my system is RedHat Linux 5.2 with 2.2.2 kernel on an AMD-K6-3D, and I was running DOSemu from the console. I tried enabling raw keyboard input, but it didn't work. I have enabled XMS and DPMI and disabled EMS. I'm using DOS version 7 (or whatever comes with Win95). All other obscure config information available on request ;) - Michael Rogers ------------------------------ From: Alistair MacDonald <[EMAIL PROTECTED]> Date: Wed, 31 Mar 1999 22:20:07 +0100 (BST) Subject: Re: yor website is damaged .. (Pasted from the archive - my subscription got cancelled by the list (again!) Christian ruediger bahls ([EMAIL PROTECTED]) wrote: > i don't know if it's your responsibilaty but : > http://www.dosemu.org/stable/announce-0.98.html > << i get the page > but mi mozilla 4.05 is not showing it ! Yes - YOUR netscape isn't showing it. > perhaps something with false statements or so ?? > >>> i think it is this ... > <td><BR></> > <HR><H3>Transfer interrupted!</H3> [...] > document.writeln ('<IMG SRC="../images/empty.gif" ' > +'WIDTH="1" HEIGHT="' + 400 +'" ALIGN="LEFT" alt="">'); > // end script --> > 1.) what is </> > ?? i dont know this ! Corruption in YOUR browser .... > 2.) why a <HR><H3>Transfer interrupted!</H3> in your document ?? ... caused by an INTERRUPTED TRANSFER. I should have thought that 'Transfer Interrupted' was FAIRLY obvious. You need to RELOAD the page. Depending upon your configuration you may also have to: 1) Clear your browser disk & memory cache 2) Disable your PROXY (if IT has the corrupted copy) > 3.) > not opened !! Once you get an INTERRUPTED TRANSFER nothing works correctly ... > 4.) i think a script should be in a comment ... > BTW the way you are commenting multiple lines is wrong ! > <!-- > > //--> > is right !! No - you are wrong.... > look in a HTML reference /www.w3c.org You should read more carefully - not just about HTML, but also JAVASCRIPT (aka ECMASCRIPT) AND browser compatability. 1) Javascript will ignore ANYTHING after the // 2) Some browsers FAIL to find '-->' if it not SEPARATED by white space from ANY preceeding content 3) There have been reports of browsers that FAIL to find '// -->' as well. Alistair ------------------------------ From: Ken Cobler <[EMAIL PROTECTED]> Date: Wed, 31 Mar 1999 19:06:15 -0600 Subject: help with icverify 6.60.17 Hello, I am trying to use DOSEMU 0.98 on Linux 2.0.36 (Redhat 5.2). The application I am trying to run is ICVerify 6.60.17 (DOS version). When I launch the program, the screen looks correct, however, it must do something different with the keyboard because no keystroke is accepted by the application (It won't process any key I press). The program does work on a Win '98 box. Luckily, I can switch to another virtual terminal (CTL-ALT-F2) on the console, log in as root, and kill the DOSEMU session without having to reboot the Linux computer. I have tried turning $_rawkeyboard = (1) and $_keybint = (on) in the /etc/dosemu.conf file with no change in behaviour. Any insight would be greatly appreciated. I am trying to determine if the ICVerify for DOS will work under DOSEMU. We need to use ICVerify here. We have the ICVerify DOS version. ICVerify does exist for SCO Unix and Solaris, but, not for Linux. We don't have the SCO or Solaris version, so, I don't know how well those ICVerify versions will run on Linux. Thanks for your help, Ken Cobler ([EMAIL PROTECTED] or [EMAIL PROTECTED]) ------------------------------ From: "Daniel VARGA (RBHU/DVA)" <[EMAIL PROTECTED]> Date: Thu, 01 Apr 1999 08:40:51 +0200 Subject: DOS terminal Server I have a Novell3.12 Server and a Btrieve application with DOS surface running on it. From my Linux box I can work with it via dosemu fine. I have 15 users, who want to work with it from _home_ as well. I need a terminal server, which picks up the phone (ev. calls them back) and gives each caller a DOS surface and also starts this application, so they do not even notice, that this is a Linux server. The caller would be of course win95 and NT users. Do you think this is possible? How? Daniel ------------------------------ From: Yasushi Shoji <[EMAIL PROTECTED]> Date: Fri, 02 Apr 1999 08:58:23 -0500 Subject: can't access /dev/fd0 - ----Next_Part(Fri_Apr__2_08:56:42_1999_893)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit hi all, i'm having trouble accessing /dev/fd0 on my linux 2.2.4-ac1 with glibc 2.1.1pre. i tried both latest stable version and devel version of dosemu, 0.98.6 and 0.99.10, compiled with egcs 1.1.2. i downloaded DR Dos 7.03 Lite from caldera.com. # BTW, how can i dd those ldisk0?.144 images? # on my linux box, it seems that image files # are too big. so i used win95 box to make disks. # i can boot a system with those disks just fine. placing disk 1 in FDD and start dos with -A just hungs, but using it's image, ldisk01.144 in this case, in $_vbootfloppy in /etc/dosemu.conf works just fine. i'll put debug info at the end of this mail $ dos -A -D+a-v -o debug.log another quesion is: how can i access to HDD image created with mkfatimage16. made a HDD image with mkfatimage16, which i can access with mtools(mdir). in /etc/dosemu.conf, i put: $_hdimage = "dos_c.img" where dos_c.img is the HDD image created with mkfatimage16. thank you for your time - -- yashi - ----Next_Part(Fri_Apr__2_08:56:42_1999_893)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=debug.log CONF: config variable parser_version_3 set CONF: config variable c_system set CONF: Parsing /var/lib/dosemu/global.conf file. CONF: config variable version_3_style_used set CONF: config variable version_3_style_used unset CONF: config variable version_3_style_used set CONF: opened include file /etc/dosemu.conf CONF: closed include file /etc/dosemu.conf debug flags: CONF: Enabling use of pentium timer CONF: dosbanner on CONF: timint on CONF: CPU set to 586 CONF: 1024k bytes XMS memory CONF: 1024k bytes EMS memory CONF: EMS-frame = 0xe000 CONF: dosemu running on _xterm SER: directory /var/lock namestub LCK.. binary No CONF: Keyboard-layout keyb-user CONF: Keyboard-layout us device: /dev/fd0 type 2 h: 0 s: 0 t: 0 floppy A: CONF: DPMI-Server off CONF: not allowing speaker port access CONF: IPX support off CONF(LPT0) f: (null) c: lpr o: -Plp %s t: 20 port: 378 device: /dev/sdb1 type 3 partition# 1 h: -1 s: -1 t: -1 drive C: device: /var/lib/dosemu/dos_c.img type 0 header_size: 128 h: -1 s: -1 t: -1 drive D: CONF: config variable c_system unset CONF: not enough privilege to define config variable c_user debug flags: +a-v debug flags: +dARWDCvkiTsm#pgcwhIExMnPrSg CONF: mostly running as USER: uid=1000 (cached 1000) gid=100 (cached 100) TIMER: using pentium timing DBG_FD already set DOSEMU-0.99.10.0 is coming up on Linux version 2.2.4-ac1 Built for 2002004 CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K)) CONF: reserving 64Kb at 0xF0000 for 'r' (Dosemu reserved area) DOS memory area being mapped in HMA: mapped id a0181 to (nil) HMA: mapped id a0181 to 0x100000 HMA: mapped id a0180 to 0x81e1000 Initialized all signals to NOT-BLOCK KBD: keyb_server_init() KBD: keyb_server_reset() KBD: initialising 'slang' mode keyboard client KBD: slang_keyb_init() S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31317e = 0004003b S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31327e = 0004003c S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31337e = 0004003d S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31347e = 0004003e S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31357e = 0004003f S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31377e = 00040040 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31387e = 00040041 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b31397e = 00040042 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32307e = 00040043 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32317e = 00040044 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32337e = 0005003b S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32347e = 0005003c S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32357e = 0005003d S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32367e = 0005003e S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32387e = 0005003f S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b32397e = 00050040 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b33317e = 00050041 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b33327e = 00050042 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b33337e = 00050043 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b33347e = 00050044 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b327e = 0004e052 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b48 = 0004e047 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b4f77 = 0004e04f S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b357e = 0004e049 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b367e = 0004e051 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b41 = 0004e048 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b42 = 0004e050 S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b43 = 0004e04d S-Lang Error: Inconsistency in define key. Conflicting key: 1b1b5b44 = 0004e04b KBD: Not using SIGIO GEN: fd=0 does not get SIGIO, use_sigio=8192 KBD: slang_keyb_init() ok KBD: Keyboard init ok, 'slang' mode CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory) PORT: registered "8254 Timer0" handle 0x06 [0x0040-0x0040] fd=-1 PORT: registered "8254 Timer1" handle 0x07 [0x0041-0x0041] fd=-1 PORT: registered "8254 Timer2" handle 0x08 [0x0042-0x0042] fd=-1 PORT: registered "8254 Ctrl02" handle 0x09 [0x0043-0x0043] fd=-1 PORT: registered "CMOS RAM" handle 0x0a [0x0070-0x0071] fd=-1 SERIAL $Header: /usr/src/dosemu0.60/serial/RCS/ser_init.c,v 1.1 1995/05/06 16:26:19 root Exp root $ SER: Running serial_init, 0 serial ports PORT: registered "8259 PIC0" handle 0x0b [0x0020-0x0021] fd=-1 PORT: registered "8259 PIC1" handle 0x0c [0x00a0-0x00a1] fd=-1 PORT: registered "8042 Keyboard data" handle 0x0d [0x0060-0x0060] fd=-1 PORT: registered "8042 Keyboard command" handle 0x0e [0x0064-0x0064] fd=-1 PORT: registered "Speaker port" handle 0x0f [0x0061-0x0061] fd=-1 PORT: registered "DMA - XT Controller" handle 0x10 [0x0000-0x000f] fd=-1 PORT: registered "DMA - XT Pages" handle 0x11 [0x0081-0x0087] fd=-1 PORT: registered "DMA - AT Controller" handle 0x12 [0x00c0-0x00de] fd=-1 PORT: registered "DMA - AT Pages" handle 0x13 [0x0089-0x008a] fd=-1 DMA: DMA Controller initialized - 8 & 16 bit modes SB: SB Initialisation SB:[Linux] SB Driver Initialisation Called SB:[Linux] No sounddevice for SoundBlaster emulation found. SB: No SB emulation available. Disabling SB SB: FM Initialisation PORT: registered "Adlib (+ Advanced) Emulation" handle 0x14 [0x0388-0x038b] fd=-1 SB:[Linux] FM Driver Initialisation Called MPU401: MPU-401 Initialisation PORT: registered "Midi Emulation" handle 0x15 [0x0330-0x0331] fd=-1 MPU401: MPU-401 Initialisation - Base 0x330 MPU:[Linux] MPU Driver Initialisation Called KBD: IOCTL fd=0x0, req=0x4b2f, param3=0x0 RTC: init time 08:19:16 CMOS initialized DMA: DMA Controller Reset - 8 & 16 bit modes SB: Resetting SB SB: Resetting FM SB:[Linux] FM Driver Reset Called MPU401: Resetting MPU-401 MPU:[Linux] MPU Driver Reset Called MOUSE: No mouse configured in serial config! num_ser=0 MOUSE: reset mouse/installed! MOUSE: video mode 0x03 found (T80x24 at 0xb8000). maxx=639, maxy=191 speed_x=0 speed_y=0 ignorexy=0 type=0 LPT: initializing printer (null) LPT: initializing printer (null) LPT: initializing printer (null) ISBLK dev /dev/fd0: 0x200 DISK /dev/fd0 removeable HDISK auto_info disk /dev/sdb1; h=64, s=32, t=1021, start=32 PARTITION SETUP for /dev/sdb1 Using MBR from /dev/sdb for PARTITION /dev/sdb1 (part#=1). beg head 1, sec 1, cyl 0 = end head 63, sec 32, cyl 1020 pre_secs 32, num_secs 2090976 = 1fe7e0, -dp->header 16384 = 0x4000 DESTROYING any traces of partition 2 DESTROYING any traces of partition 3 DESTROYING any traces of partition 4 IMAGE: Using user permissions IMAGE auto-sensing IMAGE auto_info disk /var/lib/dosemu/dos_c.img; h=4, s=17, t=31, off=128 NULLF for /var/lib/dosemu/dos_c.img INT21: rv_all: 1 + 0 = 1 PORT: registered "PCI Config" handle 0x16 [0x0cf8-0x0cff] fd=-1 PIC,mouse,IPX initialized CONFIG: 0x4023 binary: 0100 0000 0010 0011 EMS: coming up on release 2.2.4-ac1 EMS: using /proc/self/mem mmaping (yeah!!!) EMS: opening /proc/self/mem EMS: initializing memory CONF: reserving 64Kb at 0xE0000 for 'E' (EMS page frame) XMS: initializing XMS... 64 handles XMS: New UMB region: 0xc0000 XMS: umb_setup: addr 0xc0000 size 0x20000 SHM: shm_qf_id=a0182 SHM: shm_video_id=a0183 SHM: Client request area set to 0000 FLOPPY /dev/fd0 h=2, s=18, t=80 DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/0/0+0 at pos 0 DISK: /dev/fd0: Closing a disk Atleast 1 NON-SIGIO file handle in use. EMULATE GEN: fd=8 does not get SIGIO, use_sigio=8192 TIME: using 9154 usec for updating ALRM timer int 0x1c, ax=0x0000 DEFIVEC: int 0x1c @ 0xf000:0x01c0 Return from vm86() for STI DISK init 0 FLOPPY /dev/fd0 h=2, s=18, t=80 DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/1/1+0 at pos 9728 DISK read @1/0/1 (1) -> 0x8000 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/2/1+0 at pos 10240 DISK read @1/0/2 (1) -> 0x8200 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/3/1+0 at pos 10752 DISK read @1/0/3 (1) -> 0x8400 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/4/1+0 at pos 11264 DISK read @1/0/4 (1) -> 0x8600 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/5/1+0 at pos 11776 DISK read @1/0/5 (1) -> 0x8800 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/6/1+0 at pos 12288 DISK read @1/0/6 (1) -> 0x8a00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/7/1+0 at pos 12800 DISK read @1/0/7 (1) -> 0x8c00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/8/1+0 at pos 13312 DISK read @1/0/8 (1) -> 0x8e00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/9/1+0 at pos 13824 DISK read @1/0/9 (1) -> 0x9000 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/10/1+0 at pos 14336 DISK read @1/0/10 (1) -> 0x9200 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/11/1+0 at pos 14848 DISK read @1/0/11 (1) -> 0x9400 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/12/1+0 at pos 15360 DISK read @1/0/12 (1) -> 0x9600 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/13/1+0 at pos 15872 DISK read @1/0/13 (1) -> 0x9800 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/14/1+0 at pos 16384 DISK read @1/0/14 (1) -> 0x9a00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/10/0+0 at pos 5120 DISK read @0/0/10 (1) -> 0x8000 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/11/0+0 at pos 5632 DISK read @0/0/11 (1) -> 0x8200 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/12/0+0 at pos 6144 DISK read @0/0/12 (1) -> 0x8400 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/13/0+0 at pos 6656 DISK read @0/0/13 (1) -> 0x8600 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/14/0+0 at pos 7168 DISK read @0/0/14 (1) -> 0x8800 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/15/0+0 at pos 7680 DISK read @0/0/15 (1) -> 0x8a00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/16/0+0 at pos 8192 DISK read @0/0/16 (1) -> 0x8c00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/17/0+0 at pos 8704 DISK read @0/0/17 (1) -> 0x8e00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 0/0/1+0 at pos 9216 DISK read @1/0/0 (1) -> 0x9000 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/9/0+0 at pos 152064 DISK read @0/8/9 (1) -> 0x700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/10/0+0 at pos 152576 DISK read @0/8/10 (1) -> 0x900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/11/0+0 at pos 153088 DISK read @0/8/11 (1) -> 0xb00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/12/0+0 at pos 153600 DISK read @0/8/12 (1) -> 0xd00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/13/0+0 at pos 154112 DISK read @0/8/13 (1) -> 0xf00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/14/0+0 at pos 154624 DISK read @0/8/14 (1) -> 0x1100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/15/0+0 at pos 155136 DISK read @0/8/15 (1) -> 0x1300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/16/0+0 at pos 155648 DISK read @0/8/16 (1) -> 0x1500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/17/0+0 at pos 156160 DISK read @0/8/17 (1) -> 0x1700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/0/1+0 at pos 156672 DISK read @1/8/0 (1) -> 0x1900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/1/1+0 at pos 157184 DISK read @1/8/1 (1) -> 0x1b00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/2/1+0 at pos 157696 DISK read @1/8/2 (1) -> 0x1d00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/3/1+0 at pos 158208 DISK read @1/8/3 (1) -> 0x1f00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/4/1+0 at pos 158720 DISK read @1/8/4 (1) -> 0x2100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/5/1+0 at pos 159232 DISK read @1/8/5 (1) -> 0x2300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/6/1+0 at pos 159744 DISK read @1/8/6 (1) -> 0x2500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/7/1+0 at pos 160256 DISK read @1/8/7 (1) -> 0x2700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/8/1+0 at pos 160768 DISK read @1/8/8 (1) -> 0x2900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/9/1+0 at pos 161280 DISK read @1/8/9 (1) -> 0x2b00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/10/1+0 at pos 161792 DISK read @1/8/10 (1) -> 0x2d00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/11/1+0 at pos 162304 DISK read @1/8/11 (1) -> 0x2f00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/12/1+0 at pos 162816 DISK read @1/8/12 (1) -> 0x3100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/13/1+0 at pos 163328 DISK read @1/8/13 (1) -> 0x3300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/14/1+0 at pos 163840 DISK read @1/8/14 (1) -> 0x3500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/15/1+0 at pos 164352 DISK read @1/8/15 (1) -> 0x3700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/16/1+0 at pos 164864 DISK read @1/8/16 (1) -> 0x3900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 8/17/1+0 at pos 165376 DISK read @1/8/17 (1) -> 0x3b00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/0/0+0 at pos 165888 DISK read @0/9/0 (1) -> 0x3d00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/1/0+0 at pos 166400 DISK read @0/9/1 (1) -> 0x3f00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/2/0+0 at pos 166912 DISK read @0/9/2 (1) -> 0x4100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/3/0+0 at pos 167424 DISK read @0/9/3 (1) -> 0x4300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/4/0+0 at pos 167936 DISK read @0/9/4 (1) -> 0x4500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/5/0+0 at pos 168448 DISK read @0/9/5 (1) -> 0x4700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/6/0+0 at pos 168960 DISK read @0/9/6 (1) -> 0x4900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/7/0+0 at pos 169472 DISK read @0/9/7 (1) -> 0x4b00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/8/0+0 at pos 169984 DISK read @0/9/8 (1) -> 0x4d00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/9/0+0 at pos 170496 DISK read @0/9/9 (1) -> 0x4f00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/10/0+0 at pos 171008 DISK read @0/9/10 (1) -> 0x5100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/11/0+0 at pos 171520 DISK read @0/9/11 (1) -> 0x5300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/12/0+0 at pos 172032 DISK read @0/9/12 (1) -> 0x5500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/13/0+0 at pos 172544 DISK read @0/9/13 (1) -> 0x5700 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/14/0+0 at pos 173056 DISK read @0/9/14 (1) -> 0x5900 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/15/0+0 at pos 173568 DISK read @0/9/15 (1) -> 0x5b00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/16/0+0 at pos 174080 DISK read @0/9/16 (1) -> 0x5d00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/17/0+0 at pos 174592 DISK read @0/9/17 (1) -> 0x5f00 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/0/1+0 at pos 175104 DISK read @1/9/0 (1) -> 0x6100 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/1/1+0 at pos 175616 DISK read @1/9/1 (1) -> 0x6300 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/2/1+0 at pos 176128 DISK read @1/9/2 (1) -> 0x6500 OK. DISK: /dev/fd0: Trying to read 1 sectors at T/S/H 9/3/1+0 at pos 176640 DISK read @1/9/3 (1) -> 0x6700 OK. - ----Next_Part(Fri_Apr__2_08:56:42_1999_893)---- ------------------------------ From: "Ivan G. Okhrimenko" <[EMAIL PROTECTED]> Date: Sat, 03 Apr 1999 14:26:09 +0400 Subject: Autoexec and lredir Hello. Dosemu is working, but i have several problems: 1. autoexec.bat on hdimage is not parsing. I was trying to add simple line: "SET PATH=......." to autoexec.bat. This line is working from command prompt, but NOT working when placed to autoexec.bat. 2. Lredir answers "error f0bc redirecting <anydrive> to <anywhere>" on most commands. (?) What to do? Ivan. ------------------------------ From: Orlando Andico <[EMAIL PROTECTED]> Date: Sun, 4 Apr 1999 00:34:16 +0800 (JST) Subject: dosnet.o under Linux 2.2.5 Hello all, I'm using dosemu-0.98.6 under Linux 2.2.5. I cannot get the dosnet.o module to compile properly: after compilation, I cannot insert it (lots of unresolved symbols). What's the correct way to do this? TIA, Orly - ------------------------------------------------------------------- Orlando Andico <[EMAIL PROTECTED]> +63 (2) 937-2293 Mosaic Communications, Inc. +63 (912) 800-8262 Promote bacteria.. it's the only culture some people have. ------------------------------ From: Kirjah <[EMAIL PROTECTED]> Date: Mon, 05 Apr 1999 13:50:23 -0700 Subject: Master of Orion II Whenever I try to run the install program for Master of Orion II, I always get a few screen fulls of apparant garbage, and then something about "CPU in User mode" and "not enough privelages" whenever I move the mouse. This is confusing me. Someone...help? ------------------------------ From: Philippe Guillemette <[EMAIL PROTECTED]> Date: Tue, 6 Apr 1999 21:43:15 +0200 Subject: PS2 mouse crashes on console switch Hello, I'm using dosemu 0.98.6 and linux 2.0.36 on a P-120. I I use the internal driver with my PS/2 mouse. All this works fine (including the mouse unless when I switch from dosemu to linux than back to dosemu. When switching back, if I don't move the mouse, everything is fine, but I soon as I move the mouse, I have a solid keyboard freeze (_really_ nothing I can do) and I must rlog from another computer on my network to reboot mine. Any idea ? I've read the archive, but did'nt found anything yet Thanks, Philippe ------------------------------ End of linux-msdos-digest V1 #138 ********************************* To subscribe to linux-msdos-digest, send the command:
