Tip: *.img

Hi Well,

1) M$ calls what the whole rest of the world call *.ISO,
*.img. They HAVE to be different! You can just rename
them, if you please. I do.

2) And, well now, I actually found another feature I like about
Windows Nein (W10). Will wonder ever cease!

Since I am a Linux shop, I have all the cool tools for
reading *.ISO files, so I never really paid attention to
a new feature in W-Nein (10).

In Windows Explorer (WE) (NOT Internet Explorer), you can
just double click on a *.iso file and WE will mount it for
you. You can then copy files out of it. Right click on it
to eject. Sweet.

I have used the above to download M$O (M$ Office) images
on to customer's machines for installation. (I typically
carry M$O 2016 and 2019 on flash drive with me.)

-T

Why someone would pay $$$ for M$O and not just use Libre Office
is one of those wonders of the universe.

T wrote:

1) M$ calls what the whole rest of the world call *.ISO, *.img.
They HAVE to be different! You can just rename them, if you please.
I do.

IMG for [Disk Image] Image is an archive file, like for backups, OS
images, etc. I'm sure you know backup programs create a single file
(full, differential, or incremental) that are called image backups,
backup images, backup image files, etc.

ISO files *are* disk image files. Saying "image" does not mandate the
file contains a graphical image. It could be an archive, backup, or
document image. Sysprep images are not pretty graphical files you put
in a partition of the drive.

The Recovery Console Mode you can boot into is also called an image. It
is a .dat file listed in BCD where you can select to load that image to
load the OS stored within it. Program code loaded into memory are also
called images. VHD (virtual hard disk) files are image files, too, that
you load using a VMM (virtual machine manager), like with VirtualBox.

Microsoft isn't the only using "image" as a generic term to represent
any file that contains a long number of bits.

https://en.wikipedia.org/wiki/System_image

ISO just means International Standards Organization, and they produce
*lots* of standards. What you call an ISO file is just because the file
has an extension of .iso, and those can also be called ISO image files.

https://www.webopedia.com/TERM/I/ISO_image.html
https://en.wikipedia.org/wiki/ISO_image

Yep, "image" used there with "ISO". Most users just abbreviate and say
"ISO file" rather than "ISO 9660 image file", just like they say "doc
file" instead of "Microsoft [Word] .doc file".

..iso files can also be distributed using the .img extension. They are
both disk image files.

2) And, well now, I actually found another feature I like about
Windows Nein (W10). Will wonder ever cease!

Since I am a Linux shop, I have all the cool tools for
reading *.ISO files, so I never really paid attention to
a new feature in W-Nein (10).

In Windows Explorer (WE) (NOT Internet Explorer), you can
just double click on a *.iso file and WE will mount it for
you. You can then copy files out of it. Right click on it
to eject. Sweet.

I have used the above to download M$O (M$ Office) images
on to customer's machines for installation. (I typically
carry M$O 2016 and 2019 on flash drive with me.)

https://www.tenforums.com/tutorials/...dows-10-a.html

So they added an .iso filetype handler. They also have a .zip filetype
handler (zipfldr.dll) but is that minimally functional handler what you
want for creating and managing compressed archive files? Most users
that do much with those files get a free 3rd party archive manager, like
PeaZip or 7-zip, and those become that filetype's handler. Windows also
has a CD/DVD burner handler. There are lots of free and better
3rd-party alternatives.

For .iso files, I have ISObuster (free) to dig inside and WinCDEmu
(http://wincdemu.sysprogs.org/) to load (mount) them. There are lots of
free ISO mount tools, and long before Microsoft got around to adding a
handler for .iso filetypes.

There are even .iso, .img, .nrg, and other disk image filetype mounters
that try to circumvent protections, like for game CDs/DVDs. I forget
the one that uses a fluffy lamb logo (starts with "e", as I recall).

-T

Why someone would pay $$$ for M$O and not just use Libre Office
is one of those wonders of the universe.

Not relevant to your post. Use a sigblock delimiter for the fluff.

On Mon, 17 Dec 2018 19:00:29 -0600, VanguardLH wrote:

There are even .iso, .img, .nrg, and other disk image filetype mounters
that try to circumvent protections, like for game CDs/DVDs. I forget
the one that uses a fluffy lamb logo (starts with "e", as I recall).

Elby?

https://www.elby.ch/en/

I've been using their Virtual CloneDrive product for years.

On 12/17/18 5:00 PM, VanguardLH wrote:
For .iso files, I have ISObuster (free) to dig inside and WinCDEmu
(http://wincdemu.sysprogs.org/) to load (mount) them. There are lots of
free ISO mount tools, and long before Microsoft got around to adding a
handler for .iso filetypes.


I usually just boot off a Fedora stick and then I have tons
of cool file tools available withuot having to look them
up and download them. That is why I missed w-nein mounting
iso's now. Spoiled that way I guess.

I use Fedora a lot to recover files from non-bootable Windows
disks -- ALL THE TIME.

Char Jackson wrote:

On Mon, 17 Dec 2018 19:00:29 -0600, VanguardLH wrote:

There are even .iso, .img, .nrg, and other disk image filetype mounters
that try to circumvent protections, like for game CDs/DVDs. I forget
the one that uses a fluffy lamb logo (starts with "e", as I recall).

Elby?

https://www.elby.ch/en/

I've been using their Virtual CloneDrive product for years.

Yeah, Elby, that's it.

T wrote:

On 12/17/18 5:00 PM, VanguardLH wrote:
For .iso files, I have ISObuster (free) to dig inside and WinCDEmu
(http://wincdemu.sysprogs.org/) to load (mount) them. There are lots of
free ISO mount tools, and long before Microsoft got around to adding a
handler for .iso filetypes.

I usually just boot off a Fedora stick and then I have tons
of cool file tools available withuot having to look them
up and download them. That is why I missed w-nein mounting
iso's now. Spoiled that way I guess.

I use Fedora a lot to recover files from non-bootable Windows
disks -- ALL THE TIME.

As long as the booted OS can read the file system, any OS can read from
a disk moved from another PC. It becomes a data drive in the adoptive
PC.

On 12/17/18 9:27 PM, VanguardLH wrote:
T wrote:

On 12/17/18 5:00 PM, VanguardLH wrote:
For .iso files, I have ISObuster (free) to dig inside and WinCDEmu
(http://wincdemu.sysprogs.org/) to load (mount) them. There are lots of
free ISO mount tools, and long before Microsoft got around to adding a
handler for .iso filetypes.

I usually just boot off a Fedora stick and then I have tons
of cool file tools available withuot having to look them
up and download them. That is why I missed w-nein mounting
iso's now. Spoiled that way I guess.

I use Fedora a lot to recover files from non-bootable Windows
disks -- ALL THE TIME.

As long as the booted OS can read the file system, any OS can read from
a disk moved from another PC. It becomes a data drive in the adoptive
PC.


True, most of the time.

I have come across directories that Windows could not read but
that Fedora could. Also when booted in PE or Live modes, you
don't have the hassle of locked files. And you can nail
things the bad guys have set up as they are not running
and protecting their files.

And a lot of time, there is only the one computer available.
I do carry Windows PE sticks, but my Fedora sticks are
tremendously more powerful. But sometimes you need both.
(98% of the time I only need Fedora.) The more weapons
in your toolbox the better!