http://pcug.org.au/info/api.php?action=feedcontributions&feedformat=atom&user=RpetersInfo Wiki - User contributions [en]2026-04-13T15:33:07ZUser contributionsMediaWiki 1.39.17http://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1793Mistakes to Avoid2021-10-05T00:53:12Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, too quickly, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*often a longer "time to boot", on the same hardware, offset by<br />
#**fewer needs to reboot<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Expecting Linux to run (and very fast) on long superceded hardware<br />
#*specialised distributions can run remarkably well on such - but<br />
#**contemporary software, particularly for streaming, graphics editing etc require much more resources<br />
#**a dual-core (or fast single-core) CPU plus 2 GB RAM is required for reliable evaluations <br />
#**the majority of distributions have phased out releases for 32-bit computers<br />
#*popular distributions will run much better if (eventually) installed to SSD - but<br />
#**older computer '''BIOS''' doesn't support "AHCI", which is required to gain much benefit from SSD<br />
#Not Adjusting Settings<br />
#*many apparent "anoyances", such as background image, fonts etc can quickly be changed<br />
#**a summary Handbook is often accessible via the "Help" pull-down menu<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*each Desktop Environment is designed & implemented for a range of characteristics<br />
#**simple v full-featured<br />
#**contemporary v historic "look & feel"<br />
#**low v higher hardware resource pre-requisites<br />
#*many distributions have a choice of Desktop Environments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#**time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same Distribution, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1792Mistakes to Avoid2021-10-05T00:28:35Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*often a longer "time to boot", on the same hardware, offset by<br />
#**fewer needs to reboot<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Expecting Linux to run (and very fast) on long superceded hardware<br />
#*specialised distributions can run remarkably well on such - but<br />
#**contemporary software, particularly for streaming, graphics editing etc require much more resources<br />
#**a dual-core (or fast single-core) CPU plus 2 GB RAM is required for reliable evaluations <br />
#**the majority of distributions have phased out releases for 32-bit computers<br />
#*popular distributions will run much better if (eventually) installed to SSD - but<br />
#**older computer '''BIOS''' doesn't support "AHCI", which is required to gain much benefit from SSD<br />
#Not Adjusting Settings<br />
#*many apparent "anoyances", such as background image, fonts etc can quickly be changed<br />
#**a summary Handbook is often accessible via the "Help" pull-down menu<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*each Desktop Environment is designed & implemented for a range of characteristics<br />
#**simple v full-featured<br />
#**contemporary v historic "look & feel"<br />
#**low v higher hardware resource pre-requisites<br />
#*many distributions have a choice of Desktop Environments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#**time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same Distribution, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1791Mistakes to Avoid2021-10-05T00:25:13Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*often a longer "time to boot", on the same hardware, offset by<br />
#**fewer needs to reboot<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Expecting Linux to run (and very fast) on long superceded hardware<br />
#*specialised distributions can run remarkably well on such - but<br />
#**contemporary software, particularly for streaming, graphics editing etc require much more resources<br />
#**a dual-core (or fast single-core) CPU plus 2 GB RAM is required for reliable evaluations <br />
#**the majority of distributions have phased out releases for 32-bit computers<br />
#*popular distributions will run much better if (eventually) installed to SSD - but<br />
#**older computers don't support "AHCI", which is required to gain much benefit from SSD<br />
#Not Adjusting Settings<br />
#*many apparent "anoyances", such as background image, fonts etc can quickly be changed<br />
#**a summary Handbook is often accessible via the "Help" pull-down menu<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*each Desktop Environment is designed & implemented for a range of characteristics<br />
#**simple v full-featured<br />
#**contemporary v historic "look & feel"<br />
#**low v higher hardware resource pre-requisites<br />
#*many distributions have a choice of Desktop Environments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#**time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same Distribution, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1790Mistakes to Avoid2021-10-05T00:02:10Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*often a longer "time to boot", on the same hardware, offset by<br />
#**fewer needs to reboot<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Not Adjusting Settings<br />
#*many apparent "anoyances", such as background image, fonts etc can quickly be changed<br />
#**a summary Handbook is often accessible via the "Help" pull-down menu<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*many distributions have a choice of Desktop Enviroments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#**time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same Distribution, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1789Mistakes to Avoid2021-10-04T23:48:50Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Not Adjusting Settings<br />
#*many apparent "anoyances", such as background image, fonts etc can quickly be changed<br />
#**a summary Handbook is often accessible via the "Help" pull-down menu<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*many distributions have a choice of Desktop Enviroments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#**time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same Distribution, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1788Mistakes to Avoid2021-10-04T23:35:23Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*many distributions have a choice of Desktop Enviroments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#*time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same distribtion, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#**drivers for new hardware might not be available quickly - plus<br />
#**there is insufficient market to make Linux drivers viable for some hardware<br />
#*in general, avoid buying new hardware without doing a search for "hardware model + Linux"</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1787Mistakes to Avoid2021-10-04T23:30:09Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#*many distributions have a choice of Desktop Enviroments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#*time to reboot from USB 3 device is relatively short <br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same distribtion, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison<br />
#Expecting '''all''' of your existing hardware to work<br />
#*Linux generally supports older hardware longer than do other OS - but<br />
#*drivers for new hardware might not be available quickly - plus</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1786Mistakes to Avoid2021-10-04T23:23:04Z<p>Rpeters: </p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates<br />
#Changing Distribution, when a different Desktop Environment would be better<br />
#many distributions have a choice of Desktop Enviroments, whilst being similar "under the hood"<br />
#Installing too Soon<br />
#*live DVD are generally free and do not time-expire<br />
#*evaluate at least '''two''' Desktop Environments<br />
#**from the same distribtion, to get the best comparison<br />
#*evaluate at least '''two''' Distributions<br />
#**staying with one Desktop Environment, to get the best comparison</div>Rpetershttp://pcug.org.au/info/index.php?title=Mistakes_to_Avoid&diff=1785Mistakes to Avoid2021-10-04T23:11:10Z<p>Rpeters: Created page with "Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the follo..."</p>
<hr />
<div>Changing Operating System involves a learning curve and might not be quick. Many people trying Linux abandon the attempt, following inadequate investigation. Avoid the following, common mistakes:<br />
#Expecting a Windows/iOS experience, when the general look & feel might be similar but the different paradigm in Linux results in :<br />
#*"drivers" being generally inbuilt and installed automatically<br />
#*antivirus software not being required<br />
#*frequent, but not automatic updates</div>Rpetershttp://pcug.org.au/info/index.php?title=Selecting_Distribution&diff=1784Selecting Distribution2021-10-04T22:58:41Z<p>Rpeters: introduced concepts of distribution and desktop environment</p>
<hr />
<div>An individual release of Linux is called a "Distribution". The name of the dotISO file that is released often defines the two major components of a distribution:<br />
*distributer's name eg "Mint"<br />
*Desktop Envrionment ("look & feel") eg MATE<br />
<br />
That file is then named along the lines "Mint MATE nnn.iso"<br />
<br />
Mint MATE is a suggested starting point, that is reliable and straight-forward for general users, but might not suit advanced users. The following site contains a selector for various characteristics of distributions eg laptop v desktop, newer v older hardware, "based on":<br />
<br />
https://distrowatch.com/search.php<br />
<br />
The terminology "based on" is usually not included in the file name. It refers to whether the distribution is a boutique, independent collation (not recommended for beginners) or derived from a more widely used distribution. The latter is likely to provide a wider selection of apps, as well as being more stable.</div>Rpetershttp://pcug.org.au/info/index.php?title=Beginners_Start_Here&diff=1783Beginners Start Here2021-10-04T22:37:35Z<p>Rpeters: added wikilink Mistakes to Avoid</p>
<hr />
<div>An essential starting point is a "Live DVD"<br />
<br />
[["Live" CD]]<br />
<br />
Although traditionally referred to as a Live CD, most are now too large for a CD and are a Live DVD instead. It can also be put on a USB Stick, because many modern computers do not have a DVD drive.<br />
<br />
[[Selecting Distribution | Which Linux]]<br />
<br />
[[Mistakes to Avoid]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Beginners_Start_Here&diff=1782Beginners Start Here2021-10-04T22:35:26Z<p>Rpeters: added wikilink Selecting Distribution</p>
<hr />
<div>An essential starting point is a "Live DVD"<br />
<br />
[["Live" CD]]<br />
<br />
Although traditionally referred to as a Live CD, most are now too large for a CD and are a Live DVD instead. It can also be put on a USB Stick, because many modern computers do not have a DVD drive.<br />
<br />
[[Selecting Distribution | Which Linux]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1781Using dotISO Files2021-10-03T02:31:11Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install "Ventoy" [https://ventoy.net/en/download.html Ventoy]<br />
#*available for Windows or Linux<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Ventoy<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
#locate the downloaded dotISO file(s) on hard disk<br />
#*drag & drop the file(s) to the removable media<br />
#*Windows shows the two volumes on Ventoy media as the same drive letter<br />
#*drag only to the exFAT volume<br />
<br />
===Booting Live Media===<br />
#take the Ventoy device containing dotISO files to the computer to be used<br />
#*boot/reboot and go to "Setup"<br />
#*in "Boot" tab, ensure that booting from '''USB HDD''' is enabled<br />
#**a Ventoy device does not behave as a USB DVD<br />
#*(optionally) make USB HDD the first boot device<br />
#**if this is not done, the relevant Function key will need to be pressed, at boot time, to select the Ventoy device<br />
#*save settings and reboot<br />
#select required dotISO<br />
#*Ventoy should display a menu, from which the desired dotISO can be selected<br />
#*a dotISO can take a minute or longer to load, even on fast USB drives<br />
#*most dotISO display some form of progress "meter"<br />
#*a few do not<br />
<br />
===Running from Live Media===<br />
*a session may be run indefinitely<br />
**any work created/edited will generally '''not''' be saved<br />
*a running dotISO will generally have a menu item/icon to "shutdown"<br />
**no additional action is required to close a Ventoy session<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1780Using dotISO Files2021-10-03T02:23:01Z<p>Rpeters: updated boot procedure</p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install "Ventoy" [https://ventoy.net/en/download.html Ventoy]<br />
#*available for Windows or Linux<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Ventoy<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
#locate the downloaded dotISO file(s) on hard disk<br />
#*drag & drop the file(s) to the removable media<br />
#*Windows shows the two volumes on Ventoy media as the same drive letter<br />
#*drag only to the exFAT volume<br />
<br />
===Booting Live Media===<br />
#take the Ventoy device containing dotISO files to the computer to be used<br />
#*boot/reboot and go to "Setup"<br />
#*in "Boot" tab, ensure that booting from '''USB HDD''' is enabled<br />
#**a Ventoy device does not behave as a USB DVD<br />
#*(optionally) make USB HDD the first boot device<br />
#**if this is not done, the relevant Function key will need to be pressed, at boot time, to select the Ventoy device<br />
#*save settings and reboot<br />
#select required dotISO<br />
#*Ventoy should display a menu, from which the desired dotISO can be selected <br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1779Using dotISO Files2021-10-03T02:12:55Z<p>Rpeters: changed writing procedure to suit Ventoy</p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install "Ventoy" [https://ventoy.net/en/download.html Ventoy]<br />
#*available for Windows or Linux<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Ventoy<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
#locate the downloaded dotISO file(s) on hard disk<br />
#*drag & drop the file(s) to the removable media<br />
#*Windows shows the two volumes on Ventoy media as the same drive letter<br />
#*drag only to the exFAT volume<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1778Using dotISO Files2021-10-03T02:05:40Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install "Ventoy" [https://ventoy.net/en/download.html Ventoy]<br />
#*available for Windows or Linux<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Ventoy<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1777Using dotISO Files2021-10-03T01:58:39Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install "Ventoy" [[https://ventoy.net/en/download.html]]<br />
#*unetbootin is now deprecated<br />
#*Linux users install instead packge Imagewriter<br />
#*Windows users obtain instead SUSE Studio Imagewriter https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Imagewriter<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1776Using dotISO Files2021-10-03T01:54:18Z<p>Rpeters: updated advice re SD cards and brought USB devices earlier in document. Changed recommended USB writer to Ventoy</p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
ISO files are typically more than 1 GB in size and will load relatively slowly from USB 2.0 media. New, quality USB 3.0 "thumb drives", of at least 8 GB capacity, are advisable and relatively inexpensive.<br />
<br />
==== Cautions re SD Cards ====<br />
*even quality, fast-rated SD cards are highly dependent on the card reader used - USB thumb drives are a better choice for beginners<br />
*"File Explorer" might not be able to optimally reformat used SD cards. SD Card Consortium provides an App "SD Formater" for best re-formatting of SD cards<br />
<br />
The routines commonly used to produce '''bootable''' SD cards (mostly for Linux but also DOS systems for Firmware upgrades) might overwrite these areas. Experience has shown that:<br />
*bootable SD media perform the intended task well (although speed would depend on class of card)<br />
*SD cards that are to then be used for second or subsequent bootable images require special pre-treatment - See "Strictly for Geeks" below<br />
<br />
SD cards that are later reverted from use as bootable media to use for general storage might perform poorly in the latter application<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is now deprecated<br />
#*Linux users install instead packge Imagewriter<br />
#*Windows users obtain instead SUSE Studio Imagewriter https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Imagewriter<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Using_dotISO_Files&diff=1775Using dotISO Files2021-10-03T01:40:18Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
===Purpose===<br />
Files having the extension *.ISO may be new to some readers.<br />
*now available for download, to reinstall failing Windows 8, 10 or 11<br />
*continue to be the main format for Linux downloads<br />
<br />
These files are essentially an image of a CD, DVD (or BlueRay ?) optical media and usually images of bootable media. dotISO files may be downloaded, saved, copied to other disks/volumes/folders etc, exactly like any other file. However, they require special processing to achieve their usual purpose of producing a '''bootable''' media<br />
*originally dotISO were intended for CD/DVD media<br />
*the same files may now be used on '''bootable''' USB/SD media<br />
**this requires a '''different''' program to write the media<br />
<br />
The bootable media are typically used for one of:<br />
* a "live" demonstration system - often based on Linux<br />
* running software for backing up systems and/or data<br />
* installing operating systems<br />
* "rescue" systems<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#c93800; background:#d0c9cc">'''those not familiar with operating systems need to execise caution with the last two'''</span><br />
|}<br />
<br />
<br />
=== Writing Bootable USB/SD ===<br />
<br />
==== Caution re SD Cards ====<br />
According to Wikipedia, SD cards contain areas that should '''NOT''' be reformatted. The SD Card Consortium provides an App "SD Formater" for safe re-formatting of SD cards<br />
<br />
The routines commonly used to produce '''bootable''' SD cards (mostly for Linux but also DOS systems for Firmware upgrades) might overwrite these areas. Experience has shown that:<br />
*bootable SD media perform the intended task well (although speed would depend on class of card)<br />
*SD cards that are to then be used for second or subsequent bootable images require special pre-treatment - See "Strictly for Geeks" below<br />
<br />
SD cards that are later reverted from use as bootable media to use for general storage might perform poorly in the latter application<br />
<br />
==== Writing ISO Files ====<br />
#this method is relatively safe for Linux & Windows users <br />
#*it should suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is now deprecated<br />
#*Linux users install instead packge Imagewriter<br />
#*Windows users obtain instead SUSE Studio Imagewriter https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch Imagewriter<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
== Getting Technical ==<br />
'''non Windows users''' README<br />
=== Writing Bootable USB/SD ===<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''Linux users need to execise great caution with the this procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
Linux users can use the command<br />
<br />
<nowiki># lsblk</nowiki><br />
<br />
to cross check which storage devices are recognised<br />
<br />
All users should cross-check which removable device is to be written by examining the manufacturer ID, partition size, filesystem type (FAT 32) reported by the Operating System<br />
==== Writing ISO Files ====<br />
#this procedure can be achieved via GUI tools<br />
#*it shoulc suceed with all dotISO files, provided that those are bootable images<br />
#obtain and install a suitable program<br />
#*unetbootin is one of the better known<br />
#ensure that the USB/SD media to be used is formatted '''FAT 32''' <br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including scanners, mobile broadband sticks, modems etc<br />
#launch unetbootin<br />
#*locate the downloaded dotISO file on hard disk<br />
#*select the USB/SD media to be written<br />
#*click ''' OK'''<br />
<br />
===Burning Bootable CD/DVD===<br />
<br />
#this will be the simpest and most reliable approach for beginners<br />
#*virtually any computer now in use can boot CD/DVD<br />
#*most OS have suitable software for burning CD/DVD<br />
#a common mistake made by novices is to use their favourite burner software to '''copy''' a *.ISO file to a blank CD/DVD - <span style="color:#c93800;;background:#d0c9cc">'''incorrect'''</span> as explained at http://www.puppylinux.com/cd-puppy.htm<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:#004700; background:#d0c9cc">'''Correct procedure is to use a special option in the burner software to "burn CD ISO image" or "burn DVD ISO image".<br />
</span><br />
|} <br />
==== Windows 7 ====<br />
#via Windows Explorer is the simplest procedure for beginners<br />
#*locate the ISO file in Windows Explorer and right-click it. You will get various options<br />
#*click on 'Open with' then choose 'Windows Disc Image Burner' to produce a bootable CD/DVD<br />
#*to be prudent, tick the 'Verify disc after burning' box'''<br />
#popular burner software Nero has a similar option. Detailed procedure is available at the following site: http://partedmagic.com/doku.php?id=creating_the_livecd_with_nero<br />
#*simply select your dotISO file in lieu of partedmagic.iso<br />
#if none of the above options are available get the product ftp://terabyteunlimited.com/burncdcc.zip and install that<br />
<br />
{|border="1" align="center" style="text-align:center;"�<br />
|<span style="color:#004700; background:#d0c9cc">'''It makes the operation foolproof, because its ''only'' function is to burn ISO images to CD/DVD'''<br />
|}<br />
==== Other OS ====<br />
#most Linux will include CD/DVD burning software such as k3b, XFreeBurn etc, which include the function to "burn CD ISO image"<br />
<br />
<br />
==== Choice of Optical Media ====<br />
#dotISO disks must be "bit-perfect"<br />
#*avoid using cheap media blanks that are sold primarily for audio/video use<br />
#*setting a slower burn speed might produce more reliable results when using untested burner/media combination<br />
#dotISO images that are smaller than 700 MB may be burnt to DVD media<br />
#*most burner software will cope with this<br />
#*doing so is likely to result in the media reading somewhat faster than would be the case with CD media and this can be advantageous for the uses described above.<br />
#dotISO images >700 MB but << a full DVD of 4.3 GB will often be encountered<br />
#*these must be burned to DVD media<br />
#dotISO images > a full DVD size of 4.3 GB are occassionally encountered<br />
#*these can be burned only to '''dual-layer''' DVD media<br />
#*such media is relatively expensive and<br />
#*not all releases of burner software handle it reliably<br />
#avoid burning dotISO to 80 mm diameter mini-CD/DVD<br />
#*from which the read process would be relatively slow<br />
#*not all releases of burner software handle it reliably<br />
<br />
<br />
== Strictly for Geeks ==<br />
<br />
<br />
=== SD Cards ===<br />
If an SD card is to be '''re-used''' then the following preparation should be followed<br />
#attach the card to a Linux PC via a card reader<br />
#use <nowiki># lsblk</nowiki><br />
#*to identify the device as sd(x)<br />
#run <nowiki># dd if=/dev/zero of=/dev/sd(x) bs=1M count=8</nowiki> <br />
#*to zero the first 8M<br />
#*this is the notional "first cylinder" used by Windows devices and to which they might store filesystem metadata<br />
<br />
Experienced users tend to use "dd" to write ISO images to SD cards<br />
*SD cards use very large block sizes and will write slowly with the common 4 kiB block size<br />
*small block sizes might also cause unnecessary write cycle - the mortal enemy of flash memory devices<br />
<br />
Therefore run<br />
<nowiki># dd if=<path to ISO image> of=/dev/sd(x) bs=4M </nowiki> <br />
*to write the image.<br />
<br />
=== Using/Creating ISOhybrid Files ===<br />
This task is for intermediate/advanced users<br />
<br />
==== Overview ====<br />
Some dotISO files are now being provided as "ISOhybrids"<br />
*which have the main advantage of typically booting much faster from USB/SD devices<br />
**because most OS use conservative settings to boot USB/SD devices, in order to cope with older/buggy BIOS<br />
*boot speed is also highly dependent on the "Class" of SD media and (probably) unstated/indeterminate grade of USB "thumbdrive"<br />
<br />
ISOhybrids may also be burnt to conventional CD/DVD/Bluray optical media, or written to USB/SD media, as in general/intermediate procedures above<br />
*hence the "hybrid" descriptor<br />
*but require the alternative procedure below to achieve faster performance from USB/SD devices <br />
<br />
==== Hybridisation ====<br />
#this procedure may be skipped, if the ISO is known to already be hybridised<br />
#dotISO of unknown type may safely be converted to hybridISO via the program "isohybrid"<br />
#*the conversion adds a few tens of kB, if the ISO is not already hybridised<br />
#**which may push the ISO beyond the maximum capacity of optical media<br />
#**alhough these ISOhybrids could still be written to USB/SD media, as in intermediate procedures above, or advanced precedures following.<br />
#*it makes no perceptable difference if the ISO is already hybridised<br />
<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the following procedure - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==== Writing ISOhybrids ====<br />
#as a precaution, disconnect all other USB devices from the computer<br />
#*including printers, scanners, mobile broadband sticks, modems etc<br />
#**any of which could include "storage"<br />
#verify the drive letter/number of the USB/SD media<br />
#*in Windows use "Computer" menu and open the drive<br />
#*in other OS use "My Computer", hdparm, fdisk etc <br />
#*check by manufacturer ID, size, partitioning etc<br />
#the partitioning/format of the USB/SD media to be used is probably immaterial<br />
#*if in doubt, format the single/first partition as '''FAT 32''' <br />
#launch a program for direct writing disk images of storage media eg<br />
#*in Windows use http://www.softpedia.com/get/CD-DVD-Tools/Data-CD-DVD-Burning/Win32-Disk-Imager.shtml or "rawwrite"<br />
#*in other OS use "dd" (or preferably "ddrescue")<br />
#**in this procedure "dd" operates on an '''unmounted''' device<br />
#more detailed instructions are at:<br />
http://en.opensuse.org/SDB:Live_USB_stick#Bootable_USB_from_DVD_or_Net-install<br />
<br />
{|border="1" align="center" style="text-align:center;"<br />
|<span style="color:red; background:#d0c9cc">'''execise great caution with the above programs - an error in selecting the USB/SD device could result in hard disk partition being overwritten'''</span><br />
|}<br />
<br />
==Booting from Media==<br />
[[Booting from Removable Media]]<br />
<br />
<br />
--[[User:Rpeters|Rpeters]] 12:09, 24 August 2012 (EST)<br />
--[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=%22Live%22_CD&diff=1774"Live" CD2021-10-03T01:29:28Z<p>Rpeters: </p>
<hr />
<div>Most Linux can be run from a "Live" CD/DVD/USB media, without installing '''anything''' on the computer's hard drive<br />
*desirable for evaluation of Linux on computers having Windows installed, where inexpert installation could overwrite Windows<br />
**the Windows disk could be electrically disconnected, as an added precaution<br />
*enables unknown Linux to be evaluated for functionality & ease of use<br />
*'''NB''' any software will take relatively long to load and be relatively slow to run in this mode<br />
**SD (or microSD) card, of Class 10 or better rating, in a SD-USB reader will load software many times faster than a DVD drive.<br />
<br />
Live CD/DVD/USB can be created via most operating systems, using files that are mostly free to download from the Internet. See:<br />
[[Using dotISO Files]]</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1773USB demo/installer2021-10-03T01:26:03Z<p>Rpeters: /* Getting Technical */</p>
<hr />
<div>==For General Users==<br />
==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download USB-image]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8"<br />
*unzip <refind...zip> <br />
*dd if=refind-flashdrive-<.n.n.n>.img of=/dev/sd<your USB drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be placed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your USB drive letter><partition-number> bs=4M"<br />
**test boot this on any UEFI computer<br />
*as required, copy additional ISO, to separate partitions<br />
*for more detailed guides, see:<br />
[https://www.rodsbooks.com/refind/ RodsBooks site]</div>Rpetershttp://pcug.org.au/info/index.php?title=Evaluation&diff=1772Evaluation2021-10-03T01:22:32Z<p>Rpeters: </p>
<hr />
<div>*[[USB demo/installer]]<br />
*[["Live" CD]]<br />
*[[Migration Guide and Links to Documentation]]<br />
*[[Printing]]<br />
*[[Scanning]]<br />
*[[Linux at PCUG Centre]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Beginners_Start_Here&diff=1771Beginners Start Here2021-10-02T04:06:30Z<p>Rpeters: </p>
<hr />
<div>An essential starting point is a "Live DVD"<br />
<br />
[["Live" CD]]<br />
<br />
Although traditionally referred to as a Live CD, most are now too large for a CD and are a Live DVD instead. It can also be put on a USB Stick, because many modern computers do not have a DVD drive.</div>Rpetershttp://pcug.org.au/info/index.php?title=Beginners_Start_Here&diff=1770Beginners Start Here2021-10-02T03:50:56Z<p>Rpeters: Created page with "An essential starting point is a "Live DVD""</p>
<hr />
<div>An essential starting point is a "Live DVD"</div>Rpetershttp://pcug.org.au/info/index.php?title=Technical_Info&diff=1769Technical Info2021-10-02T03:44:48Z<p>Rpeters: /* Linux */</p>
<hr />
<div>__NOTOC__<br />
This page is to support a wide variety of technical IT related hints, help guides, howtos and tips, contributed by members on a range of IT related topics of interest.<br />
Some selected categories of information are shown below. Member contributions are encouraged, see [[Info_Wiki:About|About this Wiki]], [[Getting Started Editing Wiki Pages]], and the navigation [[Help:Contents|Help]] page for guidance on doing this.<br />
<br />
<font color=green>Please note that '''information related specifically to''' accessing and using the '''PCUG's 'The Internet Project' (TIP)''' are provided on the '''[http://www.tip.net.au/wiki/ TIP Wiki]'''</font><br />
<br />
Please include a link to <nowiki>[[</nowiki>{{ns:category}}:Technical Info]] at the bottom of any page you create in this area.<br />
<br />
<!-- Define Outer Table --><br />
{|style="border-spacing:8px;margin:0px -8px"<br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top;color:#000"|<br />
<!-- Start of 1st column in own table --><br />
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|-<br />
|style="margin:0;background-color:#cef2e0;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
===Computer Systems===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== Android ====<br />
* [[Getting Started with Android]]<br />
* [[Android_App_Recommendations]]<br />
* [[Connect Android to Computer]]<br />
<br />
==== Apple ====<br />
* [[iPad_App_Recommendations]]<br />
* [[iPhone_App_Recommendations]]<br />
<br />
==== Cross-Platform ====<br />
*[[Apps Recommended]]<br />
<br />
==== Linux ====<br />
* [[Beginners Start Here]]<br />
* [[Linux at PCUG Centre]]<br />
* [[Evaluation]]<br />
* [[Desktop Appearance]]<br />
* [[Installation]]<br />
* [[Configuration]]<br />
* [[Recovery]]<br />
*[[Security]]<br />
<br />
==== Smart devices====<br />
* [[QR codes]]<br />
<br />
==== Windows ====<br />
* [[File sharing between Win7 and XP]]<br />
* [[File sharing between Windows and other OS]]<br />
* [[Two Page Display]]<br />
* [[Win7 Snipping Tool]]<br />
* [[Win7 Hardware Recommendations]]<br />
<br />
==== Windows 8 ====<br />
* [[Do I need Windows 8?]]<br />
* [[Editing Windows 8 - Usefuls]]<br />
* [[Safe mode]]<br />
* [[Install a Start button]]<br />
* [[Confirmation of file delete]]<br />
* [[File history]]<br />
* [[Storage Spaces]]<br />
* [[MRU]]<br />
* [[CD/DVD player]]<br />
* [[Computer icon on desktop]]<br />
|-<br />
|}<br />
<!-- Start of 2nd column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|-<br />
|style="margin:0;background:#fef2e0;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Internet ===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== Access ====<br />
* [[Internet Access Alternatives]]<br />
<br />
==== E-mail ====<br />
* [[Scams]]<br />
* [[Spam]]<br />
* [[Handling Email SPAM]]<br />
* [[Scareware]]<br />
* [[Long URLs]]<br />
* [[Macros]]<br />
<br />
==== Family Trees ====<br />
* [[Sharing Family Tree Information]]<br />
<br />
==== Web ====<br />
* [[Webmail attachments]]<br />
<br />
==== Web Hosting ====<br />
* [[Web hosting]]<br />
** [[Web hosting in action]]<br />
*** [[A real project]]<br />
<br />
==== Microsoft Web Platform Installer ====<br />
* [[Web PI]]<br />
<br />
==== Wikis ====<br />
<br />
* [[Getting Started Editing Wiki Pages]]<br />
* [[More_on_Working_with_Wikis]]<br />
* [[Wiki Skins]]<br />
<br />
|-<br />
|}<br />
<!-- Start of 3rd column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cedff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Peripherals ===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== DVDs and Bootable USBs ====<br />
* [[Booting from Removable Media]]<br />
* [[Using dotISO Files]]<br />
* [[Creating Bootable DOS USB Memory Stick]]<br />
<br />
==== External Drives ====<br />
* [[External_Drives]]<br />
<br />
==== Monitors & Projectors ====<br />
* [[Full Screen Mode]]<br />
* [[PCUG Training Room - Notes for Presenters]]<br />
* [[Using an External Display or Projector with a Notebook]]<br />
<br />
==== Printers ====<br />
* [[Cleaning Printheads]]<br />
* [[Parallel Port Printers]]<br />
* [[Printer_Driver_not_Available]]<br />
* [[Printing via Network]]<br />
* [[Sharing Printers via CUPS]]<br />
<br />
==== Scanners ====<br />
* [[Scanning Slides using CanoScan]]<br />
* [[Scanning via Network]]<br />
<br />
|-<br />
|}<br />
<!-- Start of 4th column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cefff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Software ===<br />
|- <br />
|style="color:#000"|<br />
<br />
==== Backup ====<br />
*[[Clonezilla]]<br />
*[[Interesting_Techniques]]<br />
<br />
==== Firewall ====<br />
* [[Firewall_Software]]<br />
* [[IPFire]]<br />
<br />
==== General ====<br />
* [[Interesting_Programs]]<br />
*[[PDF_Manipulation]]<br />
<br />
==== Image and Photo Editing ====<br />
* [[GIMP]]<br />
<br />
==== Office ====<br />
*[[Calligra]]<br />
* [[OpenOffice]]<br />
<br />
==== Terminal Emulation ====<br />
*[[Terminal_Emulation]]<br />
<br />
==== Vector Drawing ====<br />
* [[OpenOffice Draw]]<br />
<br />
* [[Inkscape]]<br />
<br />
|-<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cefff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Hardware ===<br />
<br />
==== Disks ====<br />
*[[Advanced Format (AF) Drives]]<br />
*[[Floppy Disk Conversion]]<br />
*[[Secure Erasure]]<br />
*[[Solid State Drives (SSD)]]<br />
<br />
==== Gateway_Router ====<br />
*[[Choice of Type]]<br />
*[[Commercial]]<br />
*[[DIY_Firewall_Router]]<br />
<br />
==== Sub-Compact Computers ====<br />
*[[Android MK802 Pocket PC]]<br />
*[[Raspberry Pi]]<br />
*[[Serial_Console]]<br />
<br />
==== Desk-Top Computers ====<br />
<br />
*[[HP ProDesk 400 G1]]<br />
<br />
==== Telephone ====<br />
*[[NBN]]<br />
*[[TransACT]]<br />
*[[VoiP]]<br />
<br />
|-<br />
|}<br />
|}<br />
<br />
== Related Pages ==<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1768Printing2021-06-10T23:03:59Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Firmware Upgrade====<br />
Apart from the abiility to print without a specific driver, Driverless printing can have other advantages:<br />
*might find more capabilities and options in a printer than are included in the Linux driver<br />
<br />
A Firmware upgrade to the printer might have advantages:<br />
*enable driverless printing, whereas not previously available<br />
*increase functionality eg<br />
**page sizes<br />
**duplexing<br />
**resolution<br />
<br />
There will always be a risk that a firmware upgrade will fail and render the printer unusable<br />
*UPS can generally support inkjet printers during the upgrade<br />
*but Laser printers draw much more current for the fuser<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
== Getting Technical ==<br />
<br />
A good introduction to CUPS is at:<br />
http://support.fccps.cz/download/adv/frr/cups_howto/cups_howto.htm<br />
<br />
It also contains some tips for tuning.<br />
<br />
--[[User:Rpeters|Rod]] ([[User talk:Rpeters|talk]]) 16:32, 3 May 2018 (AEST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1767USB demo/installer2021-02-04T20:58:16Z<p>Rpeters: /* rEFInd */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download USB-image]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8"<br />
*unzip <refind...zip> <br />
*dd if=refind-flashdrive-<.n.n.n>.img of=/dev/sd<your USB drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be placed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your USB drive letter><partition-number> bs=4M"<br />
**test boot this on any UEFI computer<br />
*as required, copy additional ISO, to separate partitions<br />
*for more detailed guides, see:<br />
[https://www.rodsbooks.com/refind/ RodsBooks site]</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1766USB demo/installer2021-02-04T06:32:01Z<p>Rpeters: /* Getting Technical */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download USB-image]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8"<br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be installed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your drive USB letter><partition-number> bs=4M"<br />
**test boot this on any UEFI computer<br />
*as required, copy additional ISO, to separate partitions</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1765USB demo/installer2021-02-04T06:29:53Z<p>Rpeters: /* Getting Technical */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download USB-image]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8"<br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be installed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your drive USB letter><partition-number> bs=4M"<br />
**test boot this on any UEFI computer<br />
*copy additional ISO, to separate partitions</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1764USB demo/installer2021-02-04T06:26:09Z<p>Rpeters: /* rEFInd */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[USB-image,http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8"<br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be installed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your drive USB letter><partition-number> bs=4M<br />
**test boot this on any UEFI computer<br />
*copy additional ISO, to separate partitions</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1763USB demo/installer2021-02-04T06:25:17Z<p>Rpeters: /* rEFInd */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[USB-image,http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter> bs=1M count=8<br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M<br />
**test boot this on any UEFI computer<br />
***it should display pretty icons - including one for "shutdown"<br />
***if not, have you disabled "CSM" & "secure-boot", in UEFI ? (essential)<br />
*return the USB device to a booted Linux computer<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be installed there<br />
*copy one disto ISO to its relevant partition:<br />
*"dd if=<required-distro.iso> of=/dev/sd<your drive USB letter><partition-number> bs=4M<br />
**test boot this on any UEFI computer<br />
*copy additional ISO, to separate partitions</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1762USB demo/installer2021-02-04T06:14:03Z<p>Rpeters: /* Getting Technical */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[USB-image,http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter><br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M<br />
*use GParted (preferably) to create additional partitions, one for each distribution ISO<br />
**oversize each partition a little, to allow for later releases being larger<br />
**format each partition to (preferably) "unformatted"<br />
**give each partition both "label" and "name" relevant to the distro ISO to be installed there</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1761USB demo/installer2021-02-04T06:09:17Z<p>Rpeters: /* rEFInd */</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has three prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
*USB flash media, of at least 8 GB (USB3 preferred) <br />
<br />
The product is available from:<br />
[USB-image,http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download]<br />
<br />
*(caution) insert USB media and run "lsblk" to ascertain it's drive letter - sd(x)<br />
**getting this wrong can result in the existing OS being overwritten<br />
*(advisable) clear the USB drive - "dd if=/dev/zero of=/dev/sd<your drive USB letter><br />
*unzip <refind...zip> | dd of=/dev/sd<your drive letter> bs=4M</div>Rpetershttp://pcug.org.au/info/index.php?title=USB_demo/installer&diff=1760USB demo/installer2021-02-04T06:01:32Z<p>Rpeters: Created page with "==Getting Technical == === rEFInd === This very flexible product has two prerequisites: *computer having modern, UEFI, firmware *user having modicum of command line skill The..."</p>
<hr />
<div>==Getting Technical ==<br />
=== rEFInd ===<br />
This very flexible product has two prerequisites:<br />
*computer having modern, UEFI, firmware<br />
*user having modicum of command line skill<br />
<br />
The product is available from:<br />
[USB-image,http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.0.zip/download]</div>Rpetershttp://pcug.org.au/info/index.php?title=Evaluation&diff=1759Evaluation2021-02-04T05:52:10Z<p>Rpeters: </p>
<hr />
<div>*[[Linux at PCUG Centre]]<br />
*[[USB demo/installer]]<br />
*[["Live" CD]]<br />
*[[Migration Guide and Links to Documentation]]<br />
*[[Printing]]<br />
*[[Scanning]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Multi-media&diff=1754Multi-media2018-10-14T01:07:44Z<p>Rpeters: added ffmpeg</p>
<hr />
<div>ffmpeg is a command line tool. To convert between video formats use eg:<br />
<br />
ffmpeg -i input.avi output.mp4<br />
<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Configuration&diff=1753Configuration2018-10-14T01:03:41Z<p>Rpeters: added page for Multi-media</p>
<hr />
<div>* [[Additional HDD]]<br />
*[[Multi-media]]<br />
*[[Network]]<br />
*[[Printing]]<br />
*[[Scanning]]</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1752IPFire2018-09-08T00:15:40Z<p>Rpeters: primarily to provide practical example using routed modem</p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
Those preferring commercial products can purchase hardware having IPFire preinstalled:<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
A guide to installation and configuration is at:<br />
[https://wiki.ipfire.org/installation/start IPFire Installation]<br />
<br />
The IPFire project deprecates using modems in routing mode. That does not suit NBN users well. An example of how to configure an IPFire device with SOHO LAN is:<br />
[[Media:IPFire_SOHO.png]]<br />
<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1751IPFire2018-09-08T00:13:16Z<p>Rpeters: </p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
Those preferring commercial products can purchase hardware having IPFire preinstalled:<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
A guide to installation and configuration is at:<br />
[https://wiki.ipfire.org/installation/start IPFire Installation]<br />
<br />
The IPFire project deprecates using modems in routing mode. That does not suit NBN users well. An example of how to configure an IPFire device with SOHO LAN is:<br />
[[Media:IPFire_SOHO.png Example SOHO LAN]]<br />
<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1750IPFire2018-09-08T00:10:51Z<p>Rpeters: </p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
Those preferring commercial products can purchase hardware having IPFire preinstalled:<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
A guide to installation and configuration is at:<br />
[https://wiki.ipfire.org/installation/start IPFire Installation]<br />
<br />
The IPFire project deprecates using modems in routing mode. That does not suit NBN users well. An example of how to configure an IPFire device with SOHO LAN is:<br />
[[Media:IPFire_SOHO.png]]<br />
<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=File:IPFire_SOHO.png&diff=1749File:IPFire SOHO.png2018-09-08T00:09:20Z<p>Rpeters: example topology of SOHO LAN using IPFire with modem in routing mode. Not covered in IPFire project's documentation</p>
<hr />
<div>example topology of SOHO LAN using IPFire with modem in routing mode. Not covered in IPFire project's documentation</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1748IPFire2018-09-08T00:05:20Z<p>Rpeters: </p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
Those preferring commercial products can purchase hardware having IPFire preinstalled:<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
A guide to installation and configuration is at:<br />
[https://wiki.ipfire.org/installation/start IPFire Installation]<br />
<br />
The IPFire project deprecates using modems in routing mode. That does not suit NBN users well. An example of how to configure an IPFire device with SOHO LAN is:<br />
[[Media:Example.ogg]]<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1747IPFire2018-09-08T00:00:20Z<p>Rpeters: </p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
A guide to installation and configuration is at:<br />
[https://wiki.ipfire.org/installation/start IPFire Installation]<br />
<br />
The IPFire project deprecates using modems in routing mode. That does not suit NBN users. An example of how to configure an IPFire device with SOHO LAN is:<br />
[[Media:Example.ogg]]<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=IPFire&diff=1746IPFire2018-09-07T23:56:21Z<p>Rpeters: Created page with "This is a fairly flexible firewall-router software, that is freely downloadable: [https://www.ipfire.org/download IPFire Download] *default is ISO image for x86_64 hardware **..."</p>
<hr />
<div>This is a fairly flexible firewall-router software, that is freely downloadable:<br />
[https://www.ipfire.org/download IPFire Download]<br />
*default is ISO image for x86_64 hardware<br />
**image for i586 also available<br />
**image for ARM hardware supports limited range see:<br />
[https://wiki.ipfire.org/hardware/arm/start IPFire ARM Devices]<br />
<br />
[https://www.ipfire.org/hardware Preinstalled Hardware]<br />
<br />
[[User:Rpeters|Rod]]<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Technical_Info&diff=1745Technical Info2018-09-07T23:44:23Z<p>Rpeters: /* Firewall */added section for IPFire - preferred software within PCUG Linux SIG</p>
<hr />
<div>__NOTOC__<br />
This page is to support a wide variety of technical IT related hints, help guides, howtos and tips, contributed by members on a range of IT related topics of interest.<br />
Some selected categories of information are shown below. Member contributions are encouraged, see [[Info_Wiki:About|About this Wiki]], [[Getting Started Editing Wiki Pages]], and the navigation [[Help:Contents|Help]] page for guidance on doing this.<br />
<br />
<font color=green>Please note that '''information related specifically to''' accessing and using the '''PCUG's 'The Internet Project' (TIP)''' are provided on the '''[http://www.tip.net.au/wiki/ TIP Wiki]'''</font><br />
<br />
Please include a link to <nowiki>[[</nowiki>{{ns:category}}:Technical Info]] at the bottom of any page you create in this area.<br />
<br />
<!-- Define Outer Table --><br />
{|style="border-spacing:8px;margin:0px -8px"<br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top;color:#000"|<br />
<!-- Start of 1st column in own table --><br />
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|-<br />
|style="margin:0;background-color:#cef2e0;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
===Computer Systems===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== Android ====<br />
* [[Getting Started with Android]]<br />
* [[Android_App_Recommendations]]<br />
* [[Connect Android to Computer]]<br />
<br />
==== Apple ====<br />
* [[iPad_App_Recommendations]]<br />
* [[iPhone_App_Recommendations]]<br />
<br />
==== Cross-Platform ====<br />
*[[Apps Recommended]]<br />
<br />
==== Linux ====<br />
* [[Linux at PCUG Centre]]<br />
* [[Evaluation]]<br />
* [[Desktop Appearance]]<br />
* [[Installation]]<br />
* [[Configuration]]<br />
* [[Recovery]]<br />
*[[Security]]<br />
<br />
==== Smart devices====<br />
* [[QR codes]]<br />
<br />
==== Windows ====<br />
* [[File sharing between Win7 and XP]]<br />
* [[File sharing between Windows and other OS]]<br />
* [[Two Page Display]]<br />
* [[Win7 Snipping Tool]]<br />
* [[Win7 Hardware Recommendations]]<br />
<br />
==== Windows 8 ====<br />
* [[Do I need Windows 8?]]<br />
* [[Editing Windows 8 - Usefuls]]<br />
* [[Safe mode]]<br />
* [[Install a Start button]]<br />
* [[Confirmation of file delete]]<br />
* [[File history]]<br />
* [[Storage Spaces]]<br />
* [[MRU]]<br />
* [[CD/DVD player]]<br />
* [[Computer icon on desktop]]<br />
|-<br />
|}<br />
<!-- Start of 2nd column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|-<br />
|style="margin:0;background:#fef2e0;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Internet ===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== Access ====<br />
* [[Internet Access Alternatives]]<br />
<br />
==== E-mail ====<br />
* [[Scams]]<br />
* [[Spam]]<br />
* [[Handling Email SPAM]]<br />
* [[Scareware]]<br />
* [[Long URLs]]<br />
* [[Macros]]<br />
<br />
==== Family Trees ====<br />
* [[Sharing Family Tree Information]]<br />
<br />
==== Web ====<br />
* [[Webmail attachments]]<br />
<br />
==== Web Hosting ====<br />
* [[Web hosting]]<br />
** [[Web hosting in action]]<br />
*** [[A real project]]<br />
<br />
==== Microsoft Web Platform Installer ====<br />
* [[Web PI]]<br />
<br />
==== Wikis ====<br />
<br />
* [[Getting Started Editing Wiki Pages]]<br />
* [[More_on_Working_with_Wikis]]<br />
* [[Wiki Skins]]<br />
<br />
|-<br />
|}<br />
<!-- Start of 3rd column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cedff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Peripherals ===<br />
|-<br />
|style="color:#000"|<br />
<br />
==== DVDs and Bootable USBs ====<br />
* [[Booting from Removable Media]]<br />
* [[Using dotISO Files]]<br />
* [[Creating Bootable DOS USB Memory Stick]]<br />
<br />
==== External Drives ====<br />
* [[External_Drives]]<br />
<br />
==== Monitors & Projectors ====<br />
* [[Full Screen Mode]]<br />
* [[PCUG Training Room - Notes for Presenters]]<br />
* [[Using an External Display or Projector with a Notebook]]<br />
<br />
==== Printers ====<br />
* [[Cleaning Printheads]]<br />
* [[Parallel Port Printers]]<br />
* [[Printer_Driver_not_Available]]<br />
* [[Printing via Network]]<br />
* [[Sharing Printers via CUPS]]<br />
<br />
==== Scanners ====<br />
* [[Scanning Slides using CanoScan]]<br />
* [[Scanning via Network]]<br />
<br />
|-<br />
|}<br />
<!-- Start of 4th column in own table --><br />
|class="MainPageBG" style="width:25%;border:1px solid #cedff2;background-color:#f5faff;vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cefff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Software ===<br />
|- <br />
|style="color:#000"|<br />
<br />
==== Backup ====<br />
*[[Clonezilla]]<br />
*[[Interesting_Techniques]]<br />
<br />
==== Firewall ====<br />
* [[Firewall_Software]]<br />
* [[IPFire]]<br />
<br />
==== General ====<br />
* [[Interesting_Programs]]<br />
*[[PDF_Manipulation]]<br />
<br />
==== Image and Photo Editing ====<br />
* [[GIMP]]<br />
<br />
==== Office ====<br />
*[[Calligra]]<br />
* [[OpenOffice]]<br />
<br />
==== Terminal Emulation ====<br />
*[[Terminal_Emulation]]<br />
<br />
==== Vector Drawing ====<br />
* [[OpenOffice Draw]]<br />
<br />
* [[Inkscape]]<br />
<br />
|-<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5faff"<br />
|style="margin:0;background-color:#cefff2;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;"|<br />
<br />
=== Hardware ===<br />
<br />
==== Disks ====<br />
*[[Advanced Format (AF) Drives]]<br />
*[[Floppy Disk Conversion]]<br />
*[[Secure Erasure]]<br />
*[[Solid State Drives (SSD)]]<br />
<br />
==== Gateway_Router ====<br />
*[[Choice of Type]]<br />
*[[Commercial]]<br />
*[[DIY_Firewall_Router]]<br />
<br />
==== Sub-Compact Computers ====<br />
*[[Android MK802 Pocket PC]]<br />
*[[Raspberry Pi]]<br />
*[[Serial_Console]]<br />
<br />
==== Desk-Top Computers ====<br />
<br />
*[[HP ProDesk 400 G1]]<br />
<br />
==== Telephone ====<br />
*[[NBN]]<br />
*[[TransACT]]<br />
*[[VoiP]]<br />
<br />
|-<br />
|}<br />
|}<br />
<br />
== Related Pages ==<br />
[[Category:Technical Info]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1744Printing2018-09-06T12:41:49Z<p>Rpeters: /* Troubleshooting */added sub-section Firmware Upgrade</p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Firmware Upgrade====<br />
Apart from the abiility to print without a specific driver, Driverless printing can have other advantages:<br />
*might find more capabilities and options in a printer than are included in the Linux driver<br />
<br />
A Firmware upgrade to the printer might have advantages:<br />
*enable driverless printing, whereas not previously available<br />
*increase functionality eg<br />
**page sizes<br />
**duplexing<br />
**resolution<br />
<br />
There will always be a risk that a firmware upgrade will fail and render the printer unusable<br />
*UPS can generally support inkjet printers during the upgrade<br />
*but Laser printers draw much more current for the fuser<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
--[[User:Rpeters|Rod]] ([[User talk:Rpeters|talk]]) 16:32, 3 May 2018 (AEST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1741Printing2018-05-03T06:34:17Z<p>Rpeters: /* Printer/Multi-Function Device Recommendations */</p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
--[[User:Rpeters|Rod]] ([[User talk:Rpeters|talk]]) 16:32, 3 May 2018 (AEST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1740Printing2018-05-03T06:32:00Z<p>Rpeters: /* Printer/Multi-Function Device Recommendations */</p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
--[[User:Rpeters|Rpeters]] ([[User talk:Rpeters|talk]]) 16:32, 3 May 2018 (AEST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1739Printing2018-05-03T06:30:45Z<p>Rpeters: </p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
--([[User talk:Rpeters|Rod]]) --[[User:Rpeters|Rpeters]] ([[User talk:Rpeters|talk]]) 16:30, 3 May 2018 (AEST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpetershttp://pcug.org.au/info/index.php?title=Printing&diff=1738Printing2018-05-03T06:27:03Z<p>Rpeters: /* Administration */added requirement for "avahi" in many situations</p>
<hr />
<div>== For General Users ==<br />
New users of Linux may find that their printer (and scanner) is neither supported nor supportable. Simplest option is to (carefully) purchase a new printer.<br />
<br />
=== Selection Guideance ===<br />
*printers that were manufactured after 2009 and connect via Ethernet or wifi are likely to be usable without drivers<br />
**this is potentially the best support for Linux<br />
**from CLI, run "driverless list"<br />
***only printers that report an interface of "ipp://<blah.blah.blah>" are likely to be usable driverless<br />
***see below for an outline of setting up driverless printing<br />
*if a printer must use a driver then be aware that Linux uses Postscript or PDF technology as the basis for its print sub-system<br />
**printers that use Postscript, PDF or perhaps PCL print languages are readily supportable and likely to remain so<br />
**most entry-level printers do '''not''' use those technologies, that require additonal processing resouces, which in turn adds cost<br />
**be prepared to purchase a mid-range printer (or multi-function device).<br />
<br />
'''All''' of the following pre-purchase research is strongly recommended<br />
*'''read''' general guidance at https://en.opensuse.org/SDB:Purchasing_a_Printer_and_Compatibility<br />
*'''download''' the relevant driver from the manufacturer's web site<br />
*check for availability of alternate drivers at: http://www.openprinting.org/printers<br />
*'''install''' the relevant driver prior to purchase<br />
**in almost all cases this can be achieved without the printer physically present<br />
*seek assistance in a Linux forum if the drivers are not available or don't install<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Administration ====<br />
<br />
The most reliable tool is the command line tool "lpadmin".<br />
<br />
The print sub-system used in Linux, CUPS, is heading towards driverless printing. To try driverless printing run the following commands:<br />
<br />
<nowiki>$ driverless list</nowiki><br />
<br />
<nowiki>will list applicable powered-on printers on your LAN - only those having URL beginning with ipp:// are likely to work driverless</nowiki><br />
<br />
Then execute<br />
<br />
<nowiki># lpadmin -p <parameter> -v <parameter> -m everywhere -E</nowiki><br />
<br />
see man lpadmin for suitable - p parameter. The -v parameter must be the exact ipp:// URL reported by "driverless list"<br />
<br />
"driverless" printing can also be configured via the webbrowser GUI, URL http://localhost:631<br />
*in this case it is essential to use the ipp:// style URL for the network printer<br />
**copy and paste it from output of the "driverlees list" command, if necessary<br />
*in the next page, select manufacturer<br />
**at least two solutions should be found for a printer model "ajax fancy printer"<br />
***ajax fancy printer some driver of some sort<br />
***ajax fancy priner driverless<br />
**highlight the latter, then click on "modify printer"<br />
<br />
A widely deployed GUI printer configuration tool is "system-config-printer". It is the default in many distributions but currently does not handle driverless printing. It may appear in the start menu under various names, eg:<br />
*Print Settings<br />
<br />
Alternative print admin tools are included in the administration menu of some distributions<br />
**these might not detect driverless printers or downloaded drivers and are thus less reliable<br />
<br />
====Can't Access Web Interface ====<br />
Some distributions require additional privilleges, that are controlled by the parameter "SystemGroup" in the file /etc/cups/cups-files.conf<br />
*make a note of the groups permitted via that parameter<br />
*8under usual user administration, add user to one of those groups (other than root)<br />
*or complete the pop-up authorisation as user "root"<br />
<br />
====Can't Access Network Printers ====<br />
Major paradigm shifts occurred with CUPS 1.6 and again with CUPS 2.2.<br />
*"avahi" must now be installed to provide DNSSD services and find network printers or print servers<br />
**it must also be installed on computers that are operating as print servers<br />
<br />
==== Failure to Print ====<br />
Failure to print, although the driver is installed, can result from unsuitable settings.<br />
#from the CUPS Administration tab, select <br />
#*Manage Printers -> Set Default Options<br />
#check the settings for and adjuxt if necessary<br />
##paper size (usually A4 is appropriate)<br />
##paper source (tray (cassette) or manual)<br />
<br />
A paradigm shift occurred with Foomatic 4.n<br />
*Applications now prepare jobs as a PDF file, in lieu Postscript<br />
*opensource drivers (PPD files) should have been converted<br />
*binary drivers from manufacturers might not have been<br />
**LibreOffice allows selection of print job format under Tools -> Options -> Print<br />
***'''deselect''' "PDF as standard print job (not all compilations of LibreOffice have this option)<br />
***although this could be done, on a per job basis, via the print dialog Print Properties -> Device -> Printer Language to be changed to Postscript; this mode is buggy for landscape orientation pages<br />
<br />
=== Printer/Multi-Function Device Recommendations ===<br />
The following factors might assist preparation of a "short-list"<br />
*HP provide Linux support for most of their devices<br />
**low-end devices would be reliant on continuation of this support, as would be the case with other brands<br />
*Fuji-Xerox have argueably the best colour laser technology<br />
**CP/CM 305 series are the lowest cost models having Linux support<br />
**and are competitively priced, for the capability provided<br />
*Brother multi-functions all support scanning via network<br />
**mid-range models do use Postscript and should be supportable long-term<br />
*Epson printers are often supported<br />
**drivers included with Linux often don't support higher resolutions<br />
**full-function drivers are available from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX<br />
**most multi-function devices will scan via network interface, as of mid-2017<br />
**Epson's procedure for client/server scanning gets other brands working too<br />
<br />
--[[User:Rpeters|Rod]] ([[User talk:Rpeters|talk]]) 13:52, 12 September 2014 (EST)<br />
<br />
[[Category:Technical Info]]<br />
[[Category:Recommendations]]</div>Rpeters