Re: [Freedos-user] Command line
On Thu, Mar 4, 2021 at 10:05 AM Jose Senna wrote: > > Did anyone else look at this ? > https://www.nature.com/articles/d41586-021-00263-0 > Command line is still (much) alive. > > Interesting article, thanks for sharing. This article is geared for Unix (Linux or Mac) but the concepts apply to FreeDOS. You can still do a lot at the command line. Like others, this article reminds me of using the Unix command line. And it reminds me of an article I wrote for CloudSavvyIT Linux some months ago, about how to check spelling "the old school" Unix way: https://www.cloudsavvyit.com/5439/how-to-check-spelling-the-old-school-unix-way/ $cat document | tr A-Z a-z | tr -d ',.:;()?!' | tr ' ' '\n' | sort | uniq | comm -2 -3 - words That Unix command line converts a text file into lowercase, then deletes all punctuation and special characters, splits lines at spaces, sorts the result, looks for unique words .. then compares that list of words to the system dictionary (called "words"). The command outputs a list of misspelled words (words that appear in the original document that do not appear in the system dictionary). Jim ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command line
On Thu, Mar 4, 2021 at 11:05 AM Jose Senna wrote: > > Did anyone else look at this ? > https://www.nature.com/articles/d41586-021-00263-0 > Command line is still (much) alive. Those who think it isn't need to get out more. I had a Unix system at home before I got an XT clone running MSDOS. (I still have it.) Mine was an early machine intended to be a single user Unix workstation. The bigger ones I administered for a living were multi-user systems that assumed you would access them remotely, and would log in as a terminal to a command line. Mine had a well-crafted GUI, but I still used a command line for things that weren't well suited to a GUI. These days, I run Win10 Pro on my desktop, but installed an open source tabbed console emulator called ConEmu, that lets me have multiple command lines in a single tabbed interface, and what is on those command lines may differ. Here, the default if it's installed is JPSoftware's TCC-LE, a freeware limited version of their commercial Take Command GUI interface. TCC-LE looks an awful lot like (and its design is based on) the popular 4DOS command.com replacement for DOS PCs. Bit I can also run MS's PowerShell, Windows CMD-EXE, and Win32 ports of things like the *nix bash and zsh shells, or DOS character mode applications run using the vDOS Plus fork of the popular DOS emulator designed to let you run old DOS games on things that aren't MSDOS PCs. (A have a few DOS programs on an Android tablet using an Android port of DOSbox.) Most of what current users do is best done through a GUI, but there are things like commands run in pipelines that need a command line to be able to do that.Most folks simply don't need a command line, but you can get one if you do. Another issue is the shift to mobile devices for computing. While you can *get* a command line on something like a smartphone or tablet, trying to use it can be actively painful if you don't have an external keyboard you can attach. __ Dennis ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command line
> Did anyone else look at this ? > https://www.nature.com/articles/d41586-021-00263-0 > Command line is still (much) alive. "Five reasons why researchers should learn to love the command line The text interface is intimidating, but can save researchers from mundane computing tasks. Just be sure you know what you’re doing." Reminds me of when we once needed some statistical analysis and the SPSS package produced 3 pages of comments for every datasets :-p We then manually put the formula into a generic maths programming language to get only the actual results. Much later, I have seen a presentation about R which actually seems to have a syntax like compact(yourtest(data)) which would combine the best of both worlds? :-) Cheers, Eric ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Command line
Did anyone else look at this ? https://www.nature.com/articles/d41586-021-00263-0 Command line is still (much) alive. ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command Line Parsing
Jack Jackson wrote:
I've noticed a difference in command line parsing between FreeDOS and
PC-DOS.
Both FreeDOS and PC-DOS put the command line, starting with the
character after the executable, in a buffer at offset 0x80 in the PSP.
The behavior difference I see with FreeDOS is if the first non-blank
character after the executable is a left parenthesis, then FreeDOS sets
0x80 in the PSP to zero so the rest of the command line is not
available.
Examples of what is in PSP 0x80:
Command Line: SOMEPROG (aa bb cc FreeDOS: \0 DOS: (aa bb cc\0
Command Line: SOMEPROG abc (cc dd ee FreeDOS and DOS: abc (cc dd
ee\0
Does anyone know why FreeDOS behaves differently when the first
character after the executable is a left parenthesis?
Hi Jack,
I not know how to determine the value PSP 0x80, but when I try this
simple program (compiled/linked with OpenWatcom):
#include stdio.h
#include stdlib.h
void main(int argc, char const *argv[]){
int ii;
for(ii=0; iiargc; ii++){
printf(argv[%d] = %s\r\n, ii, argv[ii]);
}
}
then parameters seems be fine:
E:\pokusydosparm
argv[0] = E:\POKUSY\DOSPARM.COM
E:\pokusydosparm p1 (p2
argv[0] = E:\POKUSY\DOSPARM.COM
argv[1] = p1
argv[2] = (p2
E:\pokusydosparm (p1 (p2
argv[0] = E:\POKUSY\DOSPARM.COM
argv[1] = (p1
argv[2] = (p2
It is tested with FreeDOS 1.1 under DOSEMU, probably no reason why
it would be different in pure FreeDOS.
Franta Hanzlik
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Command Line Parsing
I've noticed a difference in command line parsing between FreeDOS and PC-DOS. Both FreeDOS and PC-DOS put the command line, starting with the character after the executable, in a buffer at offset 0x80 in the PSP. The behavior difference I see with FreeDOS is if the first non-blank character after the executable is a left parenthesis, then FreeDOS sets 0x80 in the PSP to zero so the rest of the command line is not available. Examples of what is in PSP 0x80: Command Line: SOMEPROG (aa bb cc FreeDOS: \0 DOS: (aa bb cc\0 Command Line: SOMEPROG abc (cc dd ee FreeDOS and DOS: abc (cc dd ee\0 Does anyone know why FreeDOS behaves differently when the first character after the executable is a left parenthesis? -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command Line Parsing
Hi, On Thu, May 15, 2014 at 2:57 PM, Jack Jackson j...@pebbleridge.com wrote: I've noticed a difference in command line parsing between FreeDOS and PC-DOS. The behavior difference I see with FreeDOS is if the first non-blank character after the executable is a left parenthesis, then FreeDOS sets 0x80 in the PSP to zero so the rest of the command line is not available. Does anyone know why FreeDOS behaves differently when the first character after the executable is a left parenthesis? No idea, that's very weird. Please try both 0.82 and 0.84 to confirm this bug exists in both. (I assume 4DOS doesn't have this problem.) Feel free to make an official bug report on SourceForge: http://sourceforge.net/p/freedos/bugs/ -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command line sector read and write tool?
On Thu, Dec 11, 2008 at 9:58 AM, Travis Siegel tsie...@softcon.com wrote: If copying raw sector information is all you're after, then you can use rawrite, I used it many times to write out boot disks for booting linux file systems. I don't know of a dd version for dos (thought I'd used one, but it wasn't dd), though it shouldn't be difficult to make one. Don't know if this helps or not, but hope it at least offers another option. BTW, if anyone is still looking for a DOS port of 'dd', there's a version 2.1 (1990) available in the GNUish archive at ibiblio: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/gnuish/gnufut21.zip -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command line sector read and write tool?
Hi! Is there a command line tool to read a sector from harddisk, store it somewhere and write it back later? While not user-friendly at all, you can use DEBUG for this as long as the sector is inside a FAT formatted partition. Old DEBUG versions do not support FAT32. If the sector is the MBR, then you probably find quite a few free existing tools for backup and restore of MBR. Eric -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command line sector read and write tool?
Eric schrieb: Alternatively, you could search for a dos port of dd dd for DOS sounds interesting. Was there ever a DOS port? There is dd for Windows, does someone got it to run under HX DOS Extender? -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command line sector read and write tool?
Hi! Of course there are DOS versions of DD, as for many GNU tools, for example on www.delorie.com - however, there is a misunderstanding: DD alone does not help you editing disks. The trick is that the Linux kernel lets you access disk devices (for whole disks and for partitions) as if they were files... This is not the case with the DOS kernel. To access DOS block devices, you would use other tools... Which certainly do exist but I know no good example apart from DEBUG ;-). You have similar problems in Windows. Of course you can still do all the fun stuff that DD can do if you have a diskimage as a file, even in DOS and Windows, with the DOS and Windows versions of DD ;-). Alternatively, you could search for a dos port of dd dd for DOS sounds interesting. Was there ever a DOS port? There is dd for Windows, does someone got it to run under HX DOS Extender? -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command line sector read and write tool?
If copying raw sector information is all you're after, then you can use rawrite, I used it many times to write out boot disks for booting linux file systems. I don't know of a dd version for dos (thought I'd used one, but it wasn't dd), though it shouldn't be difficult to make one. Don't know if this helps or not, but hope it at least offers another option. -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
