Re: bugs known with cups?
On Mon, 2003-12-29 at 09:13, Christian Fischer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi there, i've recompiled my dosemu (1.1.5.0) with x. now printig via cups works only for single page documents, not for larger documents. in second case i get following cups error: print_job: unsupported format 'application/octet-stream' are there any bugs known or should it works well? please do not tell me upgrading. i know it's outdated, my linux box is it too (suse 8.1). upgrading must be but it isn't possible in the moment. Your problem is with CUPS and not Dosemu. In /etc/cups/mime.types uncomment: application/octet-stream and in /etc/cups/mime.convs uncomment: application/octet-streamapplication/vnd.cups-raw0 - and restart cupsd. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: running foxpro 2.6 in dosemu
On Mon, 2003-07-21 at 01:47, Galih Radito wrote: Hi does foxpro 2.6 running with dosemu ..? would you give me manual about running foxfro 2.6 with DosEmu, if it could. Yes, quite a few have Foxpro running under dosemu. I don't believe there is a manual. Get Dosemu running first and then copy the Foxpro files into your Dosemu C: drive and try running it. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: numlock and VNC
On Fri, 2003-03-14 at 09:50, Stephen Lee wrote: On Thu, 2003-03-13 at 22:33, Stephen Lee wrote: I'm running Foxpro2.6 under Dosemu 1.1.4/RH7.3/2.4.18. In an xdosemu session displayed remotely on another linux box, the numeric keypad works when numlock is turned on. If the xdosemu session is displayed remotely via tightvnc to a Win2k box, numlock does not work under dosemu. The numlock light is on but the keypad works as if numlock was off. Numlock does work in an xterm in vnc. I did try the vncserver switch -compatiblekbd but it had no effect under vnc/dosemu. Any suggestions on what switches or code to tweak? Never mind, I forgot to run xset fp rehash before starting vncserver. Spoke too soon. I added xset fp rehash to my .vnc/xstartup file to make sure it was run every time vncserver was started. The first time I connected to the vncserver and ran xdosemu, the keypad numeric keys worked. The next time I connected, the keypad numeric keys did not work. The keypad was functionally stuck in the numlock off position even if the numlock light was on. Restarting vnc did not fix the problem. It appears that when you exit xdosemu, something to do with keypad settings is altered or reset. The only way I could get numlock work reliable was to make sure numlock was off before starting xdosemu. Once in dosemu, I could activate numlock and then the numeric keypad worked fine. Is this a bug in xdosemu? Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: DOSEMU 1.1.4.15 for testing.
On Sat, 2003-03-15 at 18:06, Bart Oldeman wrote: Hi, I've put a new patchset (1.1.4.15) at http://www.dosemu.org/testing if you were using 1.1.4.13 before then please check if this one fixes your compilation fixes, and also please let us know if there are any new problems -- if everything is fine then I'll make this one 1.1.5. No problems compiling under Redhat 7.2. However, as mentioned in another thread, numlock within xdosemu only works if numlock is off before starting xdosemu when displayed remotely via VNC. If the xdosemu session is displayed remotely to another X workstation without using VNC, the numlock problem does not occur. Based on brief testing, everything else seems to work fine with Foxpro2.6. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: DOSEMU 1.1.4.15 for testing.
On Sat, 2003-03-15 at 18:49, Bart Oldeman wrote: I've never used VNC so I really cannot say much about this specific situation; it might be problematic for DOSEMU to ask for the numlock state via VNC, it might even be a VNC problem and not a DOSEMU problem. At least the workaround isn't hard. You also could try: * set $_X_keycode=(0) in your .dosemurc or dosemu.conf or * run an X server on the Windows site such as Cygwin xfree86. set $_X_keycode=(0) makes no difference and adding Cygwin xfree86 to 20 offsite workstations is too ambitious for me. I guess I'll just have to train users to turn off numlock before starting xdosemu - a minor inconvenience considering the coolness of being able to use a DOS program remotely ;-) Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: numlock and VNC
On Thu, 2003-03-13 at 22:33, Stephen Lee wrote: I'm running Foxpro2.6 under Dosemu 1.1.4/RH7.3/2.4.18. In an xdosemu session displayed remotely on another linux box, the numeric keypad works when numlock is turned on. If the xdosemu session is displayed remotely via tightvnc to a Win2k box, numlock does not work under dosemu. The numlock light is on but the keypad works as if numlock was off. Numlock does work in an xterm in vnc. I did try the vncserver switch -compatiblekbd but it had no effect under vnc/dosemu. Any suggestions on what switches or code to tweak? Never mind, I forgot to run xset fp rehash before starting vncserver. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
numlock and VNC
I'm running Foxpro2.6 under Dosemu 1.1.4/RH7.3/2.4.18. In an xdosemu session displayed remotely on another linux box, the numeric keypad works when numlock is turned on. If the xdosemu session is displayed remotely via tightvnc to a Win2k box, numlock does not work under dosemu. The numlock light is on but the keypad works as if numlock was off. Numlock does work in an xterm in vnc. I did try the vncserver switch -compatiblekbd but it had no effect under vnc/dosemu. Any suggestions on what switches or code to tweak? Thanks for your suggestions, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu and cups
On Wed, 2003-02-05 at 09:04, hector Colina wrote: Hi people. How can to specify a cups´s printer in dosemu? I see the dosemu.conf and it use the /etc/princapt, but i have cups Simply add your printer names to the $_printer variable in dosemurc. The order you list them will correspond to LPT1, LPT2, LPT3 and LPT4 in Dosemu. Your /etc/printcap will contain the Cups printer names. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
dosemu-1.1.4 and /var/lib/dosemu
I've compiled dosemu-1.1.4 on a Redhat 7.2 (with all recent updates) box with the default settings and did a systemwide installation: ./install_systemwide -fd /usr/local/dosemu/dosemu-freedos-bin.tgz -i /usr/local/dosemu/ I then created a user account (dosemu) and ran xdosemu and got: DOSEMU will run in its own X window. To terminate it you have three choices: - type Ctrl-C _here_ (not in the dosemu window) - type CtrlAltPgDn in the dosemu window - execute 'exitemu' at the DOS prompt Hint: if you want $HOME as DOS drive D:, then use the '-home' option Running unpriviledged in low feature mode Linux kernel 2.4.18; CPU speed is 2019809000 Hz Dosemu-1.1.4.0 Running on CPU=586, FPU=1 no console CONF aborted with: *** error: /var/lib/dosemu does not exist ... giving up. I then linked /var/lib/dosemu to /usr/local/dosemu/bin/dosemu but a that did not fix the error. 'dosemu -D+a -o debug' dumps the following: CONF: config variable parser_version_3 set CONF: config variable c_system set CONF: Parsing builtin file. CONF: config variable version_3_style_used set Any suggestions on what else to report or adjustments to make? I don't recall Dosemu 1.1.3.7 giving me this problem. Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: problems with locking
On Wed, 2002-11-06 at 06:20, Siim Vahtre wrote: OK, there ARE 2 locking problems. One with a file lock and another with a record lock. Try to search archives. Try 1.1.3 version, for some people it seems to work (not for me and for some clipper users i think). But what do you try with test.txt is maybe ok, when I open for ex. with NC some file for reading (F3 - view file), it opens the file in DENY-ALL mode and it should deny other sessions to open the file. I tried 1.1.3 aswell. Exactly the same :( Try it with the latest patches (1.1.3.7) at http://www.dosemu.org/testing. I had to use the patches, starting with 1.1.3.3, before Foxpro and Samba would recognize each others locks. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: control characters with newest version?
On Tue, 2002-09-24 at 15:52, Cheryl Homiak wrote: I'm trying to decide whether I want to try the newest version of dosemu. I'm happy with my present setup except that I have a program that needs control characters that dosemu can't handle. for instance, there's a menu that needs control-i; there are others but that's the one I can think of right now. can anybody tell me whether the newest development version has any better handling of control characters than version 1.1.3? Thanks. For my application, which was Foxpro based, V1.1.3.2, was the breakthrough. All of my ctrl-a-z and ctrl-F1-F12 keys finally worked. I would try 1.1.3 with the appropriate patchset to bring it to 1.1.3.3. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Samba and kernel oplocks - Solved.
On Wed, 2002-08-28 at 23:21, Sergey Suleymanov wrote: Anderson Pereira Ataides writes: Anderson I thing problem is not only samba because nfs also have Anderson problem. I have two Linux workstations and when I lock Anderson record in one of them, the other one can't see this lock. Anderson Like you I'm waiting for a solution to this problem. Well, I'm just try locks with samba, and it seems work. oplocks = no in smb.conf and this hack to mfs.c --- src/dosext/mfs/mfs.c.orig Thu Aug 29 10:09:33 2002 +++ src/dosext/mfs/mfs.c Thu Aug 29 10:08:31 2002 @@ -3823,11 +3823,16 @@ the top two bits are set. Shift the top ones by two bits. This still allows OLE2 apps to operate, but should stop lockd from dieing */ +#if 0 if ((larg.l_start mask) != 0) larg.l_start = (larg.l_start ~mask) | ((larg.l_start mask) 2); +#else + larg.l_start = 0x7fff; +#endif ret = fcntl (fd,F_SETLK,larg); Debug0((dbg_fd, lock fd=%x rc=%x type=%x whence=%x start=%lx, len=%lx\n, fd, ret, larg.l_type, larg.l_whence, larg.l_start,larg.l_len)); + if (ret == -1) SETWORD((state-eax), ACCESS_DENIED); return ret != -1 ? TRUE : FALSE; } break; I don't understand that bit magic, maybe this won't work with nfs or something else. I'm happy to say that the above patch allows Foxpro/Dosemu file locks to be recognized by Samba 2.2.4. This means I can run the Foxpro application via Dosemu and under MSDOS/Win98/Samba simultaneously! The only issue I had with the above patch is that the line numbers did not match my version of Dosemu 1.1.3.2 with keyboard patches. I had to insert the lines manually. Now onto stress testing to ensure the changes do not affect Dosemu stability. Thanks Sergey! Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]
On Thu, 2002-08-29 at 08:04, Oscar A. Valdez wrote: I forgot to mention that I had to substitute the FreeDOS kernel that comes packaged with the binary Dosemu 1.0.2.x distribution (version 2024?) with kernel.sys version 2026. Kernel versions earlier that 2026 do not handle locks on lredir'd drives. Thanks Oscar. I am using DRDOS but since the install_systemwide script requires dosemu-freedos-bin.tgz does that mean I also need to upgrade the FreeDOS kernel as well? Recall that I am using 1.1.3.2 with the keyboard patches. Another point is that Im not using lredir as $_hdimage points directly to C:\ and the Foxpro app must run on the C: drive. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Samba and kernel oplocks
On Wed, 2002-08-28 at 23:21, Sergey Suleymanov wrote: Anderson Pereira Ataides writes: Anderson I thing problem is not only samba because nfs also have Anderson problem. I have two Linux workstations and when I lock Anderson record in one of them, the other one can't see this lock. Anderson Like you I'm waiting for a solution to this problem. Well, I'm just try locks with samba, and it seems work. oplocks = no in smb.conf and this hack to mfs.c --- src/dosext/mfs/mfs.c.orig Thu Aug 29 10:09:33 2002 +++ src/dosext/mfs/mfs.c Thu Aug 29 10:08:31 2002 @@ -3823,11 +3823,16 @@ the top two bits are set. Shift the top ones by two bits. This still allows OLE2 apps to operate, but should stop lockd from dieing */ +#if 0 if ((larg.l_start mask) != 0) larg.l_start = (larg.l_start ~mask) | ((larg.l_start mask) 2); +#else + larg.l_start = 0x7fff; +#endif ret = fcntl (fd,F_SETLK,larg); Debug0((dbg_fd, lock fd=%x rc=%x type=%x whence=%x start=%lx, len=%lx\n, fd, ret, larg.l_type, larg.l_whence, larg.l_start,larg.l_len)); + if (ret == -1) SETWORD((state-eax), ACCESS_DENIED); return ret != -1 ? TRUE : FALSE; } break; I copied your diff into a file and ran patch -p0 diff_file and got: patching file src/dosext/mfs/mfs.c Hunk #1 FAILED at 3823. 1 out of 1 hunk FAILED -- saving rejects to file src/dosext/mfs/mfs.c.rej I don't know much about patching but it appears that the prepatch status of my 1.1.3.2 mfs.c is different compared to yours. The line containing the top two bits are set. Shift the top ones by two bits. in my version of mfs.c resides at line 3789. Thanks for your help. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]
On Thu, 2002-08-29 at 11:20, Oscar A. Valdez wrote: I don't know what version of the kernel comes with 1.1.3.2, but, like Bart said, your $_hdimage gets converted to an lredir'd drive, and if your kernel doesn't handle locks properly on lredir'd drives, you won't be able to set locks on C: Bart, what version of the kernel comes with 1.1.3.2? Is it OK to use a higher version of kernel.sys with it? Oscar Hmmm...does that mean I should be using Freedos and not DRDOS if I want proper kernel locking? I hope Foxpro works well with Freedos! Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Fwd: Re: Samba and kernel oplocks - Smbmount]
On Thu, 2002-08-29 at 11:54, Bart Oldeman wrote: FreeDOS kernels before ~2026 did not translate D-215C--- INT 21 - DOS 3.0+ - FLOCK - RECORD LOCKING into N-2F110A- INT 2F CU - NETWORK REDIRECTOR (DOS 4.0+) - LOCK/UNLOCK REGION OF FILE That was the problem - the redirector interface is a relatively recent addition to FreeDOS. DR-DOS should not have this bug. I suspect that the way that DOSEMU tries to implement DOS locking techniques is not compatible with mandatory locking on the Samba Unix side. Thanks for explaining the complexities. A few more questions: 1. Does that mean Sergey's hack to mfs.c is not a permanent solution? I've made the changes but am waiting for my Foxpro users to test it. 2. Is using smbmount to access the Foxpro files from Dosemu a valid way to get around the locking problem? I suspect it will be slower but anything else? Thanks again. Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Samba and kernel oplocks
On Wed, 2002-08-28 at 06:14, Anderson Pereira Ataides wrote: I have a similar problem here but using CLIPPER not FoxPro. I received some messages to upgrade kernel and Samba. I made it and I've just tested (yesterday), but did not solve my problem. Windows workstations still can't see locks made by dosemu. And dosemu also can't see windows locks. Just to confirm, I am using: kernel 2.4.19 samba 2.2.5 dosemu 1.1.3 I thing problem is not only samba because nfs also have problem. I have two Linux workstations and when I lock record in one of them, the other one can't see this lock. Like you I'm waiting for a solution to this problem. bye, Anderson Pereira Ataides The patch sent by Bart did not work in my case either. I wonder if this problem was introduced in the 1.1.3 branch or also exists in the 1.0.2 stable series as well? Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Samba and kernel oplocks - Smbmount
On Tue, 2002-08-27 at 15:55, Stephen Lee wrote: Hi, I am running a Foxpro application under Dosemu 1.1.3.2 (xdosemu) with the keyboard patches and things seem to be running smoothly. Problems occur when some users access the same Foxpro db files via Samba 2.2.4. Files locked under Dosemu/Foxpro are not locked when accessed by Samba. Some of the samba config settings include: kernel oplocks = yes locking = Yes oplocks = Yes level2 oplocks = Yes oplock contention limit = 2 posix locking = Yes strict locking = No This is a Redhat 7.2 systems running kernel 2.4.18. What else do I need to configure to get Dosemu file locks recognized by Samba? Just for kicks, I tried to access the Foxpro db files via an smb share using smbmount. Instead of pointing $_hdimage to the Drdos/Foxpro directory directly, I pointed it to a directory mounted to the smb share containing the Drdos/Foxpro files. The idea was to make Dosemu use the Samba file locking system. Well...Dosemu runs and Foxpro starts but the whole process is REALLY slow. So slow that I didn't have the patience to test whether the file locking problem was fixed. It's not eating up cpu cycles either (according to top). Has anyone tried to access smb shares from Dosemu and if yes how did you do it? Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Status of Escape patch?
Hi, A while back, couple versions of a patch to fix the double escape key and the 30 second problem appeared on the list. What is the status of this patch and can it be included on Stas' dosemu page? Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Mapping Control and Shift Function Keys
Hi,
I'm trying to get the Shift and Control Function keys to work in a
terminal (SecureCRT) Dosemu session. I got the terminal emulator to
generate distinct escape sequences for the Fkeys and then added
corresponding enties in ./dosemu-1.1.3/src/plugin/keyboard/keyb_slang.c.
Here's a sample of cat -v in the terminal session
F11 and F12: ^[[23~^[[24~
Shift F11 and F12: ^[[36~^[[37~
Control F11 and F12: ^[[60~^[[61~
Here are the corresponding entires in keyb_slang.c under
static Keymap_Scan_Type vtxxx_fkeys[] = :
{\033[23~, KEY_F11 }, /* F11 */
{\033[24~, KEY_F12 }, /* F12 */
{\033[36~, KEY_F11 | SHIFT_MASK }, /* Shift F11 */
{\033[37~, KEY_F12 | SHIFT_MASK }, /* Shift F12 */
{\033[60~, KEY_F11 | CTRL_MASK },/* Ctrl F11 */
{\033[61~, KEY_F12 | CTRL_MASK },/* Ctrl F12 */
My Foxpro application recognizes the F1-F12 keys fine but not the Shift
or the Control Fkeys. I ran a keyboard scan program in the DOS session
and it does not detect any of the Control or Shift Fkeys either. Where
to look next?
Thanks for any suggestions,
Stephen
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Mapping Control and Shift Function Keys
On Sun, 2002-06-16 at 08:34, Stephen Lee wrote: Hi, I'm trying to get the Shift and Control Function keys to work in a terminal (SecureCRT) Dosemu session. I got the terminal emulator to generate distinct escape sequences for the Fkeys and then added corresponding enties in ./dosemu-1.1.3/src/plugin/keyboard/keyb_slang.c. I forgot to mention that Dosemu is run under Redhat 7.2 Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: lpr: unable to print file:client-error-document-format-not-supported
On Sat, 2002-06-08 at 17:12, jonsky wrote: Hi guys, I've tried to print onto console to print some file and its works fine and i've tried to print from dosemu using dir prn works also but using the clipper compiled application to print report no luck. When i look at the boot.log i saw ; lpr: unable to print file: client-error-document-format-not-supported Is it the LINEFEED and EOF Marks? Any suggestion how to go about it? Does the Clipper application generate plain text or is it expecting to print to a specific printer type like pcl (eg HP)? Normally your underlying printing system will identify the kind of print output and use the correct filter to convert it to something the printer understands (eg. ps-pcl). Be sure you have that part setup correctly. I use CUPS and so the whole process is almost trivial. What happens if your create a raw printer (ie. no print filter) and print to that instead? Note that this will only work if your clipper application outputs in a format the printer itself can understand. Stephen Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Keymap for terminals
On Sun, 2002-04-07 at 16:31, Bart Oldeman wrote: On 7 Apr 2002, Stephen Lee wrote: I would like to map some of the keys (including Function keys) to specific escape sequences. My goal is to have them work as expected under Foxpro/Dosemu. I've managed to change the escaped sequences under console mode with loadkeys mykeys.map. However, when I login to the system with a dos terminal emulator like PuTTY (using TERM=linux), I don't get the new key mappings. The same can be said for xterms. How do I get these new key mappings to work with terminals? Have you tried hacking keyb_slang.c? I will as soon as I can get my PuTTY (or xterm) session to distiguish between F11 and F23, F12 and F24, Ins and ^Ins and Del and ^Del. As mentioned above, the modified keymap only works on the console. Is is correct to presume that these keymap changes must work in the linux terminal before they will work in Dosemu? I am not sure about any standard but modern xterms seem to give a lot of different escape sequences. I wonder if I need to play around with the terminfo db for linux? Thanks, Stephen - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
