Re: lag while printing and serial redirect
On Tue, 13 Dec 2016 14:26:34 +0100 Jakub Klawiter wrote: > $ echo test | lpr -l > the printer starts to print immediately. > > But from dosemu if i'll try: > > C:>echo test > lpt1: > > it's working but there is 3-4 seconds lag before it starts to print. > Where can i look to fix it? That's the way that lpr works under dosemu. It's my understanding that the objective is to print a whole page at a time because that's how modern printers work. Since most dos programs don't send a page end/page break, dosemu just waits for a few seconds to see if anything more is coming; if not the page is assumed complete and send it to the printer. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: High Temperature with DOSEMU
On Fri, 23 Nov 2007 08:54:11 +0100 Hayen Iggena [EMAIL PROTECTED] wrote: I can get tame only for Windows. I'm using Linux. http://www.tamedos.com/downloads/tame334a.zip -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: How can I force all files created by any user in dosemu to be 'read and write' enabled for all users?
On Thu, 15 Nov 2007 10:26:56 - Tarquin Adams [EMAIL PROTECTED] wrote: How can I force all files created by any user in dosemu to be 'read and write' enabled for all users or at least for users in the same group as the creator? Write a little script to load dosemu from and set a umask value in it. umask 002 dosemu -I 'keystroke cd temp\rmyfile\r' This little script sets things up so files written by DOSEMU are r/w for all users in the same group as the guy who loaded the script. It then does this in your DOSEMU window: cd temp myfile Go to directory named c:\temp, run a file called myfile. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 64-bit compile? - SOLVED
I raised this issue on the Fedora mailing list as well as here and have received a very interesting response. See here: https://www.redhat.com/archives/fedora-list/2007-November/msg02329.html Mr. Boszormenyi apparently needed to apply a patch to the dosemu source tree in order to get dosemu to compile on his x86_64 machine. I, on the other hand, didn't need to do this and it still compiled for me and appears to work fine in my (so far, limited) testing. As this is substantially beyond my understanding, I would appreciate any feedback or information that anyone here would care to share with me. This whole x86_64 stuff is an entirely new adventure for me. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 64-bit compile? - SOLVED
On Wed, 14 Nov 2007 10:16:29 -0800 (PST) Bryan J. Smith [EMAIL PROTECTED] wrote: Hence why I wrote a brief blog article here: 'What is x86-64? Long Mode memory model ...' http://thebs413.blogspot.com/2005/10/what-is-x86-64-long-mode-memory-model.html Thanks for that write-up. It's a truly fascinating read and I can now say that I know a great deal more about the basics of what's going on here than I knew a few minutes ago. In a nutshell, 48-bit (PAE 52-bit) addressed Long Mode is focused on being 32-bit (PAE 36-bit) i486 TLB (i686 PAE) compatible. But there is no reason why it can't support i386 Virtual86 modes either. The patch allows Virtual86 programs to run on a Long Mode kernel just as fast as they do on i486 or i686 PAE kernels. Is there any disadvantage to this patch? Is there any reason why it should not or can't be included in the mainstream kernel? It sounds to me very much like a winning idea -- so why don't we see it built-in by default? I'm thinking there mus t be a downside that I'm not aware of -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 64-bit compile? - SOLVED
On Thu, 15 Nov 2007 11:39:59 +1300 Bart Oldeman [EMAIL PROTECTED] wrote: The question is how important the speed is, as most 16-bit programs were written at a time when CPUs were natively slower than the emulation speed now! For me it's not a particularly big deal on my computer; all I do with DOSEMU is write and maintain my PB programs and occasionally run WP/DOS or the like. However, I have a customer who runs a commercial publishing operation that's entirely based around Linux, Scribus, and my PB/DOS programs. I'm rather glad that I didn't set up the x86_64 version of Centos 5 when I put his new application server together a month or so back. At the time I didn't want to do that due to the adventure factor on his production machines. Now I'm taking that adventure on my own computer here and quite enjoying it, but have learned that DOSEMU stuff currently ain't where it's at when it comes to x86_64. Therefore I did the right thing at the time and didn't realize it. PowerBasic runs amazingly well under DOSEMU and because of that I brute force a lot of things that could probably be done a lot more efficiently, but since the action happens pretty much instantly anyway, it's more than good enough anyway. If you or anyone else is interested in my adventures with PowerBasic and DOSEMU, I have an article about it here: http://www.melvilletheatre.com/articles/powerbasic-linux/index.html That article gets a lot of hits every day from people doing Google searches for powerbasic linux and the like. I shall add a bit to it regarding DOSEMU and x86_64 one of these days, now that I've had the opportunity to experiment. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 64-bit compile? - SOLVED
On Mon, 12 Nov 2007 16:39:15 -0600
Frank Cox [EMAIL PROTECTED] wrote:
Having just set this computer up with Fedora 8 x86_64, I am trying to compile
dosemu to run on it. Note that this is (for now) a pure x86_64 system --
there are no i386 libraries installed on it at all.
I got this figured out.
After doing the rpmbuild --rebuild dosemu-1.4.0-1.src.rpm step that errored
out as described in my previous message, I had a file named dosemu-1.4.0.tgz in
my ~/rpmbuild/SOURCES directory. I un-tarred that and after poking around a
bit I found a file named compiletime-settings. I changed the line in that file
that said libdir ${prefix}/lib to libdir ${prefix}/lib64
I then recreated dosemu-1.4.0.tgz in the ~/rpmbuild/SOURCES directory so it now
contained the modified compiletime-settings file. After that, doing a rpm
-bb ~/rpmbuild/SPECS/dosemu.spec created the file that I wanted,
dosemu-1.4.0-1.x86_64.rpm. I installed it and it appears to work as expected.
PERFORMANCE
This 64-bit DOSEMU compile runs substantially slower than the 32-bit compile
that I used previously on this computer. I have several rather large
PowerBASIC/DOS programs that are, in fact, the main reason why I use DOSEMU.
Up until a couple of days ago, I had Fedora 7/i386 on this computer. I just
happen to still have the numbers when compiling one of those programs with
PowerBASIC/DOS under DOSEMU:
With F7/i386: 1686600 lines per minute -- total time to compile the program:
0.2 seconds
With F8/x86_64: 230400 lines per minute -- total time to compile the program:
1.6 seconds.
The F8/x86_64 DOSEMU is running approximately 13 times slower.
I understand that DOSEMU has to do more work to run on a x86_64 architecture.
However, I'm wondering if there is something that I missed or something that I
should do (compiler options?) that would give it a bit more oomph.
--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
-
To unsubscribe from this list: send the line unsubscribe linux-msdos in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
64-bit compile?
Having just set this computer up with Fedora 8 x86_64, I am trying to compile dosemu to run on it. Note that this is (for now) a pure x86_64 system -- there are no i386 libraries installed on it at all. When I download dosemu-1.4.0.tgz and do ./configure, make it appears to complete ok. It tells me: QUOTE DONE compiling Now you must install DOSEMU. Make sure you are root and: make install END OF QUOTE However, I want to make a rpm and install it from that if I possibly can. So I try this: rpmbuild --rebuild dosemu-1.4.0-1.src.rpm After many screens of write-up, I get the following errors. What am I doing wrong? Processing files: dosemu-1.4.0-1 error: File not found: /home/frankcox/rpmbuild/BUILD/dosemu-root/usr/lib64/dosemu error: File not found by glob: /home/frankcox/rpmbuild/BUILD/dosemu-root/usr/lib64/dosemu/libplugin*.so Processing files: dosemu-debuginfo-1.4.0-1 Requires(rpmlib): rpmlib (CompressedFileNames) = 3.0.4-1 rpmlib(PayloadFilesHavePrefix) = 4.0-1 Checking for unpackaged file (s): /usr/lib/rpm/check-files /home/frankcox/rpmbuild/BUILD/dosemu-root error: Installed (but unpackaged) file(s) found: /usr/lib/dosemu/libplugin_X.so /usr/lib/dosemu/libplugin_alsa.so /usr/lib/dosemu/libplugin_gpm.so /usr/lib/dosemu/libplugin_sdl.so /usr/lib/dosemu/libplugin_term.so RPM build errors: user enbeo does not exist - using root user enbeo does not exist - using root File not found: /home/frankcox/rpmbuild/BUILD/dosemu-root/usr/lib64/dosemu File not found by glob: /home/frankcox/rpmbuild/BUILD/dosemu-root/usr/lib64/dosemu/libplugin*.so Installed (but unpackaged) file(s) found: /usr/lib/dosemu/libplugin_X.so /usr/lib/dosemu/libplugin_alsa.so /usr/lib/dosemu/libplugin_gpm.so /usr/lib/dosemu/libplugin_sdl.so /usr/lib/dosemu/libplugin_term.so -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: wordperfect for dos version 6.2 crashes dosemu
On Sat, 03 Nov 2007 10:10:11 +0100 [EMAIL PROTECTED] wrote: Is there anybody who actually got wpdos 6.2 to run in DOSEMU? This isn't of much help to you, but I use WP 5.1 and it works fine... -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Performance problems
On Sat, 27 Oct 2007 12:19:54 -0600 Frank Cox [EMAIL PROTECTED] wrote: It seems to me that there was another program that does pretty much the same thing as TAME but without the send-money nag screen, i.e. a free program. But I can't recall its name at the moment I found it. Here is the readme file: QUOTE: DVPTAME Released to the Public Domain, 1991. DVPTAME lets DESQview suspend programs before their time slice is up if they are frequently polling the keyboard to check for a keystroke. You specify how many times the program is allowed to check for a keystroke in one clock tick (1/18 of a second), and DESQview does the rest. No extra programs to load, no shared programs, etc. Usage 1: DVPTAME = dvp-file Report the current polling limit Usage 2: DVPTAME n dvp-file Set the polling limit to n keyboard polls per clock tick In both cases, dvp-file is the FULL filename of the .DVP for the program you wish to tame. In many cases, DVPTAME will perform just as well as the shareware TAME. However, TAME can suspend programs which don't poll the keyboard often but make their idleness known in other ways, and can tame programs which poll the keyboard frequently even while they are still doing useful work. Ralf Brown [EMAIL PROTECTED] 1:129/26.1 END OF QUOTE As you can see, it appears to be DESQvew-specific at the moment. However, complete asm source code is included in the archive that I have so someone who is more incentivized than I am at the moment may be able to make it work with DOSEMU. DVPTAME doesn't appear to be easily available online at the moment; at least, Google didn't find it for me. Accordingly, I have put it online here for anyone who may want to take a look at it: http://www.melvilletheatre.com/dvptame.tar.bz2 -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Performance problems
On Fri, 26 Oct 2007 20:33:44 -0300 Boscovich, Maximiliano [EMAIL PROTECTED] wrote: We are running FoxPro compiled application and it really slow on performance. I wonder if TAME would help. It seems to me that there was another program that does pretty much the same thing as TAME but without the send-money nag screen, i.e. a free program. But I can't recall its name at the moment -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: /etc/skel failure
On Sat, 29 Sep 2007 16:56:46 -0600 Frank Cox [EMAIL PROTECTED] wrote: The short form of the story is that I can't have a symbolic link in ~/.dosemu/drive_c as part of an /etc/skel profile and have it actually work. After further experimentation, I'm starting to think there is something more fundamentally strange going on here. If I create a new user when the .dosemu directory is set up by /etc/skel, I load dosemu and do a dir I get the directory listing that is actually in /usr/share/dosemu/drive_z. If I delete .dosemu in my new user's directory and then run dosemu and do a dir I see what is in .dosemu/drive_c like I expected. It seems to be looking in the wrong place for drive C when the .dosemu directory is set up from /etc/skel, and it straightens itself out if it's allowed to create its own .dosemu directory instead. Some kind of a redirection problem? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
/etc/skel failure
I have had this happen before, but just now figured out exactly what's going on. I still don't know why. I create a user and run dosemu, then go into ~/.dosemu/drive_c and make a symbolic link to another directory: ln -s /opt/data/test . Now I have a link in ~/.dosemu/drive_c that goes to /opt/data/test and if I load dosemu and type cd test it takes me to /opt/data/test just like it should. I use that user's home directory to create a /etc/skel directory for creating new users home directories from. When I create a new user with that /etc/skel in place, I have a link to /opt/data/test in ~/.dosemu/drive_c just like I should. But: dosemu doesn't see it. In the dosemu window, I type dir and cant' see TEST listed at all. cd test doesn't work. Removing ~/.dosemu from the new user's directory and running dosemu and adding the link works as expected. The short form of the story is that I can't have a symbolic link in ~/.dosemu/drive_c as part of an /etc/skel profile and have it actually work. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Multi-user and shared directories (reply part 2 of 3)
Just make a symbolic link in ~/.dosemu/drive_c to point to a common directory. For example: mkdir /opt/dosstuff ln -s /opt/dosstuff ~/.dosemu/drive_c/dosstuff Set your permissions in /opt/dosstuff to whatever you want. Now you can use cd dosstuff from a dos prompt within your dosemu window to move to /opt/dosstuff. This gives you the flexibility of having one or many shared dos directories, plus having private dos directories for each user. If you choose to do it the way that I do it, your users will never see a dos prompt. autoexec.bat cranks up a frontend menu that exits with various errorlevels to jump to points in the batch file that change directories (private under ~/dosemu/freedos and shared under /opt) and run programs as needed. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Multi-user and shared directories (reply part 1 of 3)
Once again the over-eager spam filter on the mailing list server has apparently eaten my reply to Roberto. He got it himself as I sent him a copy directly, but it has not appeared on the mailing list here for the benefit of anyone else who might be interested in this topic. I will try resending it to the list now in three parts and see if it gets through this way. Begin forwarded message: Date: Wed, 29 Aug 2007 22:53:09 -0600 From: Frank Cox [EMAIL PROTECTED] To: Roberto Bechtlufft [EMAIL PROTECTED] Cc: linux-msdos@vger.kernel.org Subject: Re: Multi-user and shared directories On Thu, 30 Aug 2007 01:06:18 -0300 Roberto Bechtlufft [EMAIL PROTECTED] wrote: Well, I dont have a ~/.dosemu/freedos directory here. All I have is this: The server that the article is written about currently uses dosemu 1.2.2; I haven't gotten around to updating it to 1.4 yet (though I do use 1.4 on my own computer). The 1.4 equivalent to ~/dosemu/freedos is ~/.dosemu/drive_c Is this what you mean: Not exactly. You are making it more complex than it needs to be. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Fw: Re: Multi-user and shared directories (second try with part 3)
Looks like it's something in the last two paragraphs that causes the mailing list server to reject my this message. I will reword it a bit to see if that solves the problem. Begin forwarded message: You can create your frontend directly with the batchfile using choice.exe, or you can write it using any dos compiler or interpreter, or whatever floats your boat. I personally wrote my frontends using the powerbasic compiler because it's easy to make them bulletproof, plus they are prettier than they would be when using choice.exe. Once you have your user's directory structure, batch files, programs and what-have-you laid out, copy the whole thing into /etc/skel and all new users will automatically inherit everything ready-to-roll as you create them. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Multi-user and shared directories
On Thu, 30 Aug 2007 17:38:43 -0300 Roberto Bechtlufft [EMAIL PROTECTED] wrote: Suppose I have users roberto and fatima. roberto is under the groups roberto and dosemu, and fatima is under fatima and dosemu. When I do a chmod 002 and as roberto create a new file all users under the group roberto can read and write to it. However, I want my files to be created under the dosemu group, and not roberto, so fatima can read and write to it to. How can I do it? man newgrp -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: self-compile of src.rpm fails to run
On Sat, 02 Jun 2007 09:49:57 +0300 Andris Pavenis [EMAIL PROTECTED] wrote: I also compiled DosEmu-1.4.0 from source RPM on Fedora Core 6 and it works OK. No serious problems detected. As I just set up Fedora 7 on this computer, I decided to try compiling the source RPM again with this setup and see what happened. It compiled without error. I removed the pre-compiled rpm and installed the one that I just created and it now works perfectly; no error reported at all. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
DOSEMU vga font
I use LTSP to run terminals off of Fedora Linux servers and run DOSEMU on those terminals. (Some of you might be interested in my article about DOSEMU, PowerBasic/DOS and LTSP: http://www.melvilletheatre.net/articles ) When I start DOSEMU on a terminal, I get this message: QUOTE: You do not have the DOSEMU vga font installed and are running remote X. You need to install the vga font on your _local_ Xserver. Look at the readme for details. For now we start with an fixed font, which does not display all national characters correctly. ... be warned END OF QUOTE That message doesn't appear to affect anything, and the DOSEMU window doesn't look any different than it does when I run it directly on the server. It has never been clear to me how to get rid of this error and since it never affected or changed anything I haven't given it much thought. However, now that I'm playing with DOSEMU 1.4.0, it might be a good time to deal with this error and get rid of it. How and where do I add that missing font to keep DOSEMU happy when it's running on a terminal? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
loadhi in dosemu-1.4.0-1.i386.rpm
Has loadhi disappeared by accident or design in the latest dosemu rpm? I can find it in dosemu-1.2.2-1.i386.rpm, but it's missing in 1.4.0-1.i386.rpm. And if it's by design, is there a list of other dos commands that have been removed or replaced for whatever reason? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
umb's unavailable
One more minor issue. This doesn't appear to be an actual problem, at least not for what I'm trying to run at the moment. However, when I first crank up dosemu, I get the message UMB's unavailable! dosemu XMS 3.0 driver installed. dosemu EMS 4.0 driver installed. This is using the stock config.sys file that comes with dosemu. So... who stole the UMB's? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
self-compile failure and loadhi disappeared
I attempted to post this question to this mailing list yesterday but the list's spam filter seems a bit over-eager and it didn't appear to make it to the list. If I post it again it will probably disappear once more, so I have posted my questions at: http://www.melvilletheatre.com/dosemuquestion.txt Any input or suggestions regarding my question would be greatly appreciated. Now lets see if this post gets eaten as well -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
