You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologize if it seem improper and unrelated to this place but can't help to ask a salvation from a painful confusing
as Msys2/Mingw64 mainstream give us dd
I've tried to use it to get a blank file;
dd if=/dev/zero of=test.img bs=4M count=473
but failed
so research end up with http://www.chrysocome.net/downloads/ddrelease64.exe
one fork/version would perform it, with ddrelease64 name renamed to mere dd
But on applying it here, ie. in Msys2 environment, and as data or workspace in ext4 Linux' FS so move it by tool Ext2FS file manager, and did
..so on
by such literal CLI syntax which have failed too
So seems the author does mean it'd work only on Windows' native console, as I strongly guess..
go for H:>dd.exe if=/dev/zero' of=iso.img bs=4M count=473
and correct... it works perfect
So how could it be quite badly fail in Bash here even after ~10 CLI differebt syntax tried
How the real correct solution ?
Expected behavior
dd usual working message output
Actual behavior
$ ./dd.exe if=/dev/zero of=iso.img bs=4M count=473
rawwrite dd for windows version 1.0beta1 WIN64.
Written by John Newbigin <[email protected]>
This program is covered by terms of the GPL Version 2.
Error opening input file: 3 The system cannot find the path specified.
Description / Steps to reproduce the issue
Apologize if it seem improper and unrelated to this place but can't help to ask a salvation from a painful confusing
as Msys2/Mingw64 mainstream give us
dd
I've tried to use it to get a blank file;
dd if=/dev/zero of=test.img bs=4M count=473
but failed
so research end up with http://www.chrysocome.net/downloads/ddrelease64.exe
one fork/version would perform it, with
ddrelease64
name renamed to meredd
But on applying it here, ie. in Msys2 environment, and as data or workspace in ext4 Linux' FS so move it by tool Ext2FS file manager, and did
..so on
by such literal CLI syntax which have failed too
So seems the author does mean it'd work only on Windows' native console, as I strongly guess..
go for
H:>dd.exe if=/dev/zero' of=iso.img bs=4M count=473
and correct... it works perfect
So how could it be quite badly fail in Bash here even after ~10 CLI differebt syntax tried
How the real correct solution ?
Expected behavior
dd usual working message output
Actual behavior
Verification
Windows Version
MSYS_NT-10.0-22621
Are you willing to submit a PR?
no
The text was updated successfully, but these errors were encountered: