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
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.
> 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
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
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
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
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
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,
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
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
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
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
12 matches
Mail list logo
