Re: [fd-dev] Dosemu
On Mon, Nov 25, 2002 at 11:34:17PM -0500, George Bell wrote: You do not need WAITASEC to scroll back in Linux: You have hotkeys for that already enabled by default. Which hotkeys? I'd like to know about that. Shift + PageUp or PageDown -- Tschuess Andreas -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] codepage IDs
X-Comment-To: Axel C. Frinke Hi! 26-îÏÑ-2002 02:18 [EMAIL PROTECTED] (Axel C. Frinke) wrote to [EMAIL PROTECTED]: AF Well, with the assumption that all codepage IDs would not take more AF than 10 bits, there would be 6 remaining bits to denote variations of AB Please, don't make such silly suggestions and implementations. Making ACF Really, I would not call this suggestion 'silly'. But results of such decisions often are silly. B-\ Probably, most clear example of such decisions is an BIOS limits for disk sizes: first 512M, then 2Gb, then 4Gb, then 8Gb, then 32Gb, then 127Gb... ACF Maybe I've gone too ACF far with 'nightmare', but it's still handy to save address space. This is matter of taste, how call such desicions: silly, nightmare, etc. AB full featured lookup table may be _slightly_ more complicated, but then AB later this will not crash your (and our) head when limits will be exhausted. ACF Yes, but whenever new codepages are introduced, such lookup tables ACF must be maintained, this can become a cumbersome work. Why? -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^^=== This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^^===
Re: [fd-dev] codepage IDs
X-Comment-To: tom ehlert Hi! 26-îÏÑ-2002 16:25 [EMAIL PROTECTED] (tom ehlert) wrote to [EMAIL PROTECTED]: ACF Maybe I've gone too ACF far with 'nightmare', but it's still handy to save address space. This is matter of taste, how call such desicions: silly, nightmare, etc. te I often disagree with arkady, :( te like this time: :) te trouble to save 4 bits isn't 'silly'. it's outright 'dull' ;-) Let me clarify the situation: there is no trouble with saving four bits, but I was try to dissuade Axel to make such decision, when he tries to use part of regular enumeration space for its own needs. We already have much of troubles with FIDO communication software and FoxPro DBMS, which uses some positions in upper half of ASCII8 for their own needings. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^^=== This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^^===
Re: [fd-dev] codepage IDs
Rösberg, Tue 26.11.02 Hi Arkady, On Tue, 26 Nov 2002 18:54:43 +0300 (MSK), Arkady V.Belousov wrote: AB 26-îÏÑ-2002 16:25 [EMAIL PROTECTED] (tom ehlert) wrote to [EMAIL PROTECTED]: AF Maybe I've gone too AF far with 'nightmare', but it's still handy to save address space. AB This is matter of taste, how call such desicions: silly, nightmare, AB etc. TE trouble to save 4 bits isn't 'silly'. it's outright 'dull' ;-) Tom, why so polite? Why not slightly saying 'crack-brained'? After all, you always omit infinitive truth and wisdom, so you do need to take care of other people's opinion AB Please, don't make such silly suggestions and implementations. Making AF Really, I would not call this suggestion 'silly'. AB AB But results of such decisions often are silly. B-\ Probably, AB most clear example of such decisions is an BIOS limits for disk AB sizes: first 512M, then 2Gb, then 4Gb, then 8Gb, then 32Gb, then AB 127Gb... Hmmm... the number of codepage IDs does not grow with the same speed than hard disks do. But I go for that. And I want to repeat: my previous statement is more a wish than a demand. I would likely have the number of existing codepages limited to 4096 or 16384. But if there would be new codepages introduced with higher ID's, I would not ignore them. Of course, because of the possibility of such high codepage IDs my idea is somewhat questionable. AB full featured lookup table may be _slightly_ more complicated, but then AB later this will not crash your (and our) head when limits will be exhausted. AF Yes, but whenever new codepages are introduced, such lookup tables AF must be maintained, this can become a cumbersome work. AB Why? Actually, I starting to ask this question to myself. At meanwhile, it seems to be less effort for me to implement lookup tables than constisting on my idea. ;-) Regards, Axel. -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^^=== This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^^===
[fd-dev] Testing Freedos
Before Freedos can be claimed nonbeta software, the following steps must be taken in their entirety: 1) Scenario-based testing. Structured test scripts. 2)Module/unit testing. Testing small parts of the system. 3)Stress tests. Testing the system over the limits of its operation, such as over long time periods, or temperature limits. 4)Beta testing. Allowing users to test the system and document any problems found. 5)Gorilla testing. Testers do not follow a script, and anything that they can to break the system. The last step is especially important. :-) -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^
Re: [fd-dev] Dosemu
Hello! El vie, 22-11-2002 a las 18:16, Alain escribió: ... Yes I also belive that should be an easy interface. Has anyone heard of a DOSISH program that implement dos command in a linux system? Alain ... Lsh is a shell partially inspired by some command interpreters for PC monitors (such as 4-DOS, DR-DOS, MS-DOS, N-DOS, PC-DOS, Q-DOS and others, which might be trademarks of their owners and which is hereby acknowledged). However, most of the features of this shell are simply adapted from Unix (which also happens to be a trademark) shells. . Lsh is especially useful for users who have had some DOS experience and are now supposed to do something under UNIX. This shell will ease the transition and make the usage of dialup services extremely easy for them. . Note that this has nothing to do with the lsh Secure Shell v2 (SSH2) protocol implementation. If you need that SSH2 client, install lsh-client and see the lshc command. . upstream webpage: http://people.cs.uct.ac.za/~mwelz/lsh.html (copied from apt-cache show lsh on debian) Best Regards, Jorge-León -- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^^=== This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^^===
